You are not logged in.
- Topics: Active | Unanswered
#1 2012-05-03 15:03:54
- nathanb
- Member
- Registered: 2011-11-28
- Posts: 103
- Website
Update all packages that don't require a restart?
I like to keep my system up-to-date, but it's a big disruption to restart. Is there a quick way to sync/update all packages which don't require a restart and don't have a dependency on a package which requires a restart?
Seems like there's constantly a new kernel in the list of updated packages, but my preferred restart interval is once a month or less. Since my preferred update interval is weekly, right now I'm just manually cherry-picking. Is there a better way?
Offline
#2 2012-05-03 15:38:40
- teateawhy
- Member
- From: GER
- Registered: 2012-03-05
- Posts: 1,138
- Website
Re: Update all packages that don't require a restart?
Generally you should avoid partial upgrades.
https://wiki.archlinux.org/index.php/Pa … nsupported
For a server you can use the LTS Kernel, which is a good idea also because you will have even more stability.
Offline
#3 2012-05-04 01:13:36
- ngoonee
- Forum Fellow
- From: Between Thailand and Singapore
- Registered: 2009-03-17
- Posts: 7,362
Re: Update all packages that don't require a restart?
Cherry-pick and you'll end up sooner-or-later with some type of dead system.
You could just use your own custom kernel to avoid the kernel-related restarts, if you don't want the LTS kernel.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
#4 2012-05-04 01:17:21
- Trilby
- Inspector Parrot
- Registered: 2011-11-29
- Posts: 30,462
- Website
Re: Update all packages that don't require a restart?
Also installing a new kernel doesn't REQUIRE a reboot. The new kernel will be installed and sit patiently waiting not in use while the old one still runs. This is effectively the same as doing the partial update, but fewer headaches of trying to keep track of what was updated when.
Of course there are some conditions that do require the newer kernel be running, but in my experience these aren't all that common. These situations would also be even more of a headache in the case of a partial upgrade.
I've had (at least) two kernel updates (one version, one release) since my last reboot and I have no issues what-so-ever. Though I do know what the first step will be if I get any odd messages about missing libraries.
uname -r: 3.3.2-1 ... yup, been a lil' while.
Last edited by Trilby (2012-05-04 01:24:51)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
#5 2012-05-04 01:28:58
- nathanb
- Member
- Registered: 2011-11-28
- Posts: 103
- Website
Re: Update all packages that don't require a restart?
If partial updates will result in a dead system, this just means that the package dependencies are not set correctly. A complete and correct dependency graph should allow cherry-picking with no problems.
That said, if the pacman system can't provide that, I guess I'll settle for only updating if I'm at a point where it wouldn't be disruptive to reboot.
Offline
#6 2012-05-04 04:01:12
- Jristz
- Member
- From: America/Santiago
- Registered: 2011-06-11
- Posts: 1,048
Re: Update all packages that don't require a restart?
And Kexec not suit yours needs?
Rebbot the system but never restart the computer
Lenovo ThinkPad L420 modified
:: Intel i7 2560QM :: 8 GB RAM :: SSD 256 GB ::
:: DVD read+Writter :: 3 USB 3.0 Expresa Card ::
:: a Favulous 1 mins lasting Io-Li battery ::cry::
Offline
#7 2012-05-04 04:48:36
- ngoonee
- Forum Fellow
- From: Between Thailand and Singapore
- Registered: 2009-03-17
- Posts: 7,362
Re: Update all packages that don't require a restart?
If partial updates will result in a dead system, this just means that the package dependencies are not set correctly. A complete and correct dependency graph should allow cherry-picking with no problems.
'Dependencies' in Arch are generally not versioned because of the headaches that will induce. As a rolling release distro, developers make the assumption that every user will update the whole system at once, and hence versioned deps are only used for special cases.
If A and B depend on libC, any update to libC requires that both be updated. Cherry-picking A alone without updating B, should it then update libC (breaking B) or leave it alone (breaking A)? Changing the system to accomodate cherry-picking is possible but not worth the extra workload.
That said, if the pacman system can't provide that, I guess I'll settle for only updating if I'm at a point where it wouldn't be disruptive to reboot.
It can't, and yes that's a sensible thing to do.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
#8 2012-05-04 07:55:49
- ghen
- Member
- From: Belgium
- Registered: 2010-08-31
- Posts: 124
Re: Update all packages that don't require a restart?
Also installing a new kernel doesn't REQUIRE a reboot. The new kernel will be installed and sit patiently waiting not in use while the old one still runs.
You will no longer be able to load additional kernel modules for your running kernel, as they've been uninstalled.
I just put "IgnorePkg = linux" in my pacman.conf, and only upgrade the kernel when I can reboot shortly afterwards.
Offline