similar to: Release request for the new version of libldm

? Thank you. It will help me a lot if there is a new release version? > ? 2020?11?3??19:40?Richard W.M. Jones <rjones at redhat.com> ??? > ?On Tue, Nov 03, 2020 at 07:06:49PM +0800, zhang yuxing wrote: >> Hi, Mr.Rich: >> First of all, thank you very much for your help in the following question, >> which perfectly solved the problem in my project. >>

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

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

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

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

Two simple build fixes for libldm. Well, the first isn't a build fix as such, but a code improvement. Rich.

--- configure.ac | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index 469ea96..0e7e2ea 100644 --- a/configure.ac +++ b/configure.ac @@ -85,14 +85,14 @@ PKG_CHECK_MODULES([GIO_UNIX], [gio-unix-2.0 >= 2.32.0], ] ) -PKG_CHECK_MODULES([ZLIB], [zlib >= 1.2.5], +PKG_CHECK_MODULES([ZLIB], [zlib >= 1.2], [

Hi, Mr. Rich. I am sorry that I left too little information in the last email because I edited with my mobile phone. I wrote about my first question in the following link. https://rwmj.wordpress.com/2010/11/15/libguestfs-inspection-now-lists-windows-apps/ 2nd. Question After I call the mount_local() function in guestfs.py to operate on a disk, I hope to umount it. After calling the

The commit fixes the bug in the code which inspects partition table entries in order to find LDM Metadata partion: _read_privhead_gpt function in ldm.c always calls gpt_get_pte function with 0 (zero) as a second argument which causes the described bug. --- src/ldm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ldm.c b/src/ldm.c index 4897de9..943f095 100644 ---

How to reproduce: 1. Extract test images from test/data/ldm-data.tar.xz 2. losetup --show -f test/data/ldm-2003r2-simple-1.img Let's assume image file was associated with /dev/loop0 3. ldmtool -d /dev/loop0 create all Result: One LDM volume which contains all required components on the associated loop device will be mapped but application crashes on further attempt to do the same for

How to reproduce: 1. Extract test images from test/data/ldm-data.tar.xz 2. losetup --show -f test/data/ldm-2003r2-simple-1.img Let's assume image file was associated with /dev/loop0 3. ldmtool -d /dev/loop0 create all Result: One LDM volume which contains all required components on the associated loop device will be mapped but application crashes on further attempt to do the same for

v1 was here: https://www.redhat.com/archives/libguestfs/2018-May/msg00058.html v2: - more correct explanation of a crash reason. Mykola Ivanets (1): Fix crash while creating mapper for a volume which lacks of partitions. src/ldm.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- 2.17.0

On Wed, Jan 11, 2012 at 03:10:35AM -0800, mdbooth wrote: > Remove generated file from source control, and don't barf when it doesn't exist > while bootstrapping. > > You can merge this Pull Request by running: > > git pull https://github.com/mdbooth/libguestfs build > > Or you can view, comment on it, or merge it online at: > >

This is just an initial version of the patch, not to be applied. It implements just the diskgroup functions, ie. corresponding to these ldmtool commands: * ldmtool scan * ldmtool show diskgroup <guid> I have chosen yajl as the JSON parsing library (don't worry, this is optional). You will also, of course, need ldmtool which is not packaged in anything except Fedora. Rich.

On Wed, Dec 21, 2016 at 04:30:25PM +0000, Devloo, Ivan wrote: > Hi Sir, > > I'd like to install the ldmtool on Redhat linux 7. > > Any reason why it is not in the yum repository. > > Many thanks for your feedback, It's not available in RHEL or EPEL. https://admin.fedoraproject.org/pkgdb/package/rpms/libldm/ You'll have to add it:

Here is an update to the patch posted yesterday. The changes are: (1) Don't use inline (for mdbooth). (2) Added a comment to HACKING (for mdbooth). (3) Check for old-style and new-style glibc functions and use whatever is available (for danpb). (4) Removed the old shell_quote function instead of just commenting it out. Can anyone decode from Uli's message[1] whether these new

On Tue, Sep 03, 2013 at 09:29:49AM -0600, Mike Latimer wrote: > Hi, I'll make some advisory comments, but you really need to talk to Matt Booth (CC'd - or mdbooth on #libguestfs). > I have recently been looking into virt-v2v, and noticed the mention > of an upcoming rewrite in a few places. Is there a roadmap or post > someplace that describes the future of this project?

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; -

The ELF NEEDED are used to determine guestfsd's library dependencies with help from the dynamic linker and the package manager. This was prompted by Debian bug #972241 which was caused by a libtirpc package renaming in Debian/unstable because the SONAME had been changed. --- appliance/Makefile.am | 26 ++++++++++++++++- appliance/packagelist.in | 62

Forgive me if this is the wrong area to ask this question. I'm happy to inquire to a diff list if that's better. From: http://libguestfs.org/ "Downloads For source see the downloads directory. In Fedora or Red Hat Enterprise Linux: sudo yum install libguestfs-tools On Debian/Ubuntu: sudo apt-get install libguestfs-tools Open a disk image: guestfish --ro -i -a disk.img Other