Messages in this thread | ![/](/images/icornerl.gif) | | From | Keith Owens <> | Subject | Re: is 2.4.15 really available at www.kernel.org? | Date | Sun, 25 Nov 2001 10:57:59 +1100 |
| |
On Sat, 24 Nov 2001 14:56:18 +0100, Christoph Hellwig <hch@ns.caldera.de> wrote: >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.
I know. kbuild 2.5 goes further and gives the user a choice about (a) whether to run a script on install and (b) what the script name is, instead of hard coding it.
>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)
Architecture dependent. In kbuild 2.5 for most architectures the default location for the kernel, System.map and .config is in /lib/modules.
string 'Where to install the kernel' CONFIG_INSTALL_KERNEL_NAME "/lib/modules/KERNELRELEASE/vmlinuz" bool 'Install System.map' CONFIG_INSTALL_SYSTEM_MAP if [ "$CONFIG_INSTALL_SYSTEM_MAP" = "y" ]; then string ' Where to install System.map' CONFIG_INSTALL_SYSTEM_MAP_NAME "/lib/modules/KERNELRELEASE/System.map" fi bool 'Install .config' CONFIG_INSTALL_CONFIG if [ "$CONFIG_INSTALL_CONFIG" = "y" ]; then string ' Where to install .config' CONFIG_INSTALL_CONFIG_NAME "/lib/modules/KERNELRELEASE/.config" fi
Users with special requirements (old BIOS, small /lib etc.) can configure their install to put the kernel where they like. At least one architecture (ia64) mandates that bootable images live in a separate partition, the firmware on ia64 requires this, so the default for vmlinuz is different.
string 'Where to install the kernel' CONFIG_INSTALL_KERNEL_NAME "/boot/efi/vmlinuz-KERNELRELEASE"
>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 :)
I was tempted, but the number of things that would break ... shudder.
- 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/
| ![\](/images/icornerr.gif) |