From owner-freebsd-current Sat Mar 25 13:09:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10146 for current-outgoing; Sat, 25 Mar 1995 13:09:08 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA10124 for ; Sat, 25 Mar 1995 13:08:52 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA00247; Sun, 26 Mar 1995 07:05:16 +1000 Date: Sun, 26 Mar 1995 07:05:16 +1000 From: Bruce Evans Message-Id: <199503252105.HAA00247@godzilla.zeta.org.au> To: bde@zeta.org.au, me@tartufo.pcs.dec.com Subject: Re: cvs commit: src/sys/scsi sd.c Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>I have committed the the changes for slices to the sd driver: >>--- >>bde 95/03/23 08:09:02 >Hrrm, both of my FreeBSD disks use the whole drive starting at sector 0, >there aren't any slices on them. The slice changes don't allow me to mount >them any more. Is this on purpose, I.e. do I *have* to fdisk my disks >or is the code supposed to work with FreeBSD covering the whole disk? If there is no DOSpartition table then there is one slice (the whole disk). Unfortunately you have to have a DOSpartition table to boot with biosboot, and disklabel -B writes a dummy DOSpartition table whether you want it or not. Fortunately it writes an _invalid_ DOSpartition table. Early versions rejected all invalid DOSpartition tables and gave one slice (the whole disk), but that seemed too dangerous. The 95/03/23 version gave one slice of size 50000 sectors for the dummy table. The current version rejects just one invalid table (the dummy one) and gives one slice (the whole disk). Bruce