Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!ogicse!hsdndev!dartvax!news
From: kriso@lombard.dartmouth.edu (Kris Olander)
Newsgroups: comp.sys.hp
Subject: Standalone boot tape???
Message-ID: <1991Apr11.201346.5731@dartvax.dartmouth.edu>
Date: 11 Apr 91 20:13:46 GMT
Article-I.D.: dartvax.1991Apr11.201346.5731
Sender: news@dartvax.dartmouth.edu (The News Manager)
Distribution: usa
Organization: Dartmouth College, Hanover, NH
Lines: 43
Originator: kriso@lombard.dartmouth.edu

YOW!  Send in the fire truck to put out the ashes!

Here's one for you HP admin gurus.

I just managed to majorly screw up our HP9000 340
file server.  Don't know how, but the symptoms were:

1) ranlib (any .a file)
	produced:
	"sh: host unknown"

2) so I rebooted thinking that a new state would solve
   all my woes.

3) Boot fails right when init starts up and I get
	"getty failing ... respawning to rapidly ..."


And that's all she wrote.

So, to the get to the point of my Subject line,

I next attempted to stick in my HP-UX Install (7.0)
tape thinking that mmmaaayybe I could boot off the
tape, mount the root drive, figure out what was 
hosed, fix it (supreme confidence:), and then be
back up and running.

Wrong.  I couldn't find any way to get out of the
installation procedure.  I've bailed myself out of
a few root damage session on our Suns by using this
method, and so was hoping that ... 

Anyone know of a way (without duplicating the root
file system) of bringing up a mini-unix for damage
control sessions?

(BTW: our systems don't have floppys, just a tape drive.
	and hard drives -- of course.

-- 
Kris Olander
--------------kris.olander@dartmouth.edu----------------