On Mon, 2023-11-27 at 08:51 -0500, Neal Gompa wrote:
On Mon, Nov 27, 2023 at 8:13 AM <mkolman(a)redhat.com> wrote:
>
> On Fri, 2023-11-24 at 15:15 -0800, Adam Williamson wrote:
> > On Tue, 2023-11-21 at 13:34 +0100, Jiri Konecny wrote:
> > > Hello everyone,
> > >
> > > Is Anaconda Initial Setup important for your project or
> > > workflow?
> > > What
> > > functionality is absolutely necessary for you? Do you use the
> > > text
> > > mode
> > > or the graphical mode? Are you aware of any alternatives? Is
> > > there
> > > anything that would prevent you from migrating to one of the
> > > proposed
> > > alternatives? Also please feel free to share this mail to any
> > > relevant
> > > groups.
> >
> > In addition to the other uses identified: if you do a KDE install
> > and
> > set the root password but do not create a user account, i-s will
> > run
> > on
> > first boot and allow (not sure if it requires) user creation.
> > This is
> > probably the case for other non-GNOME desktops too (GNOME uses
> > its
> > own
> > gnome-initial-setup).
> Sure, but is this really necessary on those images ? If it only
> triggers if no user account is present only only provides user
> creation, what about enforcing user creation at installation time
> instead ?
>
That is not possible in all cases. Two cases offhand that it is not
possible on:
* ARM images
* OEM preload images
These two cases require us to not pre-configure a user but also allow
the user to be created on first boot.
Sure - those require to run int the reconfig
mode, where Initial Setup
provides access to all the screens it can run on a booted machine.
I was just wondering if the Live media use case, where Initial Setup
only creates a user account if none is created at installation time
makes sense & could be perhaps replaced by Anaconda just requiring
users to create a user at installation time on the Live images.
That could reduce the overall complexity a bit. :)