home.social

Search

7 results for “cliffle”

  1. I might bring the disk to someone I know with a Mac, but Apple hops standards so often that I'm not sure it'll work:

    - I bought the disk to use with a Mac so of course it's...Firewire.
    - It's HFS+, which is at least partially deprecated in modern Mac OS
    - It's a 2007-vintage Time Machine volume, I wonder if that even works with modern Time Machine

    So for now, using the hfsfuse implementation on Linux, which handles hardlinks well (and is also read-only which in this case is a plus).

  2. Trying to recover some files from an old Apple Time Machine disk in a house with zero Macs, and...

    my goodness directory hardlinks in HFS+ are a hack.

  3. As of today I have been "graduated" from physical therapy. 🎓

    The concept of graduating is odd, because I still have persistent neck and shoulder pain, but (1) it's not debilitating and (2) they seem confident that I will do the right things about it if/when it recurs.

    I am definitely less, like, _actively disabled_ than I was four or six months ago. I think the most hours of a day I've lost to pain recently is like two-three instead of 8-12. So that seems like a thing to celebrate.

  4. Something about my ADHD brain causes me to work on projects in cyclic patterns. I associate things with seasons. I tend to work on Forth things in the fall, for whatever reason.

    I recently managed to recover an ancient backup disk of mine, which includes the sources to PropellerForth, my first reasonable Forth system, which I had thought lost.

    The timestamps on those sources are ... exactly 20 years ago this week. 🤯

  5. At a cafe yesterday I decided to try something completely different, and sketch out a microarchitecture implementing the UXN instruction set on an FPGA. After a couple hours of analysis, I reached an unexpected conclusion:

    While these terms are not often used for stack machines, I think there's a strong argument that UXN is "CISC" to my Forth machine's "RISC." This is not intended as a criticism!

    Individual UXN instructions can touch up to twelve stack locations (ROT2k). Device accesses are blocking and stop the instruction flow for complex operations like traversing a filesystem. An implementation of reasonable complexity would almost certainly want to be microcoded, and device operations would either need to trap into something like the Alpha's PALcode (though the instruction space is fully packed, so it might need to change instruction sets) or invoke an auxiliary core.

    Of course, UXN is designed to be emulated in software, not hardware, and when writing an emulator, it's often useful to have instructions be bigger and more complex to reduce dispatch overhead. This is why my comments shouldn't be taken as criticism -- this property of UXN is fit for purpose. But I suspect the easiest way to implement it in a CPU is to build a specialized CPU running an emulator for it.

  6. Well this is possibly the most Berkeley news story of late.

    berkeleyside.org/2026/10/27/ch

    Somebody broke into my local farm store and collected all of their chickens before releasing them into the city. My guess is they thought they were "freeing" them, but didn't know anything about chickens. I've kept chickens for much of my life and, uh, do not release chickens into a partially fenced area at night in a city full of raccoons, unless you want chicken salad.

  7. Well this latest Louis Rossman video is interesting, I suspect the student paper at that college would probably love to run the story. If only they were aware #texas #cars #tech #Apple youtube.com/watch?v=ydVElnkdIGg

Share on Mastodon

Enter the server where you have an account.