From: Ed <edbrown@mailbag.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] WORM recomendations?
Date: Tue, 16 Jan 2001 08:06:41 -0600 [thread overview]
Message-ID: <3A645571.2C0E55B5@mailbag.com> (raw)
I am tired of kfs. Time to move up.
Any suggestions for a low-end WORM?
It is for a basic three machine setup (one user).
next reply other threads:[~2001-01-16 14:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 14:06 Ed [this message]
2001-01-16 14:29 forsyth
2001-01-16 14:39 rob pike
2001-01-16 14:59 nigel
2001-01-16 17:52 ` Boyd Roberts
2001-01-16 22:06 ` William K. Josephson
2001-01-16 15:13 rob pike
2001-01-16 17:58 rob pike
2001-01-16 18:08 ` Boyd Roberts
2001-01-16 18:25 jmk
2001-01-16 19:18 Richard Miller
2001-01-17 3:07 ` Eric Dorman
2001-01-16 20:55 jmk
2001-01-17 1:52 okamoto
2001-01-17 2:04 ` Boyd Roberts
2001-01-18 16:12 ` Latchesar Ionkov
2001-01-18 20:35 ` Boyd Roberts
2001-01-18 20:55 ` Latchesar Ionkov
2001-01-18 21:00 ` Boyd Roberts
2001-01-17 2:15 okamoto
2001-01-17 4:16 rob pike
2001-01-17 4:55 okamoto
2001-01-18 21:08 Russ Cox
2001-01-18 22:07 ` Boyd Roberts
2001-01-18 22:08 ` Boyd Roberts
2001-01-18 22:29 ` Boyd Roberts
2001-01-18 23:10 ` matt heath
2001-01-18 23:17 ` Boyd Roberts
2001-01-18 23:24 ` Boyd Roberts
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=3A645571.2C0E55B5@mailbag.com \
--to=edbrown@mailbag.com \
--cc=9fans@cse.psu.edu \
/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).