Stephen J. Smoogen wrote:
Since Nichael mentioned language, I suggest "stupid" is coloured, more likely to cause offence than merely opining that "These are not necessary:"On 10/5/05, Michael Stiller <ms 2scale net> wrote:Thanks to all for the suggestions so far. I guess i will go with the network install option even due to local issues i will need at least 3 installation servers now instead of one CD image. Which i actually need too cause not all machines can do a PXE boot. Special thanks to Joshua for attaching his tiny.cfg kickstart config file. I already had the installation trimmed to 218 packages utilizing attached kickstart config file. Sorry Ed for using "unpolite" words but if you want to install a really minimal *server* e.g. for web servicing you actually don't need packages like (stupid highlights include:)
pcmcia-cs the bluez stuff irda utilities isdn4k utilities cups an lha compressor (!), 4 differend shells (ash, bash, tcsh, pdksh) dialup networking stuff like ppp, mgetty, minicom, lszrz, set- and statserial pax, nano, wireless-tools
pax is a handy backup tool: some might reasonably prefer it to tar and cpio.nono is a text editor, preferred by some. You need a text editor, and if the one you want isn't there you could be in big trouble when you need one.
OTOH only one of my several headless boxes needs mgetty, and I've never discovered a use for setserial.About the only ones I can see that need to be there are: ash I think for mkinit bash for shell tcsh for certain BSD apps. setserial/statserial and mgetty are needed on a headless server.
In the middle road is pinfo for info pages, psacct, quota, and pam_passwdqc which I use for security. The rest I normally remove from a server because they are security problems.
-- Cheers John -- spambait 1aaaaaaa computerdatasafe com au Z1aaaaaaa computerdatasafe com au Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list