I have also run into this issue. In my case I "fixed" it by removing the
(not in current use) software package that had installed the symbolic link
that was causing the problem. I am quite certain the problem will recur at
some point in the future, however, in a case where I can't just do that.
In other words, I'd be very interested in a solution to this as well. Being
able to have a pathspec that is a symbolic link be treated as one would be a
Good Thing.
-Mark Bartel
-----Original Message-----
From: Johan Vromans [mailto:[EMAIL PROTECTED]]
Sent: April 5, 2001 11:52 AM
To: [EMAIL PROTECTED]
Subject: Directory loop
When processing a large list of files (25008 files) with
mkisofs -o /spare1/tmp/xx.iso -r -J -path-list /spare1/tmp/xx .dummy
I get
Warning: Directory loop (authors/id/ILYAZ/os2/5.005_53+/modules dev: 814
ino: 145915).
and an immediate exit.
A "find . -ls" reveals that there is exactly one entry on the file system
with the indicated inode.
I suspect this problem to come from a symbolic link in the path list
file. The mkisofs documentation reads that the path list file contains
pathspecs, indicating that an entry that is a symbolic link pointing
to a directory is processed as a directory, instead of being stored as
a symlink.
Any suggestions how to overcome this 'feature'?
This is mkisofs 1.14a18 (i686-pc-linux-gnu).
-- Johan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
