According to Michael Trausch: While burning my CPU.
>
> What I did was d/l kernel 2.2.1, from a mirror of (I think)
> ftp.kernel.org... they have a list of mirrors at www.kernel.org, and
> there's a Kernel HOWTO installed on your system (well, if you installed
> extra documentation) in /usr/doc/HOWTO/Kernel-HOWTO.
>
> That'll tell you pretty much everything that you need... it's about a
> 13mb download, takes 1:15:00 on a 56K v.90 modem.
Well he could indeed use 2.2.1 but what he wants is in kernel 2.0.36 as
well and he has that already, or so i understood.
The following comments of mine are not meant as critisium but meant as help.
Normaly people ftp from and to thier /pub/ftp/* directorys, now theres no
need to "mv" the file as you can leave the tar archive where it is and do;
cd /usr/src
rm linux
mkdir linux-2.2.1
ln -s linux-2.2.1 linux
tar xzf /home/ftp/pub/linux-2.2.1.tar.gz
>
> # mv ./linux-2.2.1.tar.gz /usr/src/linux-2.2.1.tar.gz
>
> Then you'll do this:
>
> # rm linux
> // 'linux' in RH 5.2 is a symbolic link to
> // 'linux-2.0.36'... rm the link.
> # tar -xzpvf linux-2.2.1.tar.gz
>
> Then, when that's done...
>
> # mv linux linux-2.2.1
"mv linux", That will not work as the link to "linux" was just deleted.
> # ln -s linux-2.2.1 linux
> # cd linux
> # make menuconfig
>
> At this point, you're going to configure every option that you'll want for
> your system... APM is in here, with sound, SCSI, IDE, etc.
>
> You can select things that are compiled in as compared to modularized,
> etc.
>
> Modularize AMAP if you can, it will result in a smaller Kernel (larger
> kernel == bzImage == some problems, sometimes).... THen you'll do
> something like this:
>
> # make dep
> # make zImage
> // if make zImage fails, then:
> # make bzImage
> # make modules
> # make modules_install
Simply typing;
make dep clean zImage && make modules modules_install
all on one line should do, that allows you to do other things while make is
in progress, you dont have to keep checking to see how afr the compile is
and having to wait to type the next "make line" in.
> # cp /usr/src/linux/arch/i386/boot/zImage /boot
> // may be bzImage
> # cd /etc ; vi lilo.conf
>
> Change the lilo.conf file to add the new kernel (like this:)
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> image=/boot/bzImage # this is the new kernel
> label=linux22 # this is the thing you type @ lilo: prompt
> root=/dev/hda3 # this is the partition that it's on
> read-only # you have to have this!
> image=/boot/vmlinuz-2.0.36-0.7 # this is the old kernel
> label=linux # see above
> root=/dev/hda3 # see above
> read-only # see above
> other=/dev/hda1 # this is my w95 partition
> label=dos # see above
> table=/dev/hda # i dunno what that is
Taken from man lilo.conf;
table=device
This specifies the device that contains the parti-
tion table. The boot loader will not pass parti-
tion information to the booted operating system if
this variable is omitted. (Some operating systems
have other means to determine from which partition
they have been booted. E.g., MS-DOS usually stores
the geometry of the boot disk or partition in its
boot sector.) Note that /sbin/lilo must be re-run
if a partition table mapped referenced with `table'
is modified.
>
> That (hopefully) should get you running.
>
> - Mike
>
--
Regards Richard.
[EMAIL PROTECTED]
