search for: l148

Hi! I am trying to use virt-customize to add packages to an image. However it seems that there is a problem where a resolv.conf is not being installed and thus package installation fails. The command is: virt-customize -v -x -a trusty-server-cloudimg-amd64-disk1.img --run-command "host openstack.org" I am having a hard time gathering complete output as the command seems to

...cat <&3' > > Both fail... So what's happening is that /etc/resolv.conf in the appliance never gets created. *If* /etc/resolv.conf had been created then we should see evidence that this code had been run: https://github.com/libguestfs/libguestfs/blob/master/daemon/command.c#L148-L215 (eg. the "renaming ... to ..." messages should appear). Question is why does /etc/resolv.conf not get created? On Fedora, it is created by dhclient running from appliance/init: https://github.com/libguestfs/libguestfs/blob/master/appliance/init#L88-L94 On Debian/Ubuntu that is s...

Hi, The function cummax() seems to have a bug. > x <- c(NA, 0) > storage.mode(x) <- "integer" > cummax(x) [1] NA 0 The correct result of this case should be NA NA. The mistake in [ https://github.com/wch/r-source/blob/trunk/src/main/cum.c#L130-L136] may be the reason. Best Regards, Dongcan -- Dongcan Jiang Team of Search Engine & Web Mining School of Electronic

On 03/13/2015 11:13 AM, Richard W.M. Jones wrote: > > Yes, the log indicates name resolution not working. Please try the > diagnosis steps that I outlined in: > > https://www.redhat.com/archives/libguestfs/2015-March/msg00075.html Sorry, I somehow missed the above message. $ ./run guestfish get-backend direct Here are the outputs of the /dev/tcp test, first doing: $ ./run

...image file listed above works perfectly when launched as an > openstack instance. I'm afraid our handling of /etc/resolv.conf inside the chroot is a large (and continuing) source of problems. Currently this code is run: https://github.com/libguestfs/libguestfs/blob/master/daemon/command.c#L148 There are a couple of thing you could do: - Don't rely too heavily on name resolution. - Use --firstboot* scripts instead, since they genuinely run in guest context, and should therefore work more like you expect. (and I guess a third one .. suggest a better approach to resolv.conf han...

...r` conversion restores the original value.? I don't know if this is something explicitly checked for like the `int` == 32bits assumption. [1]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/valid_utf8.h#L61 [2]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/character.c#L148 [3]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/valid_utf8.h#L106 [4]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/valid_utf8.h#L84 [5]: https://github.com/wch/r-source/blob/tags/R-3-6-3/src/main/valid_utf8.h#L69 [6]: https://github.com/wch/r-source/blob/tags/R-3-6-3/...