From: Milton Miller <miltonm@bga.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] make 2.5.49 mount root again for devfs users
Date: Mon, 25 Nov 2002 12:30:46 -0600 (CST) [thread overview]
Message-ID: <200211251830.gAPIUkZ90395@sullivan.realtime.net> (raw)
In-Reply-To: <3DE21B96.8BA15D27@aitel.hist.no>
What you did was bypass devfs, and cause create_dev to mknod a file
with the device number of your root instead of creating a symlink
to the normal devfs node.
Is your booter translating the device name into a number? You can
check this by looking at the printed comand line in the dmesg, or
by cat /proc/cmdline .
If you see root=0304 then your booter is translating the device number
and therefore find_in_devfs is failing (possibly because of the previously
metioned patch to read_dir).
I notice that there are lots of hardcoded maxdepth of 64 characters for
the devfs path, but yours seems to be 39 and therefore should be ok.
milton
next prev parent reply other threads:[~2002-11-25 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 12:46 Helge Hafting
2002-11-25 18:30 ` Milton Miller [this message]
2002-11-25 14:22 Helge Hafting
2002-11-25 18:06 Mohamed El Ayouty
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=200211251830.gAPIUkZ90395@sullivan.realtime.net \
--to=miltonm@bga.com \
--cc=helgehaf@aitel.hist.no \
--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®