Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!shelby!csli!dmr
From: dmr@csli.Stanford.EDU (Daniel M. Rosenberg)
Newsgroups: comp.sys.next
Subject: How to kill a NeXT machine...
Message-ID: <8853@csli.Stanford.EDU>
Date: 7 May 89 04:50:18 GMT
Sender: dmr@csli.Stanford.EDU (Daniel M. Rosenberg)
Reply-To: dmr@csli.stanford.edu (Daniel M. Rosenberg)
Organization: World Otherness Ministries
Lines: 29

I had just gotten 0.8 WriteNow to print on my LaserWriter (thanks
for the help on that!) and was seriously into hacking the hell
out of my system into workability.

Mail off of our next box never made it further than the Mailer-Daemon;
it complained something about how mailer ether didn't know how to get
to mailhost, and I couldn't figure out how to tell it what mailhost
was. So, I thought, why not just get yellow pages running on this
sucker, so as to make it have the same idea about centralized network
services as all the other machines in our area.

Simple enough, with ypinit -s, but when I /etc/reboot'ed to implement
this, our machine hung -- it did a ypbind, then stuck at the inetd
spot.

So, now we have this NeXT box that won't boot. Is there any well to interrupt
the rc.local (or whatever) script and tell it to just move on, so I can
fix the error? Or is the only thing I can do to take out the disk,
bring it to another NeXT box, and try to repair it there even though
I don't quite know what I did wrong?

Or do I have to end up waiting for 0.9 to arrive? (We didn't send in
the registration card yet. Dumb, dumb, dumb.)

Glad for any suggestions -- I remain,

-- 
# Daniel M. Rosenberg     //  Stanford CSLI  // Opinions are my own only.
# dmr@csli.stanford.edu  // decwrl!csli!dmr // dmr%csli@stanford.bitnet