From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Ts'o Subject: Re: Hacking linux-utils for swap label Date: Thu, 13 Apr 2006 12:52:26 -0400 Message-ID: <20060413165226.GA20472@thunk.org> References: <443E133D.8070209@linagora.com> <20060413123619.GA3778@rain.homenetwork> <20060413163724.GA16179@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from thunk.org ([69.25.196.29]:25317 "EHLO thunker.thunk.org") by vger.kernel.org with ESMTP id S1750886AbWDMQwa (ORCPT ); Thu, 13 Apr 2006 12:52:30 -0400 To: Greg KH Content-Disposition: inline In-Reply-To: <20060413163724.GA16179@kroah.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Apr 13, 2006 at 09:37:24AM -0700, Greg KH wrote: > vol_id in the udev package is much better than blkid, as it handles more > file system types, and is easier to intregrate into other programs and > scripts (it's also availble as a library.) I would recommend it > instead. For the record, blkid is also available as a library, and it is what is used by mount and fsck to support. 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. Blkid is available on pretty much all distributions since it's been part of e2fsprogs since 2002 or so; udev is used available on all reasonably modern distro's using a 2.6 kernel. Finally, the number of filesystem types handled by the two really aren't all that different; certainly all of the major filesystem types are covered by both libraries/programs. Regards, - Ted