From owner-freebsd-current  Sat Jan 16 08:52:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA29245
          for freebsd-current-outgoing; Sat, 16 Jan 1999 08:52:36 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29238
          for <current@FreeBSD.ORG>; Sat, 16 Jan 1999 08:52:32 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA24642;
	Sun, 17 Jan 1999 03:52:29 +1100
Date: Sun, 17 Jan 1999 03:52:29 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901161652.DAA24642@godzilla.zeta.org.au>
To: igor@physics.uiuc.edu, rnordier@nordier.com
Subject: Re: a few suggestions/comments on 3.0-RELEASE
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> Also, it might be nice if the disklabel(8) man pages explicitely
>> say that the bootstrap code can be installed on each slice.
>> (am I wrong ?)
>
>You're right, the bootblocks can be installed on each slice, and
>this also needs documenting.

This doesn't need documenting.  disklabel(8) knows nothing of slices.
It installs labels and bootblocks on disk-like devices.  Slices are
just one type of disk-like device.  All regular files larger than 1K
and many devices are disk-like, thanks to device independence.

For the bootstrap code to actual work, more is required.  E.g., slices
on vn "disks" are not bootable because the boot loader doesn't support
vn "disks".  disklabel(8) knows nothing of this limitation.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message