>> mkisofs has the ability to use file lists, so your problem is creating
>> one. Try something like this:
>>
>> cd MYDIR
>> ls -F | grep -v '[/*@]$' > /tmp/filelist1
>>
>I created the file list but I am not sure how to use mkisofs to read it. I
>check man mkisofs but didn't see anything about file lists. I reckon that I
>will need your help again.
>
>Would it be easier to pipe the result of the above command to mkisofs and then
>to cdrecord? I guess it is a dumb question, isn't it?
The "correct" term is "path list" - i.e. use the -path-list option.
However, the list of pathspecs must be in the same format as if they
were given on the command line. In your case, this shouldn't be a problem
as you are only using files that one directory deep.
There are at least three ways of making mkisofs use only selected files:
1. Use a path list, created with something like:
find [options] -print | awk '{printf("%s=%s\n",$1,$1)"}' > /tmp/pathlist
(may have to edit /tmp/pathlist by hand to ensure the syntax is correct)
mkisofs [options] -graft-points -path-list /tmp/pathlist
2. Use an exclude file, created with something like:
find [options] -print > /tmp/excludelist
mkisofs [options] -exclude-list /tmp/excludelist path_to_cd_src
mkisofs will have to check EVERY file against the exclude list - if you
have a CD source directory with 2000 files and want to exclude 1000 files,
then there will be about 1.5 million string compares ...
3. Make a "hard link" tree, created with something like:
find [options] -print | cpio -pdmvl /some/path/on/same/disk
mkisofs [options] /some/path/on/same/disk
If you use the Rock Ridge options, then the resulting files on the CD will
show up with two (or more) links, although they only have one ...
James Pearson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
