linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nori.sekhar@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Booting a udev only system
Date: Wed, 02 Mar 2005 06:21:03 +0000	[thread overview]
Message-ID: <93840d07050301220924f1e062@mail.gmail.com> (raw)

Hi,

I using kernel version 2.6.10 (kernel.org) and wish to use udev
instead of devfs. Using devfs I have been able to boot-up the kernel
using cramfs and busybox.

However, when trying to boot after I switch on CONFIG_HOTPLUG and
switching off CONFIG_DEVFS_FS, I get the following error on boot.

VFS: Cannot open root device "mtdblock/0" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I observed that do_mount_root called from mount_block_root in
init/do_mounts.c is Returning error code -6 (ENXIO - no such device or address)
when it tries to mount /dev/root on /root.

Should ramfs be the filesystem for /dev in case devfs is not used?
If yes, how can I get this configured?

I have the udev and hotplug programs loaded into the cramfs image,
but frankly I cant see how they come into the picture till the root
device is mounted successfully.

Is there any document on how to get a udev only system get started
on a kernel.org kernel and busybox. (without using initrd)

Any help in this regard is highly appreciated.

Thanks,
Sekhar Nori


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2005-03-02  6:21 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=93840d07050301220924f1e062@mail.gmail.com \
    --to=nori.sekhar@gmail.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).