https://bugzilla.novell.com/show_bug.cgi?id=388266 User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=388266#c20 Scott Couston <alpha096@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qa@suse.de --- Comment #20 from Scott Couston <alpha096@virginbroadband.com.au> 2008-06-04 18:18:31 MDT --- I cannot understand why Yast tool cannot write the DNS Servers correctly in a static IP configuration. 1. The World does NOT run on DHCP - sorry if this is big news 2. There is no functional reason to grey out anything in Yast 3. There is no function reason why we need work arounds in any RC or Final Version Can you image how a work around created by this issue effect me with 30 + PC's I have to wait untill everyone has booted their PC and left it on - no internet access at this moment in time. Once all PC's have a OpenSuse KDE session I have to re-start the Modem and then everything works thanks to Modem smarts, however IF I need to use 1 or any more PC's - I have to start that PC with a session, ask everyone else to re-boot and then re-set the Modem. If this problem is still evident in version 11.0 - without any work around - It must be considered as a 'BLOCKER' The Yast network interface in 10.1 was so much better in layout and more useful. If it still writes the Network configuration correctly I would strongly suggest we revert back to it if we cannot get the current Interface to work. I cannot understand why a simple 'IF static IP, then auto tick 'write hosts' AND auto tick resolv.conf and then write the config statement cannot be included in Yast interface OR am I that nieve that its that simple or that easy???????? I am also alos as to why this assumed simple issue attracts #20 entries. Attn: QA Can you please manage this issue and follow through with resolution in bother online update in 10.3 and included in 11.0 Final. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.