Displaying 8 results from an estimated 8 matches for "print_cmdlin".
Did you mean:
print_cmdline
2010 Oct 01
1
[PATCH 1/2] New internal function guestfs___print_timestamped_argv
This function generalises the existing print_cmdline used to output the qemu
command line to output any given command line, and exports it to other modules.
It also adds a timestamp to the old print_cmdline output for consistency with
guestfs___print_timestamped_message.
---
src/guestfs-internal.h | 1 +
src/launch.c | 48 +++++++++++...
2010 Oct 28
3
[PATCH 1/4] New internal function guestfs___print_timestamped_argv
This function generalises the existing print_cmdline used to output the qemu
command line to output any given command line, and exports it to other modules.
It also adds a timestamp to the old print_cmdline output for consistency with
guestfs___print_timestamped_message.
---
src/guestfs-internal.h | 1 +
src/launch.c | 48 +++++++++++...
2011 Dec 04
0
[GIT PULL] klibc minor fixes
...100644
--- a/scripts/basic/fixdep.c
+++ b/scripts/basic/fixdep.c
@@ -123,14 +123,13 @@ char *target;
char *depfile;
char *cmdline;
-void usage(void)
-
+static void usage(void)
{
fprintf(stderr, "Usage: fixdep <depfile> <target> <cmdline>\n");
exit(1);
}
-void print_cmdline(void)
+static void print_cmdline(void)
{
printf("cmd_%s := %s\n\n", target, cmdline);
}
@@ -143,7 +142,7 @@ int len_config = 0;
* Grow the configuration string to a desired length.
* Usually the first growth is plenty.
*/
-void grow_config(int len)
+static void grow_config(...
2010 Jul 05
5
[PATCH 0/3] RFC: Allow use of external QEMU process with libguestfs
This attempts to implement the idea proposed in
https://www.redhat.com/archives/libguestfs/2010-April/msg00087.html
The idea is that an externally managed QEMU (manual, or via libvirt)
can boot the appliance kernel/initrd. libguestfs can then be just told
of the UNIX domain socket associated with the guest daemon.
An example based on guestfish.
1. Step one, find the appliance kernel/initrd
2018 Jun 04
5
6.0.1-rc2 has been tagged
Hi,
The 6.0.1-rc2 release has been tagged. Testers may begin testing and
reporting results.
-Tom
2018 Apr 26
7
6.0.1-rc1 has been tagged
Hi,
I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading
binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do
so please try to do this before Friday, because I would like to tag 5.0.2-final then.
As a reminder to users and developers, May 18 is the deadline for submitting
merge requests for 6.0.1, so there is still time to get bug fixes
2018 Feb 09
0
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
...mic :: TestCases/Posix/large_allocator_unpoisons_on_free.cc
AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/mmap_limit_mb.cc
AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/new_array_cookie_with_new_from_class.cc
AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/print_cmdline.cc
AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/readv.cc
AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/shared-lib-test.cc
AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/stack-overflow.cc
AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/stack...
2018 Feb 09
2
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote:
> On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:
>>
>> There's been a lot of merges since rc1, and hopefully the tests are in
>> a better state now.
>>
>> 6.0.0-rc2 was just tagged, after r324506.
>>
>>