Re: future mol: 603, 2.4, glibc2.2?


Subject: Re: future mol: 603, 2.4, glibc2.2?
From: Stefan Jeglinski (jeglin@4pi.com)
Date: Wed Oct 10 2001 - 17:44:19 MDT


> > Or does your answer below imply that 603 support is back by way of
>> conspicuous absence in mentioning it?
>
>It is not there yet, but it is on my to-do list. When I get the time,
>I'll go through the source again and see if I can figure out what goes wrong.

Thanks. I'd even consider sending you a 6500, but you're way the hell
away from me.

>With mol-0.9.60 and booting in the newworld setting, right?

mol-0.9.61, boot_method: newworld

> > 1. Will occasionally go deaf to ethernet traffic.
>
>Some things to check:
>
>- The sheep_net driver filters the incoming IP traffic. The address
>which is allowed through the filter is printed to the syslog. Normally
>MOL determines the MOL-side IP address by looking at outgoing
>IP-packets. Possibly MOL is tricked to starts filtering using
>the wrong address (check /var/log/messages).

Will look for this.

>- If you use DHCP within MOL, the IP-filtering might possibly
>cause a problem when the lease is renewed.
>
>- Never use sheep_net on a an ethernet device which is not
>physically attached to an ethernet network. Communication between
>linux and Mac OS will work in the beginning, but after a while
>the transmit buffers fill up...

Neither should apply. It's a static IP which is network-connected 24/7.

>2.4.9 is fine. If you like 8.6, stay with it. It doesn't really
>matter with respect to mol.

Thanks for the response.

Stefan Jeglinski



This archive was generated by hypermail 2a24 : Wed Oct 10 2001 - 16:55:22 MDT