On Fri, Dec 21, 2012 at 04:55:09PM +0000, Matthew Garrett wrote: > On Fri, Dec 21, 2012 at 04:37:59PM +0000, Richard W.M. Jones wrote: > > On Fri, Dec 21, 2012 at 04:22:47PM +0000, Matthew Garrett wrote: > > > On Fri, Dec 21, 2012 at 10:49:19AM -0500, Don Dutile wrote: > > > > fyi: libexec has been critical to virtualization for quite some time... > > > > I think Don is referring to the helper binaries that go into > > /usr/libexec: > > > > $ rpm -ql qemu-common | grep libexec > > /usr/libexec/qemu-bridge-helper > > $ rpm -ql libvirt-daemon | grep libexec > > /usr/libexec/libvirt_iohelper > > /usr/libexec/libvirt_lxc > > /usr/libexec/libvirt_parthelper > > Is the path user visible in any way? Yes & no. The iohelper/parthelper binaries are not user visible things. They're purely internal helpers libvirt uses. The libvirt_lxc binary does appear in the XML <emulator>/usr/libexec/libvirt_lxc</emulator>. The libvirt_lxc binary is the host-side helper, akin to /bin/qemu-system-x86_64 in QEMU/KVM world. We put it under /usr/libexec though because it isn't a binary end users will ever directly invoke. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
