In article <2450.1006608941@ocs3.intra.ocs.com.au> you wrote:
> kbuild 2.5 has standard support for running user specific install
> scripts after installing the bootable kernel and modules. That is, the
> "update my bootloader" phase can be automated and will propagate from
> one .config to the next when you make oldconfig.
Never 2.4 kernels already try to excecute ~/bin/installkernel in the
'make install' pass on i386.
My personal tip for people keeping lots of kernels around is grub, though.
No need for a menu entry, one can just boot all kernel on the accessible
filesystems.
Together with the above "~/bin/installkernel" option I put my kernels always
into /lib/modules/<version>/vmlinux so I can find them easily (IMHO this
should be default in 2.5), so even lilo-using people could write simple
scripts to add all kernels present in /lib/modules/ to their config.
This does of course make the path '/lib/modules/' grossly misnamed, maybe
we could change it into /kernel in 2.5 :)
Christoph
-- Of course it doesn't work. We've performed a software upgrade. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 30 2001 - 21:00:16 EST