Bug 811019 - It is not clear where the docs are to configure wireless connections
Summary: It is not clear where the docs are to configure wireless connections
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: wireless-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Forlot Romain
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-09 21:17 UTC by Jim Wright
Modified: 2019-11-07 15:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-07 15:29:50 UTC


Attachments (Terms of Use)

Description Jim Wright 2012-04-09 21:17:38 UTC
Description of problem:

Cannot find documentation to help me connect F16 to Wifi.

Version-Release number of selected component (if applicable):

F16

How reproducible:

Go to http://fedoraproject.org/ and click "Need Help? Get it here" then follows steps.

Steps to Reproduce:
1. On http://fedoraproject.org/en/get-help under "Top 5 questions from the FAQ" click #2 i.e. "How do I configure network connections?"
2. Only the last line of the FAQ entry looks like it might help: "Also refer to the Fedora Wireless Guide at docs.fedoraproject.org to learn more about wireless, and its implementation in Fedora. "
  
Actual results:

After some searching I find that the "Wireless Guide" only exists for F13 and possibly earlier. I don't know why this is. Should I expect it to help me or is it obsolete?

Expected results:

Expect to find a "Wireless Guide" that is clearly applicable to F16 because I have been referred to it.

Additional info:

Despite my 20+ years of linux experience I still haven't got Fedora 16 working and am stuck with Fedora 14. The irony is that I spend much of my time at work helping people administer Red Hat. Frankly I am puzzled. I feel like I am walking through treacle. Maybe I am too old? Do most users have weeks of free time to devote to setting up a Fedora system?

Comment 1 Forlot Romain 2012-05-06 00:37:33 UTC
Hi,

Indeed, Wireless guide is quite old. It will be refreshed as soon as possible.

In the meanwhile, can you tell me if User Guide chapter "Connecting to the internet" in Fedora Documentation Draft section of http://docs.fedoraproject.org/ have needed informations?

If not, what kind of informations miss you ?

Thanks.

Comment 2 Jim Wright 2012-05-07 12:42:14 UTC
I think the info headed "Why is not the wireless section shown?" is closest to what I needed.

BTW It should really be "Why is the wireless section not shown?" for the benefit of native English speakers.

The problem I had was more fundamental - I did not let the installer overwrite my existing boot setup because it is dual boot. I somehow ended up with no /lib/modules/ subdirectory to match the kernel I was booting but it did not fail convincingly enough for me to check for fundamental issues. I assumed by personal account config was somehow corrupt.

So if I had found the above docs I might have ended up on http://www.fedoraforum.org/, which would be a reasonable approach.

If "Wireless Guide" is not obsolete then that is perhaps all. But how does a user know this i.e. that it is not listed under F16 docs because it has been static since F13? Maybe there should be some placeholder in the lists for F14-16.

Comment 3 Stephen Wadeley 2012-06-25 16:31:20 UTC
Hello Jim

I am currently maintaining the Wireless Guide.

A new version of the Wireless Guide, as well as the System Administrator's Guide, has been added to  http://docs.fedoraproject.org.

I have updated this Wiki page (https://fedoraproject.org/wiki/Tools/NetworkManager) 

and also:

http://fedoraproject.org/wiki/FAQ#How_do_I_configure_network_connections.3F_How_does_Fedora_support_wireless_connections.3F

to direct users to the System Administrator's Guide at http://docs.fedoraproject.org.

Thank you

Comment 4 Petr Bokoc 2019-11-07 15:29:50 UTC
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.


Note You need to log in before you can comment on or make changes to this bug.