On Fri, 2022-12-09 at 13:23 +0000, Timothée Ravier wrote:
Sorry I'm late here but while I agree with the idea, I don't
think
the implementation is done at the right level.
As currently implemented, this will likely fail as the network won't
be available / ready:
https://pagure.io/fedora-autofirstboot/blob/main/f/systemd/fedora-autofir...
IIRC that was the issue we hit when we investigated the idea to do
package updates or adding language packs in the target system chroot
after the Live iso base layer has been rsynced to the disk.
There might not be any network conectivity at this point, as the live
image is by default offline capable and thus does not require the user
to setup networking before starting the installation.
This will also mutate rpm-ostree based systems on first boot
(Silverblue & Kinoite), losing all the benefits of using a single
image for everyone and making the update slower for everyone by
default.
I think that this is better implemented in a per-desktop app on first
session startup on in the GNOME initial setup interface or
corresponding project for other desktops.
Having that done in a user visible interface will also surface errors
where in this current implementation, any error will mostly be
silently ignored.
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue