On Tue, 7 Oct 2008, John Smith wrote: > I must say that for the disadvantaged, this has been a great debate. > However, it has missed the basic premise. The Question and Issue is that > ClamAV is failing without warning.
To which the 'advantaged' respond that the warnings are in 'documentation' or in the logs, belittling the needs of a large un(der)qualified sector of the user base. It is not failing "without" warning, but without *sufficient* warning for the nature of the *whole* user base. > .... the basic fact that needs to be addressed is that the product is > not presenting information to the users that an error is occurring in > a way that can be readily identified as a situation to get fixed. (nod) And loud declarations of how it works for *some* does not help it work for the rest. > Failure to notify is not a feature, it is a problem. End users should > not have to resort to other means to determine that this product is > working correctly. <bold>If they do</bold>, then this product is > defective. I would not describe a highly effective and laudable piece of software as defective because there was a minor (and debatable!) oversight in its development. At this point I would join with the people who point to the pre-release status and say, "this is to be expected". What I *don't* expect is a bunch of people to say that a strong and valid suggestion to fix a shortcoming is 'lazy' because *they* have the extra time/resources to make it work for them. I'm hoping the suggestions provided help make it work for everyone. Remember the bottom line principal: Every time we do anything that limits the ability of *anyone* to understand such basic ideas as whether the product is *working*, we are giving that person a chance to get a virus, and to *spread* that virus. Even if *we* (select your own peer group) are "safe", we would still suffer the loss of bandwidth caused by too many infeced machines. It is in *all* our interests, even those I label as 'advantaged', to make this software as EASY and RELIABLE as possible. I think that covers that. :) - C _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
