From: rich turner <rich@storix.com>
To: linux-hotplug@vger.kernel.org
Subject: start_udev
Date: Wed, 15 Dec 2004 01:19:07 +0000 [thread overview]
Message-ID: <1103073547.4055.20.camel@rich> (raw)
i am trying to understand exactly what start_udev does.
running fc3 with / on lvm. the initrd created by fc3 works fine and
i realize using fc3's mkinitrd would solve the problem but i want to
understand what is happending.
i have created my own initrd that basically creates the root filesystem
device and exits to allow the kernel to mount the / filesystem. i do not
mount /dev in the initrd or start_udev in the initrd. this all works
fine.
when the initrd exits it executes init (rc.sysinit). everything is fine
until it comes to a line in rc.sysinit to start_udev. then i lose the
devices /dev/vg0/rootlv and checking the root filesystem fails because
there is no device by that name. i still have /dev/dm-255 but my
_real_device_names_ are gone. i could change /etc/fstab to use
/dev/dm-255 but i prefer to use _real_names_
i see that one of the things that start_udev does is mount a tmpfs on
/dev.
does start_udev mount /dev if it already is not mounted?
what is strange is that with the initrd created by fc3 (which does mount
and start udev in the initrd), after running start_udev the
_real_device_names_ for my logical volumes are still there.
does start_udev populate the new /dev with old entries found in the /dev
populated by the initrd?
thanks in advance for any help
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
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
next reply other threads:[~2004-12-15 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 1:19 rich turner [this message]
2004-12-15 3:24 ` start_udev Greg KH
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=1103073547.4055.20.camel@rich \
--to=rich@storix.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).