Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!ox.com!yale.edu!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.admin
Subject: Re: Mysterious security hole
Message-ID: <25316.Jun2205.02.4391@kramden.acf.nyu.edu>
Date: 22 Jun 91 05:02:43 GMT
References: <12714@bsu-cs.bsu.edu> <MSH-XC+@cs.widener.edu> <1991Jun18.165128.10031@iWarp.intel.com>
Organization: IR
Lines: 17

In article <1991Jun18.165128.10031@iWarp.intel.com> merlyn@iWarp.intel.com (Randal L. Schwartz) writes:
> In article <MSH-XC+@cs.widener.edu>, brendan@cs (Brendan Kehoe) writes:
  [ on not having . in $PATH ]
> |  It took some getting used to, but after about a month I got myself
> | into the pattern of doing this .. and have found it completely
> | impossible to revert back. :)
> I've been doing this for over three years, even with my "everyday"
> account.

Ditto. Usually when I find broken Makefiles and scripts I go to the
trouble of fixing them and complaining to the author. For programming,
putting ./ before programs in the current directory is hardly a burden,
and when I want a program in my PATH it's because I want to use it from
any directory---not just the current one. So I ln -s home/foo/program
~/LINKS, with ~/LINKS in my path.

---Dan