Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!pooh!chet From: chet@pooh.INS.CWRU.Edu (Chet Ramey) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Serious brain damage in /bin/sh for FreeBSD 2.1.5 Date: 2 Dec 1996 20:21:23 GMT Organization: Case Western Reserve University, Cleveland, Ohio, USA Lines: 22 Message-ID: <57vdo3$fg5@alexander.INS.CWRU.Edu> References: <stanbE1M2D2.38I@netcom.com> <57m6f4$2dl@uriah.heep.sax.de> <stanbE1nxGM.M0L@netcom.com> NNTP-Posting-Host: pooh.ins.cwru.edu In article <stanbE1nxGM.M0L@netcom.com>, Stan Brown <stanb@netcom.com> wrote: >j@uriah.heep.sax.de (J Wunsch) writes: > >>stanb@netcom.com (Stan Brown) wrote: > >>> Now I have more problems. The scripts assume that *only* ksh will >>> source a file pointed to by the $ENV variable. Well geuss what the FreeBSD > >>So these scripts are plain broken. They should not assume this. It's >>Posix-sanctioned to do it. > > Your mising the point. yes it's OK to do this *if* the shell doing it > is posix compliant. What's not OK, is doing this with a shell that > breaks badly on posix style consstructs. What `posix-style constructs' break the FreeBSD sh? Are you sure they really are POSIX and not ksh-specfic? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu