From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: Warren Toomey <wkt@tuhs.org>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Poll: good location for Unix documentation?
Date: Sun, 29 Sep 2019 08:25:20 +0000 (UTC) [thread overview]
Message-ID: <ADFDF14544A65F35.821b4786-c942-4523-9b18-24b03c8fe5ab@mail.outlook.com> (raw)
In-Reply-To: <20190928020230.GB18235@minnie.tuhs.org>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Gunkies.org is a wiki that is really good for pointing to stuff, and things like tutorials, indexes and other non original stuff.
Archive.org is a great dumping ground for stuff, although it's easy to get lost in the shuffle.
I'm not an admin on gunkies.org but I do get my email at least answered, so if you have no luck trying to create an account I'll bug the owner to make it happen.
When I had more spare time I tried to seed gunkies with as much as I could.
Get Outlook for Android
On Sat, Sep 28, 2019 at 11:03 AM +0900, "Warren Toomey" <wkt@tuhs.org> wrote:
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, and have
recommendations?
Cheers, Warren
[-- Attachment #2: Type: text/html, Size: 2058 bytes --]
next prev parent reply other threads:[~2019-09-29 8:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-09-29 8:52 ` SPC
2019-09-29 18:53 Noel Chiappa
2019-09-29 20:11 ` Brian L. Stuart
2019-09-29 20:23 ` Clem Cole
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
2019-09-29 21:54 Noel Chiappa
2019-09-29 23:03 ` Brian L. Stuart
2019-09-30 1:13 ` Warner Losh
2019-09-30 21:41 Noel Chiappa
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=ADFDF14544A65F35.821b4786-c942-4523-9b18-24b03c8fe5ab@mail.outlook.com \
--to=jsteve@superglobalmegacorp.com \
--cc=tuhs@minnie.tuhs.org \
--cc=wkt@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).