On Mon, Jan 28, 2013 at 1:34 PM, Canek Peláez Valdés <can...@gmail.com> wrote:
> On Mon, Jan 28, 2013 at 1:25 PM, Stefan G. Weichinger <li...@xunil.at> wrote:
>> Am 28.01.2013 20:08, schrieb Canek Peláez Valdés:
>>
>>> I saw that mgorny unmasked systemd, and I'm installing it as of right
>>> now. I hope to have no problems, but I still don't know how they
>>> managed to install udev in / and systemd in /usr without problems.
>>> Perhaps it will "just work" as long as /usr is not in its own
>>> partition, or you use an initramfs.
>>
>> I don't have /usr separated so it doesn't matter for me right now.
>>
>> Do you use gnome/gdm? If yes, would you share use-flags and
>> service-file? Thanks!
>
> I just booted with udev/systemd-197.  The only error was:
>
> Failed at step EXEC spawning /usr/bin/udevadm: No such file or directory
>
> Which was kinda what I was expecting, since udevadm moved to /bin.
> However, everything (except plymouth-start.service) works. The error
> happens inside the initramfs, just before the switch-root, so perhaps
> I can fix it by putting a link to udevadm in /usr/bin in my initramfs.

I had to put the link in both the initramfs (made a trivial dracut
module to do it), and in the filesystem. The error went away, and
everything works, including plymouth-start.service (I don't know why I
still have it, my laptop boots so fast I almost don't see the splash).
I have zero failed units in systemctl --full --all.

I also took the plunge and removed both 70-persistent-net.rules
80-net-name-slot.rules; my laptop uses NetworkManager, so everything
just  keep working, but now my network interfaces have silly new
names:

# ifconfig | grep UP
enp0s25: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

So the only problem was udevadm in /bin instead of /usr/bin, but
apparently (in my laptop at least) only plymouth-start.service needs
it.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Reply via email to