From owner-p4-projects@FreeBSD.ORG Sun Feb 5 19:58:34 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id C4C0B1065675; Sun, 5 Feb 2012 19:58:34 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86863106564A for ; Sun, 5 Feb 2012 19:58:34 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id 6C06C8FC14 for ; Sun, 5 Feb 2012 19:58:34 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id q15JwYUl033019 for ; Sun, 5 Feb 2012 19:58:34 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q15JwXGQ033016 for perforce@freebsd.org; Sun, 5 Feb 2012 19:58:33 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 5 Feb 2012 19:58:33 GMT Message-Id: <201202051958.q15JwXGQ033016@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 205757 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Feb 2012 19:58:35 -0000 http://p4web.freebsd.org/@@205757?ac=10 Change 205757 by rene@rene_acer on 2012/02/05 19:58:29 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/geom/chapter.sgml#11 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#25 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#33 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#128 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/contributing-ports/article.sgml#22 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/contributing/article.sgml#22 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/explaining-bsd/article.sgml#21 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/problem-reports/article.sgml#22 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/solid-state/article.sgml#20 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#76 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/audit/chapter.sgml#16 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/basics/chapter.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.sgml#16 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/book.sgml#21 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/boot/chapter.sgml#14 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/bsdinstall/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/colophon.sgml#5 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/config/chapter.sgml#34 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#50 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml#54 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/disks/chapter.sgml#33 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/dtrace/chapter.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/eresources/chapter.sgml#53 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/filesystems/chapter.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/geom/chapter.sgml#19 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/install/chapter.sgml#34 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/introduction/chapter.sgml#33 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/jails/chapter.sgml#26 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#27 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/l10n/chapter.sgml#22 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.sgml#19 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mac/chapter.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mail/chapter.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.sgml#71 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.sgml#24 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.sgml#52 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/ports/chapter.sgml#27 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/preface/preface.sgml#19 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/printing/chapter.sgml#11 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/serialcomms/chapter.sgml#15 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/users/chapter.sgml#9 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/vinum/chapter.sgml#12 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml#29 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/x11/chapter.sgml#40 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/bibliography.sgml#7 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/glossary/freebsd-glossary.sgml#14 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/trademarks.sgml#7 integrate .. //depot/projects/docproj_nl/www/en/ipv6/Makefile#2 integrate .. //depot/projects/docproj_nl/www/en/ipv6/ipv6.ent#2 integrate .. //depot/projects/docproj_nl/www/en/ipv6/w6l.sgml#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.3R/Makefile#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.3R/docbook.css#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.3R/schedule.sgml#1 branch .. //depot/projects/docproj_nl/www/en/releases/Makefile#9 integrate .. //depot/projects/docproj_nl/www/en/releng/index.sgml#48 integrate .. //depot/projects/docproj_nl/www/nl/index.xsl#23 integrate .. //depot/projects/docproj_nl/www/nl/share/sgml/header.l10n.ent#26 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/geom/chapter.sgml#11 (text+ko) ==== @@ -1,6 +1,6 @@ @@ -44,18 +44,19 @@ - What type of RAID support is available - through GEOM. + What type of RAID support is + available through GEOM. How to use the base utilities to configure, maintain, - and manipulate the various RAID levels. + and manipulate the various RAID + levels. - How to mirror, stripe, encrypt, and remotely connect disk - devices through GEOM. + How to mirror, stripe, encrypt, and remotely connect + disk devices through GEOM. @@ -82,9 +83,9 @@ GEOM Introduction - GEOM permits access and control to classes — Master Boot - Records, BSD labels, etc — through the - use of providers, or the special files in + GEOM permits access and control to classes — Master + Boot Records, BSD labels, etc — through + the use of providers, or the special files in /dev. Supporting various software RAID configurations, GEOM will transparently provide access to the operating system and @@ -115,9 +116,9 @@ Striping - Striping is a method used to combine several disk drives into - a single volume. In many cases, this is done through the use of - hardware controllers. The GEOM disk subsystem provides + Striping is a method used to combine several disk drives + into a single volume. In many cases, this is done through the + use of hardware controllers. The GEOM disk subsystem provides software support for RAID0, also known as disk striping. @@ -144,7 +145,7 @@ - Creating a stripe of unformatted ATA disks + Creating a Stripe of Unformatted ATA Disks Load the geom_stripe.ko @@ -165,8 +166,9 @@ Determine the device names for the disks which will be striped, and create the new stripe device. For example, - to stripe two unused and unpartitioned ATA disks, - for example /dev/ad2 and + to stripe two unused and unpartitioned + ATA disks, for example + /dev/ad2 and /dev/ad3: &prompt.root; gstripe label -v st0 /dev/ad2 /dev/ad3 @@ -186,17 +188,17 @@ This process should have created two other devices in the /dev/stripe - directory in addition to the st0 device. - Those include st0a and - st0c. At this point a file system may be - created on the st0a device with the - newfs utility: + directory in addition to the st0 + device. Those include st0a and + st0c. At this point a file system + may be created on the st0a device + with the newfs utility: &prompt.root; newfs -U /dev/stripe/st0a - Many numbers will glide across the screen, and after a few - seconds, the process will be complete. The volume has been - created and is ready to be mounted. + Many numbers will glide across the screen, and after a + few seconds, the process will be complete. The volume has + been created and is ready to be mounted. @@ -204,10 +206,11 @@ &prompt.root; mount /dev/stripe/st0a /mnt - To mount this striped file system automatically during the boot - process, place the volume information in - /etc/fstab file. For this purpose, a permanent - mount point, named stripe, is + To mount this striped file system automatically during the + boot process, place the volume information in + /etc/fstab file. For this purpose, a + permanent mount point, named + stripe, is created: &prompt.root; mkdir /stripe @@ -215,8 +218,8 @@ >> /etc/fstab The geom_stripe.ko module must also be - automatically loaded during system initialization, by adding a line to - /boot/loader.conf: + automatically loaded during system initialization, by adding a + line to /boot/loader.conf: &prompt.root; echo 'geom_stripe_load="YES"' >> /boot/loader.conf @@ -232,16 +235,17 @@ Mirroring is a technology used by many corporations and home - users to back up data without interruption. When a mirror exists, - it simply means that diskB replicates diskA. Or, perhaps diskC+D - replicates diskA+B. Regardless of the disk configuration, the - important aspect is that information on one disk or partition is - being replicated. Later, that information could be more easily - restored, backed up without causing service or access - interruption, and even be physically stored in a data safe. + users to back up data without interruption. When a mirror + exists, it simply means that diskB replicates diskA. Or, + perhaps diskC+D replicates diskA+B. Regardless of the disk + configuration, the important aspect is that information on one + disk or partition is being replicated. Later, that information + could be more easily restored, backed up without causing service + or access interruption, and even be physically stored in a data + safe. - To begin, ensure the system has two disk drives of equal size, - these exercises assume they are direct access (&man.da.4;) + To begin, ensure the system has two disk drives of equal + size, these exercises assume they are direct access (&man.da.4;) SCSI disks. @@ -317,7 +321,7 @@ :w /etc/fstab.bak. Then replace all old da0 references with gm0 by typing - :%s/da/mirror\/gm/g. + :%s/da/mirror\/gm/g. The resulting fstab file should look @@ -326,14 +330,14 @@ the RAID device will be gm regardless. - # Device Mountpoint FStype Options Dump Pass# -/dev/mirror/gm0s1b none swap sw 0 0 -/dev/mirror/gm0s1a / ufs rw 1 1 -/dev/mirror/gm0s1d /usr ufs rw 0 0 -/dev/mirror/gm0s1f /home ufs rw 2 2 -#/dev/mirror/gm0s2d /store ufs rw 2 2 -/dev/mirror/gm0s1e /var ufs rw 2 2 -/dev/acd0 /cdrom cd9660 ro,noauto 0 0 + # Device Mountpoint FStype Options Dump Pass# +/dev/mirror/gm0s1b none swap sw 0 0 +/dev/mirror/gm0s1a / ufs rw 1 1 +/dev/mirror/gm0s1d /usr ufs rw 0 0 +/dev/mirror/gm0s1f /home ufs rw 2 2 +#/dev/mirror/gm0s2d /store ufs rw 2 2 +/dev/mirror/gm0s1e /var ufs rw 2 2 +/dev/acd0 /cdrom cd9660 ro,noauto 0 0 Reboot the system: @@ -383,7 +387,7 @@ Troubleshooting - System refuses to boot + System Refuses to Boot If the system boots up to a prompt similar to: @@ -399,10 +403,10 @@ OK? load geom_mirror OK? boot - If this works then for whatever reason the module was not - being loaded properly. Check whether the relevant entry in - /boot/loader.conf is correct. If the problem - persists, place: + If this works then for whatever reason the module was + not being loaded properly. Check whether the relevant entry + in /boot/loader.conf is correct. If + the problem persists, place: options GEOM_MIRROR @@ -412,7 +416,7 @@ - Recovering From Disk Failure + Recovering from Disk Failure The wonderful part about disk mirroring is that when a disk fails, it may be replaced, presumably, without losing @@ -505,14 +509,14 @@ prevent the system from booting. One solution to this issue is to chain the - SCSI devices in order so a new device added to - the SCSI card will be issued unused device - numbers. But what about USB devices which may - replace the primary SCSI disk? This happens - because USB devices are usually - probed before the SCSI card. One solution - is to only insert these devices after the system has been - booted. Another method could be to use only a single + SCSI devices in order so a new device added + to the SCSI card will be issued unused device + numbers. But what about USB devices which + may replace the primary SCSI disk? This + happens because USB devices are usually + probed before the SCSI card. One solution is + to only insert these devices after the system has been booted. + Another method could be to use only a single ATA drive and never list the SCSI devices in /etc/fstab. @@ -522,9 +526,9 @@ label their disk devices and use these labels in /etc/fstab. Because glabel stores the label in the last sector of - a given provider, the label will remain persistent across reboots. - By using this label as a device, the file system may always be - mounted regardless of what device node it is accessed + a given provider, the label will remain persistent across + reboots. By using this label as a device, the file system may + always be mounted regardless of what device node it is accessed through. @@ -544,24 +548,26 @@ Permanent labels can be created with the &man.tunefs.8; or &man.newfs.8; commands. They will then be created in a sub-directory of - /dev, which will be named - according to their file system type. For example, + /dev, which will be + named according to their file system type. For example, UFS2 file system labels will be created in - the /dev/ufs - directory. Permanent labels can also be created with the - glabel label command. These are not file system - specific, and will be created in the /dev/label directory. + the /dev/ufs directory. + Permanent labels can also be created with the glabel + label command. These are not file system specific, + and will be created in the + /dev/label + directory. - A temporary label will go away with the next reboot. These - labels will be created in the - /dev/label directory and - are perfect for experimentation. A temporary label can be - created using the glabel create command. For more - information, please read the manual page of &man.glabel.8;. + A temporary label will go away with the next reboot. + These labels will be created in the + /dev/label directory + and are perfect for experimentation. A temporary label can be + created using the glabel create command. + For more information, please read the manual page of + &man.glabel.8;. + or when there is no newfs (e.g.: cd9660)? --> To create a permanent label for a UFS2 file system without destroying any @@ -608,28 +614,29 @@ &prompt.root; glabel destroy home - The following example shows how to label the partitions of a - boot disk. + The following example shows how to label the partitions of + a boot disk. Labeling Partitions on the Boot Disk By permanently labeling the partitions on the boot disk, the system should be able to continue to boot normally, even - if the disk is moved to another controller or transferred - to a different system. For this example, it is assumed that a - single ATA disk is used, which is currently - recognized by the system as ad0. It is - also assumed that the standard &os; partition scheme is used, with + if the disk is moved to another controller or transferred to + a different system. For this example, it is assumed that a + single ATA disk is used, which is + currently recognized by the system as + ad0. It is also assumed that the + standard &os; partition scheme is used, with /, /var, /usr and - /tmp file systems, as well - as a swap partition. + /tmp file systems, as + well as a swap partition. - Reboot the system, and at the &man.loader.8; prompt, press - 4 to boot into single user mode. Then enter the - following commands: + Reboot the system, and at the &man.loader.8; prompt, + press 4 to boot into single user mode. + Then enter the following commands: &prompt.root; glabel label rootfs /dev/ad0s1a GEOM_LABEL: Label for provider /dev/ad0s1a is label/rootfs @@ -643,11 +650,11 @@ GEOM_LABEL: Label for provider /dev/ad0s1b is label/swap &prompt.root; exit - The system will continue with multi-user boot. After the boot - completes, edit /etc/fstab and replace the - conventional device names, with their respective labels. The - final /etc/fstab file will look like the - following: + The system will continue with multi-user boot. After + the boot completes, edit /etc/fstab and + replace the conventional device names, with their respective + labels. The final /etc/fstab file will + look like the following: # Device Mountpoint FStype Options Dump Pass# /dev/label/swap none swap sw 0 0 @@ -656,8 +663,9 @@ /dev/label/usr /usr ufs rw 2 2 /dev/label/var /var ufs rw 2 2 - The system can now be rebooted. If everything went well, it - will come up normally and mount will show: + The system can now be rebooted. If everything went + well, it will come up normally and mount + will show: &prompt.root; mount /dev/label/rootfs on / (ufs, local) @@ -667,16 +675,17 @@ /dev/label/var on /var (ufs, local, soft-updates) - Starting with &os; 7.2, the &man.glabel.8; class supports - a new label type for UFS file systems, based on - the unique file system id, ufsid. These labels may - be found in the /dev/ufsid - directory and are created automatically during system startup. It is - possible to use ufsid labels to mount partitions - using the /etc/fstab facility. Use the - glabel status command to receive a list of - file systems and their corresponding ufsid - labels: + Starting with &os; 7.2, the &man.glabel.8; class + supports a new label type for UFS file + systems, based on the unique file system id, + ufsid. These labels may be found in the + /dev/ufsid directory + and are created automatically during system startup. It is + possible to use ufsid labels to mount + partitions using the /etc/fstab facility. + Use the glabel status command to receive a + list of file systems and their corresponding + ufsid labels: &prompt.user; glabel status Name Status Components @@ -685,10 +694,10 @@ In the above example ad4s1d represents the /var - file system, while ad4s1f represents the - /usr file system. Using the - ufsid values shown, these partitions - may now be mounted with the following entries in + file system, while ad4s1f represents + the /usr file system. + Using the ufsid values shown, these + partitions may now be mounted with the following entries in /etc/fstab: /dev/ufsid/486b6fc38d330916 /var ufs rw 2 2 @@ -724,11 +733,11 @@ system inconsistencies. This method is yet another mechanism to protect against data - loss and inconsistencies of the file system. Unlike Soft Updates - which tracks and enforces meta-data updates and Snapshots which - is an image of the file system, an actual log is stored in disk - space specifically reserved for this task, and in some cases may be - stored on another disk entirely. + loss and inconsistencies of the file system. Unlike Soft + Updates which tracks and enforces meta-data updates and + Snapshots which is an image of the file system, an actual log is + stored in disk space specifically reserved for this task, and in + some cases may be stored on another disk entirely. Unlike other file system journaling implementations, the gjournal method is block based and not @@ -742,8 +751,8 @@ options UFS_GJOURNAL If journaled volumes need to be mounted during startup, the - geom_journal.ko kernel module will also have to be - loaded, by adding the following line in + geom_journal.ko kernel module will also + have to be loaded, by adding the following line in /boot/loader.conf: geom_journal_load="YES" @@ -770,7 +779,8 @@ &prompt.root; newfs -O 2 -J /dev/da4.journal The previously issued command will create a - UFS2 file system on the journaled device. + UFS2 file system on the journaled + device. Effectively mount the device at the desired point with: @@ -780,26 +790,29 @@ In the case of several slices, a journal will be created for each individual slice. For instance, if - ad4s1 and ad4s2 - are both slices, then gjournal will create + ad4s1 and + ad4s2 are both slices, then + gjournal will create ad4s1.journal and ad4s2.journal. For better performance, keeping the journal on another disk - may be desired. For these cases, the journal provider or storage - device should be listed after the device to enable journaling - on. Journaling may also be enabled on current file systems by - using tunefs; however, always make a backup - before attempting to alter a file system. In most cases, the - gjournal will fail if it is unable to create - the actual journal but this does not protect against data loss - incurred as a result of misusing tunefs. + may be desired. For these cases, the journal provider or + storage device should be listed after the device to enable + journaling on. Journaling may also be enabled on current file + systems by using tunefs; however, always make + a backup before attempting to alter a file system. In most + cases, the gjournal will fail if it is unable + to create the actual journal but this does not protect against + data loss incurred as a result of misusing + tunefs. - It is also possible to journal the boot disk of a &os; system. - Please refer to the article Implementing UFS Journaling on - a Desktop PC for detailed instructions on this task. + It is also possible to journal the boot disk of a &os; + system. Please refer to the article Implementing UFS + Journaling on a Desktop PC for detailed instructions + on this task. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#25 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -618,9 +618,9 @@ version with the architecture and the version number which you want to install, respectively. For example, the memory stick - images for &os;/&arch.i386; &rel.current;-RELEASE are + images for &os;/&arch.i386; &rel2.current;-RELEASE are available from . + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img">. The memory stick image has a .img extension. The - &prompt.root; dd if=&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k + &prompt.root; dd if=&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k If an Operation not permitted ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#33 (text+ko) ==== @@ -1,14 +1,14 @@ - Murray + Murray Stokely Reorganized by @@ -46,7 +46,8 @@ - How to set up automatic network settings using DHCP. + How to set up automatic network settings using + DHCP. @@ -54,11 +55,13 @@ - How to set up the Apache HTTP Server. + How to set up the Apache + HTTP Server. - How to set up a File Transfer Protocol (FTP) Server. + How to set up a File Transfer Protocol (FTP) + Server. @@ -92,8 +95,8 @@ - Know how to install additional third-party - software (). + Know how to install additional third-party + software (). @@ -102,11 +105,11 @@ - - Chern - Lee - Contributed by - + + Chern + Lee + Contributed by + @@ -116,22 +119,24 @@ - The <application>inetd</application> <quote>Super-Server</quote> + The <application>inetd</application> + <quote>Super-Server</quote> Overview - &man.inetd.8; is sometimes referred to as the Internet - Super-Server because it manages connections for - several services. When a - connection is received by inetd, it - determines which program the connection is destined for, spawns - the particular process and delegates the socket to it (the program - is invoked with the service socket as its standard input, output - and error descriptors). Running - inetd for servers that are not heavily used can reduce the - overall system load, when compared to running each daemon - individually in stand-alone mode. + &man.inetd.8; is sometimes referred to as the + Internet Super-Server because it manages + connections for several services. When a connection is + received by inetd, it determines + which program the connection is destined for, spawns the + particular process and delegates the socket to it (the program + is invoked with the service socket as its standard input, + output and error descriptors). Running + inetd for servers that are not + heavily used can reduce the overall system load, when compared + to running each daemon individually in stand-alone + mode. Primarily, inetd is used to spawn other daemons, but several trivial protocols are handled @@ -156,11 +161,11 @@ depending on the configuration chosen by the user. Placing: - inetd_enable="YES" + inetd_enable="YES" or - inetd_enable="NO" + inetd_enable="NO" into /etc/rc.conf will enable or disable @@ -182,26 +187,24 @@ Like most server daemons, inetd has a number of options that it can be passed in order to - modify its behaviour. The full list of options reads: + modify its behaviour. See the &man.inetd.8; manual page for + the full list of options. - inetd - - Options can be passed to inetd using the - inetd_flags option in + Options can be passed to inetd + using the inetd_flags option in /etc/rc.conf. By default, inetd_flags is set to -wW -C 60, which turns on TCP wrapping for inetd's services, and prevents any - single IP address from requesting any service more than 60 times - in any given minute. + single IP address from requesting any service more than 60 + times in any given minute. Although we mention rate-limiting options below, novice users may be pleased to note that these parameters usually do - not need to be modified. These options may be useful should you - find that you are receiving an excessive amount of connections. - A full list of options can be found in the &man.inetd.8; - manual. + not need to be modified. These options may be useful should + you find that you are receiving an excessive amount of + connections. A full list of options can be found in the + &man.inetd.8; manual. @@ -221,8 +224,8 @@ Specify the default maximum number of times a service can be invoked from a single IP address in one - minute; the default is unlimited. May be overridden on a - per-service basis with the + minute; the default is unlimited. May be overridden on + a per-service basis with the parameter. @@ -244,9 +247,9 @@ Specify the maximum number of times a service can be invoked from a single IP address at any one time; the - default is unlimited. May be overridden on a per-service - basis with the - parameter. + default is unlimited. May be overridden on a + per-service basis with the + parameter. @@ -266,7 +269,7 @@ Reloading the <application>inetd</application> - configuration file + Configuration File &prompt.root; /etc/rc.d/inetd reload @@ -382,22 +385,24 @@ using the option. If a limit of ten instances of a particular daemon is needed, a /10 would be placed after - . Specifying /0 - allows an unlimited number of children + . Specifying + /0 allows an unlimited number of + children In addition to , two other - options which limit the maximum connections from a single - place to a particular daemon can be enabled. - limits - the number of connections from any particular IP address - per minutes, e.g. a value of ten would limit any particular - IP address connecting to a particular service to ten - attempts per minute. - limits the number of children that can be started on - behalf on any single IP address at any moment. These - options are useful to prevent intentional or unintentional - excessive resource consumption and Denial of Service (DoS) - attacks to a machine. + options which limit the maximum connections from a + single place to a particular daemon can be enabled. + + limits the number of connections from any particular IP + address per minutes, e.g., a value of ten would limit + any particular IP address connecting to a particular + service to ten attempts per minute. + limits the number of + children that can be started on behalf on any single IP + address at any moment. These options are useful to + prevent intentional or unintentional excessive resource + consumption and Denial of Service (DoS) attacks to a + machine. In this field, either of or is mandatory. @@ -439,10 +444,10 @@ This is the username that the particular daemon should run as. Most commonly, daemons run as the - root user. For security purposes, it is - common to find some servers running as the - daemon user, or the least privileged - nobody user. + root user. For security purposes, + it is common to find some servers running as the + daemon user, or the least + privileged nobody user. @@ -482,26 +487,28 @@ Depending on the choices made at install time, many of inetd's services may be enabled by default. If there is no apparent need for a particular - daemon, consider disabling it. Place a # in front of the - daemon in question in /etc/inetd.conf, - and then reload the + daemon, consider disabling it. Place a # in + front of the daemon in question in + /etc/inetd.conf, and then reload the inetd configuration. Some daemons, such as fingerd, may not be desired at all because they provide information that may be useful to an attacker. Some daemons are not security-conscious and have long, or - non-existent, timeouts for connection attempts. This allows an - attacker to slowly send connections to a particular daemon, + non-existent, timeouts for connection attempts. This allows + an attacker to slowly send connections to a particular daemon, thus saturating available resources. It may be a good idea to place , - or limitations on certain + or + limitations on certain daemons if you find that you have too many connections. By default, TCP wrapping is turned on. Consult the - &man.hosts.access.5; manual page for more information on placing - TCP restrictions on various inetd - invoked daemons. + &man.hosts.access.5; manual page for more information on + placing TCP restrictions on various + inetd invoked daemons. @@ -518,7 +525,8 @@ The auth service provides identity network services, and is - configurable to a certain degree, whilst the others are simply on or off. + configurable to a certain degree, whilst the others are simply + on or off. Consult the &man.inetd.8; manual page for more in-depth information. @@ -528,18 +536,18 @@ - - Tom - Rhodes - Reorganized and enhanced by - + + Tom + Rhodes + Reorganized and enhanced by + - - Bill - Swingle + + Bill + Swingle Written by - + Network File System (NFS) @@ -573,9 +581,9 @@ Storage devices such as floppy disks, CDROM drives, and - &iomegazip; drives can be used by other machines on the network. - This may reduce the number of removable media drives - throughout the network. + &iomegazip; drives can be used by other machines on the + network. This may reduce the number of removable media + drives throughout the network. @@ -583,29 +591,29 @@ How <acronym>NFS</acronym> Works NFS consists of at least two main - parts: a server and one or more clients. The client remotely - accesses the data that is stored on the server machine. In - order for this to function properly a few processes have to be - configured and running. + parts: a server and one or more clients. The client remotely + accesses the data that is stored on the server machine. In + order for this to function properly a few processes have to be + configured and running. The server has to be running the following daemons: - NFS - server + NFS + server - file server - UNIX clients + file server + UNIX clients rpcbind - mountd + mountd - nfsd + nfsd @@ -623,91 +631,91 @@ nfsd The NFS daemon which services - requests from the NFS - clients. + requests from the NFS + clients. mountd - The NFS mount daemon which carries out - the requests that &man.nfsd.8; passes on to it. + The NFS mount daemon which + carries out the requests that &man.nfsd.8; passes on + to it. rpcbind This daemon allows >>> TRUNCATED FOR MAIL (1000 lines) <<<