From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] CPU/Auth/Fileserver confusion
Date: Sun, 19 Dec 2004 13:31:52 +0100 [thread overview]
Message-ID: <20041219123152.GA17425@SDF.LONESTAR.ORG> (raw)
I got another piece of hardware and made a CPU/Auth und fossil based
fileserver out of my Plan 9 box. The Wiki page and andreys LANL setup
page were helpful.
If I start the terminal standalone, I can cpu to the CPU server and
can import its filesystem with 9fs.
The next step was to boot a 9pc kernel on terminal locally and get
root fs from the server. I can login as user und the dossrv of the
lib/profile gets executed. But nothing more and rio doesn't start and
there are messages like:
fifo stat 0 scrio dc000000 scr80283a04 pc 80176803
I spent the night with it and really don't find out what the problem
is.
Any help or hints appreciated,
Heiko :-(
next reply other threads:[~2004-12-19 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 12:31 Heiko Dudzus [this message]
2004-12-19 14:06 ` Heiko Dudzus
2004-12-19 16:08 ` jmk
2004-12-19 18:51 ` Heiko Dudzus
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=20041219123152.GA17425@SDF.LONESTAR.ORG \
--to=heiko.dudzus@gmx.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).