search for: lxattrlist

...; RelativePathnameList "names"], []; shortdesc = "lstat on multiple files"; longdesc = "\ This call allows you to perform the C<guestfs_lstatns> operation @@ -2694,7 +2694,7 @@ for getting extended attributes." }; { defaults with name = "lxattrlist"; added = (1, 0, 77); - style = RStructList ("xattrs", "xattr"), [Pathname "path"; StringList "names"], []; + style = RStructList ("xattrs", "xattr"), [Pathname "path"; RelativePathnameList "names"], [];...

On Tue, Oct 20, 2015 at 01:59:10PM +0200, Pino Toscano wrote: > Use RelativePathnameList as type for lists of relative paths, as used in > some listing-alike APIs. This way we can ensure absolute paths in those > lists are rejects outright. > > As a consequence, test-big-dirs.pl does not need to prepend the > directory name anymore before calling listing-alike APIs: previously

...tat /foo | grep uid: +stat /foo | grep gid: +stat /bar | grep uid: +stat /bar | grep gid: +copy-attributes /foo /bar ownership:true +stat /bar | grep uid: +stat /bar | grep gid: + +echo ----- + +setxattr user.test foo 3 /foo +setxattr user.test2 secondtest 10 /foo +setxattr user.foo another 7 /bar +lxattrlist / "foo bar" +copy-attributes /foo /bar xattributes:true +lxattrlist / "foo bar" + +echo ----- + +touch /new +chmod 0111 /new +copy-attributes /foo /new all:true mode:false +stat /new | grep mode: +stat /new | grep uid: +stat /new | grep gid: +lxattrlist / new +copy-attributes /f...

...s "foo/bar" permitted, or > > just "bar"? > > At least with *lstat*list and *readlinklist functions, the file names > are considered as relative wrt the path specified, as they are resolved > against the file descriptor of the directory. > > In case of *lxattrlist, the absolute path+name for each is built and > used as path within the guest. > > So yes, "bar", "foo/bar", and "../bar" too, should work. I think I really meant -- is it a caller bug if the parameter contains a slash in it? All the *list functions were re...

Hi, attached there is a prototype of patch for adding a new copy-attributes command. Such command would allow copy the attributes of a "file" to another, so for example in guestfish: copy-attributes foo bar permissions:true xattributes:false would only copy the permissions of foo to bar, not copying its extended attributes too. Just few notes: - my first daemon command, so

...especially in Koji), appliance start up can be slow. > +part-disk /dev/sda mbr > +mkfs ext2 /dev/sda1 > +mount /dev/sda1 / > + > +touch /foo > +touch /bar > +setxattr user.test foo 3 /foo > +setxattr user.test2 secondtest 10 /foo > +setxattr user.foo another 7 /bar > +lxattrlist / "foo bar" > +copy-attributes /foo /bar xattributes:true > +lxattrlist / "foo bar" > +EOF > + > +if [ "$(cat test.out)" != "[0] = { > + attrname: > + attrval: 2\x00 > +} > +[1] = { > + attrname: user.test > + attrval: foo &gt...

...any path at all. That is to say: is "foo/bar" permitted, or > just "bar"? At least with *lstat*list and *readlinklist functions, the file names are considered as relative wrt the path specified, as they are resolved against the file descriptor of the directory. In case of *lxattrlist, the absolute path+name for each is built and used as path within the guest. So yes, "bar", "foo/bar", and "../bar" too, should work. -- Pino Toscano

...> > > just "bar"? > > > > At least with *lstat*list and *readlinklist functions, the file names > > are considered as relative wrt the path specified, as they are resolved > > against the file descriptor of the directory. > > > > In case of *lxattrlist, the absolute path+name for each is built and > > used as path within the guest. > > > > So yes, "bar", "foo/bar", and "../bar" too, should work. > > I think I really meant -- is it a caller bug if the parameter contains > a slash in it? I...

On Fri, Mar 03, 2017 at 03:32:55PM +0100, Pino Toscano wrote: > The JNI library uses CLEANUP_FREE macros, whose functions are built in > the internal libutils. Currently, trying to use functions that use > CLEANUP_FREE variables will cause the java execution to stop with a > symbol lookup error (for guestfs_int_cleanup_free). [comment only] I wonder why our tests didn't pick this

...-get-at-the-windows-registry-in-your-windows-guests/ http://rwmj.wordpress.com/2009/10/28/libhivex-windows-registry-hive-extractor-library/ - OCaml bindings for virt-inspector - RELAX NG schema for virt-inspector - New APIs: utimens, vfs_type, truncate, truncate_size, lchown, lstatlist, lxattrlist, readlinklist, case_sensitive_path, find0, mkfs_b, mke2journal, and more ... - New program: OCaml viewer http://rwmj.wordpress.com/2009/09/29/graphical-virt-df/ - Allow stdout to be redirected when running guestfish remotely (Matt Booth). - Remove requirement for vmchannel support in qe...

Mostly like StringList (so it can used in current StringList parameters), but checking client- and daemon-side that the elements are relative paths. --- generator/bindtests.ml | 3 ++- generator/c.ml | 29 ++++++++++++++++++++++++----- generator/csharp.ml | 4 ++-- generator/daemon.ml | 20 ++++++++++++++++++-- generator/erlang.ml | 2 +- generator/fish.ml |

Mostly like StringList (so it can used in current StringList parameters), but checking client- and daemon-side that the elements are file names. --- generator/bindtests.ml | 3 ++- generator/c.ml | 29 ++++++++++++++++++++++++----- generator/csharp.ml | 4 ++-- generator/daemon.ml | 20 ++++++++++++++++++-- generator/erlang.ml | 2 +- generator/fish.ml | 10

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

...STREQ (mountpoint, "/"); if (!root_mounted && !is_root) { reply_with_error ("mount: you must mount something on / first"); diff --git a/daemon/xattr.c b/daemon/xattr.c index d16939f..926baf0 100644 --- a/daemon/xattr.c +++ b/daemon/xattr.c @@ -410,7 +410,7 @@ do_lxattrlist (const char *path, char *const *names) fprintf (stderr, " %zu: special attrval = %s\n", k, entry[0].attrval.attrval_val); for (i = 1; k+i < ret->guestfs_int_xattr_list_len; ++i) { - if (strcmp (entry[i].attrname, "") == 0) + if...

...StringList (Filename, "names")], []; shortdesc = "lstat on multiple files"; longdesc = "\ This call allows you to perform the C<guestfs_lstatns> operation @@ -1169,7 +1169,7 @@ for getting extended attributes." }; { defaults with name = "lxattrlist"; added = (1, 0, 77); - style = RStructList ("xattrs", "xattr"), [Pathname "path"; FilenameList "names"], []; + style = RStructList ("xattrs", "xattr"), [String (Pathname, "path"); StringList (Filename, "names&quo...

Very large but mechanical change to the generator. Rich.

The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.

Split up the huge generator/actions.ml into several smaller files. Rich.