From owner-doc-jp@jp.freebsd.org  Mon May  7 03:42:51 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id DAA24277;
	Mon, 7 May 2001 03:42:51 +0900 (JST)
	(envelope-from owner-doc-jp@jp.FreeBSD.org)
Received: from mx.alles.or.jp (mx.alles.or.jp [210.231.151.65])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id DAA24272
	for <doc-jp@jp.freebsd.org>; Mon, 7 May 2001 03:42:50 +0900 (JST)
	(envelope-from rushani@alles.or.jp)
Received: from smtp.alles.or.jp (ppp01058.nagaoka.alles.or.jp [210.231.144.122])
	by mx.alles.or.jp (8.9.3/3.7W-ALLESNET) with ESMTP id DAA21330
	for <doc-jp@jp.freebsd.org>; Mon, 7 May 2001 03:42:42 +0900 (JST)
Date: Mon, 07 May 2001 03:44:57 +0900 (JST)
Message-Id: <20010507.034457.71081976.rushani@alles.or.jp>
To: doc-jp@jp.freebsd.org
From: Hideyuki KURASHINA <rushani@alles.or.jp>
In-Reply-To: <20010505.121043.126571074.rushani@alles.or.jp>
References: <20010505.041103.104025248.hrs@eos.ocn.ne.jp>
	<20010505.121043.126571074.rushani@alles.or.jp>
X-Mailer: Mew version 1.95b115 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Organization: Nagaoka National College of Technology
X-URL: http://www.alles.or.jp/rushani/
Mime-Version: 1.0
Content-Type: Multipart/Mixed;
 boundary="--Next_Part(Mon_May__7_03:44:57_2001_462)--"
Content-Transfer-Encoding: 7bit
Reply-To: doc-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: doc-jp 8184
Subject: [doc-jp 8184] Re: Call for Translators
Errors-To: owner-doc-jp@jp.freebsd.org
Sender: owner-doc-jp@jp.freebsd.org
X-Originator: rushani@alles.or.jp

----Next_Part(Mon_May__7_03:44:57_2001_462)--
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

