[uClibc-cvs] uClibc/docs Glibc_vs_uClibc_Differences.txt,1.7,1.8

[Erik Andersen]

Update of /var/cvs/uClibc/docs
In directory winder:/tmp/cvs-serv14949

Modified Files:
	Glibc_vs_uClibc_Differences.txt 
Log Message:
Some minor doc updates


Index: Glibc_vs_uClibc_Differences.txt
===================================================================
RCS file: /var/cvs/uClibc/docs/Glibc_vs_uClibc_Differences.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- Glibc_vs_uClibc_Differences.txt	11 Dec 2002 20:44:48 -0000	1.7
+++ Glibc_vs_uClibc_Differences.txt	12 Feb 2003 13:09:59 -0000	1.8
@@ -36,15 +36,15 @@
 are not at all implemented.
 
 8) libnsl provides support for Network Information Service (NIS) which was
-originally called "Yellow Pages" or "YP", which is an extension of RPC
-invented by Sun to share Unix password files over the network.  I personally
-think NIS is an evil abomination, and should be avoided.  These days, using
-ldap is much more effective mechanism for doing the same thing.  uClibc does
-not provide libnsl.so.1, and has no support for Network Information Service
-(NIS).  We therefore, also do not provide any of the headers files provided by
-glibc under /usr/include/rpcsvc.   I am open to implementing ldap based
-password authentication, but I do not personally intend to implement it (since
-I have no use for it).
+originally called "Yellow Pages" or "YP", which is an extension of RPC invented
+by Sun to share Unix password files over the network.  I personally think NIS
+is an evil abomination, and should be avoided.  These days, using ldap is much
+more effective mechanism for doing the same thing.  uClibc provides a stub
+libnsl, but and has no actuall support for Network Information Service (NIS).
+We therefore, also do not provide any of the headers files provided by glibc
+under /usr/include/rpcsvc.   I am open to implementing ldap based password
+authentication, but I do not personally intend to implement it (since I have no
+use for it).
 
 9) uClibc's locale support is not 100% complete yet.  We are working on it.