mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: John Jasen <jjasen1@umbc.edu>
Cc: "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, 1 Feb 2001 11:48:48 -0600	[thread overview]
Message-ID: <20010201114848.A4161@cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0101312258190.227-100000@sliver.moot.ca> <Pine.SGI.4.31L.02.0102011058520.71788-100000@irix2.gl.umbc.edu>
In-Reply-To: <Pine.SGI.4.31L.02.0102011058520.71788-100000@irix2.gl.umbc.edu>; from jjasen1@umbc.edu on Thu, Feb 01, 2001 at 11:00:05AM -0500


  [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.

I don't think you can use the /dev/discs/ link for "root=".  It was a
long time ago that I ran into this issue -- but as I recall, links with
'..' in them do not work before the vfs is fully operational.  When I
brought it up with Richard he basically said "don't do that then".

Peter
-
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/

  reply	other threads:[~2001-02-01 17:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01  5:03 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 [this message]
2001-02-01 18:51     ` John Jasen
2001-02-01 20:58       ` Peter Samuelson
2001-02-01 23:53       ` David Ford
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=20010201114848.A4161@cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=jjasen1@umbc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjd@moot.ca \
    /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®