From owner-freebsd-hackers Tue Feb 14 08:35:15 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA00197 for hackers-outgoing; Tue, 14 Feb 1995 08:35:15 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA00191 for ; Tue, 14 Feb 1995 08:35:11 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA08302; Wed, 15 Feb 1995 03:31:40 +1100 Date: Wed, 15 Feb 1995 03:31:40 +1100 From: Bruce Evans Message-Id: <199502141631.DAA08302@godzilla.zeta.org.au> To: Herve.Soulard@inria.fr, freebsd-hackers@freefall.cdrom.com Subject: Re: Disklabel Sender: hackers-owner@FreeBSD.org Precedence: bulk >At home I'm running FreeBSD-2.0. At work I'm working on DEC-Alphas >with OSF1. I would like to use a hard disk to carry files between >the two systems. >I know it is possible because I've done it, but I cannot do it again. >Problems are with disk labels. When I disklabel the disk on FreeBSD, >I cannot read it on OSF1, and vice versa. I've only tested the >configuration where the full disk is used for FreeBSD/OSF1. Perhaps the label has been influenced by the DOS partition table even though you used the full disk. >PS: Could somebody explain me how labels, DOS partitions tables, etc > are written on the disk ? Or tell me where I could find something > that describe this. For FreeBSD of course. The label is written to the second sector of the BSD DOSpartition (if any). Locating the label is surprisingly complicated because the information in the label is sort of required to find the label. The 'c' partition described in the label must match the BSD partition described in the DOSpartition table. The 'd' partition is reserved for describing the whole disk. Other systems probably use an incompatible scheme. FreeBSD-2.1 will support relative labels. Everything in the label will be relative to the containing DOSpartition and the 'd' partition will no longer be special. Other systems certainly use an incompatible scheme. Bruce