Bug 50738
Summary: | Checking the "Active" box in neat apparently does nothing - until the program is closed | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Panic <mdrew> |
Component: | redhat-config-network | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | pknirsch, teg |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-06 14:21:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Panic
2001-08-02 18:52:59 UTC
We need "apply" functionality... This defect is considered SHOULD-FIX for Fairfax. The problem is that here 'Active' and 'Inactive' are used in two contexts. There is a very clear definition of active and inactive devices for real system devices and one for neat devices. In neat you can have multiple devices configured to use eth0. Depending on where you are (e.g. if you have a laptop) you can then activate one or the other. These neat activations are NOT done immediately on the system level for several reasons: 1) You often don't want this change to happend immediately. Just think of remote configuration over ppp and changeing the configuration of that device. 2) It should be up to the user when to restart resp stop and start the network. If neat always does it we limit choice, which is bad. 3) By having an additional Apply button (which has just been added as it was really missing) we provide the required logic to let the user update the real configuration when he/she wants to. 4) Neat's intention and logic is to configure the devices, not to automatically and magically fiddle with the current network state of the machine. That way we keep these 2 different aspects of networking separate (which is always a good idea in software and interface design). So it boils down to the simple fact that the Active checkboxes are doing exactly what they should do, but that we had ommited to provide an Apply functionality to neat (which as previously mentioned has been added now). I hope this clarifies the idea and necessity for the active checkboxes and their behaviour. Read ya, Phil |