To be fair, arch could look like that after a few days.
this post was submitted on 03 Dec 2024
300 points (97.8% liked)
Linux
48740 readers
1203 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
NixOS is like that every day for no reason
staging rebuild cycles only happen every two weeks or so.
The reason is always that something changed and causes all dependent packages to change, requiring a rebuild of those too.
Oh, you updated one byte in your config? Better download the entire ducking Internet and rebuild everything!
load more comments
(2 replies)
Read the Arch news before clicking "yes".
I used to be an adventurer like you, but then I took an error to gpg.
people laughed at me for choosing debian. they asked why i chose to have ancient runes running in my computer
who's laughing now?
Still we, dinosaur.🦖
We are still laughing, no worries.
p.s. Debian is great, I am just a "kind of new" void converted.
load more comments
(2 replies)
load more comments
(1 replies)
I have an Arch laptop that I didn't update for 3.5 years. The system update took a while when I finally went through with it. Amazingly it didn't break anything!
Yes, I am amazed that quite a few people in this thread are saying they 'had to completely reinstall the os' and that it broke everything after not much time. As long as one doesn't rely on the AUR for system critical packages or much in generel, it is incredibly hard to break an Arch system (Manjaro and other Arch-based distros don't count). This is due in part to Arch being quite reproducible but it also having very good maintainership.
It doesn't hurt to apply new package configs by going through pacdiff once in a while though.
Edit: Typo
Manjaro and other Arch-based distros don't count
I think this has a lot to do with it. I have seen people say they use Arch before and then find out they're using a derivative.
I switched from Windows to EndeavourOS a few months ago and haven’t had any issues on my personal computer, it’s amazing.
I also have EndeavourOS as a VM on my work laptop and I somehow managed to break systemd-boot when trying to do a system update though. The system update died halfway through and I defaulted to the classic solution of rebooting, which definitely made things worse because my boot partition in the VM broke. The great thing about Linux, and especially Arch, is the tools and knowledge readily available to fix things and everything was working again (with no data loss) in under 15 minutes. I’ve dealt with similar problems on Windows and either had to accept data loss or deal with significant headaches trying to resolve what should be a simple issue because the operating system refuses to provide basic information.
load more comments
(1 replies)
Sometimes I wish someone would make a an Arch box and come back to it years later to see the updates it has missed.
But that's assuming an Arch box would be reliable enough to stay alive that long lol.
Always heard of 20+ year old bsd and debian machines chugging along with no issue.
I have updated arch systems that had not been powered on for years before. It was fine. No issues what so ever. Arch is not some flaky distro that breaks if you look away for a minute. My main system has had had the same install for over 5 years now and I regularly forget to update it for months at a time. Again, no issues.
Yeah really the biggest issue I could see is pacman’s keyring being so out of date that it has to be manually refreshed with a new one
It won't rise much beyond that, since you only get one update per package. Whether it's upgrading Firefox from version 120 to 121 or to version 130, it doesn't change much in terms of download size, nor the number of updates.
At least, I assume, Arch doesn't do differential updates. On some of the slower-moving distributions, they only make you download the actual changes to the files within the packages. In that case, jumping to 121 vs. 130 would make more of a difference.
If you do want lots of package updates, you need lots of packages. The texlive-full package is always a fun one in that regard...
My arch install has been going strong for about 5 years now
I had that on a physical machine! It broke hardcore lol I had to reinstall the OS after trying to update
load more comments
(2 replies)
You see, this is why atomic desktops aren't a bad idea.
This has nothing to do with immutable desktops.
Well in an immutable distro, there is little to no chance for the system to end up in an unusable state (I guess it is the same for distros which apply the updates atomically). Traditional distros are far more likely to bork when so much shit is updated at once
I don't think this is true. The package manager is there for a reason to prevent that. If you have more updates to install at a time, then the chances are the same as if you would have installed the problematic update one at a time. Just read the manual intervention information from Arch and see if there is something to do, then it won't bork. If people don't know what they are doing and do not read the additional information (that is required to do so on Arch), well yes, then you could end up borking your machine. But not because so many updates are installed at a time. The package manager and operating system and their maintainer designed it in a way that you can install ton of updates at a time without borking. This is fine.
load more comments
(3 replies)
It's arch. There'll be no issue here.
load more comments
(2 replies)
Haskell packages every other day...
And they're red, that means the offer is about to expire. Better act quick!
Better apt quick!
You wouldn’t believe the shit I’ve seen on internet connected production servers…
load more comments
(1 replies)
Nah, just update it.
Those are rookie numbers.
This is why I Dont use rolling release Distros on Pcs i wont use often.
I used to care but with recovery tools being what they are and most apps being containers... my base systems tend to be a little more disposable.
That said, I haven't had problems, even if I am at risk for more of them. I have my snapshots and my backups.
load more comments
(6 replies)
I'm sorry, I gotta - you have the menu on AND the button bar? like, why? you click on those things? you got your screen real-estate on a sale, what?
Be nice, can't you see they're only able to afford red pixels?
load more comments
(6 replies)
Looks like a !!FUN!! time in Dwarf Fortress.
welp, looks like you don't use python virtualenvs... well i guess jokes on you all your shit is probably broken now (and as a bonus, that's probably a big part of the donwload size as well) :p
Probably should, but this machine is already cluttered terribly. A good bit of the download size is likely Pytorch files.
Is it Debian Sid?
arch linux, i'm sshed from my debian machine.
6.5 gigs. "Proceed with installation? y/n"
Yeah, I guess. Fark getting any work done today.
Got busy and didn't update my template for awhile. Machines would be instantiated a few minors back. 9.2 vs 9.4, for instance, but this was back in 7-land.
Updates would be about 600 packages, or most of the install.
Took 5 min, completely safe. Patch, bounce because we looked funny at dbus so it can't cope, and then good to go.
I used to tease my windows peer: he'd be still on "do not turn off your computer".
Recently updated a nixos machine that was on the shelf for five years or so. A few options and packages had been renamed, fixed those, upgrade completed with zero problems.
Only issue with this update was a maintainer's keyring had expired and been replaced, so his packages didn't pass the signing check. After re-installing the keyring, the whole think works fine.
view more: next ›