From owner-freebsd-current Mon Oct 26 16:34:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14713 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:34:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14707 for ; Mon, 26 Oct 1998 16:34:40 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA27973; Mon, 26 Oct 1998 19:33:22 -0500 (EST) Date: Mon, 26 Oct 1998 19:33:22 -0500 (EST) From: Brian Feldman To: Terry Lambert cc: Studded , dag-erli@ifi.uio.no, current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <199810270023.RAA29067@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I'll try and answer as many of those as possible in one shot: License: Public Domain (hence PDKSH). VERY BSD-friendly! :) Compatibility with /bin/sh: hasn't broken one single script size of binary (static ELF): text data bss dec hex filename 302081 10088 36588 348757 55255 /bin/sh 283681 5496 37692 326869 4fcd5 /bin/ksh bmakeability: pdksh uses autoconf but its Makefile is bmake-compatible Image size: green 753 0.0 0.4 500 284 p2 Ss+ 7:31PM 0:00.03 ksh green 756 0.5 0.5 600 356 p3 Ss+ 7:31PM 0:00.04 sh Standards: /bin/sh is Bourne, with a few Korn features, pdksh has just about every Korn feature, and Korn shells by definition are backward-compatible with Bourne shells. That should be about all I can think of now. From a user perspective, pdksh has a better vi mode and tab-completion, so is a better interactive shell. Cheers, Brian Feldman On Tue, 27 Oct 1998, Terry Lambert wrote: > > > Why don't we just use pdksh? > > > > Oh dear. I've had in the back of my mind for a long time to suggest us > > replacing our pseudo-implementation of sh with Bash in posix mode, but I > > haven't made the suggestion because I can think of at least 3 holy wars > > that it would start right off hand, and I can guess that there are more > > I don't know about. :) > > Issues (not wars), in order of perceived importance: > > 1) License; /bin/sh is in the boot path > > 2) 100% bug compatability with existing /bin/sh > > 3) size in a "crunched" boot floppy > > 4) size in general > > a) image size > b) memory footprint > > 5) standards compliance > > 6) All other compatability issues > > 7) All other preference issues > > 8) Blue. We'll paint the boxes blue. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message