368
submitted 8 months ago by FQQD@lemmy.ohaa.xyz to c/linuxmemes@lemmy.world
top 50 comments
sorted by: hot top controversial new old
[-] gaylord_fartmaster@lemmy.world 237 points 8 months ago

The power is out and my laptop has less than 10% battery left?

It's pacman -Syu time.

[-] 0x4E4F@sh.itjust.works 64 points 8 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 4 points 8 months ago

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

[-] PlexSheep@infosec.pub 22 points 8 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 18 points 8 months ago* (last edited 8 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 7 points 8 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.

[-] sukhmel@programming.dev 5 points 8 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

load more comments (1 replies)
load more comments (2 replies)
[-] Artyom@lemm.ee 12 points 8 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 7 points 8 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.

[-] ByteOnBikes@slrpnk.net 8 points 8 months ago

Average Linux solution.

"Got an emergency? It's so EZ. Just open up the terminal and copy/paste [long string of unreadable text]. Btw fuck windows."

[-] felsiq@lemmy.zip 36 points 8 months ago

Yea as opposed to the windows method of “just open regedit and navigate 8 folders below HKEY_CURRENT_USER to change some ambiguous system variable in hex” lmao

I’ll take editing a text file in /etc/ for my configuration any day

[-] amda@feddit.nl 3 points 8 months ago

Cellular data

load more comments (3 replies)
[-] bitwaba@lemmy.world 18 points 8 months ago* (last edited 8 months ago)

I don't think I've had a pacman update take longer than 10 minutes before. Sounds like OP was updating all their AUR packages too.

Still absolutely a terrible thing to do on 10% battery life. I bet there's an AUR package for "check battery level before update" out there somewhere though.

OPs meme is "use distro whose model is 'give users enough rope to hang themselves' " and complaining he's at the gallows

load more comments (1 replies)
[-] riodoro1@lemmy.world 124 points 8 months ago

shutdown a computer when you shouldn’t computer breaks

how could a computer do this

[-] SaharaMaleikuhm@feddit.org 12 points 8 months ago
load more comments (1 replies)
[-] SpaceCadet@feddit.nl 5 points 8 months ago* (last edited 8 months ago)

Power outages do happen, and I'm pretty sure 90% of the people on this community are not using an UPS.

Given enough users and enough time, it's inevitable that a power outage will happen to some people at an inopportune moment, like while updating an important package like the kernel.

Blaming the user for this is not fair, it's just dumb bad luck.

That said, OP could have done a bit more to fix the issue instead of being an angry man yelling at the cloud. When you're using Arch, the expectation is that you are able to fix relatively simple problems like this, or that you're at least willing to learn it. If you find yourself getting angry when Arch doesn't hold your hand, you probably shouldn't have chosen Arch.

load more comments (3 replies)
[-] FQQD@lemmy.ohaa.xyz 50 points 8 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.

[-] FiskFisk33@startrek.website 48 points 8 months ago

sure, but what os wouldn't break if you did this?

[-] bjoern_tantau@swg-empire.de 27 points 8 months ago

Just about any Linux I've ever used keeps the previous kernel version and initrd around. And nowadays snapper makes a new snapshot before and after every package installation or update.

So, I'd think there are a lot.

[-] axum 7 points 8 months ago

So what I'm hearing is install Linux-LTS and pacsnap

[-] gaylord_fartmaster@lemmy.world 16 points 8 months ago

Plus in Linux you can actually fix this with a live USB, while on Windows you can run startup repair and hope for the best.

[-] superkret@feddit.org 5 points 8 months ago* (last edited 8 months ago)

In Windows you can also fix this with a live Windows USB, manually.

[-] MangoPenguin 11 points 8 months ago

Windows doesn't in my experience, it's surprisingly robust.

But also I thought Linux distros normally keep the old Kernel around after an update so stuff like this doesn't cause a boot failure?

[-] 9point6@lemmy.world 7 points 8 months ago

Yeah windows "cumulative update" upgrades for the past couple of years basically duplicate the whole system directory and apply the update to that leaving the existing one to roll back to if anything fails

load more comments (3 replies)
[-] superkret@feddit.org 10 points 8 months ago

Any immutable distro, Debian, Ubuntu, all their derivatives, Fedora, all its derivatives, OpenSUSE, Slackware, ...
Basically, 95+% of installed Linux systems would retain the old or a backup kernel during an upgrade.

[-] rudyharrelson@lemmy.radio 4 points 8 months ago

Any immutable distro, Debian, Ubuntu, all their derivatives

Debian and Ubuntu are not immutable distributions by default, unless I am mistaken.

load more comments (4 replies)
load more comments (1 replies)
[-] zea_64 3 points 8 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)
load more comments (3 replies)
[-] eldain@feddit.nl 23 points 8 months ago

