9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installed Plan 9, now what?
Date: Mon,  8 Dec 2003 10:00:58 -0500	[thread overview]
Message-ID: <E1ATMsd-00013B-NO@t40.swtch.com> (raw)
In-Reply-To: Your message of "Mon, 08 Dec 2003 13:36:51 +0200." <81132473206F3A46A72BD6116E1A06AE056157@black.aprote.com>

> > I recently installed plan 9 on my dell dimension desktop using the
> > wiki notes. I used fossil as my filesystem. How do I stay upto date?
> > The notes on the webpage seems to be for kfs.
>
> OK, I don't get it. There seems to be some consensus that clientmount()
> shoud be 'mount -c /srv/boot /n/boot'. But in /sys/src/9/boot/local.c
> /srv/boot is created as 'srv -A fboot', which means only authentication
> is off; permission checking and arbitrary wstats are still standard. =
> This is clearly
> not enough for replica (confirmed by in vivo experiments).=20
> So, what's the deal?

the deal is that for the local file system, it's okay
not to do authentication.  kfs never did, for bootstrapping
reasons, and so i made the fossil boot process do the same.
otherwise you'd need to run an auth server just to boot
a standalone laptop.

it's only for booting, not for pulling.  i just put myself
in sys and remove the -u from the proto file, and then that's
enough for replica (and all the created files get owned by me,
which is no problem for me).  if you have a special system account
you could still do the same, as long as you're willing to give
up on things being owned by sys.

russ


  parent reply	other threads:[~2003-12-08 15:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 11:36 Tiit Lankots
2003-12-08 14:51 ` ron minnich
2003-12-08 15:00 ` Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-09  7:55 YAMANASHI Takeshi
2003-12-09 13:49 ` David Presotto
2003-12-08 12:48 David Presotto
2003-12-08 15:10 ` andrey mirtchovski
2003-12-08 16:21   ` David Presotto
2003-12-08 19:30   ` Dan Cross
2003-12-08 21:14     ` david presotto
2003-12-08 22:20       ` Dan Cross
2003-12-09  0:55         ` David Presotto
2003-12-09  1:20           ` Russ Cox
2003-12-09  1:29             ` Dan Cross
2003-12-09  1:36               ` Russ Cox
2003-12-09  3:00                 ` Dan Cross
2003-12-09  4:02                   ` Geoff Collyer
2003-12-09  3:44                     ` mirtchov
2003-12-09  4:10                     ` Scott Schwartz
2003-12-07  9:59                       ` Charles Forsyth
2003-12-07 10:28                         ` Charles Forsyth
2003-12-09  4:33                       ` Geoff Collyer
2003-12-09  4:54                     ` Dan Cross
2003-12-09  7:47                       ` okamoto
2003-12-09 11:23                       ` a
2003-12-09 12:12                         ` boyd, rounin
2003-12-09 18:33                       ` splite
2003-12-09 19:23                         ` Brantley Coile
2003-12-08 10:08 Sujan Gautam
2003-12-08 13:53 ` mirtchov

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=E1ATMsd-00013B-NO@t40.swtch.com \
    --to=rsc@swtch.com \
    --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).