linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.6/udev weirdness
Date: Sun, 16 May 2004 09:21:15 +0000	[thread overview]
Message-ID: <40A7328B.40209@gentoo.org> (raw)
In-Reply-To: <20040512235509.GA3836@heliopause.vort.org>

Russell Neches wrote:
> For instance, this document 
> 
>   http://www.reactivated.net/udevrules.php
> 
> mentions rules like 
> 
>   BUS="scsi", SYSFS{manufacturer}="Tekom Technologies, Inc", NAME="%k"
> 
> won't work because it combines information from different directories in
> sysfs. That's why I wrote the my rule the way I did -- because I thought
> it was necessary to avoid this problem. The example USB storage device
> rule from that HOWTO includes the KERNEL="sd*" parameter, but doesn't
> explain the rational for why it is necessary. (Now that I think of it, I
> did see this key when I wrote my rules, and left it out because it
> worked without it. By the time I got to 2.6.6, I'd forgotten all about
> it.)

The rule which you are referring to (containing sd*) is not the example rule, 
thats actually part of the "footnote" section explaining some different 
scenario's.

Would you mind re-reading the section titled "Example: Writing a rule for my 
USB-Storage digital camera"?
In that section I explain the importance of a key such as KERNEL="sd?1", and 
if you had followed this section while writing your rule, I think you may have 
avoided the problems you describe in this thread.
If that still does not clear it up for you, let me know, and I'll see if there 
is a way I can improve the wording there.

Thanks

Daniel


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&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

  parent reply	other threads:[~2004-05-16  9:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12 23:55 2.6.6/udev weirdness Russell Neches
2004-05-13  5:59 ` Greg KH
2004-05-13 17:51 ` Russell Neches
2004-05-13 18:15 ` Kevin P. Fleming
2004-05-13 21:02 ` Greg KH
2004-05-15  5:42 ` Russell Neches
2004-05-16  9:21 ` Daniel Drake [this message]
2004-05-16 21:03 ` Russell Neches
2004-05-17  9:49 ` Daniel Drake

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=40A7328B.40209@gentoo.org \
    --to=dsd@gentoo.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).