Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2246 ; Mon, 01 Mar 93 10:50:51 EST Xref: sserve comp.os.386bsd.development:44 comp.os.386bsd.bugs:27 Newsgroups: comp.os.386bsd.development,comp.os.386bsd.bugs Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!paladin.american.edu!news.univie.ac.at!hp4at!mcsun!ieunet!dec4ie.ieunet.ie!jkh From: jkh@whisker.lotus.ie (Jordan K. Hubbard) Subject: Re: Is fixing /bin/sh worthwhile? In-Reply-To: nate@cs.montana.edu's message of Wed, 24 Feb 1993 17: 57:56 GMT Message-ID: <JKH.93Feb25235439@whisker.lotus.ie> Sender: usenet@ieunet.ie (USENET News System) Nntp-Posting-Host: whisker.lotus.ie Organization: Lotus Development Ireland References: <CONKLIN.93Feb23174603@talisman.kaleida.com> <1993Feb24.175756.7398@coe.montana.edu> Date: Thu, 25 Feb 1993 23:54:39 GMT Lines: 12 I agree - let's fix ash. Look at it this way: It would be good to have a working "minimal" /bin/sh, just the way a commercial unix system would. The principle of least surprise will not hold if someone suddenly finds his single-user root shell has emacs command history! :-) Seriously, I think it's a good idea. Jordan -- Jordan Hubbard Lotus Development Ireland jkh@whisker.lotus.ie 386bsd Patchkit Coordinator All-around nice dude. I do not speak for Lotus as that's not in my job description.