Good point.

For example? I thought exactly this was /not/ being done by unicode.

You should try and read the link in the comment you replied to

So what is a sane init system to do in case of a broken disk? Pretend everything's good and mount its filesystems r/w so that we might get away with starting sshd anyway?
A broken disk is a broken disk. Dropping into a single-user console makes sense because "broken disk" comes in too many machine-indistinguishable flavours for a program to meaningfully take care of and the consequences of "just trying something" could be severe.

If you need this kind of robustness, use a RAID.

That's the general idea, yes, as far as we (don't) understand it. Of course, whether that's true or not is an entirely different issue, but this model at least allows us to explain a few things (e.g. CMB).

Assuming "Spacetime began with the Big Bang", I see no room for reasoning about what came "before" it. Of course, our spacetime might embedded into something else, but that's shifting the question rather than answering it, IMO.

It might be the fact that the BSDs already have a mature and sound dependency-based init system.

Came here to say this.

Thanks for the headache

But this is big. It's right there in TFA.

Now we remap the damn key to produce an Escape keysym.

Cardboard? Fucking casual.

The correct solution is to glue a drawing pin onto the keycap, upside down.

bzzzzt.
 
It's not known whether the universe was created by the Big Bang, or the Invisible Pink Unicorn, but if we assume the Big Bang model, then I don't see how there can be any "before" it.

[...] on link-local unicast address fe80::<interface identifier>.

You'd normally just wait for a router advertisement (ICMPv6) message arriving for the "all link-local nodes" multicast address (ff02::1).
If you don't feel like waiting for one, send a router solicitation to the "all link-local routers" multicast address (ff02::2), the router(s) will respond with router advertisements (possibly via unicast in this case, not sure).
The router advertisement contains the (64 bit) interface identifier; the router is then reachable on the link-local unicast address fe80::.

In unix, you can query information about all this after the fact using ndp(8).

HTH

I hope you don't mean on the client end, because that would make a ridiculous claim.

Or on the server end, because that, well, would make a ridiculous claim.

I'm not against offering a browser-or-whatever-based GUI, I just find it a stretch to call that a "small and lean" firewall.