Re: zeroing out the cloud image filesystem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 21 May 2013, Bill Nottingham wrote:

Matthew Miller (mattdm@xxxxxxxxxxxxxxxxx) said:

2) I also commented out the "Zeroing out empty space" postinstall stuff, because it drastically increases the image build time for not much benefit, IMHO.

One time image build cost vs. whatever benefit multipled by every time the image is used. :)

To put some numbers behind it, the compressed qcow2 image with the dd to
zero empty space is 215M out of appliance-creator. Without it, it's 242M.

post install is the wrong place, agreed. Pre-build of an image is not

There are privacy implications in not blanking a VM image. In some LVM setups, one may pick up a previous image's slack space still containing live data. A cautious provider does not provide an image with anything worth trolling (trawling <?>) through

Matt,

What timing is seen running (pre install):
	shred -n 0 -z /path/to/image
compared to that 'dd' approach quoted?

-- Russ herrold
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud





[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Big List of Linux Books]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux