Xref: utzoo comp.bugs.4bsd:1100 comp.unix.questions:10299 comp.unix.wizards:12682
Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!think!eplunix!das
From: das@eplunix.UUCP (David Steffens)
Newsgroups: comp.bugs.4bsd,comp.unix.questions,comp.unix.wizards
Subject: Re: Bug/misfeature in 4bsd /bin/sh
Summary: v7 /bin/sh gets it worng, too!
Message-ID: <673@eplunix.UUCP>
Date: 20 Nov 88 19:33:32 GMT
References: <117@sickkids.UUCP> <474@auspex.UUCP>
Organization: Eaton-Peabody Lab, Boston, MA
Lines: 23

In article <117@sickkids.UUCP> mark@sickkids.UUCP (Mark Bartelt) says:
> All the non-Berkeley versions of UNIX I can get my hands on give:
>	3 2 3 1 2 1
> On the other hand, under 4.3bsd we're treated to the following:
>	1 1 2 1 2 1

In article <474@auspex.UUCP> guy@auspex.UUCP (Guy Harris) says:
> Did you try this under V7?  ...  If it does the wrong thing under V7,
> you may have made an incorrect assumption here ...
> It may, in fact, have been that AT&T *fixed* the behavior of the
> shell and *added* the comment in question.

Guy is correct -- an (almost) plain vanilla v7 /bin/sh gives:
	1 1 2 1 2 1

The system I used for testing is known as "v7m", an early release
of DEC's Ultrix-11.  The code is basically Bell v7 re-worked
to run on a non-splt I/D PDP11.  The /bin/sh binary is dated
5 May 1979 and derives from sources dated 12 Jan 1979.
-- 
{harvard,mit-eddie,think}!eplunix!das		David Allan Steffens
243 Charles St., Boston, MA 02114		Eaton-Peabody Laboratory
(617) 573-3748					Mass. Eye & Ear Infirmary