From: iSteve <isteve@rulez.cz>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Phillip Susi <psusi@cfl.rr.com>,
linux-kernel@vger.kernel.org, Peter Osterlund <petero2@telia.com>
Subject: Re: Packet writing issue on 2.6.15.1
Date: Sun, 12 Feb 2006 11:46:40 +0100 [thread overview]
Message-ID: <20060212114640.31765c3a@silver> (raw)
In-Reply-To: <Pine.LNX.4.61.0602121129590.25363@yvahk01.tjqt.qr>
On Sun, 12 Feb 2006 11:32:31 +0100 (MET)
Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> Like...?
>
> cdrwtool -d /dev/hdb -q
> pktsetup 0 /dev/hdb
>
> "Burning something non-udf there":
> mkfs.xfs /dev/pktcdvd/0
> mkisofs -o /dev/pktcdvd/0 somefiles
> tar -cf /dev/pktcdvd/0 somemorefiles
>
> Anything.
"without actually having to use UDF and packet writing on the burning
side" ... sorry, should've been 'or'. I am trying to find a way that wouldn't
require having packet writing support in kernel (or as module, of course) with
the initial burning.
--
-- iSteve
next prev parent reply other threads:[~2006-02-12 10:46 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
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 [this message]
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=20060212114640.31765c3a@silver \
--to=isteve@rulez.cz \
--cc=jengelh@linux01.gwdg.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox