home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!munnari.oz.au!bruce.cs.monash.edu.au!monu6!dibbler.cs.monash.edu.au!tym
- From: tym@dibbler.cs.monash.edu.au (Tim MacKenzie)
- Subject: Re: after compiling kernel...then what?
- Message-ID: <1992Dec31.073059.11315@monu6.cc.monash.edu.au>
- Sender: news@monu6.cc.monash.edu.au (Usenet system)
- Organization: Computer Science, Monash University, Australia
- X-Newsreader: TIN [version 1.1 PL8]
- References: <marcf.725782497@yorku.ca>
- Date: Thu, 31 Dec 1992 07:30:59 GMT
- Lines: 26
-
- Marc G Fournier (marcf@nexus.yorku.ca) wrote:
- > I just successfully recompiled the kernel in Linux :)
-
- > Now what do I do with it? It just leaves it in /usr/src/linux.
- >I copied it over /Image...is that right?
-
- Not something I would do... I generally copy it into
- /Image.<something descriptive> (eg Image-991-tcp Image-990-test)
- then remove the (hard) link that is /Image and make a new /Image link:
- 'ln Image.<name> Image'
- Then I add a lilo config entry for the new kernel (and remove any that
- are for kernels that I've deleted to make room :) and finally run
- the lilo install script. (the default linux kernel loaded is always /Image).
-
- This way I can always tell which kernel I am running (it is the one
- that has 2 links: /Image and /Image.<descriptive name>) and can get
- back to any of my backup kernels if something goes wrong.
- [If you're not running LILO (version 0.7 I think) then DO! I've never had
- any problems with it and it's saved a lot of potential hassles caused by
- dud kernels (my own fault usually:)]
-
- Of course, you should aways have a couple of disks that you can boot off
- in case your hard drive goes ga-ga. (H Lu's boot/root disk or a1 and a2
- from the SLS distribution).
- --
- -Tim MacKenzie (tym@dibbler.cs.monash.edu.au)
-