[comp.sys.next] disk program damages OD label

abe@mace.cc.purdue.edu (Vic Abell) (02/21/89)

If you initialize an OD with a single, `a' partition, using the
"-t omd-all-1" hint supplied by carlton@betelgeuse.berkeley.edu,
the disk program will damage the OD label when you try to add the
host name and disk label.  Here are some diffs between label printings
before and after writing label information.

< before --- after >
6,7c6,7
< disk label: INITIALIZED
< disk name: omd-1-all
---
> disk label: od.abe
> disk name: omd-1
14c14
< host name: noname
---
> host name: vic.cc.purdue.edu
17c17,18
< a         0 247104  8192  1024   3    4096     10%   yes  time        no 4.3BSD
---
> a         0 157104  8192  1024   3    4096     10%   yes  time        no 4.3BSD
> b    157104  90000  8192  1024   3    8192     10%   yes  time        no 4.3BSD

Note that the disk name changed from "omd-1-all" to "omd-1", causing
(apparently) the disk partition count to change from one to two.  The
disk label and host name changes noted in the diffs are the actual
changes made via the disk program's label/write command.

Vic Abell

ali@polya.Stanford.EDU (Ali T. Ozer) (02/21/89)

In article <1779@mace.cc.purdue.edu> abe@mace.cc.purdue.edu (Vic Abell) writes:
>If you initialize an OD with a single, `a' partition, using the
>"-t omd-all-1" hint supplied by carlton@betelgeuse.berkeley.edu,
>the disk program will damage the OD label when you try to add the
>host name and disk label.

If your disk is built with omd-all-1, then you need to specify this type
when specifying the hostname and label info. For instance:

	disk -H hostname -t omd-all-1 /dev/rod0a

Ali Ozer, aozer@NeXT.com
NeXT Developer Support

abe@mace.cc.purdue.edu (Vic Abell) (02/23/89)

> ali@polya.Stanford.EDU (Ali T. Ozer) writes:
> 
> If your disk is built with omd-all-1, then you need to specify this type
> when specifying the hostname and label info. For instance:
> 
> 	disk -H hostname -t omd-all-1 /dev/rod0a

Why can't /etc/disk try to read the type info from the disk label,
especially when one is using disk's interactive mode to update
label information?  That way, it would be possible to write a host
name and a disk label name without having to explicitly state [and
make a typo on  :-)] or know the type.