Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 679440

Summary: Package Selection docs for @everything is incorrect
Product: Red Hat Enterprise Linux 6 Reporter: Martin Poole <mpoole>
Component: doc-Installation_GuideAssignee: Jack Reed <jreed>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: high Docs Contact:
Priority: high    
Version: 6.0CC: jreed, pbokoc, wburrows
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-09 01:13:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Poole 2011-02-22 15:31:40 UTC
Description of problem:

In the Pacakge Selection section of the 6.0 install guide (32.5) it describes the unsupported @everything option.

Neither the ISOs nor satellite channels have @everything.

Comment 1 William Burrows 2011-05-04 21:10:40 UTC
There is much more wrong with section 32.5 of the installation doc.  Here is a list:

1) As stated above, there is no '@everything' group, so instead of stating:

  Warning — @Everything is not supported

maybe it should read:

  Warning — @Everything is no longer included

2) The doc also covers using a (variant) after the @Conflict when using the @everything.  

"Packages known to cause such problems are assigned to the @Conflicts (variant) group, where variant is Server or Client. If you specify @Everything in a
kickstart file, be sure to exclude @Conflicts (variant) or the installation will fail:

@Everything (Server)
-@Conflicts"

The example given though shows the variant next to @everything instead of @conflict.  Very confusing.

3) Is the '*' also not supported?  Unlike the @everything group, the glob still pulls everything down.  The glob is also not included in the BOLD font at the top as not being supported, but is mentioned below that:

"You can use a kickstart file to install every available package by specifying @Everything or simply * in the %packages section. Red Hat does not support this type of installation."

I realize this is just semantics, but is the '*' supported or not by Red Hat? When I have asked people involved in the anaconda engineering group this question, I was informed "@Everything" is deprecated in favor of the more
generic glob mechanism, "*". "  Can we please update the doc to give the user a straightforward answer as to what is and what is not supported.