The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Clem Cole <clemc@ccc.com>
Cc: segaloco <segaloco@protonmail.com>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Re-implementations/Clean-Rooms et al.
Date: Thu, 8 Sep 2022 15:16:39 -0700	[thread overview]
Message-ID: <20220908221639.GR11929@mcvoy.com> (raw)
In-Reply-To: <CAC20D2Mqmg9uvVxPdGKJocceW8c22zz1sM0RobJTkbhF5ywi1w@mail.gmail.com>

On Thu, Sep 08, 2022 at 05:50:37PM -0400, Clem Cole wrote:
> > BSD is a different beast, as they were literally replacing the AT&T source
> > code before their eyes, so there isn't much argument that can be made for
> > 4.4BSD being a "clean-room" implementation of UNIX.
> 
> It was not a clean-room as Arthur defined it.   It was rewritten over time,
> which replaced AT&T's implementation.  Which is all that was ever claimed.

And it's a false claim.  Go look at the Bell Labs bmap() and the BSD
bmap(), the last time I looked they were bit for bit identical.

I looked there because I split bmap() into bmap_read() and bmap_write()
because the read path is trivial and the write path is quite a bit more
difficult (this was all for the work srk imagined, and I did, to get
rid of the rotational delays).  So I was pretty familiar with that
code path and as of about 20 years ago, well past 4.4BSD, bmap() was
unchanged from either v7 or 32v.

The weird thing is it isn't that hard to write something that would
walk the code and find other examples.  Nobody seemed to care.

  reply	other threads:[~2022-09-08 22:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 21:50 Clem Cole
2022-09-08 22:16 ` Larry McVoy [this message]
2022-09-08 22:26   ` Warner Losh
2022-09-08 22:28     ` Warner Losh
2022-09-08 23:30     ` Steve Nickolas
2022-09-08 23:42       ` Warner Losh
2022-09-09  0:05         ` Steve Nickolas
2022-09-09  0:17           ` Larry McVoy
2022-09-09  0:52             ` Steve Nickolas
2022-09-09  2:16               ` Larry McVoy
2022-09-08 23:34   ` Clem Cole
2022-09-08 22:17 ` Warner Losh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220908221639.GR11929@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=clemc@ccc.com \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).