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 107356 - Kernel compilation instructions in the wrong order
Kernel compilation instructions in the wrong order
Product: Red Hat Linux
Classification: Retired
Component: rhl-cg (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: John Ha
John Ha
Depends On:
  Show dependency treegraph
Reported: 2003-10-17 07:21 EDT by David Tonhofer
Modified: 2014-08-04 18:14 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-20 14:05:49 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 David Tonhofer 2003-10-17 07:21:05 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2)
Gecko/20030208 Netscape/7.02

Description of problem:
The instructions for building a custom Kernel seem to be 
a bit wrong (this also applies to the printed documentation,

Customization guide RH9.0, Appendix A, Section 2, point 5 and 6
are more or less inverted.


The 'make clean' should be run before 'make dep', *not after*
'make dep' because otherwise there will be unrecoverable errors
during compilation, e.g. the .h file for the names of devices will no
longer exist after a 'make clean'.
Comment 1 Tammy Fox 2004-02-27 01:26:43 EST
This seems inconsistent with the docs that come with the kernel.

Reassigning to new owner to confirm.
Comment 2 John Ha 2005-06-20 14:05:49 EDT
Thank you for your report. 

Unfortunately, the Red Hat Linux 9 documentation has reached end-of-life and
will no longer be updated.

Additionally, instructions on building custom kernels have been removed from Red
Hat Enterprise Linux documentation to remain consistent with our Global Support
Services policies regarding kernel support. We apologize for the inconvenience.

Thanks again for the report!

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