ericw@sycamore (Eric D. Williams) (06/06/91)
Howdy, I'm an experienced Unix type, who got this IBM 6000 dumped on me. In it's previous life, it was at our San Jose office, and is configured to look for their NIS domain. So when we turn it on here in San Diego, it locks up waiting of the San Jose NIS servers to respond. So my question: how do you boot one of these things into single-user mode so I can fix the problem? So far, I can't even talk to the ROM monitor like on other workstations. We got some harware manuals, with 9+ diagnostic diskettes but no mention of how to set the boot mode. Any advice would be appreciated! Thanks, _________________________________________________________________ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Eric D. Williams "I am the Great and Powerful Cadence Design Systems SuperUser! Ignore the confused, ericw@autosys.com tired person behind that curtain!" _________________________________________________________________ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
manish@thinker.almaden.ibm.com (Manish Arya) (06/07/91)
In a recent append, ericw@autosys.com (Eric D. Williams) writes... > So when we turn it > on here in San Diego, it locks up waiting of the San Jose NIS > servers to respond. So my question: how do you boot one of these > things into single-user mode so I can fix the problem? An UNOFFICIAL response.... If I ever need to disable NIS on a machine because no servers are around, I push the big yellow switch (unless the system gives me a chance to type "shutdown -Fr"), wait for the message "Starting tcpip daemons" to come up on the screen, and then immediately press control-C several times. This seems to abort the boot sequence early enough that ypbind doesn't start. Then I edit /etc/rc.nfs and comment out the line that starts ypbind and "shutdown -Fr" to boot the system properly. - Manish Arya
marc@ekhomeni.austin.ibm.com (Marc Wiz) (06/07/91)
I have had this problem happen to me and here's what I do: boot from floppy or tape. select maintainance mode /etc/continue hdisk0 (or whatever your root volume group is on) Using vi or whatever editor you prefer delete the NIS escape sequences from /etc/passwd and /etc/group reboot and you're up and running. Of course don't forget to remove the NIS client configuration after the system comes up. (Just keeps ypbind from being started and sets the domainname to null) Marc Wiz MaBell (512)823-4780 NFS/NIS change team Yes that really is my last name. The views expressed are my own. marc@aixwiz.austin.ibm.com or uunet!cs.utexas.edu!ibmchs!auschs!ekhomeni.austin.ibm.com!marc