Code: Select all
oldnet: Install the old type of network init-scripts with a symlink net.IFACE for each interfaceIs there any any actual documentation on how to migrate to and use the new network script (aside for the comments in the file)?
Code: Select all
oldnet: Install the old type of network init-scripts with a symlink net.IFACE for each interfaceWondering myself...AM088 wrote:The new OpenRC (0.5.1) got this new flag:So apparently now, instead of the usual net.eth0, net.wlan0, etc., there is a new way to do things; however, I can not find anything about it except the 0.5 announcement and announcement of the networking change...Code: Select all
oldnet: Install the old type of network init-scripts with a symlink net.IFACE for each interface
Is there any any actual documentation on how to migrate to and use the new network script (aside for the comments in the file)?


Yeah, an official guide is really needed.d2_racing wrote:In fact, it's time to have an official migration guide or something that we can read more about it officially.
The Funtoo doc is good, but we need a Gentoo guide too here
I am running with oldnet, so it is working fine. The reason I'm posting here is because I want to learn a new wayd2_racing wrote:Maybe if you use the use flag that disable the new stuff from OpenRc, then maybe you will be able to run like you are used to do.
If you find something, just post here


What if we already installed 0.5.1?d2_racing wrote:Until the release of an official guide, I will mask the 0.5 version or...

I mean the new use flag oldnetrahulthewall wrote:What does that mean?d2_racing wrote:... at least I will use new the use flag that remove all the new stuff.
Code: Select all
# quse -D oldnet
local:oldnet:sys-apps/openrc: Install the old type of network init-scripts with a symlink net.IFACE for each interface

iproute2 only exists in Linux, so no.sylware wrote:Come on, drop ifconfig support for good in the new openrc!
Again no, scripts should be portable across kernels and tools where possible.What is this mess with bsd kernel tools and linux kernel tools?? Have specific scripts for each kernel, bloody hell!

I forgot to add for the Linux kernel.UberLord wrote:iproute2 only exists in Linux, so no.sylware wrote:Come on, drop ifconfig support for good in the new openrc!
I do not agree, I think that anything which is too intimate with a kernel should have specific code and scripts (and I see BSD code as a threat so it does not help). Moreover bsd ifconfig is different from linux ifconfig (which has been meant to be replaced by iproute2 for years), that's why you have many switches in the script to handle the 2 ifconfig differently.UberLord wrote:Again no, scripts should be portable across kernels and tools where possible.What is this mess with bsd kernel tools and linux kernel tools?? Have specific scripts for each kernel, bloody hell!
I see no benefit in ignoring ifconfig for this
Across kernels I agree, if Gentoo want's pure linux init scripts it can provide them itself. But across tools is exactly the old net.lo approach. So I was wondering myself why the current script "network" doesn't come as three different scripts. As net.loopback, net.ifconfig, net.iproute2 for example. This would also allow neater configuration files I guess.UberLord wrote: Again no, scripts should be portable across kernels and tools where possible.
I see no benefit in ignoring ifconfig for this


For the wlan card.d2_racing wrote:So right now, do you have a working lan card and what about your Wifi card ?
Can you tell us more about your experiment ?
Code: Select all
wpa_supplicant_conf="/etc/wpa_supplicant/wpa_supplicant.conf"
wpa_supplicant_if="wlan0"