From owner-freebsd-hackers Fri Sep 1 10:51:48 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA11505 for hackers-outgoing; Fri, 1 Sep 1995 10:51:48 -0700 Received: from elf.kendall.mdcc.edu (elf.kendall.mdcc.edu [147.70.150.122]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id KAA11498 for ; Fri, 1 Sep 1995 10:51:46 -0700 Received: (from freelist@localhost) by elf.kendall.mdcc.edu (8.6.11/8.6.9) id NAA13666; Fri, 1 Sep 1995 13:41:42 -0400 Date: Fri, 1 Sep 1995 13:41:41 -0400 (EDT) From: "Don's FList drop" To: hackers@freefall.FreeBSD.org, Joerg Wunsch Subject: Re: fdisk in 2.1.0--SNAP is broken In-Reply-To: <199509011718.TAA01574@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Fri, 1 Sep 1995, J Wunsch wrote: > It's been changed since we've got a better solution than the mystic > `d' partition now to access the entire drive; it's the slice code. > Only the `c' partition remains magic now, it's the synonym for the > entire slice. Hmmm. My second drive is currently wd1c, due to a complicated series of technical issues that boil down to the fact that I didn't know what the hell I was doing when I set it up. Am I headed for a future disaster here? It's working fine, but now you've got me worrying that it's going to cause trouble down the road if I move this machine up to 2.1 or something.