From: Ian Campbell <ijc@hellion.org.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] support identification of Xen virtual block devices
Date: Fri, 17 Apr 2009 08:13:27 +0000 [thread overview]
Message-ID: <1239956007.15147.922.camel@localhost.localdomain> (raw)
In-Reply-To: <1239907047.15147.95.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On Fri, 2009-04-17 at 00:54 +0200, Kay Sievers wrote:
> On Thu, Apr 16, 2009 at 23:33, Ian Campbell <ijc@hellion.org.uk> wrote:
> > On Thu, 2009-04-16 at 22:17 +0200, Kay Sievers wrote:
> >> On Thu, Apr 16, 2009 at 20:37, Ian Campbell <ijc@hellion.org.uk> wrote:
> >> >
> >> > * Add xenvb_id utility to identify Xen disk and CD-ROM devices.
> >>
> >> What's the reason xen optical drives don't behave like real drives,
> >> and need a xen specific tool? That sounds rather odd,
> >
> > They aren't proper SCSI devices so you can't do SCSI inquiry like
> > cdrom_id wants, the properties you can query from a Xen vbd are very
> > basic, basically just TYPE=disk|cd.
> >
> > I suppose I could make the SCSI INQ stuff in cdrom_id optional, since
> > the CDROM_GET_CAPABILITY ioctl is implemented. Would that be preferred?
>
> Please check the stuff I put in the git tree:
> http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=55d8f5e208396589476583dad8f2a7f2db3e2ef5
That works fine, thanks!
Ian.
--
Ian Campbell
The world really isn't any worse. It's just that the news coverage
is so much better.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-04-17 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 18:37 [PATCH] support identification of Xen virtual block devices Ian Campbell
2009-04-16 20:17 ` Kay Sievers
2009-04-16 21:33 ` Ian Campbell
2009-04-16 22:54 ` Kay Sievers
2009-04-17 8:13 ` Ian Campbell [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=1239956007.15147.922.camel@localhost.localdomain \
--to=ijc@hellion.org.uk \
--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).