2,079 karma · joined November 29, 2016
jonah AT archive DOT org
https://bsky.app/profile/jonahedwards.com
-
> Outside of fundamentally better workflow improvements, most professional fields don't randomly change their tools. If you gave a professional artist a new pencil that had to be gripped differently for no reason, they'd throw it in the trash.
>
> But in software, we tolerate buggy tools that change all the time for no discernible reason. We tolerate software that simultaneously targets professionals and casual users, serving both segments poorly. We tolerate software that can't be customized or adapted for specific workflows. It's tough to put into words, but if you watch a musician or a painter interact with their tools, there's a very clear difference that emerges, and over time you start to realize how much better all of their stuff is.
>
> In most professional artistic settings, workflow changes only happen because they have a clear benefit -- drawing from your shoulder instead of your wrist, changing your embouchure if you play an instrument. And even in those fields, it's generally accepted that over time people will end up with very specialized setups that are very consistent and refined and that remain constant for years and years.
>
> Only in the software industry would someone tell me that my professional tools should change because change is inherently good. Only in commercial software would an elegant, consistent interface like Markdown that allowed me to build up decades of muscle memory until my computer was an extension of my fingers and I didn't need to think about the way I typed -- only in software would that be considered a bad thing.
(Borges, Funes the Memorious: https://www.sas.upenn.edu/~cavitch/pdf-library/Borges_FunesT... )
----------------------------------------
As you can see from the photo, the potato turns a dark mahogany all the way through (cause it is 355° all the way through). Even the water turns mahogany.
This experiment taught me that not all Maillard reactions produce good flavors. The Maillard pipe potato tastes awful and smells acrid. Damn it’s bad—but it’s instructive.
----------------------------------------
----------------------------------------
It is the user’s responsibility (with help from the configuration program) to avoid configuring the boot PROM on the adapter in such a way that the system is not able to boot. If this does occur, you can manually jump the Test Via using a #2 pencil. The Test Via forces the adapter into test mode, which disables the boot PROM so that the adapter configuration program can be run. You must cover the designated area thoroughly with the pencil mark.
Test mode forces the adapter not to perform the Automatic Initialization sequence, which means the EEPROM is not read and the adapter is left in the following configuration:
■ Address Configuration register = 0000h
■ Resource Configuration register = 0000h
■ Product ID register = 0000h
Test mode also shortens the ID sequence to 8 bytes (first is still FFh and last is 69h) and forces it to the active state (that is, the adapter is active and will respond to I/O cycles at base address 0200h even without going through the ID sequence).
After you are done, thoroughly erase the pencil mark.
----------------------------------------
I could still access the block devices, but couldn't instantiate the logical volumes, and dumping dd chunks showed that there was data there... so I wrote some code to scan the disk for ext2 magic numbers, and once I found them did some math on paper to find the partition boundaries and very... carefully... recreate them. I have a photo of the piece of paper here: https://www.flickr.com/photos/jedwards/4494268626/
ep0: 3c509 in test mode. Erase pencil mark! This means that someone has
scribbled with pencil in the test area on the card. Erase the pencil
mark and reboot. (This is not a joke).
It's the E1 pad between the barcode and the empty BIOS socket: https://en.wikipedia.org/wiki/3Com_3c509#/media/File:3Com_3C...A favorite example is the shape of a budding haploid yeast cell, known in the literature as a shmoo (though as that wikipedia page will indicate, there are a lot of other delightful schmoo/shmoo eponyms): https://web.archive.org/web/20071111122821/http://discoverma...
A photo of the apparatus with the lead to the right: https://www.flickr.com/photos/jedwards/2281494063/
and a close-up of the kiln: https://www.flickr.com/photos/jedwards/2282285754/
IIRC a year or two after I left, they filled the whole space with concrete to build the foundation for a new neighboring building. They found someone who wanted the lead and bucket-brigaded them out of there, which must have been quite a day (the bricks are about 25lb each, and the size of a normal brick)
I linked to the item's main page, which has other download options for different e-readers, metadata, etc, in addition to the bookreader interface (which provides additional options like Read Aloud and Search Inside (and it's open source! https://github.com/internetarchive/bookreader ).
There are a number of features available to Make It Work The Way You Want but they're often nonobvious. As a sibling comment notes, you can set the arp_announce and arp_ignore (and arp_filter) sysctls to instruct the kernel to answer or not answer for arp requests based on interface specifics (the other arp_ sysctls are related to gratuitous arp sending and receipt).
As in this post, you can use the rp_filter sysctl to change the reverse path filtering (as in RFC3704).
Additionally, you can use iproute2 rules and route tables to enforce outbound paths if you want a node to have multiple interfaces on the same subnet without arp confusion.
4 data centers, 745 nodes, 28,000 spinning disks
Wayback Machine: 57 PetaBytes
Books/Music/Video Collections: 42 PetaBytes
Unique data: 99 PetaBytes
Total used storage: 212 PetaBytes