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
The following grammar is based on this EBNF specifications for EBNF meta-grammar:
ebnf ::= [ global-desc ] { local-desc | rule | comment }
local-desc ::= '{' ? { any-character } ? '}'
global-desc :: "{{" ? { any-character } ? "}}"
rule ::= identifier '::=' expression [ '.' ]Virtualization is the conceptual technology on which modern services (server applications) are built. Whether an application happens to run on a fully- or para-virtualized VM[^2] or is containerized—or even runs on a “bare-metal” physical server after all—most modern services are designed in isolated, replicated, disposable components on commodity hardware.[^3] The [“twelve-factor methodology”][wiggins] (2011) is an influential articulation of the principles
| \documentclass[11pt, oneside]{article} | |
| \usepackage[margin=0.5in]{geometry} | |
| \geometry{letterpaper} | |
| \usepackage[parfill]{parskip} | |
| \usepackage{graphicx} | |
| \usepackage{amssymb} | |
| \usepackage{xcolor} | |
| \pagecolor{white} | |
| \usepackage[colorlinks = true, linkcolor = blue, urlcolor = blue]{hyperref} | |
| \pagestyle{empty} |
If you're self-hosting your services and having trouble getting your emails through Gmail and infuriated by Google's non-existent support, you're not the only one. I'd like to share my experiences trying to get it sorted out.
I'm the author of the post above. You can tell how arrogant Google employees are from all the previous posts he made in the past.
This documentation has moved to a dedicated site.
This documentation has moved to a dedicated site.
| ### | |
| # SSH keys setup with Apple keychain | |
| ### | |
| if [ -z "$SSH_AUTH_SOCK" ] && [ -z "$SSH_AGENT_PID" ]; then | |
| # If no SSH Agent is running, start one and load keys from Apple keychain | |
| eval `ssh-agent -s` &> /dev/null | |
| ssh-add --apple-load-keychain &> /dev/null | |
| else | |
| if [ -z "$(ssh-add -l | grep SHA256)" ]; then | |
| # If agent is running but has no keys, load keys from Apple keychain |
| #!/bin/bash | |
| gdb -p "$1" -batch -ex 'set {short}$rip = 0x050f' -ex 'set $rax=231' -ex 'set $rdi=0' -ex 'cont' |
September 2022:
This has spread to a far wider audience than I had anticipated - probably my fault for using a title that is in hindsight catnip for link aggregators. I wrote this back in 2021 just as a bunch of personal thoughts of my experiences using Rust over the years (not always well thought through), and don't intend on trying to push them further, outside of personal experiments and projects.
Managing a living language is challenging and difficult work, and I am grateful for all the hard work that the Rust community and contributors put in given the difficult constraints they work within. Many of the things I listed below are not new, and there's been plenty of difficult discussions about many of them over the years, and some are being worked on or postponed, or rejected for various good reasons. For more thoughts, please see my comment below.
