Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!unmvax!uokmax!vlstemen
From: vlstemen@uokmax.uucp (Vincent Lyle Stemen)
Newsgroups: comp.os.minix
Subject: Re: 'xxx: not found' when running xxx (159)
Message-ID: <1990May6.114406.10840@uokmax.uucp>
Date: 6 May 90 11:44:06 GMT
References: <371@cancol.oz>
Organization: Engineering Computer Network, University of Oklahoma, Norman, OK
Lines: 24

In article <371@cancol.oz> eyal@cancol.oz (Eyal Lebedinsky) writes:

>I have 1.5.9 going fine, but when I try to run a program from its own dir, I get
>'not found'. e.g., trying to run 'build' when I am in the 'tools' gets
>'build: not found'. If I try './build ...' then it works.
>
>I added my '/usr/local' to the PATH, is there a possibility that if there is
>a problem when scanning the PATH then the program will not be found? I think
>that the current dir is scanned first, right?
>

The earlier versions of Minix searched the current working directory for
commands automatically without having to specify it in the path.  I
believe this inherent to version 7 UNIX .  Although I have not yet run
Minix 1.5, it sounds like Minix has been changed to be more like system 5
UNIX in this respect.  Try adding '.' to your PATH list. 
Example:  
	  PATH=.:/bin    should search current working directory and
                     then search /bin.

-- 
--------
MSDOS --> MicroShafts Distribution Of S...
--------                                           vlstemen@uokmax.UUCP