drizzt wrote:@slack---line:
Have you tried to change the "strict" variable I mentioned some posts ago ? This one helped me with the similar problem of net.eth0 / net.eth1.
drizzt wrote:@slack---line:
Have you tried to change the "strict" variable I mentioned some posts ago ? This one helped me with the similar problem of net.eth0 / net.eth1.
Code: Select all
~ $ sudo /etc/init.d/net.wlan0 restart
* Caching service dependencies ...
err, no interface specified
err, no interface specified
err, no interface specified [ ok ]
err, no interface specified
err, no interface specified
* Bringing down interface wlan0
* Stopping dhcpcd on wlan0 ... [ ok ]
* Stopping wpa_cli on wlan0 ... [ ok ]
* Stopping wpa_supplicant on wlan0 ... [ ok ]
* Running postdown ...
err, no interface specified
* Bringing up interface wlan0
* Running preup ...
* Starting wpa_supplicant on wlan0 ...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported [ ok ]
* Starting wpa_cli on wlan0 ... [ ok ]
* Backgrounding ... ...Code: Select all
config_eth0="dhcp"
dhcpcd_eth0="-t 5" #Timeout after 10 seconds
dhcp_eth0="release nontp nonis" #Only get an adress
config_wlan0="dhcp"
dhcpcd_wlan0="-t 5"
dhcp_wlan0="release nontp nonis"
# Prefer wpa_supplicant over wireless-tools
modules="wpa_supplicant" "dhcpcd"
wpa_supplicant_wlan0="-Dwext -B -qq -c/etc/wpa_supplicant/wpa_supplicant.conf"
#preup() and postdown() are needed to un-/load the wlan module!
#By simply restarting the service without reloading the module
#we won't receive an IP anymore.
preup() {
if [ $IFACE == "wlan0" ]; then
modprobe iwl4965 && sleep 0.5 #wait 1 second before continuing, else we fail!
fi
}
postdown() {
if [ $IFACE == "wlan0" ]; then
modprobe -r iwl4965
fi
}
# rc-status
Runlevel: default
...
net.MainLAN [ inactive ]
net.dummy0 [ started ]
named [ scheduled ]
...
netmount [ scheduled ]
...
sshd [ scheduled ]
apache2 [ scheduled ]
slapd [ scheduled ]
samba [ scheduled ]
...
* Bringing down interface dummy0
* Stopping netplug on dummy0 ... [ ok ]
* Bringing up interface dummy0
* Starting netplug on dummy0 ... [ ok ]
* Backgrounding ...
* WARNING: net.dummy0 not under our control, aborting
Code: Select all
# /etc/init.d/apache2 restart
* WARNING: apache2 is scheduled to start when net.MainLAN has startedCode: Select all
rc_net_MainLAN_provide="!net"Code: Select all
# Do we allow any started service in the runlevel to satisfy the depedency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
rc_depend_strict="NO"
Code: Select all
modules=( "iproute2" )
modules=( "dhcpcd" )
config_eth0=( "dhcp" )
fallback_eth0=( "192.168.1.66/24" )
dhcpcd_eth0=( "-t 25" )
Code: Select all
config_eth0= "dhcp"
fallback_eth0= "192.168.1.66/24"

Code: Select all
modules="iproute2"
config_eth0="dhcp 192.168.99.1/24"
dhcp_eth0="nontp"Ahh. I was looking at /etc/conf.d/net.example, which is useless. Thanks! Now my config works:golding wrote:An example file can be found at /usr/share/doc/openrc/net.example
Code: Select all
config_eth0="dhcp"
fallback_eth0="192.168.10.100/24"
dhcpcd_eth0="-t 25"
Check /etc/conf.d/fsck for an example of this.fintan wrote:I've just installed openrc. I had some issues but most of them are sorted now. My home partition is 200G+. So it takes some time to check. I was wondering is it possible to check it in the background since it's not needed until I login? Thanks

banned from #gentoo since sept 2017Neddyseagoon wrote:The problem with leaving is that you can only do it once and it reduces your influence.

The txqueuelen bug was opened on 4/16:UberLord wrote:You should open bugs for those as I can't find any existing bugs.
...You need to get dmcrypt to run after root. Try putting this in /etc/conf.d/dmcrypt
rc_need="root"
rc_need="root" and rc_dmcrypt_need="root" both result in dmcrypt failing to start since "fsck would fail". I also tried removing fsck, rc_dmcrypt_after="root", etc..., but to no avail. In addition the depends() functions in root, fsck and dmcrypt seem to force the requirements I need, but still doesn't work.
I have a gpg key on usb to decrypt /home, but the /lib/rcscripts/addons/dm-crypt-start.sh requires / to be rw as shown below:
Code: Select all
local mntrem=/mnt/remdev.$$ if [ ! -d "${mntrem}" ] ; then if ! mkdir -p "${mntrem}" ; then ewarn "${source} will not be decrypted ..." einfo "Reason: Unable to create temporary mount point '${mntrem}'" return fi fi
Unfortunately it still seems like fsck, root and dmcrypt create a circular dependency for startup (despite trying to override) which dmcrypt always loses.
Any other ideas?