Justin Georgeson <[EMAIL PROTECTED]> wrote:
> not quite an answer to your question, but I tried to use mkisofs to make a RR
> image of a file system so I could burn it using an NT box (only machine with a
> burner I have access to). Anyhow I couldn't get mkisofs to do anything other
> than (what appeared to be) cat every file in the directory tree I wanted an
> image of. So whenever I typed mkisofs <stuff> I saw the contents of every file
> fly by, of coures, most of them were binaries, and there was about 450M of
> them, it was quite an irritating experience listening to them.... Anyhow if you
> can figure out how to make mkisofs actually create an image, plz let me know.
I think you're missing the whole point here. You need to RTFM first ... but
here's a hint : (from the mkisofs man page)
SYNOPSIS
mkisofs [ -a ] [ -b boot_image ] [ -c boot_catalog ] [ -A
application_id ] [ -f ] [ -d ] [ -D ] [ -i include-list ]
[ -l ] [ -L ] [ -L ] [ -p preparer ] [ -P publisher ] [ -r
] [ -R ] [ -T ] [ -v ] [ -V ] [ -V volid ] [ -x path ] [
-z ] [ -m glob ] -o filename path
You need to specify an '-o filename' on the command line so that it will
write the directory tree to an image. Normally it will write it all to stdout
so that you can pipe mkisofs to cdrecord and you won't need an intermediary
image. NOTE : this is not suggestable unless your machine is at 0.0% load
and network traffic ... even on my sparc 10 which is notorious for being able
to handle a light load and still perform well, it made me a nice couple of
coasters.
The general practise is to save the mkisofs image to a file and then burn from
that.
Let me know if you need to know any more, and I'll send you my quick
refrence once I'm at work.
> Content-Description: Card for Justin Georgeson
Please turn this off for our mailing list .. youch how mutt did not like this.
Aaron
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
