From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pony.its.uwo.ca([129.100.2.63]) (1668 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Tue, 2 Jan 2001 08:37:10 -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 f02DbC326545 for ; Tue, 2 Jan 2001 08:37:12 -0500 (EST) Received: from cpt.kirk (helo=localhost) by ignatious with local-esmtp (Exim 3.12 #1 (Debian)) id 14DRph-00033a-00 for ; Tue, 02 Jan 2001 07:50:33 -0600 Date: Tue, 2 Jan 2001 07:50:33 -0600 (CST) From: Kirk Wood X-Sender: cpt.kirk@ignatious To: speakup@braille.uwo.ca Subject: Re: Help with Kernel install. In-Reply-To: <001301c07452$0a7d54a0$c2128fd1@enterprise> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: You can setup to boot with a new kernell without endangering your current situation. If you copy the new bzImage to the /boot dir and add a new entry to lilo.conf. Just copy the curent entry with a new label and new image name. you will then have an option of shoosing the image to use when you first boot. It sounds to me like the kernel panic is not a problem with the kernell itself, but rather that it is failing to find a usable root location for the file system. Chances are that unless you have one large partition on your drive the correct root partition is /dev/hda4 or /dev/hda5. You can pick it out by running the mount command or df. ======= Kirk Wood Cpt.Kirk@1tree.net Cluelessness There are no stupid questions, but there are a lot of inquisitive idiots