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 1252491 - bootloader --disable and %packages --nocore options are not documented
Summary: bootloader --disable and %packages --nocore options are not documented
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Installation_Guide
Version: 6.8
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Clayton Spicer
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-11 14:28 UTC by Martin Kolman
Modified: 2016-08-26 00:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-26 00:40:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Kolman 2015-08-11 14:28:52 UTC
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-packageselection.html

Section Number and Name: 
bootloader (required) 
32.5. Package Selection

Describe the issue:
The bootloader --disable and %packages --nocore are not documented in the Installation guide.

Suggestions for improvement: 
The "bootloader --disable" option is a stronger version of the existing "bootloader --location=none", while "bootloader --location=none" disables bootloader installation, "bootloader --disable" disables bootloader installation but also disables installation of the bootloader package (thus saving space).

This also means that if "bootloader --disable" is used using also --location=none is redundant.


Using %packages --nocore disables installation of the core package group which is otherwise always installed by default. Disabling core package group should be only used for creating lightweight containers, trying to install a normal system with --nocore will result in a broken installation.

It should be also noted that:


%packages
-@Core
%end

is not equivalent to

%packages --nocore
%end

Using the - minus syntax for the @Core package group does not work and should not be used. The *only* correct way for excluding the core package group is the --nocore option.


Additional information: 
Strong emphasis should be added to both of these options that they are meant exclusively for container creation and that using them during normal installation *will* result in a broken system.


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