lndir - create a shadow directory of symbolic links to another directory
lndir [-e exceptfile] [-s] [-i] fromdir [todir]
The lndir program makes a shadow copy todir of a directory
except that the shadow is not populated with real files but
symbolic links pointing at the real files in the fromdir directory tree.
This is usually useful for maintaining source code for different machine
architectures. You create a shadow directory containing
links to the real
source, which you will have usually mounted from a remote
You can build in the shadow tree, and the object files will
be in the
shadow directory, while the source files in the shadow directory are just
symlinks to the real files.
This scheme has the advantage that if you update the source,
you need not
propagate the change to the other architectures by hand,
since all source
in all shadow directories are symlinks to the real thing:
just cd to the
shadow directory and recompile away.
The todir argument is optional and defaults to the current
The fromdir argument may be relative (e.g., ../src) and is
todir (not the current directory).
Note that RCS, SCCS, CVS and CVS.adm directories are not
shadowed, in addition
to any specified on the command line with -e arguments.
If you add files, simply run lndir again. New files will be
added. Old files will be checked that they have the correct
Deleting files is a more painful problem; the symlinks will
into never never land.
If a file in fromdir is a symbolic link, lndir will make the
same link in
todir rather than making a link back to the (symbolic link)
fromdir. The -i flag changes this behavior.
The options are as follows:
Add the specified file to the list of excluded
This is effective in all directories searched by
lndir. This option
may be specified as many times as needed.
-s Suppresses status messages normally output as lndir
-i Causes the program to not treat symbolic links in
The link created in todir will point back
to the corresponding
(symbolic link) file in fromdir. If the
link is to a
directory, this is almost certainly the wrong thing.
This option exists mostly to emulate the behavior
the C version
of lndir had in X11R6. Its use is not recommended.
The program displays the name of each subdirectory it enters, followed by
a colon. The -s option suppresses these messages.
A warning message is displayed if the symbolic link cannot
The usual problem is that a regular file of the same name
If the link already exists but doesn't point to the correct
program prints the link name and the location where it does
find(1), ln(1), patch(1)
lndir was first distributed as part of X11.
This version first appeared in OpenBSD 1.2.
The patch(1) program gets upset if it cannot change the
should never run patch(1) from a shadow directory anyway.
You need to use something like
$ find todir -type l -print | xargs rm
to clear out all files before you can relink (if fromdir
moved, for instance).
$ find . -type d -print
will find all files that are not directories.
OpenBSD 3.6 June 21, 1997
[ Back ]