From: Florian Huber <florian.huber@mnet-online.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-test1-mm2] unable to mount root fs on unknown-block(0,0)
Date: Mon, 21 Jul 2003 17:38:26 +0200 [thread overview]
Message-ID: <20030721173826.333bfa01.florian.huber@mnet-online.de> (raw)
In-Reply-To: <1058738091.5980.63.camel@localhost.localdomain>
On 20 Jul 2003 14:54:52 -0700
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Setting root=0303 (in your case) might helps things along.
Thanks Jeremy, it's working :)
next prev parent reply other threads:[~2003-07-21 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 10:55 [2.6.0-test1-mm2] unable to mount root fs on unknown-block(0,0) Florian Huber
2003-07-20 11:55 ` Felipe Alfaro Solana
2003-07-20 18:47 ` Joe
2003-07-20 21:54 ` Jeremy Fitzhardinge
2003-07-20 23:17 ` Jeremy Fitzhardinge
2003-07-21 15:38 ` Florian Huber [this message]
2003-07-21 18:05 ` Christian Axelsson
2003-07-23 18:42 ` [PATCH 2.6.0-test1-mm2] fix unable to mount root fs Daniel McNeil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030721173826.333bfa01.florian.huber@mnet-online.de \
--to=florian.huber@mnet-online.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).