search for: msg00100

Displaying 4 results from an estimated 4 matches for "msg00100".

Did you mean: msg00000
2013 Nov 06
2
virt-resize problem for Windows 2003
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
2006 Apr 12
1
OpenSSH 4.3p2, MIT KfW 3.0 and Cygwin
...fully built openssh with MIT's KfW (Kerberos for Windows) under Cygwin? Is it even possible? Searching around I found one reference to Nicolas Williams attempting to do this several years ago, but no indication of success and nothing more recent. http://www.cygwin.com/ml/cygwin/2002-01/msg00100.html What about compiling openssh using a native windows compiler? Is that possible? I'm afraid I have NO experience compiling anything using a native windows compiler which is why I'd prefer to use cygwin. But if cygwin isn't possible I'd resort to using something else. The...
2013 Nov 06
0
Re: virt-resize problem for Windows 2003
...1.16.19-1.el6.x86_64 > libguestfs-tools-c-1.16.19-1.el6.x86_64 > libguestfs-winsupport-1.0-7.el6.x86_64 It won't fix your problem, but there is a newer version of libguestfs available for RHEL 6 users: https://www.redhat.com/archives/libguestfs/2013-May/msg00100.html > Guest OS partitions: > C: /dev/sda1 primary > D: /dev/sda5 logical > E: /dev/sda6 logical > F: /dev/sda7 logical > > Also, if I use virt-resize on logical partitions (i.e., D: E: or F:), the > command runs...
2019 Sep 15
2
[PATCH nbdkit v2] common/bitmap: Don't fail on realloc (ptr, 0)
v1 was here: https://www.redhat.com/archives/libguestfs/2019-September/msg00100.html In v2 I've changed the patch so it avoids calling realloc at all in this case. The patch is a bit longer this way. But I don't see any other alternative if we are to avoid having a "realloc wrapper" of some kind that we use everywhere, which I guess we should avoid because...