Bug 247550 - anaconda doesn't create a useful ks.cfg
Summary: anaconda doesn't create a useful ks.cfg
Status: CLOSED DUPLICATE of bug 227383
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda   
(Show other bugs)
Version: 5.0
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: Anaconda Maintenance Team
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-09 21:54 UTC by JB Segal
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-10 16:41:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description JB Segal 2007-07-09 21:54:18 UTC
Description of problem:
auto-generated ks.cfg contains useless package list. I need a real one.

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

How reproducible:

Steps to Reproduce:
1. Install a new RHEL5 system, modifying the list of installed packages by hand.
2. Look at the auto-generated /root/anaconda-ks.cfg, to use in the next install.
Actual results:

Expected results:
Something more like what I got with RHEL4:
%packages --resolvedeps
@ editors
@ emacs
@ system-tools
@ dialup
@ ftp-server
@ emacs
@ server-cfg
@ development-tools
 . . .

Additional info:
This isn't at all useful for actually reproducing a build using kickstart.

Failing a fix, a good answer for how to correctly generate that section of the
ks.cfg after a system's installed would be really useful.

Comment 1 Chris Lumens 2007-07-10 16:41:50 UTC

*** This bug has been marked as a duplicate of 227383 ***

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