Think of the IUCV driver like you would zfcp: You use the sysfs to set up the connection parameters (for zfcp its WWPN/LUN for IUCV its enduser/node/program) and then let the application use the simple open/close/read/write/ioctl semantics.
-----Original Message----- Am not sure if I understand that fully, probably because I lack 25 years of experience with IUCV in comparisation ;-). For what I do understand, you have an address range (the name of the machine) and a service identifier [program name] for IUCV. That would match the IP/PORT equivalent in the IP world. You can connect to the other side and basically you get a pipeline to send and receive messages [packets in the IP world]. Not all features of the network stack apply to IUCV, but a char device is lacking the connect/disconnect and addressing scheme that networking implies. For me, that sounds like network. What am I missing? ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
