From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] online updates now available
Date: Tue, 21 May 2002 16:44:53 -0400 [thread overview]
Message-ID: <8aa0fc5d47540ca24e1a89f6336a7564@plan9.bell-labs.com> (raw)
We have set up a Plan 9 file server to distribute
updates using the replica(1) tools. To create an
account on the server, you must go to the web page
http://plan9.bell-labs.com/plan9dist/newaccount.html
and answer The Questions one final time. Once you
have created an account, you will be presented with
instructions for updating your Plan 9 installation.
To update your kfs system, run the following script (if you
set up a non-kfs file server, you'll have to edit to suit):
cat >/tmp/network <<'!'
#!/bin/rc
s=/n/dist/dist/replica
serverroot=/n/dist
serverlog=$s/plan9.log
serverproto=$s/plan9.proto
fn servermount {
srv tcp!sources.cs.bell-labs.com sources /n/sources
bind /n/sources/plan9 /n/dist
}
fn serverupdate { status='' }
fn clientmount { 9fs kfs }
c=/n/kfs/dist/replica
clientroot=/n/kfs
clientdb=$c/client/plan9.db
clientexclude=(dist/replica/client)
clientlog=$c/client/plan9.log
applyopt=(-u -T$c/client/plan9.time)
!
chmod +x /tmp/network
cat >>/net/ndb <<'!'
auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
!
echo -n refresh >/net/cs
disk/kfscmd allow
replica/pull -v /tmp/network
After running this, you'll be able to use
disk/kfscmd allow
replica/pull -v /dist/replica/network
to retrieve future updates.
See replica(1) for more information.
If you have customized /lib/ndb/local,
the update will not overwrite it. Instead,
add the following line:
auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
The additional packages are also available
on the same server. After updating, you can do
9fs sources
ls -l /n/sources/extra
to see them.
Enjoy.
next reply other threads:[~2002-05-21 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 20:44 Russ Cox [this message]
2002-05-21 21:41 ` Axel Belinfante
2002-05-29 8:48 ` Christopher Nielsen
2002-05-21 21:49 rsc
2002-05-29 9:04 forsyth
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=8aa0fc5d47540ca24e1a89f6336a7564@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).