1 .TH LNDIR 1 "Release 5" "X Version 11"
3 lndir \- create a shadow directory of symbolic links to another directory tree
13 except that the shadow is not
14 populated with real files but instead with symbolic links pointing at
17 directory tree. This is usually useful for maintaining source code for
18 different machine architectures. You create a shadow directory
19 containing links to the real source which you will have usually NFS
20 mounted from a machine of a different architecture, and then recompile
21 it. The object files will be in the shadow directory, while the
22 source files in the shadow directory are just symlinks to the real
25 This has the advantage that if you update the source, you need not
26 propagate the change to the other architectures by hand, since all
27 source in shadow directories are symlinks to the real thing: just cd
28 to the shadow directory and recompile away.
32 argument is optional and defaults to the current directory. The
34 argument may be relative (e.g., ../src) and is relative to
36 (not the current directory).
39 Note that RCS and SCCS directories are not shadowed.
42 Note that if you add files, you must run
44 again. Deleting files is a more painful problem; the symlinks will
45 just point into never never land.
48 gets upset if it cannot change the files. You should never run
50 from a shadow directory anyway.
52 You need to use something like
54 find todir -type l -print | xargs rm
56 to clear out all files before you can relink (if fromdir moved, for instance).
59 find . \\! -type d -print
61 will find all files that are not directories.