home tags events about rss login

Things happen.

zev bonked 21 Jun 2024 12:59 -0700
original: graydon@types.pl

Long post

Long post

@regehr @durin42 @dsp I guess this is part of my "nothing in a vacuum" point though. Git didn't come from CVS. It came from BitKeeper and Monotone; and Monotone came from BitKeeper, Aegis, Venti, Linked Timestamps (and a dozen others we knew of); and BitKeeper came from TeamWare which came from SCCS. If you work through the history there's a nearly continuous "X plus an incremental change" pattern to development, not so much dramatic reorgs.

(IMO this is true of almost all intellectual history and one of the reasons I think it's both an interesting and frustrating field. People _remember_ large structural changes in how-things-happen as though they are anchored in single inventors and singular moments of invention, but when you zoom in on the history they never do. It's more like "incremental changes pile up to the point where a sea-change in the broader field becomes plausible and then later inevitable".)

zev honked back 10 Jun 2024 12:51 -0700
in reply to: https://hachyderm.io/users/w8emv/statuses/112594031441817813

@w8emv @aburka That does sound like sshfs in reverse -- so you could perhaps use sshfs back from the beefy server to your local client (it has configurable caching options available).

Though I wonder if perhaps what @aburka is remembering is cpu from Plan 9? (Which is of course one of those annoyingly-named things that's nigh impossible to search for, so I don't have a great link to point to at the moment...)

zev honked back 22 May 2024 20:28 -0700
in reply to: https://mastodon.social/users/dougall/statuses/112488200751670463

@dougall Also perhaps noteworthy: the commit that fixes it is a revert of a revert...of a revert. (Hello, semantic satiation.)

And further, the commit hashes of second and third commits in that chain of reverts (the most recent two) just so happen to have fourteen prefix bits in common, throwing off my mental tracking of which was which via the first three hex digits when trying to count how many reversions had actually happened.

zev honked 11 May 2024 23:53 -0700

Canis borealis.

dog in profile with aurora in background

zev honked back 24 Apr 2024 19:27 -0700
in reply to: https://hachyderm.io/users/w8emv/statuses/112329305593175834

@w8emv Haven't actually replied to the poll itself because that AP functionality doesn't quite fit within honk's minimalist aesthetic, but: I tend to hold on to the ones for larger/more-expensive items (especially the servers from work, since I'll need to ship those back at some point). As mentioned elsewhere in the thread they're definitely useful when moving, though having made the rent->mortgage jump last year the importance of that is somewhat diminished, so I should probably get rid of some.

(Typing this up has also inspired me to finally toss the two 2.5" SSD boxes that have been sitting on my desk for I-don't-know-how-many weeks now...though those were more accidental than any sort of intent.)

Packrat? Who, me? Never.

zev honked 16 Apr 2024 21:16 -0700

A thing I was just dimly aware enough of to look up how to use once I realized I wanted to try it out and am now quite pleased with:

$ strace -e inject=unlink:delay_enter=5s ....

Super handy for hitting ^Z to intercept a tempfile before it gets deleted -- yet another way in which strace is awesome.

zev honked back 13 Apr 2024 00:46 -0700
in reply to: https://tech.lgbt/users/sjolsen/statuses/112262741877678420

@sjolsen Certainly, it of course doesn't free you from still ultimately using I2C, just a convenient abstraction on top of it...though FWIW 1.5Mbps was the TCP throughput I got out of it with iperf, so including a fair amount of overhead; the actual bus frequency was a good bit higher, and at least on the systems I was running it on it seemed to work well enough (though perhaps I was lucky).

zev honked back 30 Mar 2024 14:15 -0700
in reply to: https://chaos.social/users/ChuckMcManis/statuses/112186273145247536

@ChuckMcManis @dougmerritt Assuming that's regarding just the kernel (and setting aside the problem of auditing 30+ million lines of existing code, which I'd think such a customer might also want?), a dozen people doesn't seem like very many to try to thoroughly vet all the changes that get applied to Linux all the time. Even assuming sufficient subsystem expertise among the entire group to cover everything, the sheer volume per individual would be enormous -- thousands of lines per day, all day every day.

zev honked back 30 Mar 2024 12:48 -0700
in reply to: https://hachyderm.io/users/cliffle/statuses/112185792882765955

@cliffle While I can't claim anything approaching your degree of thoroughness, this patch resulted from me going through a very similar process (involving xmobar) with a new laptop a few years ago. I'd thought it was my Framework, but the timestamp suggests it was probably the Librem that predated it (and that I'd probably still be using if I hadn't fried the display with an ill-advised i2cdump command...),