On Fri, Apr 2, 2010 at 10:26 PM, Ric Werme ewe...@comcast.net wrote:
Serious bummer. It could still be the router, but it would take a
pretty weird problem.
It's prolly worth pointing out that, per MOD's description, there is
no router involved, only a switch. Of course, it could still be
Joshua Judson Rosen writes:
Well, there's an alternative to wide-screen monitors allowing for
wider windows: wide-screen monitors allowing for *more numerous*
80-column windows. :)
Me too.
Speaking for myself, as a programmer, if I am given a wide-screened
monitor to work on, I use the extra
On 04/03/2010 12:34 PM, Kevin D. Clark wrote:
Speaking for myself, as a programmer, if I am given a wide-screened
monitor to work on, I use the extra space for extra 80-column windows.
I think that there is something about the act of programming that
lends itself to working with *tall*
Jerry Feldman writes:
I usually set emacs up to close to full screen, with many more than 25
lines. I certainly like to see entire blocks of code. I still like to
keep individual lines of code and comments to under 80 columns.
Again -- me too!
Regards,
--kevin
--
alumni.unh.edu!kdc /
Michael ODonnell writes:
I'm capturing dumps of Enet traffic on the client and server boxes at
a remote customer site thus:
dumpcap -i eth0 -w /tmp/`hostname`.pcap
...and then copying them back to HQ where I feed them to Wireshark.
I am not (yet?) rigged up so I can sniff traffic
On Sat, Apr 3, 2010 at 5:19 PM, Kevin D. Clark
kevin_d_cl...@comcast.net wrote:
One thing that I've done to help me understand what is going on is to
rigorously go through each packet (sent and received) and verify that
what got sent is the same as what got received ...
Wireshark's ability
One thing I don't like about your setup is that you have 2 different
machines serving NFS directories to each other.
Explain, please. The motivation in our situation (at least historically)
is that although all our machines potentially need access to the
entire collection of files used by
