From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Reorganising the Unix Archive?
Date: Sat, 18 Feb 2017 10:12:44 +1000 [thread overview]
Message-ID: <20170218001244.GB17910@minnie.tuhs.org> (raw)
Hi all, I think the current layout of the Unix Archive at
http://www.tuhs.org/Archive/ is starting to show its limitations as we get
more systems and artifacts that are not specifically PDP-11 and Vax.
I'm after some suggestions on how to reorganise the archive. Obviously
there are many ways to do this. Just off the top of my head, top level:
- Applications: things which run at user level
- Systems: things which have a kernel
- Documentation
- Tools: tools which can be used to deal with systems and files
Under Applications, several directories which hold specific things. If
useful, perhaps directories that collect similar things.
Under Systems, a set of directories for specific organisations (e.g. Research,
USL, BSD, Sun, DEC etc.). In each of these, directories for each system.
Under Documentation, several directories which hold specific things. If
useful, perhaps directories that collect similar things.
Under Tools, subdirectories for Disk, Tape, Emulators etc., then subdirs
for the specific tools.
Does this sound OK? Any refinements or alternate suggestions?
Cheers, Warren
next reply other threads:[~2017-02-18 0:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 0:12 Warren Toomey [this message]
2017-02-18 0:21 ` Warren Toomey
2017-02-18 0:40 ` Clem Cole
2017-02-18 1:09 ` Warren Toomey
2017-02-18 17:17 ` Random832
2017-02-18 3:30 Doug McIlroy
2017-02-18 4:40 ` Warren Toomey
2017-02-18 17:19 ` Random832
2017-02-18 18:49 Doug McIlroy
2017-02-19 0:12 Doug McIlroy
2017-02-20 1:48 ` William Corcoran
2017-02-20 2:33 ` Doug McIlroy
2017-02-20 2:52 ` Larry McVoy
2017-02-20 18:06 ` Joerg Schilling
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=20170218001244.GB17910@minnie.tuhs.org \
--to=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).