9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: corey@bitworthy.net, 9fans@9fans.net
Subject: Re: [9fans] yet another installation guide
Date: Tue, 11 Aug 2009 01:34:00 -0400	[thread overview]
Message-ID: <f087ed243d2df940fb78d48e812eb44e@quanstro.net> (raw)
In-Reply-To: <200908102200.20645.corey@bitworthy.net>

On Tue Aug 11 01:02:13 EDT 2009, corey@bitworthy.net wrote:
>
> I finished the first draft of a cpu/auth server installation/configuration howto:
>
> http://www.p9dp.org/plan9-cpu-auth-server-howto.html
>
> It would be great if whoever's interested, and has a bit of time could check
> it out, try it, and offer any suggestions/comments.

step 3.
you really don't want rwm on.  use dmaon script instead of doing
it by hand.  also ip/ipconfig with no args is recommended if you already have
a dhcp server.  also, this should be in your cpurc.local.

step 5.
these devices you suggest binding are already bound
* #S	/lib/namespace

it's probablly not a good idea to suggest that everyone bind
these:
* #m, #i

since not everyone is interested in starting rio on their cpu server.
likewise aux/vga, aux/mouse and rio don't belong in everyone's /cfg/$s/cpustart.
(it's really difficult to use the serial console remotely if you've started
rio!)

step 8.
don't invalidate the host keys after you've set them!  do that first.
also set the hostowner's keys here.

step 11.
refreshing cs is not required for ndb/query to work.  ndb/query doesn't
care what cs thinks.

step 14.
setting host key can be omitted.  you should have done that in step 8.

step 17.
it's a good idea to always leave a 9fat menu around on your auth server.
if you screw a kernel up, you'll really be proud of your self for it!

- erik



  reply	other threads:[~2009-08-11  5:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11  5:00 Corey
2009-08-11  5:34 ` erik quanstrom [this message]
2009-08-11  5:37   ` John Floren
2009-08-12  0:32     ` Corey
2009-08-12  0:40       ` John Floren
2009-08-12  1:08         ` Bruce Ellis
2009-08-12  3:10           ` Charles Forsyth
2009-08-12  3:39             ` Bruce Ellis
2009-08-13 11:05         ` Corey
     [not found] <af64fb3042985ab534a589f034832434@quanstro.net>
2009-08-12  0:27 ` Corey
2009-08-12  0:36   ` 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=f087ed243d2df940fb78d48e812eb44e@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=corey@bitworthy.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).