I still don't get the problem. Are you complaining you have to chroot into your system and finish the update because your power got interrupted? Is a 5 min detour into a live system making you unconfortable? This is how you would fix it in any distro except the image based ones and the arch wiki will guide you excellently how to do it. Good luck!

[-] badloop@discuss.online 22 points 8 months ago

I mean any which way you try to frame this, saying that you won’t use Arch anymore because you didn’t take the precautions necessary based on your situation is gonna take some heat here.

[-] Scipitie@lemmy.dbzer0.com 5 points 8 months ago

What precaution would you expect OP to would've done though? A fallback kernel would be my guess - that's something many casual oriented distro do out of the box basically. . I read your post as "you're right, don't use arch" - something btw which I tend to agree with although I wouldn't say that's because of the precautions.

I use arch because there's no black box magic. For an end user who expects or wants that... Yes, arch might not be the right choice.

[-] verdigris@lemmy.ml 6 points 8 months ago

I don't think lack of precaution was the issue here given that it was an unexpected power failure, but it is a fairly easy fix with a chroot.

load more comments (5 replies)
load more comments (2 replies)
load more comments (3 replies)
[-] SpaceCadet@feddit.nl 35 points 8 months ago* (last edited 8 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.

[-] Lightfire228@pawb.social 4 points 8 months ago* (last edited 8 months ago)

For a while, I had to do this after every kernel update

Turns out, i accidentally had two /boot folders. One was is own partition, and the other was on the rootfs partition. When Arch booted, the separate partition was mounted over the rootfs /boot dir, "shadowing" it

Except, UEFI / GRUB was still pointing to the rootfs partition. So when pacman installed a kernel update, it wasn't able to update the kernel that UEFI was booting, but it was able to update the kernel modules

Kernel no likey when kernel modules are newer than the kernel itself

[-] possiblylinux127@lemmy.zip 16 points 8 months ago
[-] KomfortablesKissen@discuss.tchncs.de 13 points 8 months ago

It is! My Desktop hardly ever topples over!

[-] ikidd@lemmy.world 11 points 8 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.

load more comments (1 replies)
[-] dan@upvote.au 8 points 8 months ago* (last edited 8 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.

[-] sebsch@discuss.tchncs.de 3 points 8 months ago

Stable does not mean it's for everybody. My installation runs since now 10 years.

(The only other distribution this failsafe I know of is Debian)

[-] axum 12 points 8 months ago

If you're planning for this type of failure, what you probably want instead is Aurora from the Universal Blue project. Since it's fedora silverblue underneath, your OS either updates all at once or doesn't.

[-] antihumanitarian@lemmy.world 10 points 8 months ago

I have LTS and zen kernels installed in addition to the default Arch one, that should prevent this yes?

[-] FQQD@lemmy.ohaa.xyz 4 points 8 months ago

I'm not sure - I had zen and the default kernel and both were inaccessible

[-] ReveredOxygen@sh.itjust.works 8 points 8 months ago

This is why you keep a backup kernel

[-] Undearius@lemmy.ca 4 points 8 months ago

This got me looking to see if there is any way to have a fallback as I have had something similar happen to me.

The general advice is to have a liveboot USB around. I even saw that you can have GRUB simply boot from an .iso file on the internal drives, which eliminates the need to keep a USB stick around.

I haven't followed the steps yet but I'll give this a shot because it intrigues me.

https://www.linuxbabe.com/desktop-linux/boot-from-iso-files-using-grub2-boot-loader

load more comments (3 replies)
[-] qjkxbmwvz@startrek.website 4 points 8 months ago

When I used Arch I updated once and it removed the running kernel and its modules. So when I plugged in a webcam it didn't work, since the module was gone.

Not a catastrophe, but it was an off-putting user experience coming from Debian. Arch felt more like a desktop OS, Debian feels more like a server OS to me (updates generally warn/confirm when you need to restart services or the machine).

To each their own! Having more up to date stuff was a nice perk of running Arch, certainly.

load more comments (2 replies)
[-] f4f4f4f4f4f4f4f4@sopuli.xyz 3 points 8 months ago

I was installing Nobara 40 and discovered that the live session is allowed to suspend the PC during the install process. The system ended up having problems with some basic functions...

load more comments
view more: next ›
this post was submitted on 04 Aug 2024
368 points (100.0% liked)

linuxmemes

24607 readers
714 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS