9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve_Kilbane Steve_Kilbane@cegelecproj.co.uk
Subject: file-server setup. --> Sun config stuff..
Date: Wed,  6 Sep 1995 10:49:58 -0400	[thread overview]
Message-ID: <19950906144958._CXFEn7bg6oluZncYV3WkAFz3xN25uOlf7hvTYPvtl8@z> (raw)

In article <42iefg$gj3@hptemp1.cc.umr.edu>, johns@cs.umr.EDU (John Stone) writes:
> In article <9509051015.AA15050@phantom.cegelecproj.co.uk>,
> Steve_Kilbane <9fans@cse.psu.edu> wrote:
> >A more extreme method was to try installing the CD directly to a Sun running
> >/sparc/9ssfs. However, after that kernel loads via tftp, it doesn't do
> >anything. I'd expected the config: prompt, but it appears to have hung. ^T^Tr
> >and L1-A don't do anything. This was a surprise, because 9ss and 9sscd both
> >work.

> First, you need to be running an SS2, IPX, or one of the other SS2-like 
> Sun4C machines.

Yep. it's an SS2, with 64MB.

> That said, I think I know of one thing to check: 
> 
>   Does your SS2/IPX/...'s disk spin up at power on, or at scsi "start"? 

As far as I know. Also, I've tried:
	- booting as you suggest
	- booting from a power reset
	- booting straight after halting SunOS

with no apparent differences in results.

> If anyone else has explainations for the SCSI and lance errors, let me
> know..

I haven't seen any errors at all. It finishes downloading the kernel,
and That's All She Wrote. :-(

steve
-- 
<Steve_Kilbane@cegelecproj.co.uk>
ISPs are responsible for maintaining the Information Superhighway. They
are not responsible for how you drive.      #include <std_disclaimer.h>






             reply	other threads:[~1995-09-06 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-09-06 14:49 Steve_Kilbane [this message]
1995-09-06 20:14 Steve_Kilbane
1995-09-08 11:55 Scott
1995-09-09 16:39 philw

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=19950906144958._CXFEn7bg6oluZncYV3WkAFz3xN25uOlf7hvTYPvtl8@z \
    --to=9fans@9fans.net \
    /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).