On Sun, Sep 19, 2021 at 07:20:07AM +0200, Peter Boy wrote:
> Am 19.09.2021 um 05:28 schrieb Matthew Miller <mattdm(a)fedoraproject.org>:
> See this thread
> for some good rational from Patrick Riehecky (which refers to the Fedora
> wiki), and this bugzilla issue: https://bugzilla.redhat.com/show_bug.cgi?id=2004572
> Personally, I agree with Pat -- on by default is a good choice -- but I also
> think that at the least, we should also turn on notifications by default.
An interesting thread! I am unsure, however, to what extent I am "(not)
amused" by your suggestion to enable the 'automatically apply updates'
feature in Fedora Server by default as a kind of field test for CentOS. :-)
In any case, I would include this topic in our post-installation documentation.
That's really an omission right now.
I consider it a very good idea to enable the 'notify' option via
pre-installation. I don't know if this would still be possible for Fedora 35.
But for this to be really effective, we need a real e-mail address (or rather a list) for
root as part of the installation procedure. However, this means a change in Anaconda - a
pretty major operation. Alternatively, we could reactivate the earlier 'First
Boot' routine and put that in there. That might be easier and sooner to implement (and
a UX test bed for an Anaconda change).
Yeah, notify doesn't help if it's not notifying anyone. ;)
I don't think it makes sense to be in first boot... many people install
servers and instances in an automated way and expect it to just boot and
work, not needing to access console to answer questions. :(
So, I fear yeah, this would be a major anaconda modification.
Not saying thats impossible, but it would be a lot of work...
This matter is very serious and we should definitely urge the
administrator to consider and make a decision - in Anaconda, kick file or firstboot. And
if an administrator does not care and there is no real address for a notifications email,
then maybe a default of 'apply' is an expedient solution.
Well, I don't think forcing a first boot for server installs is very
Auto applying updates is nice, but it doesn't restart the things it
applies, so it could also be a bit of a 'false' sense of security. "Oh,
my machines apply all updates every night, they are safe".
Perhaps it would be possible to add a option to anaconda for updates.
manual -> just like it is now, nothing is applied automatically.
auto -> apply updates nightly with dnf-automatic
auto-offline -> apply updates nightly and do so offline at XX:YY
Then a notify or not option asking for email address.
But I guess this is all getting a bit too complex...