On 10 May 2011 22:26, Daniel Drake wrote:
> If I log the error after it tries to connect to /run/systemd/private, I get:
> Failed to connect to socket /run/systemd/private: No such file or directory
>
> Indeed, there's nothing at that path, and the only thing in
> /run/systemd/ is an empty directo
On 9 May 2011 22:46, Lennart Poettering wrote:
> You are lacking autofs4 support in the kernel. You should fix this first.
I'm not, autofs4 is present, we're working on figuring out on why
systemd complains at
https://bugs.freedesktop.org/show_bug.cgi?id=36993
> Your udev in your initrd is a dif
On Mon, 09.05.11 21:57, Daniel Drake (d...@laptop.org) wrote:
> Hi,
>
> Another systemd error I am encountering is:
>
> Failed to get D-Bus connection: Failed to connect to socket
> /org/freedesktop/systemd1/private: Connection refused
>
> The message appears a lot throughout boot, full logs he
Hi,
Another systemd error I am encountering is:
Failed to get D-Bus connection: Failed to connect to socket
/org/freedesktop/systemd1/private: Connection refused
The message appears a lot throughout boot, full logs here:
http://dev.laptop.org/~dsd/20110509/systemd-boot.txt
It also means I can't
