I understand your confusion, since I'm equally confused.
You say that Ubiquity is the debian-installer, however on this page it says: https://wiki.ubuntu.com/UbiquityAutomation
Code:
With respect to automation, ubiquity, the desktop CD installer, works much in the same way that debian-installer, the alternate CD installer does.
That, in combination with the statement (from the same page):
Code:
Preseeding keys for the following installer components will not be used in Ubiquity, usually because they do not fit with Ubiquity's mode of operation:
- netcfg
- LVM and RAID partitioning
- base-installer
- pkgsel/tasksel
- finish-install
and, in combination with this, from https://help.ubuntu.com/lts/installa...preseed-pkgsel
Code:
If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter pkgsel/include. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well.
led me to believe that Ubiquity was an Ubuntu-specific installer.
Especially since this works:
Code:
tasksel tasksel/first multiselect ubuntu-desktop
But this doesn't, and, much to my frustration - fails silently:
Code:
d-i pkgsel/include string openssh-server
And since Ubuntu strives to be easy I (probably erroneously) then guessed that Ubiquity was the Ubuntu-specific, graphical installer, and that the documentation is too much copied from Debian and not really updated with Ubuntu-specific options.
Hence my question about using the debian-installer instead of Ubiquity, hoping that I'd get a text-only installer that actually would work as indicated in the above mentioned documentation.
Bookmarks