From: Dave Iafrate - CSCI/F1997 <diafrate@scs.Ryerson.CA>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] BIG PROBLEMS!!!!!
Date: Mon, 9 Apr 2001 02:23:55 -0400 [thread overview]
Message-ID: <Pine.GSO.4.21.0104090220001.1863-100000@jupiter.scs.ryerson.ca> (raw)
In-Reply-To: <20010409055537.1C23E199E7@mail.cse.psu.edu>
ok. thanks for the help but that still doesnt make sense in what is
happening to our system. When we compile the kernel we are using the
9pccpudisk kernel intended for the cpu server. What exactly happens is
that we make it through all the steps of the setup but the nvram creation
causes some grief. When using disk/prep, no plan 9 partition table is
returned, nonetheless after that problem we right echo blahblahblah to the
nvram and it still wont boot up and notify the difference in the
checksum.
If anyone has a detailed description of installing a cpu/auth server or
any plan9 installation (opposed to the regular ambigious
instructions that are provided throughout the web).
Thanks in advance
On Mon, 9 Apr 2001, Russ Cox wrote:
> Date: Mon, 9 Apr 2001 01:52:40 -0400
> From: Russ Cox <rsc@plan9.bell-labs.com>
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] BIG PROBLEMS!!!!!
>
> When we reboot, the system either hangs, or will just boot with a normal
> user prompt ( not the password, auth id and auth domain)
>
> The "boot with a normal user prompt" means
> you're not using a CPU kernel but rather
> a normal terminal kernel.
>
> Russ
>
next prev parent reply other threads:[~2001-04-09 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 5:52 Russ Cox
2001-04-09 6:23 ` Dave Iafrate - CSCI/F1997 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-09 6:35 Russ Cox
2001-04-09 6:55 ` Dave Iafrate - CSCI/F1997
2001-04-09 5:42 Dave Iafrate - CSCI/F1997
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=Pine.GSO.4.21.0104090220001.1863-100000@jupiter.scs.ryerson.ca \
--to=diafrate@scs.ryerson.ca \
--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).