similar to: [PATCH] inspect: improve canonical_mountpoint implementation

For example, converts "///usr//local//" -> "/usr/local". --- src/inspect-fs-unix.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c index a1a757c..0fea9c8 100644 --- a/src/inspect-fs-unix.c +++ b/src/inspect-fs-unix.c @@ -89,6 +89,7 @@ static char *resolve_fstab_device

On Tuesday, 6 December 2016 09:46:25 CET Richard W.M. Jones wrote: > For example, converts "///usr//local//" -> "/usr/local". > --- > src/inspect-fs-unix.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 52 insertions(+) > > diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c > index a1a757c..0fea9c8 100644 > ---

Non-Linux Unix guests may have static devices for CDs, so make sure to skip them when reading /etc/fstab. This is the same as done for /dev/fdN devices, i.e. floppy devices. --- lib/inspect-fs-unix.c | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/inspect-fs-unix.c b/lib/inspect-fs-unix.c index 7e940d6..9b6bfbf 100644 --- a/lib/inspect-fs-unix.c +++ b/lib/inspect-fs-unix.c @@ -1305,6

Fixes RHBZ#1113153. --- src/inspect-fs-unix.c | 240 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 240 insertions(+) diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c index 2abbf24..6dfc299 100644 --- a/src/inspect-fs-unix.c +++ b/src/inspect-fs-unix.c @@ -96,6 +96,9 @@ static char *resolve_fstab_device (guestfs_h *g, const char *spec,

Adds support for systemd .mount files, uses Augeas to extract mount points. Fixes RHBZ#1113153. Maros Zatko (1): inspection: add support for systemd .mount files src/inspect-fs-unix.c | 240 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 240 insertions(+) -- 1.9.3

This is the (incomplete) patch which reimplements inspection APIs in the daemon. All ‘XXX’s in this patch indicate areas which are not yet implemented or need further work. Rich.

Regular EFI disks have /EFI on the first (VFAT) partition, but they are not installers. Fix this by only considering something to be an installer if it has a single partition (or whole disks like ISOs). Implementing this is quite complex since when checking a filesystem, we don't have information about whether we are even looking at a partition, nor about whether it's the first partition

Define the types which will be used to communicate between the different parts of the inspection code. The main types are: fs corresponds to ‘struct inspect_fs’ in C code root no direct correspondence with the C code, but in the C code, ‘inspect_fs’ was overloaded to store roots inspection_data the inspection data which is incrementally collected about

It's neat that you can now do: $ guestfish -a F14x64.img -i \ inspect-get-package-management /dev/vg_f13x64/lv_root yum But it would be better if we didn't have to "know" the root filesystem there, something like: $ guestfish -a F14x64.img -i <<EOF set roots inspect-get-roots inspect-get-package-management %{roots[0]} EOF yum I've not quite

I''m trying to debug a bug in my code and am looking for some general advice on how to go about isolating the problem. The problem: My Rails application talks to a WebDAV server via HTTPS. Thanks to the Ruby standard library, I was able to make authentication over SSL happen with just a few lines of code. Awesome! Now it gets a bit obscure. I''m using a PROPFIND request to the

How do I disable console''s default behavior of automatically outputting what appears to be an inspect of all records found? For example: >> Item.find(:all).each do |item| >> puts item.title >> end # bunch of text outputted that shows the contents of all fields in all items... Joe -- Posted via http://www.ruby-forum.com/.

Hi, I would like to know the practical use of the inspect function. inspect: function() { return "''" + this.replace(''\\'', ''\\\\'').replace("''", ''\\\'''') + "''"; } >From what I gather it is escaping single quote and backslashes. Any help would be appreciated. Thank

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -------------- next part -------------- >From 3c1f762abed92f7a358f3bc93e3396d0606b18ad Mon Sep 17 00:00:00 2001 From: Richard W.M. Jones

Is there an equivalent under R (I got the 0.64.1 version) of the inspect() function ? thanks. ------------------------------------------------------ mathieuros at bigfoot.com Universiti Paul Sabatier Toulouse Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com

This patch is not complete yet because it needs to support Fedora, RHEL and Windows CDs. Some examples of the current output: $ virt-inspector ubuntu-10.10-desktop-amd64.iso <?xml version="1.0"?> <operatingsystems> <operatingsystem> <root>/dev/sda</root> <name>linux</name> <distro>ubuntu</distro>

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -------------- next part -------------- >From f7806322c5173d392e1f22b99ea00d45083f3f42 Mon Sep 17

From: "Richard W.M. Jones" <rjones at redhat.com> When a Windows guest doesn't have a HKLM\SYSTEM\MountedDevices node, inspection fails. However inspection should not completely fail just because we cannot get the drive letter mapping from a guest. --- src/inspect_fs_windows.c | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) diff --git

Greetings, I'd like to monitor the FS activities (read/write) at runtime on several virtual disk images running on Qemu KVM. The aim is to periodically inspect these images to identify possible Windows registry modification, file creation and so on.. What should be the optimal procedure? Shall I launch a new handler each time? It is a quite expensive procedure and it takes a lot of time on

On Wed, Jun 05, 2013 at 04:56:03PM +0100, Matthew Booth wrote: > Support arbitrary windows system root for pre-vista systems where > boot.ini is on the same partition as the system root. ^^^^^^^^^^^^^^^^^^^^^ I was just coming back to make this point. Is this a common configuration? All the guests I can remember have had a separate boot partition, except Windows XP. Anyway,

On Wed, 2013-06-05 at 18:05 +0100, Richard W.M. Jones wrote: > On Wed, Jun 05, 2013 at 04:56:03PM +0100, Matthew Booth wrote: > > Support arbitrary windows system root for pre-vista systems where > > boot.ini is on the same partition as the system root. > ^^^^^^^^^^^^^^^^^^^^^ > > I was just coming back to make this point. Is this a common >