From owner-freebsd-current  Wed Oct  9  5:11:58 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2474837B401
	for <freebsd-current@FreeBSD.ORG>; Wed,  9 Oct 2002 05:11:57 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EB58343E6A
	for <freebsd-current@FreeBSD.ORG>; Wed,  9 Oct 2002 05:11:55 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA22830;
	Wed, 9 Oct 2002 22:11:46 +1000
Date: Wed, 9 Oct 2002 22:21:51 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: Seth Hieronymus <sethh@principia.edu>,
	<freebsd-current@FreeBSD.ORG>
Subject: Re: My problems with GEOM 
In-Reply-To: <26819.1034156676@critter.freebsd.dk>
Message-ID: <20021009213450.K4967-100000@gamplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Wed, 9 Oct 2002, Poul-Henning Kamp wrote:

> In message <20021009193847.F4643-100000@gamplex.bde.org>, Bruce Evans writes:
> >On Wed, 9 Oct 2002, Poul-Henning Kamp wrote:
> >
> >> In message <OE101iKEfhe98zdoDm90001a761@hotmail.com>, "Seth Hieronymus" writes:
> >>
> >> >I think your recent commits have fixed my hang on boot with an empty
> >> >ZIP-drive.  Thank you.
> >>
> >> Cool.
> >
> >It still can't even mount root for my configurations.  This is because
> >it breaks compatibility by dropping support for the devices on the
> >first FreeBSD slice being named without a slice number (e.g., ad0a is
> >named ad0a, not ad0s<machine-dependent slice number>a).
>
> ... as discussed years back.

The maintainer of the slice code never agreed with removing the
compatibility slice and always used this feature.  Unfortunately, the
maintainer wasn't diligent enough in fixing i386-centric documentation
that says to use explicit slice numbers.

> All you have to do is edit your /etc/fstab.

Not so.  I would have to edit fstab back and forth to boot various
kernels, and would also have to use devfs or MAKEDEV to get all the
sliced devices created, and change boot loaders back and forth to
get the slice number passed in a way that is recognized by all
kernels of interest  (or change ROOTDEVNAMES back and forth) ....

Bruce


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