Subject: Re: wanted: more informative message if root device can't be
	found/mounted
From: Arjan van de Ven <arjan@infradead.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: jurriaan <thunder7@xs4all.nl>, linux-kernel@vger.kernel.org
In-Reply-To: <20061111114436.GA10020@aepfle.de>
References: <20061111085200.GA4167@amd64.of.nowhere>
	 <20061111114436.GA10020@aepfle.de>
Content-Type: text/plain
Organization: Intel International BV
Date: Sat, 11 Nov 2006 12:57:37 +0100
Message-Id: <1163246257.3293.11.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 963
Lines: 24

On Sat, 2006-11-11 at 12:44 +0100, Olaf Hering wrote:
> On Sat, Nov 11, jurriaan wrote:
> 
> > kernel panic - unable to mount root device 09:02
> 
> These numbers are the root cause.
> Use mount by filesystem UUID. On-disk content does unlikely change.
> And if it does, you have to reconfigure the bootloader anyway.
> 
> All this luxury doesnt belong into the kernel.

one thing that we should consider is to not panic(). Panic() tends to
cause the backscroll capability to go away.. which is rather useful to
see what went wrong for this scenario...

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/