public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: mal@komcept.com (MAL)
To: linux-mtd@lists.infradead.org
Subject: devfs & mtd
Date: Wed, 26 Feb 2003 19:23:38 +0000	[thread overview]
Message-ID: <3E5D143A.2060806@komcept.com> (raw)

Hi, i'm using a DiskOnChip 2000 48MB, with a 2.4.20 kernel, the CVS MTD 
patches and a patched grub CVS.

I'm also running devfsd, but only to set up legacy /dev nodes, (-np).

All works fine, as long as I use /dev/root as the root fs in fstab.  If 
I try to use /dev/nftl/disk0/part1, (which exists), the filesystem fails 
to mount at init, (even read-only), stating that the device cannot be found.

Yes, devfsd starts _before_ the filesystem mount.

Setting the root filesystem to /dev/root, (which points to 
/dev/nftl/disk0/part1 !), works fine.

Additionally, I still have to pass root=/dev/nftla1 to the kernel, even 
though this location doesn't exist!

Please can someone help me understand how this archaic mess up works :)

Cheers,
MAL

                 reply	other threads:[~2003-02-26 19:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3E5D143A.2060806@komcept.com \
    --to=mal@komcept.com \
    --cc=linux-mtd@lists.infradead.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