Re: upgrading to 2.0.35 or 2.0.36 under Hamm
On Tue, 9 Feb 1999, Chris Evans wrote:
> I am running Hamm very happily on a machine sitting in an ISP.
> However, it can't access the SCSI controller and I need to fix that
> (very nervously). I am advised that the ncr based controller is likely
> to be happier with the 2.0.35 or 2.0.36 kernel, though it may still
> need a driver/module upgrade then.
>
> One step at a time: anyone else moved to 2.0.35/36 while
> retaining the rest of Hamm? I don't really want to make the move
> to slink until a while after it moves to be "stable" but I do need to
> make this move.
>
> Any advice on doing it so I can easily get back if things break:
> something about registering two bootable kernels using lilo?
There is little risk in upgrading to a newer stable kernel. It is
essentially independent of the Debian version (although you may run into
some problems with 2.2.1 with hamm). If you have the standard Debian setup
for /etc/lilo.conf and use make-kpkg to compile your kernel and create a
.deb, installing it will link the new kernel to /vmlinuz with the label
"Linux" and link your old kernel to /vmlinuz.old with the label "OldLinux"
and you can choose either when booting. To be safe, I always opt to make
a boot floppy for each kernel as well.
Bob
----
Bob Nielsen Internet: nielsen@primenet.com
Tucson, AZ AMPRnet: w6swe@w6swe.ampr.org
DM42nh http://www.primenet.com/~nielsen
Reply to: