From: David Ford <david@linux.com>
To: John Jasen <jjasen1@umbc.edu>
Cc: Peter Samuelson <peter@cadcamlab.org>,
"Michael J. Dikkema" <mjd@moot.ca>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.1 - can't read root fs (devfs maybe?)
Date: Thu, 01 Feb 2001 15:53:43 -0800 [thread overview]
Message-ID: <3A79F707.FD9629E6@linux.com> (raw)
In-Reply-To: <Pine.SGI.4.31L.02.0102011349410.71788-100000@irix2.gl.umbc.edu>
John Jasen wrote:
> On Thu, 1 Feb 2001, Peter Samuelson wrote:
>
> > [Michael J. Dikkema]
> > > > I went from 2.4.0 to 2.4.1 and was surprised that either the root
> > > > filesystem wasn't mounted, or it couldn't be read. I'm using devfs.. I'm
> > > > thinking there might have been a change with regards to the devfs
> > > > tree.. is the legacy /dev/hda1 still /dev/discs/disc0/part1?
> > > >
> > > > I can't even get a shell with init=/bin/bash..
> >
> > [John Jasen]
> > > Sounds like a lack of devfsd, which handles backwards compatibility
> > > for /dev entries.
> >
> > devfsd does not start up until after the root filesystem is mounted, so
> > that's not it.
>
> Errrr .... upon careful reading of the devfs/devfsd documentation, you'll
> find that it says to put /sbin/devfsd /dev in amongst the first lines in
> rc.sysinit.
>
> In looking through rc.sysinit, / is not mounted rw until much later.
Logic suggests that the root filesystem must be mounted before init runs. If
init=/bin/bash, no boot scripts are run, devfs should have populated /dev before
the init was spawned. devfs doesn't depend on the write state of the filesystem.
I am running devfs on 2.4.1, automatically mounted. I am having no problems.
-d
--
There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-01 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 5:03 2.4.1 - can't read root fs (devfs maybe?) Michael J. Dikkema
2001-01-31 6:14 ` Michael B. Trausch
2001-02-01 16:00 ` John Jasen
2001-02-01 17:48 ` Peter Samuelson
2001-02-01 18:51 ` John Jasen
2001-02-01 20:58 ` Peter Samuelson
2001-02-01 23:53 ` David Ford [this message]
2001-02-01 23:58 ` David Ford
2001-02-02 13:54 ` mirabilos
2001-02-03 1:54 ` David Ford
2001-02-14 21:20 ` Richard Gooch
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=3A79F707.FD9629E6@linux.com \
--to=david@linux.com \
--cc=jjasen1@umbc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mjd@moot.ca \
--cc=peter@cadcamlab.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