From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] To virtualise cpu/fs/auth-servers, or not?
Date: Thu, 16 Apr 2009 16:30:00 -0400 [thread overview]
Message-ID: <cb781342a3d1ba6653c70ccfd0aa4d87@quanstro.net> (raw)
In-Reply-To: <49E78FA9.7080206@home.se>
> The plan9-way seems to be to divide the tasks
> of running programs, storing files, authenti-
> cation and user interaction, to separate
> servers or computers. This makes sense in
> a large system with many users, but does it
> also have appeal in a system with at most a
> couple of users (mostly me)?
>
[...]
>
> Up till now, I have been drawterming to
> an all-in-one cpu/fs/auth-server. Nothing
> very demanding, really. More out for a
> philosophical discussion.
i find it's very useful to seperate the fs from
everything else. since i run ken's fs, i don't
have a choice. even if i did, it's really a good
idea to not allow any of the problems devon's
pointing out (or normal bugs) torpedo your
fs.
with vms and fossil/venti, you may pay a performance
penalty for this. i don't know.
- erik
next prev parent reply other threads:[~2009-04-16 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 20:06 Jonas Amoson
2009-04-16 20:30 ` erik quanstrom [this message]
2009-04-16 23:04 ` andrey mirtchovski
2009-04-17 2:33 ` erik quanstrom
2009-04-17 2:49 ` andrey mirtchovski
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=cb781342a3d1ba6653c70ccfd0aa4d87@quanstro.net \
--to=quanstro@quanstro.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).