Remove references to first-person pronouns ("I", "me", etc.): all they
do is serve to confuse the reader (who is this "I"?). Stuff inside <question> tags in the mini-faq's and clearly-attributed blocks was left alone.
This commit is contained in:
Dima Dorfman
parent
ff708993b6
commit
a0415e82f0
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9209
21 changed files with 193 additions and 186 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.36 2001/04/09 00:33:48 dd Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.37 2001/04/14 00:58:57 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="advanced-networking">
|
||||
|
|
@ -599,7 +599,7 @@ nfs_client_flags="-n 4"</programlisting>
|
|||
(a.k.a., <quote>exported</quote>) and with what clients they will
|
||||
be shared. Each line in the file specifies a file system to be
|
||||
shared. There are a handful of options that can be used in this
|
||||
file but I will only touch on a few of them. You can find out
|
||||
file but only a few will be mentioned here. You can find out
|
||||
about the rest in the &man.exports.5; man page.</para>
|
||||
|
||||
<para>Here are a few example <filename>/etc/exports</filename>
|
||||
|
|
@ -679,29 +679,39 @@ nfs_client_flags="-n 4"</programlisting>
|
|||
<sect2>
|
||||
<title>Practical Uses</title>
|
||||
|
||||
<para>There are many very cool uses for NFS. I use it quite a bit
|
||||
on the LAN I admin. Here are a few ways I have found it to be
|
||||
useful.</para>
|
||||
<para>There are many very cool uses for NFS. Some of the more common
|
||||
ones are listed below.</para>
|
||||
|
||||
<para>I have several machines on my network but only one of them has
|
||||
a CD-ROM drive. Why? Because I have that one CD-ROM drive shared
|
||||
with all the others via NFS. The same can be done with floppy
|
||||
drives.</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Have several machines on a network and share a CD-ROM or
|
||||
floppy drive among them. This is cheaper and often more
|
||||
convenient.</para>
|
||||
</listitem>
|
||||
|
||||
<para>With so many machines on the network it gets old having your
|
||||
personal files strewn all over the place. I have a central NFS
|
||||
server that houses all user home directories and shares them with
|
||||
the rest of the machines on the LAN, so no matter where I login I
|
||||
have the same home directory.</para>
|
||||
<listitem>
|
||||
<para>With so many machines on a network, it gets old having your
|
||||
personal files strewn all over the place. You can have a
|
||||
central NFS server that houses all user home directories and
|
||||
shares them with the rest of the machines on the LAN, so no
|
||||
matter where you log in you will have the same home
|
||||
directory.</para>
|
||||
</listitem>
|
||||
|
||||
<para>When you get to reinstalling FreeBSD on one of your machines,
|
||||
NFS is the way to go. Just pop your distribution CD into your
|
||||
file server and away you go.</para>
|
||||
<listitem>
|
||||
<para>When you get to reinstalling FreeBSD on one of your
|
||||
machines, NFS is the way to go! Just pop your distribution
|
||||
CD-ROM into your file server and away you go!</para>
|
||||
</listitem>
|
||||
|
||||
<para>I have a common <filename>/usr/ports/distfiles</filename>
|
||||
directory that all my machines share. That way when I go to
|
||||
install a port that I already installed on a different machine I
|
||||
do not have to download the source all over again.</para>
|
||||
<listitem>
|
||||
<para>Have a common <filename>/usr/ports/distfiles</filename>
|
||||
directory that all your machines share. That way, when you go
|
||||
to install a port that you've already installed on a different
|
||||
machine, you do not have to download the source all over
|
||||
again!</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
@ -1036,12 +1046,11 @@ hostname myclient.mydomain</programlisting>
|
|||
<sect2>
|
||||
<title>Using Shared <filename>/</filename> and <filename>/usr</filename>
|
||||
filesystems</title>
|
||||
|
||||
<para>At present there isn't an officially sanctioned way of doing this,
|
||||
although I have been using a shared <filename>/usr</filename>
|
||||
filesystem and individual <filename>/</filename> filesystems for each
|
||||
client. If anyone has any suggestions on how to do this cleanly,
|
||||
please let me and/or the &a.core; know.</para>
|
||||
|
||||
<para>Although this is not an officially sanctioned or supported way
|
||||
of doing this, some people report that it works quite well. If
|
||||
anyone has any suggestions on how to do this cleanly, please tell
|
||||
&a.doc;.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
@ -1067,21 +1076,21 @@ hostname myclient.mydomain</programlisting>
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>If you live in Europe I suggest you investigate the ISDN card
|
||||
section.</para>
|
||||
<para>If you live in Europe you might want to investigate the ISDN card
|
||||
section.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If you are planning to use ISDN primarily to connect to the
|
||||
Internet with an Internet Provider on a dial-up non-dedicated basis,
|
||||
I suggest you look into Terminal Adapters. This will give you the
|
||||
you might look into Terminal Adapters. This will give you the
|
||||
most flexibility, with the fewest problems, if you change
|
||||
providers.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If you are connecting two LANs together, or connecting to the
|
||||
Internet with a dedicated ISDN connection, I suggest you consider
|
||||
Internet with a dedicated ISDN connection, you might consider
|
||||
the stand alone router/bridge option.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -1220,8 +1229,8 @@ hostname myclient.mydomain</programlisting>
|
|||
and bridging technology, please refer to a Networking reference
|
||||
book.</para>
|
||||
|
||||
<para>In the context of this page, I will use router and bridge
|
||||
interchangeably.</para>
|
||||
<para>In the context of this page, the terms router and bridge will
|
||||
be used interchangeably.</para>
|
||||
|
||||
<para>As the cost of low end ISDN routers/bridges comes down, it will
|
||||
likely become a more and more popular choice. An ISDN router is a
|
||||
|
|
@ -1234,7 +1243,7 @@ hostname myclient.mydomain</programlisting>
|
|||
|
||||
<para>The main problem with ISDN routers and bridges is that
|
||||
interoperability between manufacturers can still be a problem. If you
|
||||
are planning to connect to an Internet provider, I recommend that you
|
||||
are planning to connect to an Internet provider, you should
|
||||
discuss your needs with them.</para>
|
||||
|
||||
<para>If you are planning to connect two lan segments together, ie: home
|
||||
|
|
@ -2924,7 +2933,7 @@ dhcp_flags=""</programlisting>
|
|||
<title><filename>/etc/namedb/named.conf</filename></title>
|
||||
|
||||
<programlisting>
|
||||
// $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.1 2000/07/15 07:49:29 kris Exp $
|
||||
// $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.37 2001/04/14 00:58:57 murray Exp $
|
||||
//
|
||||
// Refer to the named(8) man page for details. If you are ever going
|
||||
// to setup a primary server, make sure you've understood the hairy
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue