From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bleeding edge sources
Date: Tue, 8 Oct 2002 12:10:34 -0400 [thread overview]
Message-ID: <85a83f0d059c2c1de00180c499810259@plan9.bell-labs.com> (raw)
The update process is described in replica(1).
There's an example at the end.
The typical incantation (assuming you have
network connectivity) is
disk/kfscmd allow
replica/pull -v /dist/replica/network
disk/kfscmd disallow
If you've updated recently, glenda has a script
called pull in her bin/rc directory, so if you're
logged in as glenda, you can just do
pull
or
pull -s
if you want to overwrite local changes with server
changes when conflicts occur. If you don't log in
as glenda, you can use
cat >$home/bin/rc/pull <<!
#!/bin/rc
exec /usr/glenda/bin/rc/pull $*
!
chmod +x $home/bin/rc/pull
Russ
next reply other threads:[~2002-10-08 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 16:10 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-08 15:58 [9fans] lp doesn't work after upgrade from downloaded cd image Russ Cox
2002-10-08 16:05 ` [9fans] bleeding edge sources John Saylor
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=85a83f0d059c2c1de00180c499810259@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).