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:glaubitz@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 - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: