9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 topology
Date: Thu, 13 Jan 2011 20:03:25 -0800	[thread overview]
Message-ID: <4D2FCB0D.6010800@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101132037030.4272@fryrpg-zna>

On 1/13/2011 7:42 PM, Duke Normandin wrote:
> On Thu, 13 Jan 2011, John Floren wrote:
>
>> At Thu, 13 Jan 2011 14:37:52 -0700 (MST),
>> Duke Normandin wrote:
>>> On Thu, 13 Jan 2011, John Floren wrote:
>>>
>>>> I think you mentioned in another message that you have a headless box
>>>> available; I recommend temporarily hooking that up to a monitor,
>>>> keyboard, and mouse, then installing a standalone cpu/auth/file server
>>>> on it. Once you're done, you can try using drawterm from Windows or
>>>> Linux or whatever you have to test the configuration.
>>> I just checked - it's a 166Mhz P-I with 98M RAM and 4.5G HDD. Made a
>>> good dedicated mail server. May not have enough gonads for a Plan 9
>>> server though.
>> That should do well enough for a basic Plan 9 cpu/auth/file server,
>> although you may wish to forgo Venti given the small RAM and drive.
> What is Venti again?
>
> [snip]
>

Venti is the archival storage for Plan 9. Basically, new files and
changes to files get written to the Fossil file system. If Venti exists,
those changes get written to Venti; Venti never deletes anything and
works on a rather cool block-coalescing system. I highly recommend
reading the paper.

On a system with a small disk, it's a good idea to go without Venti,
because of the space required. Fossil will then hold all your files,
meaning you don't get the daily snapshots, but you probably won't miss
those immediately--there's plenty of time to set up a system with a
bigger disk for Venti if you like Plan 9, or you could even add Venti
after the fact by sticking in another disk.

>> I've never bothered to install Plan 9 as a boot option on my desktops;
>> I prefer to leave them booted into Linux and connect via drawterm,
>> so as not to disturb my open applications.
> The more I think about it, and the more I understand what Plan9 is,
> the more I'm convinced that hanging a dedicated Plan9 box off my
> router, and connecting to it from anywhere inside the subnet, is the
> way to go.

That's really the best way, in my opinion.

>> On my old laptop, I kept a Plan 9 terminal install because that was
>> actually quite convenient, and I could boot using the server's root
>> from most anywhere.
> You must have had a dedicated server box as well, then?

I did until a few weeks ago, when I moved, yes.

John



  reply	other threads:[~2011-01-14  4:03 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 18:38 Duke Normandin
2011-01-13 18:48 ` dukeofperl
2011-01-13 18:50 ` David Leimbach
2011-01-13 19:16   ` Skip Tavakkolian
2011-01-13 19:31     ` Duke Normandin
2011-01-13 19:37       ` Jacob Todd
2011-01-13 19:44       ` Skip Tavakkolian
2011-01-13 20:08         ` Duke Normandin
2011-01-13 21:01           ` Tassilo Philipp
2011-01-13 21:39           ` Brian L. Stuart
2011-01-13 22:49             ` Duke Normandin
2011-01-14  3:27               ` blstuart
2011-01-14  4:02                 ` erik quanstrom
2011-01-14  4:18                   ` Duke Normandin
2011-01-14  4:04                 ` Duke Normandin
2011-01-14  0:00           ` Federico G. Benavento
2011-01-14  3:26             ` Duke Normandin
2011-01-13 19:46     ` Bakul Shah
2011-01-13 20:11       ` erik quanstrom
2011-01-13 19:40   ` Duke Normandin
2011-01-13 20:07     ` John Floren
2011-01-13 20:24       ` Duke Normandin
2011-01-13 20:40         ` John Floren
2011-01-13 21:37           ` Duke Normandin
2011-01-13 21:59             ` Brian L. Stuart
2011-01-13 22:32               ` Duke Normandin
2011-01-13 23:18             ` John Floren
2011-01-14  3:42               ` Duke Normandin
2011-01-14  4:03                 ` John Floren [this message]
2011-01-14  4:05                   ` erik quanstrom
2011-01-14  4:15                   ` Duke Normandin
2011-01-14  4:22                     ` John Floren
2011-01-14  4:31                       ` Duke Normandin
2011-01-14  4:35                         ` Jacob Todd
2011-01-14 17:51                         ` Bakul Shah
2011-01-14 17:54                           ` erik quanstrom
2011-01-14 18:14                             ` Bakul Shah
2011-01-14 19:13                               ` erik quanstrom
2011-01-14 19:24                                 ` Duke Normandin
2011-01-14 20:44                                 ` Bakul Shah
2011-01-14 18:15                             ` Charles Forsyth
2011-01-14 18:14                         ` Federico G. Benavento
2011-01-14 18:35                           ` Duke Normandin
2011-01-14 14:58 erik quanstrom
2011-01-14 17:14 ` Duke Normandin
2011-01-14 17:40   ` erik quanstrom
2011-01-14 18:58     ` Duke Normandin
2011-01-14 19:09       ` erik quanstrom
2011-01-14 19:23       ` Charles Forsyth
2011-01-14 19:22         ` Duke Normandin
2011-01-15  0:16           ` Charles Forsyth

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=4D2FCB0D.6010800@gmail.com \
    --to=slawmaster@gmail.com \
    --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).