Hi Adam,
Firstboot stays available in RHEL for this reason (legacy plugins). Fedora
modules will probably have to be updated. At least that was the plan. It is
very easy to write a new module with the new API. Ping vpodzime, he has a
development guide.
--
Martin Sivák
msi...@redhat.com
Red Hat
Hi,
Just to clarify things.
Anaconda currently requires root password OR user with administrator privileges
(wheel group). So if you set root password in Anaconda, initial-setup will
start, but can be dismissed immediately.
It might be good idea to add some explanation text to initial-setup to
Hi,
a quick note before I start: I am no longer maintainer of initial-setup. But
since I started it I will answer some of the questions.
> the main reason why we still have i-s while it's possible to do these
> setup tasks in Anaconda itself are OEM installations. And I'm pretty
> sure we don't
Hi,
the this should be not a problem.
The intended logic here is requiring enabled root OR user(s). We might add ssh
keys as a valid option if needed too (but I am not sure about entering the key,
typing it manually is probably not a good idea).
Moreover, initial-setup has a working quit butto
Hi,
> > When I install a freeipa server I do not want firstboot because I
> > am not
> > going to create local users anyway. I am going to install freeipa
> > and
> > then create users in LDAP.
> Could such use cases not be built into firstboot?
Right you are, see another proposed feature that
Hi,
this has nothing to do with Gnome. Initial-setup will prepare system-wide
settings regardless on the WM as firstboot did.
The only difference here (which is not implemented yet) is to skip the user
creation screens in case GDM is the login manager and Gnome asks for it. In
that case GIE pa
Hi,
yes, all the screens are shared with the Anaconda installer and the internal
data structure is closely tied to kickstart. This allows us to configure almost
everything using kickstart and then dump the final kickstart for the admin to
see (as we always did).
Headless is a bit harder, someo
Hi,
the tool will be started using systemd unit file which can be disabled. It will
have to be explicit (even minimal install needs users or root password), but we
can figure something out.
Martin
- Original Message -
>
> > From: Jaroslav Reznik
> >
> > = Features/NewFirstboot =
> >
Hi,
no, system-config-* is not going to be used anywhere.
Martin
- Original Message -
> Jaroslav Reznik wrote:
> > = Features/NewFirstboot =
> > https://fedoraproject.org/wiki/Features/NewFirstboot
> >
> > Feature owner(s): Martin Sivák
> ...
>
> Firstboot currently depends on system-
Hi Adam,
it will use Anaconda screens that already exist (like Time and Date, Root
password) or are planned for F19 (User creation). So the project itself does
not require any heavy coding. The 3rd party screens are out of our hands, but
are not necessary for the system to work.
The current fi
Hi,
> If/when the "real work" behind a feature has been done early enough,
> getting from Fedora alpha to final consists of just a few bugfixes
Ah well.. only if everybody else did this so all the dependencies are stable.
In which case you just moved the development freeze to earlier date. No
im
11 matches
Mail list logo
