home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!rutgers!ub!galileo.cc.rochester.edu!ee.rochester.edu!moscom!tcm
- From: tcm@moscom.UUCP (Tom Maszerowski)
- Newsgroups: comp.os.os9
- Subject: Re: FAQ ?
- Summary: Check your PATH variable
- Keywords: use the PATH variable
- Message-ID: <3826@moscom.UUCP>
- Date: 25 Jul 92 00:56:54 GMT
- References: <1992Jul09.140452.828@chicco.sea.sublink.org> <1992Jul20.094659.10941@chicco.sea.sublink.org> <CwAerG@keihh.hanse.de>
- Reply-To: tcm@moscom.UUCP (Tom Maszerowski)
- Followup-To: comp.os.os9
- Organization: Moscom Corp., Pittsford, NY
- Lines: 24
-
- In article <1992Jul20.094659.10941@chicco.sea.sublink.org> ugo@chicco.sea.sublin
- k.org (Ugo Cei) writes:
-
- >... Every program I tried gives me the following error message:
-
- >Shell: can't execute "J". Error #000:216
-
- >What am I missing or doing wrong ? I put the executables in my CMDS
- >directory or in /dd/CMDS and give them execution and read permission,
- >but I can't understand what is going on.
-
- Check your PATH variable. The default OS-9 shell seems reluctant to
- execute an executable module unless it is either a) in your current
- execution directory (do a chx <dir> to set it) or b) in one of the
- directories in your PATH environment variable (do a printenv to
- see what PATH is set to and setenv to add your directory). The
- TOPS shell, sh, is more like the UN*X bourne shell in this regard
- and I recommend it. Still, has anyone tried porting the GNU bash
- shell to OS-9? It's mostly sh/ksh, with just a touch of the nicer
- features from csh.
- --
- Tom Maszerowski tcm@moscom.com
- {rit,tropix,ur-valhalla}!moscom!tcm
- DoD#1957 (1987 BMW K75s)
-