Re: systemd woes continue
On Mon, Sep 16, 2019 at 09:38:55PM -0500, Bob Tracy wrote: > I say "almost clean", because a recent update managed to break my > resolver configuration: "/etc/resolv.conf" came up completely empty, in > spite of "/etc/network/interfaces" having the requisite > "dns-nameservers" and "dns-search" lines for my primary interface (eth0). > The "resolvconf" package is definitely installed, but I'm guessing some > new interaction between "systemd", "NetworkManager", and possibly > "resolvconf" is, er, ah, unfortunate. It appears that all the configuration info in "/etc/network/interfaces" for my "eth0" interface was completely ignored other than the IPv4 address. No IPv6 address, no "dns-*" config items, etc. Thanks, systemd! Not :-(. I blame "systemd", because, when it was still dropping me into emergency mode, "eth0" came up correctly. --Bob
RE: systemd woes continue
Many thanks to all who have been putting effort into this issue. I plan to download the lasted build and try booting my AlphaStations again. -Original Message- From: John Paul Adrian Glaubitz [mailto:glaub...@physik.fu-berlin.de] Sent: Tuesday, September 17, 2019 7:27 AM To: Bob Tracy Cc: debian-alpha@lists.debian.org Subject: Re: systemd woes continue Hi Bob! On 9/17/19 4:38 AM, Bob Tracy wrote: > Verified. Life is now better, if not good :-). This is the first time > I've been able to accomplish an "almost clean" boot of my Alpha in MANY > months. Great. Thanks for confirming. > I say "almost clean", because a recent update managed to break my > resolver configuration: "/etc/resolv.conf" came up completely empty, in > spite of "/etc/network/interfaces" having the requisite > "dns-nameservers" and "dns-search" lines for my primary interface (eth0). > The "resolvconf" package is definitely installed, but I'm guessing some > new interaction between "systemd", "NetworkManager", and possibly > "resolvconf" is, er, ah, unfortunate. Unless you actively enabled systemd-networkd/systemd-resolveconfd, they don't become active on their own. And NetworkManager is not related to systemd. I do recommend setting up systemd-networkd/systemd-resolveconfd for headless machines though as it makes network configuration rather painless. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: systemd woes continue
Hi Bob! On 9/17/19 4:38 AM, Bob Tracy wrote: Verified. Life is now better, if not good :-). This is the first time I've been able to accomplish an "almost clean" boot of my Alpha in MANY months. Great. Thanks for confirming. I say "almost clean", because a recent update managed to break my resolver configuration: "/etc/resolv.conf" came up completely empty, in spite of "/etc/network/interfaces" having the requisite "dns-nameservers" and "dns-search" lines for my primary interface (eth0). The "resolvconf" package is definitely installed, but I'm guessing some new interaction between "systemd", "NetworkManager", and possibly "resolvconf" is, er, ah, unfortunate. Unless you actively enabled systemd-networkd/systemd-resolveconfd, they don't become active on their own. And NetworkManager is not related to systemd. I do recommend setting up systemd-networkd/systemd-resolveconfd for headless machines though as it makes network configuration rather painless. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
