From: Robert McMeekin <rrm3@rrm3.org>
To: linux-hotplug@vger.kernel.org
Subject: FAQ udev.rules.devfs
Date: Wed, 28 Jan 2004 20:27:57 +0000 [thread overview]
Message-ID: <1075321676.28559.3.camel@station.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 57 bytes --]
Hello,
I have a very small patch for the udev FAQ. :-)
[-- Attachment #2: udev-FAQ.patch --]
[-- Type: text/x-patch, Size: 601 bytes --]
--- FAQ.orig 2004-01-28 15:24:15.725363384 -0500
+++ FAQ 2004-01-28 15:24:40.129653368 -0500
@@ -53,7 +53,7 @@
Q: I really like the devfs naming scheme, will udev do that?
A: Yes, udev can create /dev nodes using the devfs naming policy. A
configuration file needs to be created to map the kernel default names
- to the devfs names. See the initial udev.conf.devfs file in the udev
+ to the devfs names. See the initial udev.rules.devfs file in the udev
release. It is the start of such a configuration file. If there are
any things missing, please let the udev authors know.
next reply other threads:[~2004-01-28 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 20:27 Robert McMeekin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 0:20 FAQ udev.rules.devfs 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=1075321676.28559.3.camel@station.local \
--to=rrm3@rrm3.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).