Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site wang.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!wanginst!wang!rudy
From: rudy@wang.UUCP (Rudy Bazelmans x72609 ms 1989)
Newsgroups: net.unix-wizards
Subject: Re: Re: Please do NOT use "/bin/test" as a command name
Message-ID: <743@wang.UUCP>
Date: Wed, 11-Dec-85 08:15:11 EST
Article-I.D.: wang.743
Posted: Wed Dec 11 08:15:11 1985
Date-Received: Fri, 13-Dec-85 08:09:21 EST
References: <313@bdaemon.UUCP> <13400016@mirror.UUCP> <1016@sdcsla.UUCP> <1019@utcs.uucp> <11193@ucbvax.BERKELEY.EDU>
Organization: Wang Labs, Lowell MA
Lines: 15

> 	So, when writing programs/shell scripts which call other programs
> do include full path names, preferrably in a place where they are easily
> found and can be easily modified (e.g. ".h" files).
> 
> 						Ilya	(...!ucbvax!ilya)

Users should NOT use full directory names in their scripts/programs UNLESS:

	1)	They specifically do not want the local version of a program.
	2)	They are writing setuid scripts (actually, this would be alright too if
		the script changed the path variable).

If users use fullly qualified pathnames for programs, then administrators of
systems would have to replace the standard programs with the new ones rather
than allow both to be available.