From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pony.its.uwo.ca([129.100.2.63]) (1691 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Tue, 9 Jan 2001 08:26:24 -0500 (EST) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from ignatious (c716099-a.rchdsn1.tx.home.com [24.7.105.70]) by pony.its.uwo.ca (8.10.0/8.10.0) with ESMTP id f09DQJf21273 for ; Tue, 9 Jan 2001 08:26:22 -0500 (EST) Received: from cpt.kirk (helo=localhost) by ignatious with local-esmtp (Exim 3.12 #1 (Debian)) id 14Fz0l-0006Tx-00 for ; Tue, 09 Jan 2001 07:40:27 -0600 Date: Tue, 9 Jan 2001 07:40:27 -0600 (CST) From: Kirk Wood X-Sender: cpt.kirk@ignatious To: speakup@braille.uwo.ca Subject: Re: Lilo geo_comp_addr Error with 2.4.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: 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