Displaying 3 results from an estimated 3 matches for "c833304".
Did you mean:
383304
2016 Dec 06
0
[PATCH 4/5] inspect: fix existance check of /dev/mapper devices
...sort using a debug API to check whether a file in the
appliance exists, instead.
Fixes commit 96b6504b09461aeb6850bb2e7b870a0a4c2f5edf.
---
src/inspect-fs-unix.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c
index c833304..7b54a4a 100644
--- a/src/inspect-fs-unix.c
+++ b/src/inspect-fs-unix.c
@@ -1806,6 +1806,19 @@ resolve_fstab_device_diskbyid (guestfs_h *g, const char *part,
return 0;
}
+static bool
+dev_mapper_exists (guestfs_h *g, const char *device)
+{
+ CLEANUP_FREE char *ret = NULL;
+ const char *cons...
2016 Dec 07
3
[PATCH v2 0/2] Improve inspection of /usr filesystems
Hi,
this patch series improves the way /usr filesystems are handled: tag
them appropriately, so later on we can find them and merge results they
contain directly back for the root filesystem.
Changes in v2:
- removed patches #1 and #2, already pushed
- drop patch #3, no more needed
- replace patch #4 with a better suggestion from Rich
- change if into assert in patch #5
Thanks,
Pino Toscano
2016 Dec 06
9
[PATCH 0/5] Improve inspection of /usr filesystems
Hi,
this patch series improves the way /usr filesystems are handled: tag
them appropriately, so later on we can find them and merge results they
contain directly back for the root filesystem.
The series includes also a new private debug API, and its usage to fix
the resolution of /dev/mapper/.. devices found in fstab; without it,
LVM /usr filesystems are not recognized as belonging to their