Article View: comp.bugs.4bsd
Article #1095Re: Hard Links between UNIX Utility Programs
From: Chuck Karish
Date: Wed, 27 Jul 1988 01:02
Date: Wed, 27 Jul 1988 01:02
17 lines
1478 bytes
1478 bytes
In article <184@chip.UUCP> mparker@chip.UUCP (M. D. Parker) writes:
>I have noticed the tendency for some programs in UNIX to have hard links.
>The program operation is then determined by the name it was invoked by.
>As a system administrator this makes it very difficult for me to restrict
>one program without restricting all their linked set.
Why don't you just remove one of the links, and make a second copy of
the program?
The remaining administrative problem is keeping track of which programs
need to be copied this way when a new version of the operating system is
installed. The installation log files (``tar v'' output) tell you
when links are made, as opposed to actual file extractions.
Chuck Karish ARPA: karish@denali.stanford.edu
BITNET: karish%denali@forsythe.stanford.edu
UUCP: {decvax,hplabs!hpda}!mindcrf!karish
USPS: 1825 California St. #5 Mountain View, CA 94041
Technical Details
Message-ID:
<23166@labrea.Stanford.EDU>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!rutgers!gatech!purdue!decwrl!ucbvax!agate!labrea!denali!karishReferences:
<184@chip.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!rutgers!gatech!purdue!decwrl!ucbvax!agate!labrea!denali!karish From: karish@denali.stanford.edu (Chuck Karish) Newsgroups: comp.bugs.4bsd,comp.bugs.misc,comp.bugs.sys5 Subject: Re: Hard Links between UNIX Utility Programs Keywords: unix links bsd sysv sys5 Message-ID: <23166@labrea.Stanford.EDU> Date: 27 Jul 88 01:02:00 GMT References: <184@chip.UUCP> Sender: news@labrea.Stanford.EDU Reply-To: karish@denali.stanford.edu (Chuck Karish) Organization: Mindcraft, Inc. Lines: 16