[EMAIL PROTECTED] writes:
> Has anyone seen similar problem on recent -current or has someone an
> idea why vmware is issuing a SIOCGIFCONF ioctl without providing an
> interface name?
>
> Oct 19 18:04:53 mp /boot/kernel/kernel: linux_ioctl_socket(): ioctl 35093 on
To clarify, this is from debug
On 19 Oct, Dag-Erling Smorgrav wrote:
> [EMAIL PROTECTED] writes:
>> The error
>>
>> Could not get address for /dev/vmnet1: argument is invalid
>> Failed to configure ethernet0
>>
>> is all I get... (this is the host-only case, for bridged it says
>> something like could not get bri
This is -current from yesterday, with the recent patches to ansi.h to
get it to compile, and vmware2 with kse patches build today.
I did a
rm /compat/linux/dev/vmnet1;ln -s /dev/vmnet1 /compat/linux/dev
(see kse-patches announcement) and this seems to be working.
I tried bridged (us
