From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.13 breaks udev rule
Date: Sun, 04 Sep 2005 01:00:32 +0000 [thread overview]
Message-ID: <20050904010032.GA30467@vrfy.org> (raw)
In-Reply-To: <20050904003150.GA3958@branci40>
On Sat, Sep 03, 2005 at 05:31:50PM -0700, Jim McCloskey wrote:
> Hello. This simple rule for my Sandisk Minicruizer:
>
> BUS="usb", SYSFS{serial}="0000183546", NAME="%k", SYMLINK="sandisk"
>
> worked without problem under the 2.6.11 kernels, but ceased to work as
> soon as I upgraded to 2.6.13.
...
> SYSFS{scsi_level}="3"
> SYSFS{state}="running"
> SYSFS{timeout}="30"
> SYSFS{type}="0"
> SYSFS{vendor}="Generic "
>
> where the same command run under 2.6.11 yields much much more
> information (all the `usb' bus sections).
There shouldn't be a difference between these kernel versions. Are you sure
that this happens for the _first_ connect after a reboot in both cases?
2.6.13 works without any problem for me.
> This is udev 056 from Debian stable/testing (068 is in unstable).
056 is definitely too old for this kernel version.
Kay
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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:[~2005-09-04 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 0:31 2.6.13 breaks udev rule Jim McCloskey
2005-09-04 1:00 ` Kay Sievers [this message]
2005-09-04 16:04 ` Greg KH
2005-09-04 22:13 ` Jim McCloskey
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=20050904010032.GA30467@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 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).