Comment 14 for bug 1907107

> installing lightdm brings in over 500 packages and took about 12 minutes to install;*
It seems normal to me, it installs a big tree of dependencies because its the first "graphic" package.

> Some package may require post-install configuration.
I used that method with success for many years with a kickstart install script.
It installs the system then run ansible-playbook in a chroot to install all packages and configure everythings.

> I can say that the Ubuntu Server installer isn't typically used to install Ubuntu Desktop.
I use it because i can't find any netboot installer which supports autoinstall and EFI installation. I used legacy netboot (60MB) for my kickstart install but now i need to autoinstall an EFI system.

> have you looked at just using the Ubuntu Desktop installer with OEM mode? https://help.ubuntu.com/community/Ubuntu_OEM_Installer_Overview
I just want a way to automate installation from a pxe boot, with an "answer file", i did with kickstart in a "script" model, i want to do the same with autoinstall.

> I would suggest that you add a runcmd to restart gdm or other packages which might need to restart after the initial install;
Thanks for the tip, i try this as soon as possible.

> cloud-init is configured to write to the console by default; that's why you see output from cloud-init on your tty.
It seems to me a little bit buggy, don't you think ?
I think cloud-config.service should defaulty have a stronger dependency as Before=getty.target for exemple.

Why don't the installer configure everything during the install process ? Generating locales, write /etc/default/locale and set /etc/timezone are not hard tasks. Even if cloud-init embeed those configuration, you could tell the installer to setup what in cloud-config as default config.

If you can't avoid that first startup scripts, you should start as early as possible in the init process, before any process that could use what it setup/modify. Does that seem illogical ?