Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: celeste@coherent.com (Celeste C. Stokely)
Newsgroups: comp.sys.sun
Subject: Re:  And then he moved /boot to /usr...
Message-ID: <8812091620.AA08571@frosted.coherent.com>
Date: 19 Dec 88 23:56:51 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 19
Approved: Sun-Spots@rice.edu
Original-Date: Fri, 9 Dec 88 08:20:05 PST
X-Sun-Spots-Digest: Volume 7, Issue 62, message 4 of 12

Yes, as it turns out, /boot is in a VERY particular spot. something like
starting at disk block 15 or some such voodoo. The only way you can get it
back in the right place is by running "/usr/etc/mdec/installboot xx yyyy",
(under 3.x, anyway), which of course isn't documented.

Say it's a server with xy disks. You do:
installboot bootxy xy0a
(at least, I think you'd say xy0a. try it. if you can then boot, you did
it right.)

installboot is a shell script which does a dd of the bootfile to a spot on
the disk. Installing bootblocks is all /usr/mdec is used for, I believe.

..Celeste Stokely
Coherent Thought Inc.
UUCP:	...!{ames,sun,uunet}!coherent!celeste   Domain: celeste@coherent.com
Internet: coherent!celeste@ames.arpa or ...@sun.com or ...@uunet.uu.net
VOX:  415-493-8805
SNAIL:3350 W. Bayshore Rd. #205, Palo Alto CA  94303