This is relatively straightforward if you follow the steps
carefully. It is recommended you have a good backup and a suitable
rescue disk handy just in case.
contains the old kernel and an initial RAM disk as well as the LILO
boot files and the following entry in
Build LVM kernel and modules
Follow the steps outlined in
Chapter 5 - Section 6.2
for instructions on how to get and build the necessary
kernel components of LVM.
Build the LVM user tools
Follow the steps in
Section 6.2 to build and install the user
tools for LVM.
Install the new tools. Once you have done this you cannot
do any LVM manipulation as they are not compatible with
the kernel you are currently running.
Rename the existing initrd.gz
This is so it doesn't get overwritten by the new one
# mv /boot/initrd.gz /boot/initrd08.gz
Make the existing boot entry point to the renamed file.
You will need to reboot using this if something goes wrong
in the next reboot. The changed entry will look something
Run lvmcreate_initrd to create a new initial RAM disk
Don't forget the put the new kernel version in there so
that it picks up the correct modules.
Add a new entry into /etc/lilo.conf
This new entry is to boot the new kernel with its new
This will install the new boot block
When you get the LILO prompt select the new entry name (in
this example lvm10) and your system should boot into Linux
using the new LVM version.
If the new kernel does not boot, then simply boot the old
one and try to fix the problem. It may be that the new
kernel does not have all the correct device drivers built
into it, or that they are not available in the initrd.
Remember that all device drivers (apart from LVM) needed
to access the root device should be compiled into the
kernel and not as modules.
If you need to do any LVM manipulation when booted back
into the old version, then simply recompile the old tools
and install them with
If you do this, don't forget to install the new tools when
you reboot into the new LVM version.
When you are happy with the new system remember to change the
``default='' entry in your lilo.conf file so that it is the default