[PATCH] libvolume_id fixes for solaris
Kay Sievers
kay.sievers at vrfy.org
Tue Mar 7 09:49:32 PST 2006
On Tue, Mar 07, 2006 at 09:05:50AM -0800, Artem Kachitchkine wrote:
>
> >This will result in an external use of the vol_id binary provided by udev
> >on Linux. We will no longer use libvolume_id code inside of HAL.
>
> Good to know. Do you have an estimate when this might happen?
Oh, I hope soon (next weeks), but we can leave the code in the tree, as
long as you need it, it's just if Linux does not use it anymore you may
need to care about porting possible fixes to it. :)
Again, if it helps you, go ahead and commit what you need...
> But if it's inevitable, I'd better start cranking out some code now. Thanks
> for the comments and never mind about the patch.
How would that possibly look like for Solaris? On Linux it looks like
this and we will probably just use that output (only needed for a few
cases, cause the event from the kernel, which is tunneled through udev
usually contains exactly that data already)
$ /sbin/vol_id -x /dev/sda2
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=067972bb-8f72-4946-9e44-a3799ca6d8b3
ID_FS_LABEL=root
ID_FS_LABEL_SAFE=root
/sbin/vol_id -x /dev/sda1
ID_FS_USAGE=other
ID_FS_TYPE=swap
ID_FS_VERSION=2
ID_FS_UUID=
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
/sbin/vol_id -x /dev/sda4
ID_FS_USAGE=filesystem
ID_FS_TYPE=ntfs
ID_FS_VERSION=3.1
ID_FS_UUID=C4C407EEC407E212
ID_FS_LABEL=XP
ID_FS_LABEL_SAFE=XP
Best,
Kay
More information about the hal
mailing list