From: Phillip Susi <psusi@cfl.rr.com>
To: Paul <set@pobox.com>,
linux-kernel@vger.kernel.org, Phillip Susi <psusi@cfl.rr.com>
Subject: Re: Packet writing issue on 2.6.15.1
Date: Sun, 12 Feb 2006 19:32:15 -0500 [thread overview]
Message-ID: <43EFD38F.30600@cfl.rr.com> (raw)
In-Reply-To: <20060212080727.GE7450@squish.home.loc>
Paul wrote:
>
> 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:
You must first format the cd-rw in packet mode with cdrwtool before
pktcdvd can write to it.
>
> 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?
>
You can't mkudffs on pktcdvd unless the media has been formatted for
packet mode, or in MRW mode, at least until the recent patches were
applied. If the media is formatted for MRW mode, then pktcdvd isn't
required to write to it, but it used to work. With the new patches
applied it will refuse to access MRW discs.
next prev parent reply other threads:[~2006-02-13 0:32 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
2006-02-12 4:54 ` Ville Syrjälä
2006-02-12 8:07 ` Paul
2006-02-13 0:32 ` Phillip Susi [this message]
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=43EFD38F.30600@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=set@pobox.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