# HG changeset patch # User Giorgos Keramidas # Date 1363092720 -3600 # Tue Mar 12 13:52:00 2013 +0100 # Node ID 71ac600c3326ad78728be96848e6e667e08eddc3 # Parent 57023da207c5e46cfe939296148a8bdae4bfd5a2 Mark directory paths with class="directory" in elements. diff -r 57023da207c5 -r 71ac600c3326 en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Tue Mar 12 13:23:34 2013 +0100 +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Tue Mar 12 13:52:00 2013 +0100 @@ -1274,7 +1274,7 @@ Then we can bring up the interface: - &prompt.root; service netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6 @@ -2189,8 +2189,8 @@ can enable debugging messages in the 802.11 protocol support layer using the wlandebug program found in - /usr/src/tools/tools/net80211. For - example: + /usr/src/tools/tools/net80211. + For example: &prompt.root; wlandebug -i ath0 +scan+auth+debug+assoc net.wlan.0.debug: 0 => 0xc80000<assoc,auth,scan> @@ -2760,7 +2760,8 @@ In order to provide OBEX Object Push service, &man.sdpd.8; server must be running. A root folder, where all incoming objects will be stored, must be created. The default path to - the root folder is /var/spool/obex. + the root folder + is /var/spool/obex. Finally, start OBEX server on valid RFCOMM channel number. The OBEX server will automatically register OBEX Object Push service with the local SDP daemon. The example below shows @@ -3689,9 +3690,9 @@ - Standard system startup files exist in - /etc to detect and support a diskless - system startup. + Standard system startup files exist + in /etc + to detect and support a diskless system startup. @@ -3710,8 +3711,9 @@ The diskless workstations use a shared read-only - / file system, and a shared - read-only /usr. + / file system, + and a shared read-only + /usr. The root file system is a copy of a standard FreeBSD root (typically the server's), with some configuration files @@ -4034,8 +4036,9 @@ To make a boot floppy, insert a floppy in the drive on the machine where you installed Etherboot, then change your - current directory to the src directory - in the Etherboot tree and + current directory to + the src + directory in the Etherboot tree and type: &prompt.root; gmake bin32/devicetype.fd0 @@ -4093,7 +4096,7 @@ Create a directory from which tftpd will serve the files, - e.g., /tftpboot. + e.g., /tftpboot. @@ -4123,7 +4126,8 @@ - You can place the tftpboot + You can place + the tftpboot directory anywhere on the server. Make sure that the location is set in both inetd.conf and dhcpd.conf. @@ -4286,7 +4290,7 @@ Running with a Read-only - <filename>/usr</filename> + /usr diskless operation @@ -4296,7 +4300,8 @@ If the diskless workstation is configured to run X, you will have to adjust the XDM configuration file, which - puts the error log on /usr by + puts the error log + on /usr by default. @@ -4310,7 +4315,8 @@ cpio. In this situation, there are sometimes problems with - the special files in /dev, due to + the special files + in /dev, due to differing major/minor integer sizes. A solution to this problem is to export a directory from the non-FreeBSD server, mount this directory onto a FreeBSD machine, and @@ -4370,7 +4376,7 @@ Choose a directory which will have a &os; installation which will be NFS mountable. For example, a directory such as - /b/tftpboot/FreeBSD/install can be + /b/tftpboot/FreeBSD/install can be used. &prompt.root; export NFSROOTDIR=/b/tftpboot/FreeBSD/install @@ -4500,8 +4506,10 @@ /etc/rc detects that you booted over NFS and runs the /etc/rc.initdiskless script. Read the comments in this script to understand what is going - on. We need to make /etc and - /var memory backed file systems because + on. We need to + make /etc + and /var + memory backed file systems because these directories need to be writable, but the NFS root directory is read-only. @@ -4510,8 +4518,9 @@ &prompt.root; tar -c -v -f conf/base/etc.cpio.gz --format cpio --gzip etc &prompt.root; tar -c -v -f conf/base/var.cpio.gz --format cpio --gzip var - When the system boots, memory file systems for - /etc and /var will + When the system boots, memory file systems + for /etc + and /var will be created and mounted, and the contents of the cpio.gz files will be copied into them.