From: Phillip Susi <psusi@cfl.rr.com>
To: iSteve <isteve@rulez.cz>
Cc: linux-kernel@vger.kernel.org, Peter Osterlund <petero2@telia.com>
Subject: Re: Packet writing issue on 2.6.15.1
Date: Sat, 11 Feb 2006 20:10:56 -0500 [thread overview]
Message-ID: <43EE8B20.7000602@cfl.rr.com> (raw)
In-Reply-To: <20060211211440.3b9a4bf9@silver>
iSteve wrote:
> I used cdrecord (via xcdroast) to blank the CDRW and then burn UDF image created
> by mkudffs.
>
> Can I get this mount rainer udf extension work using just this method, and then
> mount it?
>
> Are there any specific mkudffs option that can help me? Or am I absolutely
> obliged to use cdrwtool if I want to even think about using packet writing or
> any other method to mount a CDRW?
cdrecord is just burning the image in dao/tao/sao mode. To use pktcdvd
to read/write the disc on the fly it must be formatted for packet mode
using cdrwtool. If the disc is formatted in MRW mode, then you don't
even need pktcdvd to read/write it, that is supported by the firmware in
the drive. Right now I believe you can use the dvd-rwtools package to
format media in MRW mode, and I plan on adding it as an option to
cdrwtool at some point. See http://fy.chalmers.se/~appro/linux/DVD+RW/
for more info.
The difference between packet mode and MRW mode is that MRW reserves
some of the disc for bad sector sparing, and the drive firmware handles
the reblocking rather than pktcdvd ( it also handles the sector
remapping ). Packet mode was around first and has wider support and
requires less from the drive's firmware, but these days, it seems that
the vast majority of drives support MRW.
I still have not figured out if MRW uses zero loss linking. If it does,
then that would probably make up for the space it reserves for sector
sparing. If it does not, then packet mode with > 32 sector packets will
be more space efficient. I have been planning on experimenting to see
if it is possible to format the disc in packet mode with zero loss
linking on some newer drives. I believe that may be possible in which
case, that will eliminate the space overhead associated with packet mode
entirely.
next prev parent reply other threads:[~2006-02-12 1:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 9:35 Packet writing issue on 2.6.15.1 iSteve
2006-02-11 11:30 ` Peter Osterlund
2006-02-11 11:48 ` iSteve
2006-02-11 15:59 ` Peter Osterlund
2006-02-11 16:08 ` iSteve
2006-02-11 20:09 ` Phillip Susi
2006-02-11 20:14 ` iSteve
2006-02-12 1:10 ` Phillip Susi [this message]
2006-02-12 4:54 ` Ville Syrjälä
2006-02-12 8:07 ` Paul
2006-02-13 0:32 ` Phillip Susi
2006-02-13 4:40 ` Paul
2006-02-13 15:45 ` Phillip Susi
2006-02-12 8:23 ` iSteve
2006-02-12 10:32 ` Jan Engelhardt
2006-02-12 10:46 ` iSteve
2006-02-13 0:34 ` Phillip Susi
2006-02-13 15:00 ` iSteve
2006-02-13 15:48 ` Phillip Susi
2006-02-13 17:51 ` iSteve
2006-02-13 19:45 ` Phillip Susi
2006-02-13 19:55 ` iSteve
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=43EE8B20.7000602@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=isteve@rulez.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/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