"core" installs of 5.2 missing crucial packages like yum, selinux-policy-targeted, vim-minimal, etc.
 

Filipe Brandenburger wrote:

Hi,

On Tue, Oct 28, 2008 at 15:34, Johnny Tan <linuxweb@gmail.com> wrote:

I had a 5.0 kickstart server which did "core" installs of CentOS (i.e.:
"%packages --nobase").


IMHO, that's a very bad idea. Unless your diskspace is very very tight
(in which case you should probably look into DSL or another
distribution made for that purpose), why would you want to install
CentOS without the "base" packages?

All machines that I've seen that have been installed with --nobase are
crippled. Some programs and mainly scripts just don't work, because
they need to run some utility that is not installed.

Consider removing the --nobase and, if there are packages you would
like to remove from base and you're positive that it's safe to do it,
use -packagename.


I appreciate the guidance, but all our production machines
run nobase, and we are fine.


I'm just looking for some ideas as to why 5.2 is not
installing certain "core" files. It could very well be a
misconfiguration on our part, but I just wanted to see if
others have encountered this.


Thanks,
johnn
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

"core" installs of 5.2 missing crucial packages like yum, selinux-policy-targeted, vim-minimal, etc.
 

Kai Schaetzl wrote:

Johnny Tan wrote on Tue, 28 Oct 2008 15:34:29 -0400:

I had a 5.0 kickstart server which did "core" installs of
CentOS (i.e.: "%packages --nobase").


And you have a @core in there as well?


No, but adding that seems to work. In our 5.0 kickstart
setup, we didn't need to put that. Maybe this is one of the
"kickstart changes" mentioned in 5.2 Release Notes.


Thanks,
johnn
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos