Since neither anaconda nor system-config-kickstart can give a list of all packages that has been installed, waht is the recommended way to replicate one system for another new installation (without using hd cloning) ?
Is it possible to simply do 'rpm -qa >> my-ks.cfg' ?
When running anaconda installer, it gives system selection as well as package grouping (desktop vs server -> gnome vs kde -> gnome-pilot etc), which file provides these info?
Thanks!
--beast
wrote:
Since neither anaconda nor system-config-kickstart can give a list of all packages that has been installed, waht is the recommended way to replicate one system for another new installation (without using hd cloning) ?
Is it possible to simply do 'rpm -qa >> my-ks.cfg' ?
When running anaconda installer, it gives system selection as well as package grouping (desktop vs server -> gnome vs kde -> gnome-pilot etc), which file provides these info?
You can use kickstart to control what packages are installed.
/root/install.log has the details of what packages are installed by anaconda.
On 06/08/07 14:57 +0800, Feizhou wrote:
wrote:
Since neither anaconda nor system-config-kickstart can give a list of all packages that has been installed, waht is the recommended way to replicate one system for another new installation (without using hd cloning) ?
Is it possible to simply do 'rpm -qa >> my-ks.cfg' ?
When running anaconda installer, it gives system selection as well as package grouping (desktop vs server -> gnome vs kde -> gnome-pilot etc), which file provides these info?
You can use kickstart to control what packages are installed.
/root/install.log has the details of what packages are installed by anaconda.
Yes, it is same like running rpm-qa. After doing it myself, it can be done by listing 'rpm -qa' under %packages in ks.cfg, however there are still differences, maybe due to dependencies:
[me@localhost ~]$ wc -l old_system.pkg new_system.pkg 707 old_system.pkg 733 new_system.pkg 1440 total
--beast
beast wrote:
Since neither anaconda nor system-config-kickstart can give a list of all packages that has been installed, waht is the recommended way to replicate one system for another new installation (without using hd cloning) ?
When you install using anaconda, a kickstart file is generated automatically in /root/anaconda-ks.cfg
You can use this as a template for the next installation.
Mogens
On 06/08/07 09:22 +0200, Mogens Kjaer wrote:
beast wrote:
Since neither anaconda nor system-config-kickstart can give a list of all packages that has been installed, waht is the recommended way to replicate one system for another new installation (without using hd cloning) ?
When you install using anaconda, a kickstart file is generated automatically in /root/anaconda-ks.cfg
You can use this as a template for the next installation.
Yes, sure. But anaconda seems only generate few packages only, even though i customize lot of package.
--beast
beast wrote:
On 06/08/07 09:22 +0200, Mogens Kjaer wrote:
beast wrote:
Since neither anaconda nor system-config-kickstart can give a list of all packages that has been installed, waht is the recommended way to replicate one system for another new installation (without using hd cloning) ?
When you install using anaconda, a kickstart file is generated automatically in /root/anaconda-ks.cfg
You can use this as a template for the next installation.
Yes, sure. But anaconda seems only generate few packages only, even though i customize lot of package.
That is because anaconda does not list every package ... only the top of the tree for each. That is, all the packages required to get the install. If it is installing yum and if sqlite is a dependency of yum, it lists on only yum.
Also ... for hidden groups that are installed, it does not not list those ... like @core ... but it installs them.
I think you CAN list all the packages if you want (by doing rpm -qa) ... but make sure to only list packages that are on the DVD (that is the ones only from the base repo ... or /CentOS/ on the DVD).
Thanks, Johnny Hughes