Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 81264 - broken link in Installation Guide
broken link in Installation Guide
Product: Red Hat Database
Classification: Red Hat
Component: documentation (Show other bugs)
noarch Linux
low Severity low
: ---
: ---
Assigned To: Patrick Macdonald
Patrick Macdonald
Depends On:
  Show dependency treegraph
Reported: 2003-01-07 06:29 EST by Fred New
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-07 23:13:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fred New 2003-01-07 06:29:34 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
The first "Prev" link in
/usr/share/doc/rhdb-docs-2.1/install/html/s1-already-using.html points to a
document that doesn't exist.

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

How reproducible:

Steps to Reproduce:
1.  Open /usr/share/doc/rhdb-docs-2.1/install/html/s1-already-using.html using
Mozilla and try clicking on the first "Prev" link.

Actual Results:  Object not found!

Expected Results:  The page for Step 4 should appear.

Additional info:

This problem appears in the rhdb-docs package and on the www.redhat.com
documentation Web pages.
Comment 1 Patrick Macdonald 2003-01-07 11:46:39 EST

Thanks for the information.  It seems as though someone deleted a character
on the first prev link ref.  We'll send off a note to the web guys to fix
it on www.redhat.com. We'll make the change locally in the distro html.

Comment 2 Patrick Macdonald 2003-01-07 23:13:46 EST
Ok... the prev link on the page is now correct.  Please verify and
close this bug.

Comment 3 Patrick Macdonald 2003-01-07 23:18:21 EST
Hmm, sorry Fred.  It seems to have closed the bug when I marked it
fixed in current release.  Anyway, please verify and if you don't agree,
reopen the bug.


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