From owner-freebsd-stable  Wed Apr  1 01:41:44 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA23564
          for freebsd-stable-outgoing; Wed, 1 Apr 1998 01:41:44 -0800 (PST)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23537
          for <stable@FreeBSD.ORG>; Wed, 1 Apr 1998 01:41:38 -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 TAA10027;
	Wed, 1 Apr 1998 19:36:22 +1000
Date: Wed, 1 Apr 1998 19:36:22 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199804010936.TAA10027@godzilla.zeta.org.au>
To: jfieber@indiana.edu, nate@mt.sri.com
Subject: Re: More on 2.2.6 upgrade
Cc: jkh@time.cdrom.com, stable@FreeBSD.ORG
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk

>Aye, but my historical precedence point was that ever since I can
>remember, partitions within a disk-like device are created
>automatically by passing just the device and unit to MAKEDEV.  To
>this day this is the behavior for basically all devices *except*
>slices--look at cd, fd, ccd, and vn for instance. ...

That's because cd, fd, ccd, matcd, mcd, scd and wcd are broken :-).
vn is handled like the other sliced devices.

Partitions are created for the compatibility slice and the fd, ccd
and foocd devices because historically the "whole disk" device is
just a partition (the C partition, except on the tahoe it is the A
partition and under 386BSD and related systems it is the D partition).
Floppies and cd's have evil aliases for the A and C partitions for
compatibility.

Bruce

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