| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 17 Feb 2012 15:39:08 -0500 From: Ted Ts'o <tytso@....edu> To: Lukas Czerner <lczerner@...hat.com> Cc: Phillip Susi <psusi@...ntu.com>, linux-ext4@...r.kernel.org Subject: Re: [PATCH 2/2] e2image: add -a switch to include all data On Fri, Feb 17, 2012 at 04:35:20PM +0100, Lukas Czerner wrote: > as I said I have never tested this. Well, actually I did some very > limited testing, but since this was not (and still is not right?) the > scope of e2image I don't think it's within the scope of e2image to be guaranteed way of converting a general-purpose qcow2 image file from qemu to a raw image file. It would be *nice* if this worked, but I don't think that's the main thrust of e2image's functionality, no. I'd consider it more within e2fsprogs's scope if e2fsck, dumpe2fs, debugfs, etc., could operate directly on a qcow2 file (i.e., if the qcow2 functionality was implemented as an io_manager). Combined with Darrick's fuse2fs, or the e2tools package, it would mean that we could manipulate qcow2 files directly from the host OS. I think sysadmins who are using virtualization would find that to be a useful feature. I just keep hoping that someone will be able to convince their management that it's useful enough to put in the development effort. :-) - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists