No. After the 'Login incorrect' (or equivalent on non-Solaris systems) message, login(1) loops around back to prompting for the user name afresh. Try it.
What's unusual here is rather the missing password prompt after 'login root', which is presumably what the fictional -n option (non-existent in BSD or Solaris login) is suppressing.
Almost. The explanation there is that effectively jtnimoy did the terminal user equivalent of motion capture. Xe ran some shell sessions, which were recorded, and the animators took them and reconstructed them in Adobe and Cinema 4D.
I have that forked, as well as a fork of funscii. Both have fixes in the main branch. I've added a fair amount of stuff beyond that in a branch of unscii.
No inline images is not a restriction of the protocol. It's a restriction of the text/gemini MIME content type, and of the browser implementations. A server can still respond with text/html content over the GEMINI protocol, with embedded <image/> data. The GEMINI protocol specification does not restrict what RFC2045 types can be used.
What exactly do you think you are proving? It doesn't matter what some spec theoretically allows, if you want to server something to gemini users it can't have inline images.
It's worth mentioning at this point that one can still get (Open)Solaris descendent operating systems: OmniOS, SmartOS, and Tribblix. The latter still has SPARC in its installation guide.
Another part of my nostalgia with those old workstations (besides the core OS) was the desktop environment, i think CDE or motif or something like that. Something about the look and feel of that DE i always thought was cool!
It's also superficial and wrong, and as bad as dividing people up by hair colour into blondes, brunettes, and redheads.
The way that the BSDs differentiate cannot be reduced in this way, not least because there is a lot of what Justin C. Sherrill (of the DragonFly Digest) calls 'cross-pollination' amongst the BSDs.
A case in point:
Superficially, and erroneously, one might observe that OpenBSD, NetBSD, and FreeBSD have nvi, and only DragonFlyBSD has nvi2. In fact there was a three-way fork of actual Bostic nvi, all of them making revisions and leaving the original behind, and then things got really complex with nvi2 taking from OpenBSD's nvi, and FreeBSD's nvi taking from nvi2; not even getting into the existence of nvi-m17n along the way and how there are nvis in base and nvis in ports. (https://news.ycombinator.com/item?id=48132452) One cannot divide the BSDs up into those that have nvi2 versus those that have nvi.
Yes, you're not at all wrong! However my goal is not to definitively 100% know the exact differences between the BSDs...i merely wanted to seek out a quick/easy starting point (the very high level diffs)...so that i can start *somewhere* and hopefully avoid my paralysis by analysis. :-)
It is a generalization of the essentials, and not wrong.
You know even though I said the execution is unlike linux, in fact, there are many many details that are just like linux! What a freaking ignorant liar eh? There's like 100 things like that you could say. No wait, no way it's exactly 100. There's obviously some other number like 105 or 612 things like that. So superficial and wrong!
With due mention to FreeBSD's jails, BSD's security image developed mostly from OpenBSD which is said to have gained its security focus due to NetBSD being so insecure that the NetBSD folks were able to hack into DeRaadt's forked OpenBSD.
Android's Bionic was based on or heavily influenced by OpenBSD's libc iirc, though.
What's unusual here is rather the missing password prompt after 'login root', which is presumably what the fictional -n option (non-existent in BSD or Solaris login) is suppressing.
* https://illumos.org/man/1/login
* https://man.netbsd.org/login.1
reply