In message <[EMAIL PROTECTED]>, Julian Elischer writes:
>Poul-Henning Kamp wrote:
>>
>> In message <[EMAIL PROTECTED]>, Julian Elischer writes:
>> >
>> >The vmware vmmon driver used to use si_drv1 but suddenly it appears to
>> >have already been used (at least it is no-longer non-zero).
>> >It wo
Poul-Henning Kamp wrote:
>
> In message <[EMAIL PROTECTED]>, Julian Elischer writes:
> >
> >The vmware vmmon driver used to use si_drv1 but suddenly it appears to
> >have already been used (at least it is no-longer non-zero).
> >It would fail to open because it checks it before using it during op
In message <[EMAIL PROTECTED]>, Julian Elischer writes:
>
>The vmware vmmon driver used to use si_drv1 but suddenly it appears to
>have already been used (at least it is no-longer non-zero).
>It would fail to open because it checks it before using it during open.
>Changing the driver to use si_drv
The vmware vmmon driver used to use si_drv1 but suddenly it appears to
have already been used (at least it is no-longer non-zero).
It would fail to open because it checks it before using it during open.
Changing the driver to use si_drv2 fixes the problem.
Since drv1 is defined as 'for the use
