From: Paul <set@pobox.com>
To: linux-kernel@vger.kernel.org
Cc: Phillip Susi <psusi@cfl.rr.com>
Subject: Re: Packet writing issue on 2.6.15.1
Date: Sun, 12 Feb 2006 03:07:27 -0500 [thread overview]
Message-ID: <20060212080727.GE7450@squish.home.loc> (raw)
In-Reply-To: <43EE8B20.7000602@cfl.rr.com>
Phillip Susi <psusi@cfl.rr.com>, on Sat Feb 11, 2006 [08:10:56 PM] said:
> 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.
Hi;
This is not technically true; once the pktcdvd mapping is made,
the device can be accessed like a r/w block device. For example, after
I associate the dvd with the pktcdvd device, I then can associate it
with a cryptographic loop device, and mke2fs on that, then mount it
and use it like any other filesystem. Something like:
pktsetup dvd /dev/dvd
losetup -e serpent-256 /dev/loop0 /dev/pktcdvd/dvd
mke2fs -m0 /dev/loop0
mount -o noatime,rw /dev/loop0 /mntpoint
I realize you are differentiating between burning an iso
type image from what cdrwtool does, but I thought I would mention
my usage;) Obviously this would not be compatible with anything
else, which is intentional.
What is the difference between using cdrwtool on the cd/vd-rw
to form an initial image, and just doing a mkudffs on a pktcdvd
associated device?
Paul
set@pobox.com
next prev parent reply other threads:[~2006-02-12 8:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 9:35 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
2006-02-12 4:54 ` Ville Syrjälä
2006-02-12 8:07 ` Paul [this message]
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=20060212080727.GE7450@squish.home.loc \
--to=set@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.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
all inboxes | Powered by JetHome®