Fixed in Karmic where tools use libblkid from util-linux
** Changed in: e2fsprogs (Ubuntu)
Status: Confirmed = Fix Released
--
tools should use libvolume-id instead of libblkid
https://bugs.launchpad.net/bugs/235165
You received this bug notification because you are a member of Ubuntu
On Wed, 2009-04-15 at 19:16 +, Mikael Ståldal wrote:
blkid has the bad practice of updating a file in /etc (blkid.tab). This
is annoying and against the spirit of a
href=http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION;FHS/a.
If you test the packages in my
Already way ahead of you, this work has been done upstream but in the
opposite direction - we've merged vol_id and blkid together into a
libblkid library shipped by util-linux-ng. Packages exist in my PPA for
testing, and we'll begin using this in karmic
--
tools should use libvolume-id instead
blkid has the bad practice of updating a file in /etc (blkid.tab). This
is annoying and against the spirit of a
href=http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION;FHS/a.
Can you fix that while you're at it?
--
tools should use libvolume-id instead of libblkid
Changing status to confirmed; apparently everyone agrees that something
should be done.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Confirmed
--
tools should use libvolume-id instead of libblkid
https://bugs.launchpad.net/bugs/235165
You received this bug notification because you
For every bug report someone files where their ext3 filesystem is
reported as a FAT filesystem, somebody else files a bug where their FAT
filesystem is reported as an ext3 filesystem.
Of course, that doesn't mean common sense could be applied. The
priority should always be towards our favoured
See attached patch from SuSE
** Attachment added: e2fsprogs-libvolume_id-support.patch
http://launchpadlibrarian.net/14904049/e2fsprogs-libvolume_id-support.patch
--
tools should use libvolume-id instead of libblkid
https://bugs.launchpad.net/bugs/235165
You received this bug notification
PS, I'll note the original bug that started this chain was started
because libvolume_id gave the wrong answer, erroneously reporting an
ext3 filesystem as FAT. I've tried working with the vol_id folks
before, and they are not interested in patches to make libvolume_id give
more correct answers,
Note that libvolume_id BREAKS ext4 support. For that reason the
e2fsprogs patch HAS NOT BEEN ACCEPTED IN MAINLINE.
I am telling people who are using ubuntu to back out the changes in
mount that switch it to use volume_id, as they are problematic for ext4,
and recompile mount if they want to use
And that would leave us with the situation where depending which tool
you pass the UUID to, you'll get a different block device.
We don't want two libraries for doing the exact same thing, in different
ways. We want one library only.
Right now, the library that has the most patches to use it is
When I have submitted patches in the past, to fix problems such as the one that
kicked off this thread (an ext3 filesystem erroneously getting reported as a
FAT filesystem), it was rejected by the libvolume_id maintainer.
I've been very busy trying to get ext4 production ready, and decided I
11 matches
Mail list logo
