From: Matthias Teege <matthias@mteege.de>
To: 9fans@cse.psu.edu
Subject: [9fans] /dist is empty
Date: Mon, 15 Sep 2003 16:48:13 +0000 [thread overview]
Message-ID: <86u17eypdh.fsf@gic.mteege.de> (raw)
Moin,
I have setup a standalone fileserver. All looks god and I can mount
the fileserver to the cpu/auth server to install plan9.9gz. But my
/dist on the cpu/auth server is empty except "replica".
Is it possible, to build a plan9.9gz from the installation CD,
transfer it to the cpu/auth server and then install it on the
fileserver?
Many thanks
Matthias
--
Matthias Teege -- http://www.mteege.de
make world not war
PGP-Key auf Anfrage
next reply other threads:[~2003-09-15 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 16:48 Matthias Teege [this message]
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
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=86u17eypdh.fsf@gic.mteege.de \
--to=matthias@mteege.de \
--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).