On Wednesday 20 September 2006 2:09 am, Darryl Gregorash wrote:
On 19/09/06 22:12, Fred A. Miller wrote:
On Tuesday 19 September 2006 11:08 pm, Darryl Gregorash wrote:
<snip> The reply, "When I am done."
I don't write code and assumed it was an "easy fix."
I have no idea, and won't speculate. Meanwhile, perhaps you can do as suggested, revert to the previous version of mkinitrd, and don't forget to *run* mkinitrd afterwards.
For Moby: I never suggested this wasn't a serious issue, and perhaps the reason a fix hasn't arrived yet is because the SuSE people also regard it as such -- and thus wish to make damn sure it is properly fixed before releasing an upgrade.
Also, there are only some systems that are affected with this new kernel update. Systems I upgraded today don't have the problem with mkinitrd. Fred -- MickySoft, the ultimate corporate parasite.