Hi Gábor, Gabor Barnabas Gero <[email protected]> skribis:
> In a recent home configuration, I added a service to automatically > start the Emacs daemon. Afterwards, the shepherd.conf item in the > store throws an exception and the system refuses to continue > booting. The error disappears when I roll back to an older generation, > and the shepherd socket is created but booting still doesn't continue > and name resolution doesn't work, even after deleting resolv.conf and > restarting NetworkManager multiple times. What can I do? Could you send (1) the exception/error you’re seeing and the command that produced it, and (2) the system configuration that led to this? These are necessary so one can help understand the problem. Thanks in advance, Ludo’.
