Hello,
it seems that the online documentation for learning limbo is rather
outdated. Does anyone know where I could get a more updated version to
learn limbo coding? Thanks!
-R
On Sat, Feb 20, 2016 at 08:41:01PM +0100, Mark van Atten wrote:
> > i think that david has a mirror up, and 9fs sources still works here.
>
> http://9p.io/
Thanks, Mark!
--
Thierry Laronde
http://www.kergis.com/
http://www.arts-po.fr/
Key
On Sat, Feb 20, 2016 at 11:26:58AM -0800, erik quanstrom wrote:
> > > anyway, please update your tcp. the debugging tools that are most
> > > helpful with tcp are
> > > /net/tcp/stats
> > > /net/tcp/*/status
> > > echo tcp>/net/log && tail -f /net/log
> >
> > To update I need to update the
> i think that david has a mirror up, and 9fs sources still works here.
http://9p.io/
Mark.
> > anyway, please update your tcp. the debugging tools that are most
> > helpful with tcp are
> > /net/tcp/stats
> > /net/tcp/*/status
> > echo tcp>/net/log && tail -f /net/log
>
> To update I need to update the sources. Where are now the "updated"
> sources? since Bell Labs site seems to be
> > anyway, please update your tcp. the debugging tools that are most
> > helpful with tcp are
> > /net/tcp/stats
> > /net/tcp/*/status
> > echo tcp>/net/log && tail -f /net/log
>
> We have definitively not the same systems ;-) The echo tcp brings an
> error for netlog.
sorry, it's "echo tcp
> anyway, please update your tcp. the debugging tools that are most
> helpful with tcp are
> /net/tcp/stats
> /net/tcp/*/status
> echo tcp>/net/log && tail -f /net/log
We have definitively not the same systems ;-) The echo tcp brings an
error for netlog.
But for further puzzling things (for
On Sat, Feb 20, 2016 at 09:20:52AM -0800, erik quanstrom wrote:
> On Sat Feb 20 06:04:02 PST 2016, tlaro...@polynum.com wrote:
> > On Sat, Feb 20, 2016 at 02:31:54PM +0100, hiro wrote:
> > > what is the latency on WAN?
> >
> > When using traceroute, I have 42.6ms for a roundtrip
> > (cf. with
On Sat Feb 20 06:04:02 PST 2016, tlaro...@polynum.com wrote:
> On Sat, Feb 20, 2016 at 02:31:54PM +0100, hiro wrote:
> > what is the latency on WAN?
>
> When using traceroute, I have 42.6ms for a roundtrip
> (cf. with LAN: 0.23ms).
>
> But the very same machine, under NetBSD, with the very same
On Sat, Feb 20, 2016 at 04:06:24PM +0200, lu...@proxima.alt.za wrote:
> > But the very same machine, under NetBSD, with the very same ip address,
> > downloads the very same file from the very same external server
> > (downloads.kergis.com) in 17s, while hget(1) spends 6 minutes doing
> > it.
>
>
> But the very same machine, under NetBSD, with the very same ip address,
> downloads the very same file from the very same external server
> (downloads.kergis.com) in 17s, while hget(1) spends 6 minutes doing
> it.
Just for one more data point: dump the hget output to /dev/null. That
may at
On Sat, Feb 20, 2016 at 02:31:54PM +0100, hiro wrote:
> what is the latency on WAN?
When using traceroute, I have 42.6ms for a roundtrip
(cf. with LAN: 0.23ms).
But the very same machine, under NetBSD, with the very same ip address,
downloads the very same file from the very same external
what is the latency on WAN?
On Sat, Feb 20, 2016 at 12:23:29PM +0100, Kenny Lasse Hoff Levinsen wrote:
>> [rtl8169 gbe full speed on LAN; very slow on WAN]
> Is your MTU higher that 1500? That might be able to mess things up over the
> internet.
>
Thanks for the suggestion but no: even with -m 1500, speed is still
awful.
Is your MTU higher that 1500? That might be able to mess things up over the
internet.
Best regards,
Kenny Levinsen
> On 20. feb. 2016, at 11.32, tlaro...@polynum.com wrote:
>
> I have compared downloading a file (via ftpfs) on the LAN, and
> downloading it from the WAN.
>
> On the LAN, I get
I have compared downloading a file (via ftpfs) on the LAN, and
downloading it from the WAN.
On the LAN, I get the 10MB file in less than a 1s (this is normal since
the node I download from has only a 100Mb ethernet).
On the WAN, it takes 6 minutes (with hget).
My conclusion is that the card
16 matches
Mail list logo
