From: Peter Christy <christy@attglobal.net>
To: linux-hotplug@vger.kernel.org
Subject: udev init (cont)
Date: Sun, 04 Jan 2004 18:57:43 +0000 [thread overview]
Message-ID: <200401041857.44026.christy@attglobal.net> (raw)
Firstly, thanks for all the hints & tips guys. I'm starting to get somewhere,
but need some more information.......
I've compiled udev-012, and after running make install, I've moved the start
script and renamed it to /etc/rc.d/rc.udev - the correct place for a
Slackware init script.
I've commented out the line which refers to the functions script (which Slak
doesn't use) and following Takis hints, replaced <action "string" /bin/true>
with <echo "string">
I can now start udev manually, and I can see device nodes appear in /udev.
Further, I can see them appear "automagically" when I plug in usb memory
sticks! So far, so good......
Now the question remains as to where I should put the command to run udev at
startup. Slackware has a command right at the top of rc.S (single user init)
to mount devfs, if it exists. I tried putting something similar in for udev,
but it stopped the machine recognising pcmcia, and hung shortly thereafter.
This implies that udev has to be run pretty late in the boot procedure. But
where? At the end of single user init? In multi-user init (rc.M)? In rc.local
(right at the end of init)? What criteria have to be met before I can run
udev?
I assume it has to run fairly early to pick up things like soundcards. At
present, my /udev only seems to have a very limited number of devices
present, and doesn't include some things I would expect to see in there, like
sound or agp. Which brings me to.....:
Although I can see nodes appearing in udev, is there anything I have to do to
make sure the system is actually using them? For all I know (and I haven't
got this deep yet) the system could be completely ignoring /udev, and just
running with the existing /dev! How do I check? Is there anything else I have
to do?
TIA,
--
Pete
christy@attglobal.net
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&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:[~2004-01-04 18:57 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=200401041857.44026.christy@attglobal.net \
--to=christy@attglobal.net \
--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).