*BSD News Article 91803


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!newsxfer.itd.umich.edu!yale!oitnews.harvard.edu!fas-news.harvard.edu!giffin.student.harvard.edu!user
From: giffin@fas.harvard.edu (Daniel B Giffin)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.2-RELEASE problem (simple)
Date: Fri, 21 Mar 1997 11:36:07 -0500
Organization: Harvard University, Cambridge, Massachusetts
Lines: 15
Message-ID: <giffin-2103971136070001@giffin.student.harvard.edu>
References: <5grof3$138@bignews.shef.ac.uk> <33324C69.41C67EA6@teligent.se>
NNTP-Posting-Host: giffin.student.harvard.edu
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37471

In article <33324C69.41C67EA6@teligent.se>, Johan Lithander
<johan@teligent.se> wrote:

> You can add "current directory" to Your PATH environment variable:
> PATH=.:$PATH
> In this case the current directory will be "checked" first for the
> executable program that You entered at the prompt.

Although note this is deprecated as a permanent setting because it could
produce other than the desired effect if someone has slipped an
appropriately-named executable where you don't expect it.  Especially as
root, either put the current directory at the *end* of your path (so the
"intended" command gets executed) or, better, don't include it at all.

daniel