David C. Rankin wrote:
I'm not sure what to make of the outcome. I guess the problem is fixed for 11.1. The plan for 11.0 is a little unclear. Anyway, the bug was closed with the following discussion:
------- Comment #3 From Alexander Orlovskyy 2008-10-22 00:48:42 MDT [reply] -------
Reassign to yast2-maintainers.
------- Comment #4 From Michal Zugec 2008-10-22 08:02:02 MDT [reply] -------
This problem is fixed in openSUSE11.1 (from Beta3 above)
I guess that means there will be a patch some day for 11.0. However, until then, I would avoid any remote network card reconfiguration via YAST.
As a workaround in the mean time. Create a small script named 'kicketh0' with something like: #!/bin/bash sleep 300 /sbin/ifup eth0 exit 0 (make the file executable) Start the script (as root) with './kicketh0 &' Then start yast2 (ncurses) from the command line, make your changes without delay and hit "finish". If yast fails to restart your network card, wait the remainder of the 300 seconds and try again. If yast works right, just 'killall kicketh0 && killall sleep' and your done. I tried yast again tonight with the script in the background. Murphy's law is alive and well -- yast worked like it was supposed to. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org