search for: tar_out

While creating my first guestfish script I noticed an inconsistency in the guestfish(1) man page. The option tgz-out references "tar_out", which does not exist, instead its called "tar-out". The same is true for tgz-in/tar_in. After a quick grep in the code its not clear to me how to resolve this issue. Olaf

...+++- 2 files changed, 22 insertions(+), 6 deletions(-) diff --git a/daemon/tar.c b/daemon/tar.c index d6f8f2f..68af749 100644 --- a/daemon/tar.c +++ b/daemon/tar.c @@ -311,7 +311,7 @@ make_exclude_from_file (char *const *excludes) /* Takes optional arguments, consult optargs_bitmask. */ int do_tar_out (const char *dir, const char *compress, int numericowner, - char *const *excludes) + char *const *excludes, int xattrs, int selinux) { CLEANUP_FREE char *buf = NULL; struct stat statbuf; @@ -349,6 +349,12 @@ do_tar_out (const char *dir, const char *compress, int numeric...

...utput_format_docker.ml @@ -38,7 +38,8 @@ let docker_run_fs (g : Guestfs.guestfs) _ temp_dir = | Some t -> t in message (f_"Importing the image to docker as '%s'") docker_target; let dockertmp = Filename.temp_file ~temp_dir "docker." ".tar" in - g#tar_out ~excludes:[| "./sys/*"; "./proc/*" |] "/" dockertmp; + g#tar_out ~excludes:[| "./sys/*"; "./proc/*" |] ~xattrs:true ~selinux:true + "/" dockertmp; let cmd = [ "sudo"; "docker"; "import"; dockertmp; dock...

...ashfs filesystem out of a path > in the guest. It can be configured to exclude paths based on patterns, > and to select which compression use for the filesystem. > > The advantage of running mksquashfs directly in the appliance is that > ownerships are properly saved, as opposed to tar_out + local untar. I'm fairly sure this was proposed before as an API, but I cannot find that right now. Was rejected because mksquashfs doesn't support streaming output. However I'm fine with this, although perhaps there should be a warning in the longdesc saying that there may be probl...

...ines. It is written in python and uses libguestfs pretty heavily to manipulate ISOs and disks. Someone reported an error against Oz here: https://github.com/clalancette/oz/issues/140 There are some more details in the issue, but it essentially looks like something happened during libguestfs tar_out: RuntimeError: /dev/fd/13: error in chunked encoding Has anyone seen this before? Any idea what this is about? If you want to comment, I would appreciate it if you could comment in the issue itself. Thanks, Chris

...; "/tar_in"]; ["tar_in"; "../data/helloworld.tar"; "/tar_in"]; @@ -2828,7 +2831,8 @@ I<uncompressed> tar file) into C<directory>. To upload a compressed tarball, use C<guestfs_tgz_in> or C<guestfs_txz_in>."); - ("tar_out", (RErr, [String "directory"; FileOut "tarfile"], []), 70, [], + ("tar_out", (RErr, [String "directory"; FileOut "tarfile"], []), 70, + [Cancellable], [], "pack directory into tarfile", "\ @@ -2838,7 +2842,8 @@ it...

https://bugzilla.redhat.com/show_bug.cgi?id=847880 https://bugzilla.redhat.com/show_bug.cgi?id=847881 This patch series adds various optional arguments to the tar-in and tar-out commands. Firstly (1/7) an optional "compress" flag is added to select compression. This makes the calls tgz-in/tgz-out/txz-in/txz-out deprecated, and expands the range of compression types available.

...t/optargs-rsync_in.h \ include/guestfs-gobject/optargs-rsync_out.h \ include/guestfs-gobject/optargs-set_e2attrs.h \ + include/guestfs-gobject/optargs-setfiles.h \ include/guestfs-gobject/optargs-syslinux.h \ include/guestfs-gobject/optargs-tar_in.h \ include/guestfs-gobject/optargs-tar_out.h \ @@ -187,6 +188,7 @@ guestfs_gobject_sources= \ src/optargs-rsync_in.c \ src/optargs-rsync_out.c \ src/optargs-set_e2attrs.c \ + src/optargs-setfiles.c \ src/optargs-syslinux.c \ src/optargs-tar_in.c \ src/optargs-tar_out.c \ diff --git a/src/MAX_PROC_NR b/src/MAX_PROC_NR inde...

