Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!homxb!houxm!hropus!jgy
From: jgy@hropus.UUCP
Newsgroups: comp.sys.att
Subject: Re: Disk Partitioning on 3b2's
Message-ID: <943@hropus.UUCP>
Date: Mon, 6-Apr-87 11:46:15 EST
Article-I.D.: hropus.943
Posted: Mon Apr  6 11:46:15 1987
Date-Received: Thu, 9-Apr-87 00:19:15 EST
References: <81@paisana.UUCP> <58300003@gorgo.UUCP>
Organization: Bell Labs, Holmdel, NJ
Lines: 17

> Chris Donahue writes:
> 
> >Read the "Hard Disk Partitioning" Section in the System Administrator's
> >Guide (in Administrative Tasks major section) and look at the manual
> >page for /etc/fmthard (in the SA Reference Manual). Also, take a
> >look at the "sysadm partitioning" command. You'll get the idea.
> 
> I'll go one step further... The fmthard command is necessary since the 3B2 disk
> 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
> 

Not true, it does not touch the data on the disk, only the information
describing how to get to the data, rather like losing your inode area.
But it can be reversed with more ease!