this post was submitted on 24 Jul 2024
514 points (97.8% liked)

linuxmemes

21249 readers
1389 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    514
    Why block muting the OS? (i.imgflip.com)
    submitted 3 months ago by Gormadt@lemmy.blahaj.zone to c/linuxmemes@lemmy.world
    80 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] davidgro@lemmy.world 14 points 3 months ago (1 children)

    Sure they are, but system apps are still installed in the immutable space initially, which is the important thing, that updates to it can't go there.

    I don't know how desktop immutable systems deal with that.

    [โ€“] flying_sheep@lemmy.ml 3 points 3 months ago

    You can update the whole base image. Vanilla OS and SteamOS have an A/B partition that holds the currently-in-use image and can also hold a to-be-used image.

    Updating works by adding the to-be-used image, setting a configuration option that tells the system to boot that one, and on the next boot it'll check if the new one is bootable, then either boot it and mark it as working, or boot into the old one and display an error about how out wasn't able to boot into the new one.

    There's smart things going on like maybe hard linking files that didn't change between the two images and therefore saving space and copying time.

    The result is that you never have a broken system, but you can still frequently update the base image.