by Job » Fri, 20 Jan 1995 16:25:33
If so, what happens when the device driver is closed, does the operating
system pop all modules for you?
Do all STREAM's modules run in the kernel, or can a pushed module run in
the users address space?
Thanks,
Joby
by Chandra Ba » Sun, 22 Jan 1995 08:34:15
: If so, what happens when the device driver is closed, does the operating
: system pop all modules for you?
: Do all STREAM's modules run in the kernel, or can a pushed module run in
: the users address space?
: Thanks,
: Joby
Most of the information I am giving here is in the context of SVR4.
Use the utility autopush to configure modules to be pushed automatically when
any STREAMS based device is opened. The OS does the rest.
All STREAM's modules run in the kernel space and as such must either be
linked into the kernel or loaded as a loadable driver/Module.
Balu.
1. What happens if a stream module is pushed onto multiple stream driver?
1.
What happens if a stream module is pushed onto multiple stream driver?
Will its open and close routines called each time when it is
pushed? And shall I write some special code to handle this situation?
2.
What happens if a stream module is opened multiple times?
Will its open and close routines called each time when it is
pushed? And shall I write some special code to handle this situation?
2. Disconnecting idle users automatically!
3. Pushing modules onto mounted stream: Inappropriate ioctl for device
4. Apache verbose his version to everyone on the internet
5. Solaris x86 failure to push streams module into network stream
6. A server problem?! Our site URL sometimes doesn't resolve. Help!
7. How to push STREAMS module into socket stream
8. radeonfb aggregated LY/LZ 8MB + ia64 void * vs u32
9. Pushing arbitrary STREAMS modules over an IP connection
10. Solaris 10(Sparc) Fireengine push another stream module
11. STREAMS: push module on /dev/tcp
12. Solaris 10(Sparc) Fireengine push another stream module
13. How to push a STREAMS module between ethernet driver and IP?