public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Luke-Jr <luke@dashjr.org>, Jesper Juhl <jesper.juhl@gmail.com>,
	Bernhard Rosenkraenzer <bero@arklinux.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [slightly OT] dvdrecord 0.3.1 -- and yes, dev=/dev/cdrom works ;)
Date: Mon, 27 Feb 2006 12:59:52 +1300	[thread overview]
Message-ID: <440240F8.3010207@vilain.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0602262331330.12118@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
>>>And what about DVD-RAM drives? Any plans to support those?
>>My [limited] understanding of DVD-RAM drives was that they are basically 
>>removable block devices... you wouldn't need a recording program for that, 
>>you'd use it like a floppy.
> Same goes for DVD+RW. One may want to use it in conjunction with pktcdvd 
> for aligning and command queueing/iosched reasons.

Can I mount a friendly challenge to that idea?

The reason being, I've got a DVD writer that supports DVD-RAM, and 
because I was curious I bought one.  The media is *hard sectored*.  That 
is, you look at the underneath and you see a series of concentric dots, 
each the same angular distance from each other.  I had presumed that 
these are to give the drive something big to key its read/write 
operations on.  Nice, except I don't think the media is compatible with 
a regular DVD drive.

DVD+RW, on the other hand, I just thought was a different surface 
technology (more expensive, higher quality) than DVD-RW.  There is 
nothing to help with the lead-in/lead-out problem that is why you have 
several megabytes of lead-in and lead-out per session on a multi-session 
disc.

But maybe I'm wrong here... if I could use a DVD+RW like a DVD-RAM I'd 
be very happy indeed.

Sam.

  reply	other threads:[~2006-02-27  0:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 23:42 [slightly OT] dvdrecord 0.3.1 -- and yes, dev=/dev/cdrom works ;) Bernhard Rosenkraenzer
2006-02-25 18:17 ` David Gómez
2006-02-25 18:38   ` Jesper Juhl
2006-02-25 19:14 ` Gene Heskett
2006-02-26 13:30 ` Luke-Jr
2006-02-26 13:29   ` Jesper Juhl
2006-02-26 13:39     ` Luke-Jr
2006-02-26 13:36       ` Jesper Juhl
2006-02-26 15:50       ` Bernd Petrovitsch
2006-02-26 22:32       ` Jan Engelhardt
2006-02-26 23:59         ` Sam Vilain [this message]
2006-02-27 18:50           ` Jan Engelhardt
2006-02-28 18:58             ` Phillip Susi
2006-02-28 19:14               ` Jan Engelhardt
2006-02-28 22:30                 ` Bill Davidsen
2006-03-08 13:52                   ` Jan Engelhardt
2006-03-01  0:05               ` Rob Sims
2006-02-27 15:32 ` Dick Streefland

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=440240F8.3010207@vilain.net \
    --to=sam@vilain.net \
    --cc=bero@arklinux.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@dashjr.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