Ned Slider wrote: 
Hugo van der Kooij wrote:
  
But iptables, ntpd, sshd are however things I considere part of the core
installation.
        
Let us just not forget ip6tables ;-)

    
How about you work out a list, we can then all argue over it, whatever
packages get onto the list then can pose a potential manifest to work
with ?
      
Well. Actually. I can not think of anything else I would need there. I
would just take it from there and use yum to install those bits I might
need on that server.

How is that for a short list?

    

Plus stuff like ftp(??), wget and screen if there's room.

This is the %packages section from a kickstart file I use for booting off of only the first CD, it's a pretty good minimal package set, as it still has ftp, telnet, and wget, you could probably add a few more (ie, take them out of the list below), and still install all the packages off of one cd, I'm just too lazy to figure out which packages are on disc1 and leave them on.

%packages
@core
@base
device-mapper-multipath
-pam_pkcs11
-krb5-workstation
-ksh
-mcelog
-crash
-aspell-en
-coolkey
-aspell
-dump
-dosfstools
-libaio
-nano
-finger
-irqbalance
-conman
-pcmciautils
-pam_ccreds
-sos
-mtools
-dos2unix
-gpm
-cpuspeed
-iptstate
-NetworkManager
-pinfo
-ipsec-tools
-sysreport
-mtr
-mkbootdisk
-pam_krb5
-irda-utils
-pam_passwdqc
-amtu
-ypbind
-jwhois
-nc
-smartmontools
-ccid
-tcsh
-bluez-utils
-logwatch
-gnupg
-talk


_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
Matt