similar to: Exposing environment variables to Facter

--- dib/Makefile.am | 5 ++- dib/cmdline.ml | 49 +++++++++++++++++++++--- dib/cmdline.mli | 51 +++++++++++++++++++++++++ dib/dib.ml | 113 ++++++++++++++++++++++++++++++-------------------------- 4 files changed, 158 insertions(+), 60 deletions(-) create mode 100644 dib/cmdline.mli diff --git a/dib/Makefile.am b/dib/Makefile.am index 0786d64..ad1fd6a 100644 --- a/dib/Makefile.am +++

于 2014年07月08日 12:06, Eric Blake 写道: > On 07/07/2014 10:02 PM, Qiang Guan wrote: >> Hi , >> >> Is there anyway to get uuid info inside a lxc container which is created >> by libvirt_lxc? >> >> For kvm, we can use dmidecode or lshw to get this info inside vm. Is >> there any tools >> to do this thing for libvirt lxc? > Per the docs: >

Hello, I'm having trouble calling rsync from java on windows vista with cygwin installed. Its strange as pasting the exact same command into a command shell works fine. My test java call looks like this. * String[] envVars = {"PATH=c:/cygwin/bin;%PATH%"}; File workingDir = new File("c:/cygwin/bin/"); Process p = Runtime.getRuntime().exec("c:/cygwin/bin/rsync.exe

--- dib/dib.ml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/dib/dib.ml b/dib/dib.ml index 4a0c9ee..06a1f67 100644 --- a/dib/dib.ml +++ b/dib/dib.ml @@ -467,7 +467,7 @@ let main () = let elements = if cmdline.is_ramdisk then [cmdline.ramdisk_element] @ elements else elements in - message (f_"Elements: %s") (String.concat " "

Hi, I''ve tried to to exec function in puppet for enabling module for apache. Here is the code that I am using: class apache::mod { exec { "a2enmod" : command => "a2enmod proxy_http", path => "/usr/sbin/", notify => Class["apache::service"], require => Class["apache::install"], } } But in agent I''m getting the

Hi , Is there anyway to get uuid info inside a lxc container which is created by libvirt_lxc? For kvm, we can use dmidecode or lshw to get this info inside vm. Is there any tools to do this thing for libvirt lxc? Thanks for any help~ -- ------------ Jackie Best Regards

d-i-b 2.0 is written in Python, and thus it passes the information about the interpreter used for it (sys.executable) to the scripts that need it; this mechanism replaces the old discovery of what is the default Python interpreter in the system. Since we are not Python-based, look for 'python' and use it as default interpreter, with the --python command line option to set a different one.

Hi, this series start to implement some of the changes needed to support d-i-b 2.0; normal VM distro builds seem to work correctly, ramdisk builds are still broken and require more efforts. Thanks, Pino Toscano (5): dib: implement get_image_element_array stuff dib: export IMAGE_BLOCK_DEVICE_WITHOUT_PART dib: extract get_required_tool out of require_tool dib: require a Python interpreter

virt-dib is a new tool to run the elements of diskimage-builder using libguestfs. --- More or less stable now, although with debug stuff here and there; needs initial review, for being included. I would like to have it reviewed at this point, so it can be broadly used. TODO items open: - improve the documentation - review - getting more testing (although it has been successfully tested for

virt-dib is a new tool to run the elements of diskimage-builder using libguestfs. --- .gitignore | 5 + Makefile.am | 3 +- appliance/packagelist.in | 12 + configure.ac | 1 + dib/Makefile.am | 144 ++++++++ dib/cmdline.ml | 242 +++++++++++++ dib/dib.ml | 920 +++++++++++++++++++++++++++++++++++++++++++++++

Instead of running them before lanching the appliance with the disks and then uploading the result after root.d hooks run, mount the root in the local temporary directory using FUSE and then run the hooks on the guest. Other than being closer to what diskimage-builder does, it also avoids issues with the extra-data.d scripts assuming to find things already, and we don't error out while trying

virt-dib is a new tool to run the elements of diskimage-builder using libguestfs. --- Work in progress (debug stuff here and there), although I've submitting it for initial review, for being included later when polished for good. TODO items open: - move Uname from builder to mllib - improve the documentation - review - getting more testing (although it has been successfully tested for

Hi, this series improves virt-dib, adding some upstream changes, and refactoring the handling of output formats. Thanks, Pino Toscano (6): dib: clear up "already provided" message dib: add --checksum dib: pass custom mkfs options after the filesystem type dib: refactor output formats handling dib: clarify "output:" lines in --machine-readable documentation dib:

virt-dib is a new tool to run the elements of diskimage-builder using libguestfs. --- I would like to have it reviewed at this point, so it can be used. Documentation and code can be improved and polished following feedback. .gitignore | 5 + Makefile.am | 3 +- appliance/packagelist.in | 7 + configure.ac | 1 + dib/Makefile.am | 144

At Tue, 08 Jul 2014 12:19:40 +0800, Qiang Guan wrote: > > > 于 2014年07月08日 12:06, Eric Blake 写道: > > On 07/07/2014 10:02 PM, Qiang Guan wrote: > >> Hi , > >> > >> Is there anyway to get uuid info inside a lxc container which is created > >> by libvirt_lxc? > >> > >> For kvm, we can use dmidecode or lshw to get this info inside

Using "Sys.getenv()", I got a list of 380 environment variables... Now I open a new R session, how do I set those environment variables in my new R session using "Sys.setenv()"? There is no batch function for "Sys.setenv()"? Is there an import/export environment variables function? Basically I want to export all the environment variables from one R session and

Move the OCaml binding to C _exit to an own module. Just code motion, adapting v2v in the process. --- docs/C_SOURCE_FILES | 2 +- mllib/Makefile.am | 5 ++++- mllib/exit-c.c | 33 +++++++++++++++++++++++++++++++++ mllib/exit.ml | 19 +++++++++++++++++++ mllib/exit.mli | 20 ++++++++++++++++++++ v2v/Makefile.am | 1 - v2v/changeuid-c.c | 33

Thanks for the interesting puzzle to crunch! Looking at these few bread-crumbs, I wager an educated guess that this loops in `sendcmd()` (where CLI child processes talk to a daemonized copy which tracks the timers for events), around here: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 for the daemon and here for the child:

Thanks for the interesting puzzle to crunch! Looking at these few bread-crumbs, I wager an educated guess that this loops in `sendcmd()` (where CLI child processes talk to a daemonized copy which tracks the timers for events), around here: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 for the daemon and here for the child:

Hi, I run into problems with the ipaddress fact using the latest Facter gem (1.6.4, 1.6.5) on SLES11. The versions and gems I use work perfectly fine on SLES10 SP3. The problem: running "facter" without arguments results in an error, even though the erroring fact "ipaddress" is ok. test:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL