From: Gioele Barabucci <gioele@gioelebarabucci.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] support directory for rules and permissions
Date: Sun, 22 Feb 2004 18:20:09 +0000 [thread overview]
Message-ID: <200402221920.09402.gioele@gioelebarabucci.com> (raw)
In-Reply-To: <20040222094521.GC4873@localhost.localdomain>
On Sunday 22 February 2004 16:33, Marco d'Itri wrote:
> >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.
What if the same package would like to specify a dev name?
--
Gioele
-------------------------------------------------------
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 18:20 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
2004-02-22 18:20 ` Gioele Barabucci [this message]
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=200402221920.09402.gioele@gioelebarabucci.com \
--to=gioele@gioelebarabucci.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.