From: iSteve <isteve@rulez.cz>
To: Peter Osterlund <petero2@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Packet writing issue on 2.6.15.1
Date: Sat, 11 Feb 2006 12:48:18 +0100 [thread overview]
Message-ID: <20060211124818.063074cc@silver> (raw)
In-Reply-To: <m3r76a875w.fsf@telia.com>
On 11 Feb 2006 12:30:03 +0100
Peter Osterlund <petero2@telia.com> wrote:
> Unfortunately the driver doesn't support variable packet sizes. You
> have to format the disc with a fixed packet size.
>
> Incidentally, the latest git tree (2.6.16-rc2-git10) already contains
> a change which would have made the mount command fail in this case.
>
I apologize for lack of insight in this matter, but... Where is the packet
fixed/variable size set? In the UDF filesystem? Or somewhere in metadata of the
CD? Can I alter it with some data already on the CD, without losing the data?
If the driver cannot handle variable packet size, and it is not matter of
filesystem but matter of CDRW (which I presume), shouldn't the whole pktsetup
fail?
Thanks in advance
--
-- iSteve
next prev parent reply other threads:[~2006-02-11 11:48 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 [this message]
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
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=20060211124818.063074cc@silver \
--to=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