-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a disk img for qemu that is 4G, but disk usage is only 650M ... due to
how the image is created, it will grow to 4G, but only uses as much as it needs
... but, if I run a simple 'cp' on the file, it goes from:
image: debian.img
file format:
On Mon, Nov 3, 2008 at 10:40 AM, Marc G. Fournier [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a disk img for qemu that is 4G, but disk usage is only 650M ... due to
how the image is created, it will grow to 4G, but only uses as much as it
needs
... but,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sweet, never even thought about doing that ... thank you ...
- --On Monday, November 03, 2008 11:04:22 -0600 Matt [EMAIL PROTECTED] wrote:
On Mon, Nov 3, 2008 at 10:40 AM, Marc G. Fournier [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED
Marc G. Fournier [EMAIL PROTECTED] wrote:
I have a disk img for qemu that is 4G, but disk usage is only 650M ... due to
how the image is created, it will grow to 4G, but only uses as much as it
needs
... but, if I run a simple 'cp' on the file, it goes from:
image: debian.img
file
I have a disk img for qemu that is 4G, but disk usage is only 650M ... due to
how the image is created, it will grow to 4G, but only uses as much as it needs
... but, if I run a simple 'cp' on the file, it goes from:
tar have options for that
image: debian.img
file format: raw
virtual size:
