Diferenças

Aqui você vê as diferenças entre duas revisões dessa página.

--- free_bsd_handbook:iniciando:instalando_o_free_bsd:pos-instalacao [2009/08/04 18:27] – sem cabecalho e rodape cartola
+++ free_bsd_handbook:iniciando:instalando_o_free_bsd:pos-instalacao [2009/08/04 18:29] (atual) – versão ago 2009 gerada via cartola.org/freebsd-hb cartola
@@ Linha 1: / Linha 1: @@
 .10 Post-installation
-<code>  Configuration of various options follows the successful installation. An option can be configured by re-entering the configuration options before booting the new FreeBSD system or after installation using sysinstall (/stand/sysinstall in FreeBSD versions older than 5.2) and selecting Configure.
+<code>  Configuration of various options follows the successful installation. An option can be configured by re-entering the configuration options before booting the new FreeBSD system or after installation using sysinstall and selecting Configure.
 </code>
 .10.1 Network Device Configuration
@@ Linha 36: / Linha 36: @@
 <code>  If DHCP (Dynamic Host Configuration Protocol) is not required select [ No ] with the arrow keys and press Enter.
 </code>
-<code>  Selecting [ Yes ] will execute dhclient, and if successful, will fill in the network configuration information automatically. Refer to Section 27.5 for more information.
+<code>  Selecting [ Yes ] will execute dhclient, and if successful, will fill in the network configuration information automatically. Refer to Section 29.5 for more information.
 </code>
 <code>  The following Network Configuration screen shows the configuration of the Ethernet device for a system that will act as the gateway for a Local Area Network.
@@ Linha 99: / Linha 99: @@
 <code>  If [ No ] is selected, various services such telnetd will not be enabled. This means that remote users will not be able to telnet into this machine. Local users will still be able to access remote machines with telnet.
 </code>
-<code>  These services can be enabled after installation by editing /etc/inetd.conf with your favorite text editor. See Section 27.2.1 for more information.
+<code>  These services can be enabled after installation by editing /etc/inetd.conf with your favorite text editor. See Section 29.2.1 for more information.
 </code>
 <code>  Select [ Yes ] if you wish to configure these services during install. An additional confirmation will display:
@@ Linha 222: / Linha 222: @@
 .10.6 Configure Network File System
-<code>  Network File System (NFS) allows sharing of files across a network. A machine can be configured as a server, a client, or both. Refer to Section 27.3 for a more information.
+<code>  Network File System (NFS) allows sharing of files across a network. A machine can be configured as a server, a client, or both. Refer to Section 29.3 for a more information.
 </code>
 <code> 2.10.6.1 NFS Server
@@ Linha 483: / Linha 483: @@
 <code>  Figure 2-53. Exit User and Group Management
 </code>
-<code>  Groups can also be added at this time if specific needs are known. Otherwise, this may be accessed through using sysinstall (/stand/sysinstall in FreeBSD versions older than 5.2) after installation is completed.
+<code>  Groups can also be added at this time if specific needs are known. Otherwise, this may be accessed through using sysinstall after installation is completed.
 </code>
 <code>  When you are finished adding users, select Exit with the arrow keys and press Enter to continue the installation.
@@ Linha 508: / Linha 508: @@
 .10.14 Exiting Install
-<code>  If you need to configure additional network services or any other configuration, you can do it at this point or after installation with sysinstall (/stand/sysinstall in FreeBSD versions older than 5.2).
+<code>  If you need to configure additional network services or any other configuration, you can do it at this point or after installation with sysinstall.
 </code>
 <code>                     User Confirmation Requested
@@ Linha 538: / Linha 538: @@
 <code>  Configuring network services can be a daunting task for new users if they lack previous knowledge in this area. Networking, including the Internet, is critical to all modern operating systems including FreeBSD; as a result, it is very useful to have some understanding FreeBSD's extensive networking capabilities. Doing this during the installation will ensure users have some understanding of the various services available to them.
 </code>
