From: Harald Hoyer <harald@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: layout of udev config file directories
Date: Fri, 26 Mar 2004 10:16:45 +0000 [thread overview]
Message-ID: <4064030D.8050608@redhat.com> (raw)
In-Reply-To: <20040311175601.GA1230@vrfy.org>
Greg KH wrote:
> On Thu, Mar 11, 2004 at 06:56:01PM +0100, Kay Sievers wrote:
>
>>What is the layout the distributions use for user supplied rule files?
>>I strongly recommend that the we should put this into our tree and
>>pretend that this is the default :)
>>Otherwise every distribution comes up with it's own idea of doing this
>>and we have the same nightmare like so many other projects.
>>
>>And what should be the name of the default files '00-udev.*' ?
>>
>>So, what's the best? Just rename the default to 00-udev.* and have
>>separate directories, where packages can drop their own rule files?
>>
>> /etc/udev/rules.d/
>> /etc/udev/permissions.d/
>
>
> That a good start I think. Anyone else have a proposal?
>
> thanks,
>
> greg k-h
That's cool!
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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
prev parent reply other threads:[~2004-03-26 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 17:56 layout of udev config file directories Kay Sievers
2004-03-12 0:22 ` Greg KH
2004-03-26 10:16 ` Harald Hoyer [this message]
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=4064030D.8050608@redhat.com \
--to=harald@redhat.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 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).