similar to: [PATCH] Coalesce printable characters in debug and trace messages (RHBZ#802109).

It's not too clear from the patch, so I have also extracted the new API from <guestfs.h> and the relevant section of the man page. Rich. ---------------------------------------------------------------------- /* Events. */ #define GUESTFS_EVENT_CLOSE 0x0001 #define GUESTFS_EVENT_SUBPROCESS_QUIT 0x0002 #define GUESTFS_EVENT_LAUNCH_DONE 0x0004 #define

Because of previous automated commits, such as changing 'guestfs___' -> 'guestfs_int_', several function calls no longer lined up with their parameters, and some lines were too long. The bulk of this commit was done using emacs batch mode and the technique described here: http://www.cslab.pepperdine.edu/warford/BatchIndentationEmacs.html The changes suggested by emacs were

Extend the generator to generate a source (and the header for it) with functions that print the content of a guestfs struct. The code is modelled after the code for it in fish.ml, although made a bit more generic (destination FILE*, line separator) so it can be used also in the library, when tracing. This just introduces the new code and builds it as part of the helper libutils.la. ---

Some of the data in names and string values were being unsafely printed, causing some types of XML processors to fail (e.g. Python's Expat). This patch checks for printability of each character and outputs base64 with an encoding attribute for unsafe data. --- xml/hivexml.c | 75 ++++++++++++++++++++++++++++++++++++++++++++++++-------- 1 files changed, 64 insertions(+), 11 deletions(-)

The first c-set cleans up the list of excluded syntax-checks. The second enables the sc_avoid_ctype_macros test and changes each use of a ctype macro like isspace to c_isspace. This makes it so such tests (often parsing-related) is locale-independent. Otherwise, in some odd corner cases (combination of non-C locale and perverted inputs), I suspect that libguestfs tools would mistakenly accept

I've just tried to build the latest from git, and it failed like this: events.c: In function 'guestfs___call_callbacks_message': events.c:128:7: error: implicit declaration of function 'strlen' [-Werror=implicit-function-declaration] events.c:128:39: error: incompatible implicit declaration of built-in function 'strlen' [-Werror] events.c:131:38: error:

Add some warnings. Well, the first patch is a miscellaneous change, but patches 2-5 add some warnings. Rich.

The symbols file generated in the Debian package to aid the package maintainer automatically detect future changes shows internal library and helper function names, whereas it should only be exporting hivex_* function names. This page may help with this: http://gcc.gnu.org/wiki/Visibility Symbols: asnprintf at Base 1.2.1 c_isalnum at Base 1.2.1 c_isalpha at Base 1.2.1 c_isascii at Base

Result of earlier copy and paste. --- align/scan.c | 35 ++++++++++--------- cat/cat.c | 39 +++++++++++---------- cat/filesystems.c | 69 +++++++++++++++++++------------------- cat/log.c | 35 ++++++++++--------- cat/ls.c | 61 +++++++++++++++++---------------- df/main.c | 43 ++++++++++++------------ diff/diff.c | 67

I've been taking a long hard look at the protocol layer. It has evolved over a long time without any particular direction, and the result is, to say the least, not very organized. These patches take a first step at cleaning up the mess by abstracting out socket operations from the rest of the code. The purpose of this is to allow us to slot in a different connection layer under the

From: Maros Zatko <mzatko@redhat.com> --- fish/rl.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ fish/rl.h | 32 +++++++++++++ 2 files changed, 190 insertions(+) create mode 100644 fish/rl.c create mode 100644 fish/rl.h diff --git a/fish/rl.c b/fish/rl.c new file mode 100644 index 0000000..bb8fd62 --- /dev/null +++ b/fish/rl.c @@ -0,0 +1,158 @@ +/* guestfish -

From: Maros Zatko <hacxman@gmail.com> Auxiliary functions for readline to support space character escaping in filenames in future. Escaping function is taken from fish.c (used to be parse_quoted_string) plus its un-escaping counterpart. There are a few tests for both. Maros Zatko (3): fish: rl.{c,h} - escaping functions for readline fish: basic tests for readline escaping autotools:

Hi all, How do I set the content_transfer_encoding for mail with actionmailer to something other than quoted-printable? It''s a setting with TMail which action mailer relies on in rails 2.3.*. I am trying to set it to utf8 I have tried: - mail = TMail::Mail.new; mail.transfer_encoding = "utf8"; - setting the @header["Content-Transfer-Encoding"] in the

This is a better way to make strings printable in the output of hivexregedit / virt-win-reg. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -------------- next part -------------- >From e16d1cc51c234eb9f3e7db3b8f77f76198ffee73 Mon

On 12/6/18 3:50 PM, Richard W.M. Jones wrote: > This generates small functions which map from various integer NBD > protocol flags to the string equivalent. > > eg: > name_of_nbd_cmd (NBD_CMD_READ) > ---> "NBD_CMD_READ" > > This commit uses some hairy sed scripting to ensure that we don't add > any more dependencies to nbdkit. Hairy, but

Hi, Any link where I can download a printable pdf that documents centos 6.3 ? Thanks Kunle

Hi folks, currently I'm running Dovecot 1.2.1. Compiled from source on Fedora 10 Linux 32 Bit (all patches). Clients are Pine 4.64, Thunderbird 2.0.0.22 and Mutt 1.5.20 (using "=b" for server-side searching). When a message contains the text "under_score" and I let the server search for it, Dovecot does not find it in messages with a Content-Transfer-Encoding of

How to easily convert maildir files from (single part) quoted-printable to 8bit encoding? [I would like to ease access to sent/posted archives.]

Hi! I'm completely confusing myself attempting to solve this one. Is there a simple way of removing particular ASCII characters from a CSV file using R. Hopefully something simpler and faster than cycling through each individual character and comparing them to a list of characters to remove then deleting as necessary. As always, any help would be appreciated. Thanks! Dan [[alternative

I expect this patch to require a second version. I mainly wanted to spur discussion: * I firmly believe hivexml needs more encoding checks before printing. Base64 encoding made the most sense as hivexml already uses it elsewhere. Is this the right direction to go, to escape non-printable data? * Should there be an enumeration for encoding decisions? I'm returning strings because it felt a