> > > Hi,
> > >
> > > Just for interest.. feedback on EOL...
> > >
> > > http://search.twitter.com/search?q=clamav
> >
> > Indeed, an EOL on the previous minor version is quite an hazard and
> may be
> > regarded as a self-destructive behavior: it could easily became an
> > End-Of-(product-)Line, meaning that people will switch to something
> more
> > "serious"...
> >
> > Was that the purpose?
> >
> 
> Why is there so much bitching about this ? The original announcement
> was
> made on the 6th October last year.
> http://lists.clamav.net/lurker/message/20091006.143601.d27bbd20.en.html
> along
> with multiple reminders so people
> have had over 6 months to upgrade.
> 
> Any proactive admin should be monitoring their software mailing lists
> so the
> excuse of "We weren't told" or "Why all of
> a sudden" are null and void.
> 
> To the clamav team, thanks for an awesome product :)

Nevertheless, many people aren't so "proactive". If you put them in trouble,
they will not blame themselves: they will instead switch to something
else... I'm having a couple of "help me!" calls from some clients of mine
(system vendors and installers) who never even subscribed to this list and
were absolutely unaware of the EOL.

Also, there are cases in which upgrading is not so easy: it may mean a whole
system upgrade.

In example, SuSE 10.1 up-to-date installations have gcc 4.1.0. Clamav 0.96
doesn't even ./configure there. You need to find some suitable binaries or
switch to a newer distribution. Is there a 5 months early alert enough?
Maybe. Maybe not: clamav often is not the only piece of software running on
a box...

The problem here is that old clamav versions have stopped working at all.
Wasn't it better to instead have freshclam to stop updating the database?
Please note freshclam is very used to issue alerts when new clamav versions
are available, but this didn't ever stop clamav from working. People may
have assumed that this would have been the clamav behavior at EOL deadline,
thereby underestimating the matter.

Giampaolo

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to