From: iSteve <isteve@rulez.cz>
To: Phillip Susi <psusi@cfl.rr.com>
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 21:14:40 +0100 [thread overview]
Message-ID: <20060211211440.3b9a4bf9@silver> (raw)
In-Reply-To: <43EE446C.8010402@cfl.rr.com>
On Sat, 11 Feb 2006 15:09:16 -0500
Phillip Susi <psusi@cfl.rr.com> wrote:
> iSteve wrote:
> >
> > Any plans or time estimation to support variable packet size?
> >
> > BTW, can I currently work with packet writing if I only have a CDR? I know
> > it technically is possible, I've seen it done (not on Linux though), but I
> > wonder if it is possible with current codebase.
>
> I've been working on this area lately and thought about implementing
> such support, but I am still not even sure it can really be done, short
> of hacking the udf filesystem to hell so it understands and issues
> commands to burn the variable length packets.
>
> How did you format the existing disc? What does cdrwtool -i show? My
> guess is that you formatted this disc in windows or something and this
> disc isn't using packet mode at all, but rather has been formatted for
> mount rainier mode, in which case, you don't need pktcdvd at all to
> write to it.
>
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?
--
-- iSteve
next prev parent reply other threads:[~2006-02-11 20:14 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 [this message]
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
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=20060211211440.3b9a4bf9@silver \
--to=isteve@rulez.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.