From: "John L. Fjellstad" <john-hotplug@fjellstad.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: little udev problem - loop devices instead of hda devices!
Date: Thu, 12 Feb 2004 21:03:32 +0000 [thread overview]
Message-ID: <20040212210332.GA4129@fjellstad.org> (raw)
In-Reply-To: <1076601040.402ba0d05eb01@webmail.fish.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
On Thu, Feb 12, 2004 at 03:50:40PM +0000, fbarton@fish.co.uk wrote:
> What should I do to make sure my hda partitions are found at boot time? Why are
> the loop devices being created instead? Is it safe yet to empty /dev and just
> rely on /udev when things are properly configured (and presumably udev then
> somehow symlinks from /dev or intercepts calls to /dev/* and uses /udev/*
> instead)? Should I just go in and mknod my hda* devices again or would that not
> be a good idea? Anyone have an idea what I might have set up wrong; or does
> this look as if a piece of software is missing???
Well, I'm not an expert on udev yet, and other people on the list can
probably correct me if I make a mistake somewhere (hopefully, they'll be
gentle).
udev is a completely userspace program, unlike devfs that lived
partly in the kernel. udev will probably be started as part of init.d,
meaning it won't start up until after / has been mounted. This is a
catch-22, of course, since the system needs udev to run to find the root
partition and console, and udev won't start up until the system is up.
So, the fix this, you have to create a initrd(?) image to load up the
initial system with the bare minimum devices statically created (your /,
console etc), and then switch over to udev once / has been mounted.
Right now, udev only lives on one directory. Check your
/etc/udev/udev.conf entry for udev_root for where that is. If it is
/udev, /dev is not used at all.
As to your /dev/loop0-/dev/loop7, I suspect you have loop either
statically linked, or loaded as a module. I try to load the loop module,
and those devices got created.
Finally, even though devfs has been set to obsolete in 2.6.x, it won't
be removed yet, so you can safely use it if it works for you for now.
I personally run devfs to manage my /dev, while I'm testing udev on
/udev.
--
John L. Fjellstad
web: http://www.fjellstad.org/ Quis custodiet ipsos custodes
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2004-02-12 21:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 15:50 little udev problem - loop devices instead of hda devices! fbarton
2004-02-12 21:03 ` John L. Fjellstad [this message]
2004-02-13 1:32 ` Greg KH
2004-02-15 3:28 ` Francis Barton
2004-02-21 17:43 ` Francis Barton
2004-02-21 17:51 ` Jon Smirl
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=20040212210332.GA4129@fjellstad.org \
--to=john-hotplug@fjellstad.org \
--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).