From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [BUG, Patch] udev_volume_id -d option is broken
Date: Fri, 04 Feb 2005 13:59:06 +0000 [thread overview]
Message-ID: <1107525546.4644.37.camel@localhost.localdomain> (raw)
In-Reply-To: <200501281441.26113.cborntra@de.ibm.com>
On Sun, 2005-01-30 at 05:36 +0100, Kay Sievers wrote:
> On Fri, 2005-01-28 at 14:41 +0100, Christian Bornträger wrote:
> > The -d option in udev_allows to go from a partition to the underlying
> > disk
> > for s390 dasd labels. If the device is already the disk itself,
> > finding the
> > parent will fail, therefore -d on /sys/block/dasda/ for example gives
> > no
> > result at all.
>
> Yes, seems like a stupid bug. I've applied it to my tree.
If you have a chance to try the version in udev-051 on one of these
boxes, it would be nice to know if it is still working as expected. I
have moved the dasd label reading into a restructured version of the
volume_id library now.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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-02-04 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 13:41 [BUG, Patch] udev_volume_id -d option is broken Christian Bornträger
2005-01-30 4:36 ` Kay Sievers
2005-02-04 13:59 ` Kay Sievers [this message]
2005-02-07 18:39 ` Christian Borntraeger
2005-02-08 19:46 ` Kay Sievers
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=1107525546.4644.37.camel@localhost.localdomain \
--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.