On Sun, Dec 7, 2014 at 2:11 AM, Martin Pitt wrote:
> Tom H [2014-12-05 8:03 -0500]:
>>>
>>> | $ grep ifup /lib/udev/rules.d/99-systemd.rules
>>> | SUBSYSTEM=="net", KERNEL!="lo", TAG+="systemd",
>>> ENV{SYSTEMD_ALIAS}+="/sys/subsystem/net/devices/$name",
>>> ENV{SYSTEMD_WANTS}+="ifup@$name.serv
Hey Tom,
Tom H [2014-12-05 8:03 -0500]:
> > | $ grep ifup /lib/udev/rules.d/99-systemd.rules
> > | SUBSYSTEM=="net", KERNEL!="lo", TAG+="systemd",
> > ENV{SYSTEMD_ALIAS}+="/sys/subsystem/net/devices/$name",
> > ENV{SYSTEMD_WANTS}+="ifup@$name.service"
>
> I noticed this after sending my origin
On Fri, Dec 5, 2014 at 5:30 AM, Martin Pitt wrote:
> sorry for the late answer!
>
> Tom H [2014-11-03 15:06 -0500]:
>> "Cannot add dependency job for unit systemd-vconsole-setup.service,
>> ignoring: Unit systemd-vconsole-setup.service failed to load: No such
>> file or directory." is in the out
Hey Tom,
sorry for the late answer!
Tom H [2014-11-03 15:06 -0500]:
> "Cannot add dependency job for unit systemd-vconsole-setup.service,
> ignoring: Unit systemd-vconsole-setup.service failed to load: No such
> file or directory." is in the output of journalctl until I remove
> "systemd-vconsole