FS#2376 - kernel upgrades deleted stuff he shouldn't

Attached to Project: Arch Linux
Opened by Hylke Witjens (moto-moi) - Tuesday, 15 March 2005, 15:00 GMT
Last edited by arjan timmerman (blaasvis) - Tuesday, 15 March 2005, 15:15 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

For some reason pacman or the kernel package desides I don't need my old kernel-modules (from the kernel before the one I'm installing with pacman), so het deletes them.

This isn't very handy, because I can now no return to my old kernel in case this new kernel fails.
This task depends upon

Closed by  Judd Vinet (judd)
Wednesday, 16 March 2005, 01:40 GMT
Reason for closing:  Not a bug
Comment by Judd Vinet (judd) - Tuesday, 15 March 2005, 19:07 GMT
Which kernel modules are you speaking of? If the modules belong to the old kernel26 package (like eepro100.o, for example) then they will be removed, but should be replaced by the new kernel26 package going in.
Comment by Hylke Witjens (moto-moi) - Tuesday, 15 March 2005, 23:19 GMT
Well, just today I got a new kernel, 2.6.11.3-ARCH , but now /lib/modules/2.6.11.1-ARCH, my previous kernel modules directory, is totally emtyed out. Which can't be the intended behaviour if you'd ask me, because now I cannot return to the previous kernel, because all those modules are gone.

What I would like is that whenever a new kernel is installed, it just gets added, not replacing the previous kernel.

For example, at work I have a machine which doesn't do well with a 2.6 kernel, if I'd be running arch at that machine I would ahve to go to the machine, with a bootcd to fix it, instead of just clicking on the old kernel-image in my lilo-bootscreen ;)
Comment by Judd Vinet (judd) - Tuesday, 15 March 2005, 23:26 GMT
I suggest you build your own custom kernel then. You don't need to build it as a package, just install it as /boot/vmlinuz-failsafe or something, leaving the modules in /lib/modules/2.6.11.3-failsafe (for example).

Pacman treats a kernel package like any other. An upgrade is a remove, then an install. If you upgrade gaim, you obviously cannot use the old version of gaim unless you reinstall it. The kernel package is the same.

Loading...