Am 14.06.2022 um 06:25 schrieb Matthew Miller
<mattdm(a)fedoraproject.org>:
On Mon, Jun 13, 2022 at 11:08:21PM +0200, Peter Boy wrote:
> So we might have to handle this differently for desktop type and server
> type systems.
I think the key difference is whether basic configuration is
expected as part of Anaconda, or whether there's a further configuration
step. The first approach is common for individual desktop or server
installs. But the latter is common for image-based installs -- whether it be
Fedora IoT or a server VM or cloud image, or a pre-installed desktop.
Given that cloud-init, for example, can configure a system as fine-grained as Anaconda, I
think it's more about whether a system is running in a managed or unmanaged
environment.
Practically more important seems to me that Anaconda on the workstation live medium is so
reduced that you can configure neither the network nor a hostname (only keyboard, storage
medium and time zone). Therefore, we need to configure a plausible default hostname on
desktops anyways, and the Change Proposal is for server type systems only.
And with server type systems, perhaps we can assume that system administrators knows what
they are doing?