Re: Oddness piping mkisofs into recent cdrecord versions
Craig Harding wrote:
I've had the same problem and if you use tsize=`mkisofs -print-size
-quiet file.iso`s as one of the flags then it should work..
Make note that the 's' after the tsize cmd is correct, check the man
page for this flag..
The issue is that the mkisofs is running on another machine over a
network. I want to burn a CD, and it is really not desirable to jump
through hoops to do so, nor to try and get the tsize= through reliably.
A drawback to the recording modes or ISO filesystem characteristics. As
noted an oddity rather than a bug.
eg: mkisofs file.iso | cdrecord -data tsize=`mkisofs -print-size
-quiet file.iso`s -
On 12/18/06, *Joerg Schilling* < Joerg.Schilling@fokus.fraunhofer.de
Bill Davidsen < email@example.com <mailto:firstname.lastname@example.org>> wrote:
> I have a system with a Pioneer DVR-104 drive, revision 1.40
> When I try to pipe an ISO into the cdrecord program, it
> it needs tsize= option to do the burn. Piping the same data
> growisofs works fine on the same hardware and O/S, but requires
> use a DVD, when a CD would be adequate at times.
cdrecord writes in session at one mode, growifofs writes in packet
<mailto:EMail:email@example.com> (home) Jörg
Schilling D-13353 Berlin
<mailto:firstname.lastname@example.org> (work) Blog:
To UNSUBSCRIBE, email to cdwrite-REQUEST@other.debian.org
with a subject of "unsubscribe". Trouble? Contact
bill davidsen <email@example.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979