Bug 183445 - enhance kickstart selection dialog to match anaconda
Summary: enhance kickstart selection dialog to match anaconda
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-kickstart
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
Whiteboard: bzcl34nup
: 445473 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-01 04:01 UTC by Tom Marchant
Modified: 2008-07-31 21:31 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2008-05-07 00:24:12 UTC

Attachments (Terms of Use)

Description Tom Marchant 2006-03-01 04:01:21 UTC
Description of problem:
system-config-kickstart does not match the Anaconda installation dialog.  In
particular, in the Firewall Configuration, there should be an option to select
Samba as a trusted service.  There also does not seem to be any way to specify
LVM partitions.  Package selection does not offer the ability to select optional
packages within a group. 

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info: There may be additional discrepencies.  I did not perform
thorough matching of kickstart against Anaconda.

Comment 1 Chris Lumens 2006-03-01 15:19:15 UTC
Yes, this is something to look at for post-fc5.  All the config tools need to
provide some sort of screen that s-c-kickstart can wrap for use, similar to how
firstboot works.  The LVM part in particular is a known and fairly irritating

Comment 2 Chris Lumens 2007-02-13 18:52:01 UTC
Package selection and firewall configuration now more closely match anaconda. 
Firewall config is a little bit differently organized, but the controls
themselves are the same as you'd see in firstboot.  Network and partitioning are
still the big standout differences but they really require serious work in
anaconda before s-c-kickstart can use those screens.

Comment 3 Bug Zapper 2008-04-03 17:02:58 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 4 Bug Zapper 2008-05-07 00:24:10 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

Comment 5 Chris Lumens 2008-07-31 21:31:13 UTC
*** Bug 445473 has been marked as a duplicate of this bug. ***

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