Why would you run -Syyu? -Syu is what you want 99% or the time.
Noob here what is the difference?
also why would an extra but the same character y
make a difference? Is that common in the arch linux ecosystem?
The y argument tells pacman to update the package list. This is so your computer is downloading the new packages instead of old ones from last time you updated it. The second y tells it to delete the old package list and download it from scratch. This is useful if pacman isn't working correctly. Maybe the files got corrupted. But it wastes more resources for the repo so it is not recommended as a default.
Oh wow, I have always thought the y
stands for "yes to any questions"
turns out it has a --noconfirm
Should have read the man page......
-y, --refresh
Download a fresh copy of the master package databases (repo.db) from the server(s)
defined in pacman.conf(5). This should typically be used each time you use
--sysupgrade or -u. Passing two --refresh or -y flags will force a refresh of all
package databases, even if they appear to be up-to-date.
Y is a mnemonic for Refresh, of course!
Not everyone uses their computer all the time.
Still no reason ... unless the repo is volatile, and potentially you have a corrupt version, a simple -Syu is always enough.
Over a year, many repos become relative volatile.
pacman-keyring or what that package is called gets stale really quick over longer periods of time. Large updates are quite smooth in Arch, but IIRC, -Syyu has helped me before.
Can't relate. I update compulsively every 2 hours on average.
Real talk: so do I. Part of it is just being a computer nerd, part of it is working in IT, part of it has just been curiously testing Linux.
I have had more stability doing this over the course of a year than I had running the monthly Microsoft updates on Windows 10. On the rare occasions something broke (usually my own tinkering and not the update process) simply reinstalling it actually fixed the problem 90%+. I know I'm preaching to the choir here, but I was legit surprised and thought I would have slightly more problems with a bleeding edge distro.
As well, it's great to be able to just update everything with one simple command on the command line rather than having each application install an updater task that sometimes sits down in the system tray doing nothing but nagging you. Or having a program prompt you for an upgrade only to take you to the download page and make you basically reinstall the app over the old version with questionable results every time ...
Also hard to relate. Got my Gentoo server running full auto updates every morning and then send an ntfy alert on success or failure. Haven't seen a failed update in so long (other than the occasional package that had a bad build or something once in a while).
Back when I was fresh in the Gentoo and Linux world (Gentoo is where I started) and updating once a month, I can definitely say I ran into issues.. dunno if it's that big of an issue these days though.
Not sure if my memory is failing already but I no longer see those "Update portage before anything else" messages.
When something tries to overwrite stuff in /etc and you have to etc-update your shit... that's when things get real
Really hate those few packages that don't give a shit whether or not you've already configured it or not...
That's what the /etc/foo.conf.d/ is for :DDDDD
Yes. Once I actually locked myself out of using sudo and then forgot my root password because I updated the stuff without looking at the content of those files
I just had one of those portage update messages btw, so they are for sure still a thing
One day maybe I'll understand why people are fine with package managers that have you sweat if you're updating whenever the heck you want rather than often and with a second pair of eyes on the news
There are too many in the Linux dev community who cling to their old concepts, even if they are objectively worse. Hell, 99% of distros still don't even come with disaster recovery preconfigured; OpenSuse are the only ones I know where you don't need to be a professional to revert back to a working state in case something broke. This conservatism as well as elitism (nobody needs the new stuff if everyone just gets good and becomes a CLI magician, right?) in the community is holding us back horribly, and it shows.
With nix it's easy to revert, if you keep your previous config. Version it with git and it's really easy.
"It's easy with tool that requires extensive knowledge. Do it with another tool that requires extensive knowledge and it's even easier."
You just showed everyone the elitism I was talking about, thank you.
Meh, I used Gentoo in its literal first release off a DVD with only printed instructions for a stage one build on an old Pentium II. No internet or anything to fall back on. Learnt a hell of a lot (like don't select Firefox and Open Office and do an emerge world
as your first package step after the initial boot because it took literally a week to compile with no indication when it would be done). Definitely have a soft spot for Larry the Cow but after running that setup for a couple of years I feel I've taken what I needed from Gentoo.
Would recommend it to anyone who wants to dig in and really learn what makes their system tick, but not as a daily driver. I feel for me Arch hits the sweet spot, but was happy with Debian/Ubuntu too (at least until Ubuntu went to shit with snaps).
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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.
- 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, <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. ย
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.