$BARIJ!w?73c(B $B$G$9!#(B

>>> On Sat, 05 May 2001 12:10:43 +0900 (JST), Hideyuki KURASHINA <rushani@alles.or.jp> said:

> 4.4 BSD $B0-KbK\$N(B book.9.sgml(Network Filesystem)$B$NM=Ls$r$*4j$$$7$^$9$G$9!#(B

$BK]Lu$7$^$7$?!#::FI$r$*4j$$$7$^$9!#<+8J?=9p$7$F$*$-$^$9$H!"(B2 $B$D$a$N(B
$B%Q%i%0%i%U$N(B among $B$,F~$C$?9T$NLu$,?4G[$G$9!#(B(^-^;

$B$=$l$+$i!"86J8$N:G8e$NJ}$G!"(B

    from the protocol specification
    <xref linkend="biblio-macklem">.
    The
    NFS

$B$H$J$C$F$^$9$,!"%T%j%*%I$N0LCV$O(B

    from the protocol specification.
    <xref linkend="biblio-macklem">
    The
    NFS

$B$G$$$$$G$9$h$M!)(B

----
Hideyuki KURASHINA		Department of Mechanical Engineering, 
rushani@alles.or.jp		Nagaoka National College of Technology

----Next_Part(Mon_May__7_03:44:57_2001_462)--
Content-Type: Text/Sgml; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="book.9j.sgml"

  <sect1>
      <title>Network Filesystem</title>
      <title>$B%M%C%H%o!<%/(B $B%U%!%$%k%7%9%F%`(B</title>

  <para>Initially, networking was used
    to transfer data from one machine to another.
    Later, it evolved to allowing users to log in remotely to another machine.
    The next logical step was to bring the data to the user,
    instead of having the user go to the data --
    and network filesystems were born.
    Users working locally
    do not experience the network delays on each keystroke,
    so they have a more responsive environment.</para>
  <para>$BEv=i(B,
    $B%M%C%H%o!<%-%s%0$O%G!<%?$r$"$k%^%7%s$+$i(B
    $BB>$N%^%7%s$XE>Aw$9$k$?$a$KMQ$$$i$l$F$$$^$7$?(B.
    $B$N$A$K(B,
    $B$=$l$O5v2D$5$l$F$$$k%f!<%6$K1s$/$N%^%7%s$X%m%0%$%s$9$k$?$a$KH/E8$7$^$7$?(B.
    $B<!$NI,A3E*$J%9%F%C%W$O%f!<%6$K%G!<%?$r<h$j$K9T$+$;$kBe$j$K(B,
    $B%G!<%?$r;}$C$F$/$k$3$H$G$7$?(B.
    $B$=$7$F%M%C%H%o!<%/%U%!%$%k%7%9%F%`$,@8$^$l$?$N$G$9(B.
    $B%m!<%+%k$G:n6H$7$F$$$k%f!<%6$O%-!<$rBG$D$?$S$K%M%C%H%o!<%/$NCY$l$r46$8$:(B,
    $B$h$j1~Ez@-$NNI$$4D6-$r<j$KF~$l$^$7$?(B.</para>

  <para>Bringing the filesystem to a local machine was among the first
    of the major client-server applications.
    The
    <emphasis>server</emphasis>
    is the remote machine that exports one or more of its filesystems.
    The
    <emphasis>client</emphasis>
    is the local machine that imports those filesystems.
    From the local client's point of view,
    a remotely mounted filesystem appears in the file-tree name space
    just like any other locally mounted filesystem.
    Local clients can change into directories on the remote filesystem,
    and can read, write, and execute binaries within that remote filesystem
    identically to the way that they can do these operations
    on a local filesystem.</para>
  <para>$B%U%!%$%k%7%9%F%`$r%m!<%+%k%^%7%s$K;}$C$F$/$k$3$H$O(B
    $B:G=i$N<gMW$J%5!<%P(B-$B%/%i%$%"%s%H7?%"%W%j%1!<%7%g%s$NCf$N$R$H$D$G$7$?(B.
    <emphasis>$B%5!<%P(B</emphasis>
    $B$O(B 1 $B$D$b$7$/$O$=$l0J>e$N%U%!%$%k%7%9%F%`$r(B
    $B%(%/%9%]!<%H$9$k%j%b!<%H$N%^%7%s$G$9(B.
    <emphasis>$B%/%i%$%"%s%H(B</emphasis>
    $B$O$=$N%U%!%$%k%7%9%F%`$r%$%s%]!<%H$9$k%m!<%+%k$N%^%7%s$G$9(B.
    $B%m!<%+%k$N%/%i%$%"%s%H$+$i8+$k$H(B,
    $B%j%b!<%H$G%^%&%s%H$5$l$?%U%!%$%k%7%9%F%`$O(B
    $B%m!<%+%k$K%^%&%s%H$5$l$?B>$N%U%!%$%k%7%9%F%`$N$h$&$K(B
    $B%U%!%$%k%D%j!<$NL>A06u4V$K8=$l$^$9(B.
    $B%m!<%+%k$N%/%i%$%"%s%H$O(B
    $B%j%b!<%H$N%U%!%$%k%7%9%F%`>e$K%G%#%l%/%H%j$rJQ$($?$j(B,
    $B%m!<%+%k$N%U%!%$%k%7%9%F%`>e$G$9$k$N$HA4$/F1$8$h$&$K(B
    $B%j%b!<%H$N%U%!%$%k%7%9%F%`$GFI$_=q$-$r$7$?$j(B,
    $B%P%$%J%j$r<B9T$7$?$j$G$-$^$9(B.</para>

  <para>When the local client does an operation on a remote filesystem,
    the request is packaged and is sent to the server.
    The server does the requested operation and
    returns either the requested information or an error
    indicating why the request was denied.
    To get reasonable performance,
    the client must cache frequently accessed data.
    The complexity of remote filesystems lies in maintaining cache
    consistency between the server and its many clients.</para>
  <para>$B%m!<%+%k$N%/%i%$%"%s%H$,(B
    $B%j%b!<%H$N%U%!%$%k%7%9%F%`>e$G%*%Z%l!<%7%g%s$r$9$k$H(B,
    $B$=$N%j%/%(%9%H$,$R$H$^$H$a$K$5$l$F%5!<%P$KAw$i$l$^$9(B.
    $B%5!<%P$OMW5a$5$l$?%*%Z%l!<%7%g%s$r9T$$(B,
    $BMW5a$5$l$?>pJs$+$J$<$=$NMW5a$,5q@d$5$l$?$+$r<($9%(%i!<$N$I$A$i$+$rJV$7$^$9(B.
    $BE,@Z$J@-G=$rF@$k$K$O(B,
    $B%/%i%$%"%s%H$OIQHK$K%"%/%;%9$5$l$?%G!<%?$r%-%c%C%7%e$7$J$1$l$P$J$j$^$;$s(B.
    $B%j%b!<%H%U%!%$%k%7%9%F%`$NJ#;($5$O(B,
    $B%5!<%P$HB?$/$N%/%i%$%"%s%H$N4V$N%-%c%C%7%e$N0l4S@-$r0];}$9$k$3$H$K$"$j$^$9(B.</para>

  <para>Although many remote-filesystem protocols
    have been developed over the years,
    the most pervasive one in use among UNIX
    systems is the Network Filesystem
    (NFS),
    whose protocol and most widely used implementation were
    done by Sun Microsystems.
    The 4.4BSD kernel supports the
    NFS
    protocol, although the implementation was done independently
    from the protocol specification
    <xref linkend="biblio-macklem">.
    The
    NFS
    protocol is described in
    Chapter 9.
    </para>
  <para>$B%j%b!<%H%U%!%$%k%7%9%F%`%W%m%H%3%k$NB?$/$O(B
    $BD94|$K$o$?$C$F3+H/$5$l$F$-$^$7$?$,(B,
    UNIX $B%7%9%F%`$K$*$$$F:G$bIa5Z$7$F$$$k$b$N$O(B
    $B%M%C%H%o!<%/%U%!%$%k%7%9%F%`(B(NFS)$B$G$9(B.
    $B$=$N%W%m%H%3%k$HBgItJ,$N<BAu$O(B Sun Microsystems $B$K$h$k$b$N$G$9(B.
    $B<BAu$O%W%m%H%3%k$N5,3J$+$iFHN)$7$F9T$o$l$F$$$^$9$,(B,
    4.4BSD $B$N%+!<%M%k$O(B NFS $B%W%m%H%3%k$r%5%]!<%H$7$F$$$^$9(B.
    <xref linkend="biblio-macklem">
    NFS $B%W%m%H%3%k$O(B 9 $B>O$G=R$Y$i$l$F$$$^$9(B.
    </para>

  </sect1>

----Next_Part(Mon_May__7_03:44:57_2001_462)----
