From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - allow all files in a directory as the config
Date: Thu, 26 Feb 2004 20:55:52 +0000 [thread overview]
Message-ID: <20040226205552.GA13134@kroah.com> (raw)
In-Reply-To: <20040220015646.GA13016@vrfy.org>
On Mon, Feb 23, 2004 at 09:21:53PM +0100, Kay Sievers wrote:
> On Mon, Feb 23, 2004 at 11:32:29AM -0800, Greg KH wrote:
> > On Fri, Feb 20, 2004 at 02:56:46AM +0100, Kay Sievers wrote:
> > > I was on the train for 5 hours today and the TODO is almost empty :)
> > > So, at least four people wanted this feature, then here is a actual
> > > working patch.
> > >
> > > 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.
> > >
> > > I sort the files in our usual linked list, cause klibc has no scandir().
> >
> > Nice, applied, thanks.
>
> Nice, here is the corresponding man update which also removes the
> mention of the limitation of getgrname() and friends with klibc.
Applied, thanks.
greg k-h
-------------------------------------------------------
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
prev parent reply other threads:[~2004-02-26 20:55 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
2004-02-23 19:32 ` Greg KH
2004-02-23 20:21 ` Kay Sievers
2004-02-26 20:55 ` Greg KH [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=20040226205552.GA13134@kroah.com \
--to=greg@kroah.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.