Import ncpfs 0.3

README

@@ -17,13 +17,46 @@ I use tools written by Greg Page, Caldera. I hope I did not do too
 much harm to their business. For your convenience I included the file
 ipx.tar made available by Caldera.
 
-For the curious: the file ncplib.c is usable from user space as well!
-Look at the file ncptest.c for a possible use. I use ncptest to check
-my assumptions about the widely undocumented NetWare Core
-Protocol. Maybe this is the beginning of a free NetWare API for Linux!
-I would be happy to receive your comments on this.
+My main source of information is a book written in german by Manfred
+Hill and Ralf Zessin, "Netzwerkprogrammierung in C", IWT Verlag GmbH,
+1995, ISBN 3-88322-491-X. It contains quite a lot of typographical and
+other errors, but I find it very valuable as an introduction to NCP
+programming. If you know about the concepts and possibilities of NCP,
+Ralph Brown's interrupt list becomes much more readable. It's much
+easier to find undocumented information if you know what to look for!
 
-LIMITATIONS (compare these with smbfs :-))
+
+MAILING LIST
+
+There is a mailing list for discussing lwared and ncpfs. Here's the
+message I received after subscribing:
+
+---
+Thank you for your subscription to the list "linware".
+
+Topics for the list:
+- discussing LinWare server, its features, installation problems and bugs
+- using IPX protocol under Linux
+- IPX routing and router daemons under Linux
+
+Send your list postings to address: "linware@sh.cvut.cz"
+Send your list control commands to address: "listserv@sh.cvut.cz"
+---
+
+You can subscribe to this list by sending a message with a line 
+'add your_name@your_host linware' to listserv@sh.cvut.cz .
+
+
+NCPLIB
+
+For the curious: the file ncplib.c is usable from user space as well.
+Look at the file ncptest.c for a possible use. I use ncptest to check
+my assumptions about the widely undocumented NetWare Core Protocol.
+Maybe this is the beginning of a free NetWare API for Linux! I would
+be happy to receive your comments on this.
+
+
+LIMITATIONS (compare these with smbfs :-)
 
 The limitations ncpfs has are the natural limitations of the NCP
 protocol, which was designed with MS-DOS based PCs in mind. The first
@@ -44,4 +77,3 @@ different. You can never know when the client will access the file-id
 you offered, so you would have to cache the inode numbers
 indefinitely long. I think this should not be done in kernel mode, as
 it would require an unlimited amount of RAM.
-