Daniel Reurich <daniel@???> writes:
> On 23/03/16 11:35, Adam Borowski wrote:
>> On Tue, Mar 22, 2016 at 03:53:26PM +0000, Rainer Weikusat wrote:
>>> Daniel Reurich <daniel@???> writes:
>>>> whether you wan to create a root password is prompted for in the
>>>> installation. If you choose not to then sudo will be installed
>>>> otherwise not.
>>>
>>> This seems a bit arbitrary: System I manage usually have a root password
>>> set and sudo installed. The root password is for emergency remote
>>> access
>
> I'd love to be able to give fine grained control over what is installed,
> but given that we have powerful tools like apt for that make
> post-installing whatever package you want dead easy, I don't see a
> pressing need to either always install sudo just to fit a particular use
> case.

I wasn't suggesting/ requesting that sudo should always be installed
automatically, rather the opposite: Setting or not setting a root
password during install is not a good indicator of how the system's
going to be used/ managed afterwards. Eg, using the "traditional UNIX(*)
installation" example, someone might want to install a particular
encrypted password once he's able to ssh into a machine it can be
retrieved from. Or use a randomly generated one supposed to be set once
the program supposed to generate it has been installed. Even if that's
only

dd if=/dev/random bs=16 count=1 | base64

"during base system installation" may be a very inconvenient time to run
that.

Even this is only a theoretical concern. I'm still a regular dselect
user because because dselect makes it easy to go through everything
installed on a system and get rid of whatever wasn't supposed to be
installed.