Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 280714 - After upgrade to sys-apps/openrc-0.5.0-r2, network does not start at boot
Summary: After upgrade to sys-apps/openrc-0.5.0-r2, network does not start at boot
Status: RESOLVED DUPLICATE of bug 280720
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-08 05:22 UTC by Karel De Vriendt
Modified: 2009-08-08 08:48 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karel De Vriendt 2009-08-08 05:22:07 UTC
After upgrade to sys-apps/openrc-0.5.0-r2, network does not start at boot but must be started manually

Reproducible: Always

Steps to Reproduce:
1. upgrade to openrc-0.5.0.-rc2
2. upgrade configuration files
3. reboot

Actual Results:  
Network does not start. Error message:
....
ADDCADDRI:file exists.
 cannot start netmount as net.eth1 could not start
.... 

Expected Results:  
Network should come up as net.eth1 is in default runlevel

After the upgrade, /etc/init.d/net.lo is upgraded to a very simple script that is explicitely mentioning lo. Hence the link linking net.eth1 to net.lo is not useful any more.

/etc/init.d/net.lo:
# cat /etc/init.d/net.lo
#!/sbin/runscript
# Copyright (c) 2007-2009 Roy Marples <roy@marples.name>
# All rights reserved. Released under the 2-clause BSD license.

depend() {
provide net
}

start() {
ebegin "Bringing up network interface lo"
ifconfig lo 127.0.0.1 netmask 255.0.0.0 up && \
route add -net 127.0.0.0 netmask 255.0.0.0 dev lo
eend $?
}

stop() {
ebegin "Shutting down network interface lo"
route del -net 127.0.0.0 netmask 255.0.0.0 dev lo &&
ifconfig lo down
eend $?
}
Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-08-08 08:48:20 UTC

*** This bug has been marked as a duplicate of bug 280720 ***