From: Kay Sievers <kay@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev problems
Date: Sun, 07 Mar 2004 14:41:49 +0000 [thread overview]
Message-ID: <1078670508.1170.47.camel@pim> (raw)
In-Reply-To: <200403071315.02925.michal@cihar.com>
On Sun, 2004-03-07 at 15:30, Michal Èihaø wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sunday 07 of March 2004 15:16, Kay Sievers wrote:
> > On Sun, 2004-03-07 at 13:15, Michal Èihaø wrote:
> > > 21: BUS="scsi", SYSFS{vendor}="Apacer ", SYSFS{model}="Mega Steno
> > > ", PROGRAM="/etc/udev/apacer.sh %k %b %n", NAME="%c{1}", SYMLINK="%k
> > > %c{2} %c{3}"
> > >
> > > Why does every time match another rule?
> >
> > Yeah, It's a bug in the trailin whitespace removal.
> > We mangle the attribut evalue while we compare it and
> > libsysfs reuses it :(
> >
> > Just remove your trailing whitespace from "Apacer " and please tell me
> > if it works. Anyway I will fix it soon.
>
> When I leave just:
>
> BUS="scsi", SYSFS{vendor}="Apacer", PROGRAM="/etc/udev/apacer.sh %k %b %n",
> NAME="%c{1}", SYMLINK="%k %c{2} %c{3}"
>
> It still behaves very non determinantely, sometimes it catches all three
> slots, sometimes just one :-(. This doesn't depend whether there is another
> rule that will catch this device.
>
> Same happens when I try to match it on serial number (AFAIK no trailing
> space):
>
> BUS="usb", SYSFS_serial="19220DA1018B", PROGRAM="/etc/udev/apacer.sh %k %b
> %n", NAME="%c{1}", SYMLINK="%k %c{2} %c{3}"
If devices are missing, whats in sysfs '/sys/block/' at this time?
You may use 'tree /sys/block' to look at it.
Hmm, if all devices are there, seems we need a udev version with debug
enabled. Is it possible for you to build udev from the sources and run
'make DEBUG=true'?
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Ìk
_______________________________________________
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-07 14:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 12:15 udev problems Michal Čihař
2004-03-07 12:29 ` Kay Sievers
2004-03-07 12:47 ` Michal Čihař
2004-03-07 13:10 ` Michal Čihař
2004-03-07 13:44 ` Kay Sievers
2004-03-07 13:49 ` Michal Čihař
2004-03-07 14:05 ` Kay Sievers
2004-03-07 14:16 ` Kay Sievers
2004-03-07 14:20 ` Michal Čihař
2004-03-07 14:28 ` Kay Sievers
2004-03-07 14:30 ` Michal Čihař
2004-03-07 14:41 ` Kay Sievers [this message]
2004-03-07 14:43 ` Michal Čihař
2004-03-07 15:11 ` Michal Čihař
2004-03-07 15:28 ` Michal Čihař
2004-03-07 15:46 ` Michal Čihař
2005-04-18 18:13 ` clemens
2005-04-18 20:49 ` Greg KH
2005-04-18 21:02 ` David Zeuthen
2005-04-18 21:12 ` Greg KH
2005-04-18 21:27 ` clemens
2005-04-18 21:36 ` Kay Sievers
2005-04-19 7:36 ` clemens
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=1078670508.1170.47.camel@pim \
--to=kay@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).