search for: installlocation

...command "build-pkg" (specifying the appropriate path of course.) A subdirectory will be created as contrib/solaris/build-SSH-package, and after the build is done the package will be present in that build-SSH-package directory with a name of the form OPENssh-$SSHversion-$arch-$OSversion[-$installLocation] The build and install scripts should take into account most possible situations (existing SSH installation, differences in Solaris version between build and target systems, changes you have made to the default configuration, etc.) I would appreciate any feedback or comments. ______________ For...

...play_name) { value = guestfs_hivex_node_get_value (g, child, "DisplayVersion"); if (value) - version = guestfs_hivex_value_utf8 (g, value); + version = guestfs_hivex_value_string (g, value); value = guestfs_hivex_node_get_value (g, child, "InstallLocation"); if (value) - install_path = guestfs_hivex_value_utf8 (g, value); + install_path = guestfs_hivex_value_string (g, value); value = guestfs_hivex_node_get_value (g, child, "Publisher"); if (value) - publisher = guestfs_hivex_value...

This adds most of the hivex APIs directly to the libguestfs API, so that you can read and write Windows Registry hive files from libguestfs without needing to download and upload hive files from the guest. This is analogous to how Augeas APIs are exposed already (guestfs_aug_*) Also, inspection is now done using the new APIs, which fixes the following bug:

This fixes almost everything. Note that it adds an extra commit which fixes the whole utf8/iconv business. It's probably better to list what isn't fixed: (1) I didn't leave the osinfo code around because I'm still haven't looked too closely at virt-builder-repository. Can't we just fetch this code from the git history when we need it? (2) I didn't change the way