From owner-freebsd-current  Sun Oct 25 07:39:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA21647
          for freebsd-current-outgoing; Sun, 25 Oct 1998 07:39:19 -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 HAA21614
          for <current@FreeBSD.ORG>; Sun, 25 Oct 1998 07:39:15 -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 KAA22777;
	Sun, 25 Oct 1998 10:38:33 -0500 (EST)
Date: Sun, 25 Oct 1998 10:38:33 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Chuck Robey <chuckr@mat.net>
cc: Studded <Studded@gorean.org>,
        "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" <dag-erli@ifi.uio.no>,
        current@FreeBSD.ORG
Subject: Re: sh and ~ expansion
In-Reply-To: <Pine.BSF.4.05.9810251002310.375-100000@picnic.mat.net>
Message-ID: <Pine.BSF.4.05.9810251035400.22721-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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