brontitall

There seems to be a link to an English translation in footnote 1 of this article

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

Page 12 (PDF p36) seems almost written for the people who did the Tahoe menus

zsh wants to write a history file so you can recall previous commands. You can disable it or set to to write somewhere else

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.

The form of wording goes back at least to 2014 in The Onion

https://en.wikipedia.org/wiki/%27No_Way_to_Prevent_This,%27_...

FL20 is 2000ft. Did you mean FL200?

Complete (4.5h) interview and transcript are linked from https://amturing.acm.org/interviews/thompson_4588371.cfm

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)

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.

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

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

There is the option of PIN to drive. Evaluate your threat model and decide if you want to enable it.

Except in rapid speech, and particularly at the end of sentences, I can definitely hear “should of” being used by some people in local Australian English.

On mobile so I’m not sure which case OSC52 applies to, but I use mosh+tmux 8-10 hours a day. Both bracketed paste and tmux selection setting local clipboard work fine

I think there’s a bug in Figure 3. The unsigned m will always be >= 0 so the while loop will not terminate.

It it common to use a $ for yen, which is what I see, rather than ¥?

What is up with those prices? They are ridiculous!

I assume you’re aware that Admiral Cloudberg writes for Mentour Pilot on YouTube.

Also, pretty low volume but also low sensationalism the Australian regulator, ATSB, posts report summaries on YouTube.

E.g. https://youtu.be/dum4SfnX8uk

I thought WASM allowed capability based permissions for the code running inside, or has that fallen by the wayside, which was my sad expectation?

Only in the dial string to ATD, surely?

I can see bathtubs being used in places like real estate sites.

Huh, TIL. I guess they might have used TIES

https://en.wikipedia.org/wiki/Time_Independent_Escape_Sequen...

Only if their modem didn’t implement the Hayes command set properly or you could otherwise control the per-character timing of the OS sending. It required a pause (1sec by default), “+++” with no pauses, another pause, _then_ the ATH command

Perhaps a hard link would help to prevent the deletion?

Does anyone know why it’s “code page 437”? Like why 437? Was there 437 code pages before it? Does the 437 bit pattern map to something in the hardware? Was it a character rom part number?

The author has acknowledged their error in the article you’re referring to in a later post https://utcc.utoronto.ca/~cks/space/blog/programming/RustSor...

This was posted a few days ago: https://news.ycombinator.com/item?id=43381088

I’ve found goreleaser very helpful in the past. I notice it now claims support for non-go languages now

https://goreleaser.com/