search for: cap_from_text

.... Thanks: Cédric Bosdonnat --- m4/guestfs_daemon.m4 | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/m4/guestfs_daemon.m4 b/m4/guestfs_daemon.m4 index 522cd5f0e..52079950a 100644 --- a/m4/guestfs_daemon.m4 +++ b/m4/guestfs_daemon.m4 @@ -93,15 +93,13 @@ AC_CHECK_LIB([cap],[cap_from_text],[ ], []) ],[AC_MSG_WARN([Linux capabilities library (libcap) not found])]) -dnl hivex library (highly recommended) -dnl This used to be a part of libguestfs, but was spun off into its -dnl own separate upstream project in libguestfs 1.0.85. +dnl hivex library (required) PKG_CHECK_MODULES(...

...+ { + cap_t running_cap; + if(cap_string == NULL) + fatal("irix_set_cap received NULL for input!"); + if(sysconf(_SC_CAP) != 0) { + debug("irix_set_cap: setting capability to %s",cap_string); + running_cap=cap_from_text(cap_string); + if(running_cap != NULL) { + if(cap_set_proc(running_cap) != 0) + fatal("Unable to set the process capability " + "set to %s!",cap_string); +...

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.

1.6.1 svn 190575: CC="cc" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" menuselect make[1]: Entering directory `/home/asterisk/rpmbuild/BUILD/asterisk-1.6.1/menuselect' gcc -m64 -march=native -mtune=native -floop-interchange -floop-strip-mine -floop-block -c -o

.... yes checking for magic_file in -lmagic... yes checking magic.h usability... yes checking magic.h presence... yes checking for magic.h... yes checking for acl_from_text in -lacl... yes checking sys/acl.h usability... yes checking sys/acl.h presence... yes checking for sys/acl.h... yes checking for cap_from_text in -lcap... yes checking sys/capability.h usability... yes checking sys/capability.h presence... yes checking for sys/capability.h... yes checking for LIBVIRT... yes checking for LIBXML2... yes checking for xmlBufferDetach... yes checking for LIBCONFIG... yes checking for HIVEX... yes checking for...

Two (not related to each other) refactorings: Patches 1-12 split configure.ac into smaller files using the m4_include mechanism. Patches 13-15 split out parts of guestfs.pod (ie. guestfs(3)) into three new manual pages: guestfs-hacking(3) - how to extend and contribute to libguestfs guestfs-internals(3) - architecture and internals guestfs-security(3) - security and CVEs Patch 16 is a

Hi Rich Yes Rich I have tried libguesftfs on powerpc and it was working fine.For some reason i had to format my hard disk and now when I'm again compiling it,I'm getting following error.... Below is the status of configure .. This is how we have configured the optional components for you today: Daemon .............................. yes Appliance ........................... yes QEMU

Split up the huge generator/actions.ml into several smaller files. Rich.

The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..0943bf305 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-M UI,

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...