From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Poll: good location for Unix documentation?
Date: Sun, 29 Sep 2019 16:23:24 -0400 [thread overview]
Message-ID: <CAC20D2M+qj4RQvM1ZC9f93RCWKH24LB9id96F9cRUjZqJO83hA@mail.gmail.com> (raw)
In-Reply-To: <20190929185320.5902C18C088@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Sun, Sep 29, 2019 at 2:54 PM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
> > From: Warren Toomey
>
> > All, I'm just musing where is the best place to store Unix
> > documentation. My Unix Archive is really just a filesystem, so it's
> not
> > so good to capture and search metadata.
> > Is anybody using archive.org, gunkies or something else
>
> BitSavers seems to be the canonical location for old computer
> documentation.
>
I agree +1 BitSavers, but Warren you should keep your stuff. One-stop
shopping for UNIX archives is a good thing.
>
> The CHWiki (gunkies.org) isn't really the best place to put original
> documentation,
> but that's where I'd recommend putting meta-data. As for searching
> meta-data, are
> you speaking of something more powerful than Google?
>
> Noel
>
> PS: Speaking of old Unix documentation, I recently acquired a paper copy
> of the
> PDP-11 V6 Unix manual. Is that something I should scan? I don't know if you
> already have it (I know where to find sources in the archives, but I don't
> know where documentation scans live.)
>
What I personally have is impure, and I have not seen a complete one
elsewhere, so if you have a real manual, that is a good thing IMHO.
[-- Attachment #2: Type: text/html, Size: 2180 bytes --]
next prev parent reply other threads:[~2019-09-29 20:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 18:53 Noel Chiappa
2019-09-29 20:11 ` Brian L. Stuart
2019-09-29 20:23 ` Clem Cole [this message]
2019-09-29 21:34 ` Warren Toomey
2019-09-29 22:40 ` Dave Horsfall
2019-09-29 23:02 ` Earl Baugh
2019-10-07 18:38 ` Al Kossow
-- strict thread matches above, loose matches on Subject: below --
2019-09-30 21:41 Noel Chiappa
2019-09-29 21:54 Noel Chiappa
2019-09-29 23:03 ` Brian L. Stuart
2019-09-30 1:13 ` Warner Losh
2019-09-28 2:02 Warren Toomey
2019-09-28 2:10 ` Warren Toomey
2019-09-28 4:56 ` Lars Brinkhoff
2019-09-28 2:38 ` Adam Thornton
2019-09-29 8:25 ` Jason Stevens
2019-09-29 8:52 ` SPC
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=CAC20D2M+qj4RQvM1ZC9f93RCWKH24LB9id96F9cRUjZqJO83hA@mail.gmail.com \
--to=clemc@ccc.com \
--cc=jnc@mercury.lcs.mit.edu \
--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).