From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] namedev.c %c{N+} capability + buglet with SYMLINK
Date: Mon, 08 Mar 2004 13:04:23 +0000 [thread overview]
Message-ID: <1078751062.1098.15.camel@pim> (raw)
In-Reply-To: <16459.53560.188318.971393@martins.ozlabs.org>
On Mon, 2004-03-08 at 06:02, Martin Schwenke wrote:
> >>>>> "Kay" = Kay Sievers <kay.sievers@vrfy.org> writes:
> * Can '\t' please be a separator too?
Yes, i've put this on my list.
> * Can we please merge your '+' patch?
Sure, there are 5 other patches pending, sone touching this area.
So I will wait until these are merged. It's the number 6.
> Now, about that other bit:
>
> Martin> PROGRAM="/sbin/aliaser %b %k %n %M %m", RESULT="?*", NAME="%c{1}", SYMLINK="%c{2+}"
>
> Martin> [...]
>
> Martin> The only gotcha is that the rule won't apply when SYMLINK
> Martin> gets an empty value (that is, there is only 1 word). This
> Martin> seems kind-of broken, since it stops you using a general
> Martin> rule to do the symlinks, and I think the semantics of an
> Martin> empty SYMLINK value are pretty clear (i.e. no symlinks
> Martin> please).
>
> Looking at namedev.c and udev-add.c, I can't see why SYMLINK
> (dev->symlink, udev->symlink) being set to empty would stop the node
> for NAME being created, but that does seem to be the case.
Hmm, this one works for me:
BUS="scsi", PROGRAM="/bin/echo -n node link1 link2", RESULT="node *", NAME="%c{1}", SYMLINK="%c{4+}"
Could you please build udev with 'make DEBUG=true'.
It will be very verbose to the syslog and we may
find the reason there.
thanks,
Kay
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-03-08 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 1:49 [PATCH] namedev.c %c{N+} capability + buglet with SYMLINK Martin Schwenke
2004-03-08 2:44 ` Kay Sievers
2004-03-08 5:02 ` Martin Schwenke
2004-03-08 13:04 ` Kay Sievers [this message]
2004-03-09 4:37 ` Martin Schwenke
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=1078751062.1098.15.camel@pim \
--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 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).