From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pcf config file ...
Date: Sun, 26 Oct 2003 13:32:18 -0500 [thread overview]
Message-ID: <200310261832.h9QIWJl21300@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Sun, 26 Oct 2003 13:26:09 EST." <E1ADpad-000Kxr-PK@t40.swtch.com>
"Russ Cox" <rsc@swtch.com> writes:
> pull is hard-coded to run "9fs kfs". really you should be using
> dan cross's /dist/replica/dist, but i never remember how to do that.
> instead you can just create a /srv/kfs that pull will be able
> to mount (it doesn't see one so it starts kfs).
>
> echo 1 >/srv/kfs </srv/boot
>
> should do the trick.
It's called `inst', and while it's on sources, it never made it to the
base distribution. It is, however, pretty easy to use:
term% mount -c /srv/boot /n/inst
term% 9fs sources
term% cp /n/sources/plan9/dist/replica/inst /dist/replica
term% bind /n/sources/plan9 /n/dist
term% replica/pull -v /dist/replica/inst
After my thinkpad died a horrible, gurgling death, I bought an iBook
running MacOS X. When jmk updated the ethernet drivers such that
VirtualPC for the Mac worked (well, it already worked, but now the
network worked, too), I bought and installed VirtualPC. It's quite
nice, if a little slow, and gave me an opportunity to jump from KFS to
fossil (which I did). After doing so, however, I'm a little dismayed
about how much still depends on kfs, particularly the replica scripts
under /dist/replica (and in individual package replica scripts). It
seems to me that if fossil is the way to go moving forward, it would
behoove us to update the other parts of the system to treat it with a
little more respect. To that end, I like Andrey's modification that
Ron just posted; it'll also work on fileservers and the like. In
short, we should be updating the system to be more general, not trying
to fool things into looking vaguely like kfs so old tools will continue
working.
As an aside, I also had an idea for /dist/replica/site, or
/dist/relica/site.local, which could be customized with a particular
site's localizations (applyopts and the like). Then replica scripts
could `.' it, effectively customizing themselves for given site
configurations (the most obvious example would be doing things like
overriding default clientroot's). I still think it's a good idea,
but it never took off.
- Dan C.
next prev parent reply other threads:[~2003-10-26 18:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 9:19 xigh
2003-10-25 14:27 ` ron minnich
2003-10-25 18:27 ` Russ Cox
2003-10-25 19:39 ` Philippe Anel
2003-10-25 23:18 ` Russ Cox
2003-10-26 18:09 ` Philippe Anel
2003-10-26 18:20 ` ron minnich
2003-10-26 18:30 ` Russ Cox
2003-10-26 18:26 ` Russ Cox
2003-10-26 18:32 ` Dan Cross [this message]
2003-10-26 19:37 ` Philippe Anel
-- strict thread matches above, loose matches on Subject: below --
2003-10-25 16:26 Anel Philippe
2003-10-25 16:27 ` ron minnich
[not found] ` <Pine.LNX.4.44.0310251024230.10808-100000@maxroach.lanl.gov >
2003-10-25 16:52 ` Philippe Anel
2003-10-25 16:59 ` ron minnich
2003-10-25 17:06 ` Russ Cox
2003-10-25 17:42 ` Christian Grothaus
2003-10-25 18:22 ` Russ Cox
2003-10-25 17:48 ` Philippe Anel
2003-10-25 9:17 Philippe Anel
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=200310261832.h9QIWJl21300@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).