Re: Fedora 33 System-Wide Change proposal: systemd-resolved

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Observations based on Fedora-Workstation-Live-x86_64-33-20200828.n.0.iso

1. The ext4+squashfs image on media has no /etc/resolv.conf at all;
this is what forms the basis of /dev/mapper/live-base, and is the
source for installations (copied by rsync).

2. The installation live environment uses /dev/mapper/live-rw as
system root; it has an /etc/resolv.conf symlink pointed to
/run/systemd/resolve/stub-resolv.conf

3. The installed system has an /etc/resolv.conf file following
installation (while still in the installation environment). First line
is:
# This file is managed by man:systemd-resolved(8). Do not edit.

4. Following a reboot, the system has an /etc/resolv.conf file. First line is:
# Generated by NetworkManager


Are these the expected behavior?

--
Chris Murphy
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux