• 0 Posts
  • 17 Comments
Joined 3 years ago
Cake day: June 13th, 2023
  • fonix232@fedia.iotolinuxmemes@lemmy.world•All according to keikaku
    2·
    5 hours ago

    Just because the root filesystem is RO, it doesn’t mean you’re left in an entirely read-only system - writeable partitions (either mounted directly to violate paths, such as /home, /var, et cetera, or via some kind of overlay FS approach) do exist.

    The key differentiation is that the core OS - not including custom installed packages in most cases, albeit e.g. NixOS takes the atomic OS to a different level - is immutable aside from OS updates, therefore should any kind of shit hit the proverbial fan, restoring to default OS settings is as quick as a reboot without the write-enabled partitions being mounted (or simply wiping those on boot).

    Your data, however, is your responsibility. You mount it separately from the OS because it is truly separate. You’re modularising your workflow here - the OS provides simply the base software interface to your hardware, and does so in a separate layer, while your own software and data are another segment you don’t want to mix with the OS.

    Protecting that data is up to you - proper backups, 3-2-1 approach, etc. - the idea here is to separate concerns of the OS root fs and your data.

    But by separating the two, and making the OS atomic, you’ve essentially locked yourself into a situation where, should anything go wrong, you can restore your data and your OS separately, and not be exposed to the very thing OP meme’d about - the rootfs being corrupted within days of restoration, taking all your data with it.

  • fonix232@fedia.iotolinuxmemes@lemmy.world•All according to keikaku
    52·
    15 hours ago

    You use reproducible, read only rootfs (essentially what a “live” distro is, to some extent) because it’s 1, reproducible, so you’re not stuck when the system dies for some weird reason 2, it’s read only meaning nothing will modify it. This gives you a base that is stable, easily reproduced on any host, and isn’t up to the whims of what packages you installed and such.

    NixOS is a good candidate for this approach but you can literally turn any distro into such a base. Though it’s preferred to use one dedicated to such endeavours.

    Nobody said anything about bulk mounting anything though? I said mount your data partitions, because presumably you’d have multiple disks holding your data thus multiple partitions…

    And the fact you’ve been working with Linux for 20+ years and have no fucking clue about why someone would want their rootfs RO or RW makes me seriously worried about the very statement that you worked with Linux for 20 years without an understanding of such a basic OS function.

  • fonix232@fedia.iotoLemmy Shitpost@lemmy.world•old school
    14·
    2 days ago

    Gotta go back a little further, Victorian women already had vibrators (although quite large contraptions, and usually not kept at home but provided as a service by certain gentlemen to “reduce female hysteria”).

    Hell, the oldest dildo found by archaeologists goes back some 30 thousand years?

  • fonix232@fedia.iotoLemmy Shitpost@lemmy.world•Guide to Push Gutting a Rabbit
    1·
    11 days ago

    That’s all because the US is such a lawsuit shithole, you can get sued for literally anything. You’re the land of frivolous lawsuits.

    It’s possible to mis-operate machinery accidentally, then have an idiot lawyer chase your ambulance recommending you to sue the manufacturer because they didn’t label it accordingly, therefore they’d be liable. Of course in most cases liability is on the person, but safety measure regulation increases meant that companies were held liable for any small mistake, including lacking appropriate labelling on products even the most mentally challenged would recognise as dangerous…

    Some say it’s a nanny state issue, IMO it’s just a measure to force companies to make safe (as safe as possible, that is) equipment that has gone too far.