from the quill of Francis GALIEGUE <[EMAIL PROTECTED]> on scroll
<[EMAIL PROTECTED]>
>
> The problem is also that it's not explicited clearly somewhere: you
> must install a new kernel with rpm -i and not rpm -U :(
Can one actually do that? Without a --force I mean. I have never been
able to rpm -i a package of the same name, different version/release on
top of an older one.
> If you upgrade with -U then yes, old modules will disappear...
Hmmmmm. Not so good. Too bad rpm does not have an option to "leave old
package in place" because ideally the old kernel remains and gets
renamed ".old" JIC (just in case).
I came across a couple of other things while upgrading. What is /boot
supposed to look like? I like mine to look like this when all is done:
initrd-2.2.13-29mdkfb
vmlinuz.old -> vmlinuz-2.2.13-29mdkfb
initrd.old -> initrd-2.2.13-29mdkfb
module-info.old -> /boot/module-info-2.2.13-29mdkfb
System.map.old -> /boot/System.map-2.2.13-29mdkfb
vmlinuz-2.2.14-1mdkfb
module-info-2.2.14-1mdkfb
System.map-2.2.14-1mdkfb
kernel.h
vmlinuz -> vmlinuz-2.2.14-1mdkfb
initrd -> initrd-2.2.14-1mdkfb
vmlinuz-2.2.13-29mdkfb
initrd-2.2.14-1mdkfb
map
module-info -> /boot/module-info-2.2.14-1mdkfb
System.map -> /boot/System.map-2.2.14-1mdkfb
assuming that I upgraded from 2.2.13-29mdkfb to 2.2.14-1mdkfb. That way
I don't have to screw around with lilo.conf before I run lilo.
Also I really do think that the kernel install should run the mkinitrd.
That way the modules will still be there when it is run. Any reason why
to not do it? Also any reason to not make /boot follow the stucture
above?
b.
--
Brian J. Murrell InterLinx Support Services, Inc.
North Vancouver, B.C. 604 983 UNIX
Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD
