Hi. On Mon, 28 Oct 2024 01:04:39 -0400 Felix Miata wrote: > ToddAndMargo composed on 2024-10-27 21:51 (UTC-0700): >> On 10/27/24 19:59, Felix Miata wrote: >>> Just because other packages require its installation doesn't mean you must allow >>> to be used. All my installations have systemd-resolvd.service disabled and masked, >>> and I have an old-fashioned genuine plain text file /etc/resolv.conf. :) >> I had done something similar to that. Unfortunately, >> upgrade releases turn the buzzard back on. > WRT masked, there is no "something similar". Simply disabling isn't enough to > prevent an upgrade from reverting to package default. Disabling the service must > be followed by masking the service. Yes, but it is safer to also declare the preset disabled, as follow (for example): --------- /usr/lib/systemd/system-preset/50-disable.preset --------- disable systemd-resolved.service -------------------------------------------------------------------- The various scriptlets of the systemd-resolved RPM will then not enable it, even if something unmask the service. Note also that the posttrans scriptlet of the systemd-resolved RPM may recreate the resolv.conf link if the systemd-resolved preset is enabled (and not masked). -- francis -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
