From: blstuart@bellsouth.net
To: 9fans@9fans.net
Subject: Re: [9fans] file server?
Date: Thu, 13 Aug 2009 20:15:43 -0500 [thread overview]
Message-ID: <d9a5e6d2a10ce0e8831a3b97d28895c0@bellsouth.net> (raw)
In-Reply-To: <621112A569DAE948AD25CCDCF1C075331AB5F4@dolly.ntdom.cupdx>
> Once, it used to be the "standard" configuration to have one machine as a CPU/auth server, one machine as a file server, and one machine as a "terminal", for a total of three systems, if one had the available hardware.
The power in that model comes primarily when you have
a number of terminals being supported by the file and cpu/auth
servers. Throwing bigger disks on the file server gives everyone
more space. Upgrading the big honkin' cpu server gives everyone
a speed boost. Of course, these days, a $400 laptop is more
honkin' (in many ways) than big systems of just a few years
ago. Still the separation of functionality does have advantages.
But I digress...
> What's the "recommended" setup now? Are most people using a combined cpu/auth/file server running Fossil+Venti, or is the recommendation to use a seperate fossil+venti server dedicated to file serving, and another to serve as CPU/auth?
Currently, I'm running a combined file/cpu/auth server, and
I run 9vx in FreeBSD as a terminal connecting to my server.
While not mentioned often, 9vx has a -b option that allows
you to point it to a file server the same way a terminal does.
I can also cpu into the cpu server just like with a real terminal.
And when I'm away from home with my laptop, I can still
run 9vx with a local file system.
As soon as my supply of round tuits is replinished, I intend
to put a CPU server in place.
BLS
prev parent reply other threads:[~2009-08-14 1:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 0:30 Benjamin Huntsman
2009-08-14 0:55 ` andrey mirtchovski
2009-08-14 1:01 ` erik quanstrom
2009-08-14 1:23 ` John Floren
2009-08-14 2:00 ` erik quanstrom
2009-08-14 6:14 ` Lyndon Nerenberg
2009-08-14 8:45 ` Robert Raschke
2009-08-14 12:07 ` erik quanstrom
2009-08-14 12:44 ` Robert Raschke
2009-08-14 12:09 ` erik quanstrom
2009-08-16 2:12 ` Adrian Tritschler
2009-08-14 4:16 ` Lyndon Nerenberg
2009-08-14 1:09 ` Federico G. Benavento
2009-08-14 1:15 ` blstuart [this message]
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=d9a5e6d2a10ce0e8831a3b97d28895c0@bellsouth.net \
--to=blstuart@bellsouth.net \
--cc=9fans@9fans.net \
/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).