9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] help installing standalone cpu server
Date: Sat, 24 Jan 2004 00:15:06 -0700	[thread overview]
Message-ID: <Pine.LNX.4.44.0401232354130.16092-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <200401232339.01788.jhorey@cs.unm.edu>

most of the 'configuring a standalone cpu' concern a system running the kfs
file system, while all the latest installations run fossil.

i'll modify it tomorrow, but for if you're in a hurry here's a brief
way of doing it:

	- add the user that will own the cpu/auth/fossil server at the fossil
	  console (follow the fossilcons man page instructions)

	- tell fossil to listen on the 9fs port by editing its configuration and
	  saving it (see the 'setting up fossil' wiki page)

	- edit /rc/bin/cpurc and uncomment auth/keyfs as per the wiki
	  instructions, also uncomment the ifconfig line and edit it to make
	  sure the machine can come up with a usable ip address

	- compile a 9pcauth kernel (cd /sys/src/9/pc && mk 'CONF=pcauth'), put
	  it somewhere  where your plan9.ini can find it and edit plan9.ini to
	  boot that (possibly setting up a menu, so that you can go back to a safe
	  config if that fails, see the plan9.ini man page)

	- create a 1-block (512 byte) nvram partition on the hard drive, you
	  can borrow that from the swap one, name it nvram. use disk/prep for that


that's about it, I believe... you may have to move something in
/rc/bin/services.auth, but those things you can get from the wiki page...

what's important is to keep the old setup available in a bootmenu option
(plan9.ini man page) in case something breaks. unless you don't mind
reinstalling.

good news is -- once you set it up you don't have to worry about it ever
more ;)

andrey

On Fri, 23 Jan 2004, James Horey wrote:

> Hello,
>
> I've been trying to follow the Wiki page on installing a standalone cpu
> server. Everything is going smoothly except there is one message I am worried
> about. After I reboot Plan 9 and boot into the 9pcauth kernel, I attempt to
> authenticate "bootes" using:
>
> auth/changeuser bootes
>
> I type in my password and confirmation and answer 'yes' to 'assign Inferno/POP
> secret'. However I get the message "changeuser: can't create user bootes:
> access permission denied". I tried disk/kfscmd allow and then trying again,
> but I get the same message. Any help would be greatly appreciated.
>
> -James Horey
>



  reply	other threads:[~2004-01-24  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-24  6:39 James Horey
2004-01-24  7:15 ` andrey mirtchovski [this message]
2004-01-25  4:20   ` Jack Johnson
2004-01-24 21:33 ` James Horey
2004-01-24 21:57   ` 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=Pine.LNX.4.44.0401232354130.16092-100000@fbsd.cpsc.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).