From 8a723ca62eb4f93f19c5c66beffaf70997afb64c Mon Sep 17 00:00:00 2001 From: "Richard W.M. Jones" Date: Tue, 28 Aug 2012 16:03:50 +0100 Subject: New APIs: hivex_* Transscribe many hivex(3) APIs into the libguestfs API. There is one hive handle per libguestfs handle, as with Augeas. Note that hivex uses iconv_open for some APIs (eg. hivex_value_string). But since we delete all the i18n files from the appliance, this doesn't work -- iconv_open returns EINVAL. Therefore hivex APIs which require iconv cannot be bound in the daemon. --- src/MAX_PROC_NR | 2 +- src/guestfs.pod | 15 +++++++++------ 2 files changed, 10 insertions(+), 7 deletions(-) (limited to 'src') diff --git a/src/MAX_PROC_NR b/src/MAX_PROC_NR index aef2e272..47531021 100644 --- a/src/MAX_PROC_NR +++ b/src/MAX_PROC_NR @@ -1 +1 @@ -349 +365 diff --git a/src/guestfs.pod b/src/guestfs.pod index cd4f5c5c..7361e0a5 100644 --- a/src/guestfs.pod +++ b/src/guestfs.pod @@ -723,12 +723,15 @@ length filenames, keep the files in a tarball. =head3 ACCESSING THE WINDOWS REGISTRY Libguestfs also provides some help for decoding Windows Registry -"hive" files, through the library C which is part of the -libguestfs project although ships as a separate tarball. You have to -locate and download the hive file(s) yourself, and then pass them to -C functions. See also the programs L, -L, L and L for more help -on this issue. +"hive" files, through a separate C library called L. + +Before libguestfs 1.19.35 you had to download the hive file, operate +on it locally using hivex, and upload it again. Since this version, +we have included the major hivex APIs directly in the libguestfs API +(see L). This means that if you have opened a +Windows guest, you can read and write the registry directly. + +See also L. =head3 SYMLINKS ON NTFS-3G FILESYSTEMS -- cgit