Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site cheviot.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!mcnc!philabs!cmcl2!seismo!mcvax!ukc!cheviot!andy From: andy@cheviot.UUCP (Andy Linton) Newsgroups: net.unix-wizards Subject: Re: Rebooting 4.2BSD on a 780 Message-ID: <368@cheviot.UUCP> Date: Fri, 28-Jun-85 19:26:53 EDT Article-I.D.: cheviot.368 Posted: Fri Jun 28 19:26:53 1985 Date-Received: Sat, 29-Jun-85 23:50:55 EDT References: <11030@brl-tgr.ARPA> <412@mtxinu.UUCP> <332@basser.oz> <323@umcp-cs.UUCP> Reply-To: andy@cheviot.UUCP (Andy Linton) Organization: U. of Newcastle upon Tyne, U.K. Lines: 17 Try looking at Section 6.1 in "Installing/Operating 4.2BSD" - Section 62 in Volume 2 of the system manual. It suggests that when at the console command level you can say:- >>> B ANY or, on a 750 >>> B/3 and that these commands boot and ask for the name of the system to be booted. If you use /newvmunix as the name of your new system and things go wrong /vmunix will be rebooted when/if your new system falls over. If all goes well you can link /newvmunix to /vmunix so that 'ps' and co. work O.K. We have two 750's and use this when trying out new things.