Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitates it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Was on kbin.social but created this profile on kbin.run during the first week-long outage.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 0 Posts
  • 46 Comments
Joined 4 months ago
cake
Cake day: June 4th, 2024

help-circle
  • “I’ve said some stupid things and some wrong things, but not that." – an actual Bill Gates quote referring to the 640k quote that won’t die.

    But yes, it was probably satirically ascribed to him because of MS-DOS not having the capability to deal with any more than that amount of RAM for a lot longer than it probably should have.

    The “temporary” solution of requiring an extra driver to be able to do so (EMM386.SYS or similar) remained in place right up until DOS-based Windows was allowed to die.

    (The underlying reason was almost certainly ancient IBM PC memory-mapped IO standards, so maybe we could ascribe the original quote an engineer working there some time around 1980.)


  • (FWIW the downvote wasn’t me)

    That sounds like you’re suggesting that Microsoft wouldn’t care what was installed locally to be able to net-boot / run the rest of Windows.

    I think it’s all but certain that they’d want user’s computers to to boot into something they made, or at the very least, slapped their branding all over, even if that was only a wrapper for their web browser.

    I can definitely see them going down the line of saying that their online apps aren’t guaranteed to work under any other system, going so far as to throw in a few deliberate stumbling hazards for anything that isn’t theirs. (Until anti-trust, etc.)

    And thus, dual booting will still be something that people do. Even if - as you clarified - they’re not going to cripple that as well.


  • The only way to prevent dual booting would require a UEFI/BIOS that pulls the OS straight over a network, bypassing local storage entirely.

    Even if that didn’t already rule it out, the size that OSes are these days makes it even less likely. At least not unless Microsoft (or whoever) are planning to ditch absolutely everyone who doesn’t have gigabit internet. (It would be kind of funny for an OS to go back to being 1990s-sized to mitigate that though. And funnier still when someone inevitably captures it onto a hard disk anyway.)

    A more likely vector would be to deliberately break third party bootloaders every time Windows boots. And that would last until the next anti-trust / monopoly lawsuit and they’d roll it back to the current behaviour of only breaking third party bootloaders on installation.

    And even if somehow that didn’t get rolled back, just wait until hardware vendors introduce this thing called a “switch” that can be added just before the power connector on an SSD. Can’t boot from a drive that has no power. BIOS defaults to the next SATA channel. And now you’re booting into Linux.

    Doing the same for a mobo-mounted NVMe drive is harder but not impossible.




  • Deleting snapshots shouldn’t destroy the system as far as I know. It might confuse Timeshift later down the line if that deletion was done outside of Timeshift’s interface, but they’re supposed to be entirely separate.

    Timeshift creates a directory called “timeshift” in the root of whatever partition it’s configured to use. It should create at least one copy of every file, but it does then create hard links to save space between snapshots where files would otherwise be identical. Those links shouldn’t be to (or from) live system files though.

    Now, if someone was to bypass Timeshift and manually move files of the timeshift directory back into a live system or manually link live system locations into a snapshot, that might lead to the problem you experienced. Not sure if that’s what’s happened.

    It’s worth noting that I have Timeshift set to create its directory in a separate partition on a different physical drive, so if it was broken in some way, it would struggle to mess up. Hard links across partition boundaries are a lot harder to achieve if not impossible, so it would stop someone (or something) trying to bypass Timeshift, or at the very least give them pause for thought. And it would provide some protection against Timeshift doing something silly as well.

    Another way I suspect this could happen is if Timeshift’s own copy as well as all hard links to it in all snapshots were manually deleted before a restore was attempted. Can’t restore from what doesn’t exist, and so the system would remain broken.













  • I’d suggest “Spicious Linux”, but it’s a 5/10 pun at best, and too similar to “specious” which means “sounds legit but isn’t”; not necessarily a good look.

    “Opus” borrows letters and sounds good, but speaking of sounds, it’s the name of a sound codec, so maybe not a good choice.

    “Abstruse” has similar problems to “specious”…

    “ChameleOS” is the name of a dragon in a game.

    I figure if I run through all the bad ideas here, only good ones will be left… but that might well be specious.