HackerTrans
TopNewTrendsCommentsPastAskShowJobs

brontitall

no profile record

comments

brontitall
·9 giorni fa·discuss
I think the point here is that the Disk II controller did _not_ have a microprocessor or microcontroller. Rather, it was driven by software that ran on the system CPU, requiring minimal additional hardware
brontitall
·mese scorso·discuss
Page 12 (PDF p36) seems almost written for the people who did the Tahoe menus
brontitall
·mese scorso·discuss
zsh wants to write a history file so you can recall previous commands. You can disable it or set to to write somewhere else
brontitall
·mese scorso·discuss
Like a time capsule. Last modified date at the bottom of the page says 2007.

Also: > Saffron has been licensed to Adobe and is shipping in all Flash-based products, including Adobe Flash CS3. The Adobe Flash Player is the world's most pervasive software platform and reaches 99% of Internet-enabled desktops.
brontitall
·2 mesi fa·discuss
The form of wording goes back at least to 2014 in The Onion

https://en.wikipedia.org/wiki/%27No_Way_to_Prevent_This,%27_...
brontitall
·5 mesi fa·discuss
FL20 is 2000ft. Did you mean FL200?
brontitall
·6 mesi fa·discuss
Complete (4.5h) interview and transcript are linked from https://amturing.acm.org/interviews/thompson_4588371.cfm
brontitall
·7 mesi fa·discuss
In the default config, tmux panes _do_ have a highlighted border. It takes a bit to get used to how it’s done when there’s only 2 panes though (half the border is highlighted for each pane)
brontitall
·8 mesi fa·discuss
It reminds me a little of a thing used in clustering of DECs (later HPs) Tru64 Unix.

The clusters had a shared OS image - that is a single, shared root filesystem for all members. To allow node-specific config files, there was a type of symbolic link called a “Context Dependent Symbolic Link” (CDSL). They were just like a normal symlink, but had a `{memb}` component in the target, which was resolved at runtime to the member ID of the current system. These would be used to resolve to a path under `/cluster/members/{memb}`, so each host could have its own version of a config file.

The single shared root filesystem made upgrades and patching of the OS extra fun. There was a multi-phase process where both old and new copies of files were present and hosts were rebooted one at a time, switching from the old to the new OS.
brontitall
·8 mesi fa·discuss
This almost IS the tar format. It’s just a 512 byte header with metadata per file then the file data. Repeat for each file. The cpio format is similar but the header is shorter. Details of the contents of the headers vary, hence the different flavours. And I believe POSIX added extensible extra metadata fields that are saved as a kinda pseudo file
brontitall
·10 mesi fa·discuss
https://en.wikipedia.org/wiki/Yoda_conditions
brontitall
·10 mesi fa·discuss
Interesting! I hadn’t seen that Mad TV ad before. It’s quite reminiscent of this one from The Late Show on Australian TV in 1992. I can totally see people having a similar idea from the same blade escalation process.

https://www.youtube.com/watch?v=gStI9ysPrhs
brontitall
·2 anni fa·discuss
> (Windows also has a stable driver API and I have yet to see a Unix with that, but that's another tangent)

Solaris has (or at least had) DDI (Device Driver Interface) and DLPI (Data Link Provider Interface)