Very Computer

by **Meryl Tsen** » Sat, 31 Jan 1998 04:00:00

OK I downloaded 2.0.33 and unpacked it into its own directory. True or
false: all I have to do is compile it like what I've been doing for my
original kernel and that should be it ie make config/dep/clean/install?

by **Rod Bric** » Sat, 31 Jan 1998 04:00:00

> OK I downloaded 2.0.33 and unpacked it into its own directory. True or
> false: all I have to do is compile it like what I've been doing for my
> original kernel and that should be it ie make config/dep/clean/install?

False. But barely. I think there are three sym links you need to make,
see the README file that came with the new kernel. Then I think it's
essentially the same.

Rod

by **<al..** » Mon, 02 Feb 1998 04:00:00

> OK I downloaded 2.0.33 and unpacked it into its own directory.

WOW! really?

Quote:> True or
> false: all I have to do is compile it like what I've been doing for my
> original kernel and that should be it ie make config/dep/clean/install?

make config -> make menuconfig (easier!)
make dep ; make clean ; make modules ; make modules_install ; make zImage

check your /etc/lilo.conf for the image=/boot/vmlinuz (or something)
and mv the new zImage from /usr/src/linux/arch/i386/boot to /boot/vmlinuz.

run /sbin/lilo and reboot.

by **Sid Boyc** » Mon, 02 Feb 1998 04:00:00

> > OK I downloaded 2.0.33 and unpacked it into its own directory. True or
> > false: all I have to do is compile it like what I've been doing for my
> > original kernel and that should be it ie make config/dep/clean/install?

> False. But barely. I think there are three sym links you need to make,
> see the README file that came with the new kernel. Then I think it's
> essentially the same.

> Rod

The best approach is ........
cd /usr/src; tar czfv linux-2.0.x.tar.gz linux; rm -rf linux; tar zxfv
linux-2.0.33.tar.gz;cd linux then do your make config, make dep, make
zImage etc.
If you have problems compiling or for some reason you need to abandon
2.0.33, then rm -rf linux and tar zxfv linux-2.0.x.tar.gz and you are
back where you were. That's what I do here if any of the 2.1 kernels
don't compile or I have problems with it and I need to compile stuff
requiring a kernel version and I don't want to use the buggy kernel.
Regards
--
... Sid Boyce...Amdahl(UK)...44-121 422 0375
-----------------------------------
Any opinions expressed above are mine and do not necessarily represent
the opinions or policies of Amdahl Corporation.

by **jeff cove** » Thu, 05 Feb 1998 04:00:00

-----BEGIN PGP SIGNED MESSAGE-----

alexk> make dep ; make clean ; make modules ; make modules_install
alexk> ; make zImage

better yet,

make dep && make clean && make modules && make modules_install && make zImage

so you don't waste a lot of time if something goes wrong along the way.

alexk> check your /etc/lilo.conf for the image=/boot/vmlinuz (or
alexk> something) and mv the new zImage from
alexk> /usr/src/linux/arch/i386/boot to /boot/vmlinuz.

this is after copying your old kernel somewhere and adding it to
lilo.conf, no? :)

- --

| / | ' \ http://pobox.com/~jeff.covey |
|( ) 0 baltimore, maryland 410-669-4926 |
| \_/-, ,----' |
| ==== // classical guitar, midi sequencing, |
| / \-'~; /~~~(O) music notation, linux! and more! |
| / __/~| / | for a list of files available from me, |
|=( _____| (_________| send me mail with "send index" as subject |

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBNNhuLjnaR8Cs0X0pAQFV7gP+OzZw0bXwb7pCjf2yHzQqjaZxgLvRGdt1
ac0ZOKRgaOM6DKnErwWdM8YKQOD6/iEGomOZMO/hz720+9M8szpQhWGr5133k2Qy
ELIWolRZCs030Mwh/lYAnUw5I6Q8DDchGM4fpsxobcIbS2oJzJizohOOAFhIMRCl
L3WrRKtlpdM=
=E3Ys
-----END PGP SIGNATURE-----

Very Computer

Next step: compiling upgrade kernel

Next step: compiling upgrade kernel

Next step: compiling upgrade kernel

Next step: compiling upgrade kernel

Next step: compiling upgrade kernel

Next step: compiling upgrade kernel