Why does the anaconda-ks.cfg file *not* reflect the packages I chose during my manual install?

[Sankarshan Mukhopadhyay]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gregory Gerard wrote:

> 1. It's incredibly annoying I cannot right-click on a top-level category
> and say "Install all optional packages" but must through each
> sub-category and tediously do it.

Is this somewhat related to the fact that you are missing an "Install
Everything" kind of installation option that users were used to ?

> 2. I was hoping the ks file generated would have a good flight recording
> I could then replay but it only reflects the default packages, not the
> "all optional packages" I'd selected during the manual install.

Isn't that how it has been all along ?

> 3. While CentOS 5 configurator doesn't crash like the FC6 did (wow, that
> sucked a lot of time), it doesn't allow me to select optional packages
> at all making it pretty much a starting point for a boilerplate KS file
> that I must then extensively hand edit.

I kind of lost you here, do you mean to say system-config-kickstart does
not seem to work as expected ?

> 4. In my naive attempt at getting this behavior to work, I did a "rpm
> -qa >> mymachine.cfg" in order to have anaconda install the RPMs that
> were installed when I did the original manual install (sorry, English
> grammar is elusive right now). This just resulted in the install just
> sitting there pegging the CPU with "Completed Completed" being the last
> message on the console.

yum list  (with the grep for installed) on the original machine and then
passing that output through a yum install ? :)

- --

You see things; and you say 'Why?';
But I dream things that never were;
and I say 'Why not?' - George Bernard Shaw
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGxC0eXQZpNTcrCzMRAh2GAJ9fwi2wW9G+SvAoqUEnVFYp5u9qLACeJAg+
PaWm7Z0wYC5fHEKzBqxhvWE=
=itGt
-----END PGP SIGNATURE-----