I cut my teeth with DOS and Netware, used Windows until the day 98 was released (had been using the GM for a month), and cut over to Slackware as my daily driver. Dabbled with Redhat before stabilising on Debian, which I’ve never found a need to change from for my headless boxes.

One thing I specifically remember was hand tuning my X11 config to drive my 15” Trinitron at 1024x768 @ ~68Hz.

He truly is an idiot’s concept of a genius.

No one who anctually understands Unix or IP networking would ever craft that as an explanation for this concept.

That said, it’s an excellent explanation of how a lobotomy helped him embrace his true self.

It could be a real address, but not within a /24, nor publicly routable.

Configuring multiple v4 addresses on an interface is a kludge, typically only used on hosts which apply inter-network routing logic. It’s an explicit, primary function of the standard v6 specifications.

With v4, you would use either RFC1918 and NAT, or plumb a public address to the host.

With v6 you should use a ULA and an address with a public prefix, and selectively open ports/services to on appropriate address.

An example is the file sharing and administration daemons on my NAS are only bound to its ULA. I don’t need to worry whether it will accidentally be exposed publicly through fat fingering my firewall config, because it will never route beyond my gateway.

I use ULA prefixes to ensure the management interfaces of my devices don’t leak via public routes.

It’s one of the unique parts of the standard IPv6 stack not back ported to IPv4, that an interface on any host can be configured with multiple addresses. It permits functional isolation with the default routing logic.

IPv6 is far from perfect, but the majority of the arguments I’ve seen against deploying it are a mixture of laziness, wilful ignorance, and terminal incuriosity.