search for: 591037fd

...-marketplace/CentOS 7 x86_64 (2014_09_29) EBS > HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace > available public [marketplace: aw0evgkw8e5c1q413zgy5pjce] > x86_64 machineebs hvm xen > BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 > false standard Not Encrypted > as you can see the block device mapping is by default set to > BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 > false standard Not Encrypted > > it is a standard volume, not encrypted...

I'm staring at the free CentOS images on AWS, and seeing that whoever set those up elected to use a partition for /dev/xvda1 rather than taking advantage of Amazon's tendency to use "/dev/xvda", "/dev/xvdb", etc. for each disk and use those directly as a file system. The result is that if you elect to allocate a larger base disk image, for example allocating 50 Gig to

...tOS 7 x86_64 (2014_09_29) EBS >> HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace >> available public [marketplace: aw0evgkw8e5c1q413zgy5pjce] >> x86_64 machineebs hvm xen >> BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 >> false standard Not Encrypted >> as you can see the block device mapping is by default set to >> BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 >> false standard Not Encrypted >> >> it is a standa...

...8fe aws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace available public [marketplace: aw0evgkw8e5c1q413zgy5pjce] x86_64 machineebs hvm xen BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 false standard Not Encrypted as you can see the block device mapping is by default set to BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 false standard Not Encrypted it is a standard volume, not encrypted, and 8 GB my modification...