From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevinfo patch
Date: Fri, 26 Mar 2004 10:15:50 +0000 [thread overview]
Message-ID: <20040326101550.GA32249@vrfy.org> (raw)
In-Reply-To: <20040323215101.GA30721@us.ibm.com>
On Fri, Mar 26, 2004 at 06:25:36AM +0100, Carl-Daniel Hailfinger wrote:
> Kay Sievers wrote:
> > On Fri, Mar 26, 2004 at 01:26:46AM +0100, Carl-Daniel Hailfinger wrote:
> >
> >>Greg KH wrote:
> >>
> >>>On Tue, Mar 23, 2004 at 01:51:01PM -0800, Daniel Stekloff wrote:
> >>>
> >>>
> >>>>Hi Greg,
> >>>>
> >>>>I think this is what you want for udevinfo. Patched against the latest BK
> >>>>tree. I tested it and it seemed to work.
> >>
> >>It seems to have a bug:
> >>
> >>carldani@4100xcdt:~/work/udev-023-orig> ./udevinfo -a -p /sys/block/
> >>
> >>udevinfo starts with the device the node belongs to and then walks up the
> >>[...]
> >>to match the device for which the node will be created.
> >>
> >>device '/sys/block' has major:minor 1:9
> >> looking at class device '/sys/block':
> >>couldn't open class device directory
> >>
> >>
> >>How can /sys/block have a major/minor number which changes everytime I
> >>recompile udevinfo?
> >
> >
> > It's the attribute value read from the last sysfs device.
>
> And why does it only happen with /sys/block/ and not with /sys/block
> (Note the bug depends on the trailing slash).
Cause '/block' isn't recognized as a block device.
strstr(path, "/block/") != NULL)
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=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
next prev parent reply other threads:[~2004-03-26 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 21:51 udevinfo patch Daniel Stekloff
2004-03-23 22:42 ` Kay Sievers
2004-03-24 17:49 ` Greg KH
2004-03-26 0:26 ` Carl-Daniel Hailfinger
2004-03-26 3:47 ` Kay Sievers
2004-03-26 5:25 ` Carl-Daniel Hailfinger
2004-03-26 5:35 ` Ananth N Mavinakayanahalli
2004-03-26 10:15 ` Kay Sievers [this message]
2004-03-26 10:24 ` Kay Sievers
2004-03-26 12:50 ` Ananth N Mavinakayanahalli
2004-03-26 16:43 ` Carl-Daniel Hailfinger
2004-03-26 17:19 ` Kay Sievers
2004-03-31 23:00 ` 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=20040326101550.GA32249@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.