From: "Marco d'Itri" <md@Linux.IT>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] support directory for rules and permissions
Date: Sun, 22 Feb 2004 15:33:23 +0000 [thread overview]
Message-ID: <20040222153323.GA7864@wonderland.linux.it> (raw)
In-Reply-To: <20040222094521.GC4873@localhost.localdomain>
On Feb 22, Andrey Borzenkov <arvidjaar@mail.ru> wrote:
>- do not want to have multiple files at all?
I definitely need multiple configuration files.
>- do not want support directory but the config_file="file1 file2 ..."?
I like this syntax a lot more, and in fact it is the one I implemented
in the patch I posted yesterday (loosely based on an older version of
your patch) and which I am using in the debian package.
>could you explain what do you mean under "different configurations in
>place"?
My plan is to distribute with the package files like
/etc/udev/udev.rules (enabled by default, devfs-like names)
/etc/udev/udev-compat.rules (enabled by default, some compatibility links)
/etc/udev/udev-full.rules (more compatibility links)
/etc/udev/udev-traditional.rules (old style names)
and allow users to select the files they need from udev.conf.
I /could/ install these files in /usr/share/doc/, but then users who
choose a non-default configuration would have to manually update them
after each upgrade.
>Users should be careful only if they want to replace kernel names with
>something else. But I still fail to see why on earth would they want to?
Because some users want
The main reason to have a configuration directory like /etc/modprobe.d/
is to allow other packages to put there their own files, but this is not
needed for udev.
--
ciao, |
Marco | [4709 ap7bUU.9AuD62]
-------------------------------------------------------
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-22 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 9:45 [PATCH] support directory for rules and permissions Andrey Borzenkov
2004-02-22 10:17 ` Marco d'Itri
2004-02-22 15:02 ` Andrey Borzenkov
2004-02-22 15:33 ` Marco d'Itri [this message]
2004-02-22 18:20 ` Gioele Barabucci
2004-02-22 19:20 ` Marco d'Itri
2004-02-23 0:15 ` Kay Sievers
2004-02-23 8:48 ` Andrey Borzenkov
2004-02-28 15:15 ` Andrey Borzenkov
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=20040222153323.GA7864@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).