NIC Bonding and VLAN Tagging, Start to Finish: Bonds, 802.1Q, and Where the Bond Actually Lives
Two NICs, one logical interface, and tagged VLANs on top — the setup every serious server needs, and the three places it goes wrong.
dig example.com +traceThe full delegation chain from the root down, server by server. When a record resolves for everyone but you, +trace shows exactly which link in the chain answers differently. Read more →
Field notes from 30+ years running Unix and Linux in production — from VAX/VMS and Solaris to RHEL fleets and cloud, where downtime was never an option. Written for senior engineers who run production systems. More about unixshadow →
Test everything in dev or a lab first. These are field notes from my systems, not a runbook for yours — you’re responsible for what you run on your own.
Two NICs, one logical interface, and tagged VLANs on top — the setup every serious server needs, and the three places it goes wrong.
Joining Linux to Active Directory with SSSD: realm, adcli, keytabs, and clearing the cache — the whole job, from the first package to the last test.
One interface, several addresses — and the whole nmcli workflow around them: creating connections, setting gateways, modifying profiles, and re-applying without dropping the link.
fstab is the map of the box: six fields per line, and every one of them has bitten someone at 2am — local disks, swap, NFS, CIFS, bind mounts, overlayfs, and the filesystems you leave out.
systemctl, loginctl, journalctl, hostnamectl, timedatectl, localectl, systemd-analyze, resolvectl, networkctl, coredumpctl, busctl — the whole *ctl family, in proportion to how much you will actually use each one.
What happens between typing sudo and getting a root shell: the setuid bit, PAM authentication, sudoers parsing, and why sudo -l matters.