Bug 326969 - wifi support early network config is not good enough
Summary: wifi support early network config is not good enough
Status: RESOLVED DUPLICATE of bug 293609
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 1
Hardware: 64bit Linux
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-20 21:52 UTC by Fred van Zwieten
Modified: 2007-09-26 12:34 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred van Zwieten 2007-09-20 21:52:47 UTC
Very early in the installation process we get the opportunity to configure the network stack for configuring online repo's. We have the ability to choose a wireless adapter, but it won't ask for all wireless info needed. No ESSID asked. No key asked, etc. There are 3 possibilities here:

1. don't support wifi at all and remove the wireless adapters from the list
2. keep the current support, but a info in the help area that only open access points are supported
3. realise a full wireless config dialog, or use the one allready in Yast.

The current situation is very confusing.
Comment 1 Stephan Kulow 2007-09-21 05:02:08 UTC
the option 1 was actually what was supposed to happen, but then you remove support for open access points and other users are confused. We documented it in the manual though
Comment 2 Fred van Zwieten 2007-09-21 06:09:25 UTC
In the manual is good. In the help area on the left side is better. An extra "are you sure" dialog when a wireless adapter is selected is great. I didn't check the help area so i'm not sure it's there.
Comment 3 Matej Horvath 2007-09-26 12:34:10 UTC
I'm sorry, but I have to close this bug as duplicate of Bug 293609. If you have any suggestions please write them there.

*** This bug has been marked as a duplicate of bug 293609 ***