Detecting exploding batteries, part 2

[Danny Kukawka]

On Monday 25 September 2006 12:02, Richard Hughes wrote:
> On 25/09/06, Danny Kukawka <danny.kukawka at web.de> wrote:
> > On Monday 25 September 2006 09:19, Richard Hughes wrote:
> > > 1. Vendors (Redhat/Suse) can send out updates to a HAL package in a
> > > matter of days.
> >
> > 1.) take a look at the release cycle of HAL
> > 2.) take a look at the release cycle of the distributions (6 months - 1
> > year or more for business products)
> > 3.) take a look at the rules for updates of the distributions. For SUSE
> > e.g. we only offer official updates for (security) bugs and not for such
> > stuff. No distribution send out a update for such stuff.
>
> Well, that's SuSe policy. 

This is not only a _SUSE_ policy (if you ignore stuff as e.g. official 
unsupported repos as e.g. unstable/experimental (for debian) or Universe (for 
Ubuntu) or other privat repos).

> I can tell you for 100% certainty that 
> *every* affected user will not have realised before the 6 months
> next-release of HAL (and that's if the distro can't roll a trivial
> update).

Maybe if all of them sit on island without newspapers, internet and tv. IMO 
the most of them will have replaced their batterie within the next 6 months.

> > How many laptops blowed up? One or two?
>
> Over 10,000 batteries are affected just for the DELL problem. HP and
> Apple are likely to have a smaller recall, but still significant.

Yes and all blowed up already ... ;-)

Btw. this is the job of the hardware manufacturer and not HAL. They should 
provide a tool to identify this batteries (and they can use maybe HAL, maybe 
other tools to identify the effected batteries).

Danny