Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f34IjLR28174 for linux-xfs-outgoing; Wed, 4 Apr 2001 11:45:21 -0700 Received: from eem12.resnet.cornell.edu (eem12.resnet.cornell.edu [128.253.247.185]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f34IjKM28171 for ; Wed, 4 Apr 2001 11:45:20 -0700 Received: (from eem12@localhost) by eem12.resnet.cornell.edu (8.11.2/8.11.2) id f34IjQq01551; Wed, 4 Apr 2001 14:45:26 -0400 Date: Wed, 4 Apr 2001 14:45:25 -0400 From: Ed McKenzie To: Steve Lord Cc: linux-xfs@oss.sgi.com Subject: Re: XFS volume labels Message-ID: <20010404144525.C1267@eem12.resnet.cornell.edu> References: <200104041832.f34IW9V01300@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104041832.f34IW9V01300@jen.americas.sgi.com>; from lord@sgi.com on Wed, Apr 04, 2001 at 01:32:09PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Apr 04, 2001 at 01:32:09PM -0500, Steve Lord wrote: > Mount by label is all user space, there is no kernel code involved, Ah. There was talk on lkml about allowing the kernel to find the root fs by UUID or label, so I assumed all of this was done in the kernel. > beyond reading data out the block device interface to look for the > magic numbers. You need a version of the mount command with this > support in it for the code to function. > > I am using mount-2.10m-6 but I have to admit I have not tried a mount > by label recently. 2.10r-4 from Wolverine here. Looking at the source, it appears XFS label support is already implemented. I'm investigating. -ed