From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Another UDEV question.
Date: Wed, 03 Mar 2004 23:43:55 +0000 [thread overview]
Message-ID: <20040303234355.GA1308@kroah.com> (raw)
In-Reply-To: <200403032328.i23NSwlv009796@orion.dwf.com>
On Wed, Mar 03, 2004 at 02:16:05PM -0700, reg@dwf.com wrote:
> Ive been trying to get several devices working (again) with
> udev. Greg pointed me in the right direction on the first,
> and I was able to get the second working,- but there is something
> here that I dont understand.
>
> On the first, a usb key, the udevinfo showed the device twice,
> once as a scsi device, once as a usb. Trying to specify the device
> with the 'model' string and the scsi info didnt work, with the
> 'model' and the 'usb' did. I have no idea WHY the one worked and
> not the other.
Hm, I wonder if we are racing the kernel again :(
Can you build udev with:
make clean
make USE_LOG=true DEBUG=true
Then, with the device plugged in, can you run:
./udevtest /block/sda
And send us the output. If that works, and shows us the proper name
(based on the model) then I think our race is here again :(
thanks,
greg k-h
-------------------------------------------------------
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
prev parent reply other threads:[~2004-03-03 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 23:28 Another UDEV question reg
2004-03-03 23:43 ` Greg KH [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=20040303234355.GA1308@kroah.com \
--to=greg@kroah.com \
--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).