On Mon, Jun 05, 2000 at 12:04:31AM +0300, Kalle Olavi Niemitalo wrote:
> Sune Kirkeby <[EMAIL PROTECTED]> writes:
>
> > $ settrans /servers/socket/2 /hurd/pfinet --interface=eth0 \
> > --address=195.97.129.13 --netmask=255.255.255.0 \
> > --gateway=195.97.129.3
> > $ ping 127.0.0.1
> > ping: Translator died.
>
> If you run settrans with the --active option, you should see the
> error message from the dying translator.
>
Ah. That's a nice thing to know. Thanks (to all who replied).
> $ settrans --active /servers/socket/2 /hurd/pfinet --interface=eth0 \
> --address=195.97.129.13 --netmask=255.255.255.0 \
> --gateway=195.97.129.3
/hurd/pfinet: eth0: (os/device) no such device
settrans: /hurd/pfinet: Translator died
$
Is that not to be expectede though, since
$ devprobe eth0
$
seem to say the same thing?
I took some time to dig around in the eepro100 driver source-code, and
unlike almost every other driver it does _not_ call register_netdev
anywhere. So, does the Mach kernel register it's Linux drivers as
modules, which is where register_netdev seem to be called from, or is
the missing register_netdev unimportant to GNU/Mach?
Again, any and all suggestions as to what I am doing wrong would be
greatly appreciated.
--
Sune Kirkeby | "Imagine, if you will, that there were no such
| thing as a hypothetical situation..."
PGP signature