Displaying 5 results from an estimated 5 matches for "ldm_volume_get_nam".
Did you mean:
ldm_volume_get_name
2018 May 10
1
[PATCH 0/1] libldm: Make libldm to parse and return volume GUID.
The result of this patch will be used by libguestfs to return drive mappings
for LDM volumes. Note, that "show volume" ldmtool command already returns
hint which is a drive letter assigned by Windows to corresponding volume.
But it is not reliable source of information. More over, in multiboot
environment it is unclear which drive letter belongs to which operating
system. Volume GUID
2018 May 10
2
[PATCH libldm v2 0/1] Make libldm to parse and return volume GUID.
v2: wrap commit message, "PATCH libldm" prefix.
The result of this patch might be used by libguestfs to return drive
mappings for LDM volumes.
Note, that "show volume" ldmtool command already returns hint which
is a drive letter assigned by Windows to corresponding volume. But
it is not reliable source of information. More over, in multiboot
environment it will be unclear
2018 May 10
2
[PATCH libldm v3 0/2] Make libldm to parse and return volume GUID.
v2: wrap commit message, "PATCH libldm" prefix.
v3: correctly initialize and free GLib resources.
The result of this patch might be used by libguestfs to return drive
mappings for LDM volumes.
Note, that "show volume" ldmtool command already returns hint which
is a drive letter assigned by Windows to corresponding volume. But
it is not reliable source of information. More
2018 May 14
3
[PATCH libldm v4 0/3] Make libldm to parse and return volume GUID.
v2: wrap commit message, "PATCH libldm" prefix.
v3: correctly initialize and free GLib resources.
v4: gtk-doc is updated to reflect presence of new volume GUID field.
The result of this patch might be used by libguestfs to return drive
mappings for LDM volumes.
Note, that "show volume" ldmtool command already returns hint which
is a drive letter assigned by Windows to
2018 May 15
12
[PATCH libldm 00/12] New API: an ability to retrieve created device-mapper devices back after they have been created.
The main goal of these patch series is to implement a new API that allows to retrieve created device-mapper devices for volumes and partitions back after they have been created.
As part of this patch:
- required libdevmapper version was bumped to 1.02. I think it is safe because it was released more then 10 years ago;
- newer version of libdevmapper allowed to simplify code base a little bit;
-