You are not logged in.
Pages: 1
Topic closed
Is there any possible reason that making a cronjob run:
yes | pacman -Syu
daily would be a bad idea? I don't think I've ever said "no" to pacman before, since he's never made any unreasonable requests before.
Last edited by Cuddles McKitten (2009-10-24 17:48:15)
Offline
Nope.
Last edited by Kooothor (2012-03-06 19:29:29)
ktr
Offline
It is a bad idea. Sometimes there might be a serious update that needs care. If you don't see what has happened to that update, you might reboot into an unbootable system.
Offline
It is a bad idea. Sometimes there might be a serious update that needs care. If you don't see what has happened to that update, you might reboot into an unbootable system.
That's what I was looking for. Thanks.
Last edited by Cuddles McKitten (2009-10-24 17:43:03)
Offline
But you could use
pacman -Syuw --noconfirm
blindly and not run into any trouble (other than filling up your hard drive). It only downloads package updates, allowing you to review the changes made to your system on the next -Su, yet have your packages ready to install. Also, the --noconfirm option does what yes | pacman does.
Offline
Pacman sometimes prints important informations and if you miss something, you will could have problems. Of course you can watch /var/log/pacman.log and bypass that situations. I even saw somewhere script/application for watching pacman.log. You just should be careful.
Offline
If you are constantly reading the Arch news and keeping track of the comments on this board, then your plan might be almost acceptable. However, as reqamst pointed out, Pacman often shows important messages while installing - and it would be far better for you to read those. Unless you enjoy the challenge of fixing a system that won't boot, or a printer that won't print, or whatever, without any information... :-/
Arch updates are very good, and are done correctly the vast majority of the time - but often it's necessary for you to know something before they get applied.
Offline
On my FreeBSD box, and email gets sent with any output to cron jobs. I'm not sure how this gets configured exactly but its a really good idea IMO.
Offline
But you could use
pacman -Syuw --noconfirm
blindly and not run into any trouble (other than filling up your hard drive). It only downloads package updates, allowing you to review the changes made to your system on the next -Su, yet have your packages ready to install. Also, the --noconfirm option does what yes | pacman does.
Note for people coming from Google (as I did): this is also dangerous. It's not quite as dangerous as pacman -Syu --noconfirm, but it's still a bad idea, and here's why:
Partial upgrades are not supported.
At first this may not make sense, but consider: what happens if you don't apply those updates and install something new? The thing you installed is new, because the package databases were refreshed, but the rest of your system hasn't caught up. Therefore you get a partial upgrade situation, which is bad.
Someday I'm going to write a script to fix this. But today is not that day.
Offline
Please don't necrobump threads, especially solved ones:
https://wiki.archlinux.org/index.php/Fo … Bumping.27
Closing
Offline
Pages: 1
Topic closed