hi there,
Previously when I was hacking STREAMS coded we had a userspace
environment where on one machine we could have a few userspace
STREAMS processes, and a few userspace virtual network processes,
they all talked to each other with STREAMS drivers which could
talk with the virtual networks.
So on one machine you could have a complete simulated network, and
you could then run network programs on each of the virtual hosts.
This was cool, but now I don't have access to this. :-( So I'm
looking at LiS for development.
I've played with it for a few days now and would like to get some
confirmation about what I've discovered.
1) Can the kernel version of LiS only be debugged with GDB source
level debugger with a two machine setup?
2) The userspace version does not have access to the TCPIP stack, so
it can only be used standalone? (and for 'loopback' or 'testharness'
cases)
3) For kernel version 'strtst' program talks to the kernel LiS. For the
userspace version, it looks like 'strtst' is both the 'userspace' program
and the STREAMS part, in one program. So the 'interface' between program
and STREAMS is just a function call? Maybe I missed something, but does
this not put limitations on the userspace version?
Basically, I'm looking to set up a development environment and would be
interested to know how you develop your STREAMS code?
Do you just take the hit of debugging the kernel, do you have a clever
userspace setup, or do you just write the code and it works first time!
Thanks in advance,
andy
