From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Udev and initscripts
Date: Fri, 04 Jun 2004 10:46:36 +0000 [thread overview]
Message-ID: <40C0530C.7010102@ums.usu.ru> (raw)
It has been stated many times that scripts that should run after device
is available should live in /etc/dev.d directory. However, I have
trouble following this. The recommendation works perfectly when one has
to wait for creation of a single device, but it is difficult or
impossible to implement when waiting for many unknown devices.
The problem is that Linux From Scratch needs an initscript with the
following properties:
1) it should read a file "/etc/sysconfig/modules" (aka "/etc/modules" in
Debian). All modules listed there by the user should be modprobed into
the kernel.
2) The next initscript should be able to assume that all devices it
needs are already there.
How do I implement (2), i.e., wait for creation of all devices that can
be created by a user-specified list of modules?
Just doing nothing does not work, as illustrated by the following example:
[root in ~]# modprobe nbd ; ( ls /dev/nbd* | wc -l ) ; sleep 1 ; \
( ls /dev/nbd* | wc -l )
113
128
--
Alexander E. Patrakov
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
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-06-04 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 10:46 Alexander E. Patrakov [this message]
2004-06-04 13:36 ` Udev and initscripts Kevin P. Fleming
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=40C0530C.7010102@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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).