Subject: Re: 2.7 block ramblings (was Re: DMA for ide-scsi?)
From: Justin Cormack <justin@street-vision.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <20030913212723.GA21426@gtf.org>
References: <1063484193.1781.48.camel@mulgrave> 
	<20030913212723.GA21426@gtf.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 14 Sep 2003 12:15:27 +0100
Message-Id: <1063538182.1510.78.camel@lotte.street-vision.com>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1261
Lines: 29

On Sat, 2003-09-13 at 22:27, Jeff Garzik wrote:

> IMO, we need to move users from a [probe-]order-based device and bus
> enumeration to some system based on unique ids.  I'm of the opinion
> that _both_ block devices and filesystems need some sort of GUID.
> Luckily, a lot of blkdevs/fs's are already there.
> 
> If you look at current usage out there, order isn't _terribly_ important
> given today's tools (such as LABEL=).  More important IMO is figuring
> out which spindle is your boot disk, and which is your root disk.
> Red Hat handles root disks by doing LABEL= from initrd.  But discovering
> the boot disk is still largely an unsolved problem AFAIK...

LABEL= is so broken that I immediately remove it from all my redhat
systems. It is not unique at all. As soon as you plug another system
disk into your system at boot time all hell breaks loose. At least it
could have a random number in it or something.

If you need to know your bootdisk (why?) why not just get the bootloader
to tell you?

Justin


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/