Mailinglist Archive: opensuse (3261 mails)

[Philipp Thomas <pthomas@xxxxxxx>]

* jerrykreps (jerrykreps@xxxxxxxxxxx) [20010401 16:13]:

> > Why don't you people just use 'make bzlilo'? That'll do all that's
> > needed including calling LILO.
> 
> Wouldn't one have to make sure that /etc/lilo.conf was set up 
> accordingly BEFORE running bzlilo?  

If you use the standard setup, i.e. vmlinuz and System.map, you don't need
to change lilo.conf, but then your old kernel, saved to vmlinuz.old, will be
gone the second time you build a new kernel.

If you use my scheme, i.e. modify arch/i386/boot/Makefile to create kernel
and System.map with the kernel version tagged on, then you need to make sure
you have a matching entry for the new kernel in /etc/lilo.conf. But even if
you don't, kernel and System map are copied to INSTALL_PATH and only the
call to LILO will fail. So you just create the entry then and call LILO
manually.

IMO it is a small bit of work that greatly saves you some hassle, especially
if you play around^H^H^H experiment with a larger number of kernels.

Philipp

-- 
Penguins shall save the dinosaurs
                          -- Handelsblatt about Linux on S/390