Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!netcom.com!stanb From: stanb@netcom.com (Stan Brown) Subject: Serious brain damage in /bin/sh for FreeBSD 2.1.5 Message-ID: <stanbE1M2D2.38I@netcom.com> Organization: NETCOM On-line Communication Services (408 261-4700 guest) X-Newsreader: NN version 6.5.0 #3 (NOV) Date: Fri, 29 Nov 1996 02:46:14 GMT Lines: 30 Sender: stanb@netcom2.netcom.com It's been a bad day. I am trying to posrt some user environment set up scripts to my FreeBSD machine. I use ksh, and after having probelms with the PD ksh suplied woht FreeBSD, I downlaoded the real version for Bell Labs. 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 /bin/sh tries to load what is pointed to by the $ENV variablke. It of course doesn't like the things in there which are in ksh synatx. No problem saya I, I'll just unset $ENV at the end of the .kshrc file (the one pointed to by the $ENV). This doesn't fix system scripts that exec /bin/sh with #!/bin/sh. OK I think I'll just put a test for $SHELL being set to basname ksh around my .kshrc. Well this doesn't work because when a /bin/sh script is invoked from a ksh script /bin/sh doesn;t bother to reset $SHELL (NOTE chs does reset this). I realize all Berkley centric people think the workd revolves around csh, but the rest of us don't. Seriously, whats the rationale behind this half hearted atempt at making /bin/sh look like ksh ? Is there some way that I can fix this ? -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1996 Stan Brown. Redistribution via the Microsoft Network is prohibited.