From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from executioner.lis.net.au([203.35.83.3]) (2984 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Thu, 11 Jan 2001 13:12:33 -0500 (EST) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from uucp by executioner.lis.net.au with local-rmail (Exim 2.05 #1) id 14GmD2-00043F-00 (Debian); Fri, 12 Jan 2001 05:12:24 +1100 Received: from kerry by joana.gotss.eu.org with local (Exim 3.12 #1 (Debian)) id 14Glsd-0002XQ-00 for ; Fri, 12 Jan 2001 01:51:19 +0800 Date: Fri, 12 Jan 2001 01:51:18 +0800 To: speakup@braille.uwo.ca Subject: Re: Lilo geo_comp_addr Error with 2.4.0 Message-ID: <20010112015118.A9744@joana.gotss.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from cpt.kirk@1tree.net on Tue, Jan 09, 2001 at 07:40:27AM -0600 From: Kerry Hoath List-Id: There is a reason for the simlink aproach. make zlilo or make bzlilo will copy a kernel to /vmlinuz and automatically run lilo. This means if the default kernel is vmlinuz in the root, thinks will just go. Many people however only create a 10-20 megabyte partition for /boot keeping the intire contents below cylinder 1024. The simlink keeps /vmlinuz below this magic cylinder. Now that most bioses and lilo support lba32 adressing, this problem should go away in the long term. The simlink aproach also means you have 1 simlink cluttering up the root directory and can put the rest of the kernels in /boot/* and referr to them as /boot/blah Most comercial unixes stored the kernel image (not images) in the root of the tree hence the historic convention. REgards, Kerry On Tue, Jan 09, 2001 at 07:40:27AM -0600, Kirk Wood wrote: > Janina, > > One thing that comes to mind here for me. I know that slackware puts the > kernel image in the root directory with a softlink in the /boot > directory. This can cause confusion as far as I can see. What I have found > is that you can put the image in the /root directory (which I go ahead and > put on the first available partition) and skip the softlink altogether. I > name the kernel something that will help me remember when I compiled it > and any special features. I can find nothing sacred about vmlinuz other > then that it is the common name scheme. But I have seen the same (or a > similar) problem where someone continued following the slackware original > setup. > > ======= > Kirk Wood > Cpt.Kirk@1tree.net > > Cluelessness > There are no stupid questions, but there are a lot of > inquisitive idiots > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- -- Kerry Hoath: kerry@gotss.eu.org Alternates: kerry@emusys.com.au kerry@gotss.spice.net.au or khoath@lis.net.au ICQ UIN: 62823451