From owner-freebsd-current Sun Oct 25 07:49:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22410 for freebsd-current-outgoing; Sun, 25 Oct 1998 07:49:15 -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 HAA22405 for ; Sun, 25 Oct 1998 07:49:11 -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 KAA22909; Sun, 25 Oct 1998 10:48:23 -0500 (EST) Date: Sun, 25 Oct 1998 10:48:22 -0500 (EST) From: Brian Feldman To: Chuck Robey cc: Studded , "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion: ksh testing In-Reply-To: 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, all the rc(5) scripts work flawlessly! :) All my user scripts work flawlessly, GNU configure works flawlessly, and PERL5's config scripts work fine too. As a bonus, pdksh has better PS[1-4] support, and co-processes (blah |&). I'll be using pdksh as /bin/sh from now on, and if I run into any trouble, I'll let you know. {"/home/green"}$ l /bin/*sh* -r-xr-xr-x 1 root wheel 258328 Oct 19 01:37 /bin/csh -r-xr-xr-x 1 root wheel 297488 Oct 18 21:32 /bin/ksh lrwxr-xr-x 1 root wheel 3 Oct 25 10:39 /bin/sh -> ksh -r-xr-xr-x 1 root wheel 321120 Oct 19 01:37 /bin/sh.old {"/home/green"}$ what /bin/ksh | head -2 /bin/ksh: PD KSH v5.2.13 97/10/27 Cheers, Brian Feldman On Sun, 25 Oct 1998, Brian Feldman wrote: > IIRC, OpenBSD uses it... Anyway, by definition, the Korn shell is a > superset of the Bourne shell, so it's entirely backward-compatible. In > fact, I'll let you know in a few minutes, I'll replace /bin/sh with > /bin/ksh, reboot, and see how all the rc initialization works. I expect it > to work completely correctly, so if it doesn't, I'll be surprised :) So of > course, it should be 100% compatible, but I'll try a reboot with ksh in > place of sh, and I'll try a make world with ksh instead. More later. > > Cheers, > Brian Feldman > > P.S: NO, this is _nothing_ like Linux using BASH. BASH is horrible :P > > On Sun, 25 Oct 1998, Chuck Robey wrote: > > > On Sun, 25 Oct 1998, Brian Feldman wrote: > > > > > Why don't we just use pdksh? It's even more compact than our current > > > Bourne/partially-Korn shell, and has lots of great Korn shell features > > > everyone loves but sh doesn't have. > > > > Not being a pdksh user, well, I know YOU are aware of the importance of > > not breaking ANY sh scripts for users, whether they're part of our base > > or not, because sh is the shell everyone writes in for portability, and > > it mustn't ever be broken ... so, is pdksh 100% compatible with sh, at > > least upwardly? I mean wth NO changes to ANY sh script? > > > > Do buildworlds complete, with pdksh in place as the shell, instead of > > sh? > > > > I'm not against this per se, but those are pretty important hurdles to > > go over, and I'm wary. Give us a lecture on it. Making this change > > would be neat, if it's truly possible. > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > > (301) 220-2114 | and jaunt (NetBSD). > > ----------------------------+----------------------------------------------- > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message