9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Luke Evans <luke.evans@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Canonical way to configure permanent remote
Date: Tue, 11 Dec 2012 09:36:21 +0000	[thread overview]
Message-ID: <6cae90a8-e17e-4d72-9034-aa5158a6dc49@googlegroups.com> (raw)
In-Reply-To: <2a498b47415cd0c4ec9dfd1d84a855c1@hamnavoe.com>

Thanks for the pointers Richard.  Let me also take the opportunity to thank you for your efforts on getting Plan 9 onto the Pi.  

I had come across that linked doc, but wasn't sure that was what I was looking for.  I'll do a more thorough reading.

One of the challenges I'm finding with my early foray into Plan 9 is that there's quite a lot of reference material, a fair number of summaries and overviews (especially the various papers), a number of introductory videos, but it's difficult to navigate everything as a neophyte from an orientation and set-up task point of view.  The approach I'm taking is to 'swim about' in the materials, gradually learning the nomenclature and purposes of various bits and pieces, in the hope that the overall map of things will gradually piece itself together in my head.

Fantastic that you've already provided a 'cpu' kernel setup.  I saw this very early on when browsing the image, but had absolutely no idea what purpose it served.  It had looked like the basic system had everything it needed for this compared to my early reading of online docs, but I guess it is a sufficiently different thing.

Now that my interest is kindled, I had considered installing Plan 9 on my old G5 Mac, but it looks like the Mac/PowerPC version was never completed... unless somebody knows different.


On Monday, December 10, 2012 3:23:18 AM UTC-8, Richard Miller wrote:
> The canonical way to make your Plan 9 machine accessible to multiple users
> 
> is to make it into a cpu server.
> 
> 
> 
> The Plan 9 wiki has instructions for doing this:
> 
> 
> 
> See hget http://www.plan9.bell-labs.com/wiki/plan9/Configuring_a_Standalone_CPU_Server/index.html
> 
> 
> 
> On the raspberry pi, you'll find an already-built cpu kernel in 9picpu
> 
> on the boot partition, and a cmdline-cpu.txt file with essential boot
> 
> parameters.
> 
> 
> 
> The wiki has lots of other useful information.  For the full Plan 9
> 
> experience, you can access the wiki directly instead of via the
> 
> web interface.  In acme, open the file /acme/wiki/guide, and use
> 
> the middle mouse button to execute first 'Local 9fs wiki' and
> 
> then 'Wiki /mnt/wiki'.



  reply	other threads:[~2012-12-11  9:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10  9:37 [9fans] Canonical way to configure permanent remote cpu access Luke Evans
2012-12-10 10:12 ` lucio
2012-12-10 11:30   ` Richard Miller
2012-12-10 11:38     ` Charles Forsyth
2012-12-10 11:53       ` Richard Miller
2012-12-10 12:02     ` lucio
2012-12-10 15:41     ` Anthony Sorace
2012-12-10 16:47       ` Bakul Shah
2012-12-11  5:43         ` hiro
2012-12-10 11:23 ` Richard Miller
2012-12-11  9:36   ` Luke Evans [this message]
2012-12-11 12:21     ` [9fans] Canonical way to configure permanent remote Richard Miller

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=6cae90a8-e17e-4d72-9034-aa5158a6dc49@googlegroups.com \
    --to=luke.evans@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).