Re: cdrecord tsize confusion
- From: Unruh <unruh-spam@xxxxxxxxxxxxxx>
- Date: Thu, 29 Nov 2007 19:25:27 GMT
ToddAndMargo <ToddAndMargo@xxxxxxxxxxxxxxxxxx> writes:
Hi All,
I am confused. :'(
I am using the cdrecord option "sao". In "man cdrecord", I
have the following example:
To handle drives that need to know the size of a
What makes you think that your drive needs to know? I suspect that you are
just making trouble for yourself.
track before starting to write, first run
mkisofs -R -q -print-size /master/tree
and then run
mkisofs -R /master/tree | cdrecord speed=2 dev=2,0 tsize=XXXs
This is where I get confused. In the example above, it looks like
"/master/tree" is the source directory to create the ISO. If
I run that on my source directory:
/usr/bin/mkisofs -R -quiet -print-size \
/home/KasRescue/Foo/.
And why would you ignore the suggestions and use
/home/KasRescue/Foo/. rather than the suggested /home/KasRescue/Foo
?
And what kind of directory IS /home/KasRescue/Foo/./..?
I get back the followign error message and number:
Unknown file type (unallocated)
home/KasRescue/Foo/./..
- ignoring and continuing.
119247
If I run the command on the ISO I just created with mkisofs:
/usr/bin/mkisofs -R -quiet -print-size \
/home/KasRescue/Foo.iso
I get back a different number AND NO ERROR MESSAGE
119309
Yes. you are now asking the system to create and iso containing the iso you
just created. Why you would want to do that I do not know, but that iso
WILL contain additional information not the original directory system.
Anyway, who are you doing all this?
What am I misunderstanding?
Many thanks,.
-T
- Follow-Ups:
- Re: cdrecord tsize confusion
- From: ToddAndMargo
- Re: cdrecord tsize confusion
- From: ToddAndMargo
- Re: cdrecord tsize confusion
- References:
- cdrecord tsize confusion
- From: ToddAndMargo
- cdrecord tsize confusion
- Prev by Date: sudo config using sudoers
- Next by Date: >>>> Watch FREE Satellite TV on PC - Without Paying Monthly Fees <<<<
- Previous by thread: Re: cdrecord tsize confusion
- Next by thread: Re: cdrecord tsize confusion
- Index(es):
Relevant Pages
|