From owner-freebsd-current Sat Oct 31 07:38:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08599 for freebsd-current-outgoing; Sat, 31 Oct 1998 07:38:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08567 for ; Sat, 31 Oct 1998 07:37:57 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 0zZEdu-00004I-00; Fri, 30 Oct 1998 13:31:06 +0000 To: Mike Nguyen Cc: "Jeffrey J. Mountin" , current@FreeBSD.ORG, Brian Feldman Subject: Re: Changing sh for compatibility sake References: From: Dom Mitchell In-Reply-To: Mike Nguyen's message of "Tue, 27 Oct 1998 14:19:27 -0600 (CST)" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Fri, 30 Oct 1998 13:31:06 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Nguyen writes: > First thing I do when I install a new FreeBSD box is install the BSDi ksh > binaries from the AT&T software reuse website as /bin/ksh. A real ksh93, no > less. I haven't had the guts to replace /bin/sh with it yet (though the man > page does have a toggle to display either as sh(1) or ksh(1)). I wouldn't replace /bin/sh with ksh93... It is a *lot* bigger. It's practically a whole new shell, compared to ksh88. -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message