156 lines
2.8 KiB
HTML
156 lines
2.8 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>NIS Versus NIS+</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"><LINK
|
|
REL="HOME"
|
|
TITLE="Linux Network Administrators Guide"
|
|
HREF="index.html"><LINK
|
|
REL="UP"
|
|
TITLE="The Network Information System"
|
|
HREF="x-087-2-nis.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Getting Acquainted with NIS"
|
|
HREF="x10579.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="The Client Side of NIS"
|
|
HREF="x-087-2-nis.clients.html"></HEAD
|
|
><BODY
|
|
CLASS="SECT1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Linux Network Administrators Guide</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x10579.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
>Chapter 13. The Network Information System</TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x-087-2-nis.clients.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="X-087-2-NIS.NISPLUS"
|
|
>13.2. NIS Versus NIS+</A
|
|
></H1
|
|
><P
|
|
>NIS and NIS+ share little more than their name and a common goal. NIS+ is
|
|
structured entirely differently from NIS. Instead of a flat namespace with
|
|
disjoint NIS domains, NIS+ uses a hierarchical namespace similar to that of
|
|
DNS. Instead of maps, so-called <I
|
|
CLASS="EMPHASIS"
|
|
>tables</I
|
|
> are used that
|
|
are made up of rows and columns, in which each row represents an object in the
|
|
NIS+ database and the columns cover 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
|
|
><P
|
|
>NIS+ additionally supports secure and encrypted RPC, which helps greatly to
|
|
solve the security problems of NIS.</P
|
|
><P
|
|
>Traditional NIS has an RPC Version number of 2, while NIS+ is Version 3.
|
|
At the time we're writing, there isn't yet a good working implementation
|
|
of NIS+ for Linux, so it isn't covered here.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x10579.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x-087-2-nis.clients.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Getting Acquainted with NIS</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x-087-2-nis.html"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>The Client Side of NIS</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |