from the quill of Francis GALIEGUE <[EMAIL PROTECTED]> on scroll
<[EMAIL PROTECTED]>
>
> Yes you can. All files are different from one kernel package to
> another. This is why it works in this special case.
Hmmmmm. Interesting. I thought it actually refused to install two
packages of the same name even if they are different versions.
Interesting indeed.
> Yes but you also lose the possibility to bot on your old kernel.
Not if the upgrade does the
mv <links> <links.old>
before installing the new kernel. Another benefit of this scheme is
that "linux.old" is always named linux.old and the user doesn't have to
"guess" or "remember" what was the old kernel.
> * on boot, rc.sysinit makes the System.map symlink point to the one
> corresponsing to the running kernel - a .old symlink wouldn't be of
> any help.
System.map.old would be a symlink too, but you wouldn't really need it
anyway, because rc.sysinit does point System.map to
System.map-$(uname -r). You would only have too keep the previous
System.map around.
> * it won't solve the problems of multiple booting kernels anyway. One
> (for now) must still do it by hand.
I just wonder how many "end user" types are going to understand all of
the manual work required after upgrading his kernel package. One could
argue that end users should not be upgrading kernel packages, but we all
know they are going to want to, and they are going to do it. Why not
make it more hands off?
If I were to modify the src rpm to do the above features, would you at
least consider looking at the changes? I don't mind doing the work, I
just want to know that somebody will at least consider my changes at the
end.
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
