this post was submitted on 27 Apr 2024
-121 points (20.5% liked)

linuxmemes

24192 readers
959 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
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    -121
    nuclear take: (lemmy.world)
    submitted 11 months ago by DanTDM@lemmy.world to c/linuxmemes@lemmy.world
    73 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Shareni@programming.dev 5 points 11 months ago (2 children)

    Run pacman -Syu, reboot, and it fails to boot. Had it happen many times with arch and derivatives on multiple devices. It's far more likely to happen if you don't update for like a month.

    [–] AMDIsOurLord@lemmy.ml 2 points 11 months ago (2 children)

    First off, run Syyu, the old arch gods demand it

    Also have a copy of pacman-static somewhere so that you can fix your shit in case of a partial upgrade (and trust me, it can go horribly wrong)

    And thirdly, Arch is meant as a power user distro -- despite this abhorrent popularity it has gained, the fact of the matter remains that you need to know the system inside and out, if you make your arch system unable to boot..... Don't use arch

    This is not my attempt at elitism. Arch was never meant to be a hassle free distro and it sure as shit is not one.

    There are many maintenance-free distros you can use instead. Can I offer you a Debian in these trying times?

    [–] neoproterozoic@feddit.de 1 points 11 months ago

    Also don't use nvidia hardware

    [–] Shareni@programming.dev 2 points 11 months ago (1 children)

    Also have a copy of pacman-static somewhere so that you can fix your shit in case of a partial upgrade (and trust me, it can go horribly wrong)

    Oh I know, I quickly learned to never update it without having live media nearby to arch-chroot with.

    if you make your arch system unable to boot..... Don't use arch

    The only thing I did to make it unbootable is to update it. Going by that logic nobody should use it.

    This is not my attempt at elitism. Arch was never meant to be a hassle free distro and it sure as shit is not one.

    I definitely agree, that's why I'm commenting against dumbasses suggesting it to beginners. Especially when they glorify AUR.

    Can I offer you a Debian in these trying times?

    No need, I already landed on MX + nix after 2+ years of arch. Nix unstable gives me all of the benefits of arch (except for the DE) and then plenty more on top. Different downsides, but far less stressful. I'm

    [–] AMDIsOurLord@lemmy.ml 2 points 11 months ago (1 children)

    You need to keep the update log and go through the whole thing and see if something needs reconfiguring. Sounds shitty? Yeah, that's why I stopped using Arch and Gentoo despite being a veteran

    Nowadays I just install Debian or some derivative and call it a damn day. Unless you need some exotic setup (and those are more suited to Gentoo or Slackware anyway)

    [–] Shareni@programming.dev 1 points 11 months ago

    Oh I had a far simpler method: update and it fails to boot? Rollback and try updating again in a week. It usually works then, but I had to wait a bit more a couple of times.

    The only exception was that bad GRUB release. I think that's the only update fail that absolutely required arch-chroot.

    [–] Moshpirit@lemmy.world 6 points 11 months ago (1 children)

    Not updating in a month?! What kind of arch user is that?

    [–] Shareni@programming.dev 2 points 11 months ago

    A dumb one using Arch on a backup media device. At least that one dodged the bad grub release.

    I've had it also happen on the main device that was updated multiple times a week.