From owner-freebsd-fs@FreeBSD.ORG  Wed Jul 14 13:00:57 2004
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3D5E116A4CE; Wed, 14 Jul 2004 13:00:57 +0000 (GMT)
Received: from porthos.compasstg.net (ns01.europenetsystems.net
	[207.13.208.150])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1638243D3F; Wed, 14 Jul 2004 13:00:57 +0000 (GMT)
	(envelope-from mickonet@porthos.compasstg.net)
Received: by porthos.compasstg.net (Postfix, from userid 1006)
	id D917641DB2; Wed, 14 Jul 2004 07:56:54 -0500 (CDT)
Date: Wed, 14 Jul 2004 07:56:54 -0500
From: micko <micko@micko.net>
To: Greg 'groggy' Lehey <grog@FreeBSD.org>
Message-ID: <20040714125654.GA13080@micko.net>
References: <20040713213017.GA38398@micko.net>
	<20040713221302.GA63062@wantadilla.lemis.com>
	<20040714010650.GA8692@micko.net> <20040714030052.GA9508@micko.net>
	<20040714043704.GB79947@wantadilla.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040714043704.GB79947@wantadilla.lemis.com>
User-Agent: Mutt/1.4.1i
X-Operating-System: FreeBSD porthos.compasstg.net 4.7-STABLE FreeBSD
	4.7-STABLE 
cc: freebsd-fs@freebsd.org
Subject: Re: vinum ufs1 drives on freebsd 5.2.1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2004 13:00:57 -0000

> > I found the problem. Originally when I was creating the partitions on the
> > fbsd 4.x system I didn't slice up the drive, I used da0c/e. When using
> > the drive under fbsd 5.x and devfs, the system brings up da0s1c/e. Is there
> > anyway to override this behavior?
> 
> No.  Why do you want to?  And why is it a problem?
> 
> Note the warning in the man page:
> 
>      partition ``c'' represents the whole disk and should not be used
>      for any other purpose.
> 
> I'm surprised you got it to work at all.  *That*'s a bug.

I was using daXe partition, and I had to put the drives back into a 4.x system
since the 5.x was putting everything on daXs1. Can you point me to a page where
I can more info on how fbsd 5.x devfs is pull the partition info from the drives?

thanks
micko