| Date Of Receipt: 18-MAY-1995 11:23:53.52
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 18-May-1995 1122"
To: Mike Daniele <daniele@DEC:.zko.flume>
CC: buildhelp@DEC:.zko.flume, odehelp@DEC:.zko.flume
Subj: Re: ILINKS
Mike, I don't know what you mean by "cloned files", however, my guess
is that you're expecting a symbolic link and getting a hard link. The
ILINKS directive is explicitly for creating hard links. Multiple files
that are hard linked together look like clones, but they have the same
inode; "ls -i" will list inodes and you can confirm that this is what
is happening. For example, ex and vi are really the same command,
hard linked:
% ls -il /usr/ucb/ex /usr/ucb/vi
4778 -rwxr-xr-t 5 bin bin 294912 Aug 8 1994 /usr/ucb/ex*
4778 -rwxr-xr-t 5 bin bin 294912 Aug 8 1994 /usr/ucb/vi*
^^^^-this is the inode#
To do symbolic links use SYMLINKS along with SYMLINKDIR1 and
SYMLINKDIR2; look in any pool under
src/usr/lib/makefiles/template.mk
for usage; there are examples in numerous makefiles, eg. usr/Makefile.
If you need more help, send mail to 'buildhelp' (cc'd).
-josh
--------
To: odeadmin
Cc: daniele
Subject: ILINKS
Date: Tue, 16 May 95 16:47:34 -0400
From: Mike Daniele <daniele>
X-Mts: smtp
Hi,
there seem to be several instances of makefiles
using ILINKS = ${IDIR}<linkname> where the intent is
to create link, NOT to clone the installed file.
But we really do get cloned files.
(nissetup, ntalkd, qutaoff, etc)
The man page states "used in conjunction with ILINKTO".
Does this mean there must be a <linkname>/Makefile that
uses ILINKTO in order for this to work?
Thanks,
Mike
|