From: tfb@tfeb.org (Tim Bradshaw)
Subject: Old (7th ed 32v?) manuals
Date: Fri, 2 Apr 1999 09:03:23 +0100 (BST) [thread overview]
Message-ID: <199904020803.JAA15445@lostwithiel.tfeb.org> (raw)
I have a set of printed (decent quality) manuals which were
distributed with 32bit machines (HLH Orions) which ran BSD in later
life (I have BSD manuals for them). These ones must be from some
early port of <something>, perhaps 32v or I'm not sure what. They're
dated 1979 and seem to describe some definitely pre-BSD Unix. As you
can probably tell I haven't been through them in detail or I'd have
more info.
I don't really want them as they're 4 folders which don't actually
define any system I have (unless I succeed in finding a free PDP11 of
reasonable physical size in the UK...) and really I have too much
stuff already... But it seems a shame to just throw them out. Is it
worth trying to preserve such things? Could anyone offer them a home.
I can post them in the UK, and abroad if it's not too savagely
expensive.
--tim
reply other threads:[~1999-04-02 8:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199904020803.JAA15445@lostwithiel.tfeb.org \
--to=tfb@tfeb.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).