--On 19 November 2007 07:23:57 -0500 "David F. Skoll" <[EMAIL PROTECTED]> wrote:
> Ian Eiloart wrote: > >>> Hold on here. Are you stating that you expect users to actually RTFM? I >>> think you are expecting way too much. > >> No, it's not. Not when the users are professional IT people. > > :-) I don't think we hang around the same "Professional IT people" > >> The default configuration should suit personal installs, not corporate >> installs. > > Why is that? I bet most Clam users use it in a corporate or > organizational setting (simply because most home users don't use *NIX). Because ordinary users and IT staff have different needs. Regardless of what professionals actually do, they bloody well ought to think about it first. >> No upgrade should ever automatically change the current configuration >> file, except perhaps by adding documentation for new features. New >> features should work in a sensible way for personal installations >> without configuration. > > No. New features should require explicit enabling. Personal installs > can be served with the "config file template" idea where they say "give > me every feature you've got!" I don't mean the new feature should be on by default. Just that clamav should start even in the absence of a config file with a setting for that feature. So that the new code is backwardly compatible with the old config file. > > Regards, > > David. > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://lurker.clamav.net/list/clamav-users.html -- Ian Eiloart IT Services, University of Sussex x3148 _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
