On 9/5/26 7:23 PM, Fix The Debian Installer wrote:
First of all, drop the pearl-clutching and look at the actual engineering. Calling a
legitimate complaint about a broken deployment workflow "abuse" is a lazy way
to avoid admitting that the default installer behavior is deeply flawed.
Second, you are completely misinterpreting the problem. This isn't a request
for a granular, package-by-package aptitude clone inside the installer. The
issue is entirely about the broken, automated behavior of the default
installation wizard.
Let’s look at how the default path actually behaves, because telling users they are
"holding it wrong" completely misses the mark.
The default installer wizard completely circumvents the user by hiding the critical
software selection screens during the main setup loop. It makes a massive, heavy
assumption about the target system and automatically queues up a desktop environment
without ever explicitly prompting the administrator with a choice like, "Are you
deploying a desktop or a headless server?"
If you don't select anything at that step, you should get a headless
server installation. Does that not work for you?
Granted, this is not as explicit as you would like.
Claiming that an experienced admin should "just use preseeding" to avoid unwanted bloat
is a total failure of basic installer design. Preseeding is an external automation framework. The
native, interactive default wizard should be capable of standing on its own. It shouldn't require
an external configuration layer or a hidden "expert mode" just to prevent an unwanted GUI
from being stealth-installed by default.
This is already the case, see above.
The flaw is entirely in the default installer’s lack of explicit prompts. The
wizard should explicitly ask the user what type of deployment they want
up-front, rather than automating a bloated desktop environment by default and
forcing administrators to look for hidden advanced workarounds.
D-I, is versatile, doing an headless install is not for everyone. That
is likely why this is done this way.
If you are sysadmin, that should not be to difficult to customize the
installer to your liking.
If you install manually, how do you cope with reproducing builds and
administrating a fleet of servers?
Fix the default wizard's behavior instead of deflecting.
Debian always welcomes constructive feedback or better still contribution.
Note that I'm just explaining how you can work with what D-I currently
offers, that does not mean that the points you are raising are not valid.
P.S.
There is no need to CC me I'm subscribe to the debian-boot mailing list
This very list, is responsible for D-I related questions/contributions.
--
John Doe
