From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: Hacking linux-utils for swap label Date: Thu, 13 Apr 2006 10:10:42 -0700 Message-ID: <20060413171042.GA16607@kroah.com> References: <443E133D.8070209@linagora.com> <20060413123619.GA3778@rain.homenetwork> <20060413163724.GA16179@kroah.com> <20060413165226.GA20472@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from ns1.suse.de ([195.135.220.2]:59033 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S932114AbWDMRLo (ORCPT ); Thu, 13 Apr 2006 13:11:44 -0400 To: Theodore Ts'o Content-Disposition: inline In-Reply-To: <20060413165226.GA20472@thunk.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Apr 13, 2006 at 12:52:26PM -0400, Theodore Ts'o wrote: > Blkid also has the advantage that it doesn't require a modern 2.6 > kernel to function (since it isn't dependent on udev) in order to find > the device where a particular filesystem with a particular label or > UUID. I don't see that requirement anywhere in the vol_id code. It's a stand-alone binary that should work with just about any kernel version, as it just talks to the block device directly. No udev requirement at all (it just happens to live in the udev source tree for now, I think that's changing as HAL and some other utilities are starting to rely on it.) Anyway, I don't have any objection to blkid, just trying to point out another solution, instead of having the original poster try to reinvent the wheel again :) thanks, greg k-h