[coyotos-dev] Hi + some stuff I found researching

[Valerio Bellizzomi]

On 12/07/2006, at 17.48, Haplo wrote:

>Well, about point C. I was afraid you'd say something like that,  
>which is why I have this compelling argument prepared :P.
>1:I agree fully, the right thing to do is obviously to fix the code,  
>but this adds convenience for while that code is being fixed. Even on  
>MacOSX you'll occasionally run into a bad driver that causes a kernel  
>panic. The panic isn't a problem in coyotos, but errors will happen  
>and crashes will result, and a healing layer simply greatly reduces  
>the inconvenience. Also with the latter part of C, it could be  
>optionally made to provide convenience in fixing that code. In a  
>perfect world there's no place for a healing layer, but that's a very  
>"Linus" way of looking at it.

A separate layer isn't needed, this can be done inside the driver without
introducing a new layer in the system. With a correctly engineered pre-test
cycle, the driver can be slower but it gains robustness.
One more reason to avoid drivers written in haste to meet the time
schedule. There is nothing better than testing and verifying by hand.

val