|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
From: Avi Freedman <freedman@netaxs.com> To: bass@linux.silkroad.com (Tim Bass) Date: Fri, 4 Oct 1996 17:41:55 -0400 (EDT) Cc: michael@memra.com, nanog@merit.edu, iepg@iepg.org In-Reply-To: <199610042118.RAA02605@linux.silkroad.com> from "Tim Bass" at Oct 4, 96 05:18:25 pm > > This is not the right forum to discuss TCP internals nor is it the right > > forum to discuss building hardened kernels > > That may or may not be true, I'll pass on that one. > > What is the name of the 'right list' for this discussion, BTW? > linux-net is quiet and the linux code fragement for linux > does not work on high speed networks..... > > If you have a pointer to a better place to work on this, I would > appreciate it. I feel like I'm hacking kernel code in a vaccuum! > Some good suggestion would save time, and I have not found a > good list to work on internals. > > All suggestions to good kernel hackers lists working on > this is appreciated. > > Thanks, > > Tim It's in-scope for nanog to the extent that published results and host-mod procedures are something we may want to pass on to publishers, but probably some of the TCP/IP newsgroups would be a better place than nanog. Perhaps inet-access? Inet-access at least has so much random garbage flowing by that people are used to responding only to what they are interested in. Nanog usually (at least, in my case it does) goes right into my main mailbox; inet-access is a "when I have time" kind of thing. Avi
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |