My previous dup already installed a 37rc7 kernel, after which all the basics worked. An hour ago I did another dup, about 900 packages. After rebooting,
# ping www.google.com ping: unknown host www.google.com
/etc/resolv.conf has not been touched by the dup. There is a new file, /etc/resolv.conf.netconfig, but chkconfig --list lists no *tconfi* service, while network is turned on and *firewa* are uninstalled. rpm queries for upstart and systemd return nothing. 'ifup eth0' fixes networking. What does it take to get 'ifup eth0' to be run at boot on an ordinary no-wireless-support/no-bluetooth-support desktop system?
On 01/04/2011 11:10 AM, Felix Miata wrote:
My previous dup already installed a 37rc7 kernel, after which all the basics worked. An hour ago I did another dup, about 900 packages. After rebooting,
# ping www.google.com ping: unknown host www.google.com/etc/resolv.conf has not been touched by the dup. There is a new file, /etc/resolv.conf.netconfig, but chkconfig --list lists no *tconfi* service, while network is turned on and *firewa* are uninstalled. rpm queries for upstart and systemd return nothing. 'ifup eth0' fixes networking. What does it take to get 'ifup eth0' to be run at boot on an ordinary no-wireless-support/no-bluetooth-support desktop system?
You need /etc/sysconfig/network/ifcfg-eth0 with the lines
BOOTPROTO='dhcp' STARTMODE='ifplugd'
and with YaST having selected network control with ifup. As ifup didn't generate any warnings, you already have this part.
Larry
On 2011/01/04 11:26 (GMT-0600) Larry Finger composed:
Felix Miata wrote:
My previous dup already installed a 37rc7 kernel, after which all the basics worked. An hour ago I did another dup, about 900 packages. After rebooting,
# ping www.google.com ping: unknown host www.google.com
/etc/resolv.conf has not been touched by the dup. There is a new file, /etc/resolv.conf.netconfig, but chkconfig --list lists no *tconfi* service, while network is turned on and *firewa* are uninstalled. rpm queries for upstart and systemd return nothing. 'ifup eth0' fixes networking. What does it take to get 'ifup eth0' to be run at boot on an ordinary no-wireless-support/no-bluetooth-support desktop system?
You need /etc/sysconfig/network/ifcfg-eth0 with the lines
BOOTPROTO='dhcp'
That wouldn't have worked here. My hosts files have at least 40 more lines than the package maintainer's version.
STARTMODE='ifplugd'
On systems with only one network connection possible (as indicated in OP), why?
and with YaST having selected network control with ifup. As ifup didn't generate any warnings, you already have this part.
Too late. Apparently I forgot to lock out NetworkManager* and the latest dup added it back. Now having removed it and locking it out, all networking is apparently back to traditional. :-)
On 01/04/2011 11:43 AM, Felix Miata wrote:
On 2011/01/04 11:26 (GMT-0600) Larry Finger composed:
STARTMODE='ifplugd'
On systems with only one network connection possible (as indicated in OP), why?
Because "manual" is the default. See 'man ifcfg'. You could use "auto" as the value here, but I prefer "ifplugd" as this will not interfere later in case you happen to install a wireless card, or a second wired card.
Larry
On 2011/01/04 12:10 (GMT-0500) Felix Miata composed:
My previous dup already installed a 37rc7 kernel, after which all the basics worked. An hour ago I did another dup, about 900 packages. After rebooting,
# ping www.google.com ping: unknown host www.google.com
/etc/resolv.conf has not been touched by the dup. There is a new file, /etc/resolv.conf.netconfig, but chkconfig --list lists no *tconfi* service, while network is turned on and *firewa* are uninstalled. rpm queries for upstart and systemd return nothing. 'ifup eth0' fixes networking. What does it take to get 'ifup eth0' to be run at boot on an ordinary no-wireless-support/no-bluetooth-support desktop system?
rpcbind is not auto-starting either, so no nfs mounting on boot. :-(
-
Felix Miata -
Larry Finger