Xref: utzoo comp.sys.pyramid:303 comp.unix.wizards:14325
Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!iuvax!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.sys.pyramid,comp.unix.wizards
Subject: Re: Is SVR2 /bin/sh backwards compatible to v7?
Message-ID: <9499@smoke.BRL.MIL>
Date: 24 Jan 89 22:07:52 GMT
References: <165@apmpyr.nzapmb.co.nz>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <165@apmpyr.nzapmb.co.nz> pgfdp@nzapmb.co.nz (Paul Fox ) writes:
>	Does anyone see a problem with simply _replacing_ the UCB /bin/sh
>	(i.e. the one called /.ucbbin/sh) with the AT&T shell (the one
>	called /.attbin/sh)?

The main problem you're likely to run into is that the System V sh
has "echo" built in, with different semantics.  In particular,
	echo 'main(){printf("Hello, world!\n");}' > foo.c
doesn't do what you might expect.  We tried the plug-replacement and
found that it broke a 4.2BSD kernel makefile.

You might consider getting the BRL-enhanced SVR2 Bourne shell, which
has the added advantage of supporting job control, EMACS-style command
history editing, etc.  It can be configured in a number of ways,
including 4.2BSD "echo" semantics, by simple edits in its Makefile.