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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 15, 2007 at 06:59:20PM -0700, Gregory Gerard wrote:

> 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.

I think kickstart expect package names, not n-v-r lines, so maybe you
should try to put the output of "rpm -qa --qf '%{name}\n'" in the ks file.

-- 
--    Jos Vos <jos@xxxxxx>
--    X/OS Experts in Open Systems BV   |   Phone: +31 20 6938364
--    Amsterdam, The Netherlands        |     Fax: +31 20 6948204

_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list

[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux