Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ptsfa!ihnp4!laidbak!mdb
From: mdb@laidbak.UUCP
Newsgroups: comp.sys.att
Subject: Re: Disk Partitioning on 3b2's
Message-ID: <1043@laidbak.UUCP>
Date: Fri, 17-Apr-87 23:08:16 EST
Article-I.D.: laidbak.1043
Posted: Fri Apr 17 23:08:16 1987
Date-Received: Sun, 19-Apr-87 00:47:23 EST
References: <81@paisana.UUCP> <58300003@gorgo.UUCP> <943@hropus.UUCP>
Organization: Lachman Associates, Inc., Naperville, IL
Lines: 17
Summary: 3B2 /etc/fmthard doesn't damage data, but does zap the pointer to the bootstrap.

> [Chris Donahue]
> ...
> partitioning is actually determined by vtoc stored on the disk. The fmthard
> command writes a new vtoc onto the drive. This *always* cremes the data on
> the drive, so take care. Note also that the filesystem boundaries need to
> ...

The 3B2 /etc/fmthard command replaces the VTOC (partition map) of a hard
disk. It does not damage the contents of the partitions.

Note that /etc/fmthard does, however, make a disk non-bootable; it zeroes
the VTOC words which point at the second-level bootstrap. Use "/etc/newboot
/lib/lboot /lib/mboot /dev/rdsk/c-d-s7" to reinstall the bootstrap.

					Mark Brukhartz
					Lachman Associates, Inc.
					..!{ihnp4, sun}!laidbak!mdb