Andreas Simon wrote: > Also I don't think it's a good thing to ask the user a lot of questions > during > installation. I am a big fan of reducing the number of questions during > installation as much as possible.
Yes, the installation should be as simple as possible. But I meant a tool as in "when you want to slim down your Suse system, run this program". > It's probably a very common task to disable all unneeded > daemons after installation. Here a small tool which guides the user through > the task could be very handy. This is exactly what I meant. Something like the good old "hardensuse" script, but not (only) for security but for performance. You could automate part of it like gotisdn=`lspci | grep -i ISDN` if [ -z "$gotisdn" ]; then echo "You do not seem to have ISDN hardware. Do you want to...." .... fi This way you could remove another unneeded SUID binary. But how do you find out if the user has used klipper or kinternet? If you want to automatically detect if these have been used you'd need to integrate this directly into the application itself. Maybe for kinternet you could work with access times/md5sums of configuration files (never used it). > Another issue regarding daemons. I think it would be a good policy that all > daemons which get installed after the initial installation of the system > should be disabled by default. Always. I agree on this one. I really wonder why it is that the sshd is installed and started by default when the firewall is also started by default, thus making sshd useless. Cheers nordi --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
