Quoting Jim Popovitch <jimpop@xxxxxxxxx>: > > How do you define 'core/server packages'? > > 1) any mandatory (based on rpm dependencies) package > (i.e. krb5-libs, inetd, vi) > 2) any package that opens an external port <= 1024 by default > (i.e. apache, named/bind9, openssh, etc) > 3) any package that potentially listens on an external port <= 1024 > (telnet-server, wsftp, etc) > 4) any package that is used for non-gui server administration > (i.e. nslookup, dig, tcpdump, etc). > 5) any package that is a dependency of any of the above > (i.e. openssl, etc) > > -Jim P. 1 and 5 seem to be about the same thing really. 2 and 3 are pretty close, since telnet/ftp/etc traditionally use ports < 1024 and are server apps. But generally I could accept all the above except for number 4. Number 4 is the one open to endless debate. And many people like gui server apps (see the whole redhat-config-* line of gui programs, the industry wide move to web based configuration, etc). Some will say that some of the apps you listed are not important, depreciated, or otherwise not of value to them. Others will insist something is of great use for server admin, even though no one else sees their point. Open to lots of debate here. > -- > > fedora-legacy-list@xxxxxxxxxx > http://www.redhat.com/mailman/listinfo/fedora-legacy-list > -- Eric Rostetter -- fedora-legacy-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-legacy-list
