In my scenario, the .iso being created is a backup image. A program creates
-path-list files by iterating the specified directory, splitting any
directories larger than 650Mb, and fitting all the resulting directories and
files into as few cds as possible. Mkisofs is then run with -path-list
${file} for each file. With this workaround, the program would have to
create appropriate single-symlink dirs when it was run, and then somehow the
symlink dirs get deleted after mkisofs is run.
Well, it is of course doable, but it would be easier and orders of magnitude
more elegant to have something like a -no-traverse-symlinks option.
-Mark
-----Original Message-----
From: James Pearson [mailto:[EMAIL PROTECTED]]
Sent: April 6, 2001 2:07 PM
To: Johan Vromans
Cc: [EMAIL PROTECTED]
Subject: Re: File lists
>What I need is a way to prevent it from being considered a pathspec.
I finally understand ...
The only work round I can think of is to create a directory that contains
just you link(s) and use this directory as one of the pathspecs e.g:
mkdir /tmp/dummy
cd /tmp/dummy
ln -s foo bar
mkisofs ... -r -graft-points /foo/=foo /tmp/dummy
Symlinks to directories as pathspecs, by design are traversed...
James Pearson
--
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]
