From owner-freebsd-current  Mon Oct 19 14:14:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA20316
          for freebsd-current-outgoing; Mon, 19 Oct 1998 14:14:22 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20311
          for <current@FreeBSD.ORG>; Mon, 19 Oct 1998 14:14:21 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id OAA29824;
	Mon, 19 Oct 1998 14:03:36 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpdY29818; Mon Oct 19 21:03:30 1998
Date: Mon, 19 Oct 1998 14:03:24 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: Warner Losh <imp@village.org>
cc: current@FreeBSD.ORG
Subject: Re: newfs problems, more information: 
In-Reply-To: <199810192046.OAA29076@harmony.village.org>
Message-ID: <Pine.BSF.3.95.981019135157.13455E-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

ok, for one, there is magic that corrects 'c' partition boundaries under
some cases.. if 'c' stops being magic then everything may 'shift'
if you are relying on this without knowing it.

also, 'c' is special in the  case of bad144 error correction
though this presently has no real effect.
'c' special and its behaviour may change in the future in 
unpredictable ways. 
Until there is no code in the kernel that says

if (part == RAW_PART) {
     some magic occurs;
}

I personally wouldn't use it.

eventually you should be able to use wd0s1 or just wd0
instead of wd0s1c or wd0c

why use 'c'?
just make an 'a' with the same figures...

Oh yeah... 'c' exists even if there is no valid disklabel
(it's created by default...) I've seen (not recently) cases where people 
actually made a filesystem using 'c' and THEN they discoverd that there
was not actually a disklabel on the disk :-)
(I don't think this can happen any more with bruces code, but it was
a problem at one stage before he abstracted all that code from 
all the drivers)

I just get all queezy when I think of it.. :-)

It's just relying on too many magic bandaids, which I were removing with
my slice code before it was so suddenly deleted.

I just don't understand why others don't get this 'uneasy feeling about
'c''

julian

On Mon, 19 Oct 1998, Warner Losh wrote:

> In message <Pine.BSF.3.95.981019125826.13279G-100000@current1.whistle.com> Julian Elischer writes:
> : I also chastise people for it all the time :-)
> : NEVER put a filesystem on 'c'
> : (until 'c' loses all magic)
> 
> Why?  It works and I've been doing it literally for years.  What magic
> does 'c' have that would make this a bad idea?
> 
> Warner
> 


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