|
Bugzilla – Full Text Bug Listing |
| Summary: | IPv6 on/off visual select during Installation/Network card configuration | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | David Wright <david.wright> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | aj, forgotten_--EoyBps8f, marcel, mvidner, suse-beta |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
David Wright
2006-02-12 11:13:00 UTC
As the maintainer of yast2-network, my problem with this is where to put the switch, both during the installation and afterwards. Currently there is no dialog for such a global setting. Would it be possible to add it to the "Overview of the Configuration of Network Cards" dialog? You have the list of cards at the top, an information panel on the currently selected card and 3 buttons at the bottom. Making the list box slightly smaller (on my display the default (using half the screen height) would fit around 15 interface cards) and put the check box between the information panel and the buttons? Just a thought as I guess you don't want to go adding a new dialog just for this one option (although I've seen it elsewhere in YaST). That is assuming there aren't any other global network settings that would benefit from being done visually, making a new global options dialog a possibility... (I haven't investigated whether anything else would benefit, IPv6 came up in a factory discussion as it is a headache for many, especially new users. Suggestion: You could give users the hint, that if they use a router or DSL modem, then it's probably a good idea, to switch ipv6 off, as many of those home devices do not support ipv6. Reassigning to the new maintainer of yast2-network. move to later reopen to fix fixed *** Bug 230224 has been marked as a duplicate of this bug. *** |