search for: goodel

...using the get_range method is slowing down my program for large files. I don''t know whether I''m doing something wrong or there''s a way to access the text without significant slowing in large files. If anyone can help, I''d very much appreciate it. Thanks, Ross Goodell -- Posted via http://www.ruby-forum.com/.

...386 on a Dell Inspiron 6400 > (Core Due, 1GB RAM) with SELinux on "enforcing". I've just received my new 6400 (T7400, 2GB, 160GB, Vista Home Premium) and I'd like to install CentOS 5 too. With big surprise (looking at the partition table first and then, googling, http://www.goodells.net/dellrestore/index.htm) I found that Dell is used to use the whole of the four partitions (see the url above for details). Did you remove any of these partitions (e.g. the Media Direct one)? Could you share your experience? I'd like to preserve the base functionalities without prevent...

Hi, I'm using virt-resize to expand the primary partition (C:) in a Windows 2003 image. The command works fine but after expanding, when I boot into Windows 2003, all the other partitions (D:, E:, and F:) are lost. After using the disk management tool within Windows 2003, I can re-label the above three partitions and all the files are still there. But it is really annoying because every

Bugs item #20348, was opened at 2008-05-25 12:12 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=20348&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 3 Submitted By: Ross Goodell (rossgoodell) Assigned to: Nobody (None) Summary: Apparent problems in text selection by direction arrow keys with shift held down Initial Comment: I am working on a text editor using wxRuby (I believe I''m using wxruby-1.9.5-i386-mswin32) and I''m having significant problems gett...

...after expanding, when I boot > into Windows 2003, all the other partitions (D:, E:, and F:) are lost. I can see why this would happen. In the Windows registry, Windows stores drive letter mappings using a (basically crazy) system using the partition offset. It is described here: http://www.goodells.net/multiboot/partsigs.shtml "How does Windows XP remember drive letters?" We implement this in libguestfs: https://github.com/libguestfs/libguestfs/blob/aee6fc4863c170d08e572dbdcfcb6f328edfc013/src/inspect-fs-windows.c#L545 Virt-resize moves partitions around, so of course the p...

...ome current_control_set + with + | Not_found -> + if verbose () then + eprintf "check_windows_system_registry: cannot locate HKLM\\SYSTEM\\Select\n%!"; + None + +(* Get the drive mappings. + * This page explains the contents of HKLM\System\MountedDevices: + * http://www.goodells.net/multiboot/partsigs.shtml + *) +and get_drive_mappings h root data = + let devices = lazy (Devsparts.list_devices ()) in + let partitions = lazy (Devsparts.list_partitions ()) in + try + let path = [ "MountedDevices" ] in + let node = get_node h root path in + let values...

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:

v10: https://www.redhat.com/archives/libguestfs/2017-July/msg00245.html No actual change here, but I rebased and retested. Also this series now does not depend on any other patch series since everything else needed is upstream. Rich.

v9 was here: https://www.redhat.com/archives/libguestfs/2017-July/msg00139.html This depends on these three series (the first two being single minor patches): https://www.redhat.com/archives/libguestfs/2017-July/msg00207.html https://www.redhat.com/archives/libguestfs/2017-July/msg00209.html https://www.redhat.com/archives/libguestfs/2017-July/msg00215.html There is no substantive change. I

This depends on the patch series "[PATCH 00/27] Reimplement many daemon APIs in OCaml." (https://www.redhat.com/archives/libguestfs/2017-July/msg00098.html) v8 was posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00274.html v9: - I split up the mega-patch into a more reviewable series of smaller, incremental patches. There are some other changes vs v8, but

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

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