From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /dist is empty
Date: Tue, 16 Sep 2003 11:36:38 -0400 [thread overview]
Message-ID: <0eccc927f753f78eeeeece72f142ffe4@plan9.bell-labs.com> (raw)
In-Reply-To: <200309161531.h8GFVjj02457@augusta.math.psu.edu>
> Please don't do this. Use what's already there.
>
> 9fs batida
> bind -c /n/batida /n/inst
> mount /srv/9660 /n/dist /path/to/plan9.iso
> replica/inst -v /dist/replica/inst
Dan is right. I'd forgotten this.
> If /dist/replica/inst doesn't exist on your system (it should; it used to
> be on sources, at least) you can try something else. You don't even really
> need the CD (except to be nice to the labs). Ostensibly, you could just
> do:
>
> mount -c /srv/batida /n/inst
> 9fs sources
> bind /n/sources/plan9 /n/dist
> replica/inst -v /dist/replica/inst
>
> I do something like that to update my fileserver from sources all the time.
This is great for updating your file server once it's going.
It's not so great for populating it from scratch -- copying
from a CD will be a lot faster, due to the latency of 9P to
sources.
Russ
next prev parent reply other threads:[~2003-09-16 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 16:48 Matthias Teege
2003-09-15 19:10 ` Russ Cox
2003-09-16 8:31 ` Matthias Teege
2003-09-16 13:39 ` Russ Cox
2003-09-16 8:31 ` Matthias Teege
2003-09-16 13:40 ` Russ Cox
2003-09-16 15:31 ` Dan Cross
2003-09-16 15:36 ` Russ Cox [this message]
2003-09-16 23:47 ` boyd, rounin
2003-09-16 17:19 ` Matthias Teege
2003-09-16 18:06 ` Russ Cox
2003-09-16 15:10 ` Dan Cross
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=0eccc927f753f78eeeeece72f142ffe4@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).