Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [TRACKER] Runit support (Read 15369 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: [TRACKER] Runit support

Reply #45 –
I gave up, everything working but can't get networkmanager to work.
I did start the service, it is there in /run/runit with all the other services, eth0 seems active, has a mac address, no connection.
Maybe I should try something like connman ?
Tired of rebooting though.

Re: [TRACKER] Runit support

Reply #46 –
Instead of making 3 separate post, can't you just edit your latest post in case there are no new replies? Seriously.

I want to check if we have the same runit-artix package. Do you have the latest runit-artix installed in [gremlins] (20180414-4)? Here's the PKGBUILD.

The 20180414-2 package is faulty, but it should be fixed in the latest 20180414-4, your mirror seems not to be syncing with our builds.

Quote from: fungalnet – on
1  https://smarden.org/runit  that you have in the wiki is dead
Try http://smarden.org/runit/

Quote from: fungalnet – on
I just have a hard time understanding how anyone used these particular packages and got the system to work.
To double check the problem went back to gremlins and reinstalled your artix runit pkg and runit istelf and it did the same exact thing again.  It removed the bin link, made a bin directory and placed the init link inside the /bin.
So I moved the init link into /usr/bin and recreated the bin link to /usr/bin
It is your package that screwes this up, not me!

I don't know. Try to ask one of the early runit testers @CustomerServiceRobot.

Also, if you want something stable, don't use [gremlins].

Quote from: fungalnet – on
I gave up, everything working but can't get networkmanager to work.
I did start the service, it is there in /run/runit with all the other services, eth0 seems active, has a mac address, no connection.
Maybe I should try something like connman ?
Tired of rebooting though.
Did you install networkmanager-runit? If you have, try to check what's wrong with nmtui. NetworkManager is out of this thread's scope since "works on my machine". You may want to go to the IRC.
now only the dinit guy in artix

Re: [TRACKER] Runit support

Reply #47 –
This is live now 10:42 GMT 11:42 London time
Code: [Select]
1 gremlins/runit-artix 20180414-2 (init) [installed]
    Runit initscripts for Artix
2 system/runit-artix 20180414-1 [installed: 20180414-2]
    Runit initscripts for Artix

is your -4 pkg in goblins?

This is what I installed before with chroot when I got a net connection, on top of the networkmanager and wicd (that never worked) that I had before.

Code: [Select]
[2018-04-20 11:43] [ALPM] installed libnfnetlink (1.0.1-2)
[2018-04-20 11:43] [ALPM] installed libnetfilter_conntrack (1.0.6-1)
[2018-04-20 11:43] [ALPM] installed dnsmasq (2.79-1)
[2018-04-20 11:43] [ALPM] installed dnsmasq-runit (20180226-1)
[2018-04-20 11:43] [ALPM] installed dhcp (4.4.1-4)
[2018-04-20 11:43] [ALPM] installed dhcp-runit (20180226-1)

I had to activate eth0 manually though, all that appeared in ifconfig was lo when I logged in.

I don't know which actually helped and which is unnecessary yet, I just loaded things to get a connection somehow.

1 more question:  Is there anything around the original networkmanager used by artix (at least on the older installers) that is OpenRC dependent and I may have taken it off by removing OpenRC?
I noticed that:

Code: [Select]
system/netifrc 0.6.0-1 (base)
    Gentoo Network Interface Management Scripts

Will not install  unless I remove runit-artix  (that deffective -2 version that I am currently running on after patching the /bin link issue).

Re: [TRACKER] Runit support

Reply #48 –
Quote from: fungalnet – on
This is live now 10:42 GMT 11:42 London time
Code: [Select]
1 gremlins/runit-artix 20180414-2 (init) [installed]
    Runit initscripts for Artix
2 system/runit-artix 20180414-1 [installed: 20180414-2]
    Runit initscripts for Artix

is your -4 pkg in goblins?

This is what I installed before with chroot when I got a net connection, on top of the networkmanager and wicd (that never worked) that I had before.

There we go. It seems mirror1 is acting up again. It doesn't sync anything since 16 April. -4 is currently in gremlins, but the mirror isn't syncing right now.

Quote from: fungalnet – on
1 more question:  Is there anything around the original networkmanager used by artix (at least on the older installers) that is OpenRC dependent and I may have taken it off by removing OpenRC?
I noticed that:

Code: [Select]
system/netifrc 0.6.0-1 (base)
    Gentoo Network Interface Management Scripts

Will not install  unless I remove runit-artix  (that deffective -2 version that I am currently running on after patching the /bin link issue).

NetworkManager should be init-agnostic (unless you're using systemd, ofc). netifrc is a OpenRC-specific package.
now only the dinit guy in artix

Re: [TRACKER] Runit support

Reply #49 –
:)

I've never seen this before, my networking is ipv6 only, I can reach artixlinux.org but can't reach startpage ecosia or duckduckgo  :)