...er information, see https://bugzilla.redhat.com/show_bug.cgi?id=788642 + <https://bugzilla.redhat.com/show_bug.cgi?id=788642> New APIs diff --git a/po/POTFILES b/po/POTFILES index 60887dc..d961ac1 100644 --- a/po/POTFILES +++ b/po/POTFILES @@ -167,6 +167,7 @@ gobject/src/optargs-tar_out.c gobject/src/optargs-tune2fs.c gobject/src/optargs-umount.c gobject/src/optargs-umount_local.c +gobject/src/optargs-xfs_admin.c gobject/src/optargs-xfs_growfs.c gobject/src/session.c gobject/src/struct-application.c diff --git a/src/MAX_PROC_NR b/src/MAX_PROC_NR index 71627d7..aef2e27 100644...

...path > > in the guest. It can be configured to exclude paths based on patterns, > > and to select which compression use for the filesystem. > > > > The advantage of running mksquashfs directly in the appliance is that > > ownerships are properly saved, as opposed to tar_out + local untar. > > I'm fairly sure this was proposed before as an API, but I cannot find > that right now. Was rejected because mksquashfs doesn't support > streaming output. Yes, and it does not have any streaming for input either, so things like `cat my.tar | mksquashfs - m...

...s, TestResultString ( @@ -202,7 +202,7 @@ I<gzip compressed> tar file) into F<directory>." }; { defaults with name = "tgz_out"; added = (1, 0, 3); style = RErr, [Pathname "directory"; FileOut "tarball"], []; - deprecated_by = Some "tar_out"; + deprecated_by = Replaced_by "tar_out"; cancellable = true; shortdesc = "pack directory into compressed tarball"; longdesc = "\ @@ -212,7 +212,7 @@ it to local file C<tarball>." }; { defaults with name = "set_e2label";...

On Tue, Feb 14, 2017 at 09:12:07AM +0100, Pino Toscano wrote: > Add a new 'excludes' optional argument to copy-out, passing it straight > to tar-out: this way it is possible to exclude files when extracting a > directory from the guest. > --- > generator/actions.ml | 16 ++++++++++++++-- > gobject/Makefile.inc | 2 ++ > lib/copy-in-out.c | 13 ++++++++++--- > 3

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:

...w API to create a new squashfs filesystem out of a path in the guest. It can be configured to exclude paths based on patterns, and to select which compression use for the filesystem. The advantage of running mksquashfs directly in the appliance is that ownerships are properly saved, as opposed to tar_out + local untar. --- appliance/packagelist.in | 2 + daemon/Makefile.am | 1 + daemon/squashfs.c | 150 +++++++++++++++++++++++++++++++++++++++++++++++ generator/actions.ml | 26 ++++++++ gobject/Makefile.inc | 2 + lib/MAX_PROC_NR | 2 +- 6 files changed, 182...

Here is a preliminary fix for this bug. I'm running the test suite on this now. Rich.

Hi, this patch series does changes mostly in virt-dib, few bug fixes and a couple of new features (mostly implemented upstream already). In addition, one new API is added, and a new optional argument for an existing API is added (the latter is not needed, but could be useful anyway). Thanks, Pino Toscano (10): dib: fix listing envvars in fake-sudo dib: source dib "die" script in

We can use the setfiles(8) command to relabel the guest filesystem, even though we don't have a policy loaded nor SELinux enabled in the appliance kernel. This also deprecates or removes the old and broken SELinux support. This patch isn't quite complete - I would like to add some tests to the new API. I'm posting here to garner early feedback. Rich.

v1 -> v2: - Add simple test of the setfiles API. - Use SELinux_relabel module in virt-v2v (instead of touch /.autorelabel). - Small fixes. Rich.

This is a follow-up to the other generator changes in: https://www.redhat.com/archives/libguestfs/2017-February/msg00217.html Rich.

I'm currently working on gobject bindings for libguestfs. I haven't got as far as compiling anything yet, but I've attached the C header for initial review. Matt -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 -------------- next part -------------- An embedded and