Re: gsh question (dir exectution)

[voss@i40s16.ira.uka.de (Stefan Voss)]

In article <fmlinCDsGMv.KBL@netcom.com>, fmlin@netcom.com (Frank M. Lin) writes:
|> %dir
|> /src:
|> total 9k
|>    2 drw-brd 0000 DIR      1024 Sep 22 20:38 lpr
|>    1 drw-brd 0000 DIR       512 Sep 18 23:51 sun
|>    2 drw-brd 0000 DIR      1024 Sep 14 21:56 cs
|>    1 drw-brd 0000 DIR       512 Aug 20 22:33 whereis
|>    2 drw-brd 0000 DIR      1024 Aug  9 21:58 udl
|>    1 drw-brd 0000 DIR       512 Aug  5 23:03 toolbox.pascal
|>    1 drw-brd 0000 DIR       512 Aug  2 18:19 check.stack
|>    1 drw-brd 0000 DIR       512 Aug  2 18:19 synth.file
|>    1 drw-brd 0000 DIR       512 Jul 31 12:10 nic
|>    1 drw-brd 0000 DIR       512 Jul 27 11:16 pos.103
|>    1 drw-brd 0000 DIR       512 Jul 27 11:16 pos.110a6
|>    2 drw-brd 0000 DIR      1024 Jul 27 11:16 openany
|>    1 drw-brd 0000 DIR       512 Jul 27 11:16 cs105
|> 
|> Then I type /lpr, it gives command not found.  There is lpr command,
|> that's why I typed /lpr.  Is it normal to give the error?  Or should
|> it have cd into lpr?

1. "/lpr" trys to access an lpr file/directory at the root level. If you want to
   access to that lpr directory in /src, try "./lpr" or just "lpr" (assuming the
   prefix is set to /src). The "." means "current directory".
2. Your lpr is a *directory*, not an executable program. 

|> 
|> -- 
|> frank m. lin
|> fmlin@netcom.com

Stefan Voss
(voss@ira.uka.de)