Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site omssw2.UUCP
Path: utzoo!decvax!tektronix!reed!omssw2!tw
From: tw@omssw2.UUCP (Thomas Walsh)
Newsgroups: net.unix,net.unix-wizards
Subject: Re: panic: iinit
Message-ID: <483@omssw2.UUCP>
Date: Fri, 25-Jul-86 10:05:24 EDT
Article-I.D.: omssw2.483
Posted: Fri Jul 25 10:05:24 1986
Date-Received: Sat, 26-Jul-86 03:11:22 EDT
Expires: Sun, 10-Aug-86 03:00:00 EDT
References: <972@dicome.UUCP>
Reply-To: tw@omssw2.UUCP (Thomas Walsh)
Distribution: na
Organization: Intel Corp., OMS Div., Systems Group, Hillsboro, OR
Lines: 11
Keywords: panic: system admin ;-)

i do the same thing on xenix systems, however there are compiled in
values which tell iinit which filesystem is the root device (what
controller, what device...)  if these are unchanged (as you indicate),
the kernel being booted off of the second drive reads the superblock
off of the first drive and panics.  i don't know the names of the
#defines in bsd configuration files.  in addition, in the /dev directory
of the 'backup' root partition, the major and minor numbers of swap,
root, and possibly other devices will need to point at the 'second'
drive, or utilities which seek on these will behave strangely at best.

..reed!omssw1!omssw2!tw