From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 003 release
Date: Fri, 17 Oct 2003 18:19:23 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106654302214362@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106637061520169@msgid-missing>
On Fri, Oct 17, 2003 at 11:57:16AM -0600, clemens@dwf.com wrote:
>
> The new udev is nice, and it 'works', but Im still having two problems:
> (1) Although the messages file shows that it is reading my
> /etc/udev/namedev.config file, the entries are being ignored.
> Ive tried both:
> LABEL, BUS="usb", serial="0B0201420527B284", NAME="usb_disk"
> and
> LABEL, BUS="usb", vendor="DMI", NAME="usb_disk"
>
> and all I get are /udev/ sda, sdb, sdc, sdd, ... as I plug and unplug.
If you turn on debugging for the parser in namedev.c by uncommenting the
comment at the top of the file:
/* define this to enable parsing debugging */
/* #define DEBUG_PARSER */
to look like:
/* define this to enable parsing debugging */
#define DEBUG_PARSER
It will give you a lot of information about what the parser is reading,
and trying to match up with your device. If you could send me the
system debug log from when you plug in your device with the DEBUG_PARSER
define enabled, I'd be glad to look into it.
> /udev, I now get just /udev/sda . Previously (0.2) I got both
> sda and sda1 . Needless to say, a mount attempt on /udev/sda1
> now fails. [[ and if I tell it NAME="usb_disk" what should I
> expect for the name of the first partition???
>
> Am I missing something???
No, I think I broke the partition logic somewhere. I think the name of
the first partition in this case should be "usb_disk1". Yeah, it's a
hack for now, hopefully some new libsysfs changes in regards to the
block sysfs tree will help out with this (it's really hard to determine
the partition is different from the main block device right now in
udev.)
Ah, yeah, udev seg faults right now for partitions. Let me try to track
down the bug, give me a bit of time...
thanks for letting me know,
greg k-h
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
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:[~2003-10-17 18:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 5:56 [ANNOUNCE] udev 003 release Greg KH
2003-10-17 6:32 ` Clemens Schwaighofer
2003-10-17 17:57 ` clemens
2003-10-17 18:19 ` Greg KH [this message]
2003-10-17 18:27 ` Greg KH
2003-10-18 14:56 ` Kay Sievers
2003-10-19 21:01 ` Greg KH
2003-10-20 2:53 ` Kay Sievers
2003-10-20 10:14 ` Kay Sievers
2003-10-20 22:35 ` Greg KH
2003-10-21 0:50 ` Greg KH
2003-10-21 2:43 ` Greg KH
2003-10-21 17:44 ` Greg KH
2003-10-21 20:56 ` Greg KH
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=marc-linux-hotplug-106654302214362@msgid-missing \
--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).