In the recent discussion on directory loops the background of what
caused the problem got lost a litlle. So I'll try again.
Basically, I have a list of files (and directories) that I want to put
on a CD. So I want to feed this list of files to mkisofs.
However, mkisofs does not take files (as arguments, and from
-path-list), but pathspecs. The difference? Consider the following
situation:
foo/
file.dat
bar -> foo
As a file, 'bar' would be placed on the CD (assuming rr). But as a
pathspec, it is interpreted as the directory it points to, which gets
traversed.
So if I feed 'foo bar' to mkisofs, it will process foo (and put
foo/file.dat on the CD). When encountering bar, it will --again--
process foo, and (currently) die with a directory loop error.
Eliminating this error does not change the fact that the directory gets
stored twice.
What I need is a way to prevent it from being considered a pathspec.
-- Johan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
