Bug 191626 - Google Linux Search Site link broken
Google Linux Search Site link broken
Product: Fedora Documentation
Classification: Fedora
Component: install-guide (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Paul W. Frields
Paul W. Frields
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2006-05-13 19:40 EDT by James Stoker
Modified: 2007-09-12 22:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-09-12 22:10:52 EDT
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 James Stoker 2006-05-13 19:40:53 EDT
Description of problem:

Section 14.3 of the install guide refers to the Google linux search site at


This is currently a broken link.  The link


does still seem to work at this time.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Paul W. Frields 2006-05-13 19:51:03 EDT
This is probably a problem at your local site.  Check and/or clear your cache,
and try again.  If the problem persists, check any proxies you may be using. 
The Google site works fine from where I sit.
Comment 2 James Stoker 2006-05-13 20:04:45 EDT
This was not a local problem, as it generated a full broken link page from 
Google with the correct URL.

Rather, I think it was a transient problem at Google.  It now works for me -- 
without messing with the cache.  Perhaps Google was doing some maintenance?
Comment 3 Paul W. Frields 2006-09-25 12:52:57 EDT
Reopening, this is just a mistake in the <ulink> in nextsteps.xml.  Fixed in FC6
(devel) IG, but should probably be fixed in earlier versions.
Comment 4 Paul W. Frields 2007-09-12 22:10:52 EDT
Fixed for FC4 and FC5 editions (finally), no excuse for unreasonable delay.

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