Artix Linux Forum

Just a quick question. Is there any reason to be concerned about this error? On boot, I get this message and I don't know why.

Code: [Select]

[    3.670727] elogind[605]: Failed to connect to system bus: No such file or directory
[    3.670770] elogind[605]: Failed to fully start up daemon: No such file or directory

As far as I can tell, this does absolutely nothing. I have dbus and elogind up and running just fine over here. I don't know why it's giving me that message unless I'm just forgetting a service.

Would it possibly ever be one installer that would provide the choice of the init system?  It would be one installer for two distributions and I don't think this ever existed.
Fascinating when most others struggle with one.

Would it possibly ever be one installer that would provide the choice of the init system?

Code: [Select]

https://wiki.artixlinux.org/Runit/Runit    -->
After installing runit, make sure to copy these directories to /usr/bin. 

This seems a little vague, which directories? 

Code: [Select]

ls -la /usr/bin
lrwxrwxrwx 1 root root        10 Apr 18 17:26  init -> runit-init
lrwxrwxrwx 1 root root        29 Apr 18 18:03  halt -> /usr/lib/runit-artix/bin/halt
lrwxrwxrwx 1 root root        30 Apr 18 18:03  pause -> /usr/lib/runit-artix/bin/pause
lrwxrwxrwx 1 root root        33 Apr 18 18:03  shutdown -> /usr/lib/runit-artix/bin/shutdown
lrwxrwxrwx 1 root root        37 Apr 18 18:03  modules-load -> /usr/lib/runit-artix/bin/modules-load
lrwxrwxrwx 1 root root        28 Apr 18 18:03  zzz -> /usr/lib/runit-artix/bin/zzz
lrwxrwxrwx 1 root root         4 Apr 18 18:04  poweroff -> halt
lrwxrwxrwx 1 root root         4 Apr 18 18:04  reboot -> halt
lrwxrwxrwx 1 root root         3 Apr 18 18:07  bin -> bin

Does this look right?

Code: [Select]

ls -al /etc/runit/sv
total 60
drwxr-xr-x  6 root root 4096 Apr 18 17:14 ..
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-tty6
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-tty4
drwxr-xr-x 15 root root 4096 Apr 18 17:14 .
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-console
drwxr-xr-x  2 root root 4096 Apr 18 17:14 sulogin
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-ttyUSB0
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-ttyS0
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-tty5
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-tty2
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-tty1
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-generic
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-ttyAMA0
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-tty3
drwxr-xr-x  2 root root 4096 Apr 18 17:14 agetty-serial

I did what the wiki said, forced removal of openrc otherwise it will not be replaced, edite the init line in grub,
then system would halt after trying to boot.  I only caught a couple of lines from the top that looked like runit before it halted.
chroot was not easy either, it seems as it lost the ln for bash so artools-chroot /mnt  /usr/bin/bash   eventually worked
there seems to be a directory instead of a link called bin that had a link to the init system in it, I have no clue how it got there.

Code: [Select]

lrwxrwxrwx  1 root root   10 Apr 16 10:54 init -> runit-init

I took all my service scripts (thinking anythin with -openrc will have an -runit) and rename them into -runit trying to install them:

Code: [Select]

error: target not found: inetutils-runit
error: target not found: kmod-runit
error: target not found: openvpn-runit
error: target not found: eudev-runit
error: target not found: displaymanager-runit
error: target not found: cryptsetup-runit

The rest were ok.

The system is locked in read only mode, somehow, and /usr/bin /bin link is missing

The only way to chroot is if I specify where a shell is #artools-chroot /mnt /usr/bin/bash

When I attempt to boot in either normal or recovery I get 2-3 lines on top (same as I did with void) and within 2-3" the systems shutsdown.  It is so fast I doubt runit has saved any logs, but I am willing to look if you tell me where.

No both runit and runit artix were installed, also all the relevant -runit files except for the services I didn't find any, as listed above.
The system never had a problem before, sddm, openbox, and I followed all steps.
It was updated/upgraded just the day before.
Why am I chrooting?  Because instead of boot it just shutsdown.
The /usr/bin link was there, for sure, before the runit installation.  I have no idea what went wrong, I just followed the steps on wiki like you mention earlier on the post.  When I tried to reboot  --- puff ---  nada --

Should I try through chroot (artools) to reinstall openrc ?

I just left it as it was so I don't do anything to harm it more.  How do you recreate the link from chroot?  It says it can't because it is a read only system.