From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] multple rules files support/symlink rules support
Date: Mon, 26 Jan 2004 23:42:21 +0000 [thread overview]
Message-ID: <20040126234221.GA11473@vrfy.org> (raw)
In-Reply-To: <200401172313.00189.arvidjaar@mail.ru>
On Mon, Jan 26, 2004 at 08:31:23PM +0300, Andrey Borzenkov wrote:
> On Thursday 22 January 2004 20:44, Svetoslav Slavtchev wrote:
> > > On Sat, Jan 17, 2004 at 11:13:00PM +0300, Andrey Borzenkov wrote:
> > > > Attached patch adds support for
> > > >
> > > > - multiple rules files. You can now do
...
> I do not :) the only reason to allow multiple files was to allow overriding; I
> had to update patch for ude-014 and sorting directory contents turned out to
> be quite easy so this is the final version - it takes single name which is
> either file or directory; directory is scanned, sorted in ascending order and
> read. klibc version does not support directory.
>
> > >
> > > I don't really understand this. Can you give an example of how this
> > > would work? Why do we want to have multiple symlinks from different
> > > rules?
>
> you simply can't easily merge these two rules. Allowing second rule (in second
> file) is much more flexible - you simply get two symlinks pointing to the
> same file. None of them knows or cares about device is really named as long
> as symlinks are correctly created.
>
> because this version assumes configuration be ordered it now ignores name only
> if it has not already been defined; else name with empty NAME/SYMLINK is
> silently ignored.
Uhh, why do this inside of udev?
You must be root to setup the rules. So we can expect that you are able
to run a update script or something that creates the main file.
This can also merge your conflicting rules if needed.
thanks,
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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-01-26 23:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 20:13 [PATCH] multple rules files support/symlink rules support Andrey Borzenkov
2004-01-20 17:09 ` Andrey Borzenkov
2004-01-20 17:57 ` Svetoslav Slavtchev
2004-01-20 18:45 ` Andrey Borzenkov
2004-01-20 23:10 ` Svetoslav Slavtchev
2004-01-21 23:51 ` Greg KH
2004-01-22 17:44 ` Svetoslav Slavtchev
2004-01-26 17:31 ` Andrey Borzenkov
2004-01-26 23:42 ` Kay Sievers [this message]
2004-01-27 9:54 ` "Andrey Borzenkov"
2004-01-27 11:43 ` Marco d'Itri
2004-02-03 1:04 ` Greg KH
2004-02-03 11:25 ` Gioele Barabucci
2004-02-16 22:34 ` Greg KH
2004-02-17 7:29 ` "Andrey Borzenkov"
2004-02-17 17:29 ` 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=20040126234221.GA11473@vrfy.org \
--to=kay.sievers@vrfy.org \
--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.