hedrick@athos.rutgers.edu (Charles Hedrick) (10/19/90)
Archive-name: rutgers-cap/17-Oct-90 Original-posting-by: hedrick@athos.rutgers.edu (Charles Hedrick) Original-subject: Re: Help getting rutgers cap up! What/Where is enet.h Archive-site: athos.rutgers.edu [128.6.4.4] Archive-directory: /pub Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti) net/enet.h is part of the packet driver. This is the kernel support used by the new CAP Ethertalk implementation. It is in pub/enet.shar on athos.rutgers.edu. By using snitp.c instead of senetp.c (in lib/cap/ethertalk), it's actually possible to get my CAP Ethertalk to use /dev/nit, and not modify your kernel. But the performance implications of using /dev/nit in this application are worrisome. Not only is there more overhead for your Ethertalk, but the fact that /dev/nit is in use will slow down TCP/IP and NFS. So except for brief testing, I do not recommend using /dev/nit. All of our testing has been under 4.0.3c. I've tried it on sun3, sun3x, sun4, and sun4c. I have reasonable hope that it will work under 4.1 as well, but haven't tried it. The kernel support will need a slight change for 4.0.1, because one of the kernel routines is missing a crucial argument. I'm assuming that 4.0.3 will work, as it is normally quite close to 4.0.3c, but I actually haven't tried it on 4.0.3 either. (We use 4.0.3c on all architectures.)