From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] standalone cpu server wiki
Date: Fri, 23 Jan 2004 06:52:58 -0500 [thread overview]
Message-ID: <46c0fd119ea9c2b3f5afb8981405d642@9srv.net> (raw)
In-Reply-To: <12D8FB09-4D61-11D8-8A73-000A95E29604@nas.com>
back in the 3ed days (actually pre-3e, bra[sz]il days), when i first
got my terminal at home i booted it over 128k ISDN from work. booting
took forever. once up, the system was useable, although the lag was
noticeable enough to be sometimes annoying. the biggest problem was
reliability. given that the most intensive activity came durring boot
time, it would often fail durring that. we eventually went with a
local kfs for home terminals, and mounting the file server and doing
appropriate namespace tricks. the reliability was still less than
great, and failures were pretty much total ("recover" never did),
but they were infrequent, anyway. i ended up writting some simple
scripts to keep the file system in sync, before replica or tra
existed (*much* simpler: i assumed the local stuff could be blown
away if there were differences).
i've subsequently done about the same thing over ~300k and ~1m
links. they're both quite usable, and the reliability issues
(assuming roughly constant latancy and physical-level reliability)
start to pretty much go away around 300k. i personally consider 1m
the borderline of what's comfortable.
ア
next prev parent reply other threads:[~2004-01-23 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 1:53 James Horey
2004-01-22 2:20 ` mirtchov
2004-01-22 8:27 ` vdharani
2004-01-22 5:58 ` mirtchov
2004-01-22 21:00 ` vdharani
2004-01-23 5:00 ` Jack Johnson
2004-01-23 5:33 ` mirtchov
2004-01-23 11:52 ` a [this message]
2004-01-22 16:27 ` David Presotto
2004-01-22 21:19 ` vdharani
2004-01-22 19:13 ` David Presotto
2004-01-22 19:14 ` David Presotto
2004-01-23 2:02 ` James Horey
2004-01-23 2:27 ` okamoto
2004-01-23 5:17 ` Jack Johnson
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=46c0fd119ea9c2b3f5afb8981405d642@9srv.net \
--to=a@9srv.net \
--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).