The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Ninth Edition incomplete?
Date: Fri, 31 Mar 2017 23:43:58 -0600	[thread overview]
Message-ID: <CANCZdfqkcoGn50WNLaSDUG3oObLK=-FVpE_wD9jOCwwRR_xjsA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NDV1+L-ecuSVv-4B6=ZRLYxowST572t-JxcR4CTExY6A@mail.gmail.com>

On Fri, Mar 31, 2017 at 1:53 PM, Clem Cole <clemc at ccc.com> wrote:
>
> On Fri, Mar 31, 2017 at 3:16 PM, Norman Wilson <norman at oclsc.org> wrote:
>>
>> The 10/e manual came out in early 1990.  It happened
>> because enough of us wanted to have a current manual
>> again,
>
> Well thank you!    I was on a trip and had stopped into a book store in
> Cambridge, UK shortly after it was published and realized I was not going to
> see it in the US anytime soon and certainly not in industry which is where I
> was by then.   I said, hmmm, I better buy that while I can. So, I did, and
> it has lived for years on my shelf in the basement.
>
> Nice to have the official doc and the bits now too ;-)

It's starting to look like we need to reconstruct v8, v9 and v10 to
varying degrees based on when snapshots were taken...

Warner


  reply	other threads:[~2017-04-01  5:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 19:16 Norman Wilson
2017-03-31 19:53 ` Clem Cole
2017-04-01  5:43   ` Warner Losh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-05 16:08 Norman Wilson
2017-04-04 21:01 Norman Wilson
2017-04-05  9:39 ` Joerg Schilling
2017-04-01 14:09 Doug McIlroy
2017-04-03 17:27 ` Joerg Schilling
2017-04-04 13:07   ` Random832
2017-04-04 13:14     ` Joerg Schilling
2017-04-01 13:38 Doug McIlroy
2017-04-01 13:47 ` Jason Stevens
2017-04-01 14:27   ` Doug McIlroy
2017-04-01 15:39     ` Clem Cole
2017-03-31 15:34 Diomidis Spinellis
2017-04-01  0:40 ` Noel Hunt

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='CANCZdfqkcoGn50WNLaSDUG3oObLK=-FVpE_wD9jOCwwRR_xjsA@mail.gmail.com' \
    --to=imp@bsdimp.com \
    /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).