https://bugzilla.novell.com/show_bug.cgi?id=259304 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #5 from locilka@novell.com 2007-04-04 02:27 MST ------- I have here a table of possible states in which a firewall can operate. Some of them could be merged into one by using variables. Anyway, just to present the pieces of information with which the YaST firewall needs to work: - There is the initial state of a firewall: enabled/disabled* - And another initial state: running/not running - User can enable/disable the firewall in UI* - User can start/stop the firewall in UI - Firewall can be enabled/disabled at the end* - Firewall can be running/stopped at the end * enabled/disabled means that it starts automatically at the boot process, disabled means "Manually" in UI. Without user's help (question), we sometimes just can't know what to do. User might want to disable the firewall (or leave it disabled) while he/she wants to leave it running. To be honest, this has been discussed many times before and despite the fact that firewall isn't the only one service that has exactly the current behavior, it is the only reported case in bugzilla. Never mind, ... so how to solve that? Radio buttons: (*) When booting ( ) Manually don't fit to a situation when a common user wants to simply disable the firewall. However, if I only change them to: (*) Enable firewall ( ) Disable firewall it wouldn't work for experts with their manual setup. Let's forget now, that manual setup (manual start) doesn't make much sense in a desktop or even server environment. Maybe if experts call `rcSuSEfirewall2 start` from some (another) starting script but what's the point? That's why I've decided to rename these radio buttons to: (*) Enable firewall automatic starting ( ) Disable firewall automatic starting (or something similar using a proper English ;)) Additionally, a new functionality has been added: 1.) Unless the enable/disable is changed by user in that dialog, no status change is proposed for the currently running/stopped service. 2.) If user selects to "Enable firewall...", it's also proposed to be started after the configuration is written. 3.) If user selects to "Disable firewall...", user is asked whether he/she wants to stop the firewall after the configuration is written (default "yes, stop it"). 4.) Text about stopping or starting the firewall service uses a bold text in a summary. This new solution cannot be added into SLES10 SP1. The right product is openSUSE 10.3 where it should prove its correctness or escalate into discussion about another, better, solution that would appear in SLES11 (after oS 10.3). This is a part of the yast2-firewall changes file: --- cut --- - A brand new and better revolutionary solution has been worked out for a firewall service starting/stopping and enabling/disabling in order to maximize user understanding and minimize errors (#259304). - yast2-firewall-2.15.5 --- cut --- Closing as FIXED -- 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, or are watching someone who is.