ubuntu-image 0.7ubuntu1

[Gustavo Niemeyer]

Instead of asking whether I've read the thread, I'd appreciate if you could
try to understand the point I'm making so we can make some progress.

The gadget.yaml should represent accurately what goes into the image. Not
one image in fact, but multiple, one per volume, and all of their
partitions.

We need to represent the "writable" partition in the gadget as well if it
is supposed to be in those images, otherwise how do we provide parameters
for it, and where does it go? Which position? And so on.

A lonely "size" parameter is not meaningful in that context without further
details. Then, how do we resize the boot partition, or any other one?



On Oct 12, 2016 2:56 PM, "Oliver Grawert" <ogra at ubuntu.com> wrote:

> hi,
> On Mi, 2016-10-12 at 14:14 -0300, Gustavo Niemeyer wrote:
> > It doesn't make much sense to have an option that controls the
> > generated disk image size by itself. We have multiple volumes,
> > multiple images, and multiple partitions inside any given volume.
> > What is the size referring to? To make sense of it, ubuntu-image must
> > necessarily learn more about what to do with that value via the
> > gadget.yaml itself.
> >
>
> well, not sure what we discussed the last two days here or if you read
> anything that was said by me ...
>
> it is the padding the image has to have to be usable in kvm ...
>
> without it *we can not use* the kvm image (well, you will have a few MB
> free but not be able to install any significant snap due to not having
> the diskspace) alternatively we would have to hardcode a size for the
> writable partition in some other way which we do not support today.
>
> ciao
>         oli
> --
> Devices mailing list
> Devices at lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.snapcraft.io/
> mailman/listinfo/devices
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.snapcraft.io/archives/devices/attachments/20161012/921c2fc4/attachment.html>