Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!lll-winken.llnl.gov!noc.near.net!news.mathworks.com!tank.news.pipex.net!pipex!in2.uu.net!news1.digital.com!nntp-hub2.barrnet.net!pacbell.com!jima!jeapeda From: jeapeda@jima.esac.pacbell.com (Jim Apedaile) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: Shell Programming Date: 24 Aug 1995 23:32:45 GMT Organization: Pacific Bell, ESAC Lines: 45 Message-ID: <41j26t$ke8@gw.PacBell.COM> References: <DDtHw6.IC2@freenet.carleton.ca% <DDtpx0.8oB@seas.ucla.edu% NNTP-Posting-Host: jima.esac.pacbell.com Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In article <DDtpx0.8oB@seas.ucla.edu%, Arthur D. Jerijian <jerijian@typhoon.seas.ucla.edu% wrote: %Tom Hill (ae263@FreeNet.Carleton.CA) wrote: ... %% For example, the followign test script clears the screen under Linux: %% #!/bin/bash %% clear %% But under BSD, the same script produces only the message "command not found". %% I'd appreciate hearing from anyone who can tell me what's happening here, and give me any other pointers on shell scripting with BSD. %% Thank-you % % It seems that the bash shell interpreter doesn't come with BSDI %by default. I've never used BSDI, but I am pretty sure that you will %have no trouble compiling bash. Just get the source code from any site %that carries GNU utilities, like prep.ai.mit.edu:/pub/gnu . In the %meantime, you can use the Bourne shell (sh), although it is much more %limited than bash. For example, this sh script will clear the screen: % %#!/bin/sh %clear % % I hope this helps. % % %--Arthur Jerijian jerijian@aixugrad.seas.ucla.edu % Sorry, but BSDI comes with: /bin/bash /bin/csh /bin/ksh /bin/sh /bin/tcsh /bin/zsh The orig article didn't say which command wasn't found. If it is the clear command then /usr/bin isn't in the PATH, if it's the shell script that contains the clear command then the shell script isn't in the path or the permissions are wrong. Try ./script if that works then the current directory is not in your PATH. -- Jim Apedaile jeapeda@PacBell.COM