You are not logged in.
- Topics: Active | Unanswered
#1 2009-02-08 19:26:52
- hbarnwheeler
- Member
- Registered: 2006-08-11
- Posts: 37
Upgrade to 2.6.28 via pacman, keeping 2.6.27
So, I've seen the new kernel in the list generated by pacman-Syu for some time now and I have been hesitant to upgrade as I've seen some people with similar hardware in the forums having trouble with this. Ideally, I'd like to upgrade via pacman, but is there a way I can do this while keeping my current (2.6.27) kernel image so I can boot it for debugging purposes if I have problems with 2.6.28? I imagine I can accomplish this by building a custom 2.6.28 kernel, but I'd like to save myself the hassle if possible.
Offline
#2 2009-02-08 20:08:34
- tomk
- Forum Fellow
- From: Ireland
- Registered: 2004-07-21
- Posts: 9,839
Re: Upgrade to 2.6.28 via pacman, keeping 2.6.27
There is no facility for that in pacman itself, so you would need to do it manually, or with a script. Very briefly, it would involve renaming the files from the 2.6.27 kernel package so that pacman does not remove them when you upgrade to 2.6.28. Then you would need to edit your grub conf to create the necessary stanza for the old kernel - the new one will use the existing stanza, as always.
Offline
#3 2009-02-08 20:10:48
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: Upgrade to 2.6.28 via pacman, keeping 2.6.27
hbarnwheeler, maybe it would be easier to post what you're concerned about with the upgrade. Maybe instead of trying to prevent it, it would be best to just be ready for it?
Offline
#4 2009-02-08 20:46:29
- hbarnwheeler
- Member
- Registered: 2006-08-11
- Posts: 37
Re: Upgrade to 2.6.28 via pacman, keeping 2.6.27
hbarnwheeler, maybe it would be easier to post what you're concerned about with the upgrade. Maybe instead of trying to prevent it, it would be best to just be ready for it?
I'm not terribly worried about it. I'm confident that I can debug any issues that arise, I just don't really have time to fiddle with a borked system. I just thought maybe there was a quick and dirty way to keep a working kernel image around to fall back on should problems arise. I'll just wait until I have some time on my hands to upgrade.
Offline