On 04/21/2018 12:44 AM, Andrei Borzenkov wrote:
Yet another "bug report" that just wastes scarce time of developers.
This is normal behavior, wicked waits for link on device, if you do not like it - disable it. How to do it is described in (surprise) "man ifcfg".
Andrei, If that is the normal behavior, then the devs have configured the default behavior wrong. Bringing up the "device" should happen at boot instantaneously. (and it does). Waiting for an IP on eth0 configured with "On Cable Connect" is just wrong. Why the hell is there an option for "On Cable Connect" if the software is just going to block on boot waiting for an IP that will never come -- because there is no cable plugged in -- and never will be. When there is no cable, the device should simply be brought up, and then wicked should attempt to establish a connection on wlan0, not stall on eth0 waiting for an empty RJ-45 socket to do something it may, or may not, ever do. I dual triple boot this laptop, openSuSE, Win10, and Arch. All OS'es have the cable and wireless devices enable. openSuSE is the only one with a 30 second delay in boot. That's not normal behavior. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org