-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Sat, Oct 14, 2017 at 04:01:11PM +0200, Wojtek Porczyk wrote: > On Sat, Oct 14, 2017 at 03:36:05PM +0200, Marek Marczykowski-Górecki wrote: > > Thanks for the explanation. > > This should be enough for the online resize part. Now, back to the main > > issue here: partition to resize isn't the last one, one need to move two > > other partitions first. Hmm, maybe parted can do that too? > > Can't we change the partition order and add some compatibility to initrd? We > could support resizing only for "new" templates and leave the instruction to > resize older ones in documentation, with a big scary warning that it's better > to reinstall template than attempt manual resizing.
We've just had extensive discussion about possible options. It boils down to: 1. Leave the current partition layout but have more complex resize operation (more fragile, harder to support - especially when someone heavily customize the template). This option would allow us to release 4.0rc2 today (with possibility to add root resize script later), according to the schedule. 2. Change the partition layout to have simpler resize operation. This also would be more logical layout - boot-related partition at the beginning. But this means breaking existing 4.0rc1 installations, or at least not supporting root volume resize there at all (unless templates are reinstalled). This also means delaying rc2 a week more, to do this change, test it, and rebuild all the templates. Given those two options, we've decided it's better to have cleaner situation longterm (option 2) at the cost of less convenient rc stage, than the other way around. After all, we'll need to support this for a much longer time than we spend now at release candidates. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJZ4yanAAoJENuP0xzK19csVFcH/RUKu+YjxvyXz56SF1Gf2ZiW MF8jC9lagojeDoxMBz/9wDDkUj9xz4tLUffagPtSSyxKrF2CTQfBAPEsHsHbY/sC EAdTc1jIZl9ea4n551bVA8l41Tntwj5PWkla6TtZF3k0u0XLKCBAk23antBtqN+/ CRvmxjeVp0qrZ0nk9nUyvGvBpvBvfTI6waqLt0PUpdTspEwmgn3rY3d+5T2W0Jhk SXC+8oQRLAWeOQkiUhikCvUT8kogE/GLV5B2CerzCBgQvf4bw+D2J1/PR3ByKAYw dmmugv8AS6WPxs/Hu6y82735u4f3bnrSe7qKyZeEn63lCl+gz88chBwM5H89S4o= =S7wD -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20171016134524.GI1059%40mail-itl. For more options, visit https://groups.google.com/d/optout.
