search for: misconceived

Since the PPC Macs are no longer being produced and my PPC build machine is getting a little old I thought I would try making a universal version of the Mac OS X gem. After a little investigation it turned out to be surprisingly easy to do, just pass --enable-universal_binary when building wxWidgets and add -arch ppc -arch i386 to $extra_cppflags and $extra_ldflags in rakemacosx.rb. Now the

http://projects.puppetlabs.com/issues/7600 I call this the "agent orange" option :) This works, purging all unmanaged hosts entries: resources { ''host'': purge => true, noop => true, } We should have a similar property for all (most?) types. Please comment on the ticket or reply here, whichever you prefer. Thanks! r P.S. This is in

...tive infinite value. Elsewhere in this list, Julian Cowley pointed out that negative values also start with a non-digit character, which some people may not have understood (i.e. i;ascii-numeric works only on unsigned values). The bug fix in this release could therefore change result of certain misconceived (and probably spam-related) Sieve rules, so watch out! I started work on the spamtest(plus) and virustest extensions. These are implemented for the most part, but their configurability needs quite a bit more work. Changelog Sieve v0.1.15: * Enotify extension: - Adjusted notify method...

...tive infinite value. Elsewhere in this list, Julian Cowley pointed out that negative values also start with a non-digit character, which some people may not have understood (i.e. i;ascii-numeric works only on unsigned values). The bug fix in this release could therefore change result of certain misconceived (and probably spam-related) Sieve rules, so watch out! I started work on the spamtest(plus) and virustest extensions. These are implemented for the most part, but their configurability needs quite a bit more work. Changelog Sieve v0.1.15: * Enotify extension: - Adjusted notify method...

On Thu, Sep 17, 2020 at 01:40:04PM +0100, Richard W.M. Jones wrote: >When guestfs_lvm_canonical_lv_name was called with a /dev/dm* or >/dev/mapper* name which was not an LV then a noisy error would be >printed. This would typically have happened with encrypted disks, and >now happens very noticably when inspecting Windows BitLocker- >encrypted guests. > >Using the modified

Hi all, I have Centos 8 installed on a physical machine (www6) with separate LVM volumes for /, /var, /var/lib/mysql etc. System boot proceeds without a hiccup, in terminal systemctl status says everything is OK and running, journalctl says so as well - systemd mounts everything stated in fstab. However, on reboot systemd echoes problems with filesystem on /var : ...// unmounting all volumes

...(stderr, "mode = %o\n", statbuf.st_mode); + if (S_ISBLK (statbuf.st_mode)) + /* continue */; + else if (S_ISDIR (statbuf.st_mode)) { + fprintf (stderr, "S_ISDIR\n"); + /* The lvremove API allows you to remove all LVs by pointing to + * the VG directory. This was misconceived in the extreme, but + * here we are. XXX + */ + return strlen (device) > 5; + } + else + return 0; + + /* Reject the root (appliance) device. */ + if (is_root_device_stat (&statbuf)) { + if (verbose) + fprintf (stderr, "%s: %s is the root device\n", +...

...ngsbuf. * diff --git a/daemon/utils.ml b/daemon/utils.ml index 7630a5534..48f6b9c5c 100644 --- a/daemon/utils.ml +++ b/daemon/utils.ml @@ -129,6 +129,90 @@ let is_root_device device = device func arg (error_message err); false +(* XXX This function is copied from C, but is misconceived. It + * cannot by design work for devices like /dev/md0. It would be + * better if it checked for the existence of devices and partitions + * in /sys/block so we know what the kernel thinks is a device or + * partition. The same applies to APIs such as part_to_partnum + * and part_to_dev which r...

https://bugzilla.redhat.com/show_bug.cgi?id=1477623 The first two patches are cleanups. The third patch changes the way that we handle Device and Dev_or_Path parameters so that a parameter marked as such can really only contain a block device name (and not, for instance, a chardev). Using a chardev here caused hangs in the API. The next two patches fix API usage to conform to this new stricter

Version 1 was here: https://www.redhat.com/archives/libguestfs/2017-June/msg00003.html This patch series reimplements a few more APIs in OCaml, including some very important core APIs like ?list_filesystems? and ?mount?. All the tests pass after this. The selection of APIs that I have moved may look a little random, but in fact they are all APIs consumed by the inspection code (and some more

v2 was here: https://www.redhat.com/archives/libguestfs/2017-June/msg00008.html This series gets as far as a working (and faster) reimplementation of ‘guestfs_list_filesystems’. I also have another patch series on top of this one which reimplements the inspection APIs inside the daemon, but that needs a bit more work still, since inspection turns out to be a very large piece of code. Rich.

I think this fixes everything mentioned: - Added the Optgroups module as suggested. - Remove command temporary files. - Replace command ~flags with ?fold_stdout_on_stderr. - Nest _with_mounted function. - Rebase & retest. Rich.

v1 was posted here: https://www.redhat.com/archives/libguestfs/2017-July/msg00098.html This series now depends on two small patches which I posted separately: https://www.redhat.com/archives/libguestfs/2017-July/msg00207.html https://www.redhat.com/archives/libguestfs/2017-July/msg00209.html v1 -> v2: - Previously changes to generator/daemon.ml were made incrementally through the patch

Previously posted as part of the mega utilities/inspection series here: https://www.redhat.com/archives/libguestfs/2017-June/msg00232.html What I've done is to extract just the parts related to rewriting daemon APIs in OCaml, rebase them on top of the current master, fix a few things, and recompile and test everything. Rich.

This is a combination of: https://www.redhat.com/archives/libguestfs/2017-June/msg00046.html [PATCH 00/12] Refactor utility functions. plus: https://www.redhat.com/archives/libguestfs/2017-June/msg00023.html [PATCH v3 00/19] Allow APIs to be implemented in OCaml. with the second patches rebased on top of the utility refactoring, and some other adjustments and extensions. This passes

v6 was posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00103.html and this requires the utilities refactoring posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html Inspection is now complete[*], although not very well tested. I'm intending to compare the output of many guests using old & new virt-inspector to see if I can find any

v5: https://www.redhat.com/archives/libguestfs/2017-June/msg00065.html Since v5, this now implements inspection almost completely for Linux and Windows guests. Rich.

v7 was: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html https://www.redhat.com/archives/libguestfs/2017-June/msg00184.html I believe this addresses all comments received so far. Also it now passes a test where I compared about 100 disk images processed with old and new virt-inspector binaries. The output is identical in all cases except one which is caused by a bug in blkid