On Sat, 2004-09-11 at 17:38 -0600, Stephen J Smoogen wrote:
Sean Middleditch wrote:
On Sun, 2004-09-12 at 00:18 +0100, Paul Trippett wrote:
Why not take a BSD approach and give them the option when installing the package, say for example...
# rpm -i vsftp....rpm
Would you like to enable Anonymous logins? (y/n) [N] Would you like to enable Local user Logins? (y/n) [N]
Because RPMs are absolutely never ever supposed to ask questions.
- What if the RPM is being installed non-interactively? - What if the RPM is being installed with a GUI tool? - What if the user doesn't understand English?
And then you get into the general usability problems - are the question phrased properly? Is "Y/N" an appropriate prompt? etc.
Each rpm could then drop a scriptlet into a directory that gui would then be able to run to set things up for it.
/etc/system-setup/ vsftpd.py httpd.py samba.py kill_my_harddrive.py
And then the system-setup program would display the questions, get the answers... and possibly be able to bring the system into at least a bare-bones configuration.
Reset to original configuration [Yes] [No] [Help]
Again, what if the configuration data isn't translated into the user's
language? They end up getting some vital system configuration question
they can't possibly answer? Why the heck does this *need* to be done at
install time? If you are going to make a configuration tool, let the
user run it them self after install.
Uhm.. this is what I am talking about with the 'system-setup program'. Maybe I was not too clear, but I think you are just looking for a fight. Not going to get one today sorry.
-- Stephen John Smoogen | CCN-5 Security Team LANL SIRT Team Leader | SMTP: smoogen@xxxxxxxx Los Alamos National Laboratory | Voice: 505.664.0645 Ta-03 SM-1498 MS: B255 DP 10S | FAX: 505.665.7793 Los Alamos, NM 87545 |