Code: [Select]
 ping -c 4 2a01:7e01::f03c:91ff:febc:322
PING 2a01:7e01::f03c:91ff:febc:322(2a01:7e01::f03c:91ff:febc:322) 56 data bytes
64 bytes from 2a01:7e01::f03c:91ff:febc:322: icmp_seq=1 ttl=52 time=83.8 ms
64 bytes from 2a01:7e01::f03c:91ff:febc:322: icmp_seq=2 ttl=52 time=84.0 ms
64 bytes from 2a01:7e01::f03c:91ff:febc:322: icmp_seq=3 ttl=52 time=82.9 ms
64 bytes from 2a01:7e01::f03c:91ff:febc:322: icmp_seq=4 ttl=52 time=83.7 ms

--- 2a01:7e01::f03c:91ff:febc:322 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 82.905/83.622/84.070/0.522 ms
[artix2@7010 ~]$ ping -c 4 51.255.48.78
connect: Network is unreachable

Unless ww4 is declared and DOD brought down the internet (ipv4)  :)

Re: [TRACKER] Runit support

Reply #50 –
Quote from: fungalnet – on
:)

I've never seen this before, my networking is ipv6 only, I can reach artixlinux.org but can't reach startpage ecosia or duckduckgo  :)

Code: [Select]
 ping -c 4 2a01:7e01::f03c:91ff:febc:322
PING 2a01:7e01::f03c:91ff:febc:322(2a01:7e01::f03c:91ff:febc:322) 56 data bytes
64 bytes from 2a01:7e01::f03c:91ff:febc:322: icmp_seq=1 ttl=52 time=83.8 ms
64 bytes from 2a01:7e01::f03c:91ff:febc:322: icmp_seq=2 ttl=52 time=84.0 ms
64 bytes from 2a01:7e01::f03c:91ff:febc:322: icmp_seq=3 ttl=52 time=82.9 ms
64 bytes from 2a01:7e01::f03c:91ff:febc:322: icmp_seq=4 ttl=52 time=83.7 ms

--- 2a01:7e01::f03c:91ff:febc:322 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 82.905/83.622/84.070/0.522 ms
[artix2@7010 ~]$ ping -c 4 51.255.48.78
connect: Network is unreachable

Unless ww4 is declared and DOD brought down the internet (ipv4)  :)


I don't know if this is intended by NM, but it seems NM just stopped trying IPv4 after detecting an IPv6 IP. A workaround would be use NM with dhclient as its DHCP resolver. Or using nmtui, in Wired connection (particularly in IPv4 Configuration Section), enable the "Require IPv4 addressing for this connection" checkbox.

This is out of scope of this thread so I suggest you to go to #artix IRC channel.
now only the dinit guy in artix

Re: [TRACKER] Runit support

Reply #51 –
I know it is not relevant to the thread but never in 9 months had I ever had networking issues till I switched to runit, so it is related.
On my other artix installation, a clone of the original, netifrc is installed, so I am wondering whether it is related.

Re: [TRACKER] Runit support

Reply #52 –
Personally, I've always found NetworkManager to be a giant pain that mysteriously breaks. I just use dhcpcd and the wpa_supplicant hook.

Re: [TRACKER] Runit support

Reply #53 –
Code: [Select]
warning: dnscrypt-proxy-runit: local (20180406-1) is newer than galaxy-gremlins (20180330-1)


# yaourt runit artix
1 gremlins/halt 0.2-1 [installed]
    Artix Linux's wrapper program for OpenRC and runit's shutdown scheme
2 gremlins/runit-artix 20180414-4 (init) [installed]
    Runit initscripts for Artix
3 system/runit-artix 20180414-1 [installed: 20180414-4]
    Runit initscripts for Artix
 

Re: [TRACKER] Runit support

Reply #54 –
It is broken again.  After the the new package (runit-artix-----4) came in, together with other upgrades, it did the same exact thing again, it removed the /bin link, and then I replaced it yet again. 
Now on boot it says it is waiting for the uuid=...  (the root partition) and then it says (10s) it is not responding and crashes at stage 1.

I asked before and you said you have modified the wiki, although I did not notice anything being modified.

https://wiki.artixlinux.org/Runit/Runit#runit-artix

Quote
If you want to use runit as your init, install the runit-artix.

After installing runit, make sure to link these files to /usr/bin.

These files has no reference, which files are you talking about?

Re: [TRACKER] Runit support

Reply #55 –
Quote from: fungalnet – on
It is broken again.  After the the new package (runit-artix-----4) came in, together with other upgrades, it did the same exact thing again, it removed the /bin link, and then I replaced it yet again. 

Code: [Select]
$ pacman -Qi
Name            : runit-artix
Version         : 20180414-4
Description     : Runit initscripts for Artix
Architecture    : x86_64
URL             : https://github.com/artix-linux/runit-artix/
Licenses        : custom:CC0
Groups          : init
Provides        : runit-init
Depends On      : procps-ng  awk  runit  sh  eudev  opentmpfiles
Optional Deps   : None
Required By     : elogind-runit
Optional For    : runit
Conflicts With  : openrc
Replaces        : None
Installed Size  : 169.00 KiB
Packager        : Unknown Packager
Build Date      : Fri 20 Apr 2018 06:33:01 AM WIB
Install Date    : Fri 20 Apr 2018 06:33:36 AM WIB
Install Reason  : Installed as a dependency for another package
Install Script  : Yes
Validated By    : None

$ pacman -Ql
runit-artix /etc/
runit-artix /etc/runit/
runit-artix /etc/runit/1
runit-artix /etc/runit/2
runit-artix /etc/runit/3
runit-artix /etc/runit/core-services/
runit-artix /etc/runit/core-services/00-pseudofs.sh
runit-artix /etc/runit/core-services/01-static-devnodes.sh
runit-artix /etc/runit/core-services/02-kmods.sh
runit-artix /etc/runit/core-services/02-udev.sh
runit-artix /etc/runit/core-services/03-console-setup.sh
runit-artix /etc/runit/core-services/03-filesystems.sh
runit-artix /etc/runit/core-services/04-swap.sh
runit-artix /etc/runit/core-services/05-misc.sh
runit-artix /etc/runit/core-services/08-sysctl.sh
runit-artix /etc/runit/core-services/99-cleanup.sh
runit-artix /etc/runit/crypt.awk
runit-artix /etc/runit/ctrlaltdel
runit-artix /etc/runit/functions
runit-artix /etc/runit/rc.conf
runit-artix /etc/runit/rc.local
runit-artix /etc/runit/rc.shutdown
runit-artix /etc/runit/reboot
runit-artix /etc/runit/runsvdir/
runit-artix /etc/runit/runsvdir/current
runit-artix /etc/runit/runsvdir/default/
runit-artix /etc/runit/runsvdir/default/agetty-tty1
runit-artix /etc/runit/runsvdir/default/agetty-tty2
runit-artix /etc/runit/runsvdir/default/agetty-tty3
runit-artix /etc/runit/runsvdir/default/agetty-tty4
runit-artix /etc/runit/runsvdir/default/agetty-tty5
runit-artix /etc/runit/runsvdir/default/agetty-tty6
runit-artix /etc/runit/runsvdir/single/
runit-artix /etc/runit/runsvdir/single/sulogin
runit-artix /etc/runit/shutdown-services/
runit-artix /etc/runit/shutdown-services/00-stop-services.sh
runit-artix /etc/runit/shutdown-services/01-random-seed.sh
runit-artix /etc/runit/shutdown-services/02-hwclock.sh
runit-artix /etc/runit/shutdown-services/03-stop-udev.sh
runit-artix /etc/runit/shutdown-services/04-killall.sh
runit-artix /etc/runit/shutdown-services/97-mount-ro.sh
runit-artix /etc/runit/shutdown-services/98-deactivate-crypt.sh
runit-artix /etc/runit/stopit
runit-artix /etc/runit/sv/
runit-artix /etc/runit/sv/agetty-console/
runit-artix /etc/runit/sv/agetty-console/conf
runit-artix /etc/runit/sv/agetty-console/finish
runit-artix /etc/runit/sv/agetty-console/run
runit-artix /etc/runit/sv/agetty-console/supervise
runit-artix /etc/runit/sv/agetty-generic/
runit-artix /etc/runit/sv/agetty-generic/finish
runit-artix /etc/runit/sv/agetty-generic/run
runit-artix /etc/runit/sv/agetty-serial/
runit-artix /etc/runit/sv/agetty-serial/conf
runit-artix /etc/runit/sv/agetty-serial/finish
runit-artix /etc/runit/sv/agetty-serial/run
runit-artix /etc/runit/sv/agetty-tty1/
runit-artix /etc/runit/sv/agetty-tty1/conf
runit-artix /etc/runit/sv/agetty-tty1/finish
runit-artix /etc/runit/sv/agetty-tty1/run
runit-artix /etc/runit/sv/agetty-tty1/supervise
runit-artix /etc/runit/sv/agetty-tty2/
runit-artix /etc/runit/sv/agetty-tty2/conf
runit-artix /etc/runit/sv/agetty-tty2/finish
runit-artix /etc/runit/sv/agetty-tty2/run
runit-artix /etc/runit/sv/agetty-tty2/supervise
runit-artix /etc/runit/sv/agetty-tty3/
runit-artix /etc/runit/sv/agetty-tty3/conf
runit-artix /etc/runit/sv/agetty-tty3/finish
runit-artix /etc/runit/sv/agetty-tty3/run
runit-artix /etc/runit/sv/agetty-tty3/supervise
runit-artix /etc/runit/sv/agetty-tty4/
runit-artix /etc/runit/sv/agetty-tty4/conf
runit-artix /etc/runit/sv/agetty-tty4/finish
runit-artix /etc/runit/sv/agetty-tty4/run
runit-artix /etc/runit/sv/agetty-tty4/supervise
runit-artix /etc/runit/sv/agetty-tty5/
runit-artix /etc/runit/sv/agetty-tty5/conf
runit-artix /etc/runit/sv/agetty-tty5/finish
runit-artix /etc/runit/sv/agetty-tty5/run
runit-artix /etc/runit/sv/agetty-tty5/supervise
runit-artix /etc/runit/sv/agetty-tty6/
runit-artix /etc/runit/sv/agetty-tty6/conf
runit-artix /etc/runit/sv/agetty-tty6/finish
runit-artix /etc/runit/sv/agetty-tty6/run
runit-artix /etc/runit/sv/agetty-tty6/supervise
runit-artix /etc/runit/sv/agetty-ttyAMA0/
runit-artix /etc/runit/sv/agetty-ttyAMA0/conf
runit-artix /etc/runit/sv/agetty-ttyAMA0/finish
runit-artix /etc/runit/sv/agetty-ttyAMA0/run
runit-artix /etc/runit/sv/agetty-ttyAMA0/supervise
runit-artix /etc/runit/sv/agetty-ttyS0/
runit-artix /etc/runit/sv/agetty-ttyS0/conf
runit-artix /etc/runit/sv/agetty-ttyS0/finish
runit-artix /etc/runit/sv/agetty-ttyS0/run
runit-artix /etc/runit/sv/agetty-ttyS0/supervise
runit-artix /etc/runit/sv/agetty-ttyUSB0/
runit-artix /etc/runit/sv/agetty-ttyUSB0/conf
runit-artix /etc/runit/sv/agetty-ttyUSB0/finish
runit-artix /etc/runit/sv/agetty-ttyUSB0/run
runit-artix /etc/runit/sv/agetty-ttyUSB0/supervise
runit-artix /etc/runit/sv/sulogin/
runit-artix /etc/runit/sv/sulogin/run
runit-artix /etc/runit/sv/sulogin/supervise
runit-artix /usr/
runit-artix /usr/bin/
runit-artix /usr/bin/init
runit-artix /usr/bin/modules-load
runit-artix /usr/bin/pause
runit-artix /usr/bin/zzz
runit-artix /usr/lib/
runit-artix /usr/lib/runit-artix/
runit-artix /usr/lib/runit-artix/bin/
runit-artix /usr/lib/runit-artix/bin/halt
runit-artix /usr/lib/runit-artix/bin/poweroff
runit-artix /usr/lib/runit-artix/bin/reboot
runit-artix /usr/lib/runit-artix/bin/shutdown
runit-artix /usr/share/
runit-artix /usr/share/licenses/
runit-artix /usr/share/licenses/runit-artix/
runit-artix /usr/share/licenses/runit-artix/LICENSE
runit-artix /usr/share/man/
runit-artix /usr/share/man/man1/
runit-artix /usr/share/man/man1/pause.1.gz
runit-artix /usr/share/man/man8/
runit-artix /usr/share/man/man8/modules-load.8.gz
runit-artix /usr/share/man/man8/zzz.8.gz

It doesn't even touch /bin, and I've done no modifications to /etc/runit/core-services/03-filesystem.sh. I don't know what happened to your system, but I'm sure it's not because, I quote "it's your package fault, not me!".

Quote from: fungalnet – on
Now on boot it says it is waiting for the uuid=...  (the root partition) and then it says (10s) it is not responding and crashes at stage 1.

Either it's stuck on initramfs (which shouldn't), or it doesn't want to remount /. But it shouldn't crash and go to stage3 since it'll launch an emergency shell instead.

Quote from: fungalnet – on
I asked before and you said you have modified the wiki, although I did not notice anything being modified.

https://wiki.artixlinux.org/Runit/Runit#runit-artix

These files has no reference, which files are you talking about?
This one.
now only the dinit guy in artix

Re: [TRACKER] Runit support

Reply #56 –
it goes to emergency cell but nothing works, no commands, no ttys nothing, only the power button works.
It says it can't locate the root partition, although it is there, the uuid is correct and it is checking fine.
Three different installations of runit-artix (2 of the -3 and 1 of the -4) did exactly the same thing, removed bin link.  The -3 version would replace it with a directory /bin/ that had the init link in it.  The -4 just removed it.  The system worked fine before the transaction with runit.  Should I attempt to put openrc back in it?  Other than following the instructions (partially) of moving from manjaro or arch to artix (disregarding the systemd removal) it is the only instructions I have in getting the system back. 

You do remember that it worked yesterday with the older runit-artix except for ipv4 connectivity, I only had ipv6.  When the repositories refreshed and brought the new gremlins files and I updated that is when it locked up.

This was not a fresh install, it is an old system, it had 11GB of files in it without /var/cache which is in a separate partition and without /home.  According to what you are circling above I just followed all the instructions, but I had to use --force to get it installed and removing openrc, which is not mentioned on the instructions.  Partially I think it was due some of the ***-openrc/-runscript files that had no -runit equivalents.

Re: [TRACKER] Runit support

Reply #57 –
Quote from: fungalnet – on
it goes to emergency cell but nothing works, no commands, no ttys nothing, only the power button works.
It says it can't locate the root partition, although it is there, the uuid is correct and it is checking fine.
Three different installations of runit-artix (2 of the -3 and 1 of the -4) did exactly the same thing, removed bin link.  The -3 version would replace it with a directory /bin/ that had the init link in it.  The -4 just removed it.  The system worked fine before the transaction with runit.  Should I attempt to put openrc back in it?  Other than following the instructions (partially) of moving from manjaro or arch to artix (disregarding the systemd removal) it is the only instructions I have in getting the system back.
You know, there's a reason I only provide -1 (system) and -4 (gremlins). Both -2 and -3 are faulty, and are not supported.
If you directly installed -4 from a faulty -3 and -2 package, it would "remove" /bin. But if you installed -4 (after yet another symlink from /bin to /usr/bin) after -1, it shouldn't happen as the only transaction happened is the symlink from /usr/bin/init to runit-init.

But for now, you can either go back to -1 or go back to openrc. runit builds are still in transitionary period and eventually OpenRC and runit will have one halt/poweroff/reboot/shutdown system so you and I both don't have to deal with this headache.

Quote from: fungalnet – on
You do remember that it worked yesterday with the older runit-artix except for ipv4 connectivity, I only had ipv6.  When the repositories refreshed and brought the new gremlins files and I updated that is when it locked up.

That's NM, and has no relevance in your problem now.

Quote from: fungalnet – on
This was not a fresh install, it is an old system, it had 11GB of files in it without /var/cache which is in a separate partition and without /home.  According to what you are circling above I just followed all the instructions, but I had to use --force to get it installed and removing openrc, which is not mentioned on the instructions.

Clearly you didn't read the wiki. If you used -4, runit-artix would conflict with openrc anyway.
Quote
WARNING: If you still have openrc installed, make sure to make the symlinks for halt, shutdown, poweroff and reboot in /usr/local/bin instead for easier deletion.
Quote from: fungalnet – on
Partially I think it was due some of the ***-openrc/-runscript files that had no -runit equivalents.
I explained the *-openrc files not existing in runit because of it being handled directly by /etc/runit/1.
now only the dinit guy in artix

Re: [TRACKER] Runit support

Reply #58 –
The wiki says nothing about invalid pkgs in the repository and the only mention of -4 in the wiki is a coincidental match in the uuid example.
It says in the wiki that there are pkgs in gremlins or should they be utilized, which were on my case, no it doesn't.
Does it say in the wiki that openrc conflicts with runit-artix?  Quite the opposite, it says IF you want to remove openrc and leave runit, you should add a modification in grub etc...

What is it in wiki that makes you think I did not read or follow?

Re: [TRACKER] Runit support

Reply #59 –
Quote from: fungalnet – on
The wiki says nothing about invalid pkgs in the repository and the only mention of -4 in the wiki is a coincidental match in the uuid example.
It says in the wiki that there are pkgs in gremlins or should they be utilized, which were on my case, no it doesn't.

The wiki didn't say anything about gremlins. Neither did the wiki mentions -4.

Quote from: fungalnet – on
Does it say in the wiki that openrc conflicts with runit-artix?  Quite the opposite, it says IF you want to remove openrc and leave runit, you should add a modification in grub etc...

The wiki was intended to follow stable releases, not testing.

The wiki also never said "IF you want to remove openrc", but to use runit as your init system.

But if you look at the PKGBUILD (or even take a careful look at pacman since if you installed openrc the conflict will trigger), it does conflict with runit-artix.
https://github.com/artix-linux/packages/blob/master/runit-artix/repos/testing-x86_64/PKGBUILD#L13

In the next packaging, both OpenRC and runit-artix will depend on one package which handles shutdown/halt/poweroff/reboot, but  testing will be needed.
now only the dinit guy in artix