From: jon@robots.ox.ac.uk (Jon Tombs) Newsgroups: comp.sys.sun.admin Subject: booting a 386i without a pnpd. Message-ID: <3591@inca.comlab.ox.ac.uk> Date: 29 May 92 21:35:18 GMT Sender: news@comlab.ox.ac.uk Organization: Robotics Research Group, Engineering Science Dept, Oxford, UK. Lines: 26 Originator: jon@lucrece.robots I recently had to help out on a network with a mix of 386is and sparcs, one of the 386is was the ypmaster and they wished to move the master onto one of the sparcs. The problem after doing this was you could no longer reboot any of the 386is, you couldn't even boot single user (even though they were diskfull machines), because the ex-ypmaster was no longer running a pnpd (and a few other related daemons). You couldn't start a pnpd anymore as the daemon refused to run on a machine that wasn't the ypmaster! The only documentation I could find with the 386is was the 4.0.2 install which says you must have the ypmaster running before you can boot any other diskfull machines. Why!? The old ypmaster would still reboot after the change, can anyone tell me what magic file this machine has that allows it to reboot (and start the first pnpd). Can I just do the same to the other 386is so they can boot too? At the moment the 386i is back as ypmaster, which what they originally tried to change! If its any use 386is running 4.0.2 all diskfull with / and minimal /usr sparcs running 4.1.2. Don't tell me to RTFM coz they never bought TFM. -- Jon "I got in today, just as the sun was crashing"