From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 00:10:46 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCDBC5C8; Sun, 26 Jan 2014 00:10:46 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9D48C14FF; Sun, 26 Jan 2014 00:10:46 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0Q0Ak1T095968; Sun, 26 Jan 2014 00:10:46 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0Q0Akfm095967; Sun, 26 Jan 2014 00:10:46 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401260010.s0Q0Akfm095967@svn.freebsd.org> From: Warren Block Date: Sun, 26 Jan 2014 00:10:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43644 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 00:10:46 -0000 Author: wblock Date: Sun Jan 26 00:10:46 2014 New Revision: 43644 URL: http://svnweb.freebsd.org/changeset/doc/43644 Log: Minor punctuation and spelling fixes, add ASCII cat pictures. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml Sat Jan 25 20:00:48 2014 (r43643) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml Sun Jan 26 00:10:46 2014 (r43644) @@ -18,7 +18,7 @@

The last quarter of 2013 was very active for the &os; community, much like the preceding quarters. Many advances were made in getting &os; to run on ARM-based System-on-Chip boards - like Cubieboard, Rockchip, Snapdragon, S4, Freescale i.MX6 and + like Cubieboard, Rockchip, Snapdragon, S4, Freescale i.MX6, and Vybrid VF6xx. &os; is also becoming a better platform for Xen and the Amazon Elastic Compute Cloud. There are plans for &os; to become a fully supported compute host for OpenStack. The I/O @@ -434,8 +434,8 @@

The i.MX range is a family of Freescale Semiconductor proprietary microprocessors for multimedia applications based on - the ARM architecture and focused on low-power consumption. The - i.MX6x series is based on the ARM Cortex A9 solo, dual or quad + the ARM architecture and focused on low power consumption. The + i.MX6x series is based on the ARM Cortex A9 solo, dual, or quad cores. Initial support for them has been committed to head, and merged to stable/10. All members of the i.MX6 family (Solo, Dual, and Quad core) are supported, but @@ -620,7 +620,7 @@ of context switches.

Thanks to these cam(4) and geom(4) changes, - the peak I/O rate has doubled on comptemporary hardware, reaching + the peak I/O rate has doubled on contemporary hardware, reaching up to 1,000,000 IOPS!

@@ -710,9 +710,9 @@

The devel/py-distribute port has been replaced by the refreshed devel/py-setuptools port, which comes with a - lot of features that simplify the ways of installing Python + lot of features that simplify the methods of installing Python packages. The change also led us to install everything through - Setuptools now, which resembles a PyIP a bit and allows us to + Setuptools now, which resembles PyIP a bit and allows us to perform some major cleanup on the distutils installation behaviour.

@@ -975,8 +975,8 @@ Ports Collection, thanks to the efforts of Jeremy Messenger. MATE is a desktop environment forked from the now-unmaintained code base of GNOME 2, therefore it is basically a - replacement for GNOME 2. It recommended for users wanting - to keep GNOME 2 as their desktop to switch since + replacement for GNOME 2. Users wanting + to keep GNOME 2 as their desktop are advised to switch to MATE since GNOME 2 will be replaced by GNOME 3 in the near future. This switch will be announced in advance, so people will have time to move to MATE if they have not already. The @@ -998,7 +998,7 @@ GNOME 2 ports still need to be sorted out to evaluate which GNOME 2 components will be gone or be replaced with - their newer GNOME 3 versions. This task is current halted + their newer GNOME 3 versions. This task is currently halted until we can get the documentation into a shape good enough to gather the issues and document the migration, including how to avoid the migration if the upgrade is not preferred. (This @@ -1031,7 +1031,7 @@ from the Intel team, and introduce support for the newest hardware — in particular Haswell and ValleyView. The IvyBridge code will also be updated. The addition of several - features, which are required in order to update X.Org and Mesa, + features which are required to update X.Org and Mesa is also planned.

@@ -1169,7 +1169,7 @@ -

At the November 2013 &os; Vendor Summit, some of the work was +

At the November 2013 &os; Vendor Summit, some work was presented that Craig Rodrigues has been doing with Continuous Integration and Testing at iXsystems. Craig's presentation described how iXsystems is using modern best practices for @@ -1244,14 +1244,14 @@ change noticed.

To better manage changes such as the WITH_NEW_XORG and - Cairo 1.12 changes mentioned above, we asked on the + the Cairo 1.12 changes mentioned above, we asked on the freebsd-x11 mailing-list if people are using &os; 8.x on their desktop computers and why they do not upgrade to &os; 9.x or 10.x. So far, we received very few answers to this.

The Radeon KMS driver in &os; 10.x is now considered - stable, especially that integrated GPUs are now properly + stable, especially now that integrated GPUs are properly initialized. One of the next steps will be to merge this to stable/9.

@@ -1342,11 +1342,11 @@ replacement for the existing, quite old, virtual terminal emulator called syscons(4). Initially motivated by the lack of Unicode support in syscons(4), the project was - later expanded to cover the new requirement to support Kernel + later expanded to cover the new requirement of supporting Kernel Mode Switching (KMS).

The project is now approaching completion and is ready for - wider testing as the related code was already merged to &os; + wider testing, as the related code was already merged to &os; head. Hence, vt(9) can be tested easily by replacing the following two lines in the kernel config file:

@@ -1378,7 +1378,7 @@ device vt_vga
  • i386 (VGA/i915kms/radeonkms) — works.
  • IA64 — untested.
  • MIPS — untested.
    • -
  • PPC and PPC64 — Works, but without X.Org yet.
    • +
  • PPC and PPC64 — works, but without X.Org yet.
  • SPARC — works on certain hardware (e.g., Ultra 5).
  • vesa(4) — in progress.
  • i386/amd64 nVidia driver — need testing.
    • @@ -1469,7 +1469,7 @@ device vt_vga

    The auditdistd(8) daemon is responsible for - distributing audit trail files over TCP/IP network securely and + distributing audit trail files over TCP/IP networks securely and reliably. Currently, the daemon uses Transport Layer Security (TLS) for communication, but only server-side certificates are verified, based on the certificate's fingerprint. The ongoing @@ -1518,13 +1518,13 @@ device vt_vga

    The &os; Port Management Team ensures that the &os; ports developer community provides a Ports Collection that is - functional, stable, up-to-date and full-featured. Its secondary + functional, stable, up-to-date, and full-featured. Its secondary responsibility is to coordinate among the committers and - developers who work on it. As part of these efforts, we added 3 - new committers, took in 3 commit bits for safe keeping, and - reinstated 1 commit bit in the fourth quarter of 2013.

    + developers who work on it. As part of these efforts, we added three + new committers, took in three commit bits for safe keeping, and + reinstated one commit bit in the fourth quarter of 2013.

    -

    Ongoing effort went into testing larger changes, as many as 8 a +

    Ongoing effort went into testing larger changes, as many as eight a week, including sweeping changes to the tree, moderization of the infrastructure, and basic quality assurance (QA) runs. Many iterations of tests against 10.0-RELEASE were run to @@ -1746,7 +1746,7 @@ device vt_vga

    Support in improving the experience of Wine on &os; is needed. Key areas including fixing regressions, adding copy protection - scheme support and fixing regressions when using Wine under + scheme support, and fixing regressions when using Wine under &os;/amd64.

    @@ -1782,7 +1782,7 @@ device vt_vga KDE/&os; Team have continued to improve the experience of KDE software and Qt under &os;.

    -

    During last quarter, the team has kept most of the KDE and Qt +

    During the last quarter, the team has kept most of the KDE and Qt ports up-to-date, working on the following releases:

      @@ -1803,7 +1803,7 @@ device vt_vga long time and we are very grateful for that.

      As usual, the team is always looking for more testers and - porters so please contact us or visit our home page (see links). + porters, so please contact us or visit our home page (see links). It would be especially useful to have more helping hands on tasks such as getting rid of the dependency on the defunct HAL project and providing integration with KDE's Bluedevil Bluetooth @@ -1861,12 +1861,12 @@ device vt_vga &os; 10.x.

      It was a busy quarter for the src repository as well. The Core - Team was happy to welcome Jordan K. Hubbard (jkh) back + Team was happy to welcome Jordan K. Hubbard (jkh) back, who has recently returned to the &os; business, and joined iXsystems as project manager and release engineer of FreeNAS. - In addition to this, there were 3 commit bits offered for new - developers, 2 committers were upgraded, 1 commit bit was taken - for safekeeping, and 1 src bit was reactivated.

      + In addition to this, there were three commit bits offered for new + developers, two committers were upgraded, one commit bit was taken + for safekeeping, and one src bit was reactivated.

      @@ -1887,8 +1887,8 @@ device vt_vga

      The GCC compiler in the &os; base system is on its way to deprecation and is only used by some Tier-2 platforms at this time. While Clang is much better in many aspects, we still - cannot use in the base system all the new features that it - brings until we can drop GCC completely. As a stop-gap + cannot use all the new features that it + brings in the base system until we can drop GCC completely. As a stop-gap solution, several bug fixes and features from Apple GCC and other sources have been ported to our version of GCC 4.2.1 to make it more compatible with Clang. &os;'s GCC has added @@ -2090,9 +2090,9 @@ device vt_vga I/O. Otherwise it uses hardware virtualization extensions, without the need for emulation.

      -

      After merging the changes in order to improve Xen PVHVM +

      After merging the changes to improve Xen PVHVM support, work has shifted on getting PVH DomU support on &os;. - Patches have been posted, and after a couple of rounds of review + Patches have been posted, and after a couple of rounds of review, the series looks almost ready for merging into head. Also, very initial patches for &os; PVH Dom0 support has been posted. So far the posted series only focuses on getting &os; From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 02:30:34 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA17BEF4; Sun, 26 Jan 2014 02:30:34 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D4B021E25; Sun, 26 Jan 2014 02:30:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0Q2UYu2092496; Sun, 26 Jan 2014 02:30:34 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0Q2UYPh092495; Sun, 26 Jan 2014 02:30:34 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401260230.s0Q2UYPh092495@svn.freebsd.org> From: Warren Block Date: Sun, 26 Jan 2014 02:30:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43645 - head/en_US.ISO8859-1/books/arch-handbook/boot X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 02:30:35 -0000 Author: wblock Date: Sun Jan 26 02:30:34 2014 New Revision: 43645 URL: http://svnweb.freebsd.org/changeset/doc/43645 Log: Rewrite of portions of the Boot chapter by Sergio Andrés Gómez del Real. Committed version is a modified version of the one submitted with the patch. Thanks to Sergio Andrés Gómez del Real for the submission, to John-Mark Gurney for technical review, and to both for their patience. PR: docs/185780 Submitted by: Sergio Andrés Gómez del Real Reviewed by: jmg Modified: head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Sun Jan 26 00:10:46 2014 (r43644) +++ head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Sun Jan 26 02:30:34 2014 (r43645) @@ -4,6 +4,8 @@ The FreeBSD Documentation Project Copyright (c) 2002 Sergey Lyubka All rights reserved +Copyright (c) 2014 Sergio Andr?s G?mez del Real +All rights reserved $FreeBSD$ --> @@ -25,6 +27,18 @@ $FreeBSD$ + + + + + Sergio Andrés + Gómez del Real + + + Updated and enhanced by + + + @@ -37,88 +51,103 @@ $FreeBSD$ booting system initialization This chapter is an overview of the boot and system - initialization process, starting from the BIOS (firmware) POST, - to the first user process creation. Since the initial steps of - system startup are very architecture dependent, the IA-32 - architecture is used as an example. + initialization processes, starting from the BIOS (firmware) + POST, to the first user process creation. Since the initial + steps of system startup are very architecture dependent, the + IA-32 architecture is used as an example. + + The &os; boot process can be surprisingly complex. After + control is passed from the BIOS, a considerable amount of + low-level configuration must be done before the kernel can be + loaded and executed. This setup must be done in a simple and + flexible manner, allowing the user a great deal of customization + possibilities. Overview - A computer running FreeBSD can boot by several methods, - although the most common method, booting from a harddisk where - the OS is installed, will be discussed here. The boot process - is divided into several steps: - - - BIOS POST - boot0 stage - boot2 stage - loader stage - kernel initialization - + The boot process is an extremely machine-dependent + activity. Not only must code be written for every computer + architecture, but there may also be multiple types of booting on + the same architecture. For example, looking at + /usr/sys/src/boot + reveals a great amount of architecture-dependent code. There is + a directory for each of the various supported architectures. In + the x86-specific i386 + directory, there are subdirectories for different boot standards + like mbr (Master Boot Record), + gpt (GUID Partition + Table), and efi (Extensible Firmware + Interface). Each boot standard has its own conventions and data + structures. The example that follows shows booting an x86 + computer from an MBR hard drive with the &os; + boot0 multi-boot loader stored in the very + first sector. That boot code starts the &os; three-stage boot + process. + + The key to understanding this process is that it is a series + of stages of increasing complexity. These stages are + boot1, boot2, and + loader (see &man.boot.8; for more detail). + The boot system executes each stage in sequence. The last + stage, loader, is responsible for loading + the &os; kernel. Each stage is examined in the following + sections. - BIOS POST - boot0 - boot2 - loader - The boot0 and boot2 - stages are also referred to as bootstrap stages 1 and - 2 in &man.boot.8; as the first steps in FreeBSD's - 3-stage bootstrapping procedure. Various information is printed - on the screen at each stage, so you may visually recognize them - using the table that follows. Please note that the actual data + Here is an example of the output generated by the + different boot stages. Actual output may differ from machine to machine: - Output (may vary) - BIOS (firmware) messages + &os; Component + Output (may vary) - F1 FreeBSD + boot0 + F1 FreeBSD F2 BSD -F5 Disk 2 - boot0 +F5 Disk 2 - >>FreeBSD/i386 BOOT -Default: 1:ad(1,a)/boot/loader -boot: - boot2 + boot2 This prompt will appear if the user presses a key just after selecting an OS to boot at the boot0 - stage. + stage. + >>FreeBSD/i386 BOOT +Default: 1:ad(1,a)/boot/loader +boot: - BTX loader 1.0 BTX version is 1.01 -BIOS drive A: is disk0 -BIOS drive C: is disk1 -BIOS 639kB/64512kB available memory -FreeBSD/i386 bootstrap loader, Revision 0.8 + loader + BTX loader 1.00 BTX version is 1.02 +Consoles: internal video/keyboard +BIOS drive C: is disk0 +BIOS 639kB/2096064kB available memory + +FreeBSD/x86 bootstrap loader, Revision 1.1 Console internal video/keyboard -(jkh@bento.freebsd.org, Mon Nov 20 11:41:23 GMT 2000) -/kernel text=0x1234 data=0x2345 syms=[0x4+0x3456] -Hit [Enter] to boot immediately, or any other key for command prompt -Booting [kernel] in 9 seconds..._ - loader +(root@snap.freebsd.org, Thu Jan 16 22:18:05 UTC 2014) +Loading /boot/defaults/loader.conf +/boot/kernel/kernel text=0xed9008 data=0x117d28+0x176650 syms=[0x8+0x137988+0x8+0x1515f8] - Copyright (c) 1992-2002 The FreeBSD Project. + kernel + Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. -FreeBSD 4.6-RC #0: Sat May 4 22:49:02 GMT 2002 - devnull@kukas:/usr/obj/usr/src/sys/DEVNULL -Timecounter "i8254" frequency 1193182 Hz - kernel +FreeBSD is a registered trademark of The FreeBSD Foundation. +FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 + root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 +FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 @@ -126,84 +155,114 @@ Timecounter "i8254" frequency 1193182 H - BIOS POST + The <acronym>BIOS</acronym> - When the PC powers on, the processor's registers are set - to some predefined values. One of the registers is the + When the computer powers on, the processor's registers are + set to some predefined values. One of the registers is the instruction pointer register, and its value after a power on is well defined: it is a 32-bit value of - 0xfffffff0. The instruction pointer register points to code to - be executed by the processor. One of the registers is the + 0xfffffff0. The instruction pointer register + (also known as the Program Counter) points to code to be + executed by the processor. Another important register is the cr0 32-bit control register, and its value - just after the reboot is 0. One of the cr0's bits, the bit PE - (Protection Enabled) indicates whether the processor is running - in protected or real mode. Since at boot time this bit is - cleared, the processor boots in real mode. Real mode means, + just after a reboot is 0. One of + cr0's bits, the PE (Protection Enabled) bit, + indicates whether the processor is running in 32-bit protected + mode or 16-bit real mode. Since this bit is cleared at boot + time, the processor boots in 16-bit real mode. Real mode means, among other things, that linear and physical addresses are - identical. - - The value of 0xfffffff0 is slightly less then 4Gb, so unless - the machine has 4Gb physical memory, it cannot point to a valid - memory address. The computer's hardware translates this address - so that it points to a BIOS memory block. - - BIOS stands for Basic Input Output - System, and it is a chip on the motherboard that - has a relatively small amount of read-only memory (ROM). This + identical. The reason for the processor not to start + immediately in 32-bit protected mode is backwards compatibility. + In particular, the boot process relies on the services provided + by the BIOS, and the BIOS + itself works in legacy, 16-bit code. + + The value of 0xfffffff0 is slightly less + than 4 GB, so unless the machine has 4 GB of physical + memory, it cannot point to a valid memory address. The + computer's hardware translates this address so that it points to + a BIOS memory block. + + The BIOS (Basic Input Output + System) is a chip on the motherboard that has a relatively small + amount of read-only memory (ROM). This memory contains various low-level routines that are specific to - the hardware supplied with the motherboard. So, the processor - will first jump to the address 0xfffffff0, which really resides - in the BIOS's memory. Usually this address contains a jump - instruction to the BIOS's POST routines. - - POST stands for Power On Self Test. - This is a set of routines including the memory check, system bus - check and other low-level stuff so that the CPU can initialize - the computer properly. The important step on this stage is - determining the boot device. All modern BIOS's allow the boot - device to be set manually, so you can boot from a floppy, - CD-ROM, harddisk etc. - - The very last thing in the POST is the INT - 0x19 instruction. That instruction reads 512 bytes - from the first sector of boot device into the memory at address - 0x7c00. The term first sector originates - from harddrive architecture, where the magnetic plate is divided - to a number of cylindrical tracks. Tracks are numbered, and - every track is divided by a number (usually 64) sectors. Track - number 0 is the outermost on the magnetic plate, and sector 1, - the first sector (tracks, or, cylinders, are numbered starting - from 0, but sectors - starting from 1), has a special meaning. - It is also called Master Boot Record, or MBR. The remaining - sectors on the first track are never used Some - utilities such as &man.disklabel.8; may store the - information in this area, mostly in the second - sector.. + the hardware supplied with the motherboard. The processor will + first jump to the address 0xfffffff0, which really resides in + the BIOS's memory. Usually this address + contains a jump instruction to the BIOS's + POST routines. + + The POST (Power On Self Test) + is a set of routines including the memory check, system bus + check, and other low-level initialization so the + CPU can set up the computer properly. The + important step of this stage is determining the boot device. + Modern BIOS implementations permit the + selection of a boot device, allowing booting from a floppy, + CD-ROM, hard disk, or other devices. + + The very last thing in the POST is the + INT 0x19 instruction. The + INT 0x19 handler reads 512 bytes from the + first sector of boot device into the memory at address + 0x7c00. The term + first sector originates from hard drive + architecture, where the magnetic plate is divided into a number + of cylindrical tracks. Tracks are numbered, and every track is + divided into a number (usually 64) of sectors. Track numbers + start at 0, but sector numbers start from 1. Track 0 is the + outermost on the magnetic plate, and sector 1, the first sector, + has a special purpose. It is also called the + MBR, or Master Boot Record. The remaining + sectors on the first track are never used. + + This sector is our boot-sequence starting point. As we will + see, this sector contains a copy of our + boot0 program. A jump is made by the + BIOS to address 0x7c00 so + it starts executing. - <literal>boot0</literal> Stage + The Master Boot Record (<literal>boot0</literal>) MBR - Take a look at the file /boot/boot0. - This is a small 512-byte file, and it is exactly what FreeBSD's - installation procedure wrote to your harddisk's MBR if you chose - the bootmanager option at installation - time. + + After control is received from the BIOS + at memory address 0x7c00, + boot0 starts executing. It is the first + piece of code under &os; control. The task of + boot0 is quite simple: scan the partition + table and let the user choose which partition to boot from. The + Partition Table is a special, standard data structure embedded + in the MBR (hence embedded in + boot0) describing the four standard PC + partitions + + . + boot0 resides in the filesystem as + /boot/boot0. It is a small 512-byte file, + and it is exactly what &os;'s installation procedure wrote to + the hard disk's MBR if you chose the bootmanager + option at installation time. Indeed, + boot0 is the + MBR. As mentioned previously, the INT 0x19 - instruction loads an MBR, i.e., the boot0 - content, into the memory at address 0x7c00. Taking a look at - the file sys/boot/i386/boot0/boot0.S can - give a guess at what is happening there - this is the boot - manager, which is an awesome piece of code written by Robert - Nordier. - - The MBR, or, boot0, has a special - structure starting from offset 0x1be, called the - partition table. It has 4 records of 16 - bytes each, called partition records, which - represent how the harddisk(s) are partitioned, or, in FreeBSD's + instruction causes the INT 0x19 handler to + load an MBR (boot0) into + memory at address 0x7c00. The source file + for boot0 can be found in + sys/boot/i386/boot0/boot0.S - which is an + awesome piece of code written by Robert Nordier. + + A special structure starting from offset + 0x1be in the MBR is called + the partition table. It has four records + of 16 bytes each, called partition records, + which represent how the hard disk is partitioned, or, in &os;'s terminology, sliced. One byte of those 16 says whether a partition (slice) is bootable or not. Exactly one record must have that flag set, otherwise boot0's code @@ -229,186 +288,1471 @@ Timecounter "i8254" frequency 1193182 H - A partition record descriptor has the information about + A partition record descriptor contains information about where exactly the partition resides on the drive. Both - descriptors, LBA and CHS, describe the same information, but in - different ways: LBA (Logical Block Addressing) has the starting - sector for the partition and the partition's length, while CHS - (Cylinder Head Sector) has coordinates for the first and last - sectors of the partition. - - The boot manager scans the partition table and prints the - menu on the screen so the user can select what disk and what - slice to boot. By pressing an appropriate key, - boot0 performs the following - actions: + descriptors, LBA and CHS, + describe the same information, but in different ways: + LBA (Logical Block Addressing) has the + starting sector for the partition and the partition's length, + while CHS (Cylinder Head Sector) has + coordinates for the first and last sectors of the partition. + The partition table ends with the special signature + 0xaa55. + + The MBR must fit into 512 bytes, a single + disk sector. This program uses low-level tricks + like taking advantage of the side effects of certain + instructions and reusing register values from previous + operations to make the most out of the fewest possible + instructions. Care must also be taken when handling the + partition table, which is embedded in the MBR + itself. For these reasons, be very careful when modifying + boot0.S. + + Note that the boot0.S source file + is assembled as is: instructions are translated + one by one to binary, with no additional information (no + ELF file format, for example). This kind of + low-level control is achieved at link time through special + control flags passed to the linker. For example, the text + section of the program is set to be located at address + 0x600. In practice this means that + boot0 must be loaded to memory address + 0x600 in order to function properly. + + It is worth looking at the Makefile for + boot0 + (sys/boot/i386/boot0/Makefile), as it + defines some of the run-time behavior of + boot0. For instance, if a terminal + connected to the serial port (COM1) is used for I/O, the macro + SIO must be defined + (-DSIO). -DPXE enables + boot through PXE by pressing + F6. Additionally, the program defines a set of + flags that allow further modification of + its behavior. All of this is illustrated in the + Makefile. For example, look at the + linker directives which command the linker to start the text + section at address 0x600, and to build the + output file as is (strip out any file + formatting): + +

      + <filename>sys/boot/i386/boot0/Makefile</filename> + + BOOT_BOOT0_ORG?=0x600 + LDFLAGS=-e start -Ttext ${BOOT_BOOT0_ORG} \ + -Wl,-N,-S,--oformat,binary +
      + + Let us now start our study of the MBR, or + boot0, starting where execution + begins. + + + Some modifications have been made to some instructions in + favor of better exposition. For example, some macros are + expanded, and some macro tests are omitted when the result of + the test is known. This applies to all of the code examples + shown. + + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + start: + cld # String ops inc + xorw %ax,%ax # Zero + movw %ax,%es # Address + movw %ax,%ds # data + movw %ax,%ss # Set up + movw 0x7c00,%sp # stack +
      + + This first block of code is the entry point of the program. + It is where the BIOS transfers control. + First, it makes sure that the string operations autoincrement + its pointer operands (the cld instruction) + + When in doubt, we refer the reader to the official Intel + manuals, which describe the exact semantics for each + instruction: .. + Then, as it makes no assumption about the state of the segment + registers, it initializes them. Finally, it sets the stack + pointer register (%sp) to address + 0x7c00, so we have a working stack. + + The next block is responsible for the relocation and + subsequent jump to the relocated code. + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + movw $0x7c00,%si # Source + movw $0x600,%di # Destination + movw $512,%cx # Word count + rep # Relocate + movsb # code + movw %di,%bp # Address variables + movb $16,%cl # Words to clear + rep # Zero + stosb # them + incb -0xe(%di) # Set the S field to 1 + jmp main-0x7c00+0x600 # Jump to relocated code +
      + + Because boot0 is loaded by the + BIOS to address 0x7C00, it + copies itself to address 0x600 and then + transfers control there (recall that it was linked to execute at + address 0x600). The source address, + 0x7c00, is copied to register + %si. The destination address, + 0x600, to register %di. + The number of bytes to copy, 512 (the + program's size), is copied to register %cx. + Next, the rep instruction repeats the + instruction that follows, that is, movsb, the + number of times dictated by the %cx register. + The movsb instruction copies the byte pointed + to by %si to the address pointed to by + %di. This is repeated another 511 times. On + each repetition, both the source and destination registers, + %si and %di, are + incremented by one. Thus, upon completion of the 512-byte copy, + %di has the value + 0x600+512= + 0x800, and %si has the + value 0x7c00+512= + 0x7e00; we have thus completed the code + relocation. + + Next, the destination register + %di is copied to %bp. + %bp gets the value 0x800. + The value 16 is copied to + %cl in preparation for a new string operation + (like our previous movsb). Now, + stosb is executed 16 times. This instruction + copies a 0 value to the address pointed to by + the destination register (%di, which is + 0x800), and increments it. This is repeated + another 15 times, so %di ends up with value + 0x810. Effectively, this clears the address + range 0x800-0x80f. This + range is used as a (fake) partition table for writing the + MBR back to disk. Finally, the sector field + for the CHS addressing of this fake partition + is given the value 1 and a jump is made to the main function + from the relocated code. Note that until this jump to the + relocated code, any reference to an absolute address was + avoided. + + The following code block tests whether the drive number + provided by the BIOS should be used, or + the one stored in boot0. + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + main: + testb $SETDRV,-69(%bp) # Set drive number? + jnz disable_update # Yes + testb %dl,%dl # Drive number valid? + js save_curdrive # Possibly (0x80 set) +
      + + This code tests the SETDRV bit + (0x20) in the flags + variable. Recall that register %bp points to + address location 0x800, so the test is done + to the flags variable at address + 0x800-69= + 0x7bb. This is an example of the type of + modifications that can be done to boot0. + The SETDRV flag is not set by default, but it + can be set in the Makefile. When set, the + drive number stored in the MBR is used + instead of the one provided by the BIOS. We + assume the defaults, and that the BIOS + provided a valid drive number, so we jump to + save_curdrive. + + The next block saves the drive number provided by the + BIOS, and calls putn to + print a new line on the screen. + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + save_curdrive: + movb %dl, (%bp) # Save drive number + pushw %dx # Also in the stack +#ifdef TEST /* test code, print internal bios drive */ + rolb $1, %dl + movw $drive, %si + call putkey +#endif + callw putn # Print a newline +
      + + Note that we assume TEST is not defined, + so the conditional code in it is not assembled and will not + appear in our executable boot0. + + Our next block implements the actual scanning of the + partition table. It prints to the screen the partition type for + each of the four entries in the partition table. It compares + each type with a list of well-known operating system file + systems. Examples of recognized partition types are + NTFS (&windows;, ID 0x7), + ext2fs (&linux;, ID 0x83), and, of course, + ffs/ufs2 (&os;, ID 0xa5). + The implementation is fairly simple. + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + movw $(partbl+0x4),%bx # Partition table (+4) + xorw %dx,%dx # Item number + +read_entry: + movb %ch,-0x4(%bx) # Zero active flag (ch == 0) + btw %dx,_FLAGS(%bp) # Entry enabled? + jnc next_entry # No + movb (%bx),%al # Load type + test %al, %al # skip empty partition + jz next_entry + movw $bootable_ids,%di # Lookup tables + movb $(TLEN+1),%cl # Number of entries + repne # Locate + scasb # type + addw $(TLEN-1), %di # Adjust + movb (%di),%cl # Partition + addw %cx,%di # description + callw putx # Display it + +next_entry: + incw %dx # Next item + addb $0x10,%bl # Next entry + jnc read_entry # Till done +
      + + It is important to note that the active flag for each entry + is cleared, so after the scanning, no + partition entry is active in our memory copy of + boot0. Later, the active flag will be set + for the selected partition. This ensures that only one active + partition exists if the user chooses to write the changes back + to disk. + + The next block tests for other drives. At startup, + the BIOS writes the number of drives present + in the computer to address 0x475. If there + are any other drives present, boot0 prints + the current drive to screen. The user may command + boot0 to scan partitions on another drive + later. + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + popw %ax # Drive number + subb $0x79,%al # Does next + cmpb 0x475,%al # drive exist? (from BIOS?) + jb print_drive # Yes + decw %ax # Already drive 0? + jz print_prompt # Yes +
      + + We make the assumption that a single drive is present, so + the jump to print_drive is not performed. We + also assume nothing strange happened, so we jump to + print_prompt. + + This next block just prints out a prompt followed by the + default option: + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + print_prompt: + movw $prompt,%si # Display + callw putstr # prompt + movb _OPT(%bp),%dl # Display + decw %si # default + callw putkey # key + jmp start_input # Skip beep +
      + + Finally, a jump is performed to + start_input, where the + BIOS services are used to start a timer and + for reading user input from the keyboard; if the timer expires, + the default option will be selected: + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + start_input: + xorb %ah,%ah # BIOS: Get + int $0x1a # system time + movw %dx,%di # Ticks when + addw _TICKS(%bp),%di # timeout +read_key: + movb $0x1,%ah # BIOS: Check + int $0x16 # for keypress + jnz got_key # Have input + xorb %ah,%ah # BIOS: int 0x1a, 00 + int $0x1a # get system time + cmpw %di,%dx # Timeout? + jb read_key # No +
      + + An interrupt is requested with number + 0x1a and argument 0 in + register %ah. The BIOS + has a predefined set of services, requested by applications as + software-generated interrupts through the int + instruction and receiving arguments in registers (in this case, + %ah). Here, particularly, we are requesting + the number of clock ticks since last midnight; this value is + computed by the BIOS through the + RTC (Real Time Clock). This clock can be + programmed to work at frequencies ranging from 2 Hz to + 8192 Hz. The BIOS sets it to + 18.2 Hz at startup. When the request is satisfied, a + 32-bit result is returned by the BIOS in + registers %cx and %dx + (lower bytes in %dx). This result (the + %dx part) is copied to register + %di, and the value of the + TICKS variable is added to + %di. This variable resides in + boot0 at offset _TICKS + (a negative value) from register %bp (which, + recall, points to 0x800). The default value + of this variable is 0xb6 (182 in decimal). + Now, the idea is that boot0 constantly + requests the time from the BIOS, and when the + value returned in register %dx is greater + than the value stored in %di, the time is up + and the default selection will be made. Since the RTC ticks + 18.2 times per second, this condition will be met after 10 + seconds (this default behaviour can be changed in the + Makefile). Until this time has passed, + boot0 continually asks the + BIOS for any user input; this is done through + int 0x16, argument 1 in + %ah. + + Whether a key was pressed or the time expired, subsequent + code validates the selection. Based on the selection, the + register %si is set to point to the + appropriate partition entry in the partition table. This new + selection overrides the previous default one. Indeed, it + becomes the new default. Finally, the ACTIVE flag of the + selected partition is set. If it was enabled at compile time, + the in-memory version of boot0 with these + modified values is written back to the MBR on + disk. We leave the details of this implementation to the + reader. + + We now end our study with the last code block from the + boot0 program: + +
      + <filename>sys/boot/i386/boot0/boot0.S</filename> + + movw $0x7c00,%bx # Address for read + movb $0x2,%ah # Read sector + callw intx13 # from disk + jc beep # If error + cmpw $0xaa55,0x1fe(%bx) # Bootable? + jne beep # No + pushw %si # Save ptr to selected part. + callw putn # Leave some space + popw %si # Restore, next stage uses it + jmp *%bx # Invoke bootstrap +
      + + Recall that %si points to the selected + partition entry. This entry tells us where the partition begins + on disk. We assume, of course, that the partition selected is + actually a &os; slice. + + + From now on, we will favor the use of the technically + more accurate term slice rather than + partition. + + + The transfer buffer is set to 0x7c00 + (register %bx), and a read for the first + sector of the &os; slice is requested by calling + intx13. We assume that everything went okay, + so a jump to beep is not performed. In + particular, the new sector read must end with the magic sequence + 0xaa55. Finally, the value at + %si (the pointer to the selected partition + table) is preserved for use by the next stage, and a jump is + performed to address 0x7c00, where execution + of our next stage (the just-read block) is started. + + + + <literal>boot1</literal> Stage + + So far we have gone through the following sequence: - modifies the bootable flag for the selected partition to - make it bootable, and clears the previous + The BIOS did some early hardware + initialization, including the POST. The + MBR (boot0) was + loaded from absolute disk sector one to address + 0x7c00. Execution control was passed to + that location. - saves itself to disk to remember what partition (slice) - has been selected so to use it as the default on the next - boot + boot0 relocated itself to the + location it was linked to execute + (0x600), followed by a jump to continue + execution at the appropriate place. Finally, + boot0 loaded the first disk sector from + the &os; slice to address 0x7c00. + Execution control was passed to that location. + + + boot1 is the next step in the + boot-loading sequence. It is the first of three boot stages. + Note that we have been dealing exclusively + with disk sectors. Indeed, the BIOS loads + the absolute first sector, while boot0 + loads the first sector of the &os; slice. Both loads are to + address 0x7c00. We can conceptually think of + these disk sectors as containing the files + boot0 and boot1, + respectively, but in reality this is not entirely true for + boot1. Strictly speaking, unlike + boot0, boot1 is not + part of the boot blocks + + There is a file /boot/boot1, but it + is not the written to the beginning of the &os; slice. + Instead, it is concatenated with boot2 + to form boot, which + is written to the beginning of the &os; + slice and read at boot time.. + Instead, a single, full-blown file, boot + (/boot/boot), is what ultimately is + written to disk. This file is a combination of + boot1, boot2 and the + Boot Extender (or BTX). + This single file is greater in size than a single sector + (greater than 512 bytes). Fortunately, + boot1 occupies exactly + the first 512 bytes of this single file, so when + boot0 loads the first sector of the &os; + slice (512 bytes), it is actually loading + boot1 and transferring control to + it. + + The main task of boot1 is to load the + next boot stage. This next stage is somewhat more complex. It + is composed of a server called the Boot Extender, + or BTX, and a client, called + boot2. As we will see, the last boot + stage, loader, is also a client of the + BTX server. + + Let us now look in detail at what exactly is done by + boot1, starting like we did for + boot0, at its entry point: + +
      + <filename>sys/boot/i386/boot2/boot1.S</filename> + + start: + jmp main +
      + + The entry point at start simply jumps + past a special data area to the label main, + which in turn looks like this: + +
      + <filename>sys/boot/i386/boot2/boot1.S</filename> + + main: + cld # String ops inc + xor %cx,%cx # Zero + mov %cx,%es # Address + mov %cx,%ds # data + mov %cx,%ss # Set up + mov $start,%sp # stack + mov %sp,%si # Source + mov $0x700,%di # Destination + incb %ch # Word count + rep # Copy + movsw # code +
      + + Just like boot0, this + code relocates boot1, + this time to memory address 0x700. However, + unlike boot0, it does not jump there. + boot1 is linked to execute at + address 0x7c00, effectively where it was + loaded in the first place. The reason for this relocation will + be discussed shortly. + + Next comes a loop that looks for the &os; slice. Although + boot0 loaded boot1 + from the &os; slice, no information was passed to it about this + + Actually we did pass a pointer to the slice entry in + register %si. However, + boot1 does not assume that it was + loaded by boot0 (perhaps some other + MBR loaded it, and did not pass this + information), so it assumes nothing., + so boot1 must rescan the + partition table to find where the &os; slice starts. Therefore + it rereads the MBR: + +
      + <filename>sys/boot/i386/boot2/boot1.S</filename> + + mov $part4,%si # Partition + cmpb $0x80,%dl # Hard drive? + jb main.4 # No + movb $0x1,%dh # Block count + callw nread # Read MBR +
      + + In the code above, register %dl + maintains information about the boot device. This is passed on + by the BIOS and preserved by the + MBR. Numbers 0x80 and + greater tells us that we are dealing with a hard drive, so a + call is made to nread, where the + MBR is read. Arguments to + nread are passed through + %si and %dh. The memory + address at label part4 is copied to + %si. This memory address holds a + fake partition to be used by + nread. The following is the data in the fake + partition: + +
      + <filename>sys/boot/i386/boot2/Makefile</filename> + + part4: + .byte 0x80, 0x00, 0x01, 0x00 + .byte 0xa5, 0xfe, 0xff, 0xff + .byte 0x00, 0x00, 0x00, 0x00 + .byte 0x50, 0xc3, 0x00, 0x00 +
      + + In particular, the LBA for this fake + partition is hardcoded to zero. This is used as an argument to + the BIOS for reading absolute sector one from + the hard drive. Alternatively, CHS addressing could be used. + In this case, the fake partition holds cylinder 0, head 0 and + sector 1, which is equivalent to absolute sector one. + + Let us now proceed to take a look at + nread: + +
      + <filename>sys/boot/i386/boot2/boot1.S</filename> + + nread: + mov $0x8c00,%bx # Transfer buffer + mov 0x8(%si),%ax # Get + mov 0xa(%si),%cx # LBA + push %cs # Read from + callw xread.1 # disk + jnc return # If success, return +
      + + Recall that %si points to the fake + partition. The word + + In the context of 16-bit real mode, a word is 2 + bytes. + at offset 0x8 is copied to register + %ax and word at offset 0xa + to %cx. They are interpreted by the + BIOS as the lower 4-byte value denoting the + LBA to be read (the upper four bytes are assumed to be zero). + Register %bx holds the memory address where + the MBR will be loaded. The instruction + pushing %cs onto the stack is very + interesting. In this context, it accomplishes nothing. However, as + we will see shortly, boot2, in conjunction + with the BTX server, also uses + xread.1. This mechanism will be discussed in + the next section. + + The code at xread.1 further calls *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 04:10:53 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 409202A4; Sun, 26 Jan 2014 04:10:53 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 22696150C; Sun, 26 Jan 2014 04:10:53 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0Q4AqiU032288; Sun, 26 Jan 2014 04:10:52 GMT (envelope-from jgh@svn.freebsd.org) Received: (from jgh@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0Q4Apo1032281; Sun, 26 Jan 2014 04:10:51 GMT (envelope-from jgh@svn.freebsd.org) Message-Id: <201401260410.s0Q4Apo1032281@svn.freebsd.org> From: Jason Helfman Date: Sun, 26 Jan 2014 04:10:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43646 - in head/en_US.ISO8859-1/htdocs/java: . dists X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 04:10:53 -0000 Author: jgh Date: Sun Jan 26 04:10:51 2014 New Revision: 43646 URL: http://svnweb.freebsd.org/changeset/doc/43646 Log: - drop announcements/newsflash in favor of pointing to svn/freshports - update information on installation, and include pkg install instructions - shift java/linux-sun-jdk16 java/linux-sun-jdk17 for oracle jdk - update release information - drop links as these are very old and java@ would rather bring back with more relevant content Reviewed by: glewis@ (java) Approved by: wblock (mentor) Deleted: head/en_US.ISO8859-1/htdocs/java/java-rss.xsl head/en_US.ISO8859-1/htdocs/java/links.xml head/en_US.ISO8859-1/htdocs/java/news.xml head/en_US.ISO8859-1/htdocs/java/newsflash.xsl Modified: head/en_US.ISO8859-1/htdocs/java/Makefile head/en_US.ISO8859-1/htdocs/java/dists/16.xml head/en_US.ISO8859-1/htdocs/java/dists/17.xml head/en_US.ISO8859-1/htdocs/java/dists/index.xml head/en_US.ISO8859-1/htdocs/java/index.xml head/en_US.ISO8859-1/htdocs/java/install.xml Modified: head/en_US.ISO8859-1/htdocs/java/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/java/Makefile Sun Jan 26 02:30:34 2014 (r43645) +++ head/en_US.ISO8859-1/htdocs/java/Makefile Sun Jan 26 04:10:51 2014 (r43646) @@ -12,12 +12,7 @@ SUBDIR = dists DOCS+= howhelp.xml DOCS+= index.xml DOCS+= install.xml -DOCS+= links.xml DATA= j2j.gif -XML.DEFAULT= news.xml -XMLDOCS= newsflash -XMLDOCS+= news:java-rss.xsl::rss.xml - .include "${DOC_PREFIX}/share/mk/web.site.mk" Modified: head/en_US.ISO8859-1/htdocs/java/dists/16.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/java/dists/16.xml Sun Jan 26 02:30:34 2014 (r43645) +++ head/en_US.ISO8859-1/htdocs/java/dists/16.xml Sun Jan 26 04:10:51 2014 (r43646) @@ -13,115 +13,10 @@

      -May 09, 2012: Greg -Lewis updates the &openjdk; 6 port -to Build 25. +&openjdk; 6 is frequently updated, and it is suggested to refer to a +revision log for +detailed release history. Additionally, one may choose to review more information at +FreshPorts.

      -

      -November 30, 2011: Jung-uk -Kim updates the &openjdk; 6 port -to Build 24. -

      - -

      -August 9, 2011: Jung-uk -Kim updates the &openjdk; 6 port -to Build 23. -

      - -

      -March 1, 2011: Jung-uk -Kim updates the &openjdk; 6 port -to Build 22. -

      - -

      -February 9, 2011: Jung-uk -Kim updates the &openjdk; 6 port -to Build 21. -

      - -

      -July 10, 2010: Greg -Lewis updates the &openjdk; 6 port -to Build 20. -

      - -

      -May 17, 2010: Lev A. -Serebryakov's update to Build 19 of the -&openjdk; 6 port is committed. -

      - -

      -January 16, 2010: Brian -Gardner's update to Build 17 of the -&openjdk; 6 port is committed. -This update adds support for building a 'fastdebug' version of -&openjdk; 6, updates the cacerts -file and fixes font rendering. -

      - -

      -May 5, 2009: Brian -Gardner's update to Build 16 of the -&openjdk; 6 port is committed. -This update also fixes a problem with the port using the HotSpot JVM -from the bootstrap JDK rather building and installing it's version of HotSpot. -

      - -

      -February 23, 2009: Brian -Gardner's port of &openjdk; 6 is -committed to the &os; Ports Collection. -

      - -

      -February 6, 2009: Brian -Gardner has announced a port of -&openjdk; 6 to &os; 7.0. The patch -can be found at -http://beta.experts-exchange.com/articles/OS/Unix/BSD/Patch-for-OpenJDK6-on-BSD.html. -

      - -

      -February 14, 2008: Greg -Lewis has released the fourth patchset (patchlevel 4, "Mach 1") -for the &jdk; 1.6.0 software. This release now supports MacOS X -Leopard and NetBSD/amd64. Information on downloading the patchset can be -found at -http://www.eyesbeyond.com/freebsddom/java/jdk16.html. -

      - -

      -November 15, 2007: Greg -Lewis has released the third patchset (patchlevel 3, "Boss 302") -for the &jdk; 1.6.0 software. The main update in this patchset -is to move the source code base to 1.6.0 Update 3. Information on -downloading the patchset can be found at -http://www.eyesbeyond.com/freebsddom/java/jdk16.html. -

      - -

      -October 28, 2007: Greg -Lewis has released the second patchset (patchlevel 2, "Mestengo") -for the &jdk; 1.6.0 software. This release adds support for -NetBSD/i386 and is the first version of the JDK to support the browser -plugin on the amd64 architecture that I am aware of. In addition, the -source code base has been updated to 1.6.0 Update 2. Information -on downloading the patchset can be found at -http://www.eyesbeyond.com/freebsddom/java/jdk16.html. -

      - -

      -August 2, 2007: Greg -Lewis has released the first patchset (patchlevel 1, "Brumby") -for the &jdk; 1.6.0 software. This first release supports both -&os; and OpenBSD on the i386 and amd64 architectures. Information -on downloading the patchset can be found at -http://www.eyesbeyond.com/freebsddom/java/jdk16.html. -

      - - - + Modified: head/en_US.ISO8859-1/htdocs/java/dists/17.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/java/dists/17.xml Sun Jan 26 02:30:34 2014 (r43645) +++ head/en_US.ISO8859-1/htdocs/java/dists/17.xml Sun Jan 26 04:10:51 2014 (r43646) @@ -13,9 +13,10 @@

      -June 26, 2011: Greg Lewis -updates the &openjdk; 7 port -to Build 147. This corresponds to the initial FCS release of &jdk; 7. +&openjdk; 7 is frequently updated, and it is suggested to refer to a +revision log for +detailed release history. Additionally, one may choose to review more information at +FreshPorts.

      Modified: head/en_US.ISO8859-1/htdocs/java/dists/index.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/java/dists/index.xml Sun Jan 26 02:30:34 2014 (r43645) +++ head/en_US.ISO8859-1/htdocs/java/dists/index.xml Sun Jan 26 04:10:51 2014 (r43646) @@ -28,11 +28,11 @@ This is the official port of Sun's &java

      &jdk; 1.6.x

      JDK 1.6 support is available. Currently supported -versions are FreeBSD 6.2 and later (for i386 and amd64 architectures).

      +versions are FreeBSD 8.4 and later (for i386 and amd64 architectures).

      &jdk; 1.7.x

      JDK 1.7 support is available. Currently supported -versions are FreeBSD 7.0 and later (for i386 and amd64 architectures).

      +versions are FreeBSD 8.4 and later (for i386 and amd64 architectures).

      Modified: head/en_US.ISO8859-1/htdocs/java/index.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/java/index.xml Sun Jan 26 02:30:34 2014 (r43645) +++ head/en_US.ISO8859-1/htdocs/java/index.xml Sun Jan 26 04:10:51 2014 (r43646) @@ -22,7 +22,7 @@ installed by building from sources using the FreeBSD Ports Collection (openjdk6 and openjdk7, respectively) and are also distributed as a prebuilt binary package via the FreeBSD mirrors - and can be installed directly using pkg_add(1).

      + and can be installed directly using pkg(8).

      &openjdk; is the recommended &java; implementation on FreeBSD. The FreeBSD Foundation is no longer providing supported &java; &jdk; and @@ -35,12 +35,6 @@ FreeBSD Foundation &java; Downloads page.

      -

      News

      - - -

      Software

        @@ -57,7 +51,6 @@ Modified: head/en_US.ISO8859-1/htdocs/java/install.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/java/install.xml Sun Jan 26 02:30:34 2014 (r43645) +++ head/en_US.ISO8859-1/htdocs/java/install.xml Sun Jan 26 04:10:51 2014 (r43646) @@ -17,6 +17,16 @@ different Java Development Kits:

        OpenJDK on FreeBSD

        +

        To install &openjdk; 6 package use the pkg(8) utility:

        + +

        pkg install openjdk6 +

        + +

        More information on using pkg(8) is available in the + +FreeBSD Handbook. +

        +

        This is a native port of OpenJDK to FreeBSD.

        cd /usr/ports/java/openjdk6 @@ -27,7 +37,7 @@ different Java Development Kits:

        This port installs the Java Development Kit from Oracle which was built for Linux. It will run under FreeBSD using the Linux compatibility.

        -

        cd /usr/ports/java/linux-sun-jdk16 +

        cd /usr/ports/java/linux-sun-jdk17
        make install clean

        From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 08:32:26 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B96D0704; Sun, 26 Jan 2014 08:32:26 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A367A1462; Sun, 26 Jan 2014 08:32:26 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0Q8WQxu032400; Sun, 26 Jan 2014 08:32:26 GMT (envelope-from jgh@svn.freebsd.org) Received: (from jgh@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0Q8WQ3E032399; Sun, 26 Jan 2014 08:32:26 GMT (envelope-from jgh@svn.freebsd.org) Message-Id: <201401260832.s0Q8WQ3E032399@svn.freebsd.org> From: Jason Helfman Date: Sun, 26 Jan 2014 08:32:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43647 - head/en_US.ISO8859-1/books/fdp-primer/see-also X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 08:32:26 -0000 Author: jgh Date: Sun Jan 26 08:32:26 2014 New Revision: 43647 URL: http://svnweb.freebsd.org/changeset/doc/43647 Log: - remove now unrelated documentation project Approved by: wblock (mentor) Modified: head/en_US.ISO8859-1/books/fdp-primer/see-also/chapter.xml Modified: head/en_US.ISO8859-1/books/fdp-primer/see-also/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/fdp-primer/see-also/chapter.xml Sun Jan 26 04:10:51 2014 (r43646) +++ head/en_US.ISO8859-1/books/fdp-primer/see-also/chapter.xml Sun Jan 26 08:32:26 2014 (r43647) @@ -105,14 +105,4 @@ - - The Linux Documentation Project - - - - The Linux - Documentation Project web pages - - - From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 13:27:18 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C3E14B2; Sun, 26 Jan 2014 13:27:18 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 67F691743; Sun, 26 Jan 2014 13:27:18 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0QDRIpI046809; Sun, 26 Jan 2014 13:27:18 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0QDRIjH046808; Sun, 26 Jan 2014 13:27:18 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201401261327.s0QDRIjH046808@svn.freebsd.org> From: Ryusuke SUZUKI Date: Sun, 26 Jan 2014 13:27:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43648 - head/ja_JP.eucJP/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 13:27:18 -0000 Author: ryusuke Date: Sun Jan 26 13:27:17 2014 New Revision: 43648 URL: http://svnweb.freebsd.org/changeset/doc/43648 Log: - Merge the following from the English version: r43622 -> r43643 head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml ============================================================================== --- head/ja_JP.eucJP/share/xml/news.xml Sun Jan 26 08:32:26 2014 (r43647) +++ head/ja_JP.eucJP/share/xml/news.xml Sun Jan 26 13:27:17 2014 (r43648) @@ -20,7 +20,7 @@ the contents of will be preferred over <p>. $FreeBSD$ - Original revision: r43622 + Original revision: r43643 --> <news> <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS"> @@ -34,6 +34,19 @@ <name>1</name> <day> + <name>25</name> + + <event> + <title>³«È¯¿ÊĽ¥ì¥Ý¡¼¥È (2013 ǯ 10 ·î - 12 ·î) ¸ø³« + +

        2013 + ǯ 10 ·î¤«¤é 12 ·î¤Î³«È¯¿ÊĽ¥ì¥Ý¡¼¥È (37 ¥¨¥ó¥È¥ê) + ¤¬¸ø³«¤µ¤ì¤Þ¤·¤¿¡£

        + + + + 21

        ¿·¥³¥ß¥Ã¥¿½¢Ç¤: From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 16:37:48 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECE247E6; Sun, 26 Jan 2014 16:37:48 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D8F07147E; Sun, 26 Jan 2014 16:37:48 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0QGbm2T026408; Sun, 26 Jan 2014 16:37:48 GMT (envelope-from jgh@svn.freebsd.org) Received: (from jgh@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0QGbmlw026407; Sun, 26 Jan 2014 16:37:48 GMT (envelope-from jgh@svn.freebsd.org) Message-Id: <201401261637.s0QGbmlw026407@svn.freebsd.org> From: Jason Helfman Date: Sun, 26 Jan 2014 16:37:48 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43649 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 16:37:49 -0000 Author: jgh Date: Sun Jan 26 16:37:48 2014 New Revision: 43649 URL: http://svnweb.freebsd.org/changeset/doc/43649 Log: - add 10 to FAQ Approved by: remko (mentor) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Sun Jan 26 13:27:17 2014 (r43648) +++ head/en_US.ISO8859-1/books/faq/book.xml Sun Jan 26 16:37:48 2014 (r43649) @@ -20,7 +20,7 @@ ]> Frequently Asked Questions for &os; - &rel2.relx;, and &rel.relx; + &rel2.relx;, &rel.relx; and &rel.head.relx; The &os; Documentation Project From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 18:31:53 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA3F059A; Sun, 26 Jan 2014 18:31:53 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 94B6F1F49; Sun, 26 Jan 2014 18:31:53 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0QIVrIX072675; Sun, 26 Jan 2014 18:31:53 GMT (envelope-from jgh@svn.freebsd.org) Received: (from jgh@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0QIVriC072674; Sun, 26 Jan 2014 18:31:53 GMT (envelope-from jgh@svn.freebsd.org) Message-Id: <201401261831.s0QIVriC072674@svn.freebsd.org> From: Jason Helfman Date: Sun, 26 Jan 2014 18:31:53 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43650 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 18:31:53 -0000 Author: jgh Date: Sun Jan 26 18:31:53 2014 New Revision: 43650 URL: http://svnweb.freebsd.org/changeset/doc/43650 Log: - add Poudriere to testing section Reviewed by: bapt Approved by: wblock (mentor) Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/book.xml Sun Jan 26 16:37:48 2014 (r43649) +++ head/en_US.ISO8859-1/books/porters-handbook/book.xml Sun Jan 26 18:31:53 2014 (r43650) @@ -10897,6 +10897,20 @@ as .putsy.conf and edit it.Tinderbox website for more details. + + + Poudriere + + As a ports contributor, consider installing + poudriere. It is a powerful + system for building and testing ports. + Poudriere can be installed with + ports-mgmt/poudriere. + + Visit the Poudriere + website for more details. + From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 20:48:20 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA5DC7D6; Sun, 26 Jan 2014 20:48:20 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9866D18E6; Sun, 26 Jan 2014 20:48:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0QKmKiY025213; Sun, 26 Jan 2014 20:48:20 GMT (envelope-from jkois@svn.freebsd.org) Received: (from jkois@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0QKmK6O025212; Sun, 26 Jan 2014 20:48:20 GMT (envelope-from jkois@svn.freebsd.org) Message-Id: <201401262048.s0QKmK6O025212@svn.freebsd.org> From: Johann Kois Date: Sun, 26 Jan 2014 20:48:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43651 - head/de_DE.ISO8859-1/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 20:48:20 -0000 Author: jkois Date: Sun Jan 26 20:48:20 2014 New Revision: 43651 URL: http://svnweb.freebsd.org/changeset/doc/43651 Log: r43545 -> r43643 MFde: Resync the project news page Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/share/xml/news.xml Modified: head/de_DE.ISO8859-1/share/xml/news.xml ============================================================================== --- head/de_DE.ISO8859-1/share/xml/news.xml Sun Jan 26 18:31:53 2014 (r43650) +++ head/de_DE.ISO8859-1/share/xml/news.xml Sun Jan 26 20:48:20 2014 (r43651) @@ -4,7 +4,7 @@ @@ -16,8 +16,29 @@ + 2014 + + + 1 + + + McKusick: &os; sicherheitstechnisch up-to-date + http://www.itwire.com/business-it-news/open-source/62728-mckusick-denies-freebsd-lagging-on-security + ITWire + http://www.itwire.com/ + 06. Januar 2014 + Sam Varghese +

        Kirk McKusick weist Vorwürfe zurück, dass &os; in Sachen + Sicherheit nicht auf dem aktuellen Stand und weist darauf hin, + dass &os; in der letzten Dekade diverse gute Designs und + Techniken in random(4) implementiert hat.

        + + + + + 2013 - + 6 From owner-svn-doc-all@FreeBSD.ORG Sun Jan 26 23:12:18 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9565F07; Sun, 26 Jan 2014 23:12:18 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9AF3D15BD; Sun, 26 Jan 2014 23:12:18 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0QNCILS085776; Sun, 26 Jan 2014 23:12:18 GMT (envelope-from taras@svn.freebsd.org) Received: (from taras@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0QNCIla085775; Sun, 26 Jan 2014 23:12:18 GMT (envelope-from taras@svn.freebsd.org) Message-Id: <201401262312.s0QNCIla085775@svn.freebsd.org> From: Taras Korenko Date: Sun, 26 Jan 2014 23:12:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43653 - head/ru_RU.KOI8-R/books/handbook/bsdinstall X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Sun, 26 Jan 2014 23:38:14 +0000 X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 23:12:19 -0000 Author: taras Date: Sun Jan 26 23:12:18 2014 New Revision: 43653 URL: http://svnweb.freebsd.org/changeset/doc/43653 Log: MFen: + books/handbook/bsdinstall/chapter.xml r43126 --> r43414 Modified: head/ru_RU.KOI8-R/books/handbook/bsdinstall/chapter.xml Modified: head/ru_RU.KOI8-R/books/handbook/bsdinstall/chapter.xml ============================================================================== --- head/ru_RU.KOI8-R/books/handbook/bsdinstall/chapter.xml Sun Jan 26 20:54:36 2014 (r43652) +++ head/ru_RU.KOI8-R/books/handbook/bsdinstall/chapter.xml Sun Jan 26 23:12:18 2014 (r43653) @@ -3,7 +3,7 @@ The FreeBSD Russian Documentation Project $FreeBSD$ - Original revision: r43126 + Original revision: r43414 --> õÓÔÁÎÏ×ËÁ &os; ×ÅÒÓÉÊ 9.<replaceable>X</replaceable> É ÂÏÌÅÅ @@ -202,24 +202,24 @@ <title>òÁÚÄÅÌÙ ÄÉÓËÁ ÄÌÑ &os;/&arch.i386; É &os;/&arch.amd64; ÷ÅÓØ ÏÂßÅÍ ÖÅÓÔËÉÈ ÄÉÓËÏ× ÍÏÖÅÔ ÂÙÔØ ÒÁÚÄÅÌÅÎ ÎÁ ÍÎÏÖÅÓÔ×Ï - ÞÁÓÔÅÊ. üÔÉ ÞÁÓÔÉ ÎÁÚÙ×ÁÀÔÓÑ ÒÁÚÄÅÌÁÍÉ. + ÞÁÓÔÅÊ. üÔÉ ÞÁÓÔÉ ÎÁÚÙ×ÁÀÔÓÑ ÒÁÚÄÅÌÁÍÉ. åÓÔØ Ä×Á ÓÐÏÓÏÂÁ ÄÅÌÅÎÉÑ ÄÉÓËÁ ÎÁ ÒÁÚÄÅÌÙ. ôÒÁÄÉÃÉÏÎÎÙÊ - ÓÐÏÓÏ — Master Boot Record - (MBR) — - ÈÒÁÎÉÔ ÔÁÂÌÉÃÕ ÒÁÚÄÅÌÏ×, ×ÍÅÝÁÀÝÕÀ ÄÏ ÞÅÔÙÒÅÈ ÐÅÒ×ÉÞÎÙÈ - ÒÁÚÄÅÌÏ×. (ôÁË ÓÌÏÖÉÌÏÓØ ÉÓÔÏÒÉÞÅÓËÉ, ÞÔÏ ×Ï &os; - ÜÔÉ ÒÁÚÄÅÌÙ ÎÁÚÙ×ÁÀÔÓÑ ÓÌÁÊÓÁÍÉ.) ÷ÏÚÍÏÖÎÙ + ÓÐÏÓÏ — Master Boot Record + (MBR) — + ÈÒÁÎÉÔ ÔÁÂÌÉÃÕ ÒÁÚÄÅÌÏ×, ×ÍÅÝÁÀÝÕÀ ÄÏ ÞÅÔÙÒÅÈ ÐÅÒ×ÉÞÎÙÈ + ÒÁÚÄÅÌÏ×. (ôÁË ÓÌÏÖÉÌÏÓØ ÉÓÔÏÒÉÞÅÓËÉ, ÞÔÏ ×Ï &os; + ÜÔÉ ÒÁÚÄÅÌÙ ÎÁÚÙ×ÁÀÔÓÑ ÓÌÁÊÓÁÍÉ.) ÷ÏÚÍÏÖÎÙ ÓÉÔÕÁÃÉÉ, × ËÏÔÏÒÙÈ ÞÅÔÙÒÅ ÒÁÚÄÅÌÁ ÎÅÄÏÓÔÁÔÏÞÎÏ, ÐÏÜÔÏÍÕ ÏÄÉÎ ÉÚ - ÐÅÒ×ÉÞÎÙÈ ÒÁÚÄÅÌÏ× ÍÏÖÅÔ ÂÙÔØ ÐÒÅ×ÒÁÝÅÎ × ÒÁÓÛÉÒÅÎÎÙÊ - ÒÁÚÄÅÌ. ÷ÎÕÔÒÉ ÒÁÓÛÉÒÅÎÎÏÇÏ ÒÁÚÄÅÌÁ ÍÏÖÅÔ ÂÙÔØ ÓÏÚÄÁÎÏ - ÎÅÓËÏÌØËÏ ÌÏÇÉÞÅÓËÉÈ ÒÁÚÄÅÌÏ×. òÅÚÕÌØÔÉÒÕÀÝÁÑ + ÐÅÒ×ÉÞÎÙÈ ÒÁÚÄÅÌÏ× ÍÏÖÅÔ ÂÙÔØ ÐÒÅ×ÒÁÝÅÎ × ÒÁÓÛÉÒÅÎÎÙÊ + ÒÁÚÄÅÌ. ÷ÎÕÔÒÉ ÒÁÓÛÉÒÅÎÎÏÇÏ ÒÁÚÄÅÌÁ ÍÏÖÅÔ ÂÙÔØ ÓÏÚÄÁÎÏ + ÎÅÓËÏÌØËÏ ÌÏÇÉÞÅÓËÉÈ ÒÁÚÄÅÌÏ×. òÅÚÕÌØÔÉÒÕÀÝÁÑ ÓÔÒÕËÔÕÒÁ ×ÙÇÌÑÄÉÔ ÎÅÍÎÏÇÏ ÎÅÕËÌÀÖÅ, ÎÏ ÔÁËÏ×Á ÏÎÁ ÅÓÔØ. - óÏÚÄÁÎÉÅ ôÁÂÌÉÃÙ òÁÚÄÅÌÏ× GUID (GUID - Partition Table, GPT) + óÏÚÄÁÎÉÅ ôÁÂÌÉÃÙ òÁÚÄÅÌÏ× GUID (GUID + Partition Table, GPT) — ÜÔÏ ÂÏÌÅÅ ÎÏ×ÙÊ É ÐÒÏÓÔÏÊ ÓÐÏÓÏ ÄÅÌÅÎÉÑ ÄÉÓËÁ. ôÁËÖÅ ÎÏ×ÙÊ - ÓÐÏÓÏ (GPT) ÐÏ + ÓÐÏÓÏ (GPT) ÐÏ ÓÒÁ×ÎÅÎÉÀ Ó ÔÒÁÄÉÃÉÏÎÎÙÍ ÓÐÏÓÏÂÏÍ ÒÁÚÂÉÅÎÉÑ (MBR) ÇÏÒÁÚÄÏ ÂÏÌÅÅ ÇÉÂËÉÊ. òÁÓÐÒÏÓÔÒÁΣÎÎÙÅ ÒÅÁÌÉÚÁÃÉÉ GPT ÐÏÚ×ÏÌÑÀÔ ÓÏÚÄÁ×ÁÔØ ÄÏ 128 ÒÁÚÄÅÌÏ× ÎÁ ÏÄÎÏÍ @@ -231,7 +231,7 @@ &windows; XP, ÎÅ ÓÏ×ÍÅÓÔÉÍÙ ÓÏ ÓÈÅÍÏÊ GPT. åÓÌÉ ÎÁ ÏÄÉÎ ÄÉÓË ÎÅÏÂÈÏÄÉÍÏ ÕÓÔÁÎÏ×ÉÔØ &os; ÓÏ×ÍÅÓÔÎÏ Ó ÔÁËÏÊ ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÏÊ, ÔÏ ÓÌÅÄÕÅÔ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ÓÈÅÍÏÊ - MBR. + MBR. óÔÁÎÄÁÒÔÎÏÍÕ ÚÁÇÒÕÚÞÉËÕ &os; ÎÅÏÂÈÏÄÉÍ ÐÅÒ×ÉÞÎÙÊ ÒÁÚÄÅÌ @@ -336,8 +336,8 @@ Ethernet). äÌÑ Á×ÔÏÍÁÔÉÞÅÓËÏÇÏ ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÑ ÓÅÔÅ×ÙÈ ÉÎÔÅÒÆÅÊÓÏ× ÞÁÓÔÏ - ÐÒÉÍÅÎÑÅÔÓÑ ÐÒÏÔÏËÏÌ DHCP. åÓÌÉ × - ÐÏÄËÌÀÞÁÅÍÏÊ ÓÅÔÉ ÓÅÒ×ÉÓ DHCP ÏÔÓÕÔÓÔ×ÕÅÔ, + ÐÒÉÍÅÎÑÅÔÓÑ ÐÒÏÔÏËÏÌ DHCP. + åÓÌÉ × ÐÏÄËÌÀÞÁÅÍÏÊ ÓÅÔÉ ÓÅÒ×ÉÓ DHCP ÏÔÓÕÔÓÔ×ÕÅÔ, ÉÎÆÏÒÍÁÃÉÀ Ï ÐÏÄËÌÀÞÅÎÉÉ Ë ÎÅÏÂÈÏÄÉÍÏ ×ÚÑÔØ Õ ÓÉÓÔÅÍÎÏÇÏ ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ ÉÌÉ ÐÒÏ×ÁÊÄÅÒÁ éÎÔÅÒÎÅÔ. @@ -345,7 +345,7 @@ éÎÆÏÒÍÁÃÉÑ Ï ÐÏÄËÌÀÞÅÎÉÉ Ë ÓÅÔÉ - IP ÁÄÒÅÓ + IP ÁÄÒÅÓ @@ -403,7 +403,18 @@ ëÏÐÉÉ ÏÂÒÁÚÏ× ÕÓÔÁÎÏ×ÏÞÎÙÈ ÎÏÓÉÔÅÌÅÊ ÎÁÈÏÄÑÔÓÑ ÎÁ ×Å ÓÁÊÔÅ - &os;. + &os;. ôÁËÖÅ, × ËÁÔÁÌÏÇÅ Ó ÆÁÊÌÁÍÉ ÕÓÔÁÎÏ×ÏÞÎÙÈ + ÏÂÒÁÚÏ× ÎÁÈÏÄÉÔÓÑ ÆÁÊÌ CHECKSUM.SHA256, + ËÏÔÏÒÙÊ ÐÏÎÁÄÏÂÉÔÓÑ ×ÁÍ ÄÌÑ ÐÒÏ×ÅÒËÉ ÃÅÌÏÓÔÎÏÓÔÉ ÓËÁÞÁÎÎÏÇÏ + ÆÁÊÌÁ ÏÂÒÁÚÁ. ðÒÏ×ÅÒËÁ ÃÅÌÏÓÔÎÏÓÔÉ ÆÁÊÌÁ ÏÂÒÁÚÁ ÐÒÏÉÚ×ÏÄÉÔÓÑ + ÓÒÁ×ÎÅÎÉÅÍ ËÏÎÔÒÏÌØÎÙÈ ÓÕÍÍ. äÌÑ + ÐÏÄÓÞÅÔÁ ÐÏÓÌÅÄÎÉÈ &os; ÐÒÅÄÏÓÔÁ×ÌÑÅÔ &man.sha256.1;, ÄÒÕÇÉÅ + ÏÐÅÒÁÃÉÏÎÎÙÅ ÓÉÓÔÅÍÙ ÔÁËÖÅ ÒÁÓÐÏÌÁÇÁÀÔ ÐÏÄÏÂÎÙÍÉ ÐÒÏÇÒÁÍÍÁÍÉ. + óÒÁ×ÎÉÔÅ ÐÏÌÕÞÅÎÎÕÀ ËÏÎÔÒÏÌØÎÕÀ ÓÕÍÍÕ Ó ÏÄÎÏÊ ÉÚ + CHECKSUM.SHA256. ëÏÎÔÒÏÌØÎÙÅ ÓÕÍÍÙ + ÄÏÌÖÎÙ ÓÏ×ÐÁÓÔØ ÐÏÌÎÏÓÔØÀ. îÅÓÏ×ÐÁÄÅÎÉÅ ËÏÎÔÒÏÌØÎÙÈ ÓÕÍÍ + ÚÎÁÞÉÔ, ÞÔÏ ÆÁÊÌ ÐÏ×ÒÅÖÄÅÎ É Ë ÉÓÐÏÌØÚÏ×ÁÎÉÀ + ÎÅ ÐÒÉÇÏÄÅÎ. åÓÌÉ Õ ×ÁÓ ÕÖÅ ÉÍÅÅÔÓÑ ËÏÐÉÑ &os; ÎÁ CDROM, DVD, ÉÌÉ @@ -414,7 +425,9 @@ CD- É DVD-ÏÂÒÁÚÙ &os; Ñ×ÌÑÀÔÓÑ ÚÁÇÒÕÚÏÞÎÙÍÉ. äÌÑ ÕÓÔÁÎÏ×ËÉ ÎÅÏÂÈÏÄÉÍ ÏÄÉÎ ÉÚ ÎÉÈ. úÁÐÉÛÉÔÅ ÏÂÒÁÚ ÎÁ CD ÉÌÉ DVD ÄÉÓË ÐÒÉ ÐÏÍÏÝÉ ÐÒÏÇÒÁÍÍÙ ÄÌÑ ÚÁÐÉÓÉ CD, ËÏÔÏÒÁÑ ÅÓÔØ × ×ÁÛÅÊ ÔÅËÕÝÅÊ ÏÐÅÒÁÃÉÏÎÎÏÊ - ÓÉÓÔÅÍÅ. + ÓÉÓÔÅÍÅ. ÷Ï &os; ÚÁÐÉÓØ ÄÉÓËÏ× ÏÓÕÝÅÓÔ×ÌÑÅÔÓÑ ÕÔÉÌÉÔÏÊ + &man.cdrecord.1; ÉÚ ËÏÍÐÌÅËÔÁ + sysutils/cdrtools ëÏÌÌÅËÃÉÉ ðÏÒÔÏ×. äÌÑ ÓÏÚÄÁÎÉÑ ÚÁÇÒÕÚÏÞÎÏÇÏ ÆÌÅÛ-ÎÁËÏÐÉÔÅÌÑ ×ÙÐÏÌÎÉÔÅ ÓÌÅÄÕÀÝÉÅ ÛÁÇÉ: @@ -569,8 +582,7 @@ commit your changes? îÁÓÔÒÏÊÔÅ ×ÁÛÕ ÍÁÛÉÎÕ ÎÁ ÚÁÇÒÕÚËÕ Ó CDROM ÉÌÉ Ó USB, × ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÔÏÇÏ, ËÁËÏÅ ÕÓÔÒÏÊÓÔ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ - ÕÓÔÁÎÏ×ËÉ. îÁÓÔÒÏÊËÉ - BIOS + ÕÓÔÁÎÏ×ËÉ. îÁÓÔÒÏÊËÉ BIOS ÐÏÚ×ÏÌÑÀÔ ×ÙÂÒÁÔØ ËÏÎËÒÅÔÎÏÅ ÚÁÇÒÕÚÏÞÎÏÅ ÕÓÔÒÏÊÓÔ×Ï. âÏÌØÛÉÎÓÔ×Ï ÓÉÓÔÅÍ ÔÁËÖÅ ÐÒÅÄÏÓÔÁ×ÌÑÀÔ ×ÏÚÍÏÖÎÏÓÔØ ×ÙÂÒÁÔØ ÚÁÇÒÕÚÏÞÎÏÅ ÕÓÔÒÏÊÓÔ×Ï ×Ï ×ÒÅÍÑ ÚÁÐÕÓËÁ, ÞÁÓÔÏ ÜÔÁ ×ÏÚÍÏÖÎÏÓÔØ @@ -687,8 +699,7 @@ Loading /boot/defaults/loader.conf âÏÌØÛÉÎÓÔ×Ï ÓÉÓÔÅÍ &sparc64; ÎÁÓÔÒÏÅÎÙ ÎÁ Á×ÔÏÍÁÔÉÞÅÓËÕÀ ÚÁÇÒÕÚËÕ Ó ÖÅÓÔËÏÇÏ ÄÉÓËÁ. äÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÕÓÔÁÎÏ×ÉÔØ &os;, ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ×ÙÐÏÌÎÉÔØ ÚÁÇÒÕÚËÕ ÐÏ ÓÅÔÉ ÉÌÉ Ó CDROM, ÞÔÏ ÐÏÄÒÁÚÕÍÅ×ÁÅÔ - ÐÏÌÕÞÅÎÉÅ ÄÏÓÔÕÐÁ Ë - PROM + ÐÏÌÕÞÅÎÉÅ ÄÏÓÔÕÐÁ Ë PROM (OpenFirmware). äÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÏÌÕÞÉÔØ ÄÏÓÔÕÐ Ë PROM, @@ -702,7 +713,7 @@ OpenBoot 4.2, 128 MB memory installed, S Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. åÓÌÉ ×ÁÛÁ ÓÉÓÔÅÍÁ ÐÒÏÄÏÌÖÁÅÔ ÚÁÇÒÕÖÁÔØÓÑ Ó ÖÅÓÔËÏÇÏ ÄÉÓËÁ, ÔÏ - ÞÔÏÂÙ ÐÏÌÕÞÉÔØ ÐÒÉÇÌÁÛÅÎÉÅ PROM ×ÁÍ ÎÅÏÂÈÏÄÉÍÏ + ÞÔÏÂÙ ÐÏÌÕÞÉÔØ ÐÒÉÇÌÁÛÅÎÉÅ PROM ×ÁÍ ÎÅÏÂÈÏÄÉÍÏ ÎÁÖÁÔØ ÎÁ ËÌÁ×ÉÁÔÕÒÅ L1A ÉÌÉ StopA, ÉÌÉ ÖÅ ÐÏÓÌÁÔØ ÓÉÇÎÁÌ BREAK ÞÅÒÅÚ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÕÀ @@ -1236,7 +1247,7 @@ Trying to mount root from cd9660:/dev/is ðÅÒÅÍÅÝÅÎÉÅ ÐÏÄÓ×ÅÞÉ×ÁÎÉÑ ÎÁ ÉÍÑ ÕÓÔÒÏÊÓÔ×Á (× ÜÔÏÍ ÐÒÉÍÅÒÅ — ada0) É ×ÙÂÏÒ [ Create ] ÐÒÉ×ÅÄÅÔ ×ÁÓ Ë ÍÅÎÀ - Ó ÐÅÒÅÞÎÅÍ ÓÈÅÍ ÒÁÚÂÉÅÎÉÑ. + Ó ÐÅÒÅÞÎÅÍ ÓÈÅÍ ÒÁÚÂÉÅÎÉÑ.
        ÷ÙÂÏÒ ÓÈÅÍÙ ÒÁÚÂÉÅÎÉÑ @@ -1384,7 +1395,7 @@ Trying to mount root from cd9660:/dev/is ÒÁÚÄÅÌ UFS, ÔÏ ÔÏÞËÁ ÍÏÎÔÉÒÏ×ÁÎÉÑ ÄÏÌÖÎÁ ÂÙÔØ /. - ôÁËÖÅ ÂÕÄÅÔ ÚÁÐÒÏÛÅÎÁ ÍÅÔËÁ. íÅÔËÁ — + ôÁËÖÅ ÂÕÄÅÔ ÚÁÐÒÏÛÅÎÁ ÍÅÔËÁ. íÅÔËÁ — ÜÔÏ ÉÍÑ, ÐÒÉÓ×ÏÅÎÎÏÅ ÒÁÚÄÅÌÕ. éÍÑ ÕÓÔÒÏÊÓÔ×Á ÉÌÉ ÅÇÏ ÎÏÍÅÒ ÍÏÖÅÔ ÉÚÍÅÎÉÔØÓÑ ÅÓÌÉ ÕÓÔÒÏÊÓÔ×Ï ÂÕÄÅÔ ÐÏÄËÌÀÞÅÎÏ Ë ÄÒÕÇÏÍÕ ËÏÎÔÒÏÌÌÅÒÕ ÉÌÉ ÐÏÒÔÕ, Á ÍÅÔËÁ ÒÁÚÄÅÌÁ ÏÓÔÁÎÅÔÓÑ ÎÅÉÚÍÅÎÎÏÊ. óÓÙÌËÉ ÎÁ ÍÅÔËÉ @@ -1400,7 +1411,8 @@ Trying to mount root from cd9660:/dev/is ÄÌÑ ËÁÖÄÏÊ ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÙ. îÅÓËÏÌØËÏ ÂÕË×, ×ÚÑÔÙÈ ÏÔ ÉÍÅÎÉ ËÏÍÐØÀÔÅÒÁ, ÅÇÏ ÎÁÚÎÁÞÅÎÉÑ ÉÌÉ ÒÁÚÍÅÝÅÎÉÑ ÍÏÖÅÔ ÂÙÔØ ÄÏÂÁ×ÌÅÎÏ Ë ÍÅÔËÅ. îÁÐÒÉÍÅÒ, ËÏÒÎÅ×ÏÍÕ ÒÁÚÄÅÌÕ UFS ÄÌÑ ËÏÍÐØÀÔÅÒÁ × ÌÁÂÏÒÁÔÏÒÉÉ - ÍÏÖÎÏ ÐÒÉÓ×ÏÉÔØ ÍÅÔËÕ "labroot" ÉÌÉ "rootfs-lab". + ÍÏÖÎÏ ÐÒÉÓ×ÏÉÔØ ÍÅÔËÕ labroot ÉÌÉ + rootfs-lab. @@ -1415,7 +1427,8 @@ Trying to mount root from cd9660:/dev/is ÒÁÚÍÅÒÏÍ 20çÂ. åÓÌÉ ÄÉÓË ÂÏÌØÛÅÇÏ ÒÁÚÍÅÒÁ, ÔÏ ÂÕÄÅÔ ÕÍÅÓÔÎÙÍ ÏÔ×ÅÓÔÉ ÂÏÌØÛÅ ÍÅÓÔÁ ÄÌÑ ÒÁÚÄÅÌÁ ÐÏÄËÁÞËÉ ÉÌÉ ÄÌÑ ÒÁÚÄÅÌÁ Ó ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÏÊ /var. úÁÄÅÊÓÔ×Ï×ÁÎÎÙÅ × ÜÔÏÍ ÐÒÉÍÅÒÅ ÍÅÔËÉ - ÉÍÅÀÔ ÐÒÅÆÉËÓ ex, ÏÔ ÓÌÏ×Á "example", ×ÁÍ ÖÅ + ÉÍÅÀÔ ÐÒÅÆÉËÓ ex, ÏÔ ÓÌÏ×Á + example, ×ÁÍ ÖÅ ÒÅËÏÍÅÎÄÕÅÔÓÑ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÒÕÇÉÅ ÕÎÉËÁÌØÎÙÅ ÉÍÅÎÁ ÍÅÔÏË. ðÏ ÕÍÏÌÞÁÎÉÀ, ÚÁÇÒÕÚÞÉË gptboot &os; @@ -1620,15 +1633,16 @@ Trying to mount root from cd9660:/dev/is É ÂÅÚÏÐÁÓÎÏÓÔÉ. âÅÓÐÒÏ×ÏÄÎÙÅ ÓÅÔÉ ÒÁÓÐÏÚÎÁÀÔÓÑ ÐÏ ÔÁË ÎÁÚÙ×ÁÅÍÏÍÕ - Service Set Identifier, ÉÌÉ - SSID. + Service Set Identifier, ÉÌÉ SSID. SSID + — ÜÔÏ ËÒÁÔËÏÅ ÕÎÉËÁÌØÎÏÅ ÉÍÑ, ÐÒÉÓ×ÁÉ×ÁÅÍÏÅ ËÁÖÄÏÊ + ÓÅÔÉ. âÏÌØÛÉÎÓÔ×Ï ÂÅÓÐÒÏ×ÏÄÎÙÈ ÓÅÔÅÊ ÛÉÆÒÕÀÔ ÐÅÒÅÄÁ×ÁÅÍÙÅ ÄÁÎÎÙÅ ÞÔÏÂÙ ÚÁÝÉÔÉÔØ ÉÈ ÏÔ ÎÅÁ×ÔÏÒÉÚÉÒÏ×ÁÎÎÏÇÏ ÐÒÏÓÌÕÛÉ×ÁÎÉÑ. îÁÓÔÏÑÔÅÌØÎÏ ÒÅËÏÍÅÎÄÕÅÔÓÑ ÐÒÉÍÅÎÑÔØ ÓÔÁÎÄÁÒÔ - WPA2. + WPA2. âÏÌÅÅ ÓÔÁÒÙÅ ÓÔÁÎÄÁÒÔÙ, ÎÁÐÒÉÍÅÒ - WEP, + WEP, ÎÅ ÏÂÅÓÐÅÞÉ×ÁÀÔ ÄÏÓÔÁÔÏÞÎÏÇÏ ÕÒÏ×ÎÑ ÂÅÚÏÐÁÓÎÏÓÔÉ. ðÅÒ×ÙÍ ÄÅÌÏÍ, ÐÒÉ ÐÏÄËÌÀÞÅÎÉÉ Ë ÂÅÓÐÒÏ×ÏÄÎÏÊ ÓÅÔÉ ÎÅÏÂÈÏÄÉÍÏ @@ -1645,9 +1659,9 @@ Trying to mount root from cd9660:/dev/is
        óÐÉÓÏË ÎÁÊÄÅÎÎÙÈ ÓÅÔÅÊ ÂÕÄÅÔ ÓÏÄÅÒÖÁÔØ ÎÅÓËÏÌØËÏ - SSID Ó ÏÐÉÓÁÎÉÅÍ + SSID Ó ÏÐÉÓÁÎÉÅÍ ÔÉÐÏ× ÛÉÆÒÏ×ÁÎÉÑ, ÐÏÄÄÅÒÖÉ×ÁÅÍÙÈ ÏÂÎÁÒÕÖÅÎÎÙÍÉ ÂÅÓÐÒÏ×ÏÄÎÙÍÉ ÓÅÔÑÍÉ. - åÓÌÉ ÉÓËÏÍÙÊ SSID + åÓÌÉ ÉÓËÏÍÙÊ SSID ÎÅ ÐÏÑ×ÌÑÅÔÓÑ × ÓÐÉÓËÅ, ÔÏ ÚÁÐÕÓÔÉÔÅ ÓËÁÎÉÒÏ×ÁÎÉÅ ÐÏ×ÔÏÒÎÏ, ×ÙÂÒÁ× [ Rescan ]. åÓÌÉ ÉÓËÏÍÁÑ ÓÅÔØ ÓÎÏ×Á ÎÅ ÐÏÑ×ÉÔÓÑ × ÓÐÉÓËÅ, ÐÒÏ×ÅÒØÔÅ ÓÏÅÄÉÎÅÎÉÅ Ó ÁÎÔÅÎÎÏÊ ÉÌÉ @@ -1665,10 +1679,9 @@ Trying to mount root from cd9660:/dev/is ðÏÓÌÅ ×ÙÂÏÒÁ ÓÅÔÉ ÐÏÔÒÅÂÕÅÔÓÑ ××ÅÓÔÉ ÄÏÐÏÌÎÉÔÅÌØÎÕÀ ÉÎÆÏÒÍÁÃÉÀ - Ï ÓÏÅÄÉÎÅÎÉÉ. äÌÑ - WPA2 + Ï ÓÏÅÄÉÎÅÎÉÉ. äÌÑ WPA2 ÐÏÔÒÅÂÕÅÔÓÑ ÐÁÒÏÌØ (ÔÁËÖÅ ÉÚ×ÅÓÔÎÙÊ ËÁË Pre-Shared Key ÉÌÉ - PSK). ÷ ÃÅÌÑÈ ÂÅÚÏÐÁÓÎÏÓÔÉ + PSK). ÷ ÃÅÌÑÈ ÂÅÚÏÐÁÓÎÏÓÔÉ ÎÁÂÉÒÁÅÍÙÅ × ÐÏÌÅ ××ÏÄÁ ÐÁÒÏÌÑ ÓÉÍ×ÏÌÙ ÎÁ ÜËÒÁÎÅ ÏÔÏÂÒÁÖÁÀÔÓÑ Ú×ÅÚÄÏÞËÁÍÉ. @@ -1703,10 +1716,10 @@ Trying to mount root from cd9660:/dev/is óÕÝÅÓÔ×ÕÅÔ Ä×Á ÓÐÏÓÏÂÁ ÎÁÓÔÒÏÊËÉ ÐÒÏÔÏËÏÌÁ IPv4 ÎÁ ÓÅÔÅ×ÏÍ - ÉÎÔÅÒÆÅÊÓÅ. óÅÒ×ÉÓ DHCP + ÉÎÔÅÒÆÅÊÓÅ. óÅÒ×ÉÓ DHCP Á×ÔÏÍÁÔÉÞÅÓËÉ ÕÓÔÁÎÏ×ÉÔ ËÏÒÒÅËÔÎÕÀ ËÏÎÆÉÇÕÒÁÃÉÀ ÓÅÔÅ×ÏÇÏ ÉÎÔÅÒÆÅÊÓÁ, É ÜÔÏ — ÐÒÅÄÐÏÞÔÉÔÅÌØÎÙÊ ÓÐÏÓÏ ÎÁÓÔÒÏÊËÉ. - óÔÁÔÉÞÅÓËÁÑ ËÏÎÆÉÇÕÒÁÃÉÑ ÔÒÅÂÕÅÔ ÒÕÞÎÏÇÏ + óÔÁÔÉÞÅÓËÁÑ ËÏÎÆÉÇÕÒÁÃÉÑ ÔÒÅÂÕÅÔ ÒÕÞÎÏÇÏ ××ÏÄÁ ÎÁÓÔÒÏÅË ÐÒÏÔÏËÏÌÁ IPv4. @@ -1795,10 +1808,10 @@ Trying to mount root from cd9660:/dev/is äÌÑ ÐÒÏÔÏËÏÌÁ IPv6 ÔÁËÖÅ ×ÏÚÍÏÖÎÙ Ä×Á ÓÐÏÓÏÂÁ ÎÁÓÔÒÏÊËÉ ÓÅÔÅ×ÏÇÏ - ÉÎÔÅÒÆÅÊÓÁ. SLAAC + ÉÎÔÅÒÆÅÊÓÁ. SLAAC ÉÌÉ StateLess Address AutoConfiguration Á×ÔÏÍÁÔÉÞÅÓËÉ ÕÓÔÁÎÏ×ÉÔ ËÏÒÒÅËÔÎÙÅ ÎÁÓÔÒÏÊËÉ ÓÅÔÅ×ÏÇÏ ÉÎÔÅÒÆÅÊÓÁ. - óÔÁÔÉÞÅÓËÁÑ ËÏÎÆÉÇÕÒÁÃÉÑ ÔÒÅÂÕÅÔ ÒÕÞÎÏÇÏ + óÔÁÔÉÞÅÓËÁÑ ËÏÎÆÉÇÕÒÁÃÉÑ ÔÒÅÂÕÅÔ ÒÕÞÎÏÇÏ ××ÏÄÁ ÎÁÓÔÒÏÅË ÐÒÏÔÏËÏÌÁ IPv6. @@ -1856,11 +1869,10 @@ Trying to mount root from cd9660:/dev/is - îÁÓÔÒÏÊËÁ òÅÚÏÌ×ÅÒÁ - <acronym role="Domain Name System">DNS</acronym> + îÁÓÔÒÏÊËÁ òÅÚÏÌ×ÅÒÁ <acronym>DNS</acronym> - Domain Name System (ÉÌÉ - DNS) + Domain Name System (ÉÌÉ + DNS) òÅÚÏÌ×ÅÒ ×ÙÐÏÌÎÑÅÔ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ ÉÍÅÎ ÈÏÓÔÏ× × ÓÅÔÅ×ÙÅ ÁÄÒÅÓÁ, Á ÔÁËÖÅ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ ÓÅÔÅ×ÙÈ ÁÄÒÅÓÏ× × ÉÍÅÎÁ ÈÏÓÔÏ×. åÓÌÉ ÄÌÑ Á×ÔÏÍÁÔÉÞÅÓËÏÇÏ ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÑ ÓÅÔÅ×ÏÇÏ ÉÎÔÅÒÆÅÊÓÁ ÉÓÐÏÌØÚÏ×ÁÌÓÑ @@ -1989,7 +2001,7 @@ Trying to mount root from cd9660:/dev/is sshd - Secure Shell - (SSH) ÄÅÍÏÎ ÄÌÑ ÂÅÚÏÐÁÓÎÏÇÏ + (SSH) ÄÅÍÏÎ ÄÌÑ ÂÅÚÏÐÁÓÎÏÇÏ ÕÄÁÌÅÎÎÏÇÏ ÄÏÓÔÕÐÁ. @@ -2000,7 +2012,7 @@ Trying to mount root from cd9660:/dev/is ntpd - Network Time Protocol - (NTP) ÄÅÍÏÎ + (NTP) ÄÅÍÏÎ ÄÌÑ Á×ÔÏÍÁÔÉÞÅÓËÏÊ ÓÉÎÈÒÏÎÉÚÁÃÉÉ ×ÒÅÍÅÎÉ. @@ -2620,7 +2632,8 @@ login: äÌÑ ÐÏÌÕÞÅÎÉÑ ÄÏÓÔÕÐÁ Ë ÓÉÓÔÅÍÅ ÎÅÏÂÈÏÄÉÍÏ ÏÓÕÝÅÓÔ×ÉÔØ ÁÕÔÅÎÔÉÆÉËÁÃÉÀ. äÏÐÕÓÔÉÍÏÅ ÉÍÑ ÐÏÌØÚÏ×ÁÔÅÌÑ — - root, ÐÁÒÏÌØ — ÐÕÓÔÏÊ. + root, ÐÁÒÏÌØ + — ÐÕÓÔÏÊ.         From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 10:22:57 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBB2E9F2; Mon, 27 Jan 2014 10:22:57 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D6AEA16DC; Mon, 27 Jan 2014 10:22:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RAMvWC047242; Mon, 27 Jan 2014 10:22:57 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RAMvnr047241; Mon, 27 Jan 2014 10:22:57 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401271022.s0RAMvnr047241@svn.freebsd.org> From: Remko Lodder Date: Mon, 27 Jan 2014 10:22:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43654 - translations/nl_NL.ISO8859-1/htdocs X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 10:22:58 -0000 Author: remko Date: Mon Jan 27 10:22:57 2014 New Revision: 43654 URL: http://svnweb.freebsd.org/changeset/doc/43654 Log: Corrigeer typo. Spotted by: "Snader_LB" Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/htdocs/index.xsl Modified: translations/nl_NL.ISO8859-1/htdocs/index.xsl ============================================================================== --- translations/nl_NL.ISO8859-1/htdocs/index.xsl Sun Jan 26 23:12:18 2014 (r43653) +++ translations/nl_NL.ISO8859-1/htdocs/index.xsl Mon Jan 27 10:22:57 2014 (r43654) @@ -41,7 +41,7 @@ Gebaseerd op BSD &unix;

        &os;® is een geavanceerd - besturingssystem voor moderne platforms voor servers, desktop, en embedded computers. De broncode van &os; heeft meer dan dertig From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 11:00:33 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 93FBC821; Mon, 27 Jan 2014 11:00:33 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7F6D4197A; Mon, 27 Jan 2014 11:00:33 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RB0XUH060148; Mon, 27 Jan 2014 11:00:33 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RB0X05060147; Mon, 27 Jan 2014 11:00:33 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201401271100.s0RB0X05060147@svn.freebsd.org> From: Rene Ladan Date: Mon, 27 Jan 2014 11:00:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43655 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 11:00:33 -0000 Author: rene Date: Mon Jan 27 11:00:33 2014 New Revision: 43655 URL: http://svnweb.freebsd.org/changeset/doc/43655 Log: Document USES=desthack Modified: head/en_US.ISO8859-1/books/porters-handbook/uses.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/uses.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/uses.xml Mon Jan 27 10:22:57 2014 (r43654) +++ head/en_US.ISO8859-1/books/porters-handbook/uses.xml Mon Jan 27 11:00:33 2014 (r43655) @@ -132,6 +132,16 @@ + desthack + + (none) + + Changes the behavior of GNU configure to properly support + DESTDIR in case the original software does + not. + + + desktop-file-utils (none) From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 11:03:36 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CAA9296B; Mon, 27 Jan 2014 11:03:36 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B5D6519ED; Mon, 27 Jan 2014 11:03:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RB3aua063223; Mon, 27 Jan 2014 11:03:36 GMT (envelope-from rodrigo@svn.freebsd.org) Received: (from rodrigo@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RB3a0l063220; Mon, 27 Jan 2014 11:03:36 GMT (envelope-from rodrigo@svn.freebsd.org) Message-Id: <201401271103.s0RB3a0l063220@svn.freebsd.org> From: Rodrigo Osorio Date: Mon, 27 Jan 2014 11:03:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43656 - head/share/pgpkeys X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 11:03:37 -0000 Author: rodrigo (ports committer) Date: Mon Jan 27 11:03:36 2014 New Revision: 43656 URL: http://svnweb.freebsd.org/changeset/doc/43656 Log: Add myself as a developer Add my GnuPG key Approved by: kwm@ (co-mentor) Added: head/share/pgpkeys/rodrigo.key (contents, props changed) Modified: head/share/pgpkeys/pgpkeys.ent Modified: head/share/pgpkeys/pgpkeys.ent ============================================================================== --- head/share/pgpkeys/pgpkeys.ent Mon Jan 27 11:00:33 2014 (r43655) +++ head/share/pgpkeys/pgpkeys.ent Mon Jan 27 11:03:36 2014 (r43656) @@ -352,6 +352,7 @@ + Added: head/share/pgpkeys/rodrigo.key ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/pgpkeys/rodrigo.key Mon Jan 27 11:03:36 2014 (r43656) @@ -0,0 +1,51 @@ + + + +uid Rodrigo Osorio +sub 2048R/25498586651F5E23 2014-01-14 [expires: 2017-01-13] + +]]> + From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 11:08:09 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D6CB4C0; Mon, 27 Jan 2014 11:08:09 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ED2E61CBD; Mon, 27 Jan 2014 11:08:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RB88kT063891; Mon, 27 Jan 2014 11:08:08 GMT (envelope-from rodrigo@svn.freebsd.org) Received: (from rodrigo@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RB88OY063888; Mon, 27 Jan 2014 11:08:08 GMT (envelope-from rodrigo@svn.freebsd.org) Message-Id: <201401271108.s0RB88OY063888@svn.freebsd.org> From: Rodrigo Osorio Date: Mon, 27 Jan 2014 11:08:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43657 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 11:08:09 -0000 Author: rodrigo (ports committer) Date: Mon Jan 27 11:08:08 2014 New Revision: 43657 URL: http://svnweb.freebsd.org/changeset/doc/43657 Log: Add myself as a developer Remove myself as an Additionnal contributor Approved by: kwm@ (co-mentor) Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Mon Jan 27 11:03:36 2014 (r43656) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Mon Jan 27 11:08:08 2014 (r43657) @@ -8800,11 +8800,6 @@ - Rodrigo Osorio - rodrigo@bebik.net - - - Roger Hardiman roger@cs.strath.ac.uk Modified: head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Mon Jan 27 11:03:36 2014 (r43656) +++ head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Mon Jan 27 11:08:08 2014 (r43657) @@ -987,6 +987,10 @@ + &a.rodrigo.email; + + + &a.philip.email; From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 11:12:32 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B889384E; Mon, 27 Jan 2014 11:12:32 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A44CD1D81; Mon, 27 Jan 2014 11:12:32 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RBCWSu066459; Mon, 27 Jan 2014 11:12:32 GMT (envelope-from rodrigo@svn.freebsd.org) Received: (from rodrigo@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RBCWgb066457; Mon, 27 Jan 2014 11:12:32 GMT (envelope-from rodrigo@svn.freebsd.org) Message-Id: <201401271112.s0RBCWgb066457@svn.freebsd.org> From: Rodrigo Osorio Date: Mon, 27 Jan 2014 11:12:32 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43658 - head/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 11:12:32 -0000 Author: rodrigo (ports committer) Date: Mon Jan 27 11:12:31 2014 New Revision: 43658 URL: http://svnweb.freebsd.org/changeset/doc/43658 Log: Add myself as a developer Update the news Approved by: kwm@ (co-mentor) Modified: head/share/xml/authors.ent head/share/xml/news.xml Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Mon Jan 27 11:08:08 2014 (r43657) +++ head/share/xml/authors.ent Mon Jan 27 11:12:31 2014 (r43658) @@ -1761,6 +1761,9 @@ rodrigc@FreeBSD.org"> + +rodrigo@FreeBSD.org"> + roger@FreeBSD.org"> Modified: head/share/xml/news.xml ============================================================================== --- head/share/xml/news.xml Mon Jan 27 11:08:08 2014 (r43657) +++ head/share/xml/news.xml Mon Jan 27 11:12:31 2014 (r43658) @@ -46,6 +46,14 @@ + 23 + +

        New committer: + Rodrigo Osorio (ports)

        +         +         + + 21

        New committer: From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 11:14:51 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3765E9F4; Mon, 27 Jan 2014 11:14:51 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 22E161D97; Mon, 27 Jan 2014 11:14:51 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RBEp5Q066900; Mon, 27 Jan 2014 11:14:51 GMT (envelope-from blackend@svn.freebsd.org) Received: (from blackend@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RBEo2A066899; Mon, 27 Jan 2014 11:14:50 GMT (envelope-from blackend@svn.freebsd.org) Message-Id: <201401271114.s0RBEo2A066899@svn.freebsd.org> From: Marc Fonvieille Date: Mon, 27 Jan 2014 11:14:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43659 - head/en_US.ISO8859-1/htdocs/community X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 11:14:51 -0000 Author: blackend Date: Mon Jan 27 11:14:50 2014 New Revision: 43659 URL: http://svnweb.freebsd.org/changeset/doc/43659 Log: Remove a dead French mailinglist. PR: 186165 Submitted by: Stephane Goujet Modified: head/en_US.ISO8859-1/htdocs/community/mailinglists.xml Modified: head/en_US.ISO8859-1/htdocs/community/mailinglists.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/community/mailinglists.xml Mon Jan 27 11:12:31 2014 (r43658) +++ head/en_US.ISO8859-1/htdocs/community/mailinglists.xml Mon Jan 27 11:14:50 2014 (r43659) @@ -53,10 +53,6 @@ href="http://www.freebsd.de/mailinglists.html">Administration or Search. -

      • French -- listserver@FreeBSD-fr.org - or WWW.
        • -
      • Hungarian -- bsd@lista.bsd.hu, Administration From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 12:36:14 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 18B251A4; Mon, 27 Jan 2014 12:36:14 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0449013BA; Mon, 27 Jan 2014 12:36:14 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RCaDg6097887; Mon, 27 Jan 2014 12:36:13 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RCaD2Y097886; Mon, 27 Jan 2014 12:36:13 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401271236.s0RCaD2Y097886@svn.freebsd.org> From: Warren Block Date: Mon, 27 Jan 2014 12:36:13 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43660 - head/en_US.ISO8859-1/books/handbook/firewalls X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 12:36:14 -0000 Author: wblock Date: Mon Jan 27 12:36:13 2014 New Revision: 43660 URL: http://svnweb.freebsd.org/changeset/doc/43660 Log: Correct the instructions on enabling ftp-proxy. PR: docs/186154 Submitted by: Robert Simmons Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Jan 27 11:14:50 2014 (r43659) +++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Jan 27 12:36:13 2014 (r43660) @@ -904,7 +904,7 @@ pass from { lo0, $localnet } to any keep To enable &man.ftp-proxy.8;, add this line to /etc/rc.conf: - ftpproxy_flags="" + ftpproxy_enable="YES" Starting the proxy manually by running /usr/sbin/ftp-proxy allows testing of From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 12:38:54 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0CCBB2FB; Mon, 27 Jan 2014 12:38:54 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D36BA13D5; Mon, 27 Jan 2014 12:38:53 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RCcrth098454; Mon, 27 Jan 2014 12:38:53 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RCcrwW098453; Mon, 27 Jan 2014 12:38:53 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401271238.s0RCcrwW098453@svn.freebsd.org> From: Warren Block Date: Mon, 27 Jan 2014 12:38:53 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43661 - head/en_US.ISO8859-1/books/handbook/firewalls X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 12:38:54 -0000 Author: wblock Date: Mon Jan 27 12:38:53 2014 New Revision: 43661 URL: http://svnweb.freebsd.org/changeset/doc/43661 Log: Expand a few contractions. Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Jan 27 12:36:13 2014 (r43660) +++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Jan 27 12:38:53 2014 (r43661) @@ -1104,7 +1104,7 @@ pass inet proto icmp from any to $ext_if By default, Unix traceroute uses UDP connections according to a set formula based on destination. The rule below works with - traceroute on all unixes I've had + traceroute on all Unixes I have had access to, including GNU/Linux: # allow out the default range for traceroute(8): @@ -1125,7 +1125,7 @@ pass out on $ext_if inet proto udp from details. Under any circumstances, this solution was lifted - from an openbsd-misc post. I've found that list, and + from an openbsd-misc post. I have found that list, and the searchable list archives (accessible among other places from http://marc.theaimsgroup.com/), to be a very valuable resource whenever you need OpenBSD @@ -1290,7 +1290,7 @@ Sep 26 03:12:44 skapet sshd[24703]: Fail solution. Pass rules can be written so they maintain certain limits on what connecting hosts can do. For good measure, violators can be banished to a table of addresses - which are denied some or all access. If desired, it's even + which are denied some or all access. If desired, it is even possible to drop all existing connections from machines which overreach the limits. Here is how it is done: From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 13:12:05 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B3453113; Mon, 27 Jan 2014 13:12:05 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9D6991703; Mon, 27 Jan 2014 13:12:05 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RDC5ub013688; Mon, 27 Jan 2014 13:12:05 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RDC5Rt013686; Mon, 27 Jan 2014 13:12:05 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401271312.s0RDC5Rt013686@svn.freebsd.org> From: Warren Block Date: Mon, 27 Jan 2014 13:12:05 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43662 - head/en_US.ISO8859-1/books/handbook/firewalls X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 13:12:05 -0000 Author: wblock Date: Mon Jan 27 13:12:05 2014 New Revision: 43662 URL: http://svnweb.freebsd.org/changeset/doc/43662 Log: Whitespace-only cleanup, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Jan 27 12:38:53 2014 (r43661) +++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Jan 27 13:12:05 2014 (r43662) @@ -4,18 +4,34 @@ $FreeBSD$ --> - - Firewalls + + + + Firewalls + - Joseph J.BarbishContributed by + + + Joseph J. + Barbish + + Contributed by + + - BradDavisConverted to SGML and updated by + + + Brad + Davis + + Converted to SGML and updated by + - - firewall @@ -166,19 +182,26 @@ TCP/IP works, what the different values in the packet control fields are, and how these values are used in a normal session conversation. For a good introduction, refer - to Daryl's TCP/IP - Primer. + to + Daryl's + TCP/IP Primer. - PF and <acronym>ALTQ</acronym> + + PF and <acronym>ALTQ</acronym> + - JohnFerrellRevised and updated by + + + John + Ferrell + + Revised and updated by + - - firewall @@ -193,13 +216,15 @@ Quality of Service (QoS). Since the OpenBSD Project maintains the definitive - reference for PF in the PF FAQ, this - section of the Handbook focuses on PF as it - pertains to &os;, while providing some general usage + reference for PF in the + PF FAQ, + this section of the Handbook focuses on PF as + it pertains to &os;, while providing some general usage information. More information about porting PF to &os; - can be found at http://pf4freebsd.love2party.net/. + can be found at http://pf4freebsd.love2party.net/. Using the PF Loadable Kernel Modules @@ -208,26 +233,27 @@ loaded. Add the following line to /etc/rc.conf: - pf_enable="YES" - - Then, run the startup script to load the module: + pf_enable="YES" - &prompt.root; service pf start - - The PF module will not load if it cannot find the - ruleset configuration file. The default location is - /etc/pf.conf. If the PF ruleset is - located somewhere else, add a line to - /etc/rc.conf which specifies the full - path to the file: + Then, run the startup script to load the module: - pf_rules="/path/to/pf.conf" + &prompt.root; service pf start - The sample pf.conf - can be found in /usr/share/examples/pf/. + The PF module will not load if it cannot find the + ruleset configuration file. The default location is + /etc/pf.conf. If the PF ruleset is + located somewhere else, add a line to + /etc/rc.conf which specifies the full + path to the file: + + pf_rules="/path/to/pf.conf" + + The sample pf.conf + can be found in + /usr/share/examples/pf/. - The PF module can also be loaded - manually from the command line: + The PF module can also be loaded + manually from the command line: &prompt.root; kldload pf.ko @@ -240,7 +266,6 @@ Then, run the startup script to load the module: &prompt.root; service pflog start - @@ -248,30 +273,28 @@ kernel options - device pf kernel options - device pflog kernel options - device pfsync - While it is not necessary to compile - PF support into the &os; kernel, some of - PF's advanced features are not included in the loadable - module, namely &man.pfsync.4;, which is a pseudo-device that - exposes certain changes to the state table used by - PF. It can be paired with &man.carp.4; to - create failover firewalls using PF. More - information on CARP can be found in of the Handbook. + While it is not necessary to compile PF + support into the &os; kernel, some of PF's advanced features + are not included in the loadable module, namely + &man.pfsync.4;, which is a pseudo-device that exposes certain + changes to the state table used by PF. It + can be paired with &man.carp.4; to create failover firewalls + using PF. More information on + CARP can be found in + of the Handbook. The following PF kernel options can be found in /usr/src/sys/conf/NOTES: @@ -323,24 +346,27 @@ pflog_flags="" # additi specified in this file. The &os; installation includes several sample files located in /usr/share/examples/pf/. Refer to the - PF FAQ for - complete coverage of PF rulesets. + PF + FAQ for complete coverage of PF + rulesets. - When reading the PF FAQ, + When reading the PF FAQ, keep in mind that different versions of &os; contain different versions of PF. Currently, - &os; 8.X is using the - same version of PF as - OpenBSD 4.1. &os; 9.X - and later is using the same version of PF - as OpenBSD 4.5. + &os; 8.X is using the same + version of PF as OpenBSD 4.1. + &os; 9.X and later is using + the same version of PF as + OpenBSD 4.5. The &a.pf; is a good place to ask questions about configuring and running the PF firewall. Do not forget to check the mailing list archives before asking questions. + To control PF, use &man.pfctl.8;. Below are some useful options to this command. Review &man.pfctl.8; for a description of all available @@ -440,7 +466,8 @@ options ALTQ_NOPCC # Requir options ALTQ_HFSC enables the Hierarchical Fair Service Curve Packet Scheduler HFSC. For more - information, refer to http://www-2.cs.cmu.edu/~hzhang/HFSC/main.html. + information, refer to http://www-2.cs.cmu.edu/~hzhang/HFSC/main.html. options ALTQ_PRIQ enables Priority Queuing @@ -454,24 +481,32 @@ options ALTQ_NOPCC # Requir - <acronym>PF</acronym> Rule Sets and Tools + + <acronym>PF</acronym> Rule Sets and Tools + - PeterHansteenN. M.Contributed by + + + Peter + Hansteen + N. M. + + Contributed by + - - This section demonstrates some useful PF features and PF related tools in a series of examples. A more thorough - tutorial is available at http://home.nuug.no/~peter/pf/. + tutorial is available at http://home.nuug.no/~peter/pf/. - security/sudo is - useful for running commands like pfctl - that require elevated privileges. It can be installed from - the Ports Collection. + security/sudo is useful for running + commands like pfctl that require elevated + privileges. It can be installed from the Ports + Collection. @@ -506,7 +541,8 @@ pass out all keep state of some thinking. The point of packet filtering is to take control, not to run catch-up with what the bad guys do. Marcus Ranum has written a very entertaining and - informative article about this, The + informative article about this, The Six Dumbest Ideas in Computer Security, and it is well written too.. This gives us the opportunity to introduce two of the features which @@ -892,7 +928,7 @@ pass from { lo0, $localnet } to any keep gateway is amazingly simple, thanks to the FTP proxy program (called &man.ftp-proxy.8;) included in the base system on &os; and - other systems which offer PF. + other systems which offer PF. The FTP protocol being what it is, the proxy needs to dynamically insert rules in your rule @@ -1127,7 +1163,8 @@ pass out on $ext_if inet proto udp from Under any circumstances, this solution was lifted from an openbsd-misc post. I have found that list, and the searchable list archives (accessible among other - places from http://marc.theaimsgroup.com/), + places from http://marc.theaimsgroup.com/), to be a very valuable resource whenever you need OpenBSD or PF related information. @@ -1345,8 +1382,9 @@ Sep 26 03:12:44 skapet sshd[24703]: Fail These rules will not block slow - bruteforcers, sometimes referred to as the Hail - Mary Cloud. + bruteforcers, sometimes referred to as the + Hail Mary Cloud. Once again, please keep in mind that this example rule @@ -1444,7 +1482,8 @@ Sep 26 03:12:44 skapet sshd[24703]: Fail /usr/local/sbin/expiretable -v -d -t 24h bruteforce expiretable is in the - Ports Collection on &os; as security/expiretable. + Ports Collection on &os; as + security/expiretable. @@ -1462,11 +1501,10 @@ Sep 26 03:12:44 skapet sshd[24703]: Fail makes it possible to keep an eye on what passes into and out of the network. pftop is available through the ports system as - sysutils/pftop. The - name is a strong hint at what it does - - pftop shows a running snapshot - of traffic in a format which is strongly inspired by - &man.top.1;. + sysutils/pftop. The name is a strong + hint at what it does - pftop + shows a running snapshot of traffic in a format which is + strongly inspired by &man.top.1;. @@ -1516,11 +1554,12 @@ Sep 26 03:12:44 skapet sshd[24703]: Fail - Install the mail/spamd/ port. In - particular, be sure to read the package message and - act upon what it says. Specifically, to use + Install the mail/spamd/ port. + In particular, be sure to read the package message + and act upon what it says. Specifically, to use spamd's greylisting - features, a file descriptor file system (see fdescfs(5)) + features, a file descriptor file system (see fdescfs(5)) must be mounted at /dev/fd/. Do this by adding the following line to /etc/fstab: @@ -1670,7 +1709,8 @@ rdr pass on $ext_if inet proto tcp from paper by Evan Harris The original Harris paper and a number of other useful articles - and resources can be found at the greylisting.org + and resources can be found at the greylisting.org web site., and a number of implementations followed over the next few months. OpenBSD's spamd acquired its @@ -1893,7 +1933,8 @@ block drop out quick on $ext_if from any This completes our simple NATing firewall for a small local network. A more thorough tutorial is - available at http://home.nuug.no/~peter/pf/, + available at http://home.nuug.no/~peter/pf/, where you will also find slides from related presentations. @@ -1940,13 +1981,17 @@ block drop out quick on $ext_if from any for configuring an inclusive firewall ruleset. For a detailed explanation of the legacy rules processing - method, refer to http://www.munk.me.uk/ipf/ipf-howto.html - and http://coombs.anu.edu.au/~avalon/ip-filter.html. + method, refer to http://www.munk.me.uk/ipf/ipf-howto.html + and http://coombs.anu.edu.au/~avalon/ip-filter.html. - The IPF FAQ is at http://www.phildev.net/ipf/index.html. + The IPF FAQ is at http://www.phildev.net/ipf/index.html. A searchable archive of the IPFilter mailing list is - available at http://marc.theaimsgroup.com/?l=ipfilter. + available at http://marc.theaimsgroup.com/?l=ipfilter. Enabling IPF @@ -2424,8 +2469,9 @@ EOF adding ipfilter_enable="NO"to /etc/rc.conf. - Then, add a script like the following to /usr/local/etc/rc.d/. - The script should have an obvious name like + Then, add a script like the following to + /usr/local/etc/rc.d/. The script + should have an obvious name like ipf.loadrules.sh, where the .sh extension is mandatory. @@ -2433,7 +2479,8 @@ EOF sh /etc/ipf.rules.script The permissions on this script file must be read, - write, execute for owner root: + write, execute for owner + root: &prompt.root; chmod 700 /usr/local/etc/rc.d/ipf.loadrules.sh @@ -2658,9 +2705,11 @@ sh /etc/ipf.rules.scriptThere is no way to match ranges of IP addresses which do not express themselves easily using the dotted numeric - form / mask-length notation. The net-mgmt/ipcalc port may be - used to ease the calculation. Additional information - is available at the utility's web page: http://jodies.de/ipcalc. + form / mask-length notation. The + net-mgmt/ipcalc port may be used to ease + the calculation. Additional information is available at the + utility's web page: http://jodies.de/ipcalc. @@ -2675,8 +2724,8 @@ sh /etc/ipf.rules.scriptfrom object, it matches the source port number. When it appears as part of the to object, it matches the destination - port number. An example usage is from any to any - port = 80 + port number. An example usage is + from any to any port = 80 Single port comparisons may be done in a number of ways, using a number of different comparison operators. Instead @@ -2793,10 +2842,10 @@ sh /etc/ipf.rules.script &os; uses interface lo0 and IP - address 127.0.0.1 for internal - communication within the operating system. The firewall rules - must contain rules to allow free movement of these internally - used packets. + address 127.0.0.1 + for internal communication within the operating system. The + firewall rules must contain rules to allow free movement of + these internally used packets. The interface which faces the public Internet is the one specified in the rules that authorize and control access of @@ -2857,13 +2906,13 @@ sh /etc/ipf.rules.script To lookup unknown port numbers, refer to - /etc/services. Alternatively, visit - http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers + /etc/services. Alternatively, visit http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers and do a port number lookup to find the purpose of a particular port number. - Check out this link for port numbers used by Trojans - http://www.sans.org/security-resources/idfaq/oddports.php. + Check out this link for port numbers used by Trojans http://www.sans.org/security-resources/idfaq/oddports.php. The following ruleset creates an inclusive firewall ruleset which can be @@ -3166,7 +3215,8 @@ block in log first quick on dc0 all The LAN_IP_RANGE is used by the internal clients use for IP Addressing. Usually, this is - something like 192.168.1.0/24. + something like 192.168.1.0/24. The PUBLIC_ADDRESS can either be the static external IP address or the special keyword @@ -3290,8 +3340,9 @@ block in log first quick on dc0 all servers still has to undergo NAT, but there has to be some way to direct the inbound traffic to the correct server. For example, a web server operating on LAN - address 10.0.10.25 and using a single public - IP address of 20.20.20.5, would + address 10.0.10.25 + and using a single public IP address of + 20.20.20.5, would use this rule: rdr dc0 20.20.20.5/32 port 80 -> 10.0.10.25 port 80 @@ -3300,8 +3351,9 @@ block in log first quick on dc0 all rdr dc0 0.0.0.0/0 port 80 -> 10.0.10.25 port 80 - For a LAN DNS server on a private address of 10.0.10.33 that needs to receive - public DNS requests: + For a LAN DNS server on a private address of + 10.0.10.33 that + needs to receive public DNS requests: rdr dc0 20.20.20.5/32 port 53 -> 10.0.10.33 port 53 udp @@ -3313,7 +3365,8 @@ block in log first quick on dc0 all difference is in how the data channel is acquired. Passive mode is more secure as the data channel is acquired by the ordinal ftp session requester. For a good explanation of FTP - and the different modes, see http://www.slacksite.com/other/ftp.html. + and the different modes, see http://www.slacksite.com/other/ftp.html. IP<acronym>NAT</acronym> Rules @@ -3821,23 +3874,24 @@ ipfw add deny out any IP address configured on an interface in the &os; system to represent the PC the firewall is running on. Example usage includes from me to any, - from any to me, from 0.0.0.0/0 - to any, from any to - 0.0.0.0/0, from 0.0.0.0 to - any. from any to 0.0.0.0, + from any to me, + from 0.0.0.0/0 to any, + from any to 0.0.0.0/0, + from 0.0.0.0 to any. + from any to 0.0.0.0, and from me to 0.0.0.0. IP addresses are specified in dotted IP address format followed by the mask in CIDR notation, or as a single host in dotted IP address format. This keyword is a mandatory requirement. - The net-mgmt/ipcalc - port may be used to assist the mask calculation. + The net-mgmt/ipcalc port may be used to + assist the mask calculation. port number For protocols which support port numbers, such as TCP and UDP, it is mandatory to include the port number of the service - that will be matched. Service names from + that will be matched. Service names from /etc/services may be used instead of numeric port values. From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 13:14:44 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92D2E30B; Mon, 27 Jan 2014 13:14:44 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7E8461732; Mon, 27 Jan 2014 13:14:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RDEiM8014143; Mon, 27 Jan 2014 13:14:44 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RDEifN014142; Mon, 27 Jan 2014 13:14:44 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401271314.s0RDEifN014142@svn.freebsd.org> From: Warren Block Date: Mon, 27 Jan 2014 13:14:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43663 - head/en_US.ISO8859-1/books/handbook/firewalls X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 13:14:44 -0000 Author: wblock Date: Mon Jan 27 13:14:44 2014 New Revision: 43663 URL: http://svnweb.freebsd.org/changeset/doc/43663 Log: Fix a typo, a period that should have been a comma. Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Jan 27 13:12:05 2014 (r43662) +++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Jan 27 13:14:44 2014 (r43663) @@ -3877,7 +3877,7 @@ ipfw add deny out from any to me, from 0.0.0.0/0 to any, from any to 0.0.0.0/0, - from 0.0.0.0 to any. + from 0.0.0.0 to any, from any to 0.0.0.0, and from me to 0.0.0.0. IP addresses are specified in dotted IP address format followed by the From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 15:43:54 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F27A0E0D; Mon, 27 Jan 2014 15:43:53 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DB47A159C; Mon, 27 Jan 2014 15:43:53 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RFhrbF072127; Mon, 27 Jan 2014 15:43:53 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RFhrJE072126; Mon, 27 Jan 2014 15:43:53 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201401271543.s0RFhrJE072126@svn.freebsd.org> From: Ryusuke SUZUKI Date: Mon, 27 Jan 2014 15:43:53 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43664 - head/ja_JP.eucJP/htdocs/community X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 15:43:54 -0000 Author: ryusuke Date: Mon Jan 27 15:43:53 2014 New Revision: 43664 URL: http://svnweb.freebsd.org/changeset/doc/43664 Log: - Merge the following from the English version: r43388 -> r43659 head/ja_JP.eucJP/htdocs/community/mailinglists.xml Modified: head/ja_JP.eucJP/htdocs/community/mailinglists.xml Modified: head/ja_JP.eucJP/htdocs/community/mailinglists.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/community/mailinglists.xml Mon Jan 27 13:14:44 2014 (r43663) +++ head/ja_JP.eucJP/htdocs/community/mailinglists.xml Mon Jan 27 15:43:53 2014 (r43664) @@ -4,7 +4,7 @@ ]> - + @@ -53,10 +53,6 @@ href="http://www.freebsd.de/mailinglists.html">¥¢¥É¥ß¥Ë¥¹¥È¥ì¡¼¥·¥ç¥ó ¤Þ¤¿¤Ï ¸¡º÷
        • -
      • ¥Õ¥é¥ó¥¹¸ì -- listserver@FreeBSD-fr.org - ¤Þ¤¿¤Ï WWW
        • -
      • ¥Ï¥ó¥¬¥ê¡¼¸ì -- bsd@lista.bsd.hu, ¥¢¥É¥ß¥Ë¥¹¥È¥ì¡¼¥·¥ç¥ó From owner-svn-doc-all@FreeBSD.ORG Mon Jan 27 15:45:28 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 500C9E7A; Mon, 27 Jan 2014 15:45:28 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3C3D815A8; Mon, 27 Jan 2014 15:45:28 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RFjSFD072442; Mon, 27 Jan 2014 15:45:28 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0RFjSGB072440; Mon, 27 Jan 2014 15:45:28 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201401271545.s0RFjSGB072440@svn.freebsd.org> From: Ryusuke SUZUKI Date: Mon, 27 Jan 2014 15:45:28 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43665 - head/ja_JP.eucJP/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 15:45:28 -0000 Author: ryusuke Date: Mon Jan 27 15:45:27 2014 New Revision: 43665 URL: http://svnweb.freebsd.org/changeset/doc/43665 Log: - Merge the following from the English version: r43643 -> r43658 head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml ============================================================================== --- head/ja_JP.eucJP/share/xml/news.xml Mon Jan 27 15:43:53 2014 (r43664) +++ head/ja_JP.eucJP/share/xml/news.xml Mon Jan 27 15:45:27 2014 (r43665) @@ -20,7 +20,7 @@ the contents of will be preferred over <p>. $FreeBSD$ - Original revision: r43643 + Original revision: r43658 --> <news> <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS"> @@ -47,6 +47,14 @@ </day> <day> + <name>23</name> + <event> + <p>¿·¥³¥ß¥Ã¥¿½¢Ç¤: + <a href="mailto:rodrigo@FreeBSD.org">Rodrigo Osorio</a> (ports)</p> + </event> + </day> + + <day> <name>21</name> <event> <p>¿·¥³¥ß¥Ã¥¿½¢Ç¤: From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 12:31:45 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 009A562F; Tue, 28 Jan 2014 12:31:44 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E07E01858; Tue, 28 Jan 2014 12:31:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SCVife065192; Tue, 28 Jan 2014 12:31:44 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SCViBm065190; Tue, 28 Jan 2014 12:31:44 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281231.s0SCViBm065190@svn.freebsd.org> From: Remko Lodder <remko@FreeBSD.org> Date: Tue, 28 Jan 2014 12:31:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43666 - translations/nl_NL.ISO8859-1/flyer X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 28 Jan 2014 12:31:45 -0000 Author: remko Date: Tue Jan 28 12:31:44 2014 New Revision: 43666 URL: http://svnweb.freebsd.org/changeset/doc/43666 Log: Update the revisions in the flyer. No functional changes needed. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/flyer/Makefile translations/nl_NL.ISO8859-1/flyer/flyer.tex Modified: translations/nl_NL.ISO8859-1/flyer/Makefile ============================================================================== --- translations/nl_NL.ISO8859-1/flyer/Makefile Mon Jan 27 15:45:27 2014 (r43665) +++ translations/nl_NL.ISO8859-1/flyer/Makefile Tue Jan 28 12:31:44 2014 (r43666) @@ -1,7 +1,7 @@ # $FreeBSD$ # # %SOURCE% en_US.ISO8859-1/flyer/Makefile -# %SRCID% 39702 +# %SRCID% 39771 pdf: dvi ps ps2pdf -sPAPERSIZE=a4 flyer.ps Modified: translations/nl_NL.ISO8859-1/flyer/flyer.tex ============================================================================== --- translations/nl_NL.ISO8859-1/flyer/flyer.tex Mon Jan 27 15:45:27 2014 (r43665) +++ translations/nl_NL.ISO8859-1/flyer/flyer.tex Tue Jan 28 12:31:44 2014 (r43666) @@ -28,7 +28,7 @@ % % $FreeBSD$ % %SOURCE% en_US.ISO8859-1/flyer/flyer.tex -% %SRCID% 39706 +% %SRCID% 39771 % % FreeBSD Flyer % Gebruik make FORMAT (waar FORMAT: pdf, ps of dvi) om de flyer te bouwen. From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 13:28:52 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 569C88D6; Tue, 28 Jan 2014 13:28:52 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 432911D68; Tue, 28 Jan 2014 13:28:52 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SDSqMP085954; Tue, 28 Jan 2014 13:28:52 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SDSqRu085953; Tue, 28 Jan 2014 13:28:52 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281328.s0SDSqRu085953@svn.freebsd.org> From: Remko Lodder <remko@FreeBSD.org> Date: Tue, 28 Jan 2014 13:28:52 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43667 - head/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 28 Jan 2014 13:28:52 -0000 Author: remko Date: Tue Jan 28 13:28:51 2014 New Revision: 43667 URL: http://svnweb.freebsd.org/changeset/doc/43667 Log: Some minor whitespace cleanup. Remove empty lines and make sure the authorgroup is consistent with other entries. Modified: head/share/xml/bibliography.xml Modified: head/share/xml/bibliography.xml ============================================================================== --- head/share/xml/bibliography.xml Tue Jan 28 12:31:44 2014 (r43666) +++ head/share/xml/bibliography.xml Tue Jan 28 13:28:51 2014 (r43667) @@ -258,9 +258,6 @@ </biblioset> </biblioentry> - - - <biblioentry xml:id="biblio-ja-fbsdpc98"> <biblioset relation="book"> <citetitle>FreeBSD for PC 98'ers (in Japanese)</citetitle> @@ -338,10 +335,13 @@ <publishername>Elex Media Komputindo</publishername> </publisher> <authorgroup> - <author><personname><firstname>Onno W</firstname><surname>Purbo</surname></personname></author> - <author><personname><firstname>Dodi</firstname><surname>Maryanto</surname></personname></author> - <author><personname><firstname>Syahrial</firstname><surname>Hubbany</surname></personname></author> - <author><personname><firstname>Widjil</firstname><surname>Widodo</surname></personname></author> + <author><personname><firstname>Onno W</firstname><surname>Purbo</surname></personname></author> + + <author><personname><firstname>Dodi</firstname><surname>Maryanto</surname></personname></author> + + <author><personname><firstname>Syahrial</firstname><surname>Hubbany</surname></personname></author> + + <author><personname><firstname>Widjil</firstname><surname>Widodo</surname></personname></author> </authorgroup> </biblioset> </biblioentry> From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 13:29:19 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4365935; Tue, 28 Jan 2014 13:29:19 +0000 (UTC) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [IPv6:2a01:4f8:141:5ffd::25]) by mx1.freebsd.org (Postfix) with ESMTP id 634D31D6A; Tue, 28 Jan 2014 13:29:19 +0000 (UTC) Received: from scn-lan63.snowcn.snow.nl (gw.snow.nl [213.154.248.74]) by mail.jr-hosting.nl (Postfix) with ESMTPSA id E074F3F64D; Tue, 28 Jan 2014 14:29:17 +0100 (CET) From: Remko Lodder <remko@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_399A6DB4-5B99-414D-8B86-78D983374D0F"; protocol="application/pgp-signature"; micalg=pgp-sha1 Message-Id: <807A58F4-2AE3-4A05-AB63-BFD604032411@FreeBSD.org> Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: svn commit: r43667 - head/share/xml Date: Tue, 28 Jan 2014 14:29:16 +0100 References: <201401281328.s0SDSqRu085953@svn.freebsd.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org In-Reply-To: <201401281328.s0SDSqRu085953@svn.freebsd.org> X-Mailer: Apple Mail (2.1827) X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 28 Jan 2014 13:29:20 -0000 --Apple-Mail=_399A6DB4-5B99-414D-8B86-78D983374D0F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 28 Jan 2014, at 14:28, Remko Lodder <remko@FreeBSD.org> wrote: > Author: remko > Date: Tue Jan 28 13:28:51 2014 > New Revision: 43667 > URL: http://svnweb.freebsd.org/changeset/doc/43667 >=20 > Log: > Some minor whitespace cleanup. Remove empty lines and > make sure the authorgroup is consistent with other entries. Facilitated by: Snow B.V. >=20 > Modified: > head/share/xml/bibliography.xml >=20 > Modified: head/share/xml/bibliography.xml > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > --- head/share/xml/bibliography.xml Tue Jan 28 12:31:44 2014 = (r43666) > +++ head/share/xml/bibliography.xml Tue Jan 28 13:28:51 2014 = (r43667) > @@ -258,9 +258,6 @@ > </biblioset> > </biblioentry> >=20 > - > - > - > <biblioentry xml:id=3D"biblio-ja-fbsdpc98"> > <biblioset relation=3D"book"> > <citetitle>FreeBSD for PC 98'ers (in Japanese)</citetitle> > @@ -338,10 +335,13 @@ > <publishername>Elex Media Komputindo</publishername> > </publisher> > <authorgroup> > - <author><personname><firstname>Onno = W</firstname><surname>Purbo</surname></personname></author> > - = <author><personname><firstname>Dodi</firstname><surname>Maryanto</surname>= </personname></author> > - = <author><personname><firstname>Syahrial</firstname><surname>Hubbany</surna= me></personname></author> > - = <author><personname><firstname>Widjil</firstname><surname>Widodo</surname>= </personname></author> > + <author><personname><firstname>Onno = W</firstname><surname>Purbo</surname></personname></author> > + > + = <author><personname><firstname>Dodi</firstname><surname>Maryanto</surname>= </personname></author> > + > + = <author><personname><firstname>Syahrial</firstname><surname>Hubbany</surna= me></personname></author> > + > + = <author><personname><firstname>Widjil</firstname><surname>Widodo</surname>= </personname></author> > </authorgroup> > </biblioset> > </biblioentry> --=20 /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News --Apple-Mail=_399A6DB4-5B99-414D-8B86-78D983374D0F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJS57CsAAoJEKjD27JZ84ywKQcQAJo4R9AQ3WqY+Ks0lTs+6D1J 5LXmO1/88iYcoKavlLtKspuILpW6cNKTE/m6PJlF8+M1GV98tnt5OYR36HDwefdH ai4xa3XCyy3Li600mPLdMSIyc8tXB5s74gTeWR7JqPZ3xsPOw+FqjU7zi9PFSg5F jiKawkJxl/nATCAgEkIX4zQUGc9GTnVSSlvEEH+HgOilZgoQoV7ymOZh5qYWwxKn zJEJyyIKcfPRRBeIdhBMn5Zw4lgj4o+CX7nFQfCZIVfrwrX4+mi/8LoNn3HdSWpn llNoMKBI4UbR9fd0S+bWPZF6jqyJ9xvc1YwLjkGofsRGY4r2gfouA/KdehT4ObuF 9HqPMrzNa4wmgZPLnVP/pSm8PYq8L5hLyL+hLMvO+vQ2t+5IongDSDrEaNn60yh8 Pfxs2QBXs633q6SzCDM+fxjQrHEpd08bctRa59DKLokzLyNB4/37rnO+a1BsRfVe wDcaQRWVVLEdAC/gBPFKNXYXEakShIiJ7gM1L4tBvwuLIqN0j0u0cTKljWf4dZSD tRx41ZUkGKDVPGETdCm5Ri6EPFKKzqZV4L/yvP1Z2zoFjeltyRAYSjkUQS06aU1y /E8HMIFiiJ3Kkzq1OLb8e2OgqxVIffG7kIri9/ukl2iRgsL7GivvLQYEtYjZe/Pp 2kjkkJSQewi5FhxXTjl7 =o0LQ -----END PGP SIGNATURE----- --Apple-Mail=_399A6DB4-5B99-414D-8B86-78D983374D0F-- From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 13:32:37 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D446CDF; Tue, 28 Jan 2014 13:32:37 +0000 (UTC) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [IPv6:2a01:4f8:141:5ffd::25]) by mx1.freebsd.org (Postfix) with ESMTP id D21CA1DEB; Tue, 28 Jan 2014 13:32:36 +0000 (UTC) Received: from scn-lan63.snowcn.snow.nl (gw.snow.nl [213.154.248.74]) by mail.jr-hosting.nl (Postfix) with ESMTPSA id 587B93F64D; Tue, 28 Jan 2014 14:32:35 +0100 (CET) From: Remko Lodder <remko@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_AA792E2B-EDAB-4EA9-92BB-2BF331773458"; protocol="application/pgp-signature"; micalg=pgp-sha1 Message-Id: <9F259363-7F12-4362-84F6-4B4A09FBBB05@FreeBSD.org> Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: svn commit: r43667 - head/share/xml Date: Tue, 28 Jan 2014 14:32:34 +0100 References: <201401281328.s0SDSqRu085953@svn.freebsd.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org In-Reply-To: <201401281328.s0SDSqRu085953@svn.freebsd.org> X-Mailer: Apple Mail (2.1827) X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 28 Jan 2014 13:32:37 -0000 --Apple-Mail=_AA792E2B-EDAB-4EA9-92BB-2BF331773458 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 28 Jan 2014, at 14:28, Remko Lodder <remko@FreeBSD.org> wrote: > Author: remko > Date: Tue Jan 28 13:28:51 2014 > New Revision: 43667 > URL: http://svnweb.freebsd.org/changeset/doc/43667 >=20 > Log: > Some minor whitespace cleanup. Remove empty lines and > make sure the authorgroup is consistent with other entries. This might need a little more work for all entries to be more consistent = with eachother, and to be more conform the FDP (which is needless to say not = really the case now :-)) Cheers remko >=20 > Modified: > head/share/xml/bibliography.xml >=20 > Modified: head/share/xml/bibliography.xml > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > --- head/share/xml/bibliography.xml Tue Jan 28 12:31:44 2014 = (r43666) > +++ head/share/xml/bibliography.xml Tue Jan 28 13:28:51 2014 = (r43667) > @@ -258,9 +258,6 @@ > </biblioset> > </biblioentry> >=20 > - > - > - > <biblioentry xml:id=3D"biblio-ja-fbsdpc98"> > <biblioset relation=3D"book"> > <citetitle>FreeBSD for PC 98'ers (in Japanese)</citetitle> > @@ -338,10 +335,13 @@ > <publishername>Elex Media Komputindo</publishername> > </publisher> > <authorgroup> > - <author><personname><firstname>Onno = W</firstname><surname>Purbo</surname></personname></author> > - = <author><personname><firstname>Dodi</firstname><surname>Maryanto</surname>= </personname></author> > - = <author><personname><firstname>Syahrial</firstname><surname>Hubbany</surna= me></personname></author> > - = <author><personname><firstname>Widjil</firstname><surname>Widodo</surname>= </personname></author> > + <author><personname><firstname>Onno = W</firstname><surname>Purbo</surname></personname></author> > + > + = <author><personname><firstname>Dodi</firstname><surname>Maryanto</surname>= </personname></author> > + > + = <author><personname><firstname>Syahrial</firstname><surname>Hubbany</surna= me></personname></author> > + > + = <author><personname><firstname>Widjil</firstname><surname>Widodo</surname>= </personname></author> > </authorgroup> > </biblioset> > </biblioentry> --=20 /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News --Apple-Mail=_AA792E2B-EDAB-4EA9-92BB-2BF331773458 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJS57FyAAoJEKjD27JZ84ywilMP/jZqmQF7jSiRI5GzvHr8YYgD dJCYrKd/hl8gL709svM4Mz/8hE5PeXR3dEd+39fc89GwJRu7QjyrEHYFfpMwQ+0i 1/u9vt3wMasbNDN5BfyD/190xvMxDaMwG3zKY2qstTjbA6ZIk6QV0MSjE0eXyHUm YK7NR5GpF1j9CP5exWRz5IsUsAJP0SwQbJLJlCBDwQpXhDGpOnY/GDmU09iXHyo8 pu9ky/5aR4hZN5iUSa9igfOKKNE1mCevsiapH0HWJuL+CtDX5bGkb099d727oAh0 yBiMTr5OsLcjcWsTtyN/ooR/m/Z5iM2t0CVdI5MtbhMfwNrqTPnyFniu0PDfyrf6 BSEKMj2FCcursg0vUV2nY8EAJ7JOpXLO3hMvh+Cxc4DN4wGSiXebc84oXFte7HI5 o+eMPTuGmHUR8L3IEFu9UUH5+p9z9W3mEvMQ9/oCb+dmW0cuoN8oUvM+PuBGhXN+ 3AY8LVKmrOeHb8fZdAYVDiUMQBkuyzJGmnlKcOE+xZCWsx4Pau8UlWeQhL5F1J7I etmYOYCSuCQfMWGwaw1gGupvQkl2fEn68u413Rvmx2NR2BphBU8TzIjjlWAZIrx5 cL1vRZXxqC2/zNn8BYnav62tqoV3scPHcwVf+uFOKRPNNmD+9AY/sExfTlKWg0W4 Tn6OvKNlroBDpcqYorDl =rMnZ -----END PGP SIGNATURE----- --Apple-Mail=_AA792E2B-EDAB-4EA9-92BB-2BF331773458-- From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 13:45:44 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41780B51; Tue, 28 Jan 2014 13:45:44 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2C8621EF9; Tue, 28 Jan 2014 13:45:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SDjiuD094390; Tue, 28 Jan 2014 13:45:44 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SDji4j094389; Tue, 28 Jan 2014 13:45:44 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281345.s0SDji4j094389@svn.freebsd.org> From: Remko Lodder <remko@FreeBSD.org> Date: Tue, 28 Jan 2014 13:45:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43668 - translations/nl_NL.ISO8859-1/share/xml X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 28 Jan 2014 13:45:44 -0000 Author: remko Date: Tue Jan 28 13:45:43 2014 New Revision: 43668 URL: http://svnweb.freebsd.org/changeset/doc/43668 Log: Minor cleanup as with the English version, bump revision date, this document is on-par with the English version. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/share/xml/bibliography.xml Modified: translations/nl_NL.ISO8859-1/share/xml/bibliography.xml ============================================================================== --- translations/nl_NL.ISO8859-1/share/xml/bibliography.xml Tue Jan 28 13:28:51 2014 (r43667) +++ translations/nl_NL.ISO8859-1/share/xml/bibliography.xml Tue Jan 28 13:45:43 2014 (r43668) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% share/xml/bibliography.xml - %SRCID% 41645 + %SRCID% 43633 --> <bibliography xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="bibliography"> <title>Bibliografie @@ -344,8 +344,11 @@ Onno WPurbo + DodiMaryanto + SyahrialHubbany + WidjilWidodo From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 13:57:27 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 33BB8ECA; Tue, 28 Jan 2014 13:57:27 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0679C1FC2; Tue, 28 Jan 2014 13:57:27 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SDvQ5R098385; Tue, 28 Jan 2014 13:57:26 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SDvQhv098384; Tue, 28 Jan 2014 13:57:26 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281357.s0SDvQhv098384@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 13:57:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43669 - translations/nl_NL.ISO8859-1/books/handbook/vinum X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 13:57:27 -0000 Author: remko Date: Tue Jan 28 13:57:26 2014 New Revision: 43669 URL: http://svnweb.freebsd.org/changeset/doc/43669 Log: Remove the Vinum chapter, Makefile and directory. It is no longer used. Facilitated by: Snow B.V. Deleted: translations/nl_NL.ISO8859-1/books/handbook/vinum/ From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 14:14:16 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2AF6A1E; Tue, 28 Jan 2014 14:14:16 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9DC391160; Tue, 28 Jan 2014 14:14:16 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SEEGIe006912; Tue, 28 Jan 2014 14:14:16 GMT (envelope-from skreuzer@svn.freebsd.org) Received: (from skreuzer@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SEEGLo006911; Tue, 28 Jan 2014 14:14:16 GMT (envelope-from skreuzer@svn.freebsd.org) Message-Id: <201401281414.s0SEEGLo006911@svn.freebsd.org> From: Steven Kreuzer Date: Tue, 28 Jan 2014 14:14:16 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43670 - head/en_US.ISO8859-1/books/handbook/mac X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 14:14:16 -0000 Author: skreuzer Date: Tue Jan 28 14:14:16 2014 New Revision: 43670 URL: http://svnweb.freebsd.org/changeset/doc/43670 Log: The nagios-plugins and nagios ports are found under net-mgmt, not net-mngt Approved by: hrs (mentor) Modified: head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/mac/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Tue Jan 28 13:57:26 2014 (r43669) +++ head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Tue Jan 28 14:14:16 2014 (r43670) @@ -1534,8 +1534,8 @@ test: biba/low Before beginning this process, must be set on each file system as not doing so will result in - errors. This example assumes that net-mngt/nagios-plugins, - net-mngt/nagios, and + errors. This example assumes that net-mgmt/nagios-plugins, + net-mgmt/nagios, and www/apache22 are all installed, configured, and working correctly. From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 14:50:42 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 33D834C5; Tue, 28 Jan 2014 14:50:42 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2002814E1; Tue, 28 Jan 2014 14:50:42 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SEof7m023875; Tue, 28 Jan 2014 14:50:41 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SEofrs023874; Tue, 28 Jan 2014 14:50:41 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281450.s0SEofrs023874@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 14:50:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43671 - translations/nl_NL.ISO8859-1/share/xml X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 14:50:42 -0000 Author: remko Date: Tue Jan 28 14:50:41 2014 New Revision: 43671 URL: http://svnweb.freebsd.org/changeset/doc/43671 Log: Update the glossary to be on-par with the English version. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/share/xml/glossary.ent Modified: translations/nl_NL.ISO8859-1/share/xml/glossary.ent ============================================================================== --- translations/nl_NL.ISO8859-1/share/xml/glossary.ent Tue Jan 28 14:14:16 2014 (r43670) +++ translations/nl_NL.ISO8859-1/share/xml/glossary.ent Tue Jan 28 14:50:41 2014 (r43671) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/share/xml/glossary.ent - %SRCID% 39534 + %SRCID% 43633 FreeBSD begrippenlijst Houd dit bestand alstublieft alfabetisch/ASCII gesorteerd op @@ -22,7 +22,7 @@ - + Fucked Up Beyond All Recognition FUBAR From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 14:52:21 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6773A532; Tue, 28 Jan 2014 14:52:21 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5350514E8; Tue, 28 Jan 2014 14:52:21 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SEqLDF024983; Tue, 28 Jan 2014 14:52:21 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SEqLcb024982; Tue, 28 Jan 2014 14:52:21 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281452.s0SEqLcb024982@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 14:52:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43672 - translations/nl_NL.ISO8859-1/books/handbook X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 14:52:21 -0000 Author: remko Date: Tue Jan 28 14:52:20 2014 New Revision: 43672 URL: http://svnweb.freebsd.org/changeset/doc/43672 Log: Update book.xml to be on-par with the English version. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/books/handbook/book.xml Modified: translations/nl_NL.ISO8859-1/books/handbook/book.xml ============================================================================== --- translations/nl_NL.ISO8859-1/books/handbook/book.xml Tue Jan 28 14:50:41 2014 (r43671) +++ translations/nl_NL.ISO8859-1/books/handbook/book.xml Tue Jan 28 14:52:20 2014 (r43672) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/book.xml - %SRCID% 42118 + %SRCID% 43633 --> @@ -68,14 +68,11 @@ &tm-attrib.linux; &tm-attrib.lsilogic; &tm-attrib.m-systems; - &tm-attrib.macromedia; &tm-attrib.microsoft; - &tm-attrib.nexthop; &tm-attrib.opengroup; &tm-attrib.oracle; &tm-attrib.realnetworks; &tm-attrib.redhat; - &tm-attrib.sap; &tm-attrib.sun; &tm-attrib.themathworks; &tm-attrib.thomson; @@ -225,7 +222,6 @@ &chap.config; &chap.boot; - &chap.users; &chap.security; &chap.jails; &chap.mac; From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 14:53:25 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5918259B; Tue, 28 Jan 2014 14:53:25 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4546314F5; Tue, 28 Jan 2014 14:53:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SErPPw025287; Tue, 28 Jan 2014 14:53:25 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SErP6e025286; Tue, 28 Jan 2014 14:53:25 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281453.s0SErP6e025286@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 14:53:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43673 - translations/nl_NL.ISO8859-1/books/handbook X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 14:53:25 -0000 Author: remko Date: Tue Jan 28 14:53:24 2014 New Revision: 43673 URL: http://svnweb.freebsd.org/changeset/doc/43673 Log: Remove users/ from the build and bump revision date to match the proper version. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/books/handbook/Makefile Modified: translations/nl_NL.ISO8859-1/books/handbook/Makefile ============================================================================== --- translations/nl_NL.ISO8859-1/books/handbook/Makefile Tue Jan 28 14:52:20 2014 (r43672) +++ translations/nl_NL.ISO8859-1/books/handbook/Makefile Tue Jan 28 14:53:24 2014 (r43673) @@ -2,7 +2,7 @@ # $FreeBSD$ # # %SOURCE% en_US.ISO8859-1/books/handbook/Makefile -# %SRCID% 42118 +# %SRCID% 43633 # # Bouw het Nederlandse FreeBSD Handboek. # @@ -276,7 +276,6 @@ SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml -SRCS+= users/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 14:54:14 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6FDFA63D; Tue, 28 Jan 2014 14:54:14 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5BEBD14FF; Tue, 28 Jan 2014 14:54:14 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SEsE4x025542; Tue, 28 Jan 2014 14:54:14 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SEsE4E025541; Tue, 28 Jan 2014 14:54:14 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281454.s0SEsE4E025541@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 14:54:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43674 - translations/nl_NL.ISO8859-1/books/handbook X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 14:54:14 -0000 Author: remko Date: Tue Jan 28 14:54:13 2014 New Revision: 43674 URL: http://svnweb.freebsd.org/changeset/doc/43674 Log: Remove the Users chapter, it will be gone soon-ish. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/books/handbook/chapters.ent Modified: translations/nl_NL.ISO8859-1/books/handbook/chapters.ent ============================================================================== --- translations/nl_NL.ISO8859-1/books/handbook/chapters.ent Tue Jan 28 14:53:24 2014 (r43673) +++ translations/nl_NL.ISO8859-1/books/handbook/chapters.ent Tue Jan 28 14:54:13 2014 (r43674) @@ -11,7 +11,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/chapters.ent - %SRCID% 42118 + %SRCID% 43633 --> @@ -35,7 +35,6 @@ - From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 14:55:18 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F247E78F; Tue, 28 Jan 2014 14:55:17 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DCF3D1511; Tue, 28 Jan 2014 14:55:17 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SEtHEa025770; Tue, 28 Jan 2014 14:55:17 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SEtHws025769; Tue, 28 Jan 2014 14:55:17 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281455.s0SEtHws025769@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 14:55:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43675 - translations/nl_NL.ISO8859-1/books/handbook/preface X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 14:55:18 -0000 Author: remko Date: Tue Jan 28 14:55:17 2014 New Revision: 43675 URL: http://svnweb.freebsd.org/changeset/doc/43675 Log: Before the users chapter can be removed, preface should also be updated since that references the users chapter. Next to that it was hungry for some updates so make it on-par with the English version. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/books/handbook/preface/preface.xml Modified: translations/nl_NL.ISO8859-1/books/handbook/preface/preface.xml ============================================================================== --- translations/nl_NL.ISO8859-1/books/handbook/preface/preface.xml Tue Jan 28 14:54:13 2014 (r43674) +++ translations/nl_NL.ISO8859-1/books/handbook/preface/preface.xml Tue Jan 28 14:55:17 2014 (r43675) @@ -6,7 +6,7 @@ Vertaald door: Remko Lodder %SOURCE% en_US.ISO8859-1/books/handbook/preface/preface.xml - %SRCID% 42118 + %SRCID% 43633 --> Voorwoord @@ -42,32 +42,32 @@ - , &dtrace;, is toegevoegd met + , is toegevoegd met informatie over het krachtige prestatie-analysegereedschap &dtrace;. - , Ondersteuning voor - bestandssystemen, is toegevoegd met informatie over vreemde + , + is toegevoegd met informatie over vreemde bestandssystemen in &os;, zoals ZFS van &sun;. - , Beveiliginsgebeurtenissen auditen, + , is toegevoegd om de nieuwe auditing-mogelijkheden van &os; te bespreken en het gebruik ervan uit te leggen. - , Virtualisatie, is + , is toegevoegd met informatie over het installeren van &os; op virtualisatiesoftware. , - &os; 9.X en nieuwer installeren, is + is toegevoegd om het installeren van &os; met het nieuwe installatiegereedschap, bsdinstall te behandelen. @@ -85,41 +85,41 @@ - , Instellingen en - optimalisatie, is uitgebreid met nieuwe informatie over ACPI + , + is uitgebreid met nieuwe informatie over ACPI power en resource management, het systeemhulpprogramma cron en er staan meer opties voor het optimaliseren van de kernel beschreven. - , Beveiliging, is uitgebreid met + , is uitgebreid met meer informatie over virtuele private netwerken (VPN's), toegangscontrolelijsten voor het bestandssysteem (ACL's) en beveiligingswaarschuwingen. - , Verplichte toegangscontrole (MAC), + , is een nieuw hoofdstuk in deze editie. Er wordt in uitgelegd wat MAC is en hoe het gebruikt kan worden om &os; te beveiligen. - , Opslag, is uitgebreid met + , is uitgebreid met informatie over USB opslagapparaten, snapshots van bestandssystemen, bestandssystemen op basis van bestanden en het netwerk en versleutelde partities op schijven. - Aan , PPP en SLIP, is een + Aan ,is een paragraaf toegevoegd over problemen oplossen. - , E-mail, is uitgebreid met + , is uitgebreid met informatie over alternatieve transport programma's, SMTP authenticatie, UUCP, fetchmail, procmail en een aantal andere @@ -127,21 +127,21 @@ - , Netwerkdiensten, is + ,is nieuw in deze editie. Dit hoofdstuk bevat informatie over het opzetten van een Apache HTTP Server, ftpd en het opzetten van een server voor µsoft; &windows; clients met Samba. Een aantal paragrafen - uit , Geavanceerde - Netwerken, zijn om reden van presentatie naar dit hoofdstuk + uit , + zijn om reden van presentatie naar dit hoofdstuk verplaatst. - , Netwerken voor - gevorderden, is uitgebreid met informatie over het gebruik + , + is uitgebreid met informatie over het gebruik van &bluetooth; apparaten met &os;, het opzetten van draadloze netwerken en Asynchronous Transfer Mode (ATM) netwerken. @@ -188,26 +188,26 @@ - (&os; - installeren) is compleet herschreven met veel + + is compleet herschreven met veel schermafdrukken erbij om het makkelijker te maken voor nieuwe gebruikers om greep te krijgen op de tekst. - (&unix; - beginselen) is uitgebreid met extra informatie over + + is uitgebreid met extra informatie over processen, daemons en signalen. - (Applicaties - installeren) is uitgebreid met extra informatie over + + is uitgebreid met extra informatie over binair package-beheer. - (Het X Window systeem) + is compleet herschreven met de nadruk op het gebruik van moderne bureaubladtechnologiën zoals KDE en @@ -215,12 +215,12 @@ - (Het &os; - Opstartproces) is uitgebreid. + + is uitgebreid. - (Opslag) is + is herschreven uit wat eens twee aparte hoofdstukken waren over schijven en back-ups. We vinden dat de onderwerpen beter begrijpbaar zijn wanneer ze in @@ -230,31 +230,29 @@ - (Seriële - communicatie) is compleet gereorganiseerd en + + is compleet gereorganiseerd en bijgewerkt voor &os; 4.X/5.X. - (PPP en SLIP) + is aanzienlijk bijgewerkt. Veel nieuwe secties zijn toegevoegd aan - (Geavanceerd - netwerken). + . - (E-mail) + is uitgebreid met meer informatie over het instellen van sendmail. - ( &linux; binaire compatibiliteit) is uitgebreid met informatie over het installeren van &oracle;. @@ -265,12 +263,11 @@ - Instellingen en optimalisatie - (). + . - Multimedia () + @@ -301,8 +298,7 @@ - , - Introductie + Introduceert &os; aan een nieuwe gebruiker. Het @@ -312,32 +308,29 @@ - , Installatie van - &os; 8.X en eerder + Begeleidt de gebruiker door het gehele installatieproces van - &os; 8.X en eerder door middel van - sysinstall. Sommige geavanceerde - onderwerpen over installeren, zoals installeren via een seriële - console, worden ook behandeld. + &os; 9.X en later door middel van + bsdinstall. - , Installatie van - &os; 9.X en nieuwer + Begeleidt een gebruiker door het gehele installatieproces van - &os; 9.X en nieuwer door middel van - bsdinstall. + &os; 8.X en ouder door middel van + sysinstall. Sommige geavanceerde + installatiemethoden zoals installatie over een seriele + verbinding komen aan bod. - , &unix; - beginselen + Behandelt de basiscommando's en functionaliteit van het @@ -348,8 +341,7 @@ - , Applicaties - installeren + Behandelt de installatie van software van derden, met @@ -359,13 +351,12 @@ - , Het X Window - systeem + Beschrijft het X Window systeem in het algemeen en het gebruik van X11 op &os; in het bijzonder. Het beschrijft - ook standaard bureaubladomgevingen zoals + standaard bureaubladomgevingen zoals KDE en GNOME. @@ -375,8 +366,7 @@ - , - Bureaubladapplicaties + Levert standaard bureaubladapplicaties in een lijst, @@ -386,8 +376,7 @@ - , - Multimedia + Laat zien hoe geluid- en video-ondersteuning te @@ -397,8 +386,7 @@ - , Instellen van de - &os; kernel + Beschrijft waarom misschien een nieuwe kernel ingesteld @@ -408,8 +396,7 @@ - , - Afdrukken + Beschrijft hoe printers beheerd worden onder &os;, @@ -419,8 +406,7 @@ - , &linux; binaire - compatibiliteit + Beschrijft de mogelijkheden van &os; voor binaire @@ -435,8 +421,7 @@ - , Instellingen en - optimalisatie + Beschrijft de parameters beschikbaar voor @@ -448,8 +433,7 @@ - , Het &os; - opstartproces + Beschrijft de &os; opstartprocedure en legt uit hoe @@ -458,20 +442,7 @@ - , Gebruikers en basis - accountbeheer - - - Beschrijft hoe gebruikersaccounts aan te maken en te - wijzigen. Het beschrijft ook welke resourcebeperkingen er - gezet kunnen worden op gebruikers en andere - account-beheerstaken. - - - - - , - Beveiliging + Beschrijft vele verschillende hulpapplicaties die @@ -481,7 +452,7 @@ - , Jails + Beschrijft het jail-raamwerk, en de verbeteringen van @@ -491,8 +462,7 @@ - , Verplichte - Toegangscontrole (MAC) + Legt uit was Verplichte Toegangscontrole (MAC) is en hoe @@ -501,8 +471,7 @@ - , Security Event - Auditing + Beschrijft wat &os; Event Auditing is, hoe het @@ -512,7 +481,7 @@ - , Opslag + Beschrijft hoe opslagmedia en bestandssystemen beheerd @@ -523,8 +492,7 @@ - , - GEOM + Beschrijft wat het GEOM raamwerk in &os; is en hoe de @@ -534,8 +502,7 @@ - , Ondersteuning van - bestandssystemen + Gaat de ondersteuning voor vreemde bestandssystemen in @@ -544,8 +511,7 @@ - , - Virtualisatie + Beschrijft wat virtualisatiesystemen bieden, en hoe ze met @@ -554,9 +520,7 @@ - , - Lokalisatie - I18N/L10N gebruiken en - instellen + Beschrijft hoe &os; met andere talen dan Engels te @@ -566,8 +530,7 @@ - , &os; updaten - en upgraden + Geeft uitleg over de verschillen tussen &os;-STABLE, @@ -580,7 +543,7 @@ - , &dtrace; + Beschrijft hoe het gereedschap &dtrace; van &sun; te @@ -593,8 +556,7 @@ - , Seriële - communicatie + Legt uit hoe een verbinding te maken met terminals en @@ -604,18 +566,17 @@ - , PPP en - SLIP + - Beschrijft hoe PPP, SLIP en PPP over Ethernet te + Beschrijft hoe PPP te gebruiken om verbinding te maken met remote systemen met &os;. - , E-mail + Legt verschillende componenten uit van een mailserver en @@ -626,8 +587,7 @@ - , - Netwerkdiensten + Geeft gedetailleerde instructies en voorbeeldinstellingen @@ -638,8 +598,7 @@ - , - Firewalls + Licht de filosofie achter op software gebaseerde @@ -650,8 +609,7 @@ - , Netwerken - voor gevorderden + Beschrijft meerdere netwerk onderwerpen, inclusief @@ -664,8 +622,7 @@ - , &os; - verkrijgen + Geeft verschillende bronnen aan voor het verkrijgen van @@ -676,8 +633,7 @@ - , - Bibliografie + Dit boek behandelt veel verschillende onderwerpen die de @@ -688,8 +644,7 @@ - , Bronnen op - Internet + Beschrijft de vele forums die beschikbaar zijn voor &os; @@ -699,8 +654,7 @@ - , PGP - sleutels + Geeft de PGP-vingerafdrukken van verschillende &os; @@ -781,7 +735,7 @@ Voorbeelden - Voorbeelden die beginnen met E:\> + Voorbeelden die beginnen met C:\> geven aan dat het een &ms-dos; commando betreft. Tenzij anders vermeld, kunnen deze commando's in een Command promptscherm in een moderne µsoft.windows; omgeving From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 14:58:24 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 121068F8; Tue, 28 Jan 2014 14:58:24 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D8305153F; Tue, 28 Jan 2014 14:58:23 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SEwNxD026129; Tue, 28 Jan 2014 14:58:23 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SEwNIN026128; Tue, 28 Jan 2014 14:58:23 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281458.s0SEwNIN026128@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 14:58:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43676 - translations/nl_NL.ISO8859-1/books/handbook/users X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 14:58:24 -0000 Author: remko Date: Tue Jan 28 14:58:23 2014 New Revision: 43676 URL: http://svnweb.freebsd.org/changeset/doc/43676 Log: Really remove the handbook/users chapter. Facilitated by: Snow B.V. Deleted: translations/nl_NL.ISO8859-1/books/handbook/users/ From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 14:58:49 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDD8F952; Tue, 28 Jan 2014 14:58:49 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B93981543; Tue, 28 Jan 2014 14:58:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SEwnwY026198; Tue, 28 Jan 2014 14:58:49 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SEwnhc026197; Tue, 28 Jan 2014 14:58:49 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281458.s0SEwnhc026197@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 14:58:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43677 - translations/nl_NL.ISO8859-1/books X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 14:58:49 -0000 Author: remko Date: Tue Jan 28 14:58:49 2014 New Revision: 43677 URL: http://svnweb.freebsd.org/changeset/doc/43677 Log: Bump listed version, it is on-par with the current version. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/books/Makefile Modified: translations/nl_NL.ISO8859-1/books/Makefile ============================================================================== --- translations/nl_NL.ISO8859-1/books/Makefile Tue Jan 28 14:58:23 2014 (r43676) +++ translations/nl_NL.ISO8859-1/books/Makefile Tue Jan 28 14:58:49 2014 (r43677) @@ -1,7 +1,7 @@ # $FreeBSD$ # # %SOURCE% en_US.ISO8859-1/books/Makefile -# %SRCID% 40258 +# %SRCID% 43633 # SUBDIR = handbook From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 15:00:49 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67481AA0; Tue, 28 Jan 2014 15:00:49 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 52F2B15C4; Tue, 28 Jan 2014 15:00:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SF0njs027382; Tue, 28 Jan 2014 15:00:49 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SF0nE4027381; Tue, 28 Jan 2014 15:00:49 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281500.s0SF0nE4027381@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 15:00:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43678 - translations/nl_NL.ISO8859-1/books/handbook/jails X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 15:00:49 -0000 Author: remko Date: Tue Jan 28 15:00:48 2014 New Revision: 43678 URL: http://svnweb.freebsd.org/changeset/doc/43678 Log: Bump listed revision number, it is on-par with the English version. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/books/handbook/jails/Makefile Modified: translations/nl_NL.ISO8859-1/books/handbook/jails/Makefile ============================================================================== --- translations/nl_NL.ISO8859-1/books/handbook/jails/Makefile Tue Jan 28 14:58:49 2014 (r43677) +++ translations/nl_NL.ISO8859-1/books/handbook/jails/Makefile Tue Jan 28 15:00:48 2014 (r43678) @@ -4,7 +4,7 @@ # $FreeBSD$ # # %SOURCE% en_US.ISO8859-1/books/handbook/jails/Makefile -# %SRCID% 39829 +# %SRCID% 43633 # # From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 15:12:18 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5FCFFE3B; Tue, 28 Jan 2014 15:12:18 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 48FFA1688; Tue, 28 Jan 2014 15:12:18 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SFCIGn033675; Tue, 28 Jan 2014 15:12:18 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SFCIJC033674; Tue, 28 Jan 2014 15:12:18 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201401281512.s0SFCIJC033674@svn.freebsd.org> From: Remko Lodder Date: Tue, 28 Jan 2014 15:12:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r43679 - translations/nl_NL.ISO8859-1/share/xml X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 15:12:18 -0000 Author: remko Date: Tue Jan 28 15:12:17 2014 New Revision: 43679 URL: http://svnweb.freebsd.org/changeset/doc/43679 Log: Bump entities revision and refer to the correct entities file which is under en_US.ISO8859-1 rather then under the toplevel share/xml directory. Facilitated by: Snow B.V. Modified: translations/nl_NL.ISO8859-1/share/xml/entities.ent Modified: translations/nl_NL.ISO8859-1/share/xml/entities.ent ============================================================================== --- translations/nl_NL.ISO8859-1/share/xml/entities.ent Tue Jan 28 15:00:48 2014 (r43678) +++ translations/nl_NL.ISO8859-1/share/xml/entities.ent Tue Jan 28 15:12:17 2014 (r43679) @@ -2,7 +2,7 @@ The FreeBSD Dutch Documentation Project $FreeBSD$ - %SOURCE% share/xml/entities.ent + %SOURCE% en_US.ISO8859-1/share/xml/entities.ent %SRCID% 39534 --> From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 17:37:57 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F660E7D; Tue, 28 Jan 2014 17:37:57 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6B8AD1578; Tue, 28 Jan 2014 17:37:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SHbv7k092244; Tue, 28 Jan 2014 17:37:57 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SHbv57092243; Tue, 28 Jan 2014 17:37:57 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201401281737.s0SHbv57092243@svn.freebsd.org> From: Glen Barber Date: Tue, 28 Jan 2014 17:37:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43680 - head/en_US.ISO8859-1/books/handbook/install X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 17:37:57 -0000 Author: gjb Date: Tue Jan 28 17:37:56 2014 New Revision: 43680 URL: http://svnweb.freebsd.org/changeset/doc/43680 Log: Document the 'mini-memstick.img' file. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/install/chapter.xml Tue Jan 28 15:12:17 2014 (r43679) +++ head/en_US.ISO8859-1/books/handbook/install/chapter.xml Tue Jan 28 17:37:56 2014 (r43680) @@ -4530,6 +4530,18 @@ Please press any key to reboot. + &os;-version-RELEASE-arch-mini-memstick.img + + This image can be written to a USB memory + stick in order to install machines capable of + booting from USB drives. Similar to the + bootonly.iso image, it does + not contain the distribution sets on the medium + itself, but does support network-based + installations (for example, via ftp). + + + &os;-version-RELEASE-arch-disc1.iso This CD image contains the base &os; operating From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 17:38:34 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4C182EFF; Tue, 28 Jan 2014 17:38:34 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3781D1595; Tue, 28 Jan 2014 17:38:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SHcYL1092350; Tue, 28 Jan 2014 17:38:34 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SHcYV5092349; Tue, 28 Jan 2014 17:38:34 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201401281738.s0SHcYV5092349@svn.freebsd.org> From: Glen Barber Date: Tue, 28 Jan 2014 17:38:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43681 - head/en_US.ISO8859-1/books/handbook/install X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 17:38:34 -0000 Author: gjb Date: Tue Jan 28 17:38:33 2014 New Revision: 43681 URL: http://svnweb.freebsd.org/changeset/doc/43681 Log: Fix a small grammar nit: s/an/a/ Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/install/chapter.xml Tue Jan 28 17:37:56 2014 (r43680) +++ head/en_US.ISO8859-1/books/handbook/install/chapter.xml Tue Jan 28 17:38:33 2014 (r43681) @@ -4521,7 +4521,7 @@ Please press any key to reboot. &os;-version-RELEASE-arch-memstick.img - This image can be written to an USB memory stick + This image can be written to a USB memory stick in order to install machines capable of booting from USB drives. It also supports booting into a livefs based rescue mode. The only From owner-svn-doc-all@FreeBSD.ORG Tue Jan 28 19:21:14 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C14F64DD; Tue, 28 Jan 2014 19:21:14 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9371710AF; Tue, 28 Jan 2014 19:21:14 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0SJLEqs033910; Tue, 28 Jan 2014 19:21:14 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0SJLEZs033909; Tue, 28 Jan 2014 19:21:14 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201401281921.s0SJLEZs033909@svn.freebsd.org> From: Rene Ladan Date: Tue, 28 Jan 2014 19:21:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43682 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 19:21:14 -0000 Author: rene Date: Tue Jan 28 19:21:14 2014 New Revision: 43682 URL: http://svnweb.freebsd.org/changeset/doc/43682 Log: Document two new option helpers: - OPT_TYPE_DEPENDS_OFF to add a TYPE_DEPENDS when OPT is off - OPT_FLAG_OFF=VAL to add the VAL to FLAG when OPT is off Submitted by: mat Reviewed by: mat Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/book.xml Tue Jan 28 17:38:33 2014 (r43681) +++ head/en_US.ISO8859-1/books/porters-handbook/book.xml Tue Jan 28 19:21:14 2014 (r43682) @@ -4858,6 +4858,24 @@ USES+= gmake CFLAGS+= -DTEST .endif + If X_ABOVEVARIABLE_OFF is set then a + flag ABOVEVARIABLE will be automatically + set when option X is not selected. For + example: + + OPTIONS_DEFINE= OPT1 +OPT1_USES_OFF=gmake + + is equivalent to: + + OPTIONS_DEFINE= OPT1 + +.include <bsd.port.options.mk> + +.if ! ${PORT_OPTIONS:MOPT1} +USES+= gmake +.endif + For any of the following dependency type: @@ -4907,6 +4925,24 @@ OPT1_LIB_DEPENDS= liba.so:${PORTSDIR}/de .if ${PORT_OPTIONS:MOPT1} LIB_DEPENDS+= liba.so:${PORTSDIR}/devel/a .endif + + If X_ABOVEVARIABLE_OFF is set then a + dependency of type ABOVEVARIABLE will be + added when option X is not selected. For + example: + + OPTIONS_DEFINE= OPT1 +OPT1_LIB_DEPENDS_OFF= liba.so:${PORTSDIR}/devel/a + + is equivalent to: + + OPTIONS_DEFINE= OPT1 + +.include <bsd.port.options.mk> + +. if ! ${PORT_OPTIONS:MOPT1} +LIB_DEPENDS+= liba.so:${PORTSDIR}/devel/a +.endif From owner-svn-doc-all@FreeBSD.ORG Wed Jan 29 11:57:44 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 45971EE1; Wed, 29 Jan 2014 11:57:44 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 314C61076; Wed, 29 Jan 2014 11:57:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0TBviLP024549; Wed, 29 Jan 2014 11:57:44 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0TBvhZD024548; Wed, 29 Jan 2014 11:57:43 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201401291157.s0TBvhZD024548@svn.freebsd.org> From: Ryusuke SUZUKI Date: Wed, 29 Jan 2014 11:57:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43683 - head/ja_JP.eucJP/books/handbook/install X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 11:57:44 -0000 Author: ryusuke Date: Wed Jan 29 11:57:43 2014 New Revision: 43683 URL: http://svnweb.freebsd.org/changeset/doc/43683 Log: - Merge the following from the English version: r42409 -> r43681 head/ja_JP.eucJP/books/handbook/install/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/install/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/install/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/install/chapter.xml Tue Jan 28 19:21:14 2014 (r43682) +++ head/ja_JP.eucJP/books/handbook/install/chapter.xml Wed Jan 29 11:57:43 2014 (r43683) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r42409 + Original revision: r43681 $FreeBSD$ --> @@ -4458,6 +4458,18 @@ Please press any key to reboot. + &os;-version-RELEASE-arch-mini-memstick.img + + USB ¥á¥â¥ê¥¹¥Æ¥£¥Ã¥¯¤Ë½ñ¤­¹þ¤á¤ë¥¤¥á¡¼¥¸¤Ç¤¹¡£ + USB ¥É¥é¥¤¥Ö¤«¤éµ¯Æ°²Äǽ¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤Ç¡¢ + ¥¤¥ó¥¹¥È¡¼¥ë¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + bootonly.iso ¥¤¥á¡¼¥¸¤ÈƱÍͤˡ¢ + ÇÛÉÛʪ¤Ï´Þ¤Þ¤ì¤Æ¤¤¤Þ¤»¤ó¤¬¡¢ + (ftp ¤Ê¤É¤Î) + ¥Í¥Ã¥È¥ï¡¼¥¯·Ðͳ¤Ç¤Î¥¤¥ó¥¹¥È¡¼¥ë¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£ + + + &os;-version-RELEASE-arch-disc1.iso ¤³¤Î CD ¥¤¥á¡¼¥¸¤Ë¤Ï¡¢ From owner-svn-doc-all@FreeBSD.ORG Wed Jan 29 20:16:54 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 997705FC; Wed, 29 Jan 2014 20:16:54 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 84BED1194; Wed, 29 Jan 2014 20:16:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0TKGsax027475; Wed, 29 Jan 2014 20:16:54 GMT (envelope-from jgh@svn.freebsd.org) Received: (from jgh@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0TKGsQw027474; Wed, 29 Jan 2014 20:16:54 GMT (envelope-from jgh@svn.freebsd.org) Message-Id: <201401292016.s0TKGsQw027474@svn.freebsd.org> From: Jason Helfman Date: Wed, 29 Jan 2014 20:16:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43684 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 20:16:54 -0000 Author: jgh Date: Wed Jan 29 20:16:53 2014 New Revision: 43684 URL: http://svnweb.freebsd.org/changeset/doc/43684 Log: - Whitespace-only fixes, translators please ignore. Approved by: wblock (mentor) Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/book.xml Wed Jan 29 11:57:43 2014 (r43683) +++ head/en_US.ISO8859-1/books/porters-handbook/book.xml Wed Jan 29 20:16:53 2014 (r43684) @@ -4941,7 +4941,7 @@ OPT1_LIB_DEPENDS_OFF= liba.so:${PORTSDIR .include <bsd.port.options.mk> . if ! ${PORT_OPTIONS:MOPT1} -LIB_DEPENDS+= liba.so:${PORTSDIR}/devel/a +LIB_DEPENDS+= liba.so:${PORTSDIR}/devel/a .endif @@ -7588,8 +7588,9 @@ USE_QT4= moc_build qmake_build rcc_build www/tomcat7 to run the service, it is quite common for a vendor to distribute a .war file. A .war - file is a Web application ARchive and is extracted when called - by the application. Avoid adding a .war + file is a Web application ARchive and is extracted when + called by the application. Avoid adding a + .war file to the pkg-plist. It is not considered best practice. An application server will expand the war archive, but not @@ -10944,7 +10945,7 @@ as .putsy.conf and edit it.ports-mgmt/poudriere. Visit the Poudriere + xlink:href="http://fossil.etoilebsd.net/poudriere">Poudriere website for more details. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 01:21:13 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8192128; Thu, 30 Jan 2014 01:21:13 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A38BC114A; Thu, 30 Jan 2014 01:21:13 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U1LDTJ048504; Thu, 30 Jan 2014 01:21:13 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U1LDGX048503; Thu, 30 Jan 2014 01:21:13 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401300121.s0U1LDGX048503@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 01:21:13 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43685 - head/en_US.ISO8859-1/books/handbook/cutting-edge X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 01:21:13 -0000 Author: wblock Date: Thu Jan 30 01:21:13 2014 New Revision: 43685 URL: http://svnweb.freebsd.org/changeset/doc/43685 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Wed Jan 29 20:16:53 2014 (r43684) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Thu Jan 30 01:21:13 2014 (r43685) @@ -4,28 +4,57 @@ $FreeBSD$ --> - - Updating and Upgrading &os; + + + + Updating and Upgrading &os; + - JimMockRestructured, reorganized, and parts updated - by + + + Jim + Mock + + Restructured, reorganized, and parts updated + by + - JordanHubbardOriginal work by - - Poul-HenningKamp - - JohnPolstra - - NikClayton + + + Jordan + Hubbard + + Original work by + + + + + Poul-Henning + Kamp + + + + + + John + Polstra + + + + + + Nik + Clayton + + - - - Synopsis @@ -80,7 +109,8 @@ - Properly set up the network connection (). + Properly set up the network connection + (). @@ -98,17 +128,33 @@ - &os; Update + + &os; Update + - TomRhodesWritten by + + + Tom + Rhodes + + Written by + + - ColinPercivalBased on notes provided by + + + Colin + Percival + + Based on notes provided by + - - Updating and Upgrading + + Updating and Upgrading + freebsd-update updating-upgrading @@ -133,7 +179,8 @@ releases currently supported by the security team. Before updating to a new release, its release announcement should be reviewed as it contains important information pertinent to the - release. Release announcements are available from http://www.FreeBSD.org/releases/. + release. Release announcements are available from http://www.FreeBSD.org/releases/. If a crontab utilizing the features @@ -253,8 +300,9 @@ MergeChanges /etc/ /var/named/etc/freebsd-update will only check if updates exist. If patches exist, they will automatically be downloaded to the local disk but will not be applied. The - root user will be sent an email so that - they may be reviewed and manually installed. + root user will be + sent an email so that they may be reviewed and manually + installed. If anything goes wrong, freebsd-update has the ability to roll back the last set of changes with @@ -353,7 +401,8 @@ MergeChanges /etc/ /var/named/etc/Custom Kernels with &os; 8.X A copy of the GENERIC kernel is - needed, and should be placed in /boot/GENERIC. If the + needed, and should be placed in + /boot/GENERIC. If the GENERIC kernel is not present in the system, it may be obtained using one of the following methods: @@ -363,7 +412,8 @@ MergeChanges /etc/ /var/named/etc/If a custom kernel has only been built once, the kernel in /boot/kernel.old is actually GENERIC. Rename this - directory to /boot/GENERIC. + directory to + /boot/GENERIC. @@ -413,10 +463,10 @@ MergeChanges /etc/ /var/named/etc/ If a custom kernel has only been built once, the - kernel in - /boot/kernel.old - is actually the GENERIC kernel. - Rename this directory to /boot/kernel. + kernel in /boot/kernel.old is + actually the GENERIC kernel. + Rename this directory to + /boot/kernel. @@ -581,7 +631,8 @@ before running "/usr/sbin/freebsd-update needs to be rebuilt and re-installed. This is required as installed software may depend on libraries which have been removed during the upgrade process. This process can be - automated using ports-mgmt/portmaster: + automated using + ports-mgmt/portmaster: &prompt.root; portmaster -af @@ -658,17 +709,33 @@ before running "/usr/sbin/freebsd-update - Portsnap: a Ports Collection Update Tool + + Portsnap: a Ports Collection Update Tool + - TomRhodesWritten by + + + Tom + Rhodes + + Written by + + - ColinPercivalBased on notes provided by + + + Colin + Percival + + Based on notes provided by + - - Updating and Upgrading + + Updating and Upgrading + Portsnap Updating and Upgrading @@ -751,10 +818,12 @@ Fetching 133 new ports or files... done. Documentation is an integral part of the &os; operating system. While an up-to-date version of the &os; Documentation - Set is always available on the &os; web site, - some users might have slow or no permanent network connectivity. - There are several ways to update the local copy of documentation - with the latest &os; Documentation Set. + Set is always available on the + &os; web + site, some users might have slow or no permanent + network connectivity. There are several ways to update the + local copy of documentation with the latest &os; Documentation + Set. Using <application>Subversion</application> to Update the @@ -779,7 +848,8 @@ Fetching 133 new ports or files... done. <listitem> <para>Rebuild the &os; documentation from its source, and - install it under <filename>/usr/share/doc</filename>.</para> + install it under + <filename>/usr/share/doc</filename>.</para> </listitem> <listitem> @@ -810,13 +880,14 @@ Fetching 133 new ports or files... done. <note> <para>When no &postscript; or PDF documentation required, one - might consider installing the <package>textproc/docproj-nojadetex</package> port - instead. This version of the documentation toolchain - includes everything except the - <application>teTeX</application> typesetting engine. - <application>teTeX</application> is a very large collection - of tools, so it may be quite sensible to omit its - installation if PDF output is not really necessary.</para> + might consider installing the + <package>textproc/docproj-nojadetex</package> port instead. + This version of the documentation toolchain includes + everything except the <application>teTeX</application> + typesetting engine. <application>teTeX</application> is a + very large collection of tools, so it may be quite sensible + to omit its installation if PDF output is not really + necessary.</para> </note> </sect2> @@ -829,7 +900,9 @@ Fetching 133 new ports or files... done. <screen>&prompt.root; <userinput>svn checkout https://svn0.us-west.FreeBSD.org/doc/head /usr/doc</userinput></screen> - <para>Select the closest mirror from the available <link linkend="svn-mirrors">Subversion mirror sites</link>.</para> + <para>Select the closest mirror from the available + <link linkend="svn-mirrors">Subversion mirror + sites</link>.</para> <para>The initial download of the documentation sources may take a while. Let it run until it completes.</para> @@ -908,8 +981,8 @@ Fetching 133 new ports or files... done. <title>Installing the &os; Documentation from Source Once an up-to-date snapshot of the documentation sources - has been fetched to /usr/doc, everything is - ready for an update of the installed documentation. + has been fetched to /usr/doc, everything + is ready for an update of the installed documentation. A full update of all the languages defined in DOC_LANG may be performed by typing: @@ -932,20 +1005,29 @@ Fetching 133 new ports or files... done. &prompt.root; make FORMATS='html html-split' install clean For information on editing and submitting corrections to - the documentation, refer to the &os; Documentation + the documentation, refer to the + &os; Documentation Project Primer for New Contributors. - Using Documentation Ports + + Using Documentation Ports + - MarcFonvieilleBased on the work of + + + Marc + Fonvieille + + Based on the work of + - - - Updating and Upgrading + + Updating and Upgrading + documentation package @@ -977,10 +1059,11 @@ Fetching 133 new ports or files... done. These two methods of updating the &os; documentation are - supported by a set of documentation - ports, updated by the &a.doceng; on a monthly - basis. These are listed in the &os; Ports Collection, - under the docs + supported by a set of + documentation ports, updated by the + &a.doceng; on a monthly basis. These are listed in the &os; + Ports Collection, under the docs category. @@ -1006,28 +1089,31 @@ Fetching 133 new ports or files... done. - The master port, misc/freebsd-doc-en, - which installs all of the English documentation - ports. + The master port, + misc/freebsd-doc-en, which installs + all of the English documentation ports. - The all in one port, misc/freebsd-doc-all, - builds and installs all documentation in all available + The all in one port, + misc/freebsd-doc-all, builds and + installs all documentation in all available languages. There is a slave port for each - translation, such as misc/freebsd-doc-hu for the + translation, such as + misc/freebsd-doc-hu for the Hungarian-language documents. For example, to build and install the English documentation in split HTML format, - similar to the format used on http://www.FreeBSD.org, to - /usr/local/share/doc/freebsd, + similar to the format used on http://www.FreeBSD.org, + to /usr/local/share/doc/freebsd, install the following port &prompt.root; cd /usr/ports/misc/freebsd-doc-en @@ -1069,7 +1155,8 @@ Fetching 133 new ports or files... done. Specifies where to install the documentation. - It defaults to /usr/local/share/doc/freebsd. + It defaults to + /usr/local/share/doc/freebsd. The default target directory differs from the @@ -1272,8 +1359,9 @@ Fetching 133 new ports or files... done. - Use svn - Subversion + Use svn + + Subversion -CURRENT @@ -1284,24 +1372,27 @@ Fetching 133 new ports or files... done. branch. This is the recommended method, providing access to &os; development as it occurs. Checkout the -CURRENT code from the head - branch of one of the Subversion mirror + branch of one of the Subversion mirror sites. Due to the size of the repository, it is recommended that only desired subtrees be checked out. - Use the CTM + Use the + CTM + -CURRENT Syncing with CTM facility. If you have bad connectivity such as high price connections or only email access, CTM is an option, but it - is not as reliable as - Subversion. - For this reason, Subversion - is the recommended method for any system with - Internet connectivity. + is not as reliable as + Subversion. For this + reason, Subversion is the + recommended method for any system with Internet + connectivity. @@ -1315,7 +1406,8 @@ Fetching 133 new ports or files... done. problems. Before compiling - &os.current; + &os.current; + -CURRENT compiling , read @@ -1374,7 +1466,8 @@ Fetching 133 new ports or files... done. For a complete description of the current security - policy for old releases of FreeBSD, refer to http://www.FreeBSD.org/security/.. + policy for old releases of FreeBSD, refer to http://www.FreeBSD.org/security/.. While the &os.stable; branch should compile and run at all times, this cannot be guaranteed. While code is @@ -1430,11 +1523,13 @@ Fetching 133 new ports or files... done. - To install a new system running monthly - snapshots built from &os.stable;, refer to Snapshots for more - information. Alternatively, it is possible to install - the most recent &os.stable; release from the mirror sites and follow the - instructions below to upgrade the system to the most + To install a new system running monthly snapshots + built from &os.stable;, refer to Snapshots + for more information. Alternatively, it is possible to + install the most recent &os.stable; release from the + mirror sites and follow + the instructions below to upgrade the system to the most up-to-date &os.stable; source code. Several methods are available to upgrade from a &os; @@ -1443,9 +1538,9 @@ Fetching 133 new ports or files... done. - Use svn + Use svn + Subversion - to check out the desired development or release branch. This is the recommended method, providing access to &os; development as it occurs. @@ -1453,22 +1548,24 @@ Fetching 133 new ports or files... done. current development head, and branches identified in the release engineering page, such as - stable/9 + stable/9 + -STABLE syncing with Subversion or releng/9.2. URL prefixes for Subversion checkout of - the base system are shown in Subversion mirror - sites. - Because of the size of the repository, it is - recommended that only desired subtrees be checked - out. + the base system are shown in Subversion mirror + sites. Because of the size of the + repository, it is recommended that only desired + subtrees be checked out. - Consider using CTM + Consider using CTM + -STABLE syncing with CTM if you do not have a fast connection to @@ -1501,7 +1598,9 @@ Fetching 133 new ports or files... done. There are various ways of using an Internet or email connection to stay up-to-date with any given area, or all areas, - of the &os; project sources. The primary services are Subversion and CTM. + of the &os; project sources. The primary services are + Subversion and + CTM. While it is possible to update only parts of the source @@ -1750,9 +1849,9 @@ Fetching 133 new ports or files... done. password database. This is often necessary when new groups or special system-user accounts have been added since the last update, so that the - installworld step will be able to - use the newly installed system user or system group names - without problems. + installworld step will be able + to use the newly installed system user or system group + names without problems. @@ -1846,8 +1945,7 @@ Fetching 133 new ports or files... done. successfully, boot into single user mode using boot -s from the loader prompt. - If using UFS, run: - + If using UFS, run: &prompt.root; mount -u / &prompt.root; mount -a -t ufs @@ -1859,7 +1957,7 @@ Fetching 133 new ports or files... done. Then run: - &prompt.root; adjkerntz -i + &prompt.root; adjkerntz -i &prompt.root; mergemaster -p &prompt.root; cd /usr/src &prompt.root; make installworld @@ -2070,10 +2168,12 @@ Script started, output file is /var/tmp/ &prompt.root; exit Script done, … - Do not save the output in /tmp as this directory may be - cleared at next reboot. A better place to save the file is + Do not save the output in + /tmp as this directory may be cleared + at next reboot. A better place to save the file is /var/tmp or in - root's home directory. + root's home + directory. @@ -2084,7 +2184,9 @@ Script done, … &prompt.root; cd /usr/src - make + + make + To rebuild the world, use &man.make.1;. This command reads instructions from the Makefile, @@ -2135,36 +2237,39 @@ Script done, … build options. The first target should always be buildworld. - As the names imply, buildworld - builds a complete new tree under - /usr/obj and - installworld installs this tree on - the current machine. + As the names imply, + buildworld builds a complete new + tree under /usr/obj and + installworld installs this tree + on the current machine. Having separate options is useful for two reasons. First, it allows for a self hosted build that does not affect any components of a running system. Because - of this, buildworld can be run on a - machine running in multi-user mode with no fear of + of this, buildworld can be run on + a machine running in multi-user mode with no fear of ill-effects. It is still recommended that installworld be run in part in single user mode, though. Secondly, it allows NFS mounts to be used to upgrade multiple machines on a network. If order to upgrade three - machines, A, B and - C, run make buildworld - and make installworld on + machines, A, + B and C, + run make buildworld and + make installworld on A. B and C should then NFS mount /usr/src and - /usr/obj from A, and - run make installworld to install the - results of the build on B and + /usr/obj from + A, and run + make installworld to install the results + of the build on B and C. - Although the world target still - exists, users are strongly encouraged not to use it. + Although the world target + still exists, users are strongly encouraged not to use + it. Instead, run: @@ -2250,9 +2355,9 @@ Script done, … above 1 and noschg or similar flags have been set on the kernel binary, drop into single user mode to use - installkernel. Otherwise, both these - commands can be run from multi user mode without problems. - See &man.init.8; for details about + installkernel. Otherwise, both + these commands can be run from multi user mode without + problems. See &man.init.8; for details about kern.securelevel and &man.chflags.1; for details about the various file flags. @@ -2263,14 +2368,15 @@ Script done, … single-user mode Reboot into single user mode to test that the new kernel - works using the instructions in . + works using the instructions in + . Install the New System Binaries - Next, use installworld to install - the new system binaries: + Next, use installworld to + install the new system binaries: &prompt.root; cd /usr/src &prompt.root; make installworld @@ -2312,12 +2418,19 @@ Script done, … wrong. - <command>mergemaster</command> + + <command>mergemaster</command> + - TomRhodesContributed by + + + Tom + Rhodes + + Contributed by + - @@ -2327,10 +2440,9 @@ Script done, … &man.mergemaster.8; is a Bourne script to aid in determining the differences between the configuration files - in /etc, and the - configuration files in the source tree - /usr/src/etc. This - is the recommended solution for keeping the system + in /etc, and the configuration files in + the source tree /usr/src/etc. This is + the recommended solution for keeping the system configuration files up to date with those located in the source tree. @@ -2437,8 +2549,8 @@ Script done, … This will build the necessary directory structure and install the files. A lot of the subdirectories that have - been created under /var/tmp/root are empty and - should be deleted. The simplest way to do this is + been created under /var/tmp/root are + empty and should be deleted. The simplest way to do this is to: &prompt.root; cd /var/tmp/root @@ -2455,9 +2567,10 @@ Script done, … Go through each of these files, determining how they differ from the system's existing files. - Some of the files installed into /var/tmp/root have a - leading .. Make sure to use ls - -a in order to catch them. + Some of the files installed into + /var/tmp/root have a leading + .. Make sure to use + ls -a in order to catch them. The simplest way to compare files is to use &man.diff.1;: @@ -2521,11 +2634,11 @@ Script done, … &prompt.root; diff -r root-20130214 root-20130221 Typically, this will be a much smaller set of - differences than those between /var/tmp/root-20130221/etc - and /etc. - Because the set of differences is smaller, it is - easier to migrate those changes across into - /etc. + differences than those between + /var/tmp/root-20130221/etc and + /etc. Because the set of + differences is smaller, it is easier to migrate those + changes across into /etc. @@ -2551,12 +2664,19 @@ Script done, … - Deleting Obsolete Files and Directories + + Deleting Obsolete Files and Directories + - AntonShterenlikhtBased on notes provided by + + + Anton + Shterenlikht + + Based on notes provided by + - Deleting obsolete files and directories @@ -2668,8 +2788,8 @@ Script done, … If things went slightly wrong, it is easy to rebuild a particular piece of the system. For example, if /etc/magic was accidentally deleted as - part of the upgrade or merge of /etc, &man.file.1; will stop - working. To fix this, run: + part of the upgrade or merge of /etc, + &man.file.1; will stop working. To fix this, run: &prompt.root; cd /usr/src/usr.bin/file &prompt.root; make all install @@ -2866,20 +2986,22 @@ Building everything.. &prompt.root; mount -u -o noatime /usr/src - This example assumes /usr/src is on its - own file system. If it is part of - /usr, then - use that file system mount point instead. + This example assumes + /usr/src is on its own file + system. If it is part of + /usr, then use that file + system mount point instead. - The file system holding /usr/obj can be - mounted or remounted with - so that disk writes happen asynchronously. The - write completes immediately, and the data is written - to the disk a few seconds later. This allows writes - to be clustered together, and can provide a dramatic + The file system holding + /usr/obj can be mounted or + remounted with so that disk + writes happen asynchronously. The write completes + immediately, and the data is written to the disk a + few seconds later. This allows writes to be + clustered together, and can provide a dramatic performance boost. @@ -2941,14 +3063,20 @@ Building everything.. - Tracking for Multiple Machines + + Tracking for Multiple Machines + - MikeMeyerContributed by + + + Mike + Meyer + + Contributed by + - - NFS installing multiple machines @@ -3031,16 +3159,17 @@ Building everything.. Ports The same ideas can be used for the ports tree. The first - critical step is to mount /usr/ports from the same - machine to all the machines in the build set. Then, configure - /etc/make.conf properly to share - distfiles. Set DISTDIR to a common shared - directory that is writable by whichever user - root is mapped to by the NFS mounts. - Each machine should set WRKDIRPREFIX to a - local build directory. Finally, if the system is to build and - distribute packages, set PACKAGES to a - directory similar to DISTDIR. + critical step is to mount /usr/ports from + the same machine to all the machines in the build set. Then, + configure /etc/make.conf properly to + share distfiles. Set DISTDIR to a common + shared directory that is writable by whichever user + root is mapped to by + the NFS mounts. Each machine should set + WRKDIRPREFIX to a local build directory. + Finally, if the system is to build and distribute packages, + set PACKAGES to a directory similar to + DISTDIR. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 03:12:25 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 35ED1158; Thu, 30 Jan 2014 03:12:25 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1751419F9; Thu, 30 Jan 2014 03:12:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U3COkD091711; Thu, 30 Jan 2014 03:12:24 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U3COT1091710; Thu, 30 Jan 2014 03:12:24 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401300312.s0U3COT1091710@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 03:12:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43686 - head/en_US.ISO8859-1/books/handbook/geom X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 03:12:25 -0000 Author: wblock Date: Thu Jan 30 03:12:24 2014 New Revision: 43686 URL: http://svnweb.freebsd.org/changeset/doc/43686 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Thu Jan 30 01:21:13 2014 (r43685) +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Thu Jan 30 03:12:24 2014 (r43686) @@ -4,15 +4,24 @@ $FreeBSD$ --> - - GEOM: Modular Disk Transformation Framework + + + + GEOM: Modular Disk Transformation Framework + - TomRhodesWritten by + + + Tom + Rhodes + + Written by + - - Synopsis @@ -25,7 +34,8 @@ This chapter covers the use of disks under the GEOM - framework in &os;. This includes the major RAID + framework in &os;. This includes the major RAID control utilities which use the framework for configuration. This chapter will not go into in depth discussion on how GEOM handles or controls I/O, the underlying subsystem, or code. @@ -64,11 +74,13 @@ - Understand how &os; treats disk devices. + Understand how &os; treats disk + devices. - Know how to configure and install a new &os; kernel. + Know how to configure and install a new + &os; kernel. @@ -78,22 +90,34 @@ GEOM permits access and control to classes, such as Master Boot Records and BSD labels, through the use - of providers, or the special files in /dev. By supporting various - software RAID configurations, GEOM - transparently provides access to the operating system and - operating system utilities. + of providers, or the special files in /dev. + By supporting various software RAID + configurations, GEOM transparently provides access to the + operating system and operating system utilities. - RAID0 - Striping + + RAID0 - Striping + - TomRhodesWritten by - MurrayStokely + + + Tom + Rhodes + + Written by + + + + + Murray + Stokely + + - - GEOM @@ -142,7 +166,8 @@ Ensure that a suitable mount point exists. If this volume will become a root partition, then temporarily use - another mount point such as /mnt: + another mount point such as + /mnt: &prompt.root; mkdir /mnt @@ -192,8 +217,9 @@ Done. To mount this striped file system automatically during the boot process, place the volume information in - /etc/fstab. In this example, a - permanent mount point, named stripe, is created: + /etc/fstab. In this example, a permanent + mount point, named stripe, is + created: &prompt.root; mkdir /stripe &prompt.root; echo "/dev/stripe/st0a /stripe ufs rw 2 2" \ @@ -407,7 +433,8 @@ Done. are identical, it does not matter which is selected to boot. - See the Troubleshooting + See the Troubleshooting section if there are problems booting. Powering down and disconnecting the original ada0 disk will allow it to be kept as an offline backup. @@ -789,9 +816,11 @@ mountroot> &prompt.root; gmirror forget gm0 - Any old metadata should be cleared from the replacement - disk. Then the disk, ada4 - for this example, is inserted into the mirror: + Any old metadata should be + cleared from the + replacement disk. Then the disk, + ada4 for this example, is inserted into + the mirror: &prompt.root; gmirror insert gm0 /dev/ada4 @@ -812,12 +841,19 @@ mountroot> - Software <acronym>RAID</acronym> Devices + + Software <acronym>RAID</acronym> Devices + - WarrenBlockOriginally contributed by + + + Warren + Block + + Originally contributed by + - GEOM @@ -1116,20 +1152,46 @@ raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE)) - <acronym>RAID</acronym>3 - Byte-level Striping with - Dedicated Parity + + + <acronym>RAID</acronym>3 - Byte-level Striping with + Dedicated Parity + - MarkGladmanWritten by - DanielGerzo + + + Mark + Gladman + + Written by + + + + + Daniel + Gerzo + + + - TomRhodesBased on documentation by - MurrayStokely + + + Tom + Rhodes + + Based on documentation by + + + + + Murray + Stokely + + - - GEOM @@ -1294,7 +1356,8 @@ Done. ggate0 &prompt.root; mount /dev/ggate0 /mnt - The device may now be accessed through the /mnt mount point. + The device may now be accessed through the + /mnt mount point. However, this will fail if the device is currently mounted @@ -1362,18 +1425,18 @@ ggate0 Permanent labels can be a generic or a file system label. Permanent file system labels can be created with &man.tunefs.8; or &man.newfs.8;. These types of labels are - created in a sub-directory of /dev, and will be named - according to the file system type. For example, + created in a sub-directory of /dev, and + will be named according to the file system type. For example, UFS2 file system labels will be created in - /dev/ufs. Generic - permanent labels can be created with glabel - label. These are not file system specific and - will be created in /dev/label. + /dev/ufs. Generic permanent labels can + be created with glabel label. These are + not file system specific and will be created in + /dev/label. Temporary labels are destroyed at the next reboot. These - labels are created in /dev/label and are suited to - experimentation. A temporary label can be created using - glabel create. + labels are created in /dev/label and are + suited to experimentation. A temporary label can be created + using glabel create. @@ -1389,8 +1452,8 @@ ggate0 corruption. - A label should now exist in /dev/ufs which may be added - to /etc/fstab: + A label should now exist in /dev/ufs + which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 @@ -1612,7 +1675,8 @@ ufsid/486b6fc16926168e N/A ad4s1ftunefs. It is also possible to journal the boot disk of a &os; - system. Refer to the article Implementing UFS + system. Refer to the article Implementing UFS Journaling on a Desktop PC for detailed instructions. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 05:38:07 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95171BC8; Thu, 30 Jan 2014 05:38:07 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 66AD8139C; Thu, 30 Jan 2014 05:38:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U5c7wt057364; Thu, 30 Jan 2014 05:38:07 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U5c7rg057363; Thu, 30 Jan 2014 05:38:07 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401300538.s0U5c7rg057363@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 05:38:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43687 - head/en_US.ISO8859-1/books/handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 05:38:07 -0000 Author: wblock Date: Thu Jan 30 05:38:06 2014 New Revision: 43687 URL: http://svnweb.freebsd.org/changeset/doc/43687 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/book.xml Modified: head/en_US.ISO8859-1/books/handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/book.xml Thu Jan 30 03:12:24 2014 (r43686) +++ head/en_US.ISO8859-1/books/handbook/book.xml Thu Jan 30 05:38:06 2014 (r43687) @@ -12,11 +12,17 @@ %txtfiles; ]> - - FreeBSD Handbook - - The FreeBSD Documentation Project + + + + FreeBSD Handbook + + + The FreeBSD Documentation Project + $FreeBSD$ @@ -92,19 +98,20 @@ work of many individuals. As such, some sections may become dated and require updating. If you are interested in helping out with this project, send email to the &a.doc;. The latest - version of this document is always available from the - FreeBSD web site - (previous versions of this handbook can be obtained from - http://docs.FreeBSD.org/doc/). It may - also be downloaded in a variety of formats and compression - options from the - FreeBSD + + version of this document is always available from the FreeBSD web site + (previous versions of this handbook can be obtained from http://docs.FreeBSD.org/doc/). + It may also be downloaded in a variety of formats and + compression options from the FreeBSD FTP server or one of the numerous mirror sites. If you would prefer to have a hard copy of the handbook, you can purchase one at the - FreeBSD Mall. - You may also want to + FreeBSD + Mall. You may also want to search the handbook. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 05:46:43 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D33FDAD; Thu, 30 Jan 2014 05:46:43 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 35C931471; Thu, 30 Jan 2014 05:46:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U5khb1062024; Thu, 30 Jan 2014 05:46:43 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U5khw0062023; Thu, 30 Jan 2014 05:46:43 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401300546.s0U5khw0062023@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 05:46:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43688 - head/en_US.ISO8859-1/books/handbook/audit X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 05:46:43 -0000 Author: wblock Date: Thu Jan 30 05:46:42 2014 New Revision: 43688 URL: http://svnweb.freebsd.org/changeset/doc/43688 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/audit/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/audit/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/audit/chapter.xml Thu Jan 30 05:38:06 2014 (r43687) +++ head/en_US.ISO8859-1/books/handbook/audit/chapter.xml Thu Jan 30 05:46:42 2014 (r43688) @@ -9,16 +9,32 @@ And the /dev/audit special file if we ch some coverage of integrating MAC with Event auditing and perhaps discussion on how some companies or organizations handle auditing and auditing requirements. --> - - Security Event Auditing + + + + + Security Event Auditing + - TomRhodesWritten by - RobertWatson + + + Tom + Rhodes + + Written by + + + + + Robert + Watson + + - - Synopsis @@ -189,8 +205,8 @@ requirements. --> options AUDIT - Rebuild and reinstall - the kernel via the normal process explained in . + Rebuild and reinstall the kernel via the normal process + explained in . Once an audit-enabled kernel is built, installed, and the system has been rebooted, enable the audit daemon by adding the @@ -208,9 +224,8 @@ requirements. --> Audit Configuration All configuration files for security audit are found in - /etc/security. The - following files must be present before the audit daemon is - started: + /etc/security. The following files must be + present before the audit daemon is started: @@ -257,13 +272,13 @@ requirements. --> Selection expressions are used in a number of places in the audit configuration to determine which events should be - audited. Expressions contain a list of event classes to match, - each with a prefix indicating whether matching records should - be accepted or ignored, and optionally to indicate if the - entry is intended to match successful or failed operations. - Selection expressions are evaluated from left to right, and - two expressions are combined by appending one onto the - other. + audited. Expressions contain a list of event classes to + match, each with a prefix indicating whether matching records + should be accepted or ignored, and optionally to indicate if + the entry is intended to match successful or failed + operations. Selection expressions are evaluated from left to + right, and two expressions are combined by appending one onto + the other. The following list contains the default audit event classes present in audit_class: @@ -478,9 +493,9 @@ filesz:0 will be generated. The above example sets the minimum free space to twenty percent. - The entry specifies audit classes - to be audited for non-attributed events, such as the login - process and system daemons. + The entry specifies audit + classes to be audited for non-attributed events, such as the + login process and system daemons. The entry specifies a comma-separated list of policy flags controlling various @@ -514,13 +529,14 @@ filesz:0 of events that should never be audited for the user. The following example audit_user - audits login/logout events and successful command - execution for root, and audits - file creation and successful command execution for - www. If used with the above example - audit_control, the - lo entry for root is - redundant, and login/logout events will also be audited for + audits login/logout events and successful command execution + for root, and + audits file creation and successful command execution for + www. If used with + the above example audit_control, the + lo entry for + root is redundant, + and login/logout events will also be audited for www. root:lo,+ex:no @@ -541,9 +557,9 @@ www:fc,+ex:no format; the &man.auditreduce.1; command may be used to reduce the audit trail file for analysis, archiving, or printing purposes. A variety of selection parameters are supported by - &man.auditreduce.1;, including event type, event class, - user, date or time of the event, and the file path or object - acted on. + &man.auditreduce.1;, including event type, event class, user, + date or time of the event, and the file path or object acted + on. For example, &man.praudit.1; will dump the entire contents of a specified audit log in plain text: @@ -584,12 +600,13 @@ trailer,133 user ID and group ID, real user ID and group ID, process ID, session ID, port ID, and login address. Notice that the audit user ID and real user ID differ: the user - robert has switched to the - root account before running this command, - but it is audited using the original authenticated user. - Finally, the return token indicates the - successful execution, and the trailer - concludes the record. + robert has switched + to the root account + before running this command, but it is audited using the + original authenticated user. Finally, the + return token indicates the successful + execution, and the trailer concludes the + record. XML output format is also supported by &man.praudit.1;, and can be selected using @@ -613,15 +630,19 @@ trailer,133 Delegating Audit Review Rights - Members of the audit group are - given permission to read audit trails in /var/audit; by default, this - group is empty, so only the root user - may read audit trails. Users may be added to the - audit group in order to delegate audit - review rights to the user. As the ability to track audit log - contents provides significant insight into the behavior of - users and processes, it is recommended that the delegation of - audit review rights be performed with caution. + Members of the + audit group are + given permission to read audit trails in + /var/audit; by default, this group is + empty, so only the + root user may read + audit trails. Users may be added to the + audit group in + order to delegate audit review rights to the user. As the + ability to track audit log contents provides significant + insight into the behavior of users and processes, it is + recommended that the delegation of audit review rights be + performed with caution. @@ -640,9 +661,10 @@ trailer,133 &prompt.root; praudit /dev/auditpipe By default, audit pipe device nodes are accessible only to - the root user. To make them accessible - to the members of the audit group, add - a devfs rule to + the root user. To + make them accessible to the members of the + audit group, add a + devfs rule to devfs.rules: add path 'auditpipe*' mode 0440 group audit From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 05:52:24 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21CAAE3F; Thu, 30 Jan 2014 05:52:24 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0CF1914F1; Thu, 30 Jan 2014 05:52:24 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U5qNE5065920; Thu, 30 Jan 2014 05:52:23 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U5qN2B065919; Thu, 30 Jan 2014 05:52:23 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401300552.s0U5qN2B065919@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 05:52:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43689 - head/en_US.ISO8859-1/books/handbook/bsdinstall X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 05:52:24 -0000 Author: wblock Date: Thu Jan 30 05:52:23 2014 New Revision: 43689 URL: http://svnweb.freebsd.org/changeset/doc/43689 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Thu Jan 30 05:46:42 2014 (r43688) +++ head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Thu Jan 30 05:52:23 2014 (r43689) @@ -366,8 +366,8 @@ cable or DSL modem with an Ethernet interface), the installer will request some information about the network. - DHCP is commonly used to - provide automatic network configuration. If + DHCP is commonly + used to provide automatic network configuration. If DHCP is not available, this network information must be obtained from the local network administrator or service provider: @@ -624,10 +624,10 @@ commit your changes? Configure your machine to boot from either the CDROM or from USB, depending on the media being used for the - installation. BIOS configurations allow the - selection of a specific boot device. Most systems also - provide for selecting a boot device during startup, - typically by pressing F10, + installation. BIOS configurations + allow the selection of a specific boot device. Most + systems also provide for selecting a boot device during + startup, typically by pressing F10, F11, F12, or Escape. @@ -1477,8 +1477,9 @@ Trying to mount root from cd9660:/dev/is Use a unique label on every filesystem to avoid conflicts from identical labels. A few letters from the computer's name, use, or location can be added to the label. - For instance, labroot or rootfs-lab for the UFS root partition on the - lab's computer. + For instance, labroot or + rootfs-lab for the UFS root partition on + the lab's computer. @@ -1494,8 +1495,8 @@ Trying to mount root from cd9660:/dev/is for a 20G target disk. If more space is available on the target disk, larger swap or /var partitions may be useful. Labels shown here are prefixed - with ex for example, but readers - should use other unique label values as described + with ex for example, but + readers should use other unique label values as described above. By default, &os;'s gptboot expects @@ -1807,9 +1808,9 @@ Trying to mount root from cd9660:/dev/is There are two methods of IPv4 configuration. - DHCP will automatically - configure the network interface correctly, and is the - preferred method. Static + DHCP will + automatically configure the network interface correctly, and + is the preferred method. Static configuration requires manual entry of network information. @@ -1972,8 +1973,8 @@ Trying to mount root from cd9660:/dev/is Configuring <acronym>DNS</acronym> The Domain Name System (or - DNS) Resolver converts - hostnames to and from network addresses. If + DNS) Resolver + converts hostnames to and from network addresses. If DHCP or SLAAC was used to autoconfigure the network interface, the Resolver Configuration values may already be present. Otherwise, @@ -2736,8 +2737,9 @@ login: To gain access to the system, authentication is - required. The username is root, and - the password is blank. + required. The username is + root, and the + password is blank. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 07:58:36 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 61D096FD; Thu, 30 Jan 2014 07:58:36 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 32E991E4A; Thu, 30 Jan 2014 07:58:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U7waoG020293; Thu, 30 Jan 2014 07:58:36 GMT (envelope-from dim@svn.freebsd.org) Received: (from dim@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U7wauh020292; Thu, 30 Jan 2014 07:58:36 GMT (envelope-from dim@svn.freebsd.org) Message-Id: <201401300758.s0U7wauh020292@svn.freebsd.org> From: Dimitry Andric Date: Thu, 30 Jan 2014 07:58:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43690 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 07:58:36 -0000 Author: dim (src committer) Date: Thu Jan 30 07:58:35 2014 New Revision: 43690 URL: http://svnweb.freebsd.org/changeset/doc/43690 Log: Update porter's handbook for __FreeBSD_version values from 1100001 to 1100007. Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 05:52:23 2014 (r43689) +++ head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 07:58:35 2014 (r43690) @@ -4919,3 +4919,54 @@ it was never committed: 11.0-CURRENT. (rev 256284). + + + 1100001 + October 19, 2013 + 11.0-CURRENT after addition of support for "first boot" + rc.d scripts, so ports can make use of this. + (rev 256776). + + + + 1100002 + November 5, 2013 + 11.0-CURRENT after dropping support for historic ioctls. + (rev 257696). + + + + 1100003 + November 17, 2013 + 11.0-CURRENT after iconv changes. + (rev 258284). + + + + 1100004 + December 15, 2013 + 11.0-CURRENT after the behavior change of gss_pseudo_random + introduced in r259286. + (rev 259424). + + + + 1100005 + December 28, 2013 + 11.0-CURRENT after r259951 - Don't coalesce entries in vm_map_stack(). + (rev 260010). + + + + 1100006 + January 28, 2014 + 11.0-CURRENT after upgrades of libelf and libdwarf. + (rev 261246). + + + + 1100007 + January 30, 2014 + 11.0-CURRENT after upgrades of libc++ to 3.4 release. + (rev 261283). + From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 08:12:59 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6CEA7D7D; Thu, 30 Jan 2014 08:12:59 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3EC9A1FB3; Thu, 30 Jan 2014 08:12:59 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U8Cx73027768; Thu, 30 Jan 2014 08:12:59 GMT (envelope-from dim@svn.freebsd.org) Received: (from dim@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U8CxG3027767; Thu, 30 Jan 2014 08:12:59 GMT (envelope-from dim@svn.freebsd.org) Message-Id: <201401300812.s0U8CxG3027767@svn.freebsd.org> From: Dimitry Andric Date: Thu, 30 Jan 2014 08:12:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43691 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 08:12:59 -0000 Author: dim (src committer) Date: Thu Jan 30 08:12:58 2014 New Revision: 43691 URL: http://svnweb.freebsd.org/changeset/doc/43691 Log: Drop superfluous dots before the revision number of the most recent __FreeBSD_version description entries. Noticed by: gjb Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 07:58:35 2014 (r43690) +++ head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 08:12:58 2014 (r43691) @@ -4916,7 +4916,7 @@ it was never committed: 1100000 October 10, 2013 - 11.0-CURRENT. + 11.0-CURRENT (rev 256284). @@ -4924,21 +4924,21 @@ it was never committed: 1100001 October 19, 2013 11.0-CURRENT after addition of support for "first boot" - rc.d scripts, so ports can make use of this. + rc.d scripts, so ports can make use of this (rev 256776). 1100002 November 5, 2013 - 11.0-CURRENT after dropping support for historic ioctls. + 11.0-CURRENT after dropping support for historic ioctls (rev 257696). 1100003 November 17, 2013 - 11.0-CURRENT after iconv changes. + 11.0-CURRENT after iconv changes (rev 258284). @@ -4947,26 +4947,26 @@ it was never committed: December 15, 2013 11.0-CURRENT after the behavior change of gss_pseudo_random introduced in r259286. - (rev 259424). + (rev 259424) 1100005 December 28, 2013 - 11.0-CURRENT after r259951 - Don't coalesce entries in vm_map_stack(). + 11.0-CURRENT after r259951 - Don't coalesce entries in vm_map_stack() (rev 260010). 1100006 January 28, 2014 - 11.0-CURRENT after upgrades of libelf and libdwarf. + 11.0-CURRENT after upgrades of libelf and libdwarf (rev 261246). 1100007 January 30, 2014 - 11.0-CURRENT after upgrades of libc++ to 3.4 release. + 11.0-CURRENT after upgrades of libc++ to 3.4 release (rev 261283). From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 08:16:08 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0BDA2FDC; Thu, 30 Jan 2014 08:16:08 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EC7F91FD7; Thu, 30 Jan 2014 08:16:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U8G7Zn028264; Thu, 30 Jan 2014 08:16:07 GMT (envelope-from dim@svn.freebsd.org) Received: (from dim@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U8G7gd028263; Thu, 30 Jan 2014 08:16:07 GMT (envelope-from dim@svn.freebsd.org) Message-Id: <201401300816.s0U8G7gd028263@svn.freebsd.org> From: Dimitry Andric Date: Thu, 30 Jan 2014 08:16:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43692 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 08:16:08 -0000 Author: dim (src committer) Date: Thu Jan 30 08:16:07 2014 New Revision: 43692 URL: http://svnweb.freebsd.org/changeset/doc/43692 Log: Fix typo: libc++ 3.4 is just a singular upgrade. Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 08:12:58 2014 (r43691) +++ head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 08:16:07 2014 (r43692) @@ -4967,6 +4967,6 @@ it was never committed: 1100007 January 30, 2014 - 11.0-CURRENT after upgrades of libc++ to 3.4 release + 11.0-CURRENT after upgrade of libc++ to 3.4 release (rev 261283). From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 14:25:07 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 909B723D; Thu, 30 Jan 2014 14:25:07 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7C7DA11AD; Thu, 30 Jan 2014 14:25:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UEP7Tj077490; Thu, 30 Jan 2014 14:25:07 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UEP7nH077489; Thu, 30 Jan 2014 14:25:07 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401301425.s0UEP7nH077489@svn.freebsd.org> From: Dru Lavigne Date: Thu, 30 Jan 2014 14:25:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43693 - head/en_US.ISO8859-1/books/handbook/ports X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 14:25:07 -0000 Author: dru Date: Thu Jan 30 14:25:06 2014 New Revision: 43693 URL: http://svnweb.freebsd.org/changeset/doc/43693 Log: Fix typo. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Thu Jan 30 08:16:07 2014 (r43692) +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Thu Jan 30 14:25:06 2014 (r43693) @@ -884,7 +884,7 @@ Deinstalling ca_root_nss-3.15.1_1... don This set of files is used to compile and install applications on &os;. Before an application can be compiled using a port, the Ports Collection must first be installed. If it was not - installed during the installatio of &os;, use one of the + installed during the installation of &os;, use one of the following methods to install it: From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 15:18:50 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37B46E15; Thu, 30 Jan 2014 15:18:50 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 16081160D; Thu, 30 Jan 2014 15:18:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UFIn1h097223; Thu, 30 Jan 2014 15:18:49 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UFInOB097222; Thu, 30 Jan 2014 15:18:49 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401301518.s0UFInOB097222@svn.freebsd.org> From: Dru Lavigne Date: Thu, 30 Jan 2014 15:18:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43694 - head/en_US.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 15:18:50 -0000 Author: dru Date: Thu Jan 30 15:18:49 2014 New Revision: 43694 URL: http://svnweb.freebsd.org/changeset/doc/43694 Log: Reduce floppy section to a procedure. Make note to remove this section in 06/15 when 8.4 is EOL'd (references PR155982) This section will not appear in the print edition. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 14:25:06 2014 (r43693) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 15:18:49 2014 (r43694) @@ -1407,9 +1407,9 @@ cd0: Attempt to query device size failed - Creating and Using Floppy Disks + - Storing data on floppy disks is sometimes useful, for - example when one does not have any other removable storage media - or when one needs to transfer small amounts of data to another - computer. + This section explains how to format a 3.5 inch floppy disk + in &os;. - This section explains how to use floppy disks in &os;. It - covers formatting and usage of 3.5inch DOS floppies, but the - concepts are similar for other floppy disk formats. - - - Formatting Floppies - - - The Device - - Floppy disks are accessed through entries in - /dev, just like other - devices. To access the raw floppy disk, simply use - /dev/fdN. - - - - Formatting + + Steps to Format a Floppy A floppy disk needs to be low-level formatted before it can be used. This is usually done by the vendor, but - formatting is a good way to check media integrity. Although - it is possible to force other disk sizes, 1440kB is what - most floppy disks are designed for. - - To low-level format the floppy disk, use - &man.fdformat.1;. This utility expects the device name as - an argument. - - Make note of any error messages, as these can help + formatting is a good way to check media integrity. To + low-level format the floppy disk on &os;, use + &man.fdformat.1;. When using this utility, make note of any + error messages, as these can help determine if the disk is good or bad. - - - Formatting Floppy Disks - - To format the floppy, insert a new 3.5inch floppy + + + To format the floppy, insert a new 3.5 inch floppy disk into the first floppy drive and issue: &prompt.root; /usr/sbin/fdformat -f 1440 /dev/fd0 - - - - - - The Disk Label + - After low-level formatting the disk, a disk label needs to - placed on it. This disk label will be destroyed later, but + + After low-level formatting the disk, create a disk label as it is needed by the system to determine the size of the disk - and its geometry. - - The new disk label will take over the whole disk and will - contain all the proper information about the geometry of the - floppy. The geometry values for the disk label are listed in + and its geometry. The supported geometry values are listed in /etc/disktab. To write the disk label, use &man.bsdlabel.8;: &prompt.root; /sbin/bsdlabel -B -w /dev/fd0 fd1440 - - - - The File System - - The floppy is now ready to be high-level formatted. This - will place a new file system on it so that &os; can read and - write to the disk. Since creating the new file system - destroys the disk label, the disk label needs to be recreated - whenever the disk is reformatted. + - The floppy's file system can be either UFS or FAT. + + The floppy is now ready to be high-level formatted with a + file system. The floppy's file system can be either UFS or FAT, where FAT is generally a better choice for floppies. - To put a new file system on the floppy, issue: + To format the floppy with FAT, issue: &prompt.root; /sbin/newfs_msdos /dev/fd0 + + - The disk is now ready for use. - - - - Using the Floppy - - To use the floppy, mount it with &man.mount.msdosfs.8;. - One can also use + The disk is now ready for use. To use the floppy, mount it with &man.mount.msdosfs.8;. + One can also install and use emulators/mtools from the Ports Collection. - From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 15:28:22 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0063711F; Thu, 30 Jan 2014 15:28:21 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DFBCE16CE; Thu, 30 Jan 2014 15:28:21 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UFSLIU001019; Thu, 30 Jan 2014 15:28:21 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UFSLHp001018; Thu, 30 Jan 2014 15:28:21 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401301528.s0UFSLHp001018@svn.freebsd.org> From: Dru Lavigne Date: Thu, 30 Jan 2014 15:28:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43695 - head/en_US.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 15:28:22 -0000 Author: dru Date: Thu Jan 30 15:28:21 2014 New Revision: 43695 URL: http://svnweb.freebsd.org/changeset/doc/43695 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 15:18:49 2014 (r43694) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 15:28:21 2014 (r43695) @@ -1407,7 +1407,7 @@ cd0: Attempt to query device size failed - Creating and Using Floppy Disks + Creating and Using Floppy Disks - This section explains how to format a 3.5 inch floppy disk + This section explains how to format a 3.5 inch floppy disk in &os;. Steps to Format a Floppy - A floppy disk needs to be low-level formatted before it - can be used. This is usually done by the vendor, but - formatting is a good way to check media integrity. To - low-level format the floppy disk on &os;, use - &man.fdformat.1;. When using this utility, make note of any - error messages, as these can help - determine if the disk is good or bad. - - - To format the floppy, insert a new 3.5 inch floppy - disk into the first floppy drive and issue: + A floppy disk needs to be low-level formatted before it + can be used. This is usually done by the vendor, but + formatting is a good way to check media integrity. To + low-level format the floppy disk on &os;, use + &man.fdformat.1;. When using this utility, make note of any + error messages, as these can help determine if the disk is + good or bad. + + + To format the floppy, insert a new 3.5 inch floppy disk + into the first floppy drive and issue: &prompt.root; /usr/sbin/fdformat -f 1440 /dev/fd0 - + - - After low-level formatting the disk, create a disk label as - it is needed by the system to determine the size of the disk - and its geometry. The supported geometry values are listed in - /etc/disktab. + + After low-level formatting the disk, create a disk label + as it is needed by the system to determine the size of the + disk and its geometry. The supported geometry values are + listed in /etc/disktab. - To write the disk label, use &man.bsdlabel.8;: + To write the disk label, use &man.bsdlabel.8;: - &prompt.root; /sbin/bsdlabel -B -w /dev/fd0 fd1440 - + &prompt.root; /sbin/bsdlabel -B -w /dev/fd0 fd1440 + - - The floppy is now ready to be high-level formatted with a - file system. The floppy's file system can be either UFS or FAT, where - FAT is generally a better choice for floppies. + + The floppy is now ready to be high-level formatted with + a file system. The floppy's file system can be either UFS + or FAT, where FAT is generally a better choice for + floppies. - To format the floppy with FAT, issue: + To format the floppy with FAT, issue: - &prompt.root; /sbin/newfs_msdos /dev/fd0 + &prompt.root; /sbin/newfs_msdos /dev/fd0 - The disk is now ready for use. To use the floppy, mount it with &man.mount.msdosfs.8;. - One can also install and use - emulators/mtools from the - Ports Collection. + The disk is now ready for use. To use the floppy, mount it + with &man.mount.msdosfs.8;. One can also install and use + emulators/mtools from the Ports + Collection. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 18:17:32 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 90C52724; Thu, 30 Jan 2014 18:17:32 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B5BA16E0; Thu, 30 Jan 2014 18:17:32 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UIHWfo067515; Thu, 30 Jan 2014 18:17:32 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UIHWWm067514; Thu, 30 Jan 2014 18:17:32 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401301817.s0UIHWWm067514@svn.freebsd.org> From: Dru Lavigne Date: Thu, 30 Jan 2014 18:17:32 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43696 - head/en_US.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 18:17:32 -0000 Author: dru Date: Thu Jan 30 18:17:31 2014 New Revision: 43696 URL: http://svnweb.freebsd.org/changeset/doc/43696 Log: First half of edits to Backup sections. Merge 18.9 Backup Strategies and 18.10 Backup Basics. Clean up summary. Divide utilities into File System Backups and Directory Backups sections (not quite complete yet). Remove Do Nothing section (we don't want to encourage this). Remove Which Program is Best section as it is personal opinion and based on 23 year old findings. Next commit will finish the edits to this section. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 15:28:21 2014 (r43695) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 18:17:31 2014 (r43696) @@ -1576,11 +1576,11 @@ cd0: Attempt to query device size failed - - - Backup Strategies + + Backup Basics - + - The first requirement in devising a backup plan is to make - sure that all of the following problems are covered: - - - - Disk failure. - - - - Accidental file deletion. - - - - Random file corruption. - - - - Complete machine destruction, say by fire, including - destruction of any on-site backups. - - - - Some systems will be best served by having each of these - problems covered by a completely different technique. Except - for strictly personal systems with low-value data, it is - unlikely that one technique will cover all of them. - - Some possible techniques include: + Implementing a backup plan is essential in order to have the + ability to recover from disk failure, accidental file deletion, + random file corruption, or complete machine destruction, + including destruction of on-site backups. + + The backup type and schedule will vary, depending upon the + importance of the data, the granularity needed for file + restores, and the amount of acceptable downtime. Some possible + backup techniques include: Archives of the whole system, backed up onto permanent, off-site media. This provides protection against all of the problems listed above, but is slow and inconvenient to - restore from. Copies of the backups can be stored on site - or online, but there will still be inconveniences in - restoring files, especially for non-privileged users. - - - - Filesystem snapshots, which are really only helpful in - the accidental file deletion scenario, but can be - very helpful in that case, as well as - quick and easy to deal with. + restore from, especially for non-privileged users. - Copies of whole file systems or disks which can be - created with a periodic net/rsync of the - whole machine. This is generally most useful in networks - with unique requirements. For general protection against - disk failure, this is usually inferior to - RAID. For restoring accidentally deleted - files, it can be comparable to UFS - snapshots. + Filesystem snapshots, which are useful for restoring + deleted files or previous versions of files. - RAID, which minimizes or avoids - downtime when a disk fails at the expense of having to deal - with disk failures more often, because there are more disks, - albeit at a much lower urgency. + Copies of whole file systems or disks which are + sychronized with another system on the network using a + scheduled net/rsync. - Checking fingerprints of files using &man.mtree.8;. - Although this is not a backup, this technique indicates - when one needs to resort to backups. This is particularly - important for offline backups, and should be checked - periodically. + Hardware or software RAID, which minimizes or avoids + downtime when a disk fails. - It is quite easy to come up with more techniques, many - of them variations on the ones listed above. Specialized - requirements usually lead to specialized techniques. For - example, backing up a live database usually requires a method - particular to the database software as an intermediate step. - The important thing is to know which dangers should be protected - against, and how each will be handled. - - - - Backup Basics - - The major backup programs built into &os; are - &man.dump.8;, &man.tar.1;, &man.cpio.1;, and - &man.pax.1;. + Typically, a mix of backup techniques is used. For + example, one could create a schedule to automate a weekly, full + system backup that is stored off-site and to supplement this + backup with hourly ZFS snapshots. In addition, one could make a + manual backup of individual directories or files before making + file edits or deletions. + + This section describes some of the utilities which can be + used to create and manage backups on a &os; system. - Dump and Restore + File System Backups backup software @@ -1773,13 +1729,16 @@ cd0: Attempt to query device size failed - <command>tar</command> + Directory Backups backup software tar + Several built-in utilities are available for backing up + and restoring specified files and directories as needed. + &man.tar.1; also dates back to Version 6 of AT&T &unix;, circa 1975. tar operates in cooperation with the file system and writes files and @@ -1798,10 +1757,6 @@ cd0: Attempt to query device size failed When backing up over an insecure network, instead use ssh. - - - - <command>cpio</command> backup software @@ -1837,10 +1792,6 @@ cd0: Attempt to query device size failed backups, and backup_device is where the backups should be written to, such as /dev/nsa0). - - - - <command>pax</command> backup software @@ -1905,56 +1856,6 @@ cd0: Attempt to query device size failed - Do Nothing - - Do nothing is not a computer program, but - it is the most widely used backup strategy. There are no - initial costs. There is no backup schedule to follow. Just - say no. If something happens to your data, grin and bear - it! - - If your time and data is worth little to nothing, then - Do nothing is the most suitable backup program - for the computer. But beware, &os; is a useful tool and - over time it can be used to create a valuable collection of - files. - - Do nothing is the correct backup method for - /usr/obj and other - directory trees that can be exactly recreated by the computer. - An example is the files that comprise the HTML or &postscript; - version of this Handbook. These document formats have been - created from XML input files. Creating backups of the HTML or - &postscript; files is not necessary if the XML files are - backed up regularly. - - - - Which Backup Program Is Best? - - - LISA - - - &man.dump.8; Period. Elizabeth D. - Zwicky torture tested all the backup programs discussed here. - The clear choice for preserving all your data and all the - peculiarities of &unix; file systems is - dump. Elizabeth created file systems - containing a large variety of unusual conditions (and some not - so unusual ones) and tested each program by doing a backup and - restore of those file systems. The peculiarities included: - files with holes, files with holes and a block of nulls, files - with funny characters in their names, unreadable and - unwritable files, devices, files that change size during the - backup, files that are created/deleted during the backup and - more. She presented the results at LISA V in Oct. 1991. See - torture-testing - Backup and Archive Programs. - - - Emergency Restore Procedure From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 21:06:20 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B3207AD7; Thu, 30 Jan 2014 21:06:20 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9DBE61597; Thu, 30 Jan 2014 21:06:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UL6Ka6034023; Thu, 30 Jan 2014 21:06:20 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UL6KVB034022; Thu, 30 Jan 2014 21:06:20 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401302106.s0UL6KVB034022@svn.freebsd.org> From: Dru Lavigne Date: Thu, 30 Jan 2014 21:06:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43698 - head/en_US.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 21:06:20 -0000 Author: dru Date: Thu Jan 30 21:06:20 2014 New Revision: 43698 URL: http://svnweb.freebsd.org/changeset/doc/43698 Log: Next pass through this chapter. Clarified text in File System Backups Redid examples in Directory Backups to show how 3 utils differ when creating similar backups. New examples are aimed at what a new user is likely to do. More complex examples should be added. Next pass will finish this section, to be followed by white space fix-ups. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 19:00:09 2014 (r43697) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 21:06:20 2014 (r43698) @@ -1123,12 +1123,12 @@ cd0: Attempt to query device size failed In order to support working files larger than 4.38GB, an - UDF/ISO-9660 hybrid filesystem must be created by passing + UDF/ISO-9660 hybrid file system must be created by passing to &man.mkisofs.8; and all related programs, such as &man.growisofs.1;. This is required only when creating an ISO image file or when writing files directly to a disk. Since a disk created this - way must be mounted as an UDF filesystem with + way must be mounted as an UDF file system with &man.mount.udf.8;, it will be usable only on an UDF aware operating system. Otherwise it will look as if it contains corrupted files. @@ -1610,7 +1610,7 @@ cd0: Attempt to query device size failed - Filesystem snapshots, which are useful for restoring + File system snapshots, which are useful for restoring deleted files or previous versions of files. @@ -1650,24 +1650,20 @@ cd0: Attempt to query device size failed restore - The traditional &unix; backup programs are - dump and restore. They - operate on the drive as a collection of disk blocks, below the - abstractions of files, links and directories that are created - by the file systems. Unlike other backup software, - dump backs up an entire file system on a - device. It is unable to backup only part of a file system or - a directory tree that spans more than one file system. - dump does not write files and directories, - but rather writes the raw data blocks that comprise files and - directories. When used to extract data, - restore stores temporary files in - /tmp/ by default. When using a recovery - disk with a small /tmp, set - TMPDIR to a directory with more free space in - order for the restore to succeed. + The traditional &unix; programs for backing up a file + system are &man.dump.8;, which creates the backup, and + &man.restore.8;, which restores the backup. These utilities + work at the disk block level, below the + abstractions of the files, links, and directories that are created + by file systems. Unlike other backup software, + dump backs up an entire file system and + is unable to backup only part of a file system or + a directory tree that spans multiple file systems. + Instead of writing files and directories, dump + writes the raw data blocks that comprise files and + directories. - + If dump is used on the root directory, it will not back up /home, /usr or many other @@ -1675,39 +1671,34 @@ cd0: Attempt to query device size failed file systems or symbolic links into those file systems. + + When used to restore data, + restore stores temporary files in + /tmp/ by default. When using a recovery + disk with a small /tmp, set + TMPDIR to a directory with more free space in + order for the restore to succeed. - dump has quirks that remain from its + When using dump, be aware that some quirks remain from its early days in Version 6 of AT&T &unix;,circa 1975. The - default parameters are suitable for 9-track tapes (6250 bpi), - not the high-density media available today (up to 62,182 - ftpi). These defaults must be overridden on the command line - to utilize the capacity of current tape drives. + default parameters assume a backup to a 9-track tape, rather than + to another media or the high-density tapes available today. + These defaults must be overridden on the command line. .rhosts - It is also possible to backup data across the network to a - tape drive attached to another computer with - rdump and rrestore. - Both programs rely upon &man.rcmd.3; and &man.ruserok.3; to - access the remote tape drive. Therefore, the user performing - the backup must be listed in .rhosts on - the remote computer. The arguments to - rdump and rrestore must - be suitable to use on the remote computer. For example, to - rdump from a &os; computer to an Exabyte - tape drive connected to a host called - komodo, use: - - &prompt.root; /sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nsa8 /dev/da0a 2>&1 - - There are security implications to allowing - .rhosts authentication, so use - with caution. - - It is also possible to use dump and - restore in a more secure fashion over - ssh. + It is possible to backup a file system across the network to a + another system or to a tape drive attached to another computer. + While the &man.rdump.8; and &man.rrestore.8; utilities can be + used for this purpose, they are not considered to be secure. + + Instead, one can use dump and + restore in a more secure fashion over an + SSH connection. This example creates a + full, compressed backup of the /usr file + system and sends the backup file to the specified host over a + SSH connection. Using <command>dump</command> over @@ -1717,7 +1708,9 @@ cd0: Attempt to query device size failed targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz</userinput></screen> </example> - <para>Or, use the built-in <envar>RSH</envar>:</para> + <para>This example sets <envar>RSH</envar> in order to write the + the backup to a tape drive on a remote system over a + <acronym>SSH</acronym> connection:</para> <example> <title>Using <command>dump</command> over @@ -1738,60 +1731,73 @@ cd0: Attempt to query device size failed <para>Several built-in utilities are available for backing up and restoring specified files and directories as needed.</para> - - <para>&man.tar.1; also dates back to Version 6 of AT&T - &unix;, circa 1975. <command>tar</command> operates in - cooperation with the file system and writes files and - directories to tape. <command>tar</command> does not support - the full range of options that are available from - &man.cpio.1;, but it does not require the unusual command - pipeline that <command>cpio</command> uses.</para> + + <para>A good choice for making a backup of all of the files in a + directory is &man.tar.1;. This utility dates back to Version 6 of AT&T + &unix; and by default assumes a recursive backup to a local tape + device. Switches can be used to instead specify the name of + a backup file.</para> <indexterm><primary><command>tar</command></primary></indexterm> - <para>To <command>tar</command> to an Exabyte tape drive - connected to a host called - <systemitem>komodo</systemitem>:</para> + <para>This example creates a compressed backup of the current + directory and saves it to + <filename>/tmp/mybackup.tgz</filename>. When creating a + backup file, make sure that the backup is not saved to the + same directory that is being backed up.</para> + + <example> + <title>Backing Up the Current Directory With + <command>tar</command> + + &prompt.root; tar czvf /tmp/mybackup.tgz . + + + To restore the entire backup, cd into + the directory to restore into and specify the name of the + backup. Note that this will overwrite any newer versions of + files in the restore directory. When in doubt, restore to a + temporary directory or specify the name of the file within the + backup to restore. + + + Restoring Up the Current Directory With + <command>tar</command> - &prompt.root; tar cf - . | rsh komodo dd of=tape-device obs=20b + &prompt.root; tar xzvf /tmp/mybackup.tgz + - When backing up over an insecure network, instead use - ssh. + There are dozens of available switches which are described + in &man.tar.1;. This utility also supports the use of exclude + patterns to specify which files should not be included when + backing up the specified directory or restoring files from a + backup. backup software cpio - &man.cpio.1; is the original &unix; file interchange tape - program for magnetic media. cpio includes - options to perform byte-swapping, write a number of different - archive formats, and pipe the data to other programs. This - last feature makes cpio an excellent choice - for installation media. cpio does not know - how to walk the directory tree and a list of files must be - provided through stdin. - - - cpio - - - Since cpio does not support backups - across the network, use a pipeline and ssh - to send the data to a remote tape drive. - - &prompt.root; for f in directory_list; do -find $f >> backup.list -done -&prompt.root; cpio -v -o --format=newc < backup.list | ssh user@host "cat > backup_device" - - Where directory_list is the - list of directories to back up, - user@host - is the user/hostname combination that will be performing the - backups, and backup_device is where - the backups should be written to, such as - /dev/nsa0). + To create a backup using a specified list of files and + directories, &man.cpio.1; is a good choice. Unlike + tar, + cpio does not know + how to walk the directory tree and it must be provided the list of files + to backup. + + For example, a list of files can be created using + ls or find. This example + creates a recursive listing of the current directory which is + then piped to cpio in order to create an + output backup file named + /tmp/mybackup.cpio. + + + Using<command>ls</command> and <command>cpio</command> + to Make a Recursive Backup of the Current Directory + + &prompt.root; ls -R | cpio -ovF /tmp/mybackup.cpio + backup software @@ -1801,16 +1807,24 @@ cd0: Attempt to query device size failed POSIX IEEE - &man.pax.1; is the IEEE/&posix; answer to - tar and cpio. Over the - years the various versions of tar and - cpio have become slightly incompatible. So - rather than fight it out to fully standardize them, &posix; - created a new archive utility. pax + A backup utility which tries to bridge the features provided by + tar and cpio is &man.pax.1;. Over the + years, the various versions of tar and + cpio became slightly incompatible. &posix; + created pax which attempts to read and write many of the various cpio and tar formats, - plus new formats of its own. Its command set more resembles - cpio than tar. + plus new formats of its own. + + The pax equivalent to the previous + examples would be: + + + Backing Up the Current Directory With + <command>pax</command> + + &prompt.root; pax -wf /tmp/mybackup.pax . + @@ -1929,7 +1943,7 @@ cd0: Attempt to query device size failed Select the correct country, then choose Fixit -- Repair mode with CD-ROM/DVD/floppy or start a shell. then select - CD-ROM/DVD -- Use the live filesystem + CD-ROM/DVD -- Use the live file system CD-ROM/DVD. restore and the other needed programs are located in /mnt2/rescue. @@ -3588,13 +3602,13 @@ Device 1K-blocks Used Av reports 0 bytes of dirty extents. - The next step is to create a filesystem on the + The next step is to create a file system on the /dev/hast/test GEOM provider and mount it. This must be done on the primary node, as /dev/hast/test appears only on the primary node. Creating - the filesystem can take a few minutes, depending on the size + the file system can take a few minutes, depending on the size of the hard drive: &prompt.root; newfs -U /dev/hast/test From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 22:18:19 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BDB65EB; Thu, 30 Jan 2014 22:18:19 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 378E51CC2; Thu, 30 Jan 2014 22:18:19 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UMIJMA062264; Thu, 30 Jan 2014 22:18:19 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UMIIms062262; Thu, 30 Jan 2014 22:18:18 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201401302218.s0UMIIms062262@svn.freebsd.org> From: Glen Barber Date: Thu, 30 Jan 2014 22:18:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43699 - head/share/pgpkeys X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 22:18:19 -0000 Author: gjb Date: Thu Jan 30 22:18:18 2014 New Revision: 43699 URL: http://svnweb.freebsd.org/changeset/doc/43699 Log: Add PGP key for Dan Langille (dvl), obtained in person. Sponsored by: The FreeBSD Foundation Added: head/share/pgpkeys/dvl.key (contents, props changed) Modified: head/share/pgpkeys/pgpkeys.ent Added: head/share/pgpkeys/dvl.key ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/pgpkeys/dvl.key Thu Jan 30 22:18:18 2014 (r43699) @@ -0,0 +1,253 @@ + + + +uid Dan Langille +uid Dan Langille +uid Dan Langille +uid Dan Langille +uid Dan Langille +uid Dan Langille +uid Dan Langille +uid Dan Langille +sub 1024g/774275AAB7D6CC68 2000-12-28 + +]]> + Modified: head/share/pgpkeys/pgpkeys.ent ============================================================================== --- head/share/pgpkeys/pgpkeys.ent Thu Jan 30 21:06:20 2014 (r43698) +++ head/share/pgpkeys/pgpkeys.ent Thu Jan 30 22:18:18 2014 (r43699) @@ -122,6 +122,7 @@ + From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 22:27:27 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AEA94910; Thu, 30 Jan 2014 22:27:27 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A87B1D58; Thu, 30 Jan 2014 22:27:27 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UMRRhs065972; Thu, 30 Jan 2014 22:27:27 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UMRRvr065971; Thu, 30 Jan 2014 22:27:27 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401302227.s0UMRRvr065971@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 22:27:27 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43700 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 22:27:27 -0000 Author: wblock Date: Thu Jan 30 22:27:27 2014 New Revision: 43700 URL: http://svnweb.freebsd.org/changeset/doc/43700 Log: Add some and markup. Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 22:18:18 2014 (r43699) +++ head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 22:27:27 2014 (r43700) @@ -4924,7 +4924,7 @@ it was never committed: 1100001 October 19, 2013 11.0-CURRENT after addition of support for "first boot" - rc.d scripts, so ports can make use of this + rc.d scripts, so ports can make use of this (rev 256776). @@ -4945,7 +4945,7 @@ it was never committed: 1100004 December 15, 2013 - 11.0-CURRENT after the behavior change of gss_pseudo_random + 11.0-CURRENT after the behavior change of gss_pseudo_random introduced in r259286. (rev 259424) @@ -4953,7 +4953,7 @@ it was never committed: 1100005 December 28, 2013 - 11.0-CURRENT after r259951 - Don't coalesce entries in vm_map_stack() + 11.0-CURRENT after r259951 - Don't coalesce entries in vm_map_stack() (rev 260010). From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 22:29:48 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EC01989; Thu, 30 Jan 2014 22:29:48 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3A1F31D66; Thu, 30 Jan 2014 22:29:48 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UMTmUM066240; Thu, 30 Jan 2014 22:29:48 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UMTmKf066239; Thu, 30 Jan 2014 22:29:48 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401302229.s0UMTmKf066239@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 22:29:48 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43701 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 22:29:48 -0000 Author: wblock Date: Thu Jan 30 22:29:47 2014 New Revision: 43701 URL: http://svnweb.freebsd.org/changeset/doc/43701 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 22:27:27 2014 (r43700) +++ head/en_US.ISO8859-1/books/porters-handbook/versions.xml Thu Jan 30 22:29:47 2014 (r43701) @@ -4924,7 +4924,7 @@ it was never committed: 1100001 October 19, 2013 11.0-CURRENT after addition of support for "first boot" - rc.d scripts, so ports can make use of this + rc.d scripts, so ports can make use of this (rev 256776). @@ -4945,16 +4945,17 @@ it was never committed: 1100004 December 15, 2013 - 11.0-CURRENT after the behavior change of gss_pseudo_random - introduced in r259286. + 11.0-CURRENT after the behavior change of + gss_pseudo_random introduced in r259286. (rev 259424) 1100005 December 28, 2013 - 11.0-CURRENT after r259951 - Don't coalesce entries in vm_map_stack() - (rev 260010). + 11.0-CURRENT after r259951 - Don't coalesce entries in + vm_map_stack() (rev + 260010). From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 22:34:34 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6BFDEB14; Thu, 30 Jan 2014 22:34:34 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4BA201DE3; Thu, 30 Jan 2014 22:34:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UMYYS9069544; Thu, 30 Jan 2014 22:34:34 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UMYYDK069543; Thu, 30 Jan 2014 22:34:34 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401302234.s0UMYYDK069543@svn.freebsd.org> From: Dru Lavigne Date: Thu, 30 Jan 2014 22:34:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43702 - head/en_US.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 22:34:34 -0000 Author: dru Date: Thu Jan 30 22:34:33 2014 New Revision: 43702 URL: http://svnweb.freebsd.org/changeset/doc/43702 Log: Last pass through this chapter. Rename Amanda to Third-Party Backup Utilities. Add some examples of utils. This section is light-weight and could probably use another paragraph or two. Rename Emergency Repair Procedure to Emergency Recovery. Tighten up this section and put the emphasis on the newer installation media option as opposed to the older livefs option. Make editorial note to close PR48101 in 06/15 when 8.4 is EOl'd. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 22:29:47 2014 (r43701) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 22:34:33 2014 (r43702) @@ -1682,7 +1682,7 @@ cd0: Attempt to query device size failed When using dump, be aware that some quirks remain from its early days in Version 6 of AT&T &unix;,circa 1975. The default parameters assume a backup to a 9-track tape, rather than - to another media or the high-density tapes available today. + to another type of media or to the high-density tapes available today. These defaults must be overridden on the command line. @@ -1828,156 +1828,81 @@ cd0: Attempt to query device size failed - <application>Amanda</application> + Third-Party Backup Utilities backup software - Amanda - - - Amanda - - Amanda (Advanced Maryland - Network Disk Archiver) is a client/server backup system, - rather than a single program. An - Amanda server will backup to a - single tape drive any number of computers that have - Amanda clients and a network - connection to the Amanda server. A - common problem at sites with a number of large disks is that - the length of time required to backup to data directly to tape - exceeds the amount of time available for the task. - Amanda solves this problem by using - a holding disk to backup several file systems - at the same time. Amanda creates - archive sets: a group of tapes used over a - period of time to create full backups of all the file systems - listed in Amanda's configuration - file. The archive set also contains nightly - incremental, or differential, backups of all the file systems. - Restoring a damaged file system requires the most recent full - backup and the incremental backups. - - The configuration file provides fine grained control of - backups and the network traffic that - Amanda generates. - Amanda will use any of the above - backup programs to write the data to tape. - Amanda is not installed by - but is available as either a port or package. + The &os; Ports Collection provides many third-party + utilities which can be used to schedule the creation of + backups. Many of these applications are client/server based + and can be used to automate the backups of a single system or + all of the computers in a network. + + Popular utilities include + Amanda, + Bacula, + rsync, and + duplicity. + - Emergency Restore Procedure - - - Before the Disaster + Emergency Recovery - There are four steps which should be performed in - preparation for any disaster that may occur. + In addition to regular backups, it is recommended to + perform the following steps as part of an emergency + preparedness plan. bsdlabel - First, print the bsdlabel of each disk using a command - such as bsdlabel da0 | lpr. Also print a - copy of /etc/fstab and all boot - messages. + Create a print copy of the output of the following + commands: + + + + gpart show + + + + more /etc/fstab + + + + dmesg + + livefs CD - Second, burn a livefs CD. This CD - contains support for booting into a &os; - livefs rescue mode, allowing the user to - perform many tasks like running &man.dump.8;, - &man.restore.8;, &man.fdisk.8;, &man.bsdlabel.8;, - &man.newfs.8;, &man.mount.8;, and more. The livefs CD image - for &os;/&arch.i386; &rel2.current;-RELEASE is - available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. + Store this printout and a copy of the installation media + in a secure location. Should an emergency restore be + needed, boot into the installation media and select + Live CD to access a rescue shell. This + rescue mode can be used to view the current state of the + system, and if needed, to reformat disks and restore data + from backups. - Livefs CD images are not available for - &os; &rel.current;-RELEASE and later. In addition to - the CD-ROM installation images, flash drive installation - images may be used to recover a system. The - memstick image for - &os;/&arch.i386; &rel.current;-RELEASE is available - from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img. + The installation media + for &os;/&arch.i386; &rel2.current;-RELEASE does not + include a rescue shell. For this version, instead + download and burn a Livefs CD image from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. - Third, create backup tapes regularly. Any changes that - made after the last backup may be irretrievably lost. - Write-protect the backup media. - - Fourth, test the livefs CD and the + Next, test the rescue shell and the backups. Make notes of the procedure. Store these notes - with the CD, the printouts, and the backups. These notes + with the media, the printouts, and the backups. These notes may prevent the inadvertent destruction of the backups while under the stress of performing an emergency recovery. - For an added measure of security, store an extra - livefs CD and the latest backup at a - remote location, where a remote location is - not the basement of the same building. - A remote location should be physically separated from the + For an added measure of security, store the latest backup at a + remote location which is + physically separated from the computers and disk drives by a significant distance. - - - - After the Disaster - - First, determine if the hardware survived. Thanks - to regular, off-site backups, there is no need to worry - about the software. - - If the hardware has been damaged, the parts should be - replaced before attempting to use the computer. - - If the hardware is okay, insert the - livefs CD and boot the computer. The - original install menu will be displayed on the screen. - Select the correct country, then choose - Fixit -- Repair mode with CD-ROM/DVD/floppy or - start a shell. then select - CD-ROM/DVD -- Use the live file system - CD-ROM/DVD. - restore and the other needed programs - are located in /mnt2/rescue. - - Recover each file system separately. - - - mount - - root partition - - bsdlabel - - - newfs - - - Try to mount the root partition - of the first disk using mount /dev/da0a - /mnt. If the bsdlabel was damaged, use - bsdlabel to re-partition and label the - disk to match the label that was printed and saved. Use - newfs to re-create the file systems. - Re-mount the root partition of the disk read-write using - mount -u -o rw /mnt. Use the backups - to recover the data for this file system. Unmount the file - system with umount /mnt. Repeat for each - file system that was damaged. - - Once the system is running, backup the data onto new - media as whatever caused the crash or data loss may strike - again. Another hour spent now may save further distress - later. - From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 22:57:31 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0F5AE28; Thu, 30 Jan 2014 22:57:31 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ABB4C1F1D; Thu, 30 Jan 2014 22:57:31 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UMvVLQ077326; Thu, 30 Jan 2014 22:57:31 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UMvVSL077325; Thu, 30 Jan 2014 22:57:31 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401302257.s0UMvVSL077325@svn.freebsd.org> From: Dru Lavigne Date: Thu, 30 Jan 2014 22:57:31 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43703 - head/en_US.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 22:57:31 -0000 Author: dru Date: Thu Jan 30 22:57:31 2014 New Revision: 43703 URL: http://svnweb.freebsd.org/changeset/doc/43703 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 22:34:33 2014 (r43702) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 22:57:31 2014 (r43703) @@ -1621,18 +1621,18 @@ cd0: Attempt to query device size failed - Hardware or software RAID, which minimizes or avoids - downtime when a disk fails. + Hardware or software RAID, which + minimizes or avoids downtime when a disk fails. - Typically, a mix of backup techniques is used. For - example, one could create a schedule to automate a weekly, full + Typically, a mix of backup techniques is used. For + example, one could create a schedule to automate a weekly, full system backup that is stored off-site and to supplement this backup with hourly ZFS snapshots. In addition, one could make a - manual backup of individual directories or files before making + manual backup of individual directories or files before making file edits or deletions. - + This section describes some of the utilities which can be used to create and manage backups on a &os; system. @@ -1651,47 +1651,47 @@ cd0: Attempt to query device size failed The traditional &unix; programs for backing up a file - system are &man.dump.8;, which creates the backup, and + system are &man.dump.8;, which creates the backup, and &man.restore.8;, which restores the backup. These utilities - work at the disk block level, below the - abstractions of the files, links, and directories that are created - by file systems. Unlike other backup software, - dump backs up an entire file system and - is unable to backup only part of a file system or - a directory tree that spans multiple file systems. - Instead of writing files and directories, dump - writes the raw data blocks that comprise files and - directories. + work at the disk block level, below the abstractions of the + files, links, and directories that are created by file + systems. Unlike other backup software, + dump backs up an entire file system and is + unable to backup only part of a file system or a directory + tree that spans multiple file systems. Instead of writing + files and directories, dump writes the raw + data blocks that comprise files and directories. - + If dump is used on the root directory, it will not back up /home, - /usr or many other - directories since these are typically mount points for other - file systems or symbolic links into those file - systems. + /usr or many other directories since + these are typically mount points for other file systems or + symbolic links into those file systems. - - When used to restore data, - restore stores temporary files in - /tmp/ by default. When using a recovery - disk with a small /tmp, set - TMPDIR to a directory with more free space in - order for the restore to succeed. - - When using dump, be aware that some quirks remain from its - early days in Version 6 of AT&T &unix;,circa 1975. The - default parameters assume a backup to a 9-track tape, rather than - to another type of media or to the high-density tapes available today. - These defaults must be overridden on the command line. + + When used to restore data, restore + stores temporary files in /tmp/ by + default. When using a recovery disk with a small + /tmp, set TMPDIR to a + directory with more free space in order for the restore to + succeed. + + When using dump, be aware that some + quirks remain from its early days in Version 6 of + AT&T &unix;,circa 1975. The default parameters assume a + backup to a 9-track tape, rather than to another type of media + or to the high-density tapes available today. These defaults + must be overridden on the command line. .rhosts - It is possible to backup a file system across the network to a - another system or to a tape drive attached to another computer. - While the &man.rdump.8; and &man.rrestore.8; utilities can be - used for this purpose, they are not considered to be secure. + It is possible to backup a file system across the network + to a another system or to a tape drive attached to another + computer. While the &man.rdump.8; and &man.rrestore.8; + utilities can be used for this purpose, they are not + considered to be secure. Instead, one can use dump and restore in a more secure fashion over an @@ -1708,7 +1708,7 @@ cd0: Attempt to query device size failed targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz - This example sets RSH in order to write the + This example sets RSH in order to write the the backup to a tape drive on a remote system over a SSH connection: @@ -1730,26 +1730,27 @@ cd0: Attempt to query device size failed Several built-in utilities are available for backing up - and restoring specified files and directories as needed. + and restoring specified files and directories as + needed. A good choice for making a backup of all of the files in a - directory is &man.tar.1;. This utility dates back to Version 6 of AT&T - &unix; and by default assumes a recursive backup to a local tape - device. Switches can be used to instead specify the name of - a backup file. + directory is &man.tar.1;. This utility dates back to Version + 6 of AT&T &unix; and by default assumes a recursive backup + to a local tape device. Switches can be used to instead + specify the name of a backup file. tar This example creates a compressed backup of the current - directory and saves it to + directory and saves it to /tmp/mybackup.tgz. When creating a backup file, make sure that the backup is not saved to the same directory that is being backed up. - Backing Up the Current Directory With + <title>Backing Up the Current Directory With <command>tar</command> - + &prompt.root; tar czvf /tmp/mybackup.tgz . @@ -1761,11 +1762,11 @@ cd0: Attempt to query device size failed backup to restore. - Restoring Up the Current Directory With + <title>Restoring Up the Current Directory With <command>tar</command> &prompt.root; tar xzvf /tmp/mybackup.tgz - + There are dozens of available switches which are described in &man.tar.1;. This utility also supports the use of exclude @@ -1778,26 +1779,25 @@ cd0: Attempt to query device size failed cpio - To create a backup using a specified list of files and + To create a backup using a specified list of files and directories, &man.cpio.1; is a good choice. Unlike - tar, - cpio does not know - how to walk the directory tree and it must be provided the list of files - to backup. + tar, cpio does not know + how to walk the directory tree and it must be provided the + list of files to backup. For example, a list of files can be created using - ls or find. This example - creates a recursive listing of the current directory which is - then piped to cpio in order to create an - output backup file named + ls or find. This + example creates a recursive listing of the current directory + which is then piped to cpio in order to + create an output backup file named /tmp/mybackup.cpio. Using<command>ls</command> and <command>cpio</command> to Make a Recursive Backup of the Current Directory - + &prompt.root; ls -R | cpio -ovF /tmp/mybackup.cpio - + backup software @@ -1807,24 +1807,24 @@ cd0: Attempt to query device size failed POSIX IEEE - A backup utility which tries to bridge the features provided by - tar and cpio is &man.pax.1;. Over the - years, the various versions of tar and - cpio became slightly incompatible. &posix; - created pax which - attempts to read and write many of the various + A backup utility which tries to bridge the features + provided by tar and cpio + is &man.pax.1;. Over the years, the various versions of + tar and cpio became + slightly incompatible. &posix; created pax + which attempts to read and write many of the various cpio and tar formats, plus new formats of its own. The pax equivalent to the previous - examples would be: - + examples would be: + - Backing Up the Current Directory With + <title>Backing Up the Current Directory With <command>pax</command> &prompt.root; pax -wf /tmp/mybackup.pax . - + @@ -1839,70 +1839,67 @@ cd0: Attempt to query device size failed backups. Many of these applications are client/server based and can be used to automate the backups of a single system or all of the computers in a network. - + Popular utilities include - Amanda, + Amanda, Bacula, rsync, and - duplicity. - + duplicity. Emergency Recovery - In addition to regular backups, it is recommended to - perform the following steps as part of an emergency - preparedness plan. - - bsdlabel - - - Create a print copy of the output of the following - commands: - - - - gpart show - - - - more /etc/fstab - - - - dmesg - - + In addition to regular backups, it is recommended to + perform the following steps as part of an emergency + preparedness plan. + + + bsdlabel + + Create a print copy of the output of the following + commands: + + + + gpart show + + + + more /etc/fstab + + + + dmesg + + + + livefs CD + Store this printout and a copy of the installation media + in a secure location. Should an emergency restore be + needed, boot into the installation media and select + Live CD to access a rescue shell. This + rescue mode can be used to view the current state of the + system, and if needed, to reformat disks and restore data + from backups. + + + The installation media for + &os;/&arch.i386; &rel2.current;-RELEASE does not + include a rescue shell. For this version, instead + download and burn a Livefs CD image from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. + - livefs CD - Store this printout and a copy of the installation media - in a secure location. Should an emergency restore be - needed, boot into the installation media and select - Live CD to access a rescue shell. This - rescue mode can be used to view the current state of the - system, and if needed, to reformat disks and restore data - from backups. - - - The installation media - for &os;/&arch.i386; &rel2.current;-RELEASE does not - include a rescue shell. For this version, instead - download and burn a Livefs CD image from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. - - - Next, test the rescue shell and the - backups. Make notes of the procedure. Store these notes - with the media, the printouts, and the backups. These notes - may prevent the inadvertent destruction of the backups while - under the stress of performing an emergency - recovery. - - For an added measure of security, store the latest backup at a - remote location which is - physically separated from the - computers and disk drives by a significant distance. + Next, test the rescue shell and the backups. Make notes + of the procedure. Store these notes with the media, the + printouts, and the backups. These notes may prevent the + inadvertent destruction of the backups while under the stress + of performing an emergency recovery. + + For an added measure of security, store the latest backup + at a remote location which is physically separated from the + computers and disk drives by a significant distance. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 23:09:22 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B0CBA273; Thu, 30 Jan 2014 23:09:22 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A4EB1FD2; Thu, 30 Jan 2014 23:09:22 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UN9Mwo081720; Thu, 30 Jan 2014 23:09:22 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UN9MVm081719; Thu, 30 Jan 2014 23:09:22 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401302309.s0UN9MVm081719@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 23:09:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43704 - head/en_US.ISO8859-1/books/handbook/config X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 23:09:22 -0000 Author: wblock Date: Thu Jan 30 23:09:22 2014 New Revision: 43704 URL: http://svnweb.freebsd.org/changeset/doc/43704 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/config/chapter.xml Thu Jan 30 22:57:31 2014 (r43703) +++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Thu Jan 30 23:09:22 2014 (r43704) @@ -4,26 +4,53 @@ $FreeBSD$ --> - - Configuration and Tuning + + + + Configuration and Tuning + - ChernLeeWritten by + + + Chern + Lee + + Written by + + - MikeSmithBased on a tutorial written by + + + Mike + Smith + + Based on a tutorial written by + + - MattDillonAlso based on tuning(7) written by + + + Matt + Dillon + + Also based on tuning(7) written by + - - Synopsis - system configuration - system optimization + + system configuration + + + system optimization + One of the important aspects of &os; is proper system configuration. This chapter explains much of the &os; @@ -54,7 +81,8 @@ - How to use the various configuration files in /etc. + How to use the various configuration files in + /etc. @@ -71,7 +99,8 @@ - Understand &unix; and &os; basics (). + Understand &unix; and &os; basics + (). @@ -106,39 +135,38 @@ faster from the outer tracks to the inner. Thus, smaller and heavier-accessed file systems should be closer to the outside of the drive, while larger partitions like - /usr should be placed - toward the inner parts of the disk. It is a good idea to - create partitions in an order similar to: /, swap, + /usr should be placed toward the inner + parts of the disk. It is a good idea to create partitions + in an order similar to: /, swap, /var, and /usr. - The size of the - /var partition - reflects the intended machine's usage. This partition - is used to hold mailboxes, log files, and printer spools. + The size of the /var partition + reflects the intended machine's usage. This partition is + used to hold mailboxes, log files, and printer spools. Mailboxes and log files can grow to unexpected sizes - depending on the number of users and how long log files - are kept. On average, most users rarely need more than - about a gigabyte of free disk space in /var. + depending on the number of users and how long log files are + kept. On average, most users rarely need more than about a + gigabyte of free disk space in + /var. Sometimes, a lot of disk space is required in - /var/tmp. When - new software is installed with &man.pkg.add.1;, the - packaging tools extract a temporary copy of the packages - under /var/tmp. - Large software packages, like - Firefox, + /var/tmp. When new software is + installed with &man.pkg.add.1;, the packaging tools + extract a temporary copy of the packages under + /var/tmp. Large software packages, + like Firefox, OpenOffice or LibreOffice may be tricky to - install if there is not enough disk space under /var/tmp. + install if there is not enough disk space under + /var/tmp. - The /usr - partition holds many of the files which support the system, - including the &os; Ports Collection and system source code. - At least 2 gigabytes is recommended for this - partition. + The /usr partition holds many of + the files which support the system, including the &os; Ports + Collection and system source code. At least 2 gigabytes is + recommended for this partition. When selecting partition sizes, keep the space requirements in mind. Running out of space in one partition @@ -147,17 +175,21 @@ The Auto-defaults partition sizer used by &man.sysinstall.8; will sometimes select smaller - than adequate /var - and / partitions. - Partition wisely and generously. + than adequate /var and + / partitions. Partition wisely and + generously. Swap Partition - swap sizing - swap partition + + swap sizing + + + swap partition + As a rule of thumb, the swap partition should be about double the size of physical memory (RAM) @@ -191,9 +223,11 @@ fine, but there are several reasons why this is a bad idea. First, each partition has different operational characteristics and separating them allows the file system - to tune accordingly. For example, the root and /usr partitions are - read-mostly, with few writes, while a lot of reads and - writes could occur in /var and /var/tmp. + to tune accordingly. For example, the root and + /usr partitions are read-mostly, with + few writes, while a lot of reads and writes could occur in + /var and + /var/tmp. By properly partitioning a system, fragmentation introduced in the smaller write heavy partitions will not @@ -202,11 +236,11 @@ increase I/O performance in the partitions where it occurs the most. While I/O performance in the larger partitions may be needed, shifting them more toward the edge of the - disk will not lead to a significant performance - improvement over moving /var to the edge. Finally, - there are safety concerns. A smaller, neater root - partition which is mostly read-only has a greater chance of - surviving a bad crash. + disk will not lead to a significant performance improvement + over moving /var to the edge. Finally, + there are safety concerns. A smaller, neater root partition + which is mostly read-only has a greater chance of surviving + a bad crash. @@ -286,9 +320,10 @@ ifconfig_fxp0="inet 10.1.1.1/8"/usr/local/etc - Typically, these files are installed in /usr/local/etc. In the case - where an application has a large number of configuration - files, a subdirectory will be created to hold them. + Typically, these files are installed in + /usr/local/etc. In the case where an + application has a large number of configuration files, a + subdirectory will be created to hold them. Normally, when a port or package is installed, sample configuration files are also installed. These are usually @@ -318,22 +353,30 @@ ifconfig_fxp0="inet 10.1.1.1/8" - Starting Services + + Starting Services + - TomRhodesContributed by + + + Tom + Rhodes + + Contributed by + - - - services + + services + Many users install third party software on &os; from the Ports Collection and require the installed services to be started upon system initialization. Services, such as mail/postfix or - www/apache22 are just two - of the many software packages which may be started during system + www/apache22 are just two of the many + software packages which may be started during system initialization. This section explains the procedures available for starting third party software. @@ -345,7 +388,8 @@ ifconfig_fxp0="inet 10.1.1.1/8"Now that &os; includes rc.d, configuration of application startup is easier and provides - more features. Using the key words discussed in , applications can be set to + more features. Using the key words discussed in + , applications can be set to start after certain other services and extra flags can be passed through /etc/rc.conf in place of hard coded flags in the start up script. A basic script may @@ -416,50 +460,62 @@ run_rc_command "$1" - Configuring &man.cron.8; + + Configuring &man.cron.8; + - TomRhodesContributed by + + + Tom + Rhodes + + Contributed by + - - cron - configuration + + cron + configuration + One of the most useful utilities in &os; is &man.cron.8;. This utility runs in the background and regularly checks /etc/crontab for tasks to execute and - searches /var/cron/tabs - for custom &man.crontab.5; files. These files store - information about specific functions which &man.cron.8; is - supposed to perform at certain times. + searches /var/cron/tabs for custom + &man.crontab.5; files. These files store information about + specific functions which &man.cron.8; is supposed to perform at + certain times. Two different types of configuration files are used by &man.cron.8;: the system crontab and user - crontabs. These formats only differ in - the sixth field and later. In the system + crontabs. These formats only differ in the + sixth field and later. In the system crontab, &man.cron.8; runs the command as the user specified in the sixth field. In a user crontab, all commands run as the user who - created the crontab, so the sixth field - is the last field; this is an important security feature. - The final field is always the command to run. + created the crontab, so the sixth field is + the last field; this is an important security feature. The + final field is always the command to run. User crontabs allow individual users to schedule tasks - without the need for root privileges. + without the need for + root privileges. Commands in a user's crontab run with the permissions of the user who owns the crontab. - The root user can have a user - crontab just like any other user. The - root user crontab - is separate from the system crontab, + The root user + can have a user crontab just like any + other user. The + root user + crontab is separate from the system + crontab, /etc/crontab. Because the system crontab invokes the specified commands as - root, there is usually no need to create - a user crontab for - root. + root, there is + usually no need to create a user crontab + for root. Here is a sample entry from @@ -527,8 +583,9 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin * characters mean first-last, and can be interpreted as every time. In this example, - &man.atrun.8; is invoked by root - every five minutes, regardless of the day or month. + &man.atrun.8; is invoked by + root every five + minutes, regardless of the day or month. Commands can have any number of flags passed to them; however, commands which extend to multiple lines need to be @@ -548,11 +605,11 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin Do not use the procedure described here to edit and install the system crontab, - /etc/crontab. Instead, use an - editor and &man.cron.8; will notice that the file has - changed and immediately begin using the updated version. - See - this FAQ entry for more information. + /etc/crontab. Instead, use an editor + and &man.cron.8; will notice that the file has changed and + immediately begin using the updated version. See this + FAQ entry for more information. To install a freshly written user &man.crontab.5;, use @@ -581,14 +638,20 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin - Using &man.rc.8; Under &os; + + Using &man.rc.8; Under &os; + - TomRhodesContributed by + + + Tom + Rhodes + + Contributed by + - - In 2002, &os; integrated the NetBSD &man.rc.8; system for system initialization. The files listed in /etc/rc.d provide basic @@ -646,7 +709,8 @@ sshd_enable="YES" The # sshd line is output from the - above command, not a root console. + above command, not a + root console. To determine whether or not a service is running, use @@ -723,20 +787,27 @@ sshd is running as pid 433. systems. Additional information can be found in &man.rc.8; and - &man.rc.subr.8;. Refer to this article for - instructions on how to create custom &man.rc.8; + &man.rc.subr.8;. Refer to this article + for instructions on how to create custom &man.rc.8; scripts. - Setting Up Network Interface Cards + + Setting Up Network Interface Cards + - MarcFonvieilleContributed by + + + Marc + Fonvieille + + Contributed by + - - network cards configuration @@ -812,10 +883,11 @@ dc1: [ITHREAD] Alternatively, statically compile support for the NIC into a custom kernel. Refer to /usr/src/sys/conf/NOTES, - /usr/src/sys/arch/conf/NOTES - and the manual page of the driver to determine which line - to add to the custom kernel configuration file. For more - information about recompiling the kernel, refer to . If the + /usr/src/sys/arch/conf/NOTES and the + manual page of the driver to determine which line to add + to the custom kernel configuration file. For more + information about recompiling the kernel, refer to + . If the NIC was detected at boot, the kernel does not need to be recompiled. @@ -824,10 +896,17 @@ dc1: [ITHREAD] Using &windows; <acronym>NDIS</acronym> Drivers - NDIS - NDISulator - &windows; drivers - µsoft.windows; + + NDIS + + + NDISulator + + + &windows; drivers + + + µsoft.windows; device drivers @@ -887,7 +966,8 @@ linuxemu/chapter.xml --> &os;/amd64, a &windows; 64-bit driver is needed. The next step is to compile the driver binary into a - loadable kernel module. As root, use + loadable kernel module. As + root, use &man.ndisgen.8;: &prompt.root; ndisgen /path/to/W32DRIVER.INF /path/to/W32DRIVER.SYS @@ -928,9 +1008,9 @@ ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18M To configure the system to load the &man.ndis.4; modules at boot time, copy the generated module, - W32DRIVER_SYS.ko, to /boot/modules. Then, add the - following line to - /boot/loader.conf: + W32DRIVER_SYS.ko, to + /boot/modules. Then, add the following + line to /boot/loader.conf: W32DRIVER_SYS_load="YES" @@ -1010,22 +1090,27 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M The card has an Internet (inet) - address, 192.168.1.3. + address, 192.168.1.3. It has a valid subnet mask - (netmask), where 0xffffff00 is the same as - 255.255.255.0. + (netmask), where + 0xffffff00 is the + same as 255.255.255.0. - It has a valid broadcast address, 192.168.1.255. + It has a valid broadcast address, 192.168.1.255. The MAC address of the card - (ether) is 00:a0:cc:da:da:da. + (ether) is 00:a0:cc:da:da:da. @@ -1059,13 +1144,14 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M it would indicate the card has not been configured. - The card must be configured as root. - The NIC configuration can be performed - from the command line with &man.ifconfig.8; but will not - persist after a reboot unless the configuration is also added - to /etc/rc.conf. Add a line for each - NIC present on the system, as seen in - this example: + The card must be configured as + root. The + NIC configuration can be performed from the + command line with &man.ifconfig.8; but will not persist after + a reboot unless the configuration is also added to + /etc/rc.conf. Add a line for each + NIC present on the system, as seen in this + example: ifconfig_dc0="inet 192.168.1.3 netmask 255.255.255.0" ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP" @@ -1266,21 +1352,24 @@ round-trip min/avg/max/stddev = 0.700/0. For example, consider the case where the fxp0 interface is connected to two - networks: 10.1.1.0 with a - netmask of 255.255.255.0 and - 202.0.75.16 with a netmask of - 255.255.255.240. The system - is to be configured to appear in the ranges + networks: 10.1.1.0 + with a netmask of + 255.255.255.0 and + 202.0.75.16 with a + netmask of + 255.255.255.240. The + system is to be configured to appear in the ranges 10.1.1.1 through 10.1.1.5 and 202.0.75.17 through - 202.0.75.20. Only the first - address in a given network range should have a real netmask. - All the rest (10.1.1.2 through + 202.0.75.20. Only + the first address in a given network range should have a real + netmask. All the rest + (10.1.1.2 through 10.1.1.5 and 202.0.75.18 through - 202.0.75.20) must be configured - with a netmask of + 202.0.75.20) must be + configured with a netmask of 255.255.255.255. The following /etc/rc.conf entries @@ -1298,18 +1387,30 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n - Configuring the System Logger, - <command>syslogd</command> + + Configuring the System Logger, + <command>syslogd</command> + - NiclasZeisingContributed by + + + Niclas + Zeising + + Contributed by + - - - system logging - syslog - &man.syslogd.8; + + system logging + + + syslog + + + &man.syslogd.8; + System logging is an important aspect of system administration. It is used to detect hardware and software @@ -1322,7 +1423,8 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n system logger, &man.syslogd.8;, and how to perform log rotation and log management using &man.newsyslog.8;. Focus will be on setting up and using &man.syslogd.8; on a local machine. For - more advanced setups using a separate loghost, see . + more advanced setups using a separate loghost, see + . Using <command>syslogd</command> @@ -1857,12 +1959,19 @@ security.bsd.see_other_uids=0 - &man.sysctl.8; Read-only + + &man.sysctl.8; Read-only + - TomRhodesContributed by + + + Tom + Rhodes + + Contributed by + - In some cases it may be desirable to modify read-only &man.sysctl.8; values, which will require a reboot of the @@ -2550,7 +2659,8 @@ kern.maxvnodes: 100000 on an existing partition. For information on how to encrypt swap space, which options - exist, and why it should be done, refer to . + exist, and why it should be done, refer to + . Swap on a New or Existing Hard Drive @@ -2652,15 +2762,27 @@ kern.maxvnodes: 100000 - Power and Resource Management + + Power and Resource Management + - HitenPandyaWritten by - TomRhodes + + + Hiten + Pandya + + Written by + + + + + Tom + Rhodes + + - - It is important to utilize hardware resources in an efficient manner. Before the Advanced Configuration and Power Interface (ACPI) was introduced, it was @@ -2790,18 +2912,37 @@ kern.maxvnodes: 100000 - Using and Debugging &os; <acronym>ACPI</acronym> + + Using and Debugging &os; <acronym>ACPI</acronym> + - NateLawsonWritten by + + + Nate + Lawson + + Written by + + - PeterSchultzWith contributions from - TomRhodes + + + Peter + Schultz + + With contributions from + + + + + Tom + Rhodes + + - - ACPI problems @@ -2925,11 +3066,12 @@ kern.maxvnodes: 100000 ACPI subsystem. For &os;, &intel; has provided an interpreter (ACPI-CA) that is shared with &linux; and NetBSD. The path to the - ACPI-CA source code is src/sys/contrib/dev/acpica. - The glue code that allows ACPI-CA to work - on &os; is in src/sys/dev/acpica/Osd. - Finally, drivers that implement various - ACPI devices are found in src/sys/dev/acpica. + ACPI-CA source code is + src/sys/contrib/dev/acpica. The glue + code that allows ACPI-CA to work on &os; is + in src/sys/dev/acpica/Osd. Finally, + drivers that implement various ACPI devices + are found in src/sys/dev/acpica. @@ -3320,11 +3462,12 @@ acpi_dsdt_name="/boot/DSDT.aml" - Install acpi.ko in /boot/kernel and add the - desired level and layer to - /boot/loader.conf. This example enables - debug messages for all ACPI-CA components - and all ACPI hardware drivers such as + Install acpi.ko in + /boot/kernel and add the desired level + and layer to /boot/loader.conf. This + example enables debug messages for all + ACPI-CA components and all + ACPI hardware drivers such as (CPU and LID. It only outputs error messages at the least verbose level. @@ -3353,30 +3496,30 @@ debug.acpi.level="ACPI_LV_ERROR" - The ACPI Mailing List Archives - http://lists.freebsd.org/pipermail/freebsd-acpi/ + The ACPI Mailing List Archives http://lists.freebsd.org/pipermail/freebsd-acpi/ The old ACPI Mailing List Archives - http://home.jp.FreeBSD.org/mail-list/acpi-jp/ + http://home.jp.FreeBSD.org/mail-list/acpi-jp/ - The ACPI 2.0 Specification - http://acpi.info/spec.htm + The ACPI 2.0 Specification http://acpi.info/spec.htm - &man.acpi.4;, - &man.acpi.thermal.4;, &man.acpidump.8;, &man.iasl.8;, - and &man.acpidb.8; + &man.acpi.4;, &man.acpi.thermal.4;, &man.acpidump.8;, + &man.iasl.8;, and &man.acpidb.8; - - DSDT debugging - resource. + DSDT + debugging resource. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 23:42:09 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED24DA31; Thu, 30 Jan 2014 23:42:09 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D90321268; Thu, 30 Jan 2014 23:42:09 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UNg9Bj096002; Thu, 30 Jan 2014 23:42:09 GMT (envelope-from delphij@svn.freebsd.org) Received: (from delphij@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UNg9uK096001; Thu, 30 Jan 2014 23:42:09 GMT (envelope-from delphij@svn.freebsd.org) Message-Id: <201401302342.s0UNg9uK096001@svn.freebsd.org> From: Xin LI Date: Thu, 30 Jan 2014 23:42:09 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43705 - head/en_US.ISO8859-1/htdocs/security X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 23:42:10 -0000 Author: delphij Date: Thu Jan 30 23:42:09 2014 New Revision: 43705 URL: http://svnweb.freebsd.org/changeset/doc/43705 Log: 8.4-RELEASE is the last release of stable/8, mark it so. Confirmed with: re (gjb) Modified: head/en_US.ISO8859-1/htdocs/security/security.xml Modified: head/en_US.ISO8859-1/htdocs/security/security.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/security/security.xml Thu Jan 30 23:09:22 2014 (r43704) +++ head/en_US.ISO8859-1/htdocs/security/security.xml Thu Jan 30 23:42:09 2014 (r43705) @@ -77,7 +77,7 @@ n/a n/a n/a - last release + 2 years + June 30, 2015 releng/8.3 From owner-svn-doc-all@FreeBSD.ORG Fri Jan 31 15:30:55 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C65D1E33; Fri, 31 Jan 2014 15:30:55 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A8EEF1AF1; Fri, 31 Jan 2014 15:30:55 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VFUtkI067804; Fri, 31 Jan 2014 15:30:55 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VFUtnZ067802; Fri, 31 Jan 2014 15:30:55 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401311530.s0VFUtnZ067802@svn.freebsd.org> From: Dru Lavigne Date: Fri, 31 Jan 2014 15:30:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43706 - in head/en_US.ISO8859-1/books/handbook: advanced-networking network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 15:30:55 -0000 Author: dru Date: Fri Jan 31 15:30:54 2014 New Revision: 43706 URL: http://svnweb.freebsd.org/changeset/doc/43706 Log: First 1/2 of edits to this section. Shuffle content into a more logical order and clarify text. Rename a few sub-sections and remove reference to a section that was merged into another section. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Jan 30 23:42:09 2014 (r43705) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Fri Jan 31 15:30:54 2014 (r43706) @@ -4232,7 +4232,7 @@ cd /usr/src/etc; make distribution Enable &man.inetd.8; by following the steps outlined - in . + in . Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Thu Jan 30 23:42:09 2014 (r43705) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 15:30:54 2014 (r43706) @@ -132,20 +132,20 @@ --> The <application>inetd</application> - <quote>Super-Server</quote> + Super-Server - Overview - The &man.inetd.8; daemon is sometimes referred to as the - Internet Super-Server because it manages - connections for many 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 + The &man.inetd.8; daemon is sometimes referred to as a + Super-Server because it manages + connections for many services. Instead of starting multiple + applications, only the inetd service + needs to be started. When a connection is received + for a service that is managed by inetd, it determines which + program the connection is destined for, spawns a + process for that program, and delegates the program a socket. + Using inetd + for services that are not heavily used can reduce system load, when compared to running each daemon individually in stand-alone mode. @@ -155,133 +155,44 @@ auth, and daytime. - This section covers the basics in configuring - inetd through its command-line - options and its configuration file, - /etc/inetd.conf. - - - - Settings - - inetd is initialized through - the &man.rc.8; system. The inetd_enable - option is set to NO by default. It can be - enabled by placing: - - inetd_enable="YES" - - into /etc/rc.conf. - inetd will now start at boot time. - The command: - - &prompt.root; service inetd rcvar - - can be run to display the current effective - setting. - - Additionally, different command-line options can be passed - to inetd via the - inetd_flags option. - - - - Command-Line Options - - Like most server daemons, inetd - has a number of options that it can be passed in order to - modify its behaviour. Refer to &man.inetd.8; for - the full list of options. - - 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. - - 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 if - an excessive amount of connections are being established. - A full list of options can be found in - &man.inetd.8;. - - - - -c maximum - - - Specify the default maximum number of simultaneous - invocations of each service; the default is unlimited. - May be overridden on a per-service basis with the - parameter. - - - - - -C rate - - - 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 - - parameter. - - - - - -R rate - - - Specify the maximum number of times a service can be - invoked in one minute; the default is 256. A rate of 0 - allows an unlimited number of invocations. - - - - - -s maximum - - - 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. - - - + This section covers the basics of configuring + inetd. - - <filename>inetd.conf</filename> + Configuration File Configuration of inetd is - done by editing /etc/inetd.conf. + done by editing /etc/inetd.conf. Each line of this configuration file represents an application + which can be started by inetd. By + default, every line starts with a comment + (#), meaning that inetd + is not listening for any applications. To configure + inetd to listen for an application's + connections, remove the # at the beginning of + the line for that application. - When a modification is made to - /etc/inetd.conf, - inetd can be forced to re-read its - configuration file by running the command: + After saving your edits, configure inetd + to start at system boot by editing /etc/rc.conf: - - Reloading the <application>inetd</application> - Configuration File + inetd_enable="YES" - &prompt.root; service inetd reload - + To start + inetd now, so that it listens for + the service you configured, type: + + &prompt.root; service inetd start + + Typically, the default entry for an application does not + need to be edited beyond removing the #. + In some situations, it may be appropriate to edit the default + entry. + + As an example, this is the default entry for &man.ftpd.8; using IPv4: + + ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l - Each line of the configuration file specifies an - individual daemon. Comments in the file are preceded by a - #. The format of each entry in - /etc/inetd.conf is as follows: + The seven columns in an entry are as follows: service-name socket-type @@ -291,10 +202,7 @@ user[:group][/login-class] server-program server-program-arguments - An example entry for the &man.ftpd.8; daemon using IPv4 - might read: - - ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l + where: @@ -489,6 +397,95 @@ server-program-arguments + + When a modification is made to + /etc/inetd.conf, + inetd can be forced to re-read its + configuration file by running the command: + + + Reloading the <application>inetd</application> + Configuration File + + &prompt.root; service inetd reload + + + + + Command-Line Options + + Additionally, different command-line options can be passed + to inetd via the + inetd_flags option. + Like most server daemons, inetd + has a number of options that it can be passed in order to + modify its behaviour. Refer to &man.inetd.8; for + the full list of options. + + 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. + + 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 if + an excessive amount of connections are being established. + A full list of options can be found in + &man.inetd.8;. + + + + -c maximum + + + Specify the default maximum number of simultaneous + invocations of each service; the default is unlimited. + May be overridden on a per-service basis with the + parameter. + + + + + -C rate + + + 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 + + parameter. + + + + + -R rate + + + Specify the maximum number of times a service can be + invoked in one minute; the default is 256. A rate of 0 + allows an unlimited number of invocations. + + + + + -s maximum + + + 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. + + + From owner-svn-doc-all@FreeBSD.ORG Fri Jan 31 17:03:24 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A21D9AF2; Fri, 31 Jan 2014 17:03:24 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8CA3013B6; Fri, 31 Jan 2014 17:03:24 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VH3OCC006955; Fri, 31 Jan 2014 17:03:24 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VH3OG4006953; Fri, 31 Jan 2014 17:03:24 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401311703.s0VH3OG4006953@svn.freebsd.org> From: Dru Lavigne Date: Fri, 31 Jan 2014 17:03:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43707 - in head/en_US.ISO8859-1/books/handbook: install network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 17:03:24 -0000 Author: dru Date: Fri Jan 31 17:03:23 2014 New Revision: 43707 URL: http://svnweb.freebsd.org/changeset/doc/43707 Log: Finish up this section. Some additional shuffling to improve the flow. Fix reference in another chapter. This section should be much clearer now. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/install/chapter.xml Fri Jan 31 15:30:54 2014 (r43706) +++ head/en_US.ISO8859-1/books/handbook/install/chapter.xml Fri Jan 31 17:03:23 2014 (r43707) @@ -2604,7 +2604,7 @@ Do you want to configure inetd and the n will not be enabled. These services can be enabled after installation by editing /etc/inetd.conf with a text editor. - See for more information. + See for more information. Otherwise, select &gui.yes; to configure these services during install. An additional Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 15:30:54 2014 (r43706) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 17:03:23 2014 (r43707) @@ -113,6 +113,9 @@ + The <application>inetd</application> + Super-Server + - - The <application>inetd</application> - Super-Server - - - + The &man.inetd.8; daemon is sometimes referred to as a Super-Server because it manages connections for many services. Instead of starting multiple @@ -151,13 +149,15 @@ Primarily, inetd is used to spawn other daemons, but several trivial protocols are handled - directly, such as chargen, - auth, and + internally, such as chargen, + auth, + time, + echo, + discard, and daytime. This section covers the basics of configuring inetd. - Configuration File @@ -182,13 +182,24 @@ the service you configured, type: &prompt.root; service inetd start - + + Once inetd is started, it needs + to be notified whenever a modification is made to + /etc/inetd.conf: + + + Reloading the <application>inetd</application> + Configuration File + + &prompt.root; service inetd reload + + Typically, the default entry for an application does not need to be edited beyond removing the #. In some situations, it may be appropriate to edit the default entry. - As an example, this is the default entry for &man.ftpd.8; using IPv4: + As an example, this is the default entry for &man.ftpd.8; over IPv4: ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l @@ -209,13 +220,13 @@ server-program-argumentsservice-name - This is the service name of the particular daemon. + The service name of the daemon to start. It must correspond to a service listed in /etc/services. This determines - which port inetd must listen - to. If a new service is being created, it must be - placed in /etc/services - first. + which port inetd listens on + for incoming connections to that service. + When using a custom service, it must first be + added to /etc/services. @@ -225,10 +236,10 @@ server-program-arguments Either stream, dgram, raw, or - seqpacket. stream - must be used for connection-based, TCP daemons, while - dgram is used for daemons utilizing - the UDP transport protocol. + seqpacket. Use stream + for TCP connections and + dgram for + UDP services. @@ -236,25 +247,25 @@ server-program-argumentsprotocol - One of the following: + Use one of the following protocol names: - Protocol + Protocol Name Explanation - tcp, tcp4 + tcp or tcp4 TCP IPv4 - udp, udp4 + udp or udp4 UDP IPv4 @@ -270,12 +281,12 @@ server-program-arguments tcp46 - Both TCP IPv4 and v6 + Both TCP IPv4 and IPv6 udp46 - Both UDP IPv4 and v6 + Both UDP IPv4 and IPv6 @@ -287,11 +298,17 @@ server-program-arguments{wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]] - indicates whether the - daemon invoked from inetd is - able to handle its own socket or not. + In this field, or + must be specified. + , + and + are optional. + + indicates whether or not the + service is + able to handle its own socket. socket types must use the - option, while stream socket + option while daemons, which are usually multi-threaded, should use . usually hands off multiple sockets to a single daemon, while @@ -299,60 +316,32 @@ server-program-arguments The maximum number of child daemons - inetd may spawn can be set - using the option. If a limit - of ten instances of a particular daemon is needed, a - /10 would be placed after + inetd may spawn is set by + . For example, to limit + ten instances of the daemon, place a + /10 after . Specifying /0 allows an unlimited number of - children + 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 + IP address per minute. Once the limit + is reached, further connections from this IP address + will be dropped until the end of the minute. For example, a value + of /10 would limit any particular IP + address to ten + connection attempts per minute. + limits the number of child processes 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. + any moment. These options can limit + excessive resource + consumption and help to prevent Denial of Service attacks. - In this field, either of or - is mandatory. - , - and - are optional. + An example can be seen in the default + settings for &man.fingerd.8;: - A stream-type multi-threaded daemon without any - , - or - limits would simply - be: nowait. - - The same daemon with a maximum limit of ten daemons - would read: nowait/10. - - The same setup with a limit of twenty connections - per IP address per minute and a - maximum total limit of ten child daemons would read: - nowait/10/20. - - These options are utilized by the default - settings of the &man.fingerd.8; daemon, - as seen here: - - finger stream tcp nowait/3/10 nobody /usr/libexec/fingerd fingerd -s - - Finally, an example of this field with a maximum of - 100 children in total, with a maximum of 5 for any one - IP address would read: - nowait/100/0/5. + finger stream tcp nowait/3/10 nobody /usr/libexec/fingerd fingerd -k -s @@ -360,12 +349,11 @@ server-program-argumentsuser - 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. + The username the daemon + will run as. Daemons typically run as + root, + daemon, or + nobody. @@ -373,11 +361,10 @@ server-program-argumentsserver-program - The full path of the daemon to be executed when a - connection is received. If the daemon is a service + The full path to the daemon. + If the daemon is a service provided by inetd internally, - then should be - used. + use . @@ -385,58 +372,36 @@ server-program-argumentsserver-program-arguments - This works in conjunction with - by specifying the - arguments, starting with argv[0], + Used to + specify any command + arguments to be passed to the daemon on invocation. If - mydaemon -d is the command line, - mydaemon -d would be the value of - . Again, if the daemon is an internal service, use - here. + . - - When a modification is made to - /etc/inetd.conf, - inetd can be forced to re-read its - configuration file by running the command: - - - Reloading the <application>inetd</application> - Configuration File - - &prompt.root; service inetd reload - Command-Line Options - Additionally, different command-line options can be passed - to inetd via the - inetd_flags option. Like most server daemons, inetd - has a number of options that it can be passed in order to - modify its behaviour. Refer to &man.inetd.8; for - the full list of options. + has a number of options that can be used to + modify its behaviour. By default, + inetd is started with + -wW -C 60. These options enable TCP wrappers for + all services, including internal services, and prevent any + IP address from requesting any + service more than 60 times per minute. + + To change the default options which are passed to inetd, + add an entry for inetd_flags in + /etc/rc.conf. If + inetd is already running, restart + it with service inetd restart. - 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. - - 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 if - an excessive amount of connections are being established. - A full list of options can be found in - &man.inetd.8;. + The available rate limiting options are: @@ -444,9 +409,9 @@ server-program-arguments Specify the default maximum number of simultaneous - invocations of each service; the default is unlimited. - May be overridden on a per-service basis with the - parameter. + invocations of each service, where the default is unlimited. + May be overridden on a per-service basis by using + in /etc/inetd.conf. @@ -456,11 +421,10 @@ server-program-arguments 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 - - parameter. + IP address per minute. May be overridden on a per-service basis + by using + in + /etc/inetd.conf. @@ -469,8 +433,8 @@ server-program-arguments Specify the maximum number of times a service can be - invoked in one minute; the default is 256. A rate of 0 - allows an unlimited number of invocations. + invoked in one minute, where the default is 256. A rate of 0 + allows an unlimited number. @@ -480,63 +444,37 @@ server-program-arguments 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. + any one time, where the default is unlimited. May be + overridden on a per-service basis by using + in /etc/inetd.conf. + + Additional options are available. Refer to &man.inetd.8; for + the full list of options. - Security + Security Considerations - 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 - 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. An attacker - can send connections to a particular daemon, eventually - consuming available resources and resulting in a Denial of - Service (DoS). + Many of the daemons which can be managed by + inetd are not security-conscious. + Some daemons, such as + fingerd, can + provide information that may be useful to an + attacker. Only enable the services which are needed and + monitor the system for excessive connection attempts. max-connections-per-ip-per-minute, max-child and max-child-per-ip can be used to limit such attacks. - By default, TCP wrapping is turned on. Consult + By default, TCP wrappers is enabled. Consult &man.hosts.access.5; for more information on placing TCP restrictions on various inetd invoked daemons. - - - Miscellaneous - - daytime, - time, - echo, - discard, - chargen, and - auth are all internally provided - services of inetd. - - The auth service provides - identity network services, and is configurable to a certain - degree, whilst the others are simply on or off. - - Consult &man.inetd.8; for more in-depth - information. - From owner-svn-doc-all@FreeBSD.ORG Fri Jan 31 18:43:30 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2375AE1B; Fri, 31 Jan 2014 18:43:30 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0D45D1DFC; Fri, 31 Jan 2014 18:43:30 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VIhU9V046135; Fri, 31 Jan 2014 18:43:30 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VIhTJ9046134; Fri, 31 Jan 2014 18:43:29 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401311843.s0VIhTJ9046134@svn.freebsd.org> From: Dru Lavigne Date: Fri, 31 Jan 2014 18:43:29 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43708 - head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 18:43:30 -0000 Author: dru Date: Fri Jan 31 18:43:29 2014 New Revision: 43708 URL: http://svnweb.freebsd.org/changeset/doc/43708 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 17:03:23 2014 (r43707) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 18:43:29 2014 (r43708) @@ -113,9 +113,9 @@ - The <application>inetd</application> + <title>The <application>inetd</application> Super-Server - + - - The &man.inetd.8; daemon is sometimes referred to as a - Super-Server because it manages - connections for many services. Instead of starting multiple - applications, only the inetd service - needs to be started. When a connection is received - for a service that is managed by inetd, it determines which - program the connection is destined for, spawns a - process for that program, and delegates the program a socket. - Using inetd - for services that are not heavily used can reduce - 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 - internally, such as chargen, - auth, - time, - echo, - discard, and - daytime. - This section covers the basics of configuring - inetd. + The &man.inetd.8; daemon is sometimes referred to as a + Super-Server because it manages connections for many services. + Instead of starting multiple applications, only the + inetd service needs to be started. + When a connection is received for a service that is managed by + inetd, it determines which program + the connection is destined for, spawns a process for that + program, and delegates the program a socket. Using + inetd for services that are not + heavily used can reduce 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 + internally, such as chargen, + auth, + time, + echo, + discard, and + daytime. + + This section covers the basics of configuring + inetd. Configuration File Configuration of inetd is - done by editing /etc/inetd.conf. Each line of this configuration file represents an application + done by editing /etc/inetd.conf. Each + line of this configuration file represents an application which can be started by inetd. By default, every line starts with a comment - (#), meaning that inetd - is not listening for any applications. To configure - inetd to listen for an application's - connections, remove the # at the beginning of - the line for that application. - - After saving your edits, configure inetd - to start at system boot by editing /etc/rc.conf: + (#), meaning that + inetd is not listening for any + applications. To configure inetd + to listen for an application's connections, remove the + # at the beginning of the line for that + application. + + After saving your edits, configure + inetd to start at system boot by + editing /etc/rc.conf: inetd_enable="YES" - To start - inetd now, so that it listens for - the service you configured, type: + To start inetd now, so that it + listens for the service you configured, type: &prompt.root; service inetd start @@ -192,16 +193,17 @@ Configuration File &prompt.root; service inetd reload - + Typically, the default entry for an application does not - need to be edited beyond removing the #. + need to be edited beyond removing the #. In some situations, it may be appropriate to edit the default entry. - As an example, this is the default entry for &man.ftpd.8; over IPv4: + As an example, this is the default entry for &man.ftpd.8; + over IPv4: - ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l + ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l The seven columns in an entry are as follows: @@ -220,13 +222,13 @@ server-program-argumentsservice-name - The service name of the daemon to start. - It must correspond to a service listed in + The service name of the daemon to start. It must + correspond to a service listed in /etc/services. This determines which port inetd listens on - for incoming connections to that service. - When using a custom service, it must first be - added to /etc/services. + for incoming connections to that service. When using a + custom service, it must first be added to + /etc/services. @@ -236,8 +238,8 @@ server-program-arguments Either stream, dgram, raw, or - seqpacket. Use stream - for TCP connections and + seqpacket. Use + stream for TCP connections and dgram for UDP services. @@ -286,7 +288,8 @@ server-program-arguments udp46 - Both UDP IPv4 and IPv6 + Both UDP IPv4 and + IPv6 @@ -304,42 +307,40 @@ server-program-argumentsmax-connections-per-ip-per-minute and are optional. - indicates whether or not the - service is - able to handle its own socket. + indicates whether or + not the service is able to handle its own socket. socket types must use the - option while - daemons, which are usually multi-threaded, should use - . usually - hands off multiple sockets to a single daemon, while - spawns a child daemon for each - new socket. + option while + daemons, which are usually + multi-threaded, should use . + usually hands off multiple sockets + to a single daemon, while spawns + a child daemon for each new socket. The maximum number of child daemons inetd may spawn is set by - . For example, to limit - ten instances of the daemon, place a - /10 after - . Specifying + . For example, to limit ten + instances of the daemon, place a /10 + after . Specifying /0 allows an unlimited number of children. limits the number of connections from any particular - IP address per minute. Once the limit - is reached, further connections from this IP address - will be dropped until the end of the minute. For example, a value - of /10 would limit any particular IP - address to ten - connection attempts per minute. - limits the number of child processes that can be started on - behalf on any single IP address at - any moment. These options can limit - excessive resource - consumption and help to prevent Denial of Service attacks. + IP address per minute. Once the + limit is reached, further connections from this IP + address will be dropped until the end of the minute. + For example, a value of /10 would + limit any particular IP address to + ten connection attempts per minute. + limits the number of + child processes that can be started on behalf on any + single IP address at any moment. + These options can limit excessive resource consumption + and help to prevent Denial of Service attacks. - An example can be seen in the default - settings for &man.fingerd.8;: + An example can be seen in the default settings for + &man.fingerd.8;: finger stream tcp nowait/3/10 nobody /usr/libexec/fingerd fingerd -k -s @@ -361,10 +362,9 @@ server-program-argumentsserver-program - The full path to the daemon. - If the daemon is a service - provided by inetd internally, - use . + The full path to the daemon. If the daemon is a + service provided by inetd + internally, use . @@ -372,11 +372,9 @@ server-program-argumentsserver-program-arguments - Used to - specify any command - arguments to be - passed to the daemon on invocation. If - the daemon is an internal service, use + Used to specify any command arguments to be passed + to the daemon on invocation. If the daemon is an + internal service, use . @@ -387,17 +385,17 @@ server-program-argumentsCommand-Line Options Like most server daemons, inetd - has a number of options that can be used to - modify its behaviour. By default, - inetd is started with - -wW -C 60. These options enable TCP wrappers for - all services, including internal services, and prevent any - IP address from requesting any - service more than 60 times per minute. - - To change the default options which are passed to inetd, - add an entry for inetd_flags in - /etc/rc.conf. If + has a number of options that can be used to modify its + behaviour. By default, inetd is + started with -wW -C 60. These options + enable TCP wrappers for all services, including internal + services, and prevent any IP address from + requesting any service more than 60 times per minute. + + To change the default options which are passed to + inetd, add an entry for + inetd_flags in + /etc/rc.conf. If inetd is already running, restart it with service inetd restart. @@ -409,9 +407,10 @@ server-program-arguments Specify the default maximum number of simultaneous - invocations of each service, where the default is unlimited. - May be overridden on a per-service basis by using - in /etc/inetd.conf. + invocations of each service, where the default is + unlimited. May be overridden on a per-service basis by + using in + /etc/inetd.conf. @@ -421,8 +420,8 @@ server-program-arguments Specify the default maximum number of times a service can be invoked from a single - IP address per minute. May be overridden on a per-service basis - by using + IP address per minute. May be + overridden on a per-service basis by using in /etc/inetd.conf. @@ -433,7 +432,8 @@ server-program-arguments Specify the maximum number of times a service can be - invoked in one minute, where the default is 256. A rate of 0 + invoked in one minute, where the default is + 256. A rate of 0 allows an unlimited number. @@ -446,13 +446,14 @@ server-program-argumentsIP address at any one time, where the default is unlimited. May be overridden on a per-service basis by using - in /etc/inetd.conf. + in + /etc/inetd.conf. - Additional options are available. Refer to &man.inetd.8; for - the full list of options. + Additional options are available. Refer to &man.inetd.8; + for the full list of options. @@ -460,19 +461,18 @@ server-program-argumentsMany of the daemons which can be managed by inetd are not security-conscious. - Some daemons, such as - fingerd, can - provide information that may be useful to an - attacker. Only enable the services which are needed and - monitor the system for excessive connection attempts. + Some daemons, such as fingerd, can + provide information that may be useful to an attacker. Only + enable the services which are needed and monitor the system + for excessive connection attempts. max-connections-per-ip-per-minute, max-child and max-child-per-ip can be used to limit such attacks. By default, TCP wrappers is enabled. Consult - &man.hosts.access.5; for more information on - placing TCP restrictions on various + &man.hosts.access.5; for more information on placing TCP + restrictions on various inetd invoked daemons. @@ -657,28 +657,28 @@ mountd_flags="-r" read-only, preventing clients from making any changes to those exported file systems. - The next example exports - /home to three clients - by IP address. This can be useful for - networks without DNS. Optionally, - /etc/hosts could be configured for - internal hostnames; please review &man.hosts.5; for more - information. The -alldirs flag allows - subdirectories to be mount points. In other words, it will - not mount the subdirectories but permit the client to mount - only the directories that are required or needed. + The next example exports /home to + three clients by IP address. This can be + useful for networks without DNS. + Optionally, /etc/hosts could be + configured for internal hostnames; please review &man.hosts.5; + for more information. The -alldirs flag + allows subdirectories to be mount points. In other words, it + will not mount the subdirectories but permit the client to + mount only the directories that are required or needed. /home -alldirs 10.0.0.2 10.0.0.3 10.0.0.4 - This next line exports - /a so that two clients - from different domains may access the file system. The - flag allows the - root user on the remote system to write - data on the exported file system as root. - If the -maproot=root flag is not specified, - the client's root user will be mapped to - the server's nobody account and will be + This next line exports /a so that two + clients from different domains may access the file system. + The flag allows the + root user on the + remote system to write data on the exported file system as + root. If the + -maproot=root flag is not specified, the + client's root user + will be mapped to the server's nobody account and will be subject to the access limitations defined for user, nobody. @@ -692,16 +692,16 @@ mountd_flags="-r" the export information for one file system to one or more clients. A remote host can only be specified once per file system. For example, assume that - /usr is a single file - system. This entry, in /etc/exports, - would be invalid: + /usr is a single file system. This + entry, in /etc/exports, would be + invalid: # Invalid when /usr is one file system /usr/src client /usr/ports client - The /usr file - system has two lines specifying exports to the same host, + The /usr file system has two lines + specifying exports to the same host, client. The correct format for this situation is: @@ -713,9 +713,8 @@ mountd_flags="-r" system. The following is an example of a valid export list, where - /usr and - /exports are local - file systems: + /usr and /exports + are local file systems: # Export src and ports to client01 and client02, but only # client01 has root privileges on it @@ -739,7 +738,8 @@ mountd_flags="-r" On a new server being configured with NFS services, the server can be started by - running this command as root: + running this command as root: &prompt.root; service nfsd start @@ -750,9 +750,10 @@ mountd_flags="-r" The client now has everything it needs to mount a remote file system. In these examples, the server's name is server and the client's name is - client. For testing or to temporarily mount - a remote file system, execute mount - as root on + client. For testing or to + temporarily mount a remote file system, execute + mount as root on client: @@ -762,16 +763,16 @@ mountd_flags="-r" &prompt.root; mount server:/home /mnt This mounts the server: - /home file system to - the client: - /mnt mount point. The - files and directories in the server - /home file system will - now be available on client, in the + /home file system to the + client: + /mnt mount point. The files and + directories in the server + /home file system will now be available + on client, in the /mnt directory. - To mount a remote file system each time the client - boots, add it to /etc/fstab: + To mount a remote file system each time the client boots, + add it to /etc/fstab: server:/home /mnt nfs rw 0 0 @@ -786,8 +787,8 @@ mountd_flags="-r" require file locking to operate correctly. In the case of NFS, rpc.lockd can be used for file locking. To enable it, add this line to - /etc/rc.conf on both client - and server: + /etc/rc.conf on both client and + server: rpc_lockd_enable="YES" rpc_statd_enable="YES" @@ -796,8 +797,8 @@ rpc_statd_enable="YES" NFS client and server are already configured. - Start the application, as root, - with: + Start the application, as root, with: &prompt.root; service lockd start &prompt.root; service statd start @@ -805,8 +806,7 @@ rpc_statd_enable="YES" If locking is not required on the server, the NFS client can be configured to lock locally by passing to &man.mount.nfs.8;. - Refer to &man.mount.nfs.8; for further - details. + Refer to &man.mount.nfs.8; for further details. @@ -836,10 +836,11 @@ rpc_statd_enable="YES" - Several clients may need access to the /usr/ports/distfiles - directory. Sharing that directory allows for quick access - to the source files without having to download them to - each client. + Several clients may need access to the + /usr/ports/distfiles directory. + Sharing that directory allows for quick access to the + source files without having to download them to each + client. @@ -886,14 +887,15 @@ rpc_statd_enable="YES" /net directories. When a file is accessed within one of these directories, amd looks up the corresponding - remote mount and automatically mounts it. /net is used to mount an - exported file system from an IP address, - while /host is used to - mount an export from a remote hostname. + remote mount and automatically mounts it. + /net is used to mount an exported file + system from an IP address, while + /host is used to mount an export from a + remote hostname. For instance, an attempt to access a file within - /host/foobar/usr would - tell amd to mount the + /host/foobar/usr would tell + amd to mount the /usr export on the host foobar. @@ -901,10 +903,9 @@ rpc_statd_enable="YES" Mounting an Export with <application>amd</application> - showmount -e shows the - exported file systems that can be mounted from - the NFS server, - foobar: + showmount -e shows the exported file + systems that can be mounted from the NFS + server, foobar: &prompt.user; showmount -e foobar Exports list on foobar: @@ -914,13 +915,13 @@ Exports list on foobar: The output from showmount shows - /usr as an export. - When changing directories to - /host/foobar/usr, + /usr as an export. When changing + directories to /host/foobar/usr, amd intercepts the request and - attempts to resolve the hostname foobar. If - successful, amd automatically - mounts the desired export. + attempts to resolve the hostname + foobar. If successful, + amd automatically mounts the + desired export. amd is enabled by placing this line in /etc/rc.conf: @@ -942,8 +943,8 @@ Exports list on foobar: /etc/amd.conf defines some of the more advanced features of amd. - Consult &man.amd.8; and &man.amd.conf.5; - for more information. + Consult &man.amd.8; and &man.amd.conf.5; for more + information. @@ -1193,32 +1194,37 @@ Exports list on foobar: ellington - 10.0.0.2 + 10.0.0.2 NIS master coltrane - 10.0.0.3 + 10.0.0.3 NIS slave basie - 10.0.0.4 + 10.0.0.4 Faculty workstation bird - 10.0.0.5 + 10.0.0.5 Client machine cli[1-11] - 10.0.0.[6-17] + 10.0.0.[6-17] Other client machines @@ -1376,8 +1382,8 @@ nis_client_flags="-S NIS do NIS maps - NIS maps - are generated from the configuration files in /etc on the + NIS maps are generated from the + configuration files in /etc on the NIS master, with one exception: /etc/master.passwd. This is to prevent the propagation of passwords to all the servers in @@ -1392,8 +1398,8 @@ nis_client_flags="-S NIS do It is advisable to remove all entries for system accounts as well as any user accounts that do not need to be propagated to the NIS clients, such - as the root and any other - administrative accounts. + as the root and + any other administrative accounts. Ensure that the /var/yp/master.passwd is neither @@ -1603,8 +1609,7 @@ Remember to update map ypservers on elli Edit /etc/rc.conf and add the following lines in order to set the NIS domain name and start - &man.ypbind.8; during network - startup: + &man.ypbind.8; during network startup: nisdomainname="test-domain" nis_client_enable="YES" @@ -1618,7 +1623,8 @@ nis_client_enable="YES" /etc/master.passwd. When removing the accounts, keep in mind that at least one local account should remain and this account should be - a member of wheel. If there is + a member of wheel. If there is a problem with NIS, this local account can be used to log in remotely, become the superuser, and fix the problem. Before saving the @@ -1633,8 +1639,8 @@ nis_client_enable="YES" account on the client. There are many ways to configure the NIS client by modifying this line. One method is described in - . For - more detailed reading, refer to the book + . For more + detailed reading, refer to the book Managing NFS and NIS, published by O'Reilly Media. @@ -1728,27 +1734,27 @@ nis_client_enable="YES" Barring Some Users - In this example, the basie system - is a faculty workstation within the NIS - domain. The passwd map on the master + In this example, the basie + system is a faculty workstation within the + NIS domain. The + passwd map on the master NIS server contains accounts for both faculty and students. This section demonstrates how to allow faculty logins on this system while refusing student logins. - To prevent specified users from logging on to a - system, even if they are present in the + To prevent specified users from logging on to a system, + even if they are present in the NIS database, use vipw - to add - -username with - the correct number of colons towards the end of + to add -username with the correct number + of colons towards the end of /etc/master.passwd on the client, where username is the username of a user to bar from logging in. The line with the blocked user must be before the + line that allows NIS users. In this example, - bill is barred from logging on to - basie: + bill is barred + from logging on to basie: basie&prompt.root; cat /etc/master.passwd root:[password]:0:0::0:0:The super-user:/root:/bin/csh @@ -1824,21 +1830,24 @@ basie&prompt.root; - charlie, - delta + charlie, delta IT department apprentices echo, foxtrott, - golf, ... + golf, + ... employees able, - baker, ... + baker, + ... interns @@ -1861,7 +1870,8 @@ basie&prompt.root; war, - death, famine, + death, + famine, pollution Only IT employees are allowed to log onto these servers. @@ -1869,16 +1879,21 @@ basie&prompt.root; - pride, greed, - envy, wrath, - lust, sloth + pride, + greed, + envy, + wrath, + lust, + sloth All members of the IT department are allowed to login onto these servers. - one, two, - three, four, + one, + two, + three, + four, ... Ordinary workstations used by employees. @@ -2567,8 +2582,11 @@ result: 0 Success by the client to obtain the addressing information. &os; does not install a DHCP server, but several servers are available in the &os; Ports Collection. The - DHCP protocol is fully described in RFC 2131. - Informational resources are also available at isc.org/downloads/dhcp/. + DHCP protocol is fully described in RFC + 2131. + Informational resources are also available at isc.org/downloads/dhcp/. This section describes how to use the built-in DHCP client. It then describes how to @@ -2706,7 +2724,8 @@ result: 0 Success to act as a DHCP server using the Internet Systems Consortium (ISC) implementation of the DHCP server. This implementation and - its documentation can be installed using the net/isc-dhcp42-server package or + its documentation can be installed using the + net/isc-dhcp42-server package or port. @@ -2719,8 +2738,9 @@ result: 0 Success installation - The installation of net/isc-dhcp42-server installs a - sample configuration file. Copy + The installation of + net/isc-dhcp42-server installs a sample + configuration file. Copy /usr/local/etc/dhcpd.conf.example to /usr/local/etc/dhcpd.conf and make any edits to this new file. @@ -2898,9 +2918,10 @@ dhcpd_ifaces="dc0" one DHCP server forwards a request from a client to another DHCP server on a separate network. If this functionality is - required, install the net/isc-dhcp42-relay - package or port. The installation includes dhcrelay(8) - which provides more detail. + required, install the + net/isc-dhcp42-relay package or port. + The installation includes dhcrelay(8) which provides + more detail. @@ -2939,7 +2960,8 @@ dhcpd_ifaces="dc0" is the most common implementation of the DNS protocol. The &os; version provides enhanced security features, a new file system layout, and automated &man.chroot.8; - configuration. BIND is maintained by the isc.org. It is not + configuration. BIND is maintained by the isc.org. It is not necessary to run a name server to perform DNS lookups on a system. @@ -3028,8 +3050,8 @@ dhcpd_ifaces="dc0" - . is how the root zone is usually - referred to in documentation. + . is how the root zone is + usually referred to in documentation. @@ -3038,24 +3060,28 @@ dhcpd_ifaces="dc0" - example.org. is a + example.org. is a zone under the org. TLD. - 1.168.192.in-addr.arpa is a zone - referencing all IP addresses which fall - under the 192.168.1.* + 1.168.192.in-addr.arpa is a + zone referencing all IP addresses which + fall under the 192.168.1.* IP address space. As one can see, the more specific part of a hostname - appears to its left. For example, example.org. is more specific than - org., as org. is more specific - than the root zone. The layout of each part of a hostname is - much like a file system: the /dev directory falls within the + appears to its left. For example, example.org. is more + specific than org., as + org. is more specific than the root + zone. The layout of each part of a hostname is much like a file + system: the /dev directory falls within the root, and so on. @@ -3074,8 +3100,8 @@ dhcpd_ifaces="dc0" - A domain, such as - example.org, is + A domain, such as example.org, is registered and IP addresses need to be assigned to hostnames under it. @@ -3102,10 +3128,10 @@ dhcpd_ifaces="dc0" - When one queries for - www.FreeBSD.org, the resolver - usually queries the uplink ISP's name - server, and retrieves the reply. With a local, caching + When one queries for www.FreeBSD.org, the + resolver usually queries the uplink ISP's + name server, and retrieves the reply. With a local, caching DNS server, the query only has to be made once to the outside world by the caching DNS server. Additional queries will not @@ -3286,8 +3312,8 @@ options { name server, enabling this may be worthwhile. - 127.0.0.1 will - not work here. Change this + 127.0.0.1 + will not work here. Change this IP address to a name server at the uplink. @@ -3538,8 +3564,8 @@ zone "1.168.192.in-addr.arpa" { to named.conf. For example, the simplest zone entry for - example.org can look - like: + example.org + can look like: zone "example.org" { type master; @@ -3573,8 +3599,8 @@ zone "1.168.192.in-addr.arpa" { zone files - An example master zone file for - example.org (existing + An example master zone file for example.org (existing within /etc/namedb/master/example.org) is as follows: @@ -3677,7 +3703,8 @@ www IN CNAME example. - example.org. + example.org. the domain name, also the origin for this @@ -3686,7 +3713,8 @@ www IN CNAME example. - ns1.example.org. + Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A181A899; Fri, 31 Jan 2014 21:35:12 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 71D441B6A; Fri, 31 Jan 2014 21:35:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VLZCg4014163; Fri, 31 Jan 2014 21:35:12 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VLZCfJ014161; Fri, 31 Jan 2014 21:35:12 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401312135.s0VLZCfJ014161@svn.freebsd.org> From: Dru Lavigne Date: Fri, 31 Jan 2014 21:35:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43710 - head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 21:35:12 -0000 Author: dru Date: Fri Jan 31 21:35:11 2014 New Revision: 43710 URL: http://svnweb.freebsd.org/changeset/doc/43710 Log: Editorial pass through the NTP chapter. Headings and content shuffled about to improve flow. Text clarified and logic should be much clearer now. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 20:55:48 2014 (r43709) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 21:35:11 2014 (r43710) @@ -5227,208 +5227,158 @@ Starting smbd. --> Clock Synchronization with NTP - NTP - - Over time, a computer's clock is prone to drift. The - Network Time Protocol (NTP) is one way to ensure the clock - stays accurate. - - Many Internet services rely on, or greatly benefit from, - computers' clocks being accurate. For example, a web server - may receive requests to send a file if it has been modified - since a certain time. In a local area network environment, it - is essential that computers sharing files from the same file - server have synchronized clocks so that file timestamps stay - consistent. Services such as &man.cron.8; also rely on an - accurate system clock to run commands at the specified - times. - NTP - ntpd + ntpd - &os; ships with the &man.ntpd.8; - NTP server - which can be used to query other - NTP servers to - set the clock on the machine or provide time services to - others. - - - Choosing Appropriate NTP Servers - - - NTP - choosing servers - - - In order to synchronize the clock, one or more - NTP servers - must be defined. The network administrator or ISP may have - set up an NTP server for this purpose—check their - documentation to see if this is the case. There is an Over time, a computer's clock is prone to drift. This is + problematic as many network services require the computers on a network + to share the same accurate time. Accurate time is also needed to ensure + that file timestamps stay + consistent. The + Network Time Protocol (NTP) is one way to provide clock + accuracy in a network. + + &os; includes &man.ntpd.8; + which can be configured to query other + NTP servers in order to + synchronize the clock on that machine or to provide time services to + other computers in the network. The servers which are queried + can be local to the network or provided by an ISP. + In addition, an online - list of publicly accessible NTP servers which may be - referenced to find an NTP server nearest to the system. Take - care to review the policy for any chosen servers, and ask for - permission if required. - - Choosing several unconnected NTP servers is a good idea in - case one of the servers being used becomes unreachable or - its clock is unreliable. &man.ntpd.8; uses the responses it - receives from other servers intelligently—it will favor - unreliable servers less than reliable ones. - + list of publicly accessible NTP servers + is available. When choosing a public NTP server, select + one that is geographically close and + review its usage policy. + + Choosing several NTP servers is recommended in + case one of the servers becomes unreachable or + its clock proves unreliable. As ntpd receives responses, + it favors + reliable servers over the less reliable ones. + + This section describes how to configure ntpd on &os;. Further documentation can be found in + /usr/share/doc/ntp/ in HTML + format. - Configuring The Machine + <acronym>NTP</acronym> Configuration - - NTP - configuration + NTP + ntp.conf + ntpdate - - Basic Configuration - - ntpdate - - To synchronize the clock only when the machine boots up, - use &man.ntpdate.8;. This may be appropriate for some - desktop machines which are frequently rebooted and only - require infrequent synchronization, but most machines should - run &man.ntpd.8;. - - Using &man.ntpdate.8; at boot time is also a good idea - for machines that run &man.ntpd.8;. The &man.ntpd.8; - program changes the clock gradually, whereas &man.ntpdate.8; + To only synchronize the clock when a system boots, + use &man.ntpdate.8;. This alone can be appropriate for + desktops which are frequently rebooted. However, + most systems should + run ntpdate at boot time as well as configure ntpd. + This is because ntpd + changes the clock gradually, whereas ntpdate sets the clock, no matter how great the difference between a machine's current clock setting and the correct time. - To enable &man.ntpdate.8; at boot time, add + To enable ntpdate at boot time, add ntpdate_enable="YES" to - /etc/rc.conf. Also specify all - synchronization servers and any flags to be passed to - &man.ntpdate.8; in ntpdate_flags. - - - - General Configuration + /etc/rc.conf. To also enable + ntpd, add the ntpd_enable="YES" + entry to /etc/rc.conf. Additional variables can be specified + in /etc/rc.conf. Refer to &man.rc.conf.5;, + &man.ntpdate.8;, and &man.ntpd.8; for details. + + Both applications + read /etc/ntp.conf to determine + which servers to query. Here is a simple example of an + /etc/ntp.conf: - - NTP - ntp.conf - - - NTP is configured by the - /etc/ntp.conf file in the format - described in &man.ntp.conf.5;. Here is a simple - example: + + Sample <filename>/etc/ntp.conf</filename> server ntplocal.example.com prefer server timeserver.example.org server ntp2a.example.net driftfile /var/db/ntp.drift + - The server option specifies which - servers are to be used, with one server listed on each line. - If a server is specified with the prefer - argument, as with - ntplocal.example.com, + The format of this file is + described in &man.ntp.conf.5;. The server option specifies which + servers to query, with one server listed on each line. + If a server entry includes prefer, that server is preferred over other servers. A response from a preferred server will be discarded if it differs - significantly from other servers' responses, otherwise it - will be used without any consideration to other responses. - The prefer argument is normally used for - NTP servers that are known to be highly accurate, such as + significantly from responses; otherwise it + will be used. + The prefer argument should only be used for + NTP servers that are known to be highly accurate, such as those with special time monitoring hardware. - The driftfile option specifies which + The driftfile entry specifies which file is used to store the system clock's frequency offset. - The &man.ntpd.8; program uses this to automatically + ntpd uses this to automatically compensate for the clock's natural drift, allowing it to maintain a reasonably correct setting even if it is cut off - from all external time sources for a period of time. - - The driftfile option specifies which - file is used to store information about previous responses - from the NTP servers being used. This file contains - internal information for NTP. It should not be modified by - any other process. - - - - Controlling Access to Your Server - - By default, the NTP server will be accessible to all - hosts on the Internet. The restrict - option in /etc/ntp.conf - controls which machines can access the server. - - To deny all machines from accessing the NTP + from all external time sources for a period of time. This + file also stores information about previous responses + from NTP servers. Since this file contains + internal information for NTP, it should not be modified. + + By default, an NTP server is accessible to any + network host. The restrict + option in /etc/ntp.conf can be used to + control which systems can access the server. For example, + to deny all machines from accessing the NTP server, add the following line to /etc/ntp.conf: restrict default ignore - This will also prevent access from the server to any - servers listed in the local configuration. If there is a - need to synchronise the NTP server with an external NTP + This will also prevent access from other NTP servers. + If there is a + need to synchronize with an external NTP server, allow only that specific server. Refer to &man.ntp.conf.5; for more information. To allow machines within the network to synchronize their clocks with the server, but ensure they are not - allowed to configure the server or used as peers to - synchronize against, add + allowed to configure the server or be used as peers to + synchronize against, instead use: restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap - instead, where - 192.168.1.0 is an - IP address on the network and + where + 192.168.1.0 is the + local network address and 255.255.255.0 is - the network's netmask. + the network's subnet mask. - The /etc/ntp.conf file can contain - multiple restrict options. For more - details, see the Access Control Support + Multiple restrict entries are supported. + For more + details, refer to the Access Control Support subsection of &man.ntp.conf.5;. - - - - Running the NTP Server - - To ensure the NTP server is started at boot time, add the - line ntpd_enable="YES" to - /etc/rc.conf. To pass - additional flags to &man.ntpd.8;, edit the - ntpd_flags parameter in - /etc/rc.conf. - - To start the server without rebooting the machine, run - ntpd being sure to specify any additional - parameters from ntpd_flags in - /etc/rc.conf. For example: + Once + ntpd_enable="YES" has been added to + /etc/rc.conf, ntpd + can be started now without rebooting the system by typing: - &prompt.root; ntpd -p /var/run/ntpd.pid + &prompt.root; service ntpd start - Using <application>ntpd</application> with a Temporary - Internet Connection + Using <acronym>NTP</acronym> with a <acronym>PPP</acronym> + Connection - The &man.ntpd.8; program does not need a permanent + ntpd does not need a permanent connection to the Internet to function properly. However, if - there is a temporary connection that is configured to dial out - on demand, it is a good idea to prevent NTP traffic from - triggering a dial out or keeping the connection alive. PPP - users can use the filter + a PPP connection is configured to dial out + on demand, NTP traffic should be prevented from + triggering a dial out or keeping the connection alive. This can be configured + with filter directives in /etc/ppp/ppp.conf. For example: @@ -5441,7 +5391,7 @@ driftfile /var/db/ntp.drift - For more details see the + For more details, refer to the PACKET FILTERING section in &man.ppp.8; and the examples in /usr/share/examples/ppp/. @@ -5452,14 +5402,6 @@ driftfile /var/db/ntp.drift - - - Further Information - - Documentation for the NTP server can be found in - /usr/share/doc/ntp/ in HTML - format. - From owner-svn-doc-all@FreeBSD.ORG Fri Jan 31 21:54:18 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E63FFCD3; Fri, 31 Jan 2014 21:54:18 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B83CB1DAF; Fri, 31 Jan 2014 21:54:18 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VLsIWV021561; Fri, 31 Jan 2014 21:54:18 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VLsI7D021560; Fri, 31 Jan 2014 21:54:18 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401312154.s0VLsI7D021560@svn.freebsd.org> From: Dru Lavigne Date: Fri, 31 Jan 2014 21:54:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43711 - head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 21:54:19 -0000 Author: dru Date: Fri Jan 31 21:54:18 2014 New Revision: 43711 URL: http://svnweb.freebsd.org/changeset/doc/43711 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 21:35:11 2014 (r43710) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 21:54:18 2014 (r43711) @@ -5228,39 +5228,38 @@ Starting smbd. Clock Synchronization with NTP NTP - ntpd + ntpd - Over time, a computer's clock is prone to drift. This is - problematic as many network services require the computers on a network - to share the same accurate time. Accurate time is also needed to ensure - that file timestamps stay - consistent. The - Network Time Protocol (NTP) is one way to provide clock - accuracy in a network. - - &os; includes &man.ntpd.8; - which can be configured to query other - NTP servers in order to - synchronize the clock on that machine or to provide time services to - other computers in the network. The servers which are queried - can be local to the network or provided by an ISP. - In addition, an online - list of publicly accessible NTP servers - is available. When choosing a public NTP server, select - one that is geographically close and - review its usage policy. - - Choosing several NTP servers is recommended in - case one of the servers becomes unreachable or - its clock proves unreliable. As ntpd receives responses, - it favors - reliable servers over the less reliable ones. - - This section describes how to configure ntpd on &os;. Further documentation can be found in - /usr/share/doc/ntp/ in HTML - format. + Over time, a computer's clock is prone to drift. This is + problematic as many network services require the computers on a + network to share the same accurate time. Accurate time is also + needed to ensure that file timestamps stay consistent. The + Network Time Protocol (NTP) is one way to + provide clock accuracy in a network. + + &os; includes &man.ntpd.8; which can be configured to query + other NTP servers in order to synchronize the + clock on that machine or to provide time services to other + computers in the network. The servers which are queried can be + local to the network or provided by an ISP. + In addition, an online + list of publicly accessible NTP + servers is available. When choosing a public + NTP server, select one that is geographically + close and review its usage policy. + + Choosing several NTP servers is + recommended in case one of the servers becomes unreachable or + its clock proves unreliable. As ntpd + receives responses, it favors reliable servers over the less + reliable ones. + + This section describes how to configure + ntpd on &os;. Further documentation + can be found in /usr/share/doc/ntp/ in HTML + format. <acronym>NTP</acronym> Configuration @@ -5270,115 +5269,117 @@ Starting smbd. ntpdate - To only synchronize the clock when a system boots, - use &man.ntpdate.8;. This alone can be appropriate for - desktops which are frequently rebooted. However, - most systems should - run ntpdate at boot time as well as configure ntpd. - This is because ntpd - changes the clock gradually, whereas ntpdate - sets the clock, no matter how great the difference between a - machine's current clock setting and the correct time. - - To enable ntpdate at boot time, add - ntpdate_enable="YES" to - /etc/rc.conf. To also enable - ntpd, add the ntpd_enable="YES" - entry to /etc/rc.conf. Additional variables can be specified - in /etc/rc.conf. Refer to &man.rc.conf.5;, - &man.ntpdate.8;, and &man.ntpd.8; for details. - - Both applications - read /etc/ntp.conf to determine - which servers to query. Here is a simple example of an - /etc/ntp.conf: + To only synchronize the clock when a system boots, use + &man.ntpdate.8;. This alone can be appropriate for desktops + which are frequently rebooted. However, most systems should + run ntpdate at boot time as well as + configure ntpd. This is because + ntpd changes the clock gradually, + whereas ntpdate sets the clock, no + matter how great the difference between a machine's current + clock setting and the correct time. + + To enable ntpdate at boot time, + add ntpdate_enable="YES" to + /etc/rc.conf. To also enable + ntpd, add the + ntpd_enable="YES" entry to + /etc/rc.conf. Additional variables can + be specified in /etc/rc.conf. Refer to + &man.rc.conf.5;, &man.ntpdate.8;, and &man.ntpd.8; for + details. + + Both applications read /etc/ntp.conf + to determine which servers to query. Here is a simple example + of an /etc/ntp.conf: - - Sample <filename>/etc/ntp.conf</filename> + + Sample <filename>/etc/ntp.conf</filename> server ntplocal.example.com prefer server timeserver.example.org server ntp2a.example.net driftfile /var/db/ntp.drift - + - The format of this file is - described in &man.ntp.conf.5;. The server option specifies which - servers to query, with one server listed on each line. - If a server entry includes prefer, - that server is preferred over other servers. A response - from a preferred server will be discarded if it differs - significantly from responses; otherwise it - will be used. - The prefer argument should only be used for - NTP servers that are known to be highly accurate, such as - those with special time monitoring hardware. - - The driftfile entry specifies which - file is used to store the system clock's frequency offset. - ntpd uses this to automatically - compensate for the clock's natural drift, allowing it to - maintain a reasonably correct setting even if it is cut off - from all external time sources for a period of time. This - file also stores information about previous responses - from NTP servers. Since this file contains - internal information for NTP, it should not be modified. - - By default, an NTP server is accessible to any - network host. The restrict - option in /etc/ntp.conf can be used to - control which systems can access the server. For example, - to deny all machines from accessing the NTP - server, add the following line to - /etc/ntp.conf: + The format of this file is described in &man.ntp.conf.5;. + The server option specifies which servers + to query, with one server listed on each line. If a server + entry includes prefer, that server is + preferred over other servers. A response from a preferred + server will be discarded if it differs significantly from + responses; otherwise it will be used. The + prefer argument should only be used for + NTP servers that are known to be highly + accurate, such as those with special time monitoring + hardware. + + The driftfile entry specifies which + file is used to store the system clock's frequency offset. + ntpd uses this to automatically + compensate for the clock's natural drift, allowing it to + maintain a reasonably correct setting even if it is cut off + from all external time sources for a period of time. This + file also stores information about previous responses + from NTP servers. Since this file contains + internal information for NTP, it should not + be modified. + + By default, an NTP server is accessible + to any network host. The restrict option + in /etc/ntp.conf can be used to control + which systems can access the server. For example, to deny all + machines from accessing the NTP server, add + the following line to + /etc/ntp.conf: - restrict default ignore + restrict default ignore - This will also prevent access from other NTP servers. - If there is a - need to synchronize with an external NTP + This will also prevent access from other + NTP servers. If there is a need to + synchronize with an external NTP server, allow only that specific server. Refer to &man.ntp.conf.5; for more information. - To allow machines within the network to synchronize - their clocks with the server, but ensure they are not - allowed to configure the server or be used as peers to - synchronize against, instead use: - - restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap - - where - 192.168.1.0 is the - local network address and - 255.255.255.0 is - the network's subnet mask. - - Multiple restrict entries are supported. - For more - details, refer to the Access Control Support - subsection of &man.ntp.conf.5;. - - Once - ntpd_enable="YES" has been added to - /etc/rc.conf, ntpd - can be started now without rebooting the system by typing: + To allow machines within the network to synchronize their + clocks with the server, but ensure they are not allowed to + configure the server or be used as peers to synchronize + against, instead use: + + restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap + + where 192.168.1.0 is the local + network address and 255.255.255.0 is the network's + subnet mask. + + Multiple restrict entries are + supported. For more details, refer to the Access + Control Support subsection of + &man.ntp.conf.5;. + + Once ntpd_enable="YES" has been added + to /etc/rc.conf, + ntpd can be started now without + rebooting the system by typing: &prompt.root; service ntpd start - Using <acronym>NTP</acronym> with a <acronym>PPP</acronym> - Connection + Using <acronym>NTP</acronym> with a + <acronym>PPP</acronym> Connection ntpd does not need a permanent connection to the Internet to function properly. However, if a PPP connection is configured to dial out - on demand, NTP traffic should be prevented from - triggering a dial out or keeping the connection alive. This can be configured - with filter + on demand, NTP traffic should be prevented + from triggering a dial out or keeping the connection alive. + This can be configured with filter directives in /etc/ppp/ppp.conf. For example: @@ -5398,8 +5399,8 @@ driftfile /var/db/ntp.drift Some Internet access providers block low-numbered ports, - preventing NTP from functioning since replies never - reach the machine. + preventing NTP from functioning since replies never reach + the machine. From owner-svn-doc-all@FreeBSD.ORG Fri Jan 31 23:25:43 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3353E17C; Fri, 31 Jan 2014 23:25:43 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1FA6F1454; Fri, 31 Jan 2014 23:25:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VNPgX7057489; Fri, 31 Jan 2014 23:25:42 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VNPgWh057488; Fri, 31 Jan 2014 23:25:42 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401312325.s0VNPgWh057488@svn.freebsd.org> From: Warren Block Date: Fri, 31 Jan 2014 23:25:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43713 - head/en_US.ISO8859-1/books/fdp-primer/overview X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 23:25:43 -0000 Author: wblock Date: Fri Jan 31 23:25:42 2014 New Revision: 43713 URL: http://svnweb.freebsd.org/changeset/doc/43713 Log: Refer to a diff file generically rather than with the ambiguous ".diff.txt". Modified: head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml Modified: head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml Fri Jan 31 22:10:26 2014 (r43712) +++ head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml Fri Jan 31 23:25:42 2014 (r43713) @@ -244,7 +244,7 @@ enter a short description of the changes and any important details about them. Use the [ Browse... ] button to - attach the .diff.txt. + attach the diff file. From owner-svn-doc-all@FreeBSD.ORG Fri Jan 31 23:29:14 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 592C037F; Fri, 31 Jan 2014 23:29:14 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3954B1484; Fri, 31 Jan 2014 23:29:14 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VNTEP1057895; Fri, 31 Jan 2014 23:29:14 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VNTEnx057894; Fri, 31 Jan 2014 23:29:14 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401312329.s0VNTEnx057894@svn.freebsd.org> From: Dru Lavigne Date: Fri, 31 Jan 2014 23:29:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43714 - head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 23:29:14 -0000 Author: dru Date: Fri Jan 31 23:29:13 2014 New Revision: 43714 URL: http://svnweb.freebsd.org/changeset/doc/43714 Log: First 1/2 of syslogd section. Tighten wording and clarify unclear bits. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 23:25:42 2014 (r43713) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 23:29:13 2014 (r43714) @@ -5422,117 +5422,99 @@ driftfile /var/db/ntp.driftInteracting with system logs is a crucial aspect of both security and system administration. Monitoring the log files of - multiple hosts can get very unwieldy when these hosts are - distributed across medium or large networks, or when they are - parts of various different types of networks. In these cases, - configuring remote logging may make the whole process a lot more - comfortable. - - Centralized logging to a specific logging host can reduce - some of the administrative burden of log file administration. - Log file aggregation, merging and rotation may be configured in - one location, using the native tools of &os;, such as - &man.syslogd.8; and &man.newsyslog.8;. In the following example - configuration, host A, named + multiple hosts can become unwieldy as the number of systems increases. + Configuring centralized logging can reduce + some of the administrative burden of log file administration. + + Centralized log file aggregation, merging, and rotation can be configured + using &os; native tools, such as + &man.syslogd.8; and &man.newsyslog.8;. This section demonstrates an example + configuration, where host A, named logserv.example.com, will collect logging information for the local network. Host B, named logclient.example.com will - pass logging information to the server system. In live - configurations, both hosts require proper forward and reverse - DNS or entries in - /etc/hosts. Otherwise, data will be - rejected by the server. + class="fqdomainname">logclient.example.com, will be configured to + pass logging information to the logging server. Log Server Configuration - Log servers are machines configured to accept logging - information from remote hosts. In most cases this is to ease - configuration, in other cases it may just be a better - administration move. Regardless of reason, there are a few - requirements before continuing. - - A properly configured logging server has met the following - minimal requirements: + A log server is a system that has been configured to accept logging + information from other hosts. Before configuring a log server, check the following: - The firewall ruleset allows for UDP - to be passed on port 514 on both the client and - server; - - - - syslogd has been configured to - accept remote messages from client machines; + If there is a firewall between the logging server and + any logging clients, ensure that the firewall ruleset allows UDP + port 514 for both the clients and the + server. - The syslogd server and all client - machines must have valid entries for both forward and - reverse DNS, or be properly configured - in /etc/hosts. + The logging server and all client + machines must have forward and reverse entries in + the local DNS. If the network does not have + a DNS server, create entries in each system's + /etc/hosts. Proper name resolution is required + so that log entries are not rejected by the logging server. - To configure the log server, the client must be listed - in /etc/syslog.conf, and the logging - facility must be specified: + On the log server, edit + /etc/syslog.conf to specify the name of + the client to receive log entries from, the logging + facility to be used, and the name of the log to store the + host's log entries. This example adds the hostname of + B, logs all facilities, and stores + the log entries in /var/log/logclient.log. + + + Sample Log Server Configuration +logclient.example.com *.* /var/log/logclient.log + - - More information on various supported and available - facilities may be found in + When adding multiple log clients, add a similar two-line entry + for each client. More information about the available + facilities may be found in &man.syslog.conf.5;. - - - Once added, all facility messages will - be logged to the file specified previously, - /var/log/logclient.log. - The server machine must also have the following listing - placed inside /etc/rc.conf: + Next, configure /etc/rc.conf: syslogd_enable="YES" syslogd_flags="-a logclient.example.com -v -v" - The first option will enable the - syslogd daemon on boot up, and the second - option allows data from the specified client to be accepted on - this server. The latter part, using , - will increase the verbosity of logged messages. This is - extremely useful for tweaking facilities as administrators are - able to see what type of messages are being logged under which + The first entry starts + syslogd at system boot. The second + entry allows log entries from the specified client. + The + increases the verbosity of logged messages. This is + useful for tweaking facilities as administrators are + able to see what type of messages are being logged under each facility. Multiple options may be specified to allow logging from multiple clients. IP addresses and whole netblocks may also be specified. Refer to - &man.syslog.3; for a full list of possible + &man.syslogd.8; for a full list of possible options. - Finally, the log file should be created. The method used - does not matter, but &man.touch.1; works great for situations - such as this: + Finally, create the log file: - &prompt.root; touch - /var/log/logclient.log + &prompt.root; touch /var/log/logclient.log - At this point, the syslogd daemon + At this point, syslogd should be restarted and verified: &prompt.root; service syslogd restart &prompt.root; pgrep syslog - If a PID is returned, the server has - been restarted successfully, and client configuration may - begin. If the server has not restarted, consult the - /var/log/messages log for any - output. + If a PID is returned, the server + restarted successfully, and client configuration can + begin. If the server did not restart, consult + /var/log/messages for the error. From owner-svn-doc-all@FreeBSD.ORG Fri Jan 31 23:51:01 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0C74A5C; Fri, 31 Jan 2014 23:51:01 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AC10A1670; Fri, 31 Jan 2014 23:51:01 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VNp1K9067875; Fri, 31 Jan 2014 23:51:01 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VNp1Sv067874; Fri, 31 Jan 2014 23:51:01 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401312351.s0VNp1Sv067874@svn.freebsd.org> From: Warren Block Date: Fri, 31 Jan 2014 23:51:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43715 - head/en_US.ISO8859-1/books/fdp-primer/docbook-markup X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 23:51:01 -0000 Author: wblock Date: Fri Jan 31 23:51:01 2014 New Revision: 43715 URL: http://svnweb.freebsd.org/changeset/doc/43715 Log: Replace lost replaceable tags. Fix some examples with &os;, show device markup under filenames, and remove the obsolete devicename section. Modified: head/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml Modified: head/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml Fri Jan 31 23:29:13 2014 (r43714) +++ head/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml Fri Jan 31 23:51:01 2014 (r43715) @@ -146,8 +146,8 @@ - &os; Name - Entities + &os; + Name Entities @@ -808,7 +808,7 @@ Usage: warning - paraInstalling FreeBSD may make you want to delete Windows from your + paraInstalling &os; may make you want to delete Windows from your hard disk.para warning @@ -1304,7 +1304,7 @@ This is the file called 'foo2' Usage: - paraFreeBSD is without doubt emphasistheemphasis + para&os; is without doubt emphasistheemphasis premiere &unix;-like operating system for the Intel architecture.para @@ -1555,10 +1555,10 @@ This is the file called 'foo2' - Files, Directories, Extensions + Files, Directories, Extensions, Device Names - To refer to the name of a file, a directory, or a file - extension, use filename. For directory names, set + To refer to the name of a file, a directory, a file + extension, or a device name, use filename. For directory names, set the class attribute to directory. @@ -1572,16 +1572,25 @@ This is the file called 'foo2' class="directory"/usr/doc/en_US.ISO8859-1/books/handbook/filename. The main file is called filenamebook.xmlfilename. There is also a filenameMakefilefilename and a - number of files with a filename.entfilename extension.para + number of files with a filename.entfilename extension.para + +parafilenamekbd0filename is the first keyboard detected + by the system, and appears in + filename/devfilename.para + Appearance: The source for the Handbook in English is found in usr/doc/en_US.ISO8859-1/books/handbook/. + class="directory">/usr/doc/en_US.ISO8859-1/books/handbook/. The main file is called book.xml. There is also a Makefile and a number of files with a .ent extension. + + kbd0 is the first keyboard detected + by the system, and appears in + /dev. @@ -1630,63 +1639,6 @@ This is the file called 'foo2' - - Devices - - - &os; Extension - - These elements are part of the &os; extension to - DocBook, and do not exist in the original DocBook - DTD. - - - There are two names for devices: the device name as it - appears in /dev, or the name of the - device as it appears in the kernel. For this latter course, - use devicename. - - Sometimes there is no choice. Some devices, such as - network cards, do not have entries in - /dev, or the entries are markedly - different from their kernel device names. - - - <tag>devicename</tag> - - Usage: - - paradevicenamesiodevicename is used for serial - communication in FreeBSD. devicenamesiodevicename manifests - through a number of entries in filename/devfilename, including - filename/dev/ttyd0filename and filename/dev/cuaa0filename.para - -paraBy contrast, network devices such as - devicenameed0devicename do not appear in filename/devfilename.para - -paraIn MS-DOS, the first floppy drive is referred to as - devicenamea:devicename. In FreeBSD it is - filename/dev/fd0filename.para - - Appearance: - - sio is used for serial - communication in FreeBSD. sio - manifests through a number of entries in - /dev, including - /dev/ttyd0 and - /dev/cuaa0. - - By contrast, network devices such as - ed0 do not appear in - /dev. - - In MS-DOS, the first floppy drive is referred to as - a:. In FreeBSD it is - /dev/fd0. - - - Hosts, Domains, IP Addresses, User Names, and Other System Items @@ -1999,7 +1951,7 @@ This is the file called 'foo2' Appearance: - &prompt.user; man command + &prompt.user; man command replaceable can be used in many From owner-svn-doc-all@FreeBSD.ORG Fri Jan 31 23:54:22 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59586B7E; Fri, 31 Jan 2014 23:54:22 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 358E816A0; Fri, 31 Jan 2014 23:54:22 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0VNsMEg068504; Fri, 31 Jan 2014 23:54:22 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0VNsMN0068503; Fri, 31 Jan 2014 23:54:22 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401312354.s0VNsMN0068503@svn.freebsd.org> From: Warren Block Date: Fri, 31 Jan 2014 23:54:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43716 - head/en_US.ISO8859-1/books/fdp-primer/docbook-markup X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 23:54:22 -0000 Author: wblock Date: Fri Jan 31 23:54:21 2014 New Revision: 43716 URL: http://svnweb.freebsd.org/changeset/doc/43716 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml Modified: head/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml Fri Jan 31 23:51:01 2014 (r43715) +++ head/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml Fri Jan 31 23:54:21 2014 (r43716) @@ -147,7 +147,7 @@ &os; - Name Entities + Name Entities @@ -1558,8 +1558,8 @@ This is the file called 'foo2' Files, Directories, Extensions, Device Names To refer to the name of a file, a directory, a file - extension, or a device name, use filename. For directory names, set - the class attribute to + extension, or a device name, use filename. For + directory names, set the class attribute to directory. @@ -1576,8 +1576,7 @@ This is the file called 'foo2' parafilenamekbd0filename is the first keyboard detected by the system, and appears in - filename/devfilename.para - + filename/devfilename.para Appearance: @@ -1606,11 +1605,10 @@ This is the file called 'foo2' To include the name of a program from the &os; - Ports Collection in the document, use the - package tag. Since the Ports Collection can be installed in - any number of locations, only include the category and the - port name; do not include - /usr/ports. + Ports Collection in the document, use the package + tag. Since the Ports Collection can be installed in any + number of locations, only include the category and the port + name; do not include /usr/ports. By default, package refers to a binary package. To refer to a port that will be built from source, set the @@ -1631,8 +1629,7 @@ This is the file called 'foo2' Appearance: Install the net/wireshark binary - package to - view network traffic. + package to view network traffic. net/wireshark can also be built and installed from the Ports Collection. From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 00:50:47 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6D7945D3; Sat, 1 Feb 2014 00:50:47 +0000 (UTC) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A21AF1A57; Sat, 1 Feb 2014 00:50:46 +0000 (UTC) X-AuditID: 1209190f-f790b6d000000c3a-c7-52ec43b12f7b Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 49.EC.03130.1B34CE25; Fri, 31 Jan 2014 19:45:37 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id s110jadU022501; Fri, 31 Jan 2014 19:45:36 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id s110jXeB026175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 31 Jan 2014 19:45:35 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id s110jXPx007821; Fri, 31 Jan 2014 19:45:33 -0500 (EST) Date: Fri, 31 Jan 2014 19:45:33 -0500 (EST) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: Dru Lavigne Subject: Re: svn commit: r43710 - head/en_US.ISO8859-1/books/handbook/network-servers In-Reply-To: <201401312135.s0VLZCfJ014161@svn.freebsd.org> Message-ID: References: <201401312135.s0VLZCfJ014161@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNIsWRmVeSWpSXmKPExsUixG6nrrvR+U2QwdbfIhY/Ph5isuhqUrW4 sWg/k8Xu/l5mBxaPGZ/mswQwRnHZpKTmZJalFunbJXBlrHpymqXgGX9F34zLjA2MX3m6GDk5 JARMJNbO/cUMYYtJXLi3nq2LkYtDSGA2k8Tfh++ZIJyNjBLbv/1lBKkSEjgElDnKCZFoYJTY NOsVUBUHB4uAtsSGyYogNWwCahKP9zazQkxVlNh8ahLYBhEg++nXvWBzmAWiJPYsbWQFaRUW CJd4viIJJMwpYCXReuM8WAmvgKPEstbTTBBrLSWOTPjJBmKLCuhIrN4/hQWiRlDi5MwnLBAj LSX+rf3FOoFRaBaS1CwkqQWMTKsYZVNyq3RzEzNzilOTdYuTE/PyUot0TfRyM0v0UlNKNzGC wphTkn8H47eDSocYBTgYlXh4G068DhJiTSwrrsw9xCjJwaQkynvS5E2QEF9SfkplRmJxRnxR aU5q8SFGCQ5mJRFeeWmgHG9KYmVValE+TEqag0VJnPcmh32QkEB6YklqdmpqQWoRTFaGg0NJ gveVA1CjYFFqempFWmZOCUKaiYMTZDgP0HBdJ5DhxQWJucWZ6RD5U4yKUuK8G0ASAiCJjNI8 uF5YmnnFKA70ijBvDkgVDzBFwXW/AhrMBDS458BrkMEliQgpqQbGpTKRO6I+d277q79L8qrX UsG9jacuKlZ92LjuWVxc93nvsrV/VnZP37VrMZ/Y7n+Ss24K8i3a8MQy9vzc+8vUtqw5+MFp T/X2Ey+XBJUfDv9lfnuhlZB1Tln6NqYm79UmQVN/q3/8+am2SGqZ1r7rOYwTpDa5iOoEXpzZ MqXLYEqk3c73URry0UosxRmJhlrMRcWJAE3PXhAOAwAA Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 00:50:47 -0000 On Fri, 31 Jan 2014, Dru Lavigne wrote: > Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 20:55:48 2014 (r43709) > +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 31 21:35:11 2014 (r43710) > @@ -5227,208 +5227,158 @@ Starting smbd. > + To only synchronize the clock when a system boots, > + use &man.ntpdate.8;. This alone can be appropriate for ntpd.8 seems to claim that ntpdate is deprecated (to be replaced by 'ntpd -q', I guess?). Yet, we still ship an /etc/rc.d/ntpdate in the base system, so maybe I'm confused as to what exactly is going on. > + desktops which are frequently rebooted. However, > + most systems should > + run ntpdate at boot time as well as configure ntpd. > + This is because ntpd > + changes the clock gradually, whereas ntpdate > sets the clock, no matter how great the difference between a > that server is preferred over other servers. A response > from a preferred server will be discarded if it differs > - significantly from other servers' responses, otherwise it > - will be used without any consideration to other responses. > - The prefer argument is normally used for > - NTP servers that are known to be highly accurate, such as > + significantly from responses; otherwise it "if it differs significantly from responses" seems strange, I think I prefer the original ("from other servers' responses"). -Ben > + will be used. > + The prefer argument should only be used for > + NTP servers that are known to be highly accurate, such as > those with special time monitoring hardware. > From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 00:53:09 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D83C7645 for ; Sat, 1 Feb 2014 00:53:09 +0000 (UTC) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9D1731A67 for ; Sat, 1 Feb 2014 00:53:09 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id lx4so5002179iec.13 for ; Fri, 31 Jan 2014 16:53:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=edekLLdobM/AAbglCPp3hAogH/0lMIFDoKfYkH6iOec=; b=HjGdrpAmZ5DLhxw+rQUk1lzVMijxsjcKP6l1bGbBvhs6BN62fTENAFO39vZ3DLpEap HjtR6syeTPZ2o4BMgc/cmuWl0tBr/UFcqjerY4BMNSir0B/XFrS30qkr6sYPhk1brYve zKtSM+EfCMb0LVLjwYRUTQlq+UqZ4i8XMis08ivf4Htn2L+eOo3reL/MsSINbE+Iu/FD NJnHBmwwo7hf6ZIvDXH5wH2WM+sfKsG9wSITy81xM5rlnlWrmHFv5KIZ4Y7HPHH3p0xs o2U91VxPt155cfiNwIFOiR++aoUq0D4vznmSIF83DQ53CKqdXtMZ8WfutHCwBEZL84gB g3Pw== X-Gm-Message-State: ALoCoQmqMnFidF8gMIQgTauNAHrBTYvVcJ7BbomlHxBI5rHGPk282WO1d1KOgKhYWYttmMoFkMYs X-Received: by 10.50.67.72 with SMTP id l8mr5234948igt.0.1391215983238; Fri, 31 Jan 2014 16:53:03 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id a1sm2846155igo.0.2014.01.31.16.53.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 Jan 2014 16:53:02 -0800 (PST) Sender: Warner Losh Subject: Re: svn commit: r43710 - head/en_US.ISO8859-1/books/handbook/network-servers Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Fri, 31 Jan 2014 17:53:01 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201401312135.s0VLZCfJ014161@svn.freebsd.org> To: Benjamin Kaduk X-Mailer: Apple Mail (2.1085) Cc: svn-doc-head@freebsd.org, Dru Lavigne , svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 00:53:09 -0000 On Jan 31, 2014, at 5:45 PM, Benjamin Kaduk wrote: > On Fri, 31 Jan 2014, Dru Lavigne wrote: >=20 >> Modified: = head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >> --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml = Fri Jan 31 20:55:48 2014 (r43709) >> +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml = Fri Jan 31 21:35:11 2014 (r43710) >> @@ -5227,208 +5227,158 @@ Starting smbd. >> + To only synchronize the clock when a system boots, >> + use &man.ntpdate.8;. This alone can be appropriate for >=20 > ntpd.8 seems to claim that ntpdate is deprecated (to be replaced by = 'ntpd -q', I guess?). Yet, we still ship an /etc/rc.d/ntpdate in the = base system, so maybe I'm confused as to what exactly is going on. ntpdate is deprecated. Except it may never actually die. Warner From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 02:33:08 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8F4F346; Sat, 1 Feb 2014 02:33:08 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A1910110E; Sat, 1 Feb 2014 02:33:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s112X87s030934; Sat, 1 Feb 2014 02:33:08 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s112X8SJ030933; Sat, 1 Feb 2014 02:33:08 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201402010233.s112X8SJ030933@svn.freebsd.org> From: Warren Block Date: Sat, 1 Feb 2014 02:33:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43718 - head/en_US.ISO8859-1/books/handbook/bibliography X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 02:33:08 -0000 Author: wblock Date: Sat Feb 1 02:33:08 2014 New Revision: 43718 URL: http://svnweb.freebsd.org/changeset/doc/43718 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Sat Feb 1 01:29:20 2014 (r43717) +++ head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Sat Feb 1 02:33:08 2014 (r43718) @@ -4,7 +4,10 @@ $FreeBSD$ --> - + + Bibliography While the manual pages provide the definitive reference for @@ -22,9 +25,11 @@ - Using + Using FreeBSD (in Traditional Chinese), published by - Drmaster, + Drmaster, 1997. ISBN 9-578-39435-7. @@ -44,8 +49,9 @@ FreeBSD Handbook Second Edition (Simplified Chinese - translation), published by Posts & Telecom - Press. ISBN 7-115-10541-3. + translation), published by Posts & + Telecom Press. ISBN 7-115-10541-3. @@ -66,23 +72,25 @@ - Complete - Introduction to FreeBSD (in Japanese), published - by Shoeisha Co., + Complete + Introduction to FreeBSD (in Japanese), published by + Shoeisha Co., Ltd. ISBN 4-88135-473-6 P3600E. - Personal + Personal UNIX Starter Kit FreeBSD (in Japanese), published - by ASCII. ISBN - 4-7561-1733-3 P3000E. + by ASCII. + ISBN 4-7561-1733-3 P3000E. FreeBSD Handbook (Japanese translation), published by - ASCII. ISBN - 4-7561-1580-2 P3800E. + ASCII. + ISBN 4-7561-1580-2 P3800E. @@ -93,14 +101,16 @@ - + FreeBSD de Luxe (in German), published by Verlag Modere Industrie, 2003. ISBN 3-8266-1343-0. - FreeBSD + FreeBSD Install and Utilization Manual (in Japanese), published by Mainichi @@ -110,22 +120,25 @@ Onno W Purbo, Dodi Maryanto, Syahrial Hubbany, Widjil - Widodo Building Internet Server - with FreeBSD (in Indonesia Language), - published by Elex + Widodo Building Internet + Server with FreeBSD (in Indonesia + Language), published by + Elex Media Komputindo. Absolute BSD: The Ultimate Guide to FreeBSD (Traditional - Chinese translation), published by GrandTech + Chinese translation), published by GrandTech Press, 2003. ISBN 986-7944-92-5. - The FreeBSD 6.0 - Book (in Traditional Chinese), published by - Drmaster, 2006. ISBN 9-575-27878-X. + The + FreeBSD 6.0 Book (in Traditional Chinese), + published by Drmaster, 2006. ISBN 9-575-27878-X. @@ -134,7 +147,8 @@ - Absolute + Absolute FreeBSD, 2nd Edition: The Complete Guide to FreeBSD, published by No Starch @@ -142,47 +156,52 @@ - + The Complete FreeBSD, published by - O'Reilly, 2003. - ISBN: 0596005164 + O'Reilly, + 2003. ISBN: 0596005164 - The + The FreeBSD Corporate Networker's Guide, published by - Addison-Wesley, + Addison-Wesley, 2000. ISBN: 0201704811 - + FreeBSD: An Open-Source Operating System for Your Personal Computer, published by The Bit Tree Press, 2001. ISBN: 0971204500 - Teach Yourself FreeBSD in 24 Hours, published by - Sams, + Teach Yourself FreeBSD in 24 Hours, published by Sams, 2002. ISBN: 0672324245 - FreeBSD 6 Unleashed, published by - Sams, + FreeBSD 6 Unleashed, published by Sams, 2006. ISBN: 0672328755 - FreeBSD: The Complete Reference, published by McGrawHill, + FreeBSD: The Complete Reference, published by McGrawHill, 2003. ISBN: 0072224096 - BSD Magazine, - published by Software Press Sp. z o.o. SK. - ISSN 1898-9144 + BSD + Magazine, published by Software Press Sp. z o.o. + SK. ISSN 1898-9144 @@ -192,28 +211,32 @@ - Ohio State University has written a UNIX + Ohio State University has written a UNIX Introductory Course which is available online in HTML and PostScript format. - An Italian translation + An Italian translation of this document is available as part of the FreeBSD Italian Documentation Project. - Jpman Project, - Japan FreeBSD Users Group. FreeBSD + Jpman + Project, Japan FreeBSD Users Group. FreeBSD User's Reference Manual (Japanese translation). - Mainichi + Mainichi Communications Inc., 1998. ISBN4-8399-0088-4 P3800E. Edinburgh - University has written an Online Guide for - newcomers to the UNIX environment. + University has written an + Online + Guide for newcomers to the UNIX environment. @@ -223,15 +246,19 @@ - Jpman Project, - Japan FreeBSD Users Group. FreeBSD + Jpman + Project, Japan FreeBSD Users Group. FreeBSD System Administrator's Manual (Japanese - translation). Mainichi Communications - Inc., 1998. ISBN4-8399-0109-0 P3300E. + translation). + Mainichi + Communications Inc., 1998. ISBN4-8399-0109-0 + P3300E. - Dreyfus, Emmanuel. Cahiers + Dreyfus, Emmanuel. Cahiers de l'Admin: BSD 2nd Ed. (in French), Eyrolles, 2004. ISBN 2-212-11463-X @@ -281,13 +308,15 @@ - Spinellis, Diomidis. Code + Spinellis, Diomidis. Code Reading: The Open Source Perspective. Addison-Wesley, 2003. ISBN 0-201-79940-5 - Spinellis, Diomidis. Code + Spinellis, Diomidis. Code Quality: The Open Source Perspective. Addison-Wesley, 2006. ISBN 0-321-16607-8 @@ -345,8 +374,9 @@ Reading, Mass. : Addison-Wesley, 1996. ISBN 0-201-54979-4 - (Chapter 2 of this book is available online as - part of the FreeBSD Documentation Project.) + (Chapter 2 of this book is available online + as part of the FreeBSD Documentation Project.) @@ -384,7 +414,7 @@ Wright, Gary R. and W. Richard Stevens. TCP/IP Illustrated, Volume 2: The - Implementation. Reading, Mass. : + Implementation. Reading, Mass. : Addison-Wesley, 1995. ISBN 0-201-63354-X @@ -429,7 +459,8 @@ Intel Corporation publishes documentation on their CPUs, - chipsets and standards on their developer web + chipsets and standards on their + developer web site, usually as PDF files. @@ -478,7 +509,8 @@ Raymond, Eric S. The New Hacker's Dictionary, 3rd edition. MIT Press, 1996. ISBN - 0-262-68092-0. Also known as the Jargon + 0-262-68092-0. Also known as the Jargon File @@ -492,7 +524,8 @@ Simon Garfinkel, Daniel Weise, Steven Strassmann. The UNIX-HATERS Handbook. IDG Books Worldwide, Inc., 1994. ISBN 1-56884-203-1. Out of print, - but available online. + but available online. @@ -503,23 +536,24 @@ The BSD family tree. - http://www.FreeBSD.org/cgi/cvsweb.cgi/src/share/misc/bsd-family-tree - or - /usr/share/misc/bsd-family-tree + http://www.FreeBSD.org/cgi/cvsweb.cgi/src/share/misc/bsd-family-tree + or /usr/share/misc/bsd-family-tree on a FreeBSD machine. Networked Computer Science Technical Reports - Library. - http://www.ncstrl.org/ + Library. http://www.ncstrl.org/ Old BSD releases from the Computer Systems - Research group (CSRG). - http://www.mckusick.com/csrg/: The - 4CD set covers all BSD versions from 1BSD to 4.4BSD and + Research group (CSRG). http://www.mckusick.com/csrg/: + The 4CD set covers all BSD versions from 1BSD to 4.4BSD and 4.4BSD-Lite2 (but not 2.11BSD, unfortunately). The last disk also holds the final sources plus the SCCS files. From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 02:35:50 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 908433D7; Sat, 1 Feb 2014 02:35:50 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7CC2C111F; Sat, 1 Feb 2014 02:35:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s112Zorw031267; Sat, 1 Feb 2014 02:35:50 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s112ZokL031266; Sat, 1 Feb 2014 02:35:50 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201402010235.s112ZokL031266@svn.freebsd.org> From: Warren Block Date: Sat, 1 Feb 2014 02:35:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43719 - head/en_US.ISO8859-1/books/handbook/bibliography X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 02:35:50 -0000 Author: wblock Date: Sat Feb 1 02:35:50 2014 New Revision: 43719 URL: http://svnweb.freebsd.org/changeset/doc/43719 Log: Fix abbreviations of "Edition". Modified: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Sat Feb 1 02:33:08 2014 (r43718) +++ head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Sat Feb 1 02:35:50 2014 (r43719) @@ -285,7 +285,7 @@ Harbison, Samuel P. and Steele, Guy L. Jr. C: - A Reference Manual. 4th ed. Prentice Hall, + A Reference Manual. 4th Ed. Prentice Hall, 1995. ISBN 0-13-326224-3 @@ -466,19 +466,19 @@ Shanley, Tom. 80486 System - Architecture. 3rd ed. Reading, Mass. : + Architecture. 3rd Ed. Reading, Mass. : Addison-Wesley, 1995. ISBN 0-201-40994-1 Shanley, Tom. ISA System - Architecture. 3rd ed. Reading, Mass. : + Architecture. 3rd Ed. Reading, Mass. : Addison-Wesley, 1995. ISBN 0-201-40996-8 Shanley, Tom. PCI System - Architecture. 4th ed. Reading, Mass. : + Architecture. 4th Ed. Reading, Mass. : Addison-Wesley, 1999. ISBN 0-201-30974-2 From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 02:43:43 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7A344E8; Sat, 1 Feb 2014 02:43:43 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B29C4119B; Sat, 1 Feb 2014 02:43:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s112hh9t034743; Sat, 1 Feb 2014 02:43:43 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s112hh0l034742; Sat, 1 Feb 2014 02:43:43 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201402010243.s112hh0l034742@svn.freebsd.org> From: Warren Block Date: Sat, 1 Feb 2014 02:43:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43720 - head/en_US.ISO8859-1/books/handbook/boot X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 02:43:43 -0000 Author: wblock Date: Sat Feb 1 02:43:43 2014 New Revision: 43720 URL: http://svnweb.freebsd.org/changeset/doc/43720 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Sat Feb 1 02:35:50 2014 (r43719) +++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Sat Feb 1 02:43:43 2014 (r43720) @@ -4,7 +4,11 @@ $FreeBSD$ --> - + + + The &os; Booting Process @@ -543,14 +547,20 @@ boot: - Boot Time Splash Screens + + Boot Time Splash Screens + - Joseph J.BarbishContributed by + + + Joseph J. + Barbish + + Contributed by + - - The splash screen creates an alternate boot screen. The splash screen hides all the boot probe messages and service startup messages before displaying either a command line or @@ -606,10 +616,12 @@ boot: boot time, even when the splash screen is enabled. Sample splash screen files can be downloaded from the - gallery at http://artwork.freebsdgr.org. - By installing the sysutils/bsd-splash-changer - port, splash images can be chosen from a collection - randomly at each boot. + gallery at http://artwork.freebsdgr.org. + By installing the + sysutils/bsd-splash-changer port, + splash images can be chosen from a collection randomly at + each boot. @@ -651,7 +663,8 @@ bitmap_load="YES" bitmap_name="/boot/splash.pcx" Beginning with &os; 8.3, another option is to use - ASCII art in TheDraw + ASCII art in TheDraw format. splash_txt="YES" @@ -711,7 +724,8 @@ bitmap_name="/boot/splash.b Once the kernel is loaded by either the default loader - () or by boot2 (), which bypasses the loader, it + () or by boot2 + (), which bypasses the loader, it examines any boot flags and adjusts its behavior as necessary. @@ -780,19 +794,23 @@ bitmap_name="/boot/splash.b --> - - Device Hints + + Device Hints + - TomRhodesContributed by + + + Tom + Rhodes + + Contributed by + - - - device.hints @@ -915,8 +933,9 @@ bitmap_name="/boot/splash.b If the system console is set to insecure in /etc/ttys, - the system will prompt for the root - password before initiating single-user mode. + the system will prompt for the + root password before + initiating single-user mode. An Insecure Console in @@ -933,10 +952,10 @@ console none <para>An <literal>insecure</literal> console means that physical security to the console is considered to be insecure, so only someone who knows the - <systemitem class="username">root</systemitem> password may use single-user mode. - Thus, to add this measure of security, choose - <literal>insecure</literal>, instead of the default of - <literal>secure</literal>.</para> + <systemitem class="username">root</systemitem> password may + use single-user mode. Thus, to add this measure of + security, choose <literal>insecure</literal>, instead of the + default of <literal>secure</literal>.</para> </note> </sect2> @@ -988,12 +1007,14 @@ console none not terminate in a timely manner.</para> <para>To power down a &os; machine on architectures and systems - that support power management, use <command>shutdown -p - now</command> to turn the power off immediately. To reboot a - &os; system, use <command>shutdown -r now</command>. One must - be <systemitem class="username">root</systemitem> or a member of - <systemitem class="groupname">operator</systemitem> in order to run - &man.shutdown.8;. One can also use &man.halt.8; and + that support power management, use + + <command>shutdown -p now</command> to turn the power off + immediately. To reboot a &os; system, use + <command>shutdown -r now</command>. One must be + <systemitem class="username">root</systemitem> or a member of + <systemitem class="groupname">operator</systemitem> in order to + run &man.shutdown.8;. One can also use &man.halt.8; and &man.reboot.8;. Refer to their manual pages and to &man.shutdown.8; for more information.</para> From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 02:45:52 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16D6D54B; Sat, 1 Feb 2014 02:45:52 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 02C6011A0; Sat, 1 Feb 2014 02:45:52 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s112jpV8035084; Sat, 1 Feb 2014 02:45:51 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s112jpZQ035083; Sat, 1 Feb 2014 02:45:51 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201402010245.s112jpZQ035083@svn.freebsd.org> From: Warren Block <wblock@FreeBSD.org> Date: Sat, 1 Feb 2014 02:45:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43721 - head/en_US.ISO8859-1/books/handbook/boot X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 01 Feb 2014 02:45:52 -0000 Author: wblock Date: Sat Feb 1 02:45:51 2014 New Revision: 43721 URL: http://svnweb.freebsd.org/changeset/doc/43721 Log: Fix spelling. Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Sat Feb 1 02:43:43 2014 (r43720) +++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Sat Feb 1 02:45:51 2014 (r43721) @@ -1020,7 +1020,7 @@ console none <note> <para>Power management requires &man.acpi.4; to be loaded as - a module or staticly compiled into a custom kernel.</para> + a module or statically compiled into a custom kernel.</para> </note> </sect1> </chapter> From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 02:48:30 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 444C8600 for <svn-doc-all@freebsd.org>; Sat, 1 Feb 2014 02:48:30 +0000 (UTC) Received: from nm15-vm7.access.bullet.mail.gq1.yahoo.com (nm15-vm7.access.bullet.mail.gq1.yahoo.com [216.39.63.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 06ABA11B0 for <svn-doc-all@freebsd.org>; Sat, 1 Feb 2014 02:48:29 +0000 (UTC) Received: from [216.39.60.173] by nm15.access.bullet.mail.gq1.yahoo.com with NNFMP; 01 Feb 2014 02:45:50 -0000 Received: from [216.39.60.250] by tm9.access.bullet.mail.gq1.yahoo.com with NNFMP; 01 Feb 2014 02:45:50 -0000 Received: from [127.0.0.1] by omp1021.access.mail.gq1.yahoo.com with NNFMP; 01 Feb 2014 02:45:50 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 134206.14881.bm@omp1021.access.mail.gq1.yahoo.com Received: (qmail 11946 invoked by uid 60001); 1 Feb 2014 02:45:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1391222750; bh=W02ZZDFvlJNqsbM6S1TfR1dEMfmgr5r4Kx41VPYHfyE=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LQ4HtJ4c/CgoHcFByWw8EnHiS3y/xZhl4aiCEyHwFK5pAkwVLWep5zet/Y/d6VCYaFbeRhjL4IUsDbrXDA3JNqRnG3v/qXU7gowMVZCg3VW15aCm3iIHyqPOUWkG4v/Hzd37gSn2HMCn16QMVTJQ+doo8CfWGsCb83K2EHk6ly8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=att.net; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=iXLPgOotdqhyCQqYR66Cc4x7Sqw70/ank9X3WvgTp3pZVHR8rbHl4xy2zIayIjV7CiVHzKdEHuKbjc1ITzhLAXVB2l3mQBm/jSUUdA0TXd7d6dXle6Fszbldv98a0oscoY9fpLIXmcnMjuVUBZKe0+x9/QiWLireGVZB5O4v3ss=; X-YMail-OSG: l26hcQIVM1lgQoweKko11HR5Wd_qNdfDocp8o2exNQ3ien0 1U4xoh1jC_rNJoos18KgTvlOTXaqSaOapaYxcgOUJOlL9ZH36l1LJn39iyvP XFsCHQ73Jdqf3ehqXK5zcmAOZdeCUEvt_Nr5wTlS6diVUZL9J8FpvPpWTwbh n9mYkDyoc5jEDdhF92YkRoaVObWU29Ed1nqdl7KmXWVaWTiU3GnYwLaq0MIb DZ9P6OjLX939nkf8Tp5nt2HxAulMESipQNAYvPhGjwjnntBUdPkW6wTtUq24 hTWkZGoKyl0uIy6Zt2ZZVvYMbG6PQUKimJRI8ZVvNgVsko8gUL0HHCZc4kvT 3HEvbDB2tc11XSbgG9TJJXXHxQm0PtGVY3iPTQRshn9tG820mGT1oJWpVKaK NF5r64AjudLQnFcKxuAVIQXchQpoc92VRgZSPFFzHQncRQA734hOMsbjTrPU 68Bj6h9OI1sh40i8JcglMB3lU3tGcD8VNi7815N0fsn9m9mjyOj8tnv6B.MK CypW5ursCren8p5akVpwmc_g- Received: from [99.98.83.69] by web184904.mail.gq1.yahoo.com via HTTP; Fri, 31 Jan 2014 18:45:50 PST X-Rocket-MIMEInfo: 002.001, Cgo.IE9uIEphbiAzMSwgMjAxNCwgYXQgNTo0NSBQTSwgQmVuamFtaW4gS2FkdWsgd3JvdGU6Cj4gCj4.ICBPbiBGcmksIDMxIEphbiAyMDE0LCBEcnUgTGF2aWduZSB3cm90ZToKPj4gCj4.PiAgTW9kaWZpZWQ6IAo.IGhlYWQvZW5fVVMuSVNPODg1OS0xL2Jvb2tzL2hhbmRib29rL25ldHdvcmstc2VydmVycy9jaGFwdGVyLnhtbAo.Pj4gCj4gPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4.PiAgLS0tIGhlYWQvZW4BMAEBAQE- X-Mailer: YahooMailWebService/0.8.174.629 References: <201401312135.s0VLZCfJ014161@svn.freebsd.org> <alpine.GSO.1.10.1401311936490.27579@multics.mit.edu> <ACA43870-8169-4D7B-BCBA-71915E6654A7@bsdimp.com> Message-ID: <1391222750.9523.YahooMailNeo@web184904.mail.gq1.yahoo.com> Date: Fri, 31 Jan 2014 18:45:50 -0800 (PST) From: Dru Lavigne <dru.lavigne@att.net> Subject: Re: svn commit: r43710 - head/en_US.ISO8859-1/books/handbook/network-servers To: Warner Losh <imp@bsdimp.com>, Benjamin Kaduk <bjk@freebsd.org> In-Reply-To: <ACA43870-8169-4D7B-BCBA-71915E6654A7@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "svn-doc-head@freebsd.org" <svn-doc-head@freebsd.org>, "svn-doc-all@freebsd.org" <svn-doc-all@freebsd.org>, "doc-committers@freebsd.org" <doc-committers@freebsd.org> X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Dru Lavigne <dru@freebsd.org> List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 01 Feb 2014 02:48:30 -0000 =0A=0A> On Jan 31, 2014, at 5:45 PM, Benjamin Kaduk wrote:=0A> =0A>> On Fr= i, 31 Jan 2014, Dru Lavigne wrote:=0A>> =0A>>> Modified: =0A> head/en_US.I= SO8859-1/books/handbook/network-servers/chapter.xml=0A>>> =0A> =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A= >>> --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml=A0= =A0=A0 =0A> Fri Jan 31 20:55:48 2014=A0=A0=A0 (r43709)=0A>>> +++ head/en_U= S.ISO8859-1/books/handbook/network-servers/chapter.xml=A0=A0=A0 =0A> Fri Ja= n 31 21:35:11 2014=A0=A0=A0 (r43710)=0A>>> @@ -5227,208 +5227,158 @@ Start= ing smbd.</screen>=0A>>> +=A0=A0=A0 <para>To only synchronize the clock wh= en a system boots,=0A>>> +=A0=A0=A0 =A0 use &man.ntpdate.8;.=A0 This alone= can be appropriate for=0A>> =0A>> ntpd.8 seems to claim that ntpdate is d= eprecated (to be replaced by =0A> 'ntpd -q', I guess?).=A0 Yet, we still sh= ip an /etc/rc.d/ntpdate in the =0A> base system, so maybe I'm confused as t= o what exactly is going on.=0A> =0A> ntpdate is deprecated. Except it may n= ever actually die.=0A=0A=0AGood catch! I'll make an appropriate patch this = weekend.=0A=0ACheers,=0A=0ADru=0A From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 02:49:01 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B49C626; Sat, 1 Feb 2014 02:49:01 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 17ABE11B3; Sat, 1 Feb 2014 02:49:01 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s112n0IT035470; Sat, 1 Feb 2014 02:49:00 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s112n0o9035469; Sat, 1 Feb 2014 02:49:00 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201402010249.s112n0o9035469@svn.freebsd.org> From: Warren Block <wblock@FreeBSD.org> Date: Sat, 1 Feb 2014 02:49:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43722 - head/en_US.ISO8859-1/books/handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 01 Feb 2014 02:49:01 -0000 Author: wblock Date: Sat Feb 1 02:49:00 2014 New Revision: 43722 URL: http://svnweb.freebsd.org/changeset/doc/43722 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/handbook/colophon.xml Modified: head/en_US.ISO8859-1/books/handbook/colophon.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/colophon.xml Sat Feb 1 02:45:51 2014 (r43721) +++ head/en_US.ISO8859-1/books/handbook/colophon.xml Sat Feb 1 02:49:00 2014 (r43722) @@ -4,7 +4,10 @@ $FreeBSD$ --> -<colophon xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="colophon"> +<colophon xmlns="http://docbook.org/ns/docbook" + xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" + xml:id="colophon"> + <para>This book is the combined work of hundreds of contributors to <quote>The FreeBSD Documentation Project</quote>. The text is authored in XML according to the DocBook DTD and is formatted From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 16:28:03 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6642BAE1; Sat, 1 Feb 2014 16:28:03 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 524951A6B; Sat, 1 Feb 2014 16:28:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s11GS36P053360; Sat, 1 Feb 2014 16:28:03 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s11GS3Pk053359; Sat, 1 Feb 2014 16:28:03 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201402011628.s11GS3Pk053359@svn.freebsd.org> From: Ryusuke SUZUKI <ryusuke@FreeBSD.org> Date: Sat, 1 Feb 2014 16:28:03 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43723 - head/ja_JP.eucJP/htdocs/security X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 01 Feb 2014 16:28:03 -0000 Author: ryusuke Date: Sat Feb 1 16:28:02 2014 New Revision: 43723 URL: http://svnweb.freebsd.org/changeset/doc/43723 Log: - Merge the following from the English version: r43582 -> r43705 head/ja_JP.eucJP/htdocs/security/security.xml Modified: head/ja_JP.eucJP/htdocs/security/security.xml Modified: head/ja_JP.eucJP/htdocs/security/security.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/security/security.xml Sat Feb 1 02:49:00 2014 (r43722) +++ head/ja_JP.eucJP/htdocs/security/security.xml Sat Feb 1 16:28:02 2014 (r43723) @@ -6,7 +6,7 @@ ]> <!-- $FreeBSD$ --> <!-- The FreeBSD Japanese Documentation Project --> -<!-- Original revision: r43582 --> +<!-- Original revision: r43705 --> <html xmlns="http://www.w3.org/1999/xhtml"> <head> @@ -76,7 +76,7 @@ <td>¤Ê¤·</td> <td>¤Ê¤·</td> <td>¤Ê¤·</td> - <td>ºÇ½ª¥ê¥ê¡¼¥¹¸å 2 ǯ</td> + <td>2015 ǯ 6 ·î 30 Æü</td> </tr> <tr> <td>releng/8.3</td> From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 17:01:49 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7530377; Sat, 1 Feb 2014 17:01:49 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A36F21DA0; Sat, 1 Feb 2014 17:01:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s11H1nqn068029; Sat, 1 Feb 2014 17:01:49 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s11H1nmZ068028; Sat, 1 Feb 2014 17:01:49 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201402011701.s11H1nmZ068028@svn.freebsd.org> From: Ryusuke SUZUKI <ryusuke@FreeBSD.org> Date: Sat, 1 Feb 2014 17:01:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43724 - head/ja_JP.eucJP/books/handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 01 Feb 2014 17:01:49 -0000 Author: ryusuke Date: Sat Feb 1 17:01:49 2014 New Revision: 43724 URL: http://svnweb.freebsd.org/changeset/doc/43724 Log: - Merge the following from the English version: r41678 -> r43722 head/ja_JP.eucJP/books/handbook/colophon.xml Modified: head/ja_JP.eucJP/books/handbook/colophon.xml Modified: head/ja_JP.eucJP/books/handbook/colophon.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/colophon.xml Sat Feb 1 16:28:02 2014 (r43723) +++ head/ja_JP.eucJP/books/handbook/colophon.xml Sat Feb 1 17:01:49 2014 (r43724) @@ -3,16 +3,18 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r41678 + Original revision: r43722 $FreeBSD$ --> -<colophon xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="colophon"> +<colophon xmlns="http://docbook.org/ns/docbook" + xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" + xml:id="colophon"> + <para>¤³¤ÎËÜ¤Ï <quote>The FreeBSD Documentation Project</quote> ¤ËÂФ¹¤ë¤¿¤¯¤µ¤ó¤Î¿Í¡¹¤Î¶¦Æ±ºî¶È¤Ë¤è¤Ã¤Æ´°À®¤·¤¿¤â¤Î¤Ç¤¹¡£ ʸ½ñ¤Ï DocBook DTD ¤òÍѤ¤¤¿ XML ·Á¼°¤Ç´ÉÍý¤µ¤ì¤Æ¤ª¤ê¡¢ XSLT ¤ò»È¤Ã¤Æ XML ¤«¤é¤µ¤Þ¤¶¤Þ¤Ê²ÄÆÉ·Á¼°¤ËÁÈÈǤµ¤ì¤Æ¤¤¤Þ¤¹¡£ - ¤â¤·¡¢Donald Knuth »á¤Ë¤è¤ë - ÁÈÈǸÀ¸ì &tex;¡¢ + ¤â¤·¡¢Donald Knuth »á¤Ë¤è¤ëÁÈÈǸÀ¸ì &tex;¡¢ Leslie Lamport »á¤Ë¤è¤ë <application>LaTeX</application> ¤ª¤è¤Ó Sebastian Rahtz »á¤Ë¤è¤ë <application>JadeTeX</application> ¥Þ¥¯¥í¥Ñ¥Ã¥±¡¼¥¸¤¬¤Ê¤«¤Ã¤¿¤é¡¢ From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 18:37:55 2014 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 07A8AC04; Sat, 1 Feb 2014 18:37:55 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DBF711386; Sat, 1 Feb 2014 18:37:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s11IbsMc010118; Sat, 1 Feb 2014 18:37:54 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s11IbsvU010117; Sat, 1 Feb 2014 18:37:54 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402011837.s11IbsvU010117@svn.freebsd.org> From: Dru Lavigne <dru@FreeBSD.org> Date: Sat, 1 Feb 2014 18:37:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43725 - head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 01 Feb 2014 18:37:55 -0000 Author: dru Date: Sat Feb 1 18:37:54 2014 New Revision: 43725 URL: http://svnweb.freebsd.org/changeset/doc/43725 Log: Finish syslogd section. Clarify examples. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat Feb 1 17:01:49 2014 (r43724) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat Feb 1 18:37:54 2014 (r43725) @@ -5520,80 +5520,43 @@ syslogd_flags="-a logclient.example.com <sect2> <title>Log Client Configuration - A logging client is a machine which sends log information - to a logging server in addition to keeping local - copies. - - Similar to log servers, clients must also meet a few - minimum requirements: - - - - &man.syslogd.8; must be configured to send messages of - specific types to a log server, which must accept - them; - - - - The firewall must allow UDP packets - through on port 514; - - - - Both forward and reverse DNS must - be configured or have proper entries in the - /etc/hosts. - - - - Client configuration is a bit more relaxed when compared - to that of the servers. The client machine must have the - following listing placed inside - /etc/rc.conf: + A logging client sends log entries + to a logging server on the network. The client also keeps a local + copy of its own logs. + + Once a logging server has been configured, edit + /etc/rc.conf on the logging client: syslogd_enable="YES" syslogd_flags="-s -v -v" - As before, these entries will enable the - syslogd daemon on boot up, and increases - the verbosity of logged messages. The - option prevents logs from being accepted by this client from - other hosts. - - Facilities describe the system part for which a message - is generated. For an example, ftp and - ipfw are both facilities. When log - messages are generated for those two services, they will - normally include those two utilities in any log messages. - Facilities are accompanied with a priority or level, which - is used to mark how important a log message is. The most - common will be the warning and - info. Refer to &man.syslog.3; - for a full list of available facilities and - priorities. - - The logging server must be defined in the client's - /etc/syslog.conf. In this instance, - the @ symbol is used to send logging - data to a remote server and would look similar to the - following entry: + The first entry enables + syslogd on boot up. The second entry + prevents logs from being accepted by this client from + other hosts () and increases + the verbosity of logged messages. + + Next, define the logging server in the client's + /etc/syslog.conf. In this example, all + logged facilities are sent to a remote system, denoted by + the @ symbol, + with the specified hostname: *.* @logserv.example.com - Once added, syslogd must be restarted + After saving the edit, restart syslogd for the changes to take effect: &prompt.root; service syslogd restart To test that log messages are being sent across the network, use &man.logger.1; on the client to send a message to - syslogd: + syslogd: - &prompt.root; logger - "Test message from logclient" + &prompt.root; logger "Test message from logclient" This message should now exist both in - /var/log/messages on the client, and + /var/log/messages on the client and /var/log/logclient.log on the log server. @@ -5601,30 +5564,33 @@ syslogd_flags="-s -v -v" Debugging Log Servers - In certain cases, debugging may be required if messages - are not being received on the log server. There are several - reasons this may occur; however, the most common two are - network connection issues and DNS issues. - To test these cases, ensure both hosts are able to reach one - another using the hostname specified in - /etc/rc.conf. If this appears to be - working properly, an alternation to the - syslogd_flags option in - /etc/rc.conf will be required. - - In the following example, - /var/log/logclient.log is empty, and the - /var/log/messages files indicate no - reason for the failure. To increase debugging output, change - the syslogd_flags option to look like the - following example, and issue a restart: + If no messages are + being received on the log server, the cause is most likely a + network connectivity issue, a hostname resolution issue, or a typo in a configuration file. + To isolate the cause, ensure that both the logging server and the logging client are able to ping + each other using the hostname specified in their + /etc/rc.conf. If this fails, check the + network cabling, the firewall ruleset, and the hostname entries + in the DNS server or + /etc/hosts on both the logging server and + clients. Repeat until the ping is + successful from both hosts. + + If the ping succeeds on both hosts but + log messages are still not being received, temporarily + increase logging verbosity to narrow down the configuration + issue. In the following example, + /var/log/logclient.log on the logging server is empty and + /var/log/messages on the logging client does not indicate a + reason for the failure. To increase debugging output, edit the + syslogd_flags entry on the logging server and issue a restart: syslogd_flags="-d -a logclien.example.com -v -v" &prompt.root; service syslogd restart Debugging data similar to the following will flash on the - screen immediately after the restart: + console immediately after the restart: logmsg: pri 56, flags 4, from logserv.example.com, msg syslogd: restart syslogd: restarted @@ -5635,16 +5601,11 @@ cvthname(192.168.1.10) validate: dgram from IP 192.168.1.10, port 514, name logclient.example.com; rejected in rule 0 due to name mismatch. - It appears obvious the messages are being rejected due - to a name mismatch. After reviewing the configuration bit - by bit, it appears a typo in the following - /etc/rc.conf line has an issue: - - syslogd_flags="-d -a logclien.example.com -v -v" - - The line should contain logclient, not - logclien. After the proper alterations - are made, a restart is issued with expected results: + In this example, the log messages are being rejected due to a + typo which results in + a hostname mismatch. The client's hostname should be logclient, not + logclien. Fix the typo, issue + a restart, and verify the results: &prompt.root; service syslogd restart logmsg: pri 56, flags 4, from logserv.example.com, msg syslogd: restart @@ -5668,24 +5629,25 @@ Logging to FILE /var/log/messagesSecurity Considerations As with any network service, security requirements should - be considered before implementing this configuration. At - times, log files may contain sensitive data about services + be considered before implementing a logging server. + Log files may contain sensitive data about services enabled on the local host, user accounts, and configuration data. Network data sent from the client to the server will - not be encrypted nor password protected. If a need for - encryption exists, it might be possible to use + not be encrypted or password protected. If a need for + encryption exists, consider using security/stunnel, which - will transmit data over an encrypted tunnel. + will transmit the logging data over an encrypted tunnel. Local security is also an issue. Log files are not encrypted during use or after log rotation. Local users may - access these files to gain additional insight on system - configuration. In those cases, setting proper permissions - on these files will be critical. The &man.newsyslog.8; - utility supports setting permissions on newly created and + access log files to gain additional insight into system + configuration. Setting proper permissions + on log files is critical. The built-in log rotator, &man.newsyslog.8;, + supports setting permissions on newly created and rotated log files. Setting log files to mode - 600 should prevent any unwanted snooping - by local users. + 600 should prevent unwanted access + by local users. Refer to &man.newsyslog.conf.5; for + additional information. From owner-svn-doc-all@FreeBSD.ORG Sat Feb 1 18:52:00 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 095C5E8A; Sat, 1 Feb 2014 18:52:00 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CE2D414F2; Sat, 1 Feb 2014 18:51:59 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s11IpxdJ016924; Sat, 1 Feb 2014 18:51:59 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s11IpxpT016922; Sat, 1 Feb 2014 18:51:59 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402011851.s11IpxpT016922@svn.freebsd.org> From: Dru Lavigne Date: Sat, 1 Feb 2014 18:51:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43726 - head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 18:52:00 -0000 Author: dru Date: Sat Feb 1 18:51:59 2014 New Revision: 43726 URL: http://svnweb.freebsd.org/changeset/doc/43726 Log: Whitespace fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat Feb 1 18:37:54 2014 (r43725) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat Feb 1 18:51:59 2014 (r43726) @@ -5422,130 +5422,131 @@ driftfile /var/db/ntp.driftInteracting with system logs is a crucial aspect of both security and system administration. Monitoring the log files of - multiple hosts can become unwieldy as the number of systems increases. - Configuring centralized logging can reduce - some of the administrative burden of log file administration. - - Centralized log file aggregation, merging, and rotation can be configured - using &os; native tools, such as - &man.syslogd.8; and &man.newsyslog.8;. This section demonstrates an example + multiple hosts can become unwieldy as the number of systems + increases. Configuring centralized logging can reduce some of + the administrative burden of log file administration. + + Centralized log file aggregation, merging, and rotation can + be configured using &os; native tools, such as &man.syslogd.8; + and &man.newsyslog.8;. This section demonstrates an example configuration, where host A, named logserv.example.com, will collect logging information for the local network. Host B, named logclient.example.com, will be configured to - pass logging information to the logging server. + class="fqdomainname">logclient.example.com, will + be configured to pass logging information to the logging + server. Log Server Configuration - A log server is a system that has been configured to accept logging - information from other hosts. Before configuring a log server, check the following: + A log server is a system that has been configured to + accept logging information from other hosts. Before + configuring a log server, check the following: If there is a firewall between the logging server and - any logging clients, ensure that the firewall ruleset allows UDP - port 514 for both the clients and the - server. + any logging clients, ensure that the firewall ruleset + allows UDP port 514 for both the + clients and the server. - The logging server and all client - machines must have forward and reverse entries in - the local DNS. If the network does not have - a DNS server, create entries in each system's - /etc/hosts. Proper name resolution is required - so that log entries are not rejected by the logging server. + The logging server and all client machines must have + forward and reverse entries in the local + DNS. If the network does not have a + DNS server, create entries in each + system's /etc/hosts. Proper name + resolution is required so that log entries are not + rejected by the logging server. - On the log server, edit + On the log server, edit /etc/syslog.conf to specify the name of - the client to receive log entries from, the logging - facility to be used, and the name of the log to store the - host's log entries. This example adds the hostname of + the client to receive log entries from, the logging facility + to be used, and the name of the log to store the host's log + entries. This example adds the hostname of B, logs all facilities, and stores - the log entries in /var/log/logclient.log. + the log entries in + /var/log/logclient.log. Sample Log Server Configuration - +logclient.example.com + +logclient.example.com *.* /var/log/logclient.log - When adding multiple log clients, add a similar two-line entry - for each client. More information about the available - facilities may be found in - &man.syslog.conf.5;. + When adding multiple log clients, add a similar two-line + entry for each client. More information about the available + facilities may be found in &man.syslog.conf.5;. Next, configure /etc/rc.conf: syslogd_enable="YES" syslogd_flags="-a logclient.example.com -v -v" - The first entry starts - syslogd at system boot. The second - entry allows log entries from the specified client. - The - increases the verbosity of logged messages. This is - useful for tweaking facilities as administrators are - able to see what type of messages are being logged under each - facility. + The first entry starts syslogd + at system boot. The second entry allows log entries from the + specified client. The increases the + verbosity of logged messages. This is useful for tweaking + facilities as administrators are able to see what type of + messages are being logged under each facility. Multiple options may be specified to allow logging from multiple clients. IP addresses and whole netblocks may also be specified. Refer to - &man.syslogd.8; for a full list of possible - options. + &man.syslogd.8; for a full list of possible options. Finally, create the log file: &prompt.root; touch /var/log/logclient.log - At this point, syslogd - should be restarted and verified: + At this point, syslogd should + be restarted and verified: &prompt.root; service syslogd restart &prompt.root; pgrep syslog If a PID is returned, the server - restarted successfully, and client configuration can - begin. If the server did not restart, consult + restarted successfully, and client configuration can begin. + If the server did not restart, consult /var/log/messages for the error. Log Client Configuration - A logging client sends log entries - to a logging server on the network. The client also keeps a local - copy of its own logs. + A logging client sends log entries to a logging server on + the network. The client also keeps a local copy of its own + logs. Once a logging server has been configured, edit - /etc/rc.conf on the logging client: + /etc/rc.conf on the logging + client: syslogd_enable="YES" syslogd_flags="-s -v -v" - The first entry enables - syslogd on boot up. The second entry - prevents logs from being accepted by this client from - other hosts () and increases - the verbosity of logged messages. + The first entry enables syslogd + on boot up. The second entry prevents logs from being + accepted by this client from other hosts () + and increases the verbosity of logged messages. Next, define the logging server in the client's /etc/syslog.conf. In this example, all - logged facilities are sent to a remote system, denoted by - the @ symbol, - with the specified hostname: + logged facilities are sent to a remote system, denoted by the + @ symbol, with the specified + hostname: *.* @logserv.example.com - After saving the edit, restart syslogd - for the changes to take effect: + After saving the edit, restart + syslogd for the changes to take + effect: &prompt.root; service syslogd restart @@ -5557,21 +5558,22 @@ syslogd_flags="-s -v -v"This message should now exist both in /var/log/messages on the client and - /var/log/logclient.log on the - log server. + /var/log/logclient.log on the log + server. Debugging Log Servers - If no messages are - being received on the log server, the cause is most likely a - network connectivity issue, a hostname resolution issue, or a typo in a configuration file. - To isolate the cause, ensure that both the logging server and the logging client are able to ping - each other using the hostname specified in their + If no messages are being received on the log server, the + cause is most likely a network connectivity issue, a hostname + resolution issue, or a typo in a configuration file. To + isolate the cause, ensure that both the logging server and the + logging client are able to ping each other + using the hostname specified in their /etc/rc.conf. If this fails, check the - network cabling, the firewall ruleset, and the hostname entries - in the DNS server or + network cabling, the firewall ruleset, and the hostname + entries in the DNS server or /etc/hosts on both the logging server and clients. Repeat until the ping is successful from both hosts. @@ -5579,11 +5581,13 @@ syslogd_flags="-s -v -v"If the ping succeeds on both hosts but log messages are still not being received, temporarily increase logging verbosity to narrow down the configuration - issue. In the following example, - /var/log/logclient.log on the logging server is empty and - /var/log/messages on the logging client does not indicate a - reason for the failure. To increase debugging output, edit the - syslogd_flags entry on the logging server and issue a restart: + issue. In the following example, + /var/log/logclient.log on the logging + server is empty and /var/log/messages on + the logging client does not indicate a reason for the failure. + To increase debugging output, edit the + syslogd_flags entry on the logging server + and issue a restart: syslogd_flags="-d -a logclien.example.com -v -v" @@ -5601,11 +5605,11 @@ cvthname(192.168.1.10) validate: dgram from IP 192.168.1.10, port 514, name logclient.example.com; rejected in rule 0 due to name mismatch. - In this example, the log messages are being rejected due to a - typo which results in - a hostname mismatch. The client's hostname should be logclient, not - logclien. Fix the typo, issue - a restart, and verify the results: + In this example, the log messages are being rejected due + to a typo which results in a hostname mismatch. The client's + hostname should be logclient, not + logclien. Fix the typo, issue a restart, + and verify the results: &prompt.root; service syslogd restart logmsg: pri 56, flags 4, from logserv.example.com, msg syslogd: restart @@ -5629,25 +5633,23 @@ Logging to FILE /var/log/messagesSecurity Considerations As with any network service, security requirements should - be considered before implementing a logging server. - Log files may contain sensitive data about services - enabled on the local host, user accounts, and configuration - data. Network data sent from the client to the server will - not be encrypted or password protected. If a need for - encryption exists, consider using - security/stunnel, which - will transmit the logging data over an encrypted tunnel. + be considered before implementing a logging server. Log files + may contain sensitive data about services enabled on the local + host, user accounts, and configuration data. Network data + sent from the client to the server will not be encrypted or + password protected. If a need for encryption exists, consider + using security/stunnel, which will transmit + the logging data over an encrypted tunnel. Local security is also an issue. Log files are not encrypted during use or after log rotation. Local users may access log files to gain additional insight into system - configuration. Setting proper permissions - on log files is critical. The built-in log rotator, &man.newsyslog.8;, - supports setting permissions on newly created and - rotated log files. Setting log files to mode - 600 should prevent unwanted access - by local users. Refer to &man.newsyslog.conf.5; for - additional information. + configuration. Setting proper permissions on log files is + critical. The built-in log rotator, &man.newsyslog.8;, + supports setting permissions on newly created and rotated log + files. Setting log files to mode 600 + should prevent unwanted access by local users. Refer to + &man.newsyslog.conf.5; for additional information.