This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1
| //This is a collection of RTTTLs that can be used with any RTTTL player. Foremost it is for the Ulanzi TC001 LED Matrix. | |
| //Onlineplayer: https://adamonsoon.github.io/rtttl-play/ | |
| Original1:d=4,o=5,b=140:16e,16g,16a,16c | |
| //ESPHOME - https://esphome.io/components/rtttl.html | |
| two_short:d=4,o=5,b=100:16e6,16e6 | |
| long:d=1,o=5,b=100:e6 | |
| siren:d=8,o=5,b=100:d,e,d,e,d,e,d,e |
| function ephemeralContainer() { | |
| pod_name="$1" | |
| container_name="$2" | |
| namespace="${3:-default}" | |
| if [[ -z "${pod_name}" || -z "${container_name}" ]]; then | |
| echo "requires pod name as first argument and container name as second argument" | |
| return 1 | |
| fi | |
| pod_json="$(kubectl -n "${namespace}" get pod "${pod_name}" -o json)" | |
| if [[ -z "${pod_json}" ]]; then |
preface: Posting these online since it sounds like these notes are somewhat interesting based on a few folks I've shared with. These are semi-rough notes that I basically wrote for myself in case I ever needed to revisit this fix, so keep that in mind.
I recently bought an LG ULTRAGEAR monitor secondhand off of a coworker. I really love it and it's been great so far, but I ran into some minor issues with it in Linux. It works great on both Mac and Windows, but on Linux it displays just a black panel until I use the second monitor to go in and reduce the refresh rate down to 60 Hz.
This has worked decent so far but there's some issues:
| # | |
| # U2F SSH key generation and installation guide | |
| # | |
| # install U2F libraries on client machine | |
| sudo apt-get install pamu2fcfg libpam-u2f | |
| # | |
| # Currently, there are only two ciphers that support | |
| # 'special keys' or (sk) this is the notation in the |
The IronMon challenge is a Pokémon Randomizer Challenge run created by iateyourpie. Designed to make experiencing the randomizer fun and challenging, while taking away the wild Pokémon grind that come with some other challenges. It was originally made for Fire Red / Leaf Green but the rules can be applied/adjusted for other games as well. If you're interested to find out more about IronMon, join our Discord community!
IronMon has varying levels of difficulties, to keep it more approachable but also provide the toughest challenge possible for those who want it.
| # Manual opt parsing example | |
| # | |
| # Features: | |
| # - supports short and long flags (ie: -v|--verbose) | |
| # - supports short and long key/value options (ie: -f <file> | --filename <file>) | |
| # - supports short and long key/value options with equals assignment (ie: -f=<file> | --filename=<file>) | |
| # - does NOT support short option chaining (ie: -vh) | |
| # - everything after -- is positional even if it looks like an option (ie: -f) | |
| # - once we hit an arg that isn't an option flag, everything after that is considered positional | |
| function optparsing_demo() { |
We're on the cusp of 2022 and most software is now written in JavaScript, but it is still virtually impossible to fail integration tests on a JavaScript error and get a useful stack trace from the browser.
This gist includes my description of the problem and sample code from my attempts to solve it.
window.onerror, unhandledrejection, etc)