search for: myimg

I am familiar with using dd to create a disk image. dd if=/dev/hda1 of=myimge.img However, is there a way to capture the entire disk image into a file. I have 3 partitions: hda1 / hda2 swap hda3 /home and mbr How can I wrap them all into 1 image file. Thanks, Jerry

Dear all, I have question regarding GLMs: I have a discrete response variable and a continuous explaining variable. Like this: http://www.myimg.de/?img=example1db0f.jpg I want to use a GLM to investigate. I have to specify the "familiy of the distribution of the response variable" - or, maybe more precise, the "family of the distribution of the residuals of the response variable" (the mean of the response should be...

I am running this command /usr/libexec/qemu-kvm -no-acpi -smp 4 -m 2048 -drive file=myimg.img,format=raw -vga std -device rtl8139 and expecting a window to open up for the console. It does not. This is on CentOS 8. Do I have something missing/not installed - or something wrong on the command line. Jerry

Hi! I'm trying to use "Marco Polo Gro?er Reiseplaner 2005/2006" with Wine 0.9.13 on Gentoo Linux. To use it, I ran travel\setup.exe from the DVD and the setup just stops, before the "real thing" starts. Please see http://www.myimg.de/?img=BildschirmfotoWinedesktopSeaa8.png In the terminal window from which I started wine, I get: alexander@blatt ~ $ wine 'D:\travel\setup.exe' fixme:ole:ITypeInfo_fnRelease destroy child objects err:ole:get_unmarshaler_from_stream Failed to read common OBJREF header, 0x00000001 fixme:...

...tip to use Wine 0.9.12., I now successfully installed "Marco Polo Gro?er Reiseplaner 2005/2006" on Wine 0.9.12. running on Gentoo Linux. After the installation finished, I upgraded to Wine 0.9.13. First off, the names of the streets aren't printed correctly. Please see <http://www.myimg.de/?img=WineMarcoPoloGroerReiseplaner2.png>. As you can see there, the names of the streets aren't printed correctly - they are printed on a gray box. On a real Windows XP installation, that's not so. Further, certain "sections" (most importantly for me, the Route section) are...

...ite mydisk.img` will fill mydisk.img with pseudorandom content. I implemented this both with Ruby and Go. The 'write' op relies on pwrite_device. I have pasted the codes to the end of this mail. I'm creating mydisk.img as a qcow2 file with a raw sparse file bakcend $ truncate -s 100g myimg.raw $ qemu-img create -f qcow2 -b myimg.{raw,img} Then I do # pv /dev/sda2 | guest-xfer -d /dev/sda write mydisk.img I find that the ruby implementation produces a 24 MiB/s throughput, while the go one only 2 MiB/s. Note that the 'cat' operation (that writes device content to stdout) is...

...h pseudorandom content. > > I implemented this both with Ruby and Go. The 'write' op relies on > pwrite_device. > I have pasted the codes to the end of this mail. > > I'm creating mydisk.img as a qcow2 file with a raw sparse file bakcend > > $ truncate -s 100g myimg.raw > $ qemu-img create -f qcow2 -b myimg.{raw,img} > > Then I do > > # pv /dev/sda2 | guest-xfer -d /dev/sda write mydisk.img > > I find that the ruby implementation produces a 24 MiB/s throughput, while > the go one only 2 MiB/s. > > Note that the 'cat' op...

> > > Is the build process documented? Or am I just going to have to plod > through > > the makefiles? > > I don't think so. > Oh well... > > 1. Run installer > > 2. Installer loads ldlinux.sys onto the filesystem (and copies > ldlinux.c32, > > but irrelevant for now). > > 3. Installer calculates which blocks in the filesystem contain