From: steve jenkin <sjenkin@canb.auug.org.au>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Has this been discussed on-list? How Unix changed Software.
Date: Wed, 7 Sep 2022 11:40:04 +1000 [thread overview]
Message-ID: <DF4161CD-6FFC-4957-9946-AEA1190B3DFA@canb.auug.org.au> (raw)
In-Reply-To: <CAKH6PiWDZ82ZuNZx7ytE1g0qVzQqE_7CE3XsfKaAGumAU8SG_w@mail.gmail.com>
Doug, Larry et al,
Thanks very much for the history - unaware of those stories/ facts.
I’ve scanned the 1989 Miller et al paper, will read properly soon.
The legacy of that paper is the extensive automatic testing now commonplace in large Open Software projects.
I wasn't clear in what I wrote. Have been immersed in early papers of teaching the kernel at UNSW :(
Reminds on this list precise terms matter: that “Unix” / UNIX (tm) and "the kernel" (+ version) are very different.
I meant the V5 / V6 kernel was ‘known defect free', hadn’t thought of Userland / utilities & libraries :(
From what I’ve read: distribution tapes, pre-USG, were created from the current copy of ’the system’ - not sure which machine that was, presumably one controlled by Ken.
Is that a reasonable statement, the kernel, pre-USG, had zero (known) Technical Debt when shipped?
I’ve read that Ken wrote the kernel with an eye to it being a coding exemplar.
Deliberately wrote consistent, high quality code.
Is that another mis-interpretation of mine?
regards
steve j
> On 7 Sep 2022, at 01:07, Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
>
>> (Research) Unix ... 'shipped' with zero known bugs.
>
> It wasn't a Utopia. Right from the start man pages reported BUGS,
> though many were infelicities, not implementation errors.
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
next prev parent reply other threads:[~2022-09-07 1:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 15:07 Douglas McIlroy
2022-09-06 17:13 ` Larry McVoy
2022-09-07 1:40 ` steve jenkin [this message]
2022-09-07 2:33 ` segaloco via TUHS
2022-09-07 4:08 ` Steve Jenkin
2022-09-07 13:08 ` Steffen Nurpmeso
2022-09-07 14:56 ` Larry McVoy
2022-09-07 21:27 ` Steve Jenkin
2022-09-07 22:36 ` Larry McVoy
2022-09-08 14:42 ` Paul Winalski
2022-09-08 15:02 ` Larry McVoy
2022-09-08 15:04 ` ron minnich
2022-09-08 15:52 ` Warner Losh
2022-09-08 16:47 ` Paul Winalski
2022-09-08 16:50 ` segaloco via TUHS
2022-09-08 17:58 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2022-09-06 19:04 Douglas McIlroy
2022-09-05 23:48 [TUHS] " steve jenkin
2022-09-06 16:09 ` [TUHS] " Marc Donner
2022-09-07 4:00 ` steve jenkin
2022-09-07 14:58 ` John Cowan
2022-09-07 17:13 ` Paul Winalski
2022-09-08 14:12 ` Paul Winalski
2022-09-07 5:15 ` steve jenkin
2022-09-07 13:20 ` Dan Cross
2022-09-07 13:52 ` Steve Nickolas
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=DF4161CD-6FFC-4957-9946-AEA1190B3DFA@canb.auug.org.au \
--to=sjenkin@canb.auug.org.au \
--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).