I am not sure of the difference between text mode and graphical mode, except that I am an end-user of anaconda,
and I use it via the Everything.iso. Therein, anaconda is a mixed mode, with text / graphical for partition management(creating, mounting,deleting)
and graphical mode for application and application-group selection/subselection.
FWIW, I like the existing functionality, with one suggest enhancement -- put a 2 line text description for each of the subgroups that are part of a main group.
Leslie Satenstein
On Monday, November 27, 2023 at 11:22:17 a.m. EST, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
On Mon, 2023-11-27 at 14:12 +0100, mkolman@xxxxxxxxxx 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 would simplify the whole thing, as there would be less scenarios
> to test/debug/go wrong.
The problem, as always, is different use cases. We want to very
strongly encourage people to create a user before logging in on KDE
installs, as we really don't want people using KDE as root. But for a
small headless install, someone might want to operate as root without a
user account.
Workstation has sorted this out by disabling user/root spokes in the
installer entirely and having its own g-i-s which requires creation of
an admin user, but we don't have anything like that in place for KDE
currently. So we have to try and manage both KDE and e.g. a minimal or
Server install as best we can, using essentially the same workflows.
If someone wants to do some customization for KDE, of course, that
could help.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx
https://www.happyassassin.net
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> 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 would simplify the whole thing, as there would be less scenarios
> to test/debug/go wrong.
The problem, as always, is different use cases. We want to very
strongly encourage people to create a user before logging in on KDE
installs, as we really don't want people using KDE as root. But for a
small headless install, someone might want to operate as root without a
user account.
Workstation has sorted this out by disabling user/root spokes in the
installer entirely and having its own g-i-s which requires creation of
an admin user, but we don't have anything like that in place for KDE
currently. So we have to try and manage both KDE and e.g. a minimal or
Server install as best we can, using essentially the same workflows.
If someone wants to do some customization for KDE, of course, that
could help.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx
https://www.happyassassin.net
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
