search for: readlinklist

...[Pathname "path"; RelativePathnameList "names"], []; optional = Some "linuxxattrs"; shortdesc = "lgetxattr on multiple files"; longdesc = "\ @@ -2719,7 +2719,7 @@ for getting standard stats." }; { defaults with name = "readlinklist"; added = (1, 0, 77); - style = RStringList "links", [Pathname "path"; StringList "names"], []; + style = RStringList "links", [Pathname "path"; RelativePathnameList "names"], []; shortdesc = "readlink on multiple file...

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

...t; elements (and only their size was checked). > > > > Are these all relative pathnames, or are they in fact just filenames > > without 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&...

...contained only invalid > > elements (and only their size was checked). > > Are these all relative pathnames, or are they in fact just filenames > without 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 &qu...

...ze was checked). > > > > > > Are these all relative pathnames, or are they in fact just filenames > > > without 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. >...

...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 qemu (horray!) a...

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

...ed (use guestfs-browser instead). - New C API test type 'InitScratchFS' makes the tests run a little more quickly. - Excluded packages in the appliance are now listed in a separate file appliance/excludelist.in, and can be customized per-distro. Bugs fixed - 663407 readlink and readlinklist returns /sysroot/ in some paths - 661280 virt-rescue: panic when shutting down: "/sbin/reboot: No such file or directory" - 657499 checksum: wrong check sum type causes umount to fail - 655554 Whole disk paths are not made canonical by virt-inspector - 654638 openssl updated to 1.0.0b...

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 |

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

If we want to permit more than 255 drives to be added, then we will have to add the disks to the same virtio-scsi target using different unit (LUN) numbers. Unfortunately SCSI LUN enumeration in the Linux is not deterministic (eg. two disks with target=0, lun=[0,1] can be enumerated as /dev/sda or /dev/sdb randomly). Dealing with that will require some very complex device name translation on the

...thname, "path"); StringList (Filename, "names")], []; optional = Some "linuxxattrs"; shortdesc = "lgetxattr on multiple files"; longdesc = "\ @@ -1194,7 +1194,7 @@ for getting standard stats." }; { defaults with name = "readlinklist"; added = (1, 0, 77); - style = RStringList "links", [Pathname "path"; FilenameList "names"], []; + style = RStringList "links", [String (Pathname, "path"); StringList (Filename, "names")], []; shortdesc = "readlink on...

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.