Path: utzoo!censor!geac!jtsv16!uunet!tut.cis.ohio-state.edu!ucbvax!agate!shelby!unix!quintus!arisia!sgi!shinobu!odin!rock!mitch
From: mitch@rock.sgi.com (Thomas P. Mitchell)
Newsgroups: comp.sys.sgi
Subject: Re: Booting backup kernel
Message-ID: <357@odin.SGI.COM>
Date: 17 Aug 89 00:48:15 GMT
References: <1263@uvm-gen.UUCP> 
Distribution: usa
Organization: Silicon Graphics Computer Systems,  Mountain View CA.
Lines: 31

In article  elkins@topaz.rutgers.edu (George Elkins) writes:
>In article <1263@uvm-gen.UUCP>, ackerman@uvm-gen.uvm.edu (Steve Ackerman) writes:
>> Fortunately, I had a backup of it in /unix.old.
Good man.
>option.  At the PROM monitor level you could type
>	boot dkip(0,0,0)unix.old
>or from sash you could type
>	boot -f dkip(0,0,0)unix.old
>
>The general format for the boot command from sash is:
>	boot [-f device(address)file] [arguments]
>
>You may need to modify the above for your particular device,
>address and desired init level, etc.  E.g. from PROM,
>	boot dksc(0,1,0)unix.old initstate=1

CAUTION HERE:  initstate should be checked very carefully
		s =/= S
		s =/= 1
		S =/= 1
		1 =/= 2 
		1 =/= 3   etc.
         and the transitions from one to another are not 
         always symmetrical (cannot in some cases). 

#define =/= not necessarily the same.


 
Thomas P. Mitchell (ARPA:mitch@csd.sgi.com, UUCP:  {decwrl,ucbvax}!sgi!mitch )
Rainbows -- The best (well second best) reason for windows.