From owner-freebsd-hackers Wed Jul 12 11:09:19 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA13769 for hackers-outgoing; Wed, 12 Jul 1995 11:09:19 -0700 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 LAA13763 for ; Wed, 12 Jul 1995 11:09:12 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA01192; Thu, 13 Jul 1995 04:01:38 +1000 Date: Thu, 13 Jul 1995 04:01:38 +1000 From: Bruce Evans Message-Id: <199507121801.EAA01192@godzilla.zeta.org.au> To: freebsd-hackers@freebsd.org, hm@ernie.altona.hamburg.com Subject: Re: A problem with disklabel & "use entire disk" on 2.0.5R. Sender: hackers-owner@freebsd.org Precedence: bulk >> > I *had* to use the translated geometry to get anything to boot. >> >> This comes up over and over again. In Usenet. In private mails/talks >> i'm getting. I'm not very happy that the slice code broke *many* >> systems that used to run before with their dedicated disks. IMHO, we >> ... >One of them was me. The system in question has never seen another OS than >*BSD and it will never. (It will never see any commercial PC SYSV U*nx, >any Microsoft OS, nor any IBM OS). I always used the whole disk for *BSD >since 386BSD and it went fine until 2.0.5 ... :-( Why didn't you use the existing (whole-disk) slice? The one created by copying the boot blocks over the MBR isn't acceptable to foreign OS's or disk managers, but you don't wan't those, and it is acceptable to FreeBSD. >So to repeat the original question: is there any drawback in using this >totally strange cylinder/head/sector layout i was forced to use ???? No. It is only used for loading the first sector of the FreeBSD boot blocks. It gets put in the disk label but newfs no longer uses the geometry in the label by default and drivers no longer use the geometry in the label at all. Bruce