home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!gumby!destroyer!news.iastate.edu!aviator.cc.iastate.edu!michaelv
- From: michaelv@iastate.edu (Michael L. VanLoon)
- Subject: Re: Major Problems with 386bsd0.1 please read
- Message-ID: <michaelv.713741023@aviator.cc.iastate.edu>
- Sender: news@news.iastate.edu (USENET News System)
- Organization: Iowa State University, Ames IA
- References: <9208100044.AA09303@cs.utexas.edu> <1992Aug10.090201.601@cl.cam.ac.uk>
- Date: Thu, 13 Aug 1992 21:23:43 GMT
- Lines: 22
-
- In <1992Aug10.090201.601@cl.cam.ac.uk> qs101@cl.cam.ac.uk (Quentin Stafford-Fraser) writes:
- >In article <9208100044.AA09303@cs.utexas.edu>, STDN%MARIST@VM.MARIST.EDU
- >(Dan Newcombe) writes:
-
- >|> 4) cc: I compiled the following C program using cc -o test test.c
-
- >I have done this more than once, and I kick myself every time :-)
- >Test is a builtin command in almost every shell. It has different return
- >codes, but no output.
- >You can run your program using ./test, or some such.
-
- You can always find out which command is getting executed by typing:
- which <command>
-
- Trying 'which test' on this Ultrix system under tcsh tells me:
- /bin/test
-
- --
- ------------------------------------------------------------------------------
- Michael L. VanLoon Project Vincent Systems Staff
- michaelv@iastate.edu Iowa State University Computation Center
- ------------------------------------------------------------------------------
-