Path: utzoo!utgpu!watmath!clyde!att!rutgers!mailrus!cornell!uw-beaver!rice!sun-spots-request From: dlc@vetch.c3.lanl.gov (Dale Carstensen) Newsgroups: comp.sys.sun Subject: Re: And then he moved /boot to /usr ... Message-ID: <8812131505.AA13179@vetch.c3.lanl.gov> Date: 20 Dec 88 22:23:43 GMT Sender: usenet@rice.edu Organization: Sun-Spots Lines: 23 Approved: Sun-Spots@rice.edu Original-Date: Tue, 13 Dec 88 08:05:02 MST X-Sun-Spots-Digest: Volume 7, Issue 66, message 3 of 10 (I think this is a better reply than the first one I sent to sun-spots.) The question was whether the physical placement of /boot makes a difference. The answer, for SunOS 4.0, is yes. You need to know this for restoring a lost /boot, and to set up local disk drives that have boot capability. Read the 4.0 man page for installboot. The boot program that is placed on sector 1-whatever of your boot disk does have block addresses for the /boot program. It is patched by the installboot program, which is not a "dd" script as the 3.5 installboot program was. In response to your later message, this knowledge is probably makes you think that setup (I thought it's name is now suninstall) is smart. You also need to know where the two boot programs are. Bootfile is in /usr/stand/boot., where is the architecture (sun3, for instance), or /export/exec//stand/boot. for heterogeneous servers, typically. Protobootblock is in /usr/mdec/boot, where is the disk type, or /export/exec//mdec/boot for heterogeneous servers, typically. Two other directories that suninstall and setup_client use are (for heterogeneous servers these may be /export/exec/ instead of /usr): /usr/etc/install/proto (most of the / file-system) /usr/boot (the /sbin directory and /vmunix)