9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "david presotto" <presotto@closedmind.org>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Installed Plan 9, now what?
Date: Mon,  8 Dec 2003 16:14:12 -0500	[thread overview]
Message-ID: <001001c3bdd0$3a91b260$6f096887@bl.belllabs.com> (raw)
In-Reply-To: <200312081930.hB8JUsl28107@augusta.math.psu.edu>

Isn't that what /dist/replica/network is?  How many times indirects
shall we go before we get to the file we're allowed to change.

Andrey's script is fine by me.  It gets it right in more cases
than the old one.  If you dinna like, it, replace it with your own.
----- Original Message -----
From: "Dan Cross" <cross@math.psu.edu>
To: <9fans@cse.psu.edu>
Sent: Monday, December 08, 2003 2:30 PM
Subject: Re: [9fans] Installed Plan 9, now what?


> andrey mirtchovski <mirtchov@cpsc.ucalgary.ca> writes:
> >
> > On Mon, 8 Dec 2003, David Presotto wrote:
> >
> > > fn clientmount { echo 'srv -AWP replica'>>/srv/fscons;chmod 600
/srv/replica; mount -c /srv/replica /n/kfs }
> > >
> >
> > why not just add that to the /dist/replica/network script on sources?
with
> > appropriate checks whether the system is running kfs or fossil and
whether
> > $user can write to /srv/fscons we won't need to worry about it too much.
> >
> > i can send you a sample script for that.
> >
> > can you explain the chmod 600? it appears that /srv/replica is 600
already
> > after the srv command is issued...
>
> I'll propose again that replica scripts attempt to dot a script called
> /dist/replica/site which could override things like the clientmount
> function for dfferent sites.
>
> - Dan C.
>
>



  reply	other threads:[~2003-12-08 21:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- 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 11:36 Tiit Lankots
2003-12-08 14:51 ` ron minnich
2003-12-08 15:00 ` Russ Cox
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='001001c3bdd0$3a91b260$6f096887@bl.belllabs.com' \
    --to=presotto@closedmind.org \
    --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).