The problem is that this bug was definitely present in Gutsy, and possibly
Feisty. So telling someone not to upgrade won't necessarily help them. If
you are providing Tech Support for someone, I would say it is safe to
upgrade to Hardy, but you need to go ahead and check their load/unload
cycles using the tools mentioned in this thread, and if necessary, apply the
fixes posted here.
On Mon, Jul 7, 2008 at 7:26 AM, Vincenzo Ciancia <email address hidden>
wrote:
>
> Let's state it clearly since
> in the latter case at least I will advice people that still didn't
> upgrade not to use hardy until we are reasonably sure that we are not
> going to damage their disk.
>
The problem is that this bug was definitely present in Gutsy, and possibly
Feisty. So telling someone not to upgrade won't necessarily help them. If
you are providing Tech Support for someone, I would say it is safe to
upgrade to Hardy, but you need to go ahead and check their load/unload
cycles using the tools mentioned in this thread, and if necessary, apply the
fixes posted here.
On Mon, Jul 7, 2008 at 7:26 AM, Vincenzo Ciancia <email address hidden>
wrote:
>
> Let's state it clearly since
> in the latter case at least I will advice people that still didn't
> upgrade not to use hardy until we are reasonably sure that we are not
> going to damage their disk.
>