public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Heinz <thomasheinz@gmx.net>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: SCSI DVD-RAM partitions
Date: Fri, 5 Aug 2005 19:02:19 +0200	[thread overview]
Message-ID: <200508051902.20165.thomasheinz@gmx.net> (raw)
In-Reply-To: <20050731140157.GA6173@infradead.org>

Hi Christoph

You wrote:
>>Ok, thanks for your valuable input. In fact, I thought about making
>>the device available both as /dev/srX and /dev/sdX at the same time
>>in order to support partitions. In my case it would even suffice to
>>make it available as /dev/sdX instead of /dev/srX.
> 
> That doesn't make sense because sd is a very different driver from sd.
> Besides that aliasing different dev_ts to the same underlying blockdevice
> can't work, it's cause all sorts of aliasing problems.

Ok.

> It would probably be better to use device-mapper than the loop device.
> I think there's already userland partition parsing code for dm, and
> having a simple command line tool to do that, and maybe even automatically
> run through udev and creating /dev/sr<num>p<partition> devices would
> be very nice to have as an almost invisible workaround.

Ok, that sounds reasonable. I have not yet searched for the partition
parsing code for dm but it should not be too hard to write this on
one's own. However, it is not clear to me whether this would work
automatically, i.e. insert dvd-ram medium -> udev event is triggered ->
device nodes are created via dmsetup.

Will there some (udev) event be triggered once a dvd-ram medium is
inserted?

Moreover, some event would have to be triggered if the dvd-ram medium
is removed in order to delete the device nodes.


Regards,

Thomas

      reply	other threads:[~2005-08-05 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09 12:32 SCSI DVD-RAM partitions Thomas Heinz
2005-07-12  2:37 ` Christoph Hellwig
2005-07-12  8:23   ` Thomas Heinz
2005-07-31 14:01     ` Christoph Hellwig
2005-08-05 17:02       ` Thomas Heinz [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=200508051902.20165.thomasheinz@gmx.net \
    --to=thomasheinz@gmx.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@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