On 17-Sep-99 Richard Adams wrote:
> It will copy vmlinuz to /vmlinuz period, unless
> /usr/src/linux/Makefile is edited around line 69 and the hash
> removed, then /boot will be the default install path.
What it actually does is copy (b)zImage (say version 2.2.12) to
/boot/vmlinuz-2.2.12
then
cp /boot/vmlinuz /boot/vmlinuz.old
rm /boot/vmlinuz
ln -s /boot/vmlinuz-2.2.12 /boot/vmlinuz
It does not remove any /boot/vmlinuz-* files, therefore you can alter your
lilo.conf to look something like this:-
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz
label=linux
root=/dev/sda2
read-only
image=/boot/vmlinuz.old
label=linux.old
root=/dev/sda2
read-only
image=/boot/vmlinuz-2.2.5
label=linux-2.2.5
root=/dev/sda2
read-only
image=/boot/vmlinuz-2.0.38
label=linux-2.0.38
root=/dev/sda2
read-only
image=/boot/vmlinuz-2.0.36-0.7
label=linux.rh52
root=/dev/sda2
initrd=/boot/initrd-2.0.36-0.7.img
read-only
You don't lose anything of what has gone before unless you get rid of it, it
sets your System.map up correctly (which most people forget to do). Here is
an ls -l of my /boot directory:-
lrwxrwxrwx 1 root root 17 Sep 6 01:06 System.map ->
System.map-2.2.12
-rw-r--r-- 1 root root 105911 Oct 14 1998 System.map-2.0.36-0.7
-rw-r--r-- 1 root root 85079 Aug 3 13:11 System.map-2.0.37
-rw-r--r-- 1 root root 85097 Aug 27 11:22 System.map-2.0.38
-rw-rw-r-- 1 root root 183825 Sep 6 01:06 System.map-2.2.12
-rw-rw-r-- 1 root root 183790 Sep 6 00:50 System.map.old
-rw-r--r-- 1 root root 512 Aug 3 18:08 boot.0800
-rw-r--r-- 1 root root 4536 May 7 1998 boot.b
-rw-r--r-- 1 root root 300 May 7 1998 chain.b
-rw-r--r-- 1 root root 210884 Aug 3 18:08 initrd-2.0.36-0.7.img
-rw------- 1 root root 28672 Sep 6 01:06 map
lrwxrwxrwx 1 root root 28 Aug 3 13:07 module-info ->
/boot/module-info-2.0.36-0.7
-rw-r--r-- 1 root root 11773 Oct 14 1998 module-info-2.0.36-0.7
-rw-r--r-- 1 root root 308 May 7 1998 os2_d.b
lrwxrwxrwx 1 root root 14 Sep 6 01:06 vmlinuz ->
vmlinuz-2.2.12
-rw-r--r-- 1 root root 454325 Oct 14 1998 vmlinuz-2.0.36-0.7
-rw-r--r-- 1 root root 410565 Aug 3 13:11 vmlinuz-2.0.37
-rw-rw-r-- 1 root root 429925 Aug 27 11:22 vmlinuz-2.0.38
-rw-rw-r-- 1 root root 567931 Sep 6 01:06 vmlinuz-2.2.12
-rw-rw-r-- 1 root root 563216 Sep 6 00:50 vmlinuz.old
What could be more flexible than that? Why would you (unless you are a kernel
developer) want to do anything else?
>
> After reading ./arch/i386/boot/Makefile i would certanly not use make
> install on my system, i define a EXTRAVERSION in the Top dir Makefile
> and it seems that make install and install.sh in the same directory
> dont use the extraversion number, simply .old, now that would render
> my system useable with 2 kernels only as modules would be the
> biggest problem. Or am i missing something which is before my eys
> here so close i cant see it.??.
Dirk G1TLH (perplexed of Dereham)
---
Dirk-Jan Koopman, Tobit Computer Co Ltd
At the source of every error which is blamed on the computer you will find
at least two human errors, including the error of blaming it on the computer.
