From: Florian Huber <florian.huber@mnet-online.de>
To: linux-kernel@vger.kernel.org
Cc: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: Re: root= needs hex in 2.6.0-test1-mm2
Date: Wed, 23 Jul 2003 17:06:57 +0200 [thread overview]
Message-ID: <20030723170657.2ba9e7db.florian.huber@mnet-online.de> (raw)
In-Reply-To: <1058962821.574.0.camel@teapot.felipe-alfaro.com>
On 23 Jul 2003 14:20:21 +0200
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org> wrote:
> I would say it's a bug :-)
"It's not a bug, it's an undocumented feature" ;)
On the one hand it sounds reasonable tom me that I cannot use the
device "path", because devfs sets it, but why has it changed? It
seemed to work well with older kernel versions. And what do the hex
numbers stand for?
TIA
Florian Huber
next prev parent reply other threads:[~2003-07-23 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 6:56 Tom Felker
2003-07-23 12:20 ` Felipe Alfaro Solana
2003-07-23 15:06 ` Florian Huber [this message]
2003-07-23 15:48 ` Charles Lepple
2003-07-23 13:43 ` Christoph Hellwig
2003-07-23 15:08 ` Felipe Alfaro Solana
2003-07-23 18:17 ` Diego Calleja García
2003-07-23 19:30 ` Steven Cole
2003-07-23 15:33 ` Con Kolivas
2003-07-23 18:52 ` Tom Felker
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=20030723170657.2ba9e7db.florian.huber@mnet-online.de \
--to=florian.huber@mnet-online.de \
--cc=felipe_alfaro@linuxmail.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
all inboxes | Powered by JetHome®