It's commonly trotted out, but the people who spearheaded the disastrous changes including mass outsourcing were Boeing for life - with McD people writing alarming memos about outsourcing goals set for Dreamliner
Main issue with opening it further is lack of DMU-level userland API, especially given how syscall heavy it could get (and iouring might be locked out due to politics)
The secret is that ZFS actually implements an object storage layer on top of block devices and only then implements ZVOL and ZPL (ZFS POSIX filesystem) on top of that.
A "zfs send" is essentially a serialized stream of objects sorted by dependency (objects later in stream will refer to objects earlier in stream, but not the other way around).
My understanding is that issues in scaling 68k line were already well known by then, same as with VAX (even if crucial people at Digital didn't want to believe).
The difference is that 68k was ubiquitous, reasonably cheap 32bit capable platform with MMU that had huge availability of parts and made porting software easy. Sun was working with 68k partially because they chose it in 1980, a year after it was made available, and by 1986 they published SPARC ISA and shipped first systems a year later
Finder has a lot of signs of being actually a MacOS Classic application - not just the internal presence of Classic-style paths (with ":" separators) but also how Dock was originally developed on MacOS 9.x because the principal developer didn't have OSX machine allocated.
The missing part is the editor - similarly windows lacked (or hid it way too well) the icon editor, unlike OS/2 where I recall spending hours as small kid making custom icons for games like MSFS
There's generally at least one watchdog device available in most PCs delivered in last decade, but it's not always utilized. Essentially at one point an intel southbridge integrated a basic watchdog on all models, and it started to just... be included.
So these days you can find a variation on the TCO timer watchdog in most PCs, even if the exact implementation varies so we now have a bunch of drivers for the different variants.
Linux doesn't see one on my Ryzen 5600X desktop at least. My Intel Skylake Thinkpad does seem to have two though (iTCO as well as INT3F0D, not sure what that is, but if I interpret the files under /sys correctly it belongs to the LPC/eSPI controller PCIe device, while the TCO watchdog is found under the SMBus PCIe device).
In both cases they do have software watchdogs (NMI based) which relies on a hardware timer triggering an NMI in the kernel. But that relies on the NMI handler still working, which is not as good as a real HW watchdog.
Apparently it depends to a little bit on how the motherboard is designed, theoretically SP5100 watchdog which is part of the CPU logic in recent ryzens, apparently, is supposed to be enabled if the motherboard is designed with IPMI in mind.
For whatever reason, it's enabled on my laptop despite it obviously not having IPMI support :)
A lot of "fun" with those documents is that some of them quite probably were archeological digs on Microsoft side too.
For example, the MAPI specs have references to valid parts of the protocols and data structures that are not used anywhere and which in fact crash MAPI libraries (so Outlook and Exchange just throw errors if you give them such data), sometimes giving a glimpse of how there might have been abandoned features that were never delivered.
Like, surprisingly, HTML email support in Outlook[1] :D
[1] MAPI Message struct, and thus Exchange and Outlook, crashes when encountering "HTML message" let's call it "submessage". Turns out the valid way to save a HTML message is by wrapping it in RTF and saving it as Rich Text submessage. Plain text is another submessage.
reply