It’s nice to see only a handful of processes running on a new setup.
It’s nice to see only a handful of processes running on a new setup.
That's a heck of a gotcha.
However, even the text itself is worded to leave out the sudo implication to the end of the whole paragraph, which is typically skipped by anyone who simply wants their OS installed.
edit: If, after installing, you install sudo and manually disable the root password, you won't be able to boot to the rescue or emergency targets; a valid root password is now required by default.
If you want them to work without a password, like classic "single-user mode", you can edit both the rescue and emergency unit files, and add the --force flag to sulogin.
https://salsa.debian.org/installer-team/user-setup/blob/70b7...
The popularity-contest package is installed, you're asked whether you want to participate, and then the package is uninstalled when you say no -- as opposed to asking and then installing the package if you say yes.
d-i passwd/root-login boolean false
in a preseed file seems to still work just fine (to skip "creation" of a root account).The "sudo" package will be installed and the user created during installation will be added to the "sudo" group.
I had a better / more elaborate explanation bookmarked somewhere but can't find it now, the tldr is a "modern" OS (past ~2-3 decades) wants the freedom to manage anonymous (malloc) and named (mmio) memory between physical RAM and disk devices. Disabling swap means the OS must always keep the anonymous pages in physical RAM, which negatively impacts any IO-bound workload (can't cache) and, ironically, puts more pressure on the disk.
So unless you have an extremely specific and finely tuned use-case with lots of benchmark data, the OS will almost always make a better call.
I have been running swapless for two decades without any issue.
* http://jdebp.uk./FGA/dont-throw-those-paging-files-away.html