home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!uvaarpa!darwin.sura.net!udel!gatech!paladin.american.edu!auvm!NEXT1.ACS.UMN.EDU!STEVE
- X-Envelope-to: ADVISE-L%NDSUVM1.bitnet@KSUVM.KSU.EDU
- Content-transfer-encoding: 7BIT
- Message-ID: <9301281751.AA02049@next1.acs.umn.edu>
- Newsgroups: bit.listserv.advise-l
- Date: Thu, 28 Jan 1993 11:51:07 -0600
- Sender: User Services List <ADVISE-L@UGA.BITNET>
- From: Steve Barstad <steve@NEXT1.ACS.UMN.EDU>
- Subject: Re: what is /bin/sh
- Comments: To: User Services List <ADVISE-L%NDSUVM1.bitnet@KSUVM.KSU.EDU>
- Lines: 18
-
- It's a UNIX thing...
-
- Unix uses / instead of \ as subdirectory seperators.
-
- so...
- /bin is a subdir
- sh is an executable file
-
- sh is a lot like command.com, it defines what command line functions
- are avail.
-
- One will often see something like: %!/bin/sh at the top of 'batch'
- files. It tell Unix what command set to expect.
-
- There are also tsh & csh & many other flavors.
-
- Steve Barstad
- U of MN
-