9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Wiki standalone CPU/Auth instructions
Date: Thu, 21 Dec 2006 22:05:26 +0000	[thread overview]
Message-ID: <9660b43503e9b9a072e5f12a78154187@quintile.net> (raw)
In-Reply-To: <c6603429cd5c157015df3e8851b8d0eb@coraid.com>

Claudio,

WRT Eric's email:

> --rw-rw---- M 9 mach0 adm 2125 Dec 18 08:13 /adm/keys
> --rw-rw---- M 9 mach0 adm 1539 Dec 18 08:14 /adm/keys.who

I think he is onto somthing here, my permissions are a little different,
my CPU servers boot as the user 'bootes' - its like root on a unix box, its a
name which is used by convention for the owner of a machine but everything
still works if you use a different name, you just have to rembember to use the
same name as the owner of all your cpu and auth servers. It seems Eric uses
mach0 as the hostowner for his cpu server, and from your description
you have chosen glenda.

I also allow the world to read keys.who as this does not contain secrets, only
admin info (real name email address etc).

--rw------- M 17739 bootes sys 300 Jan  3  2006 /adm/keys
--rw-rw-r-- M 17739 bootes sys 166 Aug 17  2005 /adm/keys.who

As I rembember it I had to create these files using the
fossil console. This was years ago though and the distribution may
now create these correctly.

	cpu% con -l /srv/fscons
	  prompt:  fsys main create /active/adm/keys bootes sys 600
	  prompt:  fsys main create /active/adm/keys.who bootes sys 664
	ctrl-\ q

Note: ``prompt:'' is the default prompt printed by the fossil console

-Steve


  reply	other threads:[~2006-12-21 22:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 21:39 erik quanstrom
2006-12-21 22:05 ` Steve Simon [this message]
2006-12-21 22:26   ` Claudio Leite
  -- strict thread matches above, loose matches on Subject: below --
2006-12-21 22:44 erik quanstrom
2006-12-21 21:28 Claudio Leite
2006-12-21 21:31 ` John Floren
2006-12-21 21:35   ` Paul Lalonde
2006-12-21 21:49     ` John Floren
2006-12-21 23:21       ` Paul Lalonde
2006-12-21 23:36         ` Claudio Leite
2006-12-21 23:41           ` John Floren
2006-12-21 22:33 ` Claudio Leite
2006-12-22  0:12 ` Georg Lehner
2007-01-06  8:15   ` Philip Dye

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=9660b43503e9b9a072e5f12a78154187@quintile.net \
    --to=steve@quintile.net \
    --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).