> - IUCV network protocol family Why the need to make IUCV a network device? IUCV is not just a point-to-point beastie, it's a single-application-to-single-application protocol. The fact that it was used to create a network protocol for VM and Linux is because an extra layer to mux and demux application (socket) streams was added. You should think of IUCV as a serial device like a modem (or more like a winmodem). [It probably has a lot in common with the TTY driver.] The intent of the fsiucv driver was to exploit IUCV as it was first created. Having written many IUCV apps over the past 25 years (some of which are still running in a couple of major online systems) I attempted to take the semantics and map them to Linux. The char approach fitted better than a network device. The excellent skb handling routines that allow you to add headers/trailers etc. as you build up the protocol layers is overkill for the base IUCV operation. If I were to build an APPC driver then I'd definitely go the network driver way (FMH5/FMH7 processing is tailored for socket buffers).
Like I said, if ---------------------------------------------------------------------- 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
