Subject: Re: 2.7 block ramblings (was Re: DMA for ide-scsi?)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Justin Cormack <justin@street-vision.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <1063538182.1510.78.camel@lotte.street-vision.com>
References: <1063484193.1781.48.camel@mulgrave>
	 <20030913212723.GA21426@gtf.org>
	 <1063538182.1510.78.camel@lotte.street-vision.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1063551760.14837.10.camel@dhcp23.swansea.linux.org.uk>
Mime-Version: 1.0
Date: Sun, 14 Sep 2003 16:02:41 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1029
Lines: 23

On Sul, 2003-09-14 at 12:15, Justin Cormack wrote:
> 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.

You can use UUID's for labels too if you prefer. I normally write a 
host string into my labels. What I actually want is mount by label to
develop an rpc service so I can mount by label and if the disk is in
another box NFS it 8)

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

The bootloader doesn't know. It has a bios concept of the boot device
which is really hard if at all possible to translate without things like
EDD.

-
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/