From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: initially building /dev very early in system booting
Date: Sat, 31 Dec 2005 01:26:48 +0000 [thread overview]
Message-ID: <20051231012648.GA8304@vrfy.org> (raw)
In-Reply-To: <20051230220644.GA30318@altair.ipal.net>
On Fri, Dec 30, 2005 at 04:06:44PM -0600, Phil Howard wrote:
> My issue is about how to initially fill in /dev and not at all about any
> hotpluggable devices.
...
> So that brings me to doing what effectively "udevstart" would seem to do.
> But I would not literally use "udevstart". Instead, my thinking was to
> include a subset of that code to build a subset of /dev enough to get the
> system up to the next stage. At this point I don't need all devices, so
> the fact that I won't yet have any udev config files (in /etc which is
> not yet mounted) shouldn't be much of an issue.
...
> So any advice on what is ultimately an effort to scan /sys for devices to
> build into /dev would be appreciated.
Take the two readdir() loops over /sys/block and /sys/class from udevstart.c.
If you find a "dev" file below the current devpath, read() it and call
mknod() with the numbers read and the last part of the current devpath directory.
That should do it, if you don't want to use udev itself for it. Be
prepared, that it will not create /dev/input/mice, but /dev/mice and
such things without any rules configured.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&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
prev parent reply other threads:[~2005-12-31 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 22:06 initially building /dev very early in system booting Phil Howard
2005-12-31 1:26 ` Kay Sievers [this message]
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=20051231012648.GA8304@vrfy.org \
--to=kay.sievers@vrfy.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).