diff options
author | jim <empty> | 1989-10-20 08:35:04 +0000 |
---|---|---|
committer | jim <empty> | 1989-10-20 08:35:04 +0000 |
commit | 42facd80aee57e5a8b1ff5140dbdb78c5a2fb412 (patch) | |
tree | 32cd2e1e6bde1ff947995c504106f563de6efc55 /xc/config | |
parent | a8c97ca5ae0103c218a8002ded0646765666e9f9 (diff) |
Initial revision
Diffstat (limited to 'xc/config')
-rw-r--r-- | xc/config/util/lndir.man | 60 | ||||
-rw-r--r-- | xc/config/util/mkdirhier.man | 15 |
2 files changed, 75 insertions, 0 deletions
diff --git a/xc/config/util/lndir.man b/xc/config/util/lndir.man new file mode 100644 index 000000000..7b95e6a8b --- /dev/null +++ b/xc/config/util/lndir.man @@ -0,0 +1,60 @@ +.TH LNDIR L +.SH NAME +lndir - create a shadow directory of symbolic links to another directory tree. +.SH SYNOPSIS +.B lndir +fromdir todir +.SH DESCRIPTION +.I Lndir +makes a shadow copy +.I todir +of a directory tree +.I fromdir, +except that the shadow is not +populated with real files but instead with symbolic links pointing at +the real files in the +.I 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 NFS +mounted from a machine of a different architecture, and then recompile +it. The object files will be in the shadow directory, while the +source files in the shadow directory are just symlinks to the real +files. +.PP +.ft B +Note that RCS directories are not shadowed - they are symlinks to the +real RCS directories. +.ft +.PP +This 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 shadow directories are symlinks to the real thing - just cd +to the shadow directory and recompile away. +.PP +Ignore the diagnostics it generates about files already existing when +it runs - those are the directories which it are real, and are created +before the symlinking. +.PP +Note that if you add files, you must run +.I lndir +again. Deleting files is a more painful problem - the symlinks will +just point into never never land. +.SH ORIGIN +From the X11R2 distribution. +.SH BUGS +You can write through symlinks and clobber the files sometimes. Strict +RCS locking can prevent this. +.sp 1 +patch gets upset if it cannot change the files. +.sp 1 +You need to use something like +.nf + find todir -type l -print | xargs rm +.fi +to clear out all files before you can relink. (If fromdir moved, for instance) +Something like +.nf + find . \\! -type d -print +.fi +will find all files that are not directories. diff --git a/xc/config/util/mkdirhier.man b/xc/config/util/mkdirhier.man new file mode 100644 index 000000000..574083a2e --- /dev/null +++ b/xc/config/util/mkdirhier.man @@ -0,0 +1,15 @@ +.TH MKDIRHIER 1 "26 October 1988" "X Version 11" +.SH NAME +mkdirhier \- makes a directory hierarchy +.SH SYNOPSIS +.B mkdirhier +directory ... +.SH DESCRIPTION +The +.I mkdirhier +command creates the specified directories. Unlike +.I mkdir +if any of the parent directories of the specified directory +do not exist, it creates them as well. +.SH "SEE ALSO" +mkdir(1) |