Re: upgrading to 2.0.35 or 2.0.36 under Hamm
All you really need to do is get all the required packages (gcc, bin86,
etc), download the kernel source, and build as normal. Nothing special.
I've had no trouble with 2.0.x on Hamm, although 2.1/2.2 require a bit of
work.
At 05:12 AM 2/9/99 -0800, Kenneth Scharf wrote:
>---------------------------------------------------
>>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.
>---------------------------------------------------
>I am currently running 2.0.36 on a hamm machine. I got the slink
>kernel-package and kernel-source packages and installed them, then
>configured the kernel and built a new one using make-kpkg. (You might
>not need the slink kernel-package to build 2.0.36 I was just being
>prudent). If you want to keep the old kernel, make a symlink under
>/boot such as vmlinuz_old and a section in lilo.config with a label
>such as old_linux before you install the new kernel. See the man
>pages and /usr/doc pages for the kernel-package stuff. Kernel-package
>makes it real easy to build and install the new kernel, it also will
>set up lilo for you.
>==
>Amateur Radio, when all else fails!
>
>http://www.qsl.net/wa2mze
>
>Debian Gnu Linux, Live Free or .....
>
>
>_________________________________________________________
>DO YOU YAHOO!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
>
>--
>Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org <
/dev/null
>
>
>
Reply to: