Skip to main content ↑ ↓
Topic: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1 (Read 2919 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

I was switching on wifi via a file.start in /etc/local.d and the local service was in the nonetwork runlevel, which is some kind of transitional runlevel. But after the recent  update which upgraded openrc (0.61-3 -> 0.62.2-1) this no longer ran at boot. Switching the local service from nonetwork to default resolved this, I can't even remember why it was in nonetwork in the first place.
I'm not sure this represents any kind of problem as such, but it might be worth mentioning in case anyone else was using nonetwork.

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #1 –
On this PC, I don't use a network connection manager.

Yesterday when I started my system after updates (including openrc) I lost my internet connection.  :o

After some research on this forum, I found this solution:
"Then just enable service dhcpcd in your init"
https://forum.artixlinux.org/index.php/topic,5625.msg35312.html#msg35312

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #2 –
OpenRC 0.62.2 requires services local, localmount and netmount to be added to runlevel default.

This can be done with commands:

- rc-update add local default
- rc-update add localmount default
- rc-update add netmount default

artist

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #3 –
Quote from: Artist – on
OpenRC 0.62.2 requires services local, localmount and netmount to be added to runlevel default.

This can be done with commands:
- rc-update add local default
- rc-update add localmount default
- rc-update add netmount default
Done  8)
Thanks !

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #4 –
I am confused.  Can someone clarify why this has to be done and what this provides.

I am on a wire and I use /etc/init.d/net.lo and /etc/init.d/net.eth0 and /etc/init.d/net.eth1

That is on my gateway system and I can't really afford to lose those hard coded routes and ethernet assignments.

On my workstation /etc/init.d/net.eth0 is gone.

On my server I have /etc/conf.d/net

Quote
[ruben@www3 init.d]$ cat /tmp/net
config_eth0="96.57.23.83/29"
config_eth1="10.0.0.37/24"
routes_eth0="default via 96.57.23.81
96.57.23.80/29 via 96.57.23.81 dev eth0"
dns_domain_eth1="mrbrklyn.com"
dns_servers_eth1="10.0.0.37 166.84.1.2"
dns_domain_eth0="mrbrklyn.com"
dns_servers_eth0="96.57.23.83  166.84.1.2"

But I haven't run the update on it yet

Those far, networking has been simple and straight forward with artix and I hope it remains that way.

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #5 –
This is an upstream change and I do not know if it change is documented somewhere.

The standard way for the network setup on OpenRC is via dynamic service net.lo to which soft links can be created for other devices. All defined in /etc/conf.d/net.

Related info is also available in our wiki: https://wiki.artixlinux.org/Main/OpenRC#Network_management

artist

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #6 –
I am also confused. Sounds like this update shouldn't cause mrbrklyn's issues.

What is the actual change? Is the nonetwork runlevel no more?

I don't use netmount at all (no network shares to mount). I can still keep the service disabled if I don't use it, right?

Quote from: Artist – on
Related info is also available in our wiki: https://wiki.artixlinux.org/Main/OpenRC#Network_management
Slightly off topic: in that wiki it says "netifrc is not mandatory for OpenRC", but the openrc package still depends on netifrc. Which is wrong?

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #7 –
This network change is not one we were aware of. With the setup I described we had/have no network related problems. Any details that can help us reproduce the problem are welcome.

artist

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #8 –
This isn't really about networking specifically.  From what I understand, nonetwork is a transitional runlevel which was intended to be used on the switchover between full runlevels. So you went from boot to nonetwork to default. Now you go straight from boot to default without passing through nonetwork. The nonetwork name is just a name and could include any services, they don't have to be networking related. The nonetwork runlevel still exists, you can see it in /etc/runlevels but for whatever reason it isn't being used as before.
So, as explained elsewhere, if you see any services in the nonetwork level you might want to move them to default instead:
Code: [Select]
$ rc-update
(check if any line says nonetwork)
# rc-update del servicename nonetwork
# rc-update add servicename default
But if you didn't have any services in there which you were using, you might not need to do this.

Re: nonetwork runlevel not being entered at boot after OpenRC upgrade to 0.62.2-1

Reply #9 –
Updating another machine I could see that before the OpenRC update, local was in both the default and nonetwork runlevels, while afterwards it was only in nonetwork, the update actually removed the service from default, so the problem was not quite what I had thought.