old-www/LDP/nag/node132.html

45 lines
1.8 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>NIS versus NIS+</TITLE>
</HEAD>
<BODY LANG="EN">
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
<B> Next:</B> <A HREF="node133.html">The Client Side of </A>
<B>Up:</B> <A HREF="node130.html">The Network Information System</A>
<B> Previous:</B> <A HREF="node131.html">Getting Acquainted with NIS</A>
<BR> <P>
<H1><A NAME="SECTION0012200000">NIS versus NIS+</A></H1>
<P>
<A NAME="nisnisplus"></A>
<A NAME="5039"></A>
<P>
NIS and NIS+ share little more than their name and a common goal.
NIS+ is structured in an entirely different way. Instead of a flat
name space with disjoint NIS domains, it uses a hierarchical name space
similar to that of DNS. Instead of maps, so called <em>tables</em> are
used that are made up of rows and columns, where each row represents an
object in the NIS+ database, while the columns cover those properties
of the objects that NIS+ knows and cares about. Each table for a
given NIS+ domain comprises those of its parent domains. In addition,
an entry in a table may contain a link to another table. These features
make it possible to structure information in many ways.
<P>
Traditional NIS has an RPC version number of-2, while NIS+ is
version-3.
<P>
NIS+ does not seem to be very widely used yet, and I don't really
know that much about it. (Well, almost nothing). For this reason, we
will not deal with it here. If you are interested in learning more about
it, please refer to Sun's NIS+ administration manual
([<A HREF="#nisplus"></A>]).
<P>
<BR> <HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>