Andrei Borzenkov composed on 2015-09-25 10:31 (UTC+0300):
Felix Miata wrote:
I don't want my ethernet "managed". I want life like it was with ifup, config dictates onboot, and onboot it starts, regardless whether a cable connection actually exists, so that when a connection exists, there's no need for any response from a manager, or anything else.
Last night I "installed" Leap for first time ever, same method as nearly always, HTTP started via Grub stanza including network configuration on HD0. Installation went without any significant hitches, and so did first several boots. Then I got a whole bunch of boots without eth0 configured, couldn't get systemctl or anything else to find me any understandable clues, and eventually found and looked at and was very disappointed by https://en.opensuse.org/Portal:Wicked/Troubleshooting . Man pages for wicked and wicked-config are too big, complicated and free of examples to figure out what to do to make eth0 config start unconditionally, and persist, or why this isn't default on an HTTP installation with one only NIC and no wireless hardware, or even if it's any more possible since Wicked arrival.
Is it even possible any more to have eth0 configured on boot unconditionally? If so, how?
Does https://bugzilla.opensuse.org/show_bug.cgi?id=911562 help?
It does help, incompletely. It provides a way to ensure the interface gets an address assigned regardless of link state (LINK_REQUIRED='no'). If it provides an answer why a simple fixed IP interface/wirelessless configuration needs all of wicked, wickedd and wickedd-nanny enabled to get up, I missed it. -- "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@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org