• 0x4E4F@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      Exactly my thoughts as well.

      Why update on that little battery life left… the power will return sooner or later, going without updates even for a week or two is no real problem. Hell, I update like once every 3 weeks to a month, it’s not that big of a deal.

      • Petter1@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        4 months ago

        I update always after a session, meaning about once a month 😂I don’t really need my PC, lol

    • PlexSheep@infosec.pub
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      Wait if the power is out, how do they have Internet to load new packages? Something doesn’t make sense here

      • kolorafa@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        4 months ago

        It first downloads all packages from net, then it proceed totally offline starting by verifying downloaded files, signatures, extracting new packages and finally rebuilding initramfs.

        Because arch is replacing the kernel and inittamfs in-place there is a chance that it will not boot if interrupted.

        This issue was long resolved on other distro.

        One way to mitigate it is by having multiple kernels (like LTS or hardened) that you can always pick in grub if the main one fail.

        • superkret@feddit.org
          link
          fedilink
          arrow-up
          1
          ·
          4 months ago

          This issue was solved on Slackware in 1993.
          It installs a “huge” kernel that contains all drivers to run on almost any hardware by default, alongside the “generic” kernel with only the modules you need. If the generic kernel fails to boot, you always have the backup, which is known to work, cause it’s the kernel you first boot into after installation.

          • lad@programming.dev
            link
            fedilink
            English
            arrow-up
            2
            ·
            4 months ago

            I’m not familiar with slackware but why is specific kernel called generic, while generic one is not called generic? I’m puzzled

            • superkret@feddit.org
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              4 months ago

              I have no idea either.

              Edit: Did some reading. “Linux-generic” is just the name of the linux kernel that is used in most computers (as opposed to Linux-realtime, which is the only other Linux kernel that’s still relevant).

      • Artyom@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        4 months ago

        Cable internet tends to stay online even if your power is out. You’d need a battery backup for your modem/router, but it is possible to stay online. Houses can be clever like that, almost all of your utilities will partially work, even when service is interrupted.

        • cmnybo@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 months ago

          That depends on the ISP having backup batteries for their equipment. It will usually only last a couple of hours. 5G will usually stay up for a few days. For longer outages, you will need satellite internet and lots of fuel for your generator.

  • DefederateLemmyMl@feddit.nl
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    4 months ago
    • Boot to usb
    • Mount your root filesystem
    • arch-chroot your mounted root filesystem
    • mount /boot
    • mkinitcpio -p linux

    Steps 1,2 and 3 are the entry way to solve all “unbootable Arch” problems by the way, presuming you know what needs to be changed to fix it of course.

    • ikidd@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      So I’m trying to understand if you think that shutting down an update during regenerating the initramfs indicates that Arch isn’t stable? Because that’s a FAFO move and would crater any non-atomic update distro.

    • dan@upvote.au
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      4 months ago

      When talking about Linux, “stable” usually means “doesn’t have major changes often”, or in other words, “doesn’t have lots of updates that break stuff”. That’s why “Debian stable” is called that. Arch is not that.

  • FQQD@lemmy.ohaa.xyzOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    I think I didn’t make it clear enough: My laptop was on the power during the update process, when the power randomly cut out - for the first time in about 6 years, it doesn’t happen often. Of course you can interpret it as user error - but I think it’s reasonable to update my system when plugged into, normally reliable power. The laptop battery is pretty much dead, so it would’ve shut itself down automatically anyway.

      • zea@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        If it was on something like BTRFS it’d probably be fine, though I imagine there’s still a small window where the FS could flush while the file is being written. renameat2 has the EXCHANGE flag to atomically switch 2 files, so if arch maintainers want to fix it they could do

        1. Write to temporary file
        2. Fsync temporary file
        3. Renameat2 EXCHANGE temporary and target
        4. Fsync directory (optional, since a background flush would still be atomic, just might take some time)
          • kolorafa@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            4 months ago

            Just having btrfs is not enough, you need to have automatic snapshots (or do them manually) before doing updates and configured grub to allow you to rollback.

            Personally, I’m to lazy to configure stuff like that, I rather just pick my Vetroy USB from backpack, boot into live image and just fix it (while learning something/new interesting) than spend time preventing something that might never happen to me :)