Will cause a write error. This would only happen for the final range of
an image created with -f. We now pad out any partial last sector if direct
IO is specified (-f on imageunzip/frisbee) and write that to the file.

If the padding causes any problems in the future, we can always get rid of
it by truncating the file to the correct size when we are done...I think.

we start putting the submap entries into the XML descriptor.

image. Been wanting to do this for a while since the dependency on
copying the contents of the root disk to create an image, has always
been a dubious approach, since there is no consistency over time,
and because it is unclear if the resulting image will boot on a
physical node later (cause of the XEN stuff that is on the disk).

 * bootstrap-filestyle
 * http://dev.tudosobreweb.com.br/bootstrap-filestyle/
 *
 * Copyright (c) 2013 Markus Vinicius da Silva Lima
 * Version 1.0.3
 * Licensed under the MIT license.
 */

To further prevent (or maybe promote) confusion.

If they specify filesystem creation, it can take 5 minutes or longer
depending on the FS type and size. We print a warning about this.

Previously, Linux could do ext* and BSD could do UFS. Now linux can also
RO mount UFS while FreeBSD can RW mount ext[23] and RO mount ext4
(FreeBSD 10 only for ext4). So ext3 would be a good choice if you want your
blockstore available no matter the OS being used.

and libraries. Rough, needs plenty more work.

The -f <fstype> option to createdataset will now pre-initialize the dataset
with an empty filesystem. Supported types are: ufs and ext[234].

Note to self: Make sure you are testing the version of the code you think you are testing.

Can do ext[234] or ufs.

with disk images being corrupted.

correct (non-xen) kernel.