From: Robert Sherwood <sherwood_robert@hotmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] int cpuserver = HELP!
Date: Tue, 16 Dec 2003 09:51:57 +0000 [thread overview]
Message-ID: <6fe98129.0312151909.1a01693b@posting.google.com> (raw)
Hi, all.
I have gotten plan9 installed. Thanks for the tip about moving the
cdrom drive to primary slave. That worked like a charm.
I am trying to set up the machine I installed as a CPU server, and I'm
having trouble getting the box to execute /rc/bin/cpurc.
As I understand it, the only thing required to cause init to launch
/rc/bin/cpurc is to compile and install a kernel with the following
lines in the mk file:
port
int cpuserver = 1;
Of course, I'm sure there's more work to do to get a working CPU
server, but I can't seem to force init to launch "cpurc". Is there any
way to query my freshly compiled "9pccpu" kernel to verify that it's a
cpu kernel. I'm at my wits' end. It just keeps launching
/rc/bin/termrc.
Thanks,
Rob
next reply other threads:[~2003-12-16 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 9:51 Robert Sherwood [this message]
2003-12-16 10:36 ` C H Forsyth
2003-12-17 9:46 ` Robert Sherwood
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=6fe98129.0312151909.1a01693b@posting.google.com \
--to=sherwood_robert@hotmail.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).