|
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
Newsgroups: comp.os.linux.development, comp.os.linux.misc
From: iii...@swan.pyr (Alan Cox)
Date: Fri, 24 Sep 1993 17:35:47 GMT
Local: Fri, Sep 24 1993 1:35 pm
Subject: Re: Net-2 Patches are GREAT (sometimes)
In article <CDuxG4....@swi.psy.uva.nl> j...@swi.psy.uva.nl (Jan Wielemaker) writes: I forgot to mention this. The new release when it comes out will have >jmorr...@rflab.ee.ubc.ca (John Paul Morrison) writes: >>the newest pl13 source and followed the net2-debugged instructions. The >>instructions tell you to move your inet directory, then unpack the new >>code. No Makefile or CONFIG is included with net2-debugged, so I >>assume you are supposed to copy the old ones (from inet.old!). that corrected (and a few other oddments). >Tried exactly the same. I've got no network at home, but we're trying to Nope you've found a bug. It took me 4 machines and about 40 rlogin >get the network stuff going at the University. Even using the loopback >net, just `rlogin myself' followed by logout crashed the system without >any message!? At least that works on plain pl13. Now I trust that the >inet-D package is debugged, but how does one get it *properly* linked >to the kernel? attempts to duplicate it, but on some systems if you rlogin to localhost and the rlogin immediately screws up (as the rlogind/rlogin client pair of old tended too) you on odd occasion get a crash. This sort of thing illustrates how hard network debugging is, and why the real all new networking is taking so long. [Someone else asked how does NET2debugged fit in with the new networking. The answer is every relevant bug fix I've made has been fed back to the new networking people and most accepted and added. In time Net2debugged will no longer be neccessary and for once not being needed will make me happy! >The first thing I want are *reliable* remote running X11 applications. Try net2debugged on a real net. I don't release it until its had 3 days on a real machine doing real work on a busy net (40K/second broadcast packets + all the normal stuff). I've added local rlogin to my test list for the future and started looking at it except for that it does seem pretty much ok from reports so far apart from one other extra printk that crept in (udp.c udp_rcv kill the printk about Packet received for unknown socket). I've been using net2debugged heavily for X and its been quite good - I even test mpeg_play to a remote host as standard. >The second thing I want is nfs. NIS would be the greatest! NFS has been solid (but none too quick) since 0.99.11 (I think) 0.99.10 certainly had a memory corrupting bug. Over slip you need to turn on udp checksums and unless you have net2debugged set the slip mtu to about 1200 before not after you use dip to connect (goes for NET2E4 also) > Thanks --- Jan Thanks for finding a bug. I know where most of this evening will be going now 8-). Alan iii...@pyr.swan.ac.uk You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||