Fabrice FACORAT wrote:
> Le Vendredi 31 Ao�t 2001 19:59, vous avez �crit :
>
>>Updated using Software Manager
>>
>>1. neither links in /boot not entry in /etc/lilo.conf were created. I
>>had to manually run installkernel -c (to create links) and lilo.
>>
>
> amazing. but it's easy to correct.
>
When you know and expect it - yes. For somebody on cooker list? No
doubts. But just today I have read a sad story exactly about this -
somebody used Software Manager to update kernel, got no error messages,
rebooted - and was left before two characters LI. What would you say to
this guy? And he was lucky - he knew how to correct this. 95% of users
that post in NG do not even know what lilo is (should they, really?)
>
>>2. supermount was not disabled during update. Error messages after next
>>reboot (obviously, mandrake_everytime kicks in too late, after
>>automounted filesystems already failed).
>>
>
> supermount at this time is disbale. But it back in the last kernel.
I know this. What is the point of your comment? What I wanted to say -
it should be disabled in postinstall script of kernel because it is
*known* that it does not work. And it is done in cooker (just read
kernel changelog).
> supermount -i disable
>
Oh, my ...
>
>
>>3. lm_sensors do not work anymore. I specifically configured them and
>>verified that everything works with 2.4.3-20mdk. Please, could anybody
>>finally check what's going on?
>>
>
> update to the latest lm_utils
>
Oh, God! I posted three or four times that lm_utils are broken since
2.4.6 (IIRC). Again, what do you want to say? Besides, thay are not
"the latest and greatest". They are exactly those that are built for
specific kernel release.
-andrej
