sysvinit-init x86 system:
Today I did a zypper dup on an M2 system. If I boot the new 3.4 kernel, eth0
doesn't show up from 'ifconfig -a', tried after seeing "unable to
hostnames" on tty1 while finding a perfectly valid /etc/resolv.conf. Booting
either 3.4 or prior (3.3) kernel, init spends a bunch of time playing games
with fstab's cifs and nfs entries, both noauto and auto (which I have over
100 of), as if needing to stat every file, dir and subdir, tremendously
lengthening boot time, regardless whether eth0 came up or not.
tty1 does not show network as a failed service, even though there is no eth0
and thus no functional network.
Lack of network seems to cause clock error = to TZ offset, only with 3.4,
which in turn causes numerous "mount time in the future" and "you must
specify filesystem type errors" on partitions.
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org