A different "network-aware" concept of this was "aide", that allowed the checksums to be stored on a server, for mutiple clients. [1]

Had some drawbacks compared to using offline media of course, but in day to day operation on an air-gapped network it had its uses.

Also worth knowing is the "-V" (for very parameter) of rpm.

[1] https://docs.redhat.com/en/documentation/red_hat_enterprise_...

Im a 3D artist not a pixel artist but I've had these Saint11 tutorial series bookmarked for a while:

https://saint11.art/blog/pixel-art-tutorials/

+1 to these, amazing resource. Really helped me.

My own retro 8-bit inspired VT100 terminal emulator called 8btty, mostly running Claude Code, either native build or integrated into the Unreal Engine 5 interface.

The "gimbal lock" on a 2D sphere didn't clue you in?

And you can also argue that that's overengineered (the original NT design docs were posted on here a while ago), that the UNIX model (while much more primitive and simplified) has proven more successful in the real world, and that the original "clean, overengineered" NT design has been buried under a progressively bigger truckload of crap year upon year and is no longer as clean as it once was.

> the original "clean, overengineered" NT design has been buried under a progressively bigger truckload of crap year upon year and is no longer as clean as it once was.

The original UNIX model has (considering the current state of GNU/Linux) similarly buried under a progressively bigger truckload of crap year upon year and is no longer as clean as it once was.

A central difference is: the NT kernel stayed rather clean (the crapload rather happened in the Windows subsystem).

Once you've taken most all of the other subsystems out of NT (which they pretty much have), all you're left with is is the crapload in the Windows subsystem.

Yeah was thinking exactly the same thing.

You don't want to work for IBM unless your life is already over. Been there, done that, never again. It's depressing as hell. Your manager doesn't understand what you do, and they think that once your contract expires you'll be sitting around for weeks waiting for them to renew it.

Stratus VOS ran on a bunch of non-x86 hardware, i860, PA-RISC, 68000. It wasn't Windows (UNIX admin with a modicum of Stratus VOS experience in production, back in the day).

It seems I encountered the “ftServer” line, which on closer inspection launched in 2001, and was indeed intel/windows 2k, based around Pentium III Xeon Chips.

They still list old product sheets here, the oldest being the ftServer 5200 AFAICT - https://www.stratus.com/solutions/previous-generation-produc...

https://www.stratus.com/assets/5200hw.pdf