From: Rob Love <rml@tech9.net>
To: linux-hotplug@vger.kernel.org
Subject: [howto] easy udev setup in Fedora
Date: Tue, 09 Dec 2003 21:27:05 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107100546816197@msgid-missing> (raw)
OK, fedora-devel now comes with a 2.6 kernel (rah rah), and Fedora Core
2 is slated to be a 2.6 kernel-based distribution.
So, for those of you using fedora-devel, or planning to upgrade to
Fedora Core 2 when released, there is no reason not to dance in the
beauty of a dynamic dev directory.
I have compiled these easy-to-follow steps:
- download and install the udev rpm [1]
- download the udev tarball [2] and untar it
- copy etc/init.d/udev to /etc/init.d
- type "/sbin/chkconfig --add udev"
- make sure that your /udev is mounted during early
boot, if it is not a directory on your root
- reboot
And then it will Just Work.
Really, all of these steps should be automated by the RPM spec file. I
will add that. But for now, the above will suffice.
[1] http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-008-1.i386.rpm
[2] http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-008.tar.gz
Rob Love
-------------------------------------------------------
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:[~2003-12-09 21:27 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=marc-linux-hotplug-107100546816197@msgid-missing \
--to=rml@tech9.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).