From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] grid setup procedure
Date: Mon, 21 Aug 2006 09:10:13 -0700 [thread overview]
Message-ID: <3e1162e60608210910y1a602901ub22335c118c44a42@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0608210843k11736738ib581f7f5208dc567@mail.gmail.com>
On 8/21/06, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> On 8/21/06, John Floren <slawmaster@gmail.com> wrote:
> >
> > If I wanted to make a setup similar to 9grid.de, for instance, or any
> > other site that has machines dedicated to file serving or auth or cpu,
> > do I install a file server after doing my standalone server, then have
> > the standalone boot from the file server?
>
> Probably the best bet is to setup your standalone system to boot other
> systems, then boot a separate cpu/auth server and any terminals you
> like. You can then configure your original standalone as purely a
> file server. When I had my 9grid running, I had a file server and a
> cpu server and configured them to point to sources as auth (so anyone
> with a sources account could log into my cpu server). Instead of
> booting a separate terminal, I just used drawterm to the cpu server.
>
> > I suppose the thing to do is
> > email some of the people who have done this.
>
> That's not a bad idea - of course, they should all be on this list.
>
> -eric
>
I personally just run a cpu/fs/auth machine and have a parallels
terminal/fs as well. I typically use parallels these days though, as
drawterm's "yellow problem" is quite irritating.
Anyone have a solution to that?
Dave
next prev parent reply other threads:[~2006-08-21 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 17:49 John Floren
2006-08-20 21:08 ` Eric Van Hensbergen
2006-08-21 14:13 ` John Floren
2006-08-21 15:43 ` Eric Van Hensbergen
2006-08-21 16:10 ` David Leimbach [this message]
2006-08-22 14:39 ` [9fans] exit message arisawa
2006-08-22 14:45 ` erik quanstrom
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=3e1162e60608210910y1a602901ub22335c118c44a42@mail.gmail.com \
--to=leimy2k@gmail.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).