From: Christophe Saout <christophe@saout.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: IGNORE method
Date: Tue, 13 Jan 2004 18:24:26 +0000 [thread overview]
Message-ID: <1074018266.8658.2.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <20040110013128.GA2112@vrfy.org>
Am Di, den 13.01.2004 schrieb Greg KH um 19:08:
> On Sat, Jan 10, 2004 at 11:44:10AM +0100, Christophe Saout wrote:
> > Am Sa, den 10.01.2004 schrieb Greg KH um 02:35:
> > >
> > > Ah. Yeah, that might be a lot simpler. Something like (in your new
> > > syntax):
> > > KERNEL="dm-[0-9]*", NAME=""
> > >
> > > It's not the most intuitive, but I could live with it. Christophe, what
> > > do you think?
> >
> > Sure, I thought of this too. I added the IGNORE rule because it's more
> > intuitive but if this is more flexible, I'm ok with it. You should be
> > aware that this would also ignore an additional SYMLINK.
>
> So you would like to not create a name, but create a symlink? What
> would you create the symlink to?
No, I don't want to. :D I just wondered what should be done if a symlink
is specified but an empty name. A warning? At the moment udev silently
ignores errors anyway so... not important.
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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-01-13 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 1:31 IGNORE method Kay Sievers
2004-01-10 1:35 ` Greg KH
2004-01-10 10:44 ` Christophe Saout
2004-01-13 18:08 ` Greg KH
2004-01-13 18:24 ` Christophe Saout [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=1074018266.8658.2.camel@leto.cs.pocnet.net \
--to=christophe@saout.de \
--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.