From: "Marco d'Itri" <md@Linux.IT>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - allow all files in a directory as the config
Date: Fri, 20 Feb 2004 12:30:41 +0000 [thread overview]
Message-ID: <20040220123041.GA4890@wonderland.linux.it> (raw)
In-Reply-To: <20040220015646.GA13016@vrfy.org>
On Feb 20, Kay Sievers <kay.sievers@vrfy.org> wrote:
>I was on the train for 5 hours today and the TODO is almost empty :)
Don't forget about the patch to merge multiple entries (e.g. for adding
symlinks)... :-)
>We may specify now in udev.conf:
>
> udev_rules="/etc/udev/"
>
>and udev will scan the whole directory for files ending with *.rules,
>sort it in lexical order and create our rule list from all of the files.
>A plain given file will still work and the same applies to the *.permissions.
As a vendor, I think that it would be easier to just specify a list of
files in udev.conf. This way users could easily select the config files
they need (devfs style, devfsstyle with compatibility symlink, old
style, etc) without the need to rename the config files provided
(something annoying for package managers).
--
ciao, |
Marco | [4685 un7QkK300vm7o]
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
next prev parent reply other threads:[~2004-02-20 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 1:56 [PATCH] udev - allow all files in a directory as the config Kay Sievers
2004-02-20 12:30 ` Marco d'Itri [this message]
2004-02-23 19:32 ` Greg KH
2004-02-23 20:21 ` Kay Sievers
2004-02-26 20:55 ` 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=20040220123041.GA4890@wonderland.linux.it \
--to=md@linux.it \
--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).