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.
Thanks! Congratulations!
One (simple?) question: is there a simple idiom to force/allow replica
to (selectively!) update/overwrite some of the files that are reported
'locally modified; will not update'?
(ala wrap/install -f if memory serves me right?)
Axel.
For example, earlier this afternoon I did
(output isn't exact, this is from memory).
g% replica/pull -v /dist/replica/network
...
386/bin/ssh: locally modified; will not update
386/bin/sshnet: locally modified; will not update
lib/ndb/local: locally modified; will not update
...
g%
and resolved these by taking the new ssh binaries:
g% replica/pull -vs /dist/replica/network 386/bin/ssh 386/bin/sshnet
c 386/bin/ssh
c 386/bin/sshnet
g%
Note the lack of rooted slashes in the paths on the command line.
I would have next told replica/pull that I was happy
with lib/ndb/local the way I changed it:
g% replica/pull -vc /dist/replica/network lib/ndb/local
g%
except that when trying to figure out that there shouldn't
be rooted slashes on the pull ssh command line, I tried
g% replica/pull -vs /dist/replica/network
...
g%
which forced the server copy for everything. I don't actually
use /lib/ndb/local, so I was okay. Live and learn.
Russ
srv tcp!sources.cs.bell-labs.com: mount failed: authentication failed
--
Christopher Nielsen - Metal-wielding pyro techie
"Those who are willing to trade freedom for security deserve
neither freedom nor security." --Benjamin Franklin