-<code>  Network services are programs that accept input from anywhere on the network. Every effort is made to make sure these programs will not do anything "harmful". Unfortunately, programmers are not perfect and through time there have been cases where bugs in network services have been exploited by attackers to do bad things. It is important that you only enable the network services you know that you need. If in doubt it is best if you do not enable a network service until you find out that you do need it.
+<code>  Network services are programs that accept input from anywhere on the network. Every effort is made to make sure these programs will not do anything "harmful". Unfortunately, programmers are not perfect and through time there have been cases where bugs in network services have been exploited by attackers to do bad things. It is important that you only enable the network services you know that you need. If in doubt it is best if you do not enable a network service until you find out that you do need it. You can always enable it later by re-running sysinstall or by using the features provided by the /etc/rc.conf file.
-  You can always enable it later by re-running sysinstall or by using the features provided by the /etc/rc.conf file.
 </code>
 <code>  Selecting the Networking option will display a menu similar to the one below:
@@ Linha 571: / Linha 570: @@
 <code>  After selecting an MTA, or choosing not to select an MTA, the network configuration menu will appear with the next option being NFS client.
 </code>
-<code>  The NFS client option will configure the system to communicate with a server via NFS. An NFS server makes file systems available to other machines on the network via the NFS protocol. If this is a stand-alone machine, this option can remain unselected. The system may require more configuration later; see Section 27.3 for more information about client and server configuration.
+<code>  The NFS client option will configure the system to communicate with a server via NFS. An NFS server makes file systems available to other machines on the network via the NFS protocol. If this is a stand-alone machine, this option can remain unselected. The system may require more configuration later; see Section 29.3 for more information about client and server configuration.
 </code>
 <code>  Below that option is the NFS server option, permitting you to set the system up as an NFS server. This adds the required information to start up the RPC remote procedure call services. RPC is used to coordinate connections between hosts and programs.
@@ Linha 587: / Linha 586: @@
 <code>  Figure 2-58. Network Configuration Lower-level
 </code>
-<code>  The rpcbind(8), rpc.statd(8), and rpc.lockd(8) utilities are all used for Remote Procedure Calls (RPC). The rpcbind utility manages communication between NFS servers and clients, and is required for NFS servers to operate correctly. The rpc.statd daemon interacts with the rpc.statd daemon on other hosts to provide status monitoring. The reported status is usually held in the /var/db/statd.status file. The next option listed here is the rpc.lockd option, which, when selected, will provide file locking
+<code>  The rpcbind(8), rpc.statd(8), and rpc.lockd(8) utilities are all used for Remote Procedure Calls (RPC). The rpcbind utility manages communication between NFS servers and clients, and is required for NFS servers to operate correctly. The rpc.statd daemon interacts with the rpc.statd daemon on other hosts to provide status monitoring. The reported status is usually held in the /var/db/statd.status file. The next option listed here is the rpc.lockd option, which, when selected, will provide file locking services. This is usually used with rpc.statd to monitor what hosts are requesting locks and how frequently they request them. While these last two options are marvelous for debugging, they are not required for NFS servers and clients to operate correctly.
-  services. This is usually used with rpc.statd to monitor what hosts are requesting locks and how frequently they request them. While these last two options are marvelous for debugging, they are not required for NFS servers and clients to operate correctly.
 </code>
-<code>  As you progress down the list the next item here is Routed, which is the routing daemon. The routed(8) utility manages network routing tables, discovers multicast routers, and supplies a copy of the routing tables to any physically connected host on the network upon request. This is mainly used for machines which act as a gateway for the local network. When selected, a menu will be presented requesting the default location of the utility. The default location is already defined for you and can be
+<code>  As you progress down the list the next item here is Routed, which is the routing daemon. The routed(8) utility manages network routing tables, discovers multicast routers, and supplies a copy of the routing tables to any physically connected host on the network upon request. This is mainly used for machines which act as a gateway for the local network. When selected, a menu will be presented requesting the default location of the utility. The default location is already defined for you and can be selected with the Enter key. You will then be presented with yet another menu, this time asking for the flags you wish to pass on to routed. The default is -q and it should already appear on the screen.
-  selected with the Enter key. You will then be presented with yet another menu, this time asking for the flags you wish to pass on to routed. The default is -q and it should already appear on the screen.
 </code>
 <code>  Next in line is the Rwhod option which, when selected, will start the rwhod(8) daemon during system initialization. The rwhod utility broadcasts system messages across the network periodically, or collects them when in "consumer" mode. More information can be found in the ruptime(1) and rwho(1) manual pages.