Very Computer

Hi there !

I have recently compiled my kernel with a few patches (like to mount a HPFS
system, sound patches and the Quota patch). It compiled very well (make
config; make dep; make zlilo), but what do I have to do to replace the old
kernel with the new one ?

Thanks in advance

Theo

Quote:>Hi there !

>I have recently compiled my kernel with a few patches (like to mount a HPFS
>system, sound patches and the Quota patch). It compiled very well (make
>config; make dep; make zlilo), but what do I have to do to replace the old
>kernel with the new one ?

zlilo? I just run make and a new zImage is created.
This is what I did:

make - produces /usr/src/linux/zImage
cp /zImage /zImage.old
cp zImage /zImage
rdev /zImage (verify it has the correct root partition, if not
  change it - see 'man rdev' for specifics)
/etc/lilo/install
sync
shutdown -r now

Note that if you just copy over the kernel without running lilo
and rdev, it will probably just reboot endlessly.
I did this.  Solution?  Boot from the a1 diskette, and get into a
root shell.  Mount the root filesystem of your disk on /mnt,
and run rdev and lilo, then reboot.

This probably should be a bit more documented in the install docs
for the kernel upgrades.  It's there, but a bit cryptic...

| Dan |

--

Associate Programmer                     (914) 789-5378
Advanced Network & Services               Elmsford, NY

:
: >I have recently compiled my kernel with a few patches (like to mount a HPFS
: >system, sound patches and the Quota patch). It compiled very well (make
: >config; make dep; make zlilo), but what do I have to do to replace the old
: >kernel with the new one ?
:
: zlilo? I just run make and a new zImage is created.
: This is what I did:
:
: make - produces /usr/src/linux/zImage
: cp /zImage /zImage.old
: cp zImage /zImage
: rdev /zImage (verify it has the correct root partition, if not
:   change it - see 'man rdev' for specifics)
: /etc/lilo/install
: sync
: shutdown -r now

A minor suggestion:  use mv instead of cp:

$ cd /usr/src/linux
$ make
$ mv /vmlinux /vmlinux.old        # only if /vmlinux is a good kernel!
$ mv zImage /vmlinux
$ /etc/lilo/install
$ fastboot

(my system is set up to boot from the file named vmlinux)

I highly recommend that you add an entry in the lilo config file to
allow you to boot zImage.old, or vmlinux.old, or whatever you named
the kernel that you know used to work.

That way, when the shiney new kernel doesn't work (and some day you
_will_ build a kernel that doesn't work), you can just type
vmlinux.old and the LILO prompt and you're back up and running --
recompiling the kernel for another try!

--
Grant Edwards                                 |Yow!  Today, THREE WINOS from
Rosemount Inc.                                |DETROIT sold me a framed
                                              |photo of TAB HUNTER before

   Delete above 2 steps. I would subject don't touch the old working
kernel at this point yet(If you do so, you may have problem to bring
your system back for the no-go new kernel), instead

$ mv /usr/src/linux/vmlinux /vmlinux.test
   then add an entry for this new kernel (/vmlinux.test) to /etc/lilo/config
  (or /etc/lilo.conf if you run future Debian Linux). This way, you can
  boot your machine with a choice either old kernel or new one. LILO will
  handle this.

Quote:>$ /etc/lilo/install
>$ fastboot

>(my system is set up to boot from the file named vmlinux)

>I highly recommend that you add an entry in the lilo config file to
>allow you to boot zImage.old, or vmlinux.old, or whatever you named
>the kernel that you know used to work.

  Very important!!!

Quote:>That way, when the shiney new kernel doesn't work (and some day you
>_will_ build a kernel that doesn't work), you can just type
>vmlinux.old and the LILO prompt and you're back up and running --
>recompiling the kernel for another try!

   Above warning is valid!

--
[Tzeng Ruey Yuan] --yuan