Bug 65769 - 7.3 getting started guide has no instructions for configuring dialup
Summary: 7.3 getting started guide has no instructions for configuring dialup
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rhl-gsg
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: John Ha
QA Contact: John Ha
URL: http://www.redhat.com/docs/manuals/li...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-31 16:01 UTC by waxmop
Modified: 2014-08-04 22:13 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-05-31 16:01:23 UTC
Embargoed:


Attachments (Terms of Use)

Description waxmop 2002-05-31 16:01:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (WinNT; U)

Description of problem:
According to the site above, the getting started guide includes instructions on how to configure my dialup.  But it doesn't, and you guys removed rp3 from the 7.3 
edition. 

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


How reproducible:
Always

Steps to Reproduce:
1.Go read the above URL and notice the part that says the getting started guide will show how to configure dialup access.
2.Search through and feel sad that there is no mention in the getting started guide about dialup connections.
3.
	

Actual Results:  na

Expected Results:  I wanted to find some documentation for configuring my dialup.

Additional info:

Comment 1 John Ha 2002-05-31 16:24:58 UTC
There are instructions for online access in chapter 5 of the Red Hat Linux
Getting Started Guide entitled "Getting Online".

Red Hat Linux 7.3 uses a wizard-type program called internet-druid (a simpler
front-end to the more advanced Network Administration Tool (neat) that lets you
configure analog modem, cable and DSL modem, and other connections automatically. 

For more information about neat, refer to chapter 6 of the Red Hat Linux
Customization guide, which shows each configuration option in detail.


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