On Sun, Jul 19, 2020 at 03:40:41PM +0200, Michael Biebl <[email protected]> wrote: > Maybe you start with a minimal debian system and turn that bit by bit > into a system like the one where you encounter the problem to see which > change is causing it.
Unfortunately, I was away for a bit and when I returned some helpful person had it set up from scratch, deleting the old installation. I was told that /var/tmp had wrong permissions (1700 instead of 1777), so maybe that was the reason for the problem, although when I manually chmod 1700 /var/tmp, I can't reproduce the problem with the fresh setup, either. > I do also notice, that you run a 5.7.0 kernel. So this appears to be a > jessie->buster upgraded system with a mix of unstable/testing. > Maybe there is some configuration mixed/messed up. Certainly, although the kernel was added afterwards (the whole upgrade was to get a more recent kernel for newer hardware, and more specifically, a debian kernel, as we used mainlinme-ppa kernels before). On Sun, Jul 19, 2020 at 05:03:21PM +0200, Michael Biebl <[email protected]> wrote: > getent passwd systemd-network Already sent this one - I don't think resolving the passwd/group entries were the problem, something else went wrong, and the problem here is just very bad error reporting. Anyway, I'm sorry to not be able to provide closure here, I did reserve the pxe environment for further debugging, but due to circumstances out of my control, it has been deleted. A fresh buster setup, not surprisingly, works fine. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / [email protected] -=====/_/_//_/\_,_/ /_/\_\
