search for: arg_i

Hello! This really isn't so important, but it comes often in my mind, when I write documentation for functions. Writing R Extensions manual says that one should describe each element of the argument list (which is afcourse OK) in a form: \item{arg_i}{Description of arg_i.} When I started with R it really helped me that some "man pages" used \item{arg_i}{Mode. Description of arg_i.} e.g. \item{argument1}{Logical. Bla bla bla.} \item{argument2}{Integer. Bla bla bla.} \item{argument2}{Character. Bla bla bla.} Although one can most...

6 ?????? 2023 ?. 22:54:24 GMT+03:00, mikkmart via R-devel <r-devel at r-project.org> ?????: >The pattern of functions accepting other functions as inputs and >passing additional ... arguments to them is prevalent throughout >the R ecosystem. Currently, however, all such functions must one >way or another tackle the problem of inadvertently passing arguments >meant to go to

...t; #include <inttypes.h> +#include <mntent.h> #include "do_mounts.h" #include "kinit.h" @@ -199,12 +200,97 @@ mount_root(int argc, char *argv[], dev_t root_dev, const char *root_dev_name) return ret; } +int do_cmdline_mounts(int argc, char *argv[]) +{ + int arg_i; + + for (arg_i = 0; arg_i < argc; arg_i++) { + const char *fs_name, *fs_dir, *fs_type; + char *fs_opts; + unsigned long flags = 0; + char new_fs_opts[128] = { 0 }; + char *saveptr = NULL; + char *fs_opts_savedptr = NULL; + int opt_first = 1; + const char *opt; + + if (strncmp(argv[arg_...

This patch series allows user-specified mount commands to be sent in via kernel command line ("kinit_mount=...") or via an embedded /etc/fstab file. The first patch is a cleanup of a patch sent last November by San Mehat (http://web.archiveorange.com/archive/v/EazJNBMORV2U7E0coh5h); the next two are small improvements or bug fixes.

This is something I've been working on: Reworking inspection so it's not a big mess of ad hoc C code, but instead uses a well-defined domain-specific language to describe how we inspect guests. The best introduction to this is the manual page, which I include below (it's also included in patch 2/3). Rich. ---------------------------------------------------------------------- NAME

Previously posted: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html Inspection now really succeeds on a small number of simple guests. To test it out: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" Rich.

This is a more working version. Inspection (partially) succeeds on a real guest this time :-) You can test it out on a real guest (in this case, a CentOS disk image located at /tmp/centos-6.img) by doing: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" which will print lots of debugging, and at the end the

For background on this change, see: https://rwmj.wordpress.com/2015/12/06/inspection-now-with-added-prolog/ v2 was previously posted here: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html To test this patch series on a real guest, you can do: $ ./run guestfish -v -x -a /var/tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection