From: arnold@skeeve.com
To: tuhs@tuhs.org, norman@oclsc.org
Subject: Re: [TUHS] Lions notes, early history
Date: Mon, 02 Nov 2020 10:16:18 -0700 [thread overview]
Message-ID: <202011021716.0A2HGIeg005278@freefriends.org> (raw)
In-Reply-To: <20201102162553.D5D884422E@lignose.oclsc.org>
The 1996 reprint is available:
https://www.amazon.com/Lions-Commentary-Unix-John/dp/1573980137/ref=sr_1_1?crid=4GU9QHV2HJM&dchild=1&keywords=john+lions+unix&qid=1604337238&sprefix=john+lions%2Caps%2C295&sr=8-1
next prev parent reply other threads:[~2020-11-02 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 16:25 Norman Wilson
2020-11-02 17:16 ` arnold [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-02 5:07 Greg 'groggy' Lehey
2020-11-02 5:21 ` Warner Losh
2020-11-02 9:51 ` Warren Toomey
2020-11-02 10:26 ` Ed Bradford
2020-11-02 11:04 ` arnold
2020-11-03 1:16 ` Greg 'groggy' Lehey
2020-11-02 7:21 ` Andrew Hume
2020-11-02 7:59 ` David Arnold
2020-11-02 14:26 ` Clem Cole
2020-11-02 21:17 ` Dave Horsfall
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=202011021716.0A2HGIeg005278@freefriends.org \
--to=arnold@skeeve.com \
--cc=norman@oclsc.org \
--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).