From glen.j.barber at gmail.com  Sun Nov  1 04:00:12 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Sun Nov  1 04:00:18 2009
Subject: docs/140159: [handbook][patch] Chapter 5: GNOME entries in rc.conf
	conflict with FAQ
Message-ID: <200911010359.nA13xJN0015597@www.freebsd.org>


>Number:         140159
>Category:       docs
>Synopsis:       [handbook][patch] Chapter 5: GNOME entries in rc.conf conflict with FAQ
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 01 04:00:11 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Glen Barber
>Release:        FreeBSD 8.0-RC2
>Organization:
>Environment:
FreeBSD orion 8.0-RC2 FreeBSD 8.0-RC2 #20 r198568: Wed Oct 28 20:32:04 EDT 2009     root@orion:/usr/obj/usr/src/sys/ORION  i386
>Description:
rc.conf entries for GNOME in Chapter 5 [1] conflict with GNOME FAQs [2].  The  Handbook states "no further configuration is necessary" which is not true for all users.


[1] - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html
[2] - http://www.freebsd.org/gnome/docs/faq2.html#full-gnome
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- /usr/doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml.orig	2009-10-25 16:56:43.000000000 -0400
+++ /usr/doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml	2009-10-31 23:46:55.000000000 -0400
@@ -1447,9 +1447,12 @@
           disabled by default), can be enabled by adding
           <literal>gdm_enable="YES"</literal> to
           <filename>/etc/rc.conf</filename>.  Once you have rebooted,
-          <application>GNOME</application> will start automatically
-          once you log in &mdash; no further configuration is
-          necessary.</para>
+          <application>GDM</application> will start automatically.</para>
+
+	<para>Additionally, to enable all <application>GNOME</application>
+	  services when <application>GDM</application> starts, add 
+	  <literal>gnome_enable="YES"</literal> to 
+	  <filename>/etc/rc.conf</filename>.</para>
 
         <para><application>GNOME</application> may also be started
 	  from the command-line by properly configuring a file named


>Release-Note:
>Audit-Trail:
>Unformatted:
From ryanjudaswolf at gmail.com  Sun Nov  1 08:31:14 2009
From: ryanjudaswolf at gmail.com (Ryan Wolf)
Date: Sun Nov  1 08:31:22 2009
Subject: Dual Booting Ubuntu Linux & FreeBSD using the new Grub2
Message-ID: <f86423ba0911010106s5621508es2896c52dd89db2ab@mail.gmail.com>

To the Ubuntu & FreeBSD Documentation Folks:

I spent all day trying to figure this out all because there isn't proper
documentation in books or on the internet on it, and no one's documentation
is up to date yet. After I figured it out, thought I would put together a
document so that others won't have to strain as hard as I did just
installing two operating systems that don't talk to each other to well. I
hope Ubuntu decides to have more support for access to BSD partitions, as it
doesn't seem to support it too well at the moment.

Enjoy the document guys. It's my first time writing one, so I hope it helps.

~ Ryan
-------------- next part --------------
31OCT09

* * *

Tutorial on dual booting Ubuntu 9.10 and FreeBSD 7.2-RELEASE
Created by Ryan Judas Wolf
ryanjudaswolf@gmail.com

* * *

Contents:

1. Proper Installation of the two operating systems
2. Discovering the Physical & Logical Drives in Ubuntu
3. Installing the Grub2 Bootloader
4. Configuration of Grub2; Files and Folders
	4.1 grub.cfg (/boot/grub/grub.cfg)
	4.2 grub (/etc/default/grub)
	4.3 /etc/grub.d/ (folder)
5. Adding Entries to Grub 2

* * *

1. Proper Installation of the two operating systems:

You can install the operating systems in any order, which is nice to know for the uninitiated. Just make sure that, when installing FreeBSD, to not install any bootloader and leave it untouched. If you make this mistake, you will have to reinstall FreeBSD at another time. In this case, run the live CD version of Ubuntu, and continue with the process below.

* * *

2. Discovering the Physical & Logical Drives in Ubuntu

A system typically boots from the hard disk at /dev/hda, /dev/sda, /dev/hdb, or /dev/sdb. Bring up a terminal session. The following command [parted] displays a list of the partitions that includes one with a boot flag:

	$ sudo parted /dev/hda print
	Error: Error opening /dev/hda: No medium found
	Retry/cancel? c

	wolf@Tsuhiro-Laptop:/$ sudo parted /dev/sda print
	[sudo] password for wolf: 
	Model: ATA Hitachi HTS54258 (scsi)
	Disk /dev/sda: 80.0GB
	Sector size (logical/physical): 512B/512B
	Partition Table: msdos

	Number  Start   End     Size    Type      File system     Flags
	 1      32.3kB  60.0GB  60.0GB  primary   ext4
 	 2      60.0GB  61.5GB  1497MB  extended
	 5      60.0GB  61.5GB  1497MB  logical   linux-swap(v1)
	 3      61.5GB  80.0GB  18.5GB  primary                   boot

	wolf@Tsuhiro-Laptop:/$ 

In this case, Ubuntu is installed on /dev/sda1, where /sda is the drive, and 1 is the primary partition that is is installed on. FreeBSD is installed on 
/dev/sda3.

* * *

3. Installing the Grub2 Bootloader

The following is to install/reinstall the Master Boot Record. You can take this approach if you installed Ubuntu first, then FreeBSD second on a separate partition on the same harddisk. 

	1. Boot the system using an Ubuntu Live (installation) CD/DVD
	2. Open a terminal emulator window (Menubar: Applications->
	   Accessories->Terminal).
	3. Give the following commands, substituting the name of the device
	   that holds the root partition that you found from the [parted]
	   command (e.g., /dev/sda1) for the example below '/dev/xxx/'. 
	   Substitute the name of the primary drive that you want to install
	   the MBR on (e.g., /dev/sda) for '/dev/yyy'. 
	4. If your linux primary drive is not currently mounted, you will have
	   to mount it with. Do not forget to unmount /mnt when done.
		
		a. If the system does not have a separate 'boot' partition, use
		   these commands:

		$ sudo mount /dev/xxx /mnt
		$ sudo grub-install --root-directory=/mnt /dev/yyy
		Installation finished. No error reported.
		This is the contents of the device map /mnt/boot/grub/device.map.
		Check if this is correct or not. If any of the lines is incorrect,
		fix it an re-run the script 'grub-install'.
		$ cat /boot/grub/device.map
		(hd0)  /dev/sda

	This last line is important to remember. You will be using it when you go to configure your system for use with FreeBSD. Copy it down at this time. Remembering to unmount your physical drive.

		$ sudo umount /mnt

		b. If the system *does* have a separate boot partition, use these commands, substituting the name of the device driver that holds the boot partition (e.g., /dev/sda1) for /dev/zzz:

		$ sudo mount /dev/xxx /mnt
		$ sudo mount /dev/zzz /mnt/boot
		$ sudo grub-install --root-directory=/mnt /dev/yyy
		Installation finished. No error reported.
		This is the contents of the device map /mnt/boot/grub/device.map.
		Check if this is correct or not. If any of the lines is incorrect,
		fix it and re-run the script 'grub-install'.
		$ cat /boot/grub/device.map
		(hd0)   /dev/sda
		$sudo umount /mnt
	
	5. Reboot the system. Remove the CD/DVD when the system asks you to.

	6. Continue to reboot the system of the hard drive you specified in the place of /dev/xxx.

If you ever have problems again, it is easy enough to run:

	$ sudo grub-install /dev/sda

Then make sure it is installed properly:

	$ cat /boot/grub/device.map
	(hd0)   /dev/sda
	
* * *	

4. Configuration of Grub2; Files and Folders:		

There are two locations that need to be known about for the new Grub2 bootloader, which is inconsistent with the original Grub 0.97 bootloader

/boot/grub/	- Main directory holding the Grub2 program
/etc/grub.d/    - Configuration directory for bootloader

While the main grub bootloader file continues to reside in the /boot/grub folder, it is no longer Grub's familiar menu.lst. The main Grub 2 instruction file is now grub.cfg. This file is produced by various scripts run when either the "update-grub" or "update-grub2" command is executed. The files primarily responsible for the content of grub.cfg are /etc/default/grub and individual script files located in /etc/grub.d/

The program name "update-grub2" is provided for compatibility with older versions of the grub2 packaging, but from now on this document will only use the name "update-grub".

Many of the files in /boot/grub will not be familiar to users of Grub Legacy. Especially noticeable are the multitude of *.mod files in the /boot/grub folder. Grub 2 is modular and the *.mod files are loaded as necessary by grub. Despite the addition of these files, the total size of the /boot/grub contents is fairly close to that of Grub Legacy and should not require a larger /boot partition. 

* * *

4.1 grub.cfg (/boot/grub/grub.cfg)

DO NOT EDIT THIS FILE This is the main Grub 2 file. It "replaces" Grub Legacy's /boot/grub/menu.lst. This file contains the Grub menu instructions. Unlike Grub Legacy's menu.lst file, grub.cfg is NOT MEANT TO BE EDITED!!!

    * grub.cfg is automatically generated or updated whenever "update-grub" is executed. The command must be run as root.

    * The scripts used to generate grub.cfg include the files contained in /etc/grub.d and information gathered from /etc/default/grub

    * The file is divided into sections. Each section of the file is clearly delineated and is recognizable by the section header ### BEGIN. The information on this line references the file in the /etc/grub.d folder which is used to incorporate the information into grub.cfg

    * By default, and whenever the "update-grub" command is executed, this file is made read-only. This is in keeping with the intent that the file should not be edited manually. If you must edit this file, instructions are provided later on this page.

    * Sample grub.cfg including two Ubuntu kernels, memtest86+, Windows and a custom entry (41_srcd) imported from an /etc/grub.d/ script: 

      #
      # DO NOT EDIT THIS FILE
      #
      # It is automatically generated by /usr/sbin/update-grub using templates
      # from /etc/grub.d and settings from /etc/default/grub
      #

      ### BEGIN /etc/grub.d/00_header ###
      set default=0
      set timeout=5
      set root=(hd0,5)
      search --fs-uuid --set b02e1934-12dd-418a
      if font /usr/share/grub/ascii.pff ; then
        set gfxmode=640x480
        insmod gfxterm
        insmod vbe
        terminal gfxterm
      fi
      ### END /etc/grub.d/00_header ###

      ### BEGIN /etc/grub.d/05_debian_theme ###
      set menu_color_normal=cyan/blue
      set menu_color_highlight=white/blue
      ### END /etc/grub.d/05_debian_theme ###

      ### BEGIN /etc/grub.d/10_hurd ###
      ### END /etc/grub.d/10_hurd ###

      ### BEGIN /etc/grub.d/10_linux ###
      set root=(hd0,5)
      search --fs-uuid --set b02e1934-12dd-418a-be3a-9ff7d3e7e7ea
      menuentry "Ubuntu, linux 2.6.28-13-generic" {
              linux   /boot/vmlinuz-2.6.28-13-generic root=UUID=b02e1934-12dd-418a ro  quiet splash 			vga800
              initrd  /boot/initrd.img-2.6.28-13-generic
      }
      menuentry "Ubuntu, linux 2.6.28-13-generic (single-user mode)" {
              linux   /boot/vmlinuz-2.6.28-13-generic root=UUID=b02e1934-12dd-418a ro single 
              initrd  /boot/initrd.img-2.6.28-13-generic
      }
      menuentry "Ubuntu, linux 2.6.28-11-generic" {
              linux   /boot/vmlinuz-2.6.28-11-generic root=UUID=b02e1934-12dd-418a ro  quiet splash 			vga800
              initrd  /boot/initrd.img-2.6.28-11-generic
      }
      menuentry "Ubuntu, linux 2.6.28-11-generic (single-user mode)" {
              linux   /boot/vmlinuz-2.6.28-11-generic root=UUID=b02e1934-12dd-418a ro single 
              initrd  /boot/initrd.img-2.6.28-11-generic
      }
      ### END /etc/grub.d/10_linux ###

      ### BEGIN /etc/grub.d/20_memtest86+ ###
      menuentry "Memory test (memtest86+)" {
              linux   /boot/memtest86+.bin
      }
      menuentry "Memory test (memtest86+, serial console 115200)" {
              linux   /boot/memtest86+.bin console=ttyS0,115200n8
      }
      ### END /etc/grub.d/20_memtest86+ ###

      ### BEGIN /etc/grub.d/30_os-prober ###
      menuentry "Microsoft Windows XP Home Edition (on /dev/sda1)" {
              set root=(hd0,1)
              chainloader +1
      }
      ### END /etc/grub.d/30_os-prober ###

      ### BEGIN /etc/grub.d/40_custom ###
      # This file is an example on how to add custom entries

      ### END /etc/grub.d/40_custom ###

      ### BEGIN /etc/grub.d/41_srcd ###
      menuentry "SystemRescue CD on hard drive" {
              set root=(hd0,10)
              linux   /sysrcd/rescuecd subdir=sysrcd setkmap=us
              initrd  /sysrcd/initram.igz
      } 
      ### END /etc/grub.d/41_srcd ###

* * *

4.2 grub (/etc/default/grub)

This file contains information previously found in the upper section of /boot/grub/menu.lst. It contains settings primarily affecting Grub's menu display. This file can be edited by root to make changes to these settings; they will be imported into grub.cfg when "update-grub" is executed.

    

      # If you change this file, run 'update-grub' afterwards to update
      # /boot/grub/grub.cfg.

      GRUB_DEFAULT=0
      GRUB_HIDDEN_TIMEOUT=0
      GRUB_HIDDEN_TIMEOUT_QUIET=true
      GRUB_TIMEOUT=10
      GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
      GRUB_CMDLINE_LINUX=""

      # Uncomment to disable graphical terminal (grub-pc only)
      #GRUB_TERMINAL=console

      # The resolution used on graphical terminal
      # note that you can use only modes which your graphic card supports via VBE
      # you can see them in real GRUB with the command `vbeinfo'
      #GRUB_GFXMODE=640x480

      # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
      #GRUB_DISABLE_LINUX_UUID=true

      # Uncomment to disable generation of recovery mode menu entrys
      #GRUB_DISABLE_LINUX_RECOVERY="true"



      This file contains information formerly contained in the upper section of Grub Legacy's ''menu.lst'' and items contained on the end of the kernel line. The items in this file can be edited by a user with administrator (root) privileges. Grub developers have have placed explanatory comments within the file itself.

    * GRUB_DEFAULT=0

          o Sets the default and pre-selected menu entry. Entries may be numeric or saved

          o    GRUB_DEFAULT=0
                + Sets the default menu entry by menu position. As with Grub Legacy, the first "menuentry" in grub.cfg is 0, the second is 1, etc. 

          o    GRUB_DEFAULT=saved
                + Sets the default menu entry with whatever was selected on the last boot. If the menu is displayed during boot, the previously selected option will be highlighted. If no action is taken, this is selection which will be booted at the end of the timeout, or if the 	menu is hidden. 

    * GRUB_TIMEOUT=5

          o No change from Grub Legacy. This is the number of seconds before the default entry is automatically booted. To have your choice, you probably want to change this to a greater value. Setting a value of -1 will display the menu until the user makes a selection (no timeout). 

    * GRUB_HIDDEN_TIMEOUT=0
          o The menu will be hidden unless a # symbol is present at the beginning of this line. ( # GRUB_HIDDEN_TIMEOUT=0 ). You need to modify this in order to see the bootloader when you turn on your system. That said, put the # in front of it.

          o The default setting initially depends on the presence of other operating systems.
                + Another OS Detected: The menu will be displayed. ( The line will begin with a # symbol. )
                + No other OS Detected: The menu will be hidden. 

          o For integers greater than 0, the system will pause, but not display the menu, for the entered number of seconds.
          o 0 The menu will not be displayed. There will be no delay.
                + When this entry is set to 0:

                      # The user may force displaying the menu as the computer boots by holding down the SHIFT key.
                            * During boot, the system will check the SHIFT key status. If it cannot determine the key status, a short delay will enable the user to display the menu by pressing the ESC key. 

                      # If enabled, the splash screen designated in 05_debian_theme will be displayed even if the hidden menu feature is 				selected. 

    * GRUB_HIDDEN_MENU_QUIET=true
          o true - No countdown is displayed. The screen will be blank.
          o false - A counter will display on a blank screen for the duration of the GRUB_HIDDEN_TIMEOUT value. 

    * GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo Debian
          o Determines the descriptive name in the menu entry. (Ubuntu, Xubuntu, Debian, etc.) 

    * GRUB_CMDLINE_LINUX
          o If it exists, this line imports any entries to the end of the linux command line (Grub Legacy's "kernel" line) for both normal and recovery modes. This is similar to the "altoptions" line in menu.lst 

    * GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
          o This line imports any entries to the end of the 'linux' line (Grub Legacy's "kernel" line). The entries are appended to the end of the normal mode only. This is similar to the "defoptions" line in menu.lst.  If you want a black screen with scrolling boot messages, remove "quiet splash". If you want a grub splash screen with limited messages underneath the Ubuntu logo, use only "splash". 
	  	  < This [only "splash"] will not work in Karmic during boot as the xsplash does not display the messages , but the messages at shutdown will be displayed. 

    * #GRUB_TERMINAL=console
          o Uncomment to disable graphical terminal (grub-pc only). 

    * #GRUB_DISABLE_LINUX_UUID=true
          o Uncomment this line if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux. 

    * GRUB_DISABLE_LINUX_RECOVERY=true
          o Add or uncomment this line to prevent "Recovery" mode kernel options from appearing in the menu. 

    * GRUB_DISABLE_OS_PROBER=true
          o Enables/disables the os-prober check of other partitions for operating systems, including Windows, Linux, OSX and Hurd. 

This is an example of what your file should look like after modified:

	# If you change this file, run 'update-grub' afterwards to update
	# /boot/grub/grub.cfg.

	GRUB_DEFAULT=0
	#GRUB_HIDDEN_TIMEOUT=10
	GRUB_HIDDEN_TIMEOUT_QUIET=false
	GRUB_TIMEOUT="10"
	GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
	GRUB_CMDLINE_LINUX_DEFAULT="splash"
	GRUB_CMDLINE_LINUX=""

	# Uncomment to disable graphical terminal (grub-pc only)
	#GRUB_TERMINAL=console

	# The resolution used on graphical terminal
	# note that you can use only modes which your graphic card supports via VBE
	# you can see them in real GRUB with the command `vbeinfo'
	GRUB_GFXMODE=1280x800

	# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
	#GRUB_DISABLE_LINUX_UUID=true

	# Uncomment to disable generation of recovery mode menu entrys
	#GRUB_DISABLE_LINUX_RECOVERY="true"

PLEASE NOTE: If you want to change the resolution of your menu, make sure that you know the proper resolutions that your computer can run at before modifying. If you are unsure, even in the slightest, leave the defaults at 640x480

* * *

4.3 /etc/grub.d/ (folder)

The files in this folder are read during execution of '"update-grub"'command. The scripts in these files export the information they gather into /boot/grub/grub.cfg. The files are run in sequential order - files with names starting with a numeral are run first, followed by files whose name begins with a letter. The order the file is run determines the location of items in the grub menu.

Custom entries can be added to the 40_custom file or placed in a new file.

Any file created must be executable in order to be included in the grub.cfg file during the "update-grub" command. This can be accomplished from the terminal with "sudo chmod u+x /etc/grub.d/filename". The following is a very brief look at what the files accomplish.

    * 00_header
          o Loads settings from /etc/default/grub, including visual presentations, 		    timeout, and terminal options. 
    * 05_debian_theme
          o Sets background, text colors, and themes. 
    * 10_hurd
          o Locates hurd kernels. 
    * 10_linux
          o Locates kernels based on the distributor determined by the "lsb_release 		    -i -s" results ("Ubuntu"). 
    * 20_memtest86+
          o If the file /boot/memtest86+.bin exists, it is included as a menu item. 
    * 30_os-prober
          o Searches for other OS's and includes them in the menu. 
    * 40_custom
          o A template for adding custom menu entries which will be inserted into grub.cfg upon execution of the "update-grub" command. This and any other custom files must be made executable to allow importation into grub.cfg. These files are placed in the Grub menu in the numerical order of the file name. 

* * *

5. Adding Entries to Grub 2

grub.cfg is updated when update-grub is run. Changes to grub.cfg should be made to the appropriate script files and not to the grub.cfg file itself.

NOTE: The first comment in grub.cfg is "DO NOT EDIT THIS FILE". The file is read-only and is returned to this status anytime update-grub is run. 

The file that you need to modify is in the /etc/grub.d folder. In your favorite editor, edit 40_custom and include the following information into it:

	#!/bin/sh
	exec tail -n +3 $0
	# This file provides an easy way to add custom menu entries.  Simply type the
	# menu entries you want to add after this comment.  Be careful not to change
	# the 'exec tail' line above.
	menuentry "FreeBSD 7.2-RELEASE i386" {
      	  set root=(hd0,3)
      	  chainloader +1
	}

Make sure to leave no spaces in the document, and copying the information thereafter 'menuentry' verbatim to the document. Make sure that your installation of FreeBSD is installed onto onto the proper drive (if that is hd0, make it so), and that the correct partition is designated (found from the [parter] command at the beginning of this document).

Once this is done, upgrade Grub2:

	wolf@Tsuhiro-Laptop:/$ sudo update-grub
	Generating grub.cfg ...
	Found linux image: /boot/vmlinuz-2.6.31-14-generic
	Found initrd image: /boot/initrd.img-2.6.31-14-generic
	Found memtest86+ image: /boot/memtest86+.bin
	done
	wolf@Tsuhiro-Laptop:/$ 

Your new amendment may or may not be recognized. So far, the os-probe that is with Grub2 does not recognize FreeBSD partitions. If you want to confirm that it is now in your grub.cfg file, just [cat] it to make sure, looking for the '40_custom' at the bottom for it. When you reboot, you should see the option for FreeBSD as you typed it. 

* * *

Enjoy your new dualboot system! If you have any questions, feel free to email me at ryanjudaswolf@gmail.com

Bibliography:
A Practical Guide to Ubuntu Linux, Mark G. Sobell p.430, 574
https://wiki.ubuntu.com/Grub2#User-defined%20Entries 

* * *


From brueffer at FreeBSD.org  Sun Nov  1 11:40:41 2009
From: brueffer at FreeBSD.org (brueffer@FreeBSD.org)
Date: Sun Nov  1 11:40:48 2009
Subject: docs/139605: [patch] Add basic examples to usbconfig(8)
Message-ID: <200911011140.nA1BefaZ084803@freefall.freebsd.org>

Synopsis: [patch] Add basic examples to usbconfig(8)

State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Sun Nov 1 12:39:14 CET 2009
State-Changed-Why: 
I've committed a slightly different version, as some of the
information was really missing from the DESCRIPTION section.
Thanks!


Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Sun Nov 1 12:39:14 CET 2009
Responsible-Changed-Why: 
MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=139605
From info at rickvanderzwet.nl  Sun Nov  1 15:38:40 2009
From: info at rickvanderzwet.nl (Rick van der Zwet)
Date: Sun Nov  1 15:38:47 2009
Subject: FYI: handbook style trac wiki plugin
Message-ID: <5aaae08a0911010717v4bc28628s2778be40c8b7fc8f@mail.gmail.com>

I really like the great style of the FreeBSD handbook/article pages,
but having quite some difficulties with the format.
Docbook is not so friendly to setup on an non FreeBSD machine for example :-)

So I hacked around a bit with the trac wiki
(http://trac.edgewall.org/) and created a plugin which mimics the
behavior of the handbook (for a very small bit):

    https://trac-hacks.org/wiki/FreeDocPlugin#example1

Of course not all features are included. If you like the idea and like
something included as well, let me know.

/Rick
-- 
http://rickvanderzwet.nl
From rocket2dmn at ubuntu.com  Sun Nov  1 21:11:27 2009
From: rocket2dmn at ubuntu.com (Connor Imes)
Date: Sun Nov  1 21:11:34 2009
Subject: Dual Booting Ubuntu Linux & FreeBSD using the new Grub2
In-Reply-To: <f86423ba0911010106s5621508es2896c52dd89db2ab@mail.gmail.com>
References: <f86423ba0911010106s5621508es2896c52dd89db2ab@mail.gmail.com>
Message-ID: <4AEDF42F.1050009@ubuntu.com>

Ryan Wolf wrote:
> To the Ubuntu & FreeBSD Documentation Folks:
>
> I spent all day trying to figure this out all because there isn't
> proper documentation in books or on the internet on it, and no one's
> documentation is up to date yet. After I figured it out, thought I
> would put together a document so that others won't have to strain as
> hard as I did just installing two operating systems that don't talk to
> each other to well. I hope Ubuntu decides to have more support for
> access to BSD partitions, as it doesn't seem to support it too well at
> the moment.
>
> Enjoy the document guys. It's my first time writing one, so I hope it
> helps.
>
> ~ Ryan
That is a nice looking document, Ryan.  One of the Ubuntu Documentation
contributors, drs305, has written (and been updating) a wiki page on
Grub2, which you can find here [1].  It is geared toward Ubuntu users
who have Grub2 installed from Ubuntu, but a lot of the basics should be
applicable to FreeBSD as well.  You are welcome to expand on the wiki
page, or if you host your guide on a FreeBSD site, please let us know. 
I don't believe the existing wiki page outlines multibooting in much
detail yet, so your knowledge in this field would be very helpful.

[1] https://help.ubuntu.com/community/Grub2

Cheers,
-Connor
From unixmania at gmail.com  Sun Nov  1 23:22:20 2009
From: unixmania at gmail.com (Carlos A. M. dos Santos)
Date: Sun Nov  1 23:22:27 2009
Subject: Dual Booting Ubuntu Linux & FreeBSD using the new Grub2
In-Reply-To: <4AEDF42F.1050009@ubuntu.com>
References: <f86423ba0911010106s5621508es2896c52dd89db2ab@mail.gmail.com>
	<4AEDF42F.1050009@ubuntu.com>
Message-ID: <e71790db0911011458q19a88454o79874af954578a65@mail.gmail.com>

On Sun, Nov 1, 2009 at 6:48 PM, Connor Imes <rocket2dmn@ubuntu.com> wrote:
> Ryan Wolf wrote:
>> To the Ubuntu & FreeBSD Documentation Folks:
>>
>> I spent all day trying to figure this out all because there isn't
>> proper documentation in books or on the internet on it, and no one's
>> documentation is up to date yet. After I figured it out, thought I
>> would put together a document so that others won't have to strain as
>> hard as I did just installing two operating systems that don't talk to
>> each other to well. I hope Ubuntu decides to have more support for
>> access to BSD partitions, as it doesn't seem to support it too well at
>> the moment.
>>
>> Enjoy the document guys. It's my first time writing one, so I hope it
>> helps.
>>
>> ~ Ryan
> That is a nice looking document, Ryan. ?One of the Ubuntu Documentation
> contributors, drs305, has written (and been updating) a wiki page on
> Grub2, which you can find here [1]. ?It is geared toward Ubuntu users
> who have Grub2 installed from Ubuntu, but a lot of the basics should be
> applicable to FreeBSD as well. ?You are welcome to expand on the wiki
> page, or if you host your guide on a FreeBSD site, please let us know.
> I don't believe the existing wiki page outlines multibooting in much
> detail yet, so your knowledge in this field would be very helpful.
>
> [1] https://help.ubuntu.com/community/Grub2

I'm 4-booting Ubuntu 9.04, FreeBSD 7, 8 and -CURRENT using GRUB. I had
to apply the following patch to grub2-1.96+20080512 in order to make
it pass the correct info to the FreeBSD loader because I'm using a
GPT-partitioned disk, with 17 partitions:

--- loader/i386/bsd.c.orig	2008-02-19 13:40:45.000000000 -0300
+++ loader/i386/bsd.c	2009-02-01 21:20:59.000000000 -0200
@@ -101,6 +101,8 @@

 	  if ((p[0] >= 'a') && (p[0] <= 'z'))
 	    *part = p[0] - 'a';
+	  else
+	    *part = 0xff;
 	}
     }
 }

FreeBSD boot partitions are 2, 5, 8. I created the following
"/etc/grub.d/10_freebsd" file, so "update-grub" does not remove
FreeBSD from the boot menu.

#!/bin/sh -e
cat << EOF
menuentry "FreeBSD 7-STABLE AMD64" {
	set root=(hd0,5)
	freebsd /boot/loader
}
menuentry "FreeBSD 8-STABLE AMD64" {
	set root=(hd0,8)
	freebsd /boot/loader
}
menuentry "FreeBSD 9-CURRENT AMD64" {
	set root=(hd0,2)
	freebsd /boot/loader
}
EOF

Then I created a "/etc/grub.d/01_casantos" file, to unset the defult
OS and timeout:

#!/bin/sh -e
cat << EOF
unset default
unset timeout
EOF


-- 
My preferred quotation of Robert Louis Stevenson is "You cannot
make an omelette without breaking eggs". Not because I like the
omelettes, but because I like the sound of eggs being broken.
From bugmaster at FreeBSD.org  Mon Nov  2 11:06:06 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov  2 11:06:38 2009
Subject: Current unassigned doc problem reports
Message-ID: <200911021106.nA2B668i032903@freefall.freebsd.org>

(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .)

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/140159  doc        [handbook][patch] Chapter 5: GNOME entries in rc.conf 
o docs/140082  doc        handbook/jails: russian translation is missing
o docs/140075  doc        release notes: missing word "NOT", which changes all t
o docs/140014  doc        [patch] articles/gjournal-desktop: russian translation
o docs/139705  doc        [patch] tunefs(8) man page bugs section ambiguous on a
o docs/139682  doc        [PATCH] dialog(1) man page does not mention radiolist 
o docs/139603  doc        [patch] Clarify subpixel smoothing for fonts in Handbo
p docs/139370  doc        [PATCH] de(4) manual page typo
o docs/139336  doc        ZFS documentation suggestion
o docs/139165  doc        gssapi.3 man page out of sync with between crypto and 
o docs/139153  doc        the hier(7) man page needs to be updated
o docs/139018  doc        translation of submitting.sgml from docproj/submitting
o docs/138887  doc        manpage ports(7) incorrect
o docs/138845  doc        Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138663  doc        system(3) man page confuses users about "return value 
o docs/138485  doc        bpf(4) and ip(4) man pages missing important corner ca
o docs/138206  doc        [patch] ntp(1): not enabled function, and false manual
o docs/137762  doc        [handbook] proposed: mention "make delete-old" in sec 
o docs/137171  doc        [patch] replacement of k8temp(4) by amdtemp(4) isn't r
o docs/136918  doc        [patch] grammar fixes to locking.9
o docs/136712  doc        [handbook] [patch] draft new section on gmirror per pa
o docs/136666  doc        [handbook] Configure serial port for remote kernel deb
o docs/136100  doc        change FreeBSD Ports distfiles survey's url to portsco
o docs/136035  doc        ftpchroot(5) omits an important option
p docs/136029  doc        MALLOC_PRODUCTION knob should be mentioned somewhere, 
o docs/135999  doc        Netgear GS105v3 should be added to list of switches th
o docs/135676  doc        FAQ About The FreeBSD Mailing Lists doesn't mention ma
o docs/135516  doc        pax(1) manual not mentioning chflags unawareness
o docs/135475  doc        [patch] jot(1) manpage and behaviour differ
o docs/135165  doc        [patch] make(1) fixes: punctuation, typos, tweaks
o docs/134376  doc        pthread(3): pthread manpages don't mention that PTHREA
o docs/134226  doc        /usr/share/examples/ftpd/ftpd.conf does not exist.
o docs/134222  doc        installation failure of japanese docs
o docs/134123  doc        The RUNQUEUE(9) man page is out of date
o docs/134074  doc        [patch] locking.9 man page slight enhancements
o docs/133567  doc        [patch] doc/Makefile switch to csup
o docs/133245  doc        french handbook 27.3.5 amd.map amd.conf
o docs/133228  doc        handbook 23.3.5 screenmap section is confusing
o docs/133186  doc        [patch] powerd(8) man page errors
o docs/133118  doc        [patch] Error in getopt (1) manual EXAMPLES section
o docs/132959  doc        [patch] description mismatches on xterm/termcap, fortu
o docs/132884  doc        [request] No manpage for SYSINIT and SYSUNINIT
o docs/132839  doc        [patch] Fix example script in ldap-auth article
o docs/132718  doc        [handbook] Information about adding a new mirror is ou
o docs/132311  doc        [patch] man5/nsmb.conf.5
o docs/132260  doc        dhcpd(8) pid not stored in documented location
o docs/132190  doc        EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/132113  doc        [handbook] Update handbook jails creation
o docs/131918  doc        [patch] Fixes for the BPF(4) man page
o docs/131684  doc        [patch] articles/linux-comparison: replace Addenda by 
o docs/131590  doc        [patch] whitespace-only change of developers-handbook/
o docs/130895  doc        [patch] No man page installed for padlock(4) on amd64 
o docs/130364  doc        Man page for top needs explanation of CPU states
o docs/130238  doc        nfs.lockd man page doesn't mention NFSLOCKD option or 
o docs/129671  doc        New TCP chapter for Developer's Handbook (from rwatson
o docs/129095  doc        ipfw(8): Can not check that packet originating/destine
o docs/128524  doc        No geom documentation for loading gjournal(8)
o docs/128356  doc        [request] add Firefox plugin for FreeBSD manual pages
o docs/127908  doc        [patch] readdir(3) error documentation
s docs/127844  doc        Example code skeleton_capture_n.c in meteor(4) manpage
o docs/126590  doc        [patch] Write routine called forever in Sample Echo Ps
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
f docs/122052  doc        minor update on handbook section 20.7.1
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o bin/121424   doc        [patch] [ipfw] Rectify ambiguous English in manual
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
a docs/119536  doc        a few typos in French handbook (basics)
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118214  doc        close(2) error returns incomplete
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/117747  doc        'break' system call needs a man page
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/116116  doc        mktemp (3) re/move note
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111147  doc        hostapd.conf is not documented
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110061  doc        [patch] tuning(7) missing reference to vfs.read_max
o docs/109981  doc        No manual entry for post-grohtml
o docs/109977  doc        No manual entry for ksu
o docs/109973  doc        No manual entry for c++filt
o docs/109972  doc        No manual entry for zless/bzless
f docs/109226  doc        [request] No manual entry for sntp
o docs/109201  doc        [request]: manual for callbootd
a docs/108980  doc        list of missing man pages
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/105608  doc        fdc(4) debugging description staled
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/91174   doc        [REQUEST] Handbook: Addition of Oracle 9i installation
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84271   doc        [patch] compress(1) doesn't warn about nasty link hand
o docs/83820   doc        getino(3) manpage not installed
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
o docs/63570   doc        [patch] Language cleanup for the Handbook's DNS sectio
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
o docs/53596   doc        Updates to mt(1) manual page
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/50211   doc        [patch] doc.docbook.mk: fix textfile creation
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/43823   doc        [patch] update to environ(7) manpage
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/38556   doc        EPS file of beastie, as addition to existing examples
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
a docs/30008   doc        [patch] French softupdates document should be translat
o docs/27605   doc        [patch] Cross-document references (<olink>)
o docs/26286   doc        *printf(3) etc should gain format string warnings
o docs/24786   doc        missing FILES descriptions in sa(4)
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc

162 problems total.

From remko at FreeBSD.org  Mon Nov  2 14:17:48 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Mon Nov  2 14:17:55 2009
Subject: docs/128356: [request] add Firefox plugin for FreeBSD manual
	pages
Message-ID: <200911021417.nA2EHmTJ003114@freefall.freebsd.org>

Synopsis: [request] add Firefox plugin for FreeBSD manual pages

State-Changed-From-To: open->suspended
State-Changed-By: remko
State-Changed-When: Mon Nov 2 14:17:08 UTC 2009
State-Changed-Why: 
It has been almost a year, without visible information. I'll
suspend the ticket till someone can update the patch to make
it possible to search a online summary.

http://www.freebsd.org/cgi/query-pr.cgi?pr=128356
From info at rickvanderzwet.nl  Mon Nov  2 18:20:09 2009
From: info at rickvanderzwet.nl (Rick van der Zwet)
Date: Mon Nov  2 18:20:16 2009
Subject: FYI: handbook style trac wiki plugin
In-Reply-To: <20091102180649.GC34619@eggman.experts-exchange.com>
References: <5aaae08a0911010717v4bc28628s2778be40c8b7fc8f@mail.gmail.com>
	<20091102180649.GC34619@eggman.experts-exchange.com>
Message-ID: <5aaae08a0911021020w596f7205o4dc055f316e3e495@mail.gmail.com>

2009/11/2 Jason <jhelfman@e-e.com>:
> On Sun, Nov 01, 2009 at 04:17:38PM +0100, Rick van der Zwet thus spake:
>> I really like the great style of the FreeBSD handbook/article pages,
....
>> Docbook is not so friendly to setup on an non FreeBSD machine for example
>> :-)
>
> In following the "Quick Setup," I really had no issues.
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html

Indeed on a BSD system I also got a running in a breeze :-) But try
for example to get it working under mac or linux and you end up in
places where-all-bits-are-black ;-)

/Rick

-- 
http://rickvanderzwet.nl
From jhelfman at e-e.com  Mon Nov  2 18:45:11 2009
From: jhelfman at e-e.com (Jason)
Date: Mon Nov  2 18:46:08 2009
Subject: FYI: handbook style trac wiki plugin
In-Reply-To: <5aaae08a0911010717v4bc28628s2778be40c8b7fc8f@mail.gmail.com>
References: <5aaae08a0911010717v4bc28628s2778be40c8b7fc8f@mail.gmail.com>
Message-ID: <20091102180649.GC34619@eggman.experts-exchange.com>

On Sun, Nov 01, 2009 at 04:17:38PM +0100, Rick van der Zwet thus spake:
>I really like the great style of the FreeBSD handbook/article pages,
>but having quite some difficulties with the format.

I didn't have any such issues, and hope you success in future with FreeBSD format.

>Docbook is not so friendly to setup on an non FreeBSD machine for example :-)

In following the "Quick Setup," I really had no issues. 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html

>
>So I hacked around a bit with the trac wiki
>(http://trac.edgewall.org/) and created a plugin which mimics the
>behavior of the handbook (for a very small bit):
>
>    https://trac-hacks.org/wiki/FreeDocPlugin#example1
>
>Of course not all features are included. If you like the idea and like
>something included as well, let me know.

Interesting idea, however this really sidesteps everything about standards,
so I am not certain how much this idea will be embraced.
  
>
>/Rick
>--
>http://rickvanderzwet.nl
>_______________________________________________
>freebsd-doc@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-doc
>To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"
>
From sales at c2it-hardware.co.za  Fri Nov  6 20:06:00 2009
From: sales at c2it-hardware.co.za (C2IT Computer Hardware)
Date: Fri Nov  6 20:07:04 2009
Subject: New Arrival of REFURBISHED and NEW Computers & Laptops
Message-ID: <20091106120552.118049531@telkomsa.net>


From remko at FreeBSD.org  Sat Nov  7 11:42:04 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sat Nov  7 11:42:10 2009
Subject: docs/140159: [handbook][patch] Chapter 5: GNOME entries in
	rc.conf conflict with FAQ
Message-ID: <200911071142.nA7Bg2JC054686@freefall.freebsd.org>

Synopsis: [handbook][patch] Chapter 5: GNOME entries in rc.conf conflict with FAQ

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Sat Nov 7 11:42:02 UTC 2009
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=140159
From remko at FreeBSD.org  Sat Nov  7 11:42:40 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sat Nov  7 11:42:46 2009
Subject: docs/139705: [patch] tunefs(8) man page bugs section ambiguous
	on active filesystems
Message-ID: <200911071142.nA7Bgecp054774@freefall.freebsd.org>

Synopsis: [patch] tunefs(8) man page bugs section ambiguous on active filesystems

Responsible-Changed-From-To: freebsd-doc->remko
Responsible-Changed-By: remko
Responsible-Changed-When: Sat Nov 7 11:42:39 UTC 2009
Responsible-Changed-Why: 
This is incorrect after receiving feedback. Take the PR so that I can
resolve that.

http://www.freebsd.org/cgi/query-pr.cgi?pr=139705
From dfilter at FreeBSD.ORG  Sat Nov  7 11:50:03 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sat Nov  7 11:50:09 2009
Subject: docs/140159: commit references a PR
Message-ID: <200911071150.nA7Bo2Rc054905@freefall.freebsd.org>

The following reply was made to PR docs/140159; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/140159: commit references a PR
Date: Sat,  7 Nov 2009 11:41:48 +0000 (UTC)

 remko       2009-11-07 11:41:31 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en_US.ISO8859-1/books/handbook/x11 chapter.sgml 
   Log:
   Add some more information about starting GNOME services.
   
   PR:             docs/140159
   Submitted by:   Glen Barber <glen dot j dot barber at gmail dot com>
   Facilitated by: Snow B.V.
   
   Revision  Changes    Path
   1.196     +6 -3      doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
From gabor at FreeBSD.org  Sat Nov  7 16:56:46 2009
From: gabor at FreeBSD.org (gabor@FreeBSD.org)
Date: Sat Nov  7 16:56:52 2009
Subject: docs/140014: [patch] articles/gjournal-desktop: russian
	translation is missing
Message-ID: <200911071656.nA7GujCd027243@freefall.freebsd.org>

Synopsis: [patch] articles/gjournal-desktop: russian translation is missing

State-Changed-From-To: open->closed
State-Changed-By: gabor
State-Changed-When: Sat Nov 7 16:55:43 UTC 2009
State-Changed-Why: 
Committed, thanks.


Responsible-Changed-From-To: freebsd-doc->gabor
Responsible-Changed-By: gabor
Responsible-Changed-When: Sat Nov 7 16:55:43 UTC 2009
Responsible-Changed-Why: 
Committed, thanks.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140014
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Sun Nov  8 00:20:01 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Sun Nov  8 00:20:09 2009
Subject: docs/140375: [UPDATE] Updated zh_TW.Big5/articles/nanobsd
Message-ID: <20091108001643.B8DCB6FC443@mx.hs.ntnu.edu.tw>


>Number:         140375
>Category:       docs
>Synopsis:       [UPDATE] Updated zh_TW.Big5/articles/nanobsd
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 08 00:20:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Denny Lin
>Release:        FreeBSD 7.2-RELEASE-p4 amd64
>Organization:
>Environment:
System: FreeBSD cnmc32.hs.ntnu.edu.tw 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Mon Oct 26 19:41:45 CST 2009 root@cnmc32.hs.ntnu.edu.tw:/usr/obj/usr/src/sys/CNMC32 amd64


	
>Description:
An update of zh_TW.Big5/articles/nanobsd.

Changes that were made:
1. Merged changes from the English version (revision 1.4, 1.5).
2. Added section on how to install packages for a NanoBSD image (translated from the English version).
3. All the parentheses were changed to full width characters. This was done because all the other punctuation marks are full width characters (commas, periods, etc.).
4. Some other changes in the text.
	
>How-To-Repeat:
	
>Fix:
See patches. The updated files are also available at:
http://security-hole.info/~dennylin93/patches/
http://security-hole.info/~dennylin93/doc/zh_TW.Big5/articles/nanobsd/

	

--- nanobsd-Makefile.patch begins here ---
--- doc/zh_TW.Big5/articles/nanobsd/Makefile.orig	2009-11-07 22:30:58.000000000 +0800
+++ doc/zh_TW.Big5/articles/nanobsd/Makefile	2009-11-07 22:31:21.000000000 +0800
@@ -1,7 +1,4 @@
 # 
-# The FreeBSD Traditional Chinese Project
-#
-# Original Revision: 1.2
 # $FreeBSD: doc/zh_TW.Big5/articles/nanobsd/Makefile,v 1.1 2006/07/09 14:03:00 vanilla Exp $
 #
 # Article: Introduction to NanoBSD
--- nanobsd-Makefile.patch ends here ---

--- nanobsd-article.sgml.patch begins here ---
--- doc/zh_TW.Big5/articles/nanobsd/article.sgml.orig	2009-11-07 17:03:57.000000000 +0800
+++ doc/zh_TW.Big5/articles/nanobsd/article.sgml	2009-11-07 23:39:14.000000000 +0800
@@ -1,9 +1,3 @@
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD Chinese (Traditional) Documentation Project
-
-     Original Revision: 1.1
--->
 <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
 <!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
 %articles.ent;
@@ -36,7 +30,7 @@
     <abstract>
       <para>這篇文件提供了關於 <application>NanoBSD</application> 工具的情報介紹，
 	這工具可用來建立用於嵌入式環境應用程式的 &os; 系統映像檔，
-	以便存放到 Compact Flash 卡(或隨身碟)。</para>
+	以便存放到 Compact Flash 卡（或其他儲存裝置）。</para>
     </abstract>
   </articleinfo>
 
@@ -47,13 +41,13 @@
 
     <para><application>NanoBSD</application> 是 &a.phk; 目前正在開發的一項工具。
       它可用來建立用於嵌入式環境應用程式的 &os; 系統映像檔，
-      以便存放到 Compact Flash 卡(或隨身碟，mass storage medium)。</para>
+      以便存放到 Compact Flash 卡（或其他儲存裝置）。</para>
 
     <para>這一工具也可以用來自製安裝映像檔，
-      以簡化俗稱為 <quote>嵌入式系統(computer appliances)</quote> 的系統安裝、維護工作。 
+      以簡化俗稱為 <quote>嵌入式系統（computer appliances）</quote> 的系統安裝、維護工作。
       通常，每個嵌入式系統產品都有限定硬體和軟體，
       或者換言之，所有的應用程式都是預先裝好的。
-      這些設備可以直接放到現有的網路中，而且(幾乎是)立即使用。</para>
+      這些設備可以直接放到現有的網路中，而且（幾乎是）立即使用。</para>
 
     <para><application>NanoBSD</application> 提供的功能包括：</para>
 
@@ -89,8 +83,8 @@
     <sect2 id="design">
       <title>NanoBSD 的設計</title>
 
-      <para>一旦將映像檔存入嵌入式硬體，就可以用它來引導 <application>NanoBSD</application>
-	了。 預設情況下，隨身碟會劃分為三部分：</para>
+      <para>一旦將映像檔存入嵌入式硬體，就可以用 <application>NanoBSD</application>
+        開機。預設情況下，儲存裝置會劃分為三部分：</para>
 
       <itemizedlist>
 	<listitem>
@@ -100,22 +94,23 @@
 
 	<listitem>
 	  <para>一個設定檔分割區，在運行環境中，
-	    可以將其掛載(mount)到 <filename role="directory">/cfg</filename> 目錄下。</para>
+	    可以將其掛載（mount）到 <filename class="directory">/cfg</filename> 目錄
+	    下。</para>
 	</listitem>
       </itemizedlist>
 
       <para>這些分割區，在預設情況下是以唯讀方式掛載。</para>
 
-      <para><filename role="directory">/etc</filename> 和
-	<filename role="directory">/var</filename> 目錄均為
-	&man.md.4;(malloc)磁碟。</para>
+      <para><filename class="directory">/etc</filename> 和
+	<filename class="directory">/var</filename> 目錄均為
+	&man.md.4;（malloc）磁碟。</para>
 
       <para>設定檔的分割區則是在
-	<filename role="directory">/cfg</filename> 目錄。
-	它包含了用於 <filename role="directory">/etc</filename>
-	目錄的檔案，在啟動之後暫時以唯讀方式掛載。 因此，若想要重開機保留新的設定，
-	那麼要記得從 <filename role="directory">/etc</filename> 把改過的檔案複製回
-	<filename role="directory">/cfg</filename> 目錄才行。</para>
+	<filename class="directory">/cfg</filename> 目錄。
+	它包含了 <filename class="directory">/etc</filename>
+	目錄的檔案，在啟動之後暫時以唯讀方式掛載。因此，若想要重開機後保留新的設定，
+	那麼要記得把改過的檔案從 <filename class="directory">/etc</filename> 複製回
+	<filename class="directory">/cfg</filename> 目錄才行。</para>
 
       <example>
 	<title>把修改過 <filename>/etc/resolv.conf</filename> 設定保存起來</title>
@@ -129,12 +124,12 @@
 
       <note>
 	<para>只有在系統啟動過程中，以及需要修改設定檔的時候，才需要掛載含有
-	  <filename role="directory">/cfg</filename> 的那個分割區。</para>
+	  <filename class="directory">/cfg</filename> 的分割區。</para>
 
-	<para>一直都掛載 <filename role="directory">/cfg</filename>
+	<para>一直掛載 <filename class="directory">/cfg</filename>
 	  不是一個好主意，特別是當您把 <application>NanoBSD</application>
-	  放在不適合進行大量寫入動作的分割區時
-	 (比如：由於檔案系統的同步化會定期在系統碟內寫入資料)。</para>
+	  放在不適合進行大量寫入動作的儲存裝置時
+	 （比如：由於檔案系統的同步化會定期在系統碟內寫入資料）。</para>
       </note>
     </sect2>
 
@@ -143,8 +138,8 @@
 
       <para><application>NanoBSD</application> 映像檔是透過使用非常簡單的
 	<filename>nanobsd.sh</filename> shell  script 來打造的，這個 script 可以在
-	<filename role="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename>
-	目錄中找到。 這個 script 建立的映像檔，可以用 &man.dd.1; 工具來複製到隨身碟上。</para>
+	<filename class="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename>
+	目錄中找到。這個 script 建立的映像檔，可以用 &man.dd.1; 工具來複製到隨身碟上。</para>
 
       <para>打造
 	<application>NanoBSD</application> 映像檔所需的指令是：</para>
@@ -168,7 +163,7 @@
 	</callout>
 
 	<callout arearefs="nbsd-dd">
-	  <para>在隨身碟上安裝 <application>NanoBSD</application>。</para>
+	  <para>將 <application>NanoBSD</application> 安裝到儲存裝置上。</para>
 	</callout>
       </calloutlist>
     </sect2>
@@ -177,16 +172,16 @@
       <title>自行打造 NanoBSD 映像檔</title>
 
       <para>這可能是 <application>NanoBSD</application> 最為重要，
-	同時也是您最感興趣的功能。 同時，在開發
-	<application>NanoBSD</application> 應用程式時，這也是相當耗時的過程。</para>
+	同時也是您最感興趣的功能。同時，在開發
+	<application>NanoBSD</application> 時，這也最耗時間的過程之一。</para>
 
-      <para>執行下面的指令將會
-	<filename>nanobsd.sh</filename> 讀取目前所在目錄的
+      <para>執行下面的指令會使
+	<filename>nanobsd.sh</filename> 目前所在的目錄讀取
 	<filename>myconf.nano</filename> 檔的設定：</para>
 
       <screen>&prompt.root; <userinput>sh nanobsd.sh -c myconf.nano</userinput></screen>
 
-      <para>自行打造的流程，只需兩個步驟：</para>
+      <para>自行打造的流程，有兩種方式：</para>
 
       <itemizedlist>
 	<listitem>
@@ -202,42 +197,45 @@
 	<title>自訂選項</title>
 
         <para>透過修改設定，可以設定用於
-          <application>NanoBSD</application> 打造過程中 <literal>buildworld</literal>
-          和 <literal>installworld</literal> 階段的編譯、安裝選項，以及
-          <application>NanoBSD</application> 主要打造過程中的選項。
-          透過使用這些選項可以削減系統的尺寸，使之能夠放入
-          64 MB 的隨身碟。 您還可以進一步透過這些選項來削減 &os;，
+          <application>NanoBSD</application> 打造過程中 <maketarget>buildworld</maketarget>
+          和 <maketarget>installworld</maketarget> 階段的編譯、安裝選項，以及
+          <application>NanoBSD</application> 主要打造過程中內部的選項。透
+          過這些選項可以削減系統的尺寸，使之能夠放入
+          64 MB 的隨身碟。您還可以進一步透過這些選項來削減 &os;，
           直到它只包含 kernel 以及兩三個 userland 檔案為止。</para>
 
-	<para>設定檔案中包含用以代替預設值的設定選項。簡介最重要的幾項設定如下：</para>
+	<para>設定檔案中包含用以代替預設值的設定選項。最重要的幾項設定如下：</para>
 
 	<itemizedlist>
 	  <listitem>
-	    <para><literal>NANO_NAME</literal> &mdash; 本次打造的名稱(所建立工作目錄的名稱)。</para>
+	    <para><literal>NANO_NAME</literal> &mdash;
+	      本次打造的名稱（所建立工作目錄的名稱）。</para>
 	  </listitem>
 
 	  <listitem>
-	    <para><literal>NANO_SRC</literal> &mdash; 用以編譯、打造映像檔的 source tree 的位置。</para>
+	    <para><literal>NANO_SRC</literal> &mdash; 用以編譯、打造映像檔的
+	      source tree 的位置。</para>
 	  </listitem>
 
 	  <listitem>
-	    <para><literal>NANO_KERNEL</literal> &mdash; 設定用來編譯的 kernel 設定檔檔名。</para>
+	    <para><literal>NANO_KERNEL</literal> &mdash; 設定用來編譯 kernel
+	      的設定檔檔名。</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><literal>CONF_BUILD</literal> &mdash; 用於
-	      <literal>buildworld</literal> 打造階段的選項。</para>
+	      <maketarget>buildworld</maketarget> 階段的選項。</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><literal>CONF_INSTALL</literal> &mdash; 用於
-	      <literal>installworld</literal> 打造階段的選項。</para>
+	      <maketarget>installworld</maketarget> 階段的選項。</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><literal>CONF_WORLD</literal> &mdash; 用於
-	      <literal>buildworld</literal> 和
-	      <literal>installworld</literal> 這兩個打造階段的選項。</para>
+	      <maketarget>buildworld</maketarget> 和
+	      <maketarget>installworld</maketarget> 這兩個階段的選項。</para>
 	  </listitem>
 
 	  <listitem>
@@ -250,49 +248,67 @@
       <sect3>
 	<title>自訂功能</title>
 
-	<para>透過在設定檔案中使用 shell 函數，可以進一步微調
-	  <application>NanoBSD</application>。 舉例說明一下自行打造函數的基本方式：</para>
+	<para>透過在設定檔案中使用 shell 函式，可以進一步微調
+	  <application>NanoBSD</application>。舉例說明一下自訂函式的基本方式：</para>
 
-	  <programlisting>cust_foo()(
+	  <programlisting>cust_foo () (
 	echo "bar=topless" &gt; \
 		&dollar;{NANO_WORLDDIR}/etc/foo
 )
 customize_cmd cust_foo</programlisting>
 
-        <para>下面舉更實際點的例子，它會把預設的
-          <filename role="directory">/etc</filename> 目錄大小，從 5MB 調整為 30MB：</para>
+	<para>下面舉更實際點的例子，它會把 <filename class="directory">/etc</filename>
+           目錄預設的大小，從 5MB 調整為 30MB：</para>
 
-	<programlisting>cust_etc_size()(
+	<programlisting>cust_etc_size () (
 	cd &dollar;{NANO_WORLDDIR}/conf
 	echo 30000 &gt; default/etc/md_size
 )
 customize_cmd cust_etc_size</programlisting>
 
-	<para>除此之外，還有幾個預設的功能定義可以用來自訂：</para>
+	<para>除此之外，還有幾個預設的自訂函式可以使用：</para>
 
 	<itemizedlist>
 	  <listitem>
-	    <para><literal>cust_comconsole</literal> &mdash; 在預設 VGA 顯示卡上停用 &man.getty.8;
-	     (<filename>/dev/ttyv*</filename>)並啟用 serial port 的 COM1 以作為系統 console。</para>
+	    <para><literal>cust_comconsole</literal> &mdash; 在 VGA 裝置上停用
+              &man.getty.8;（<filename>/dev/ttyv*</filename>）並啟用 serial port
+	      的 COM1 以作為系統 console。</para>
 	  </listitem>
 
 	  <listitem>
-	    <para><literal>cust_allow_ssh_root</literal> &mdash; 允許 &man.sshd.8;
-	      可以用 <username>root</username> 帳號登入。</para>
+	    <para><literal>cust_allow_ssh_root</literal> &mdash; 允許 
+	      <username>root</username> 可以用 &man.sshd.8; 登入。</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><literal>cust_install_files</literal> &mdash;
-	      從 <filename role="directory">nanobsd/Files</filename>
-	      目錄中安裝檔案，這包含一些實用的系統管理 script 。</para>
+	      從 <filename class="directory">nanobsd/Files</filename>
+	      目錄中安裝檔案，這包含一些實用的系統管理 script。</para>
 	  </listitem>
 	</itemizedlist>
       </sect3>
 
       <sect3>
-	<title>設定檔案舉例</title>
+	<title>安裝 packages</title>
+
+	<para>Packages 可以藉由自訂函式加入 <application>NanoBSD</application>
+	  的印象檔。下面的函式會安裝位於
+	  <filename>/usr/src/tools/tools/nanobsd/packages</filename>
+	  的 packages：</para>
+
+	<programlisting>install_packages () (
+mkdir -p ${NANO_WORLDDIR}/packages
+cp /usr/src/tools/tools/nanobsd/packages/* ${NANO_WORLDDIR}/packages
+chroot ${NANO_WORLDDIR} sh -c 'cd packages; pkg_add -v *;cd ..;'
+rm -rf ${NANO_WORLDDIR}/packages
+)
+customize_cmd install_packages</programlisting>
+      </sect3>
+
+      <sect3>
+	<title>設定檔案範例</title>
 
-	<para>下面是用於自行打造的 <application>NanoBSD</application> 映像檔的完整例子：</para>
+	<para>下面是用於自行打造的 <application>NanoBSD</application> 映像檔的完整範例：</para>
 
 	<programlisting>NANO_NAME=custom
 NANO_SRC=/usr/src
@@ -335,7 +351,7 @@
 
 FlashDevice SanDisk 1G
 
-cust_nobeastie()(
+cust_nobeastie() (
 	touch &dollar;{NANO_WORLDDIR}/boot/loader.conf
 	echo "beastie_disable=\"YES\"" &gt;&gt; &dollar;{NANO_WORLDDIR}/boot/loader.conf
 )
@@ -358,12 +374,13 @@
 	</step>
 
 	<step>
-	  <para>將新的映像檔放入正運行的
+	  <para>將新的映像檔上傳至正在運行的
 	    <application>NanoBSD</application> 中未用的分割區之一。</para>
 
 	  <para>與之前最初安裝 <application>NanoBSD</application> 的步驟相比，
-	    這一步驟最重要的區別在於：這次不用 <filename>_.disk.full</filename> 檔(它包含整個磁碟的映像檔)，
-	    而應安裝 <filename>_.disk.image</filename> 映像檔(這個檔案中，只包含一個系統分割區)。</para>
+	    這一步驟最重要的區別在於：這次不用 <filename>_.disk.full</filename>
+	    檔（它包含整個磁碟的映像檔）， 而應安裝 <filename>_.disk.image</filename>
+	    映像檔（這個檔案中，只包含一個系統分割區）。</para>
 	</step>
 
 	<step>
@@ -376,20 +393,20 @@
 
 	<step>
 	  <para>如果發生了任何問題，則可以從先前的分割區啟動
-	 (其中包含了舊的、 可用的映像檔)，來盡快恢復系統功能。
-	  接下來可以修正新編譯的版本中存在的問題，並重複前述步驟。</para>
+	    （其中包含了舊的、可用的映像檔），來盡快恢復系統功能。
+	    接下來可以修正新編譯的版本中存在的問題，並重複前述步驟。</para>
 	</step>
       </procedure>
 
       <para>要在正在運行的
 	<application>NanoBSD</application> 系統中安裝新的映像檔，可以使用位於
-	<filename role="directory">/root</filename> 目錄的
+	<filename class="directory">/root</filename> 目錄的
 	<filename>updatep1</filename> 或
-	<filename>updatep2</filename>  script ，
+	<filename>updatep2</filename> script ，
 	實際上要用哪一個 script，則取決於正在運行的系統是位於哪個分割區而定。</para>
 
-      <para>隨時提供新 <application>NanoBSD</application> 映像檔所提供的服務，
-	以及採用的傳輸方法的不同，您可以參考並使用下列三種方式之一：</para>
+      <para>視提供新 <application>NanoBSD</application> 映像檔的主機所提供的服務，
+	以及希望採用的傳輸方式，您可以參考並使用下列三種方式之一：</para>
 
       <sect3>
 	<title>使用 &man.ftp.1;</title>
@@ -403,7 +420,7 @@
       <sect3>
 	<title>使用 &man.ssh.1;</title>
 
-	<para>如果想更安全的話，應參考下面例子：</para>
+	<para>如果想使用加密連線的話，應參考下面例子：</para>
 
 	<screen>&prompt.root; <userinput>ssh myhost cat _.disk.image.gz | zcat | sh updatep1</userinput></screen>
       </sect3>
@@ -415,7 +432,8 @@
 
 	<procedure>
 	  <step>
-	    <para>首先，在提供映像檔的主機上開啟 TCP listen，並讓它把映像檔傳給 client：</para>
+	    <para>首先，在提供映像檔的主機上開啟 TCP listener，並讓它把映像檔傳給
+	      client：</para>
 
 	    <screen>myhost&prompt.root; <userinput>nc -l <replaceable>2222</replaceable> &lt; _.disk.image</userinput></screen>
 
@@ -425,7 +443,7 @@
 	    </note>
 	  </step>
 	  <step>
-	    <para>連到提供新映像檔服務的主機，並執行 <filename>updatep1</filename> 這支 script：</para>
+	    <para>連到提供新映像檔的主機，並執行 <filename>updatep1</filename> 這支 script：</para>
 	      
 	    <screen>&prompt.root; <userinput>nc myhost <replaceable>2222</replaceable> | sh updatep1</userinput></screen>
 	  </step>
--- nanobsd-article.sgml.patch ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Sun Nov  8 00:50:02 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Sun Nov  8 00:50:09 2009
Subject: docs/140377: [PATCH] Typo in Handbook (Virtualization)
Message-ID: <20091108004822.6FEBF6FC443@mx.hs.ntnu.edu.tw>


>Number:         140377
>Category:       docs
>Synopsis:       [PATCH] Typo in Handbook (Virtualization)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 08 00:50:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Denny Lin
>Release:        FreeBSD 7.2-RELEASE-p4 amd64
>Organization:
>Environment:
System: FreeBSD cnmc32.hs.ntnu.edu.tw 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Mon Oct 26 19:41:45 CST 2009 root@cnmc32.hs.ntnu.edu.tw:/usr/obj/usr/src/sys/CNMC32 amd64


	
>Description:
"VMWare" should be "VMware".
	
>How-To-Repeat:
	
>Fix:
Patched (sed 's/VMWare/VMware/g').

	

--- virtualization-chapter.sgml.patch begins here ---
--- doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml.orig	2009-11-08 08:42:29.000000000 +0800
+++ doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml	2009-11-08 08:42:40.000000000 +0800
@@ -768,20 +768,20 @@
     </sect2>
 
     <sect2 id="virtualization-guest-vmware">
-      <title>VMWare on MacOS</title>
+      <title>VMware on MacOS</title>
 
-      <para><application>VMWare Fusion</application> for &mac; is a
+      <para><application>VMware Fusion</application> for &mac; is a
 	commercial software product available for &intel; based &apple;
 	&mac; computers running &macos; 10.4.9 or higher.  FreeBSD is a
 	fully supported guest operating system.  Once
-	<application>VMWare Fusion</application> has been installed on
+	<application>VMware Fusion</application> has been installed on
 	&macos; X, the user must configure a virtual machine and then
 	install the desired guest operating system.</para>
 
 	<sect3 id="virtualization-guest-vmware-install">
-	  <title>Installing FreeBSD on VMWare/&macos; X</title>
+	  <title>Installing FreeBSD on VMware/&macos; X</title>
 
-	  <para>The first step is to start VMWare Fusion, the Virtual
+	  <para>The first step is to start VMware Fusion, the Virtual
 	    Machine Library will load.  Click "New" to create the VM:</para>
 
 	  <mediaobject>
@@ -906,10 +906,10 @@
         </sect3>
 
 	<sect3 id="virtualization-guest-vmware-configure">
-	  <title>Configuring FreeBSD on &macos; X/VMWare</title>
+	  <title>Configuring FreeBSD on &macos; X/VMware</title>
 
 	  <para>After FreeBSD has been successfully installed on &macos;
-	    X with <application>VMWare</application>, there are a number
+	    X with <application>VMware</application>, there are a number
 	    of configuration steps that can be taken to optimize the system
 	    for virtualized operation.</para>
 
@@ -919,14 +919,14 @@
 
 	      <para>The most important step is to reduce the
 	        <option>kern.hz</option> tunable to reduce the CPU utilization
-		of FreeBSD under the <application>VMWare</application>
+		of FreeBSD under the <application>VMware</application>
 		environment.  This is accomplished by adding the following
 		line to <filename>/boot/loader.conf</filename>:</para>
 
 	  	<programlisting>kern.hz=100</programlisting>
 
 	      <para>Without this setting, an idle FreeBSD
-	        <application>VMWare</application> guest
+	        <application>VMware</application> guest
 		OS will use roughly 15% of the CPU of a single
 		processor &imac;.  After this change the usage will be
 		closer to a mere 5%.</para>
@@ -936,7 +936,7 @@
 	      <title>Create a new kernel configuration file</title>
 
 	      <para>You can remove all of the FireWire, and USB device
-	        drivers.  <application>VMWare</application> provides a
+	        drivers.  <application>VMware</application> provides a
 		virtual network adapter used by the &man.em.4; driver,
 		so all other network devices except for &man.em.4; can
 		be removed from the kernel.</para>
--- virtualization-chapter.sgml.patch ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From linimon at FreeBSD.org  Sun Nov  8 03:50:07 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Sun Nov  8 03:50:13 2009
Subject: docs/140369: [patch] src/contrib/pf/man/pf.4
Message-ID: <200911080350.nA83o77n087974@freefall.freebsd.org>

Synopsis: [patch] src/contrib/pf/man/pf.4

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Nov 8 03:49:49 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=140369
From bcr at FreeBSD.org  Sun Nov  8 12:42:08 2009
From: bcr at FreeBSD.org (bcr@FreeBSD.org)
Date: Sun Nov  8 12:42:14 2009
Subject: docs/140377: [PATCH] Typo in Handbook (Virtualization)
Message-ID: <200911081242.nA8Cg7GM090192@freefall.freebsd.org>

Synopsis: [PATCH] Typo in Handbook (Virtualization)

Responsible-Changed-From-To: freebsd-doc->bcr
Responsible-Changed-By: bcr
Responsible-Changed-When: Sun Nov 8 12:40:57 UTC 2009
Responsible-Changed-Why: 
I'll take care of this one.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140377
From gavin at FreeBSD.org  Sun Nov  8 16:14:14 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Sun Nov  8 16:14:20 2009
Subject: docs/107924: [usb67] usbd(8) does not call detach
Message-ID: <200911081614.nA8GEE44072007@freefall.freebsd.org>

Synopsis: [usb67] usbd(8) does not call detach

Responsible-Changed-From-To: freebsd-usb->freebsd-docs
Responsible-Changed-By: gavin
Responsible-Changed-When: Sun Nov 8 16:11:48 UTC 2009
Responsible-Changed-Why: 
This PR is actually only relevent for 6.x, as usbd was replaced in 7.x.
Because of that, I can't see this problem being fixed in 6.x alone -
so pass over to doc team to document as a bug instead.

http://www.freebsd.org/cgi/query-pr.cgi?pr=107924
From bugmaster at FreeBSD.org  Mon Nov  9 11:06:06 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov  9 11:06:37 2009
Subject: Current unassigned doc problem reports
Message-ID: <200911091106.nA9B66ai078303@freefall.freebsd.org>

(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .)

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/140375  doc        [UPDATE] Updated zh_TW.Big5/articles/nanobsd
o docs/140369  doc        [patch] src/contrib/pf/man/pf.4
o docs/140082  doc        handbook/jails: russian translation is missing
o docs/140075  doc        release notes: missing word "NOT", which changes all t
o docs/139682  doc        [PATCH] dialog(1) man page does not mention radiolist 
o docs/139603  doc        [patch] Clarify subpixel smoothing for fonts in Handbo
p docs/139370  doc        [PATCH] de(4) manual page typo
o docs/139336  doc        ZFS documentation suggestion
o docs/139165  doc        gssapi.3 man page out of sync with between crypto and 
o docs/139153  doc        the hier(7) man page needs to be updated
o docs/139018  doc        translation of submitting.sgml from docproj/submitting
o docs/138887  doc        manpage ports(7) incorrect
o docs/138845  doc        Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138663  doc        system(3) man page confuses users about "return value 
o docs/138485  doc        bpf(4) and ip(4) man pages missing important corner ca
o docs/138206  doc        [patch] ntp(1): not enabled function, and false manual
o docs/137762  doc        [handbook] proposed: mention "make delete-old" in sec 
o docs/137171  doc        [patch] replacement of k8temp(4) by amdtemp(4) isn't r
o docs/136918  doc        [patch] grammar fixes to locking.9
o docs/136712  doc        [handbook] [patch] draft new section on gmirror per pa
o docs/136666  doc        [handbook] Configure serial port for remote kernel deb
o docs/136100  doc        change FreeBSD Ports distfiles survey's url to portsco
o docs/136035  doc        ftpchroot(5) omits an important option
p docs/136029  doc        MALLOC_PRODUCTION knob should be mentioned somewhere, 
o docs/135999  doc        Netgear GS105v3 should be added to list of switches th
o docs/135676  doc        FAQ About The FreeBSD Mailing Lists doesn't mention ma
o docs/135516  doc        pax(1) manual not mentioning chflags unawareness
o docs/135475  doc        [patch] jot(1) manpage and behaviour differ
o docs/135165  doc        [patch] make(1) fixes: punctuation, typos, tweaks
o docs/134376  doc        pthread(3): pthread manpages don't mention that PTHREA
o docs/134226  doc        /usr/share/examples/ftpd/ftpd.conf does not exist.
o docs/134222  doc        installation failure of japanese docs
o docs/134123  doc        The RUNQUEUE(9) man page is out of date
o docs/134074  doc        [patch] locking.9 man page slight enhancements
o docs/133567  doc        [patch] doc/Makefile switch to csup
o docs/133245  doc        french handbook 27.3.5 amd.map amd.conf
o docs/133228  doc        handbook 23.3.5 screenmap section is confusing
o docs/133186  doc        [patch] powerd(8) man page errors
o docs/133118  doc        [patch] Error in getopt (1) manual EXAMPLES section
o docs/132959  doc        [patch] description mismatches on xterm/termcap, fortu
o docs/132884  doc        [request] No manpage for SYSINIT and SYSUNINIT
o docs/132839  doc        [patch] Fix example script in ldap-auth article
o docs/132718  doc        [handbook] Information about adding a new mirror is ou
o docs/132311  doc        [patch] man5/nsmb.conf.5
o docs/132260  doc        dhcpd(8) pid not stored in documented location
o docs/132190  doc        EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/132113  doc        [handbook] Update handbook jails creation
o docs/131918  doc        [patch] Fixes for the BPF(4) man page
o docs/131684  doc        [patch] articles/linux-comparison: replace Addenda by 
o docs/131590  doc        [patch] whitespace-only change of developers-handbook/
o docs/130895  doc        [patch] No man page installed for padlock(4) on amd64 
o docs/130364  doc        Man page for top needs explanation of CPU states
o docs/130238  doc        nfs.lockd man page doesn't mention NFSLOCKD option or 
o docs/129671  doc        New TCP chapter for Developer's Handbook (from rwatson
o docs/129095  doc        ipfw(8): Can not check that packet originating/destine
o docs/128524  doc        No geom documentation for loading gjournal(8)
s docs/128356  doc        [request] add Firefox plugin for FreeBSD manual pages
o docs/127908  doc        [patch] readdir(3) error documentation
s docs/127844  doc        Example code skeleton_capture_n.c in meteor(4) manpage
o docs/126590  doc        [patch] Write routine called forever in Sample Echo Ps
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
f docs/122052  doc        minor update on handbook section 20.7.1
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o bin/121424   doc        [patch] [ipfw] Rectify ambiguous English in manual
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
a docs/119536  doc        a few typos in French handbook (basics)
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118214  doc        close(2) error returns incomplete
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/117747  doc        'break' system call needs a man page
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/116116  doc        mktemp (3) re/move note
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111147  doc        hostapd.conf is not documented
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110061  doc        [patch] tuning(7) missing reference to vfs.read_max
o docs/109981  doc        No manual entry for post-grohtml
o docs/109977  doc        No manual entry for ksu
o docs/109973  doc        No manual entry for c++filt
o docs/109972  doc        No manual entry for zless/bzless
f docs/109226  doc        [request] No manual entry for sntp
o docs/109201  doc        [request]: manual for callbootd
a docs/108980  doc        list of missing man pages
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
o docs/107924  docs       [usb67] usbd(8) does not call detach
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/105608  doc        fdc(4) debugging description staled
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/91174   doc        [REQUEST] Handbook: Addition of Oracle 9i installation
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84271   doc        [patch] compress(1) doesn't warn about nasty link hand
o docs/83820   doc        getino(3) manpage not installed
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
o docs/63570   doc        [patch] Language cleanup for the Handbook's DNS sectio
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
o docs/53596   doc        Updates to mt(1) manual page
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/50211   doc        [patch] doc.docbook.mk: fix textfile creation
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/43823   doc        [patch] update to environ(7) manpage
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/38556   doc        EPS file of beastie, as addition to existing examples
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
a docs/30008   doc        [patch] French softupdates document should be translat
o docs/27605   doc        [patch] Cross-document references (<olink>)
o docs/26286   doc        *printf(3) etc should gain format string warnings
o docs/24786   doc        missing FILES descriptions in sa(4)
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc

162 problems total.

From "ds atukrhubdotnet" at chaos.ukrhub.net  Mon Nov  9 14:40:04 2009
From: "ds atukrhubdotnet" at chaos.ukrhub.net (Taras Korenko)
Date: Mon Nov  9 14:40:16 2009
Subject: docs/140418: [patch] articles/custom-gcc: russian translation is
	missing
Message-ID: <20091109143200.7970D40C6@chaos.ukrhub.net>


>Number:         140418
>Category:       docs
>Synopsis:       [patch] articles/custom-gcc: russian translation is missing
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 09 14:40:03 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Taras Korenko <ds at ukrhub dot net>
>Release:        FreeBSD 7.1-STABLE i386
>Organization:
Ukrcom
>Environment:
System: FreeBSD chaos.ukrhub.net 7.1-STABLE FreeBSD 7.1-STABLE #3: Sun Jan 11 08:10:44 EET 2009 ds@chaos.ukrhub.net:/usr/obj/usr/src/sys/ChKern71 i386


>Description:
Russian translation of doc/en_US.ISO8859-1/articles/custom-gcc is
available ouside the FDP. Please, insert it into the Documentation
Project.
>How-To-Repeat:
Just check the repository.
>Fix:
Fetch http://chaos.ukrhub.net/custom-gcc/doc.ru.articles.custom-gcc.tbz ,
unpack,
place unpacked to the proper directories,
patch doc/ru_RU.KOI8-R/articles/Makefile with Makefile.diff



>Release-Note:
>Audit-Trail:
>Unformatted:
From rsofia at poly.edu  Mon Nov  9 16:41:56 2009
From: rsofia at poly.edu (Randy Sofia)
Date: Mon Nov  9 16:42:31 2009
Subject: Missing context in handbook
Message-ID: <4AF841AE.1030804@poly.edu>

http://www.freebsd.org/doc/en/books/handbook/network-nfs.html

The handbook specifies "The -alldirs flag allows the 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."

While this is true, it is not noted in the handbook that it will also 
allow directories BELOW that directory to be mountable so long as it is 
part of the same file system.  As stated in the man pages:

 "the -alldirs flag; this form allows the host(s) to
     mount at any point within the file system, including regular files 
if the
     -r option is used on mountd(8)."


So for example if my /etc/exports looks like:
/home/randy  -alldirs  10.0.0.2 10.0.0.3 10.0.0.4


Not only will I be able to mount  /home/randy/Desktop   but I will also 
be able to mount /home/boris as well (if /home/randy and /home/boris are 
on the same file system).

--randy
From kurin at delete.org  Mon Nov  9 18:58:53 2009
From: kurin at delete.org (Toby Burress)
Date: Mon Nov  9 18:59:05 2009
Subject: ldap-auth article patch
Message-ID: <20091109184326.GG67127@lithium.delete.org>

Could I trouble someone to look at docs/132839?  It's just a patch
to the ldap-auth article.  I don't think it's very contentious.

It fixes some misinformation that the OpenLDAP guys have emailed
me about, and want to keep from spreading.
From jhelfman at e-e.com  Mon Nov  9 22:50:03 2009
From: jhelfman at e-e.com (Jason Helfman)
Date: Mon Nov  9 22:50:09 2009
Subject: docs/140434: added unset variable information to rc.conf man page
	for "hostname"
Message-ID: <200911092244.nA9MiRW7037338@www.freebsd.org>


>Number:         140434
>Category:       docs
>Synopsis:       added unset variable information to rc.conf man page for "hostname"
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 09 22:50:03 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Jason Helfman
>Release:        7.2-RELEASE-p4
>Organization:
Experts Exchange
>Environment:
FreeBSD eggman.experts-exchange.com 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct  2 12:21:39 UTC 2009     root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
After performing an automated installation of FreeBSD 7.2, I found that the console login showed "Amnesiac."

For some reason, I thought this was associated to a timezone, but found it was the hostname value if unset in /etc/rc.conf.

>How-To-Repeat:
Remove hostname value from /etc/rc.conf, and reboot.
>Fix:
Add hostname value to /etc/rc.conf, and reboot.

Patch attached with submission follows:

--- rc.conf.5.orig	2009-11-09 14:29:55.000000000 -0800
+++ rc.conf.5	2009-11-09 14:35:09.000000000 -0800
@@ -346,7 +346,8 @@
 .Pq Vt str
 The fully qualified domain name (FQDN) of this host on the network.
 This should almost certainly be set to something meaningful, even if
-there is no network connection.
+there is no network connection. If this value is unset, your console 
+login will display a default hostname value of "Amnesiac."
 If
 .Xr dhclient 8
 is used to set the hostname via DHCP,


>Release-Note:
>Audit-Trail:
>Unformatted:
From dan at obluda.cz  Tue Nov 10 00:30:02 2009
From: dan at obluda.cz (Dan Lukes)
Date: Tue Nov 10 00:30:09 2009
Subject: docs/140435: man ls,
	section STANDARD: the -A is exception from POSIX also
Message-ID: <200911100021.nAA0L5ng089063@kolej.mff.cuni.cz>


>Number:         140435
>Category:       docs
>Synopsis:       man ls, section STANDARD: the -A is exception from POSIX also
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 10 00:30:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Dan Lukes
>Release:        FreeBSD 7.2-RELEASE-p3 i386
>Organization:
Obludarium
>Environment:
bin/ls/ls.1,v 1.100.8.1 2009/04/15 03:14:26

>Description:
	see Synopsis
>How-To-Repeat:
	N/A
>Fix:
Change text
     With the exception of options -I, -g, -n and -o, the ls utility conforms
     to IEEE Std 1003.1-2001 (``POSIX.1'').
To
     With the exception of options -A, -I, -g, -n and -o, the ls utility conforms
     to IEEE Std 1003.1-2001 (``POSIX.1'').
>Release-Note:
>Audit-Trail:
>Unformatted:
From trhodes at FreeBSD.org  Tue Nov 10 00:39:57 2009
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Tue Nov 10 00:40:04 2009
Subject: ldap-auth article patch
In-Reply-To: <20091109184326.GG67127@lithium.delete.org>
References: <20091109184326.GG67127@lithium.delete.org>
Message-ID: <20091109193952.1b8f790e.trhodes@FreeBSD.org>

On Mon, 9 Nov 2009 13:43:26 -0500
Toby Burress <kurin@delete.org> wrote:

> Could I trouble someone to look at docs/132839?  It's just a patch
> to the ldap-auth article.  I don't think it's very contentious.
> 
> It fixes some misinformation that the OpenLDAP guys have emailed
> me about, and want to keep from spreading.

Patch modified, please verify the original meaning by giving
my version a once over.

--- article.sgml.old     2009-03-20 00:57:22.000000000 -0400
+++ article.sgml 2009-03-20 01:03:08.000000000 -0400
@@ -307,7 +307,6 @@
         organizational unit will look like:</para>
       <programlisting>dn: ou=people,dc=example,dc=org
-objectClass: top
 objectClass: organizationalUnit
 ou: people</programlisting>
@@ -336,7 +335,6 @@
 objectClass: person
 objectClass: posixAccount
 objectClass: shadowAccount
-objectClass: top
 uidNumber: 10000
 gidNumber: 10000
 homeDirectory: /home/tuser
@@ -352,13 +350,11 @@
         user entries, but we will use the defaults below:</para>
       <programlisting>dn: ou=groups,dc=example,dc=org
-objectClass: top
 objectClass: organizationalUnit
 ou: groups
 dn: cn=tuser,ou=groups,dc=example,dc=org
 objectClass: posixGroup
-objectClass: top
 gidNumber: 10000
 cn: tuser</programlisting>
@@ -604,51 +600,74 @@
         <screen>&prompt.root; <userinput>sysctl security.bsd.see_other_uids=0</userinput>.</screen>
       </caution>
-      <para>A more flexible (and probably more secure) approach can be
-        used by writing a custom program, or even a web interface.  The
-        following is part of a <application>Ruby</application> library
-        that can change LDAP passwords.  It sees use both on the command
-        line, and on the web.</para>
+  <para>A more flexible (and probably more secure) approach can be
+        used by writing a custom program, or even a web interface.
+        The following is modeled on a <application>Python</application>
+        library that can change LDAP passwords.  It may be used on both
+        on the command line, and on the web.</para>
-      <example id="chpw-ruby">
-        <title>Ruby script for changing passwords</title>
+      <example id="chpw-python">
+        <title>Python script for changing passwords</title>
-        <programlisting><![CDATA[require 'ldap'
-require 'base64'
-require 'digest'
-require 'password' # ruby-password
-
-ldap_server = "ldap.example.org"
-luser = "uid=#{ENV['USER']},ou=people,dc=example,dc=org"
-
-# get the new password, check it, and create a salted hash from it
-def get_password
-  pwd1 = Password.get("New Password: ")
-  pwd2 = Password.get("Retype New Password: ")
-
-  raise if pwd1 != pwd2
-  pwd1.check # check password strength
-
-  salt = rand.to_s.gsub(/0\./, '')
-  pass = pwd1.to_s
-  hash = "{SSHA}"+Base64.encode64(Digest::SHA1.digest("#{pass}#{salt}")+salt).chomp!
-  return hash
-end
-
-oldp = Password.get("Old Password: ")
-newp = get_password
-
-# We'll just replace it.  That we can bind proves that we either know
-# the old password or are an admin.
-
-replace = LDAP::Mod.new(LDAP::LDAP_MOD_REPLACE | LDAP::LDAP_MOD_BVALUES,
-                        "userPassword",
-                        [newp])
-
-conn = LDAP::SSLConn.new(ldap_server, 389, true)
-conn.set_option(LDAP::LDAP_OPT_PROTOCOL_VERSION, 3)
-conn.bind(luser, oldp)
-conn.modify(luser, [replace])]]></programlisting>
+        <programlisting><![CDATA[import ldap # python-ldap
+import os, sys
+from getpass import getpass
+
+uri = "ldap://ldap1.example.com"
+searchbase = "ou=people,dc=example,dc=com"
+filter = "(&(objectClass=posixAccount)(uid=%s))"
+
+# get the username; if none is given, use the current user
+user = os.environ['USER']
+if len(sys.argv) > 1:
+    user = sys.argv[1]
+
+ldapobj = ldap.initialize(uri)
+ldapobj.start_tls_s() # this is pretty important
+
+# Get the users DN, and then bind as that.
+# The way to do this is first bind anonymously (if you do not allow
+# anonymous binds, there's probably some standard account you use for this.
+ldapobj.simple_bind_s()
+
+# Search for a user with the uid we gave.  We search everything under
+# the "base" we configure above (as there may be other users with the same
+# UID elsewhere in the tree; we do not want to return those.
+result = ldapobj.search_s(searchbase, ldap.SCOPE_SUBTREE, filter%user)
+
+if len(result) > 1:
+    # This is kind of suspicious; we only want one user.
+    print "I found several users that match that user id."
+    print "Talk to your sysadmin."
+    sys.exit(1)
+
+# The results are an array of (dn, attrlist) tuples.
+dn = result[0][0]
+
+# Now we get the user's old password, and bind to the server with it
+# and his DN.  If it succeeds, we have the proper credentials to
+# change his password.
+passwd = getpass("current password: ")
+try:
+    ldapobj.simple_bind_s(dn, passwd)
+except ldap.INVALID_CREDENTIALS:
+    print "Bad password."
+    sys.exit(1)
+
+# Get and confirm new password.
+npass1 = 'a'
+npass2 = 'b'
+while npass1 != npass2:
+    npass1 = getpass("new password: ")
+    npass2 = getpass("new password (again): ")
+
+# This is the key.  This uses the LDAP Password Modify Extended Operation.
+# It is important to use this when you can, although not all libraries
+# (e.g.: ruby-ldap) support it.  See rfc3062.
+ldapobj.passwd_s(dn, passwd, npass1)
+
+# And we are done.
+ldapobj.unbind()]]></programlisting>
       </example>
       <para>Although not guaranteed to be free of security holes (the
@@ -759,7 +778,6 @@
           <title>Creating a management group</title>
           <programlisting>dn: cn=homemanagement,dc=example,dc=org
-objectClass: top
 objectClass: posixGroup
 cn: homemanagement
 gidNumber: 121 # required for posixGroup

Thanks,

-- 
Tom Rhodes
From dougb at FreeBSD.org  Tue Nov 10 03:19:30 2009
From: dougb at FreeBSD.org (dougb@FreeBSD.org)
Date: Tue Nov 10 03:19:36 2009
Subject: docs/140434: [patch] added unset variable information to
	rc.conf(5) man page for "hostname"
Message-ID: <200911100319.nAA3JUrr021397@freefall.freebsd.org>

Synopsis: [patch] added unset variable information to rc.conf(5) man page for "hostname"

State-Changed-From-To: open->patched
State-Changed-By: dougb
State-Changed-When: Tue Nov 10 03:10:50 UTC 2009
State-Changed-Why: 

I committed similar text to HEAD and will MFC it soon.


Thanks!

Doug


Responsible-Changed-From-To: freebsd-doc->dougb
Responsible-Changed-By: dougb
Responsible-Changed-When: Tue Nov 10 03:10:50 UTC 2009
Responsible-Changed-Why: 

I'll handle this one.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140434
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Tue Nov 10 14:10:03 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Tue Nov 10 14:10:10 2009
Subject: docs/140444: [UPDATE] New Traditional Chinese translation of
	custom-gcc
Message-ID: <20091110140334.185386FC45D@mx.hs.ntnu.edu.tw>


>Number:         140444
>Category:       docs
>Synopsis:       [UPDATE] New Traditional Chinese translation of custom-gcc
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 10 14:10:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Denny Lin
>Release:        FreeBSD 7.2-RELEASE-p4 amd64
>Organization:
>Environment:
System: FreeBSD cnmc32.hs.ntnu.edu.tw 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Mon Oct 26 19:41:45 CST 2009 root@cnmc32.hs.ntnu.edu.tw:/usr/obj/usr/src/sys/CNMC32 amd64


	
>Description:
New Traditional Chinese translation of "Using newer version of GCC and binutils with the FreeBSD Ports Collection."

Should be put in doc/zh_TW.Big5/articles/custom-gcc.

The attached files are also available at http://security-hole.info/~dennylin93/doc/zh_TW.Big5/articles/custom-gcc/.

>How-To-Repeat:
	
>Fix:

	

--- Makefile begins here ---
# 
# $FreeBSD$
#
# Article: Using newer version of GCC and binutils with the FreeBSD Ports Collection

DOC?= article

FORMATS?= html
WITH_ARTICLE_TOC?= YES

INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=

SRCS=		article.sgml

URL_RELPREFIX?=	../../../..
DOC_PREFIX?= ${.CURDIR}/../../..

.include "${DOC_PREFIX}/share/mk/doc.project.mk"
--- Makefile ends here ---

--- article.sgml begins here ---
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
%articles.ent;
]>

<article>
  <articleinfo>
    <title>������ &os; Ports Collection 雿輻�冽�啁����祉�� <application>GCC</application>
      ��� <application>binutils</application></title>

    <author>
      <firstname>Martin</firstname>
      <surname>Matuska</surname>
      <affiliation>
	<address><email>mm@FreeBSD.org</email></address>
      </affiliation>
    </author>

    <pubdate>$FreeBSD$</pubdate>

    <legalnotice id="trademarks" role="trademarks">
      &tm-attrib.freebsd;
      &tm-attrib.general;
    </legalnotice>

    <copyright>
      <year>2009</year>
      <holder>The &os; Documentation Project</holder>
    </copyright>

    <abstract>
      <para>甇斤�����隞嗉牧���鈭�憒�雿�敺� &os; ports tree 雿輻�冽�啁����祉��
	<application>GCC</application> 蝺刻陌��刻��
	<application>binutils</application>���
	��芾����� <application>GCC</application> 閮剖��銋���舀�祆��隞嗉��隢�蝭�������</para>
    </abstract>
  </articleinfo>

  <sect1 id="intro">
    <title>蝪∩��</title>

    <para>��� &os; 8.0 鋆∴��蝟餌絞���閮剔��蝺刻陌��函�� <application>GCC</application>
      ������ 4.2.1�����斗迨銋�憭�嚗�蝟餌絞��祈澈銋���急�� <application>binutils</application>
      ������ 2.15������鈭������砍歇蝬���箏嗾撟港��嚗�銝�銝���舀�湔�啁�� CPU ���隞日��嚗�憒�
      <acronym>SSSE3</acronym>���<acronym>SSE4.1</acronym>���<acronym>SSE4.2</acronym>
      蝑����蝷���潸迂��航��������靽�嚗����鈭�蝔�撘�頛���啁�������砌蒂銝����鋡怎宏璊���啁頂蝯勗�扼��撟詨末嚗�隞���嗅�臭誑������
      &os; ports tree 雿輻�冽�啁����祉�� <application>GCC</application> 蝺刻陌��剁��憒�嚗�������
      4.4嚗����</para>
  </sect1>

  <sect1 id="prerequisites">
    <title>������</title>

    <sect2 id="installing-binutils">
      <title>敺� ports 摰�鋆� binutils</title>

      <para>��亥��雿輻�冽����� <application>GCC</application>
	��啁����祉�������踝��敹����摰�鋆������啁����祉�� <application>binutils</application>���
	�����嗅��鋆���啁����祉�� <application>binutils</application>
	���敹�閬�璇�隞塚��雿���交�����摰�鋆�嚗�撠���⊥��雿輻�冽�� <acronym>CPU</acronym>
	������隞日�����</para>

      <para>��亥��敺� &os; ports tree 摰�鋆������啁����祉��
	<application>binutils</application>嚗�隢�銝�嚗�

      <screen>&prompt.root; <userinput>cd /usr/ports/devel/binutils && make install</userinput></screen>
    </sect2>

    <sect2 id="installing-gcc">
      <title>敺� ports 摰�鋆� GCC</title>

      <para>&os; ports tree ���靘�鈭���貊車��啁����祉��
	<application>GCC</application>���銝���Ｙ��蝭�靘���臭蝙��函帘摰���� 4.4
	�����研��雿���荔����臭誑摰�鋆�銋���������湔�啁�������穿��憒�嚗�
	<filename role="package">lang/gcc43</filename> ���
	<filename role="package">lang/gcc45</filename>嚗����</para>

      <para>��亥��摰�鋆�銝���Ｘ����啁�� <application>GCC</application>
	ports 銋�銝�嚗�隢�銝�嚗�

      <screen>&prompt.root; <userinput>cd /usr/ports/lang/<replaceable>gcc44</replaceable> && make install</userinput></screen>
    </sect2>
  </sect1>

  <sect1 id="configuring-ports-gcc">
    <title>閮剖�� ports 雿輻�刻�芾�������祉��
      <application>GCC</application></title>

    <para>雿輻�典�� &os; ports tree 摰�鋆���� <application>GCC</application>
      銋����嚗�敹����������銝�鈭�憿�憭����閮剖�����<para>

    <sect2 id="adjusting-make.conf">
      <title>隤踵�� <filename>make.conf</filename></title>

      <para>撠�銝����撟曇��������
	<filename>/etc/make.conf</filename>
	瑼�獢�嚗�閬����瘜�隤踵�湛��嚗�</para>

      <programlisting>.if !empty(.CURDIR:M/usr/ports/*) && exists(/usr/local/bin/gcc44)
CC=gcc44
CXX=g++44
CPP=cpp44
.endif</programlisting>

      <para>甇文��嚗���臭誑������閮剛�����
	<envar>${CC}</envar> ��� <envar>${CPP}</envar>���</para>

      <note>
	<para>銝���Ｙ��蝭�鋆⊥�舐策 <application>GCC</application>
	  ������ 4.4�����亥��雿輻�� <command>gcc43</command> 撠�
	  <literal>���gcc44���</literal> ��踵����� <literal>���gcc43���</literal>���
	  <literal>���4.4���</literal> ��踵����� <literal>���4.3���</literal>嚗�隞交迨憿���具��</para>
      </note>
    </sect2>

    <sect2 id="adjusting-libmap.conf">
      <title>隤踵�� <filename>libmap.conf</filename></title>

      <para>閮勗�� ports �����瑁��瑼���� libraries ������蝯���� libgcc_s
	��� libstdc++���蝟餌絞撌脫����批遣���鈭� libraries嚗�雿���舀��
	撠梁����祉�� <application>GCC</application>嚗������� 4.2.1嚗����
	rtld嚗���� ldd嚗�甇�蝣箇�������穿��撠�銝����撟曇��������
	<filename>/etc/libmap.conf</filename> 瑼�獢�嚗�閬����瘜�隤踵�湛��嚗�</para>

      <programlisting>libgcc_s.so.1   gcc44/libgcc_s.so.1
libgomp.so.1    gcc44/libgomp.so.1
libobjc.so.3    gcc44/libobjc.so.2
libssp.so.0     gcc44/libssp.so.0
libstdc++.so.6  gcc44/libstdc++.so.6</programlisting>

      <note>
	<para>銝���Ｙ��蝭�靘���舫��撠� <application>GCC</application>
	  ������ 4.4�����亥��雿輻�� <command>gcc43</command>嚗�撠�
	  <literal>���gcc44���</literal> ��踵�����
	  <literal>���gcc43���</literal>嚗�隞交迨憿���具����澆��瘜冽�������荔�����鈭�
	  libraries ��質��蝟餌絞��祈澈��� libraries ��詨捆���</para>
      </note>

      <warning>
	<para>���鈭� C++ ��仿��鈭� libraries 瘝����閮剖��憟踝����臭誑��⊥����瑁�����
	  ��交�����颲行��撠���������� libraries 閮剖��憟踝��撱箄降��喳�� libstdc++.so
	  閬�甇�蝣箝��</para>
      </warning>
    </sect2>

    <sect2 id="custom-cflags">
      <title>��芾�� ports tree 雿輻�函�� <literal>CFLAGS</literal></title>

      <para>��亥�����撠� ports tree �����芾��嚗�蝟餌絞��批遣銝���舀�湛�����
	<literal>CFLAGS</literal>嚗���扯��蝭�靘�隤踵��
	<filename>/etc/make.conf</filename>嚗�</para>

      <programlisting>.if !empty(.CURDIR:M/usr/ports/*) && exists(/usr/local/bin/gcc44)
CC=gcc44
CXX=g++44
CPP=cpp44
CFLAGS+=-mssse3
.endif</programlisting>

      <para>��臭誑摰���典��隞�
	<literal>CFLAGS</literal>嚗�銋���臭誑閮剖����芾�����
	<literal>CPUTYPE</literal>���������撱箄降閮剖����芾�����
	<literal>CPUTYPE</literal> �����箄迂憭� ports �����芾店�����訾誑甇方����貊�箏�箇�����</para>
    </sect2>

    <sect2 id="excluding-unbuildable-ports">
      <title>�����斤�⊥����冽�啁����祉�� <application>GCC</application>
      蝺刻陌��� ports���</title>

      <para>��亥�������支��鈭�頝���啁����祉��
	<application>GCC</application> ������憿���� ports嚗�靘���抒��靘�隤踵��
	<filename>/etc/make.conf</filename>嚗�</para>

      <programlisting>.if !empty(.CURDIR:M/usr/ports/*) && exists(/usr/local/bin/gcc44)
.if empty(.CURDIR:M/usr/ports/net/openldap*)
CC=gcc44
CXX=g++44
CPP=cpp44
.endif
.endif</programlisting>

      <para>銝���Ｙ��蝭�靘�摰�鋆�
	<filename role="package">net/openldap</filename>* ports
	���嚗�銝����雿輻�� <command>gcc</command> 4.4�����血��嚗�銋���臭誑��典��銝�銵�銝�閮剜�游��
	ports嚗�</para>

      <programlisting>.if empty(.CURDIR:M/usr/ports/net/openldap*) && empty(.CURDIR:M/usr/ports/xxx/yyy) && ...</programlisting>
    </sect2>
  </sect1>

  <sect1 id="performance-imparct">
    <title>撠�鈭���脖����瑁��瑼�銋�敶梢��</title>

    <para>雿輻�� <application>GCC</application> ������ 4.4 銝�
      <acronym>SSSE3</acronym> ���隞日�������典�堆����� <acronym>CPU</acronym>
      ��舀�湛��撟喳��靘�雓�嚗������賢�航�賣��擃� 10% �����冽��鈭�皜祈岫��嗡葉嚗�蝯����憿舐內�����賣��������頞����
      20%嚗�憒�嚗�������憭�慦�擃����嚗����</para>

    <para>雿����<ulink
	url="http://people.freebsd.org/~mm/benchmarks/perlbench/"></ulink>
      ���銵冽�潮＊蝷箔�� &os; 蝟餌絞��批遣��� <application>GCC</application> �����祈��
      <application>GCC</application> ������ 4.3���4.4 銋�瘥�頛����銵冽�澆����急�����蝔�
      <literal>CFLAGS</literal> ���蝯����嚗�雿輻�函����� perlbench
      ��������賣葫閰血��隞嗚��</para>
  </sect1>
</article>
--- article.sgml ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From www at FreeBSD.org  Tue Nov 10 14:54:58 2009
From: www at FreeBSD.org (World Wide Web Owner)
Date: Tue Nov 10 14:55:06 2009
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200911101454.nAAEsvGa016963@www.freebsd.org>

? relnotes7/doc/en_US.ISO8859-1/readme/contacting.html
? relnotes7/doc/en_US.ISO8859-1/readme/docbook.css
? relnotes7/doc/en_US.ISO8859-1/readme/index.html
? relnotes7/doc/en_US.ISO8859-1/readme/obtain.html
? relnotes7/doc/en_US.ISO8859-1/readme/seealso.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/HTML.manifest
? relnotes7/doc/en_US.ISO8859-1/relnotes/TRADEMARKS.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/article.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/docbook.css
? relnotes7/doc/en_US.ISO8859-1/relnotes/index.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/new.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/upgrade.html
? relnotes7/doc/share/sgml/catalog-auto
? relnotes7/doc/share/sgml/dev-auto.sgml
===> FAQ
===> advocacy
===> commercial
env SGML_CATALOG_FILES= XML_CATALOG_FILES="file:///w/www/build/www/en/commercial/catalog-cwd.xml  file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml  file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml  file:///w/www/build/doc/share/sgml/catalog.xml  file:///w/www/build/doc/share/sgml/catalog-common.xml  file:///w/www/build/www/en/share/sgml/catalog.xml  file:///w/www/build/www/share/sgml/catalog.xml  file:///w/www/build/www/share/sgml/catalog-common.xml  file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc  --xinclude --stringparam LOCALBASE /usr/local --stringparam WEB_PREFIX /w/www/build/www --nonet --catalogs  -o consult.html --param pagename "'Consulting Services'"  --param basename "'consult.html'"    /w/www/build/www/share/sgml/templates.entries.xsl /w/www/build/www/share/sgml/commercial.consult.xml
/w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : error parsing attribute name
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                      ^
/w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : attributes construct error
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                      ^
/w/www/build/www/share/sgml/commercial.consult.xml:3065: namespace error : Namespace prefix mailto on opentech is not defined
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                      ^
/w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : Couldn't find end of Start Tag opentech line 3065
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                      ^
/w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : Opening and ending tag mismatch: description line 3059 and a
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                                                           ^
/w/www/build/www/share/sgml/commercial.consult.xml:3071: parser error : Opening and ending tag mismatch: entry line 3056 and description
    </description>
                  ^
/w/www/build/www/share/sgml/commercial.consult.xml:3072: parser error : Opening and ending tag mismatch: entries line 6 and entry
  </entry>
          ^
/w/www/build/www/share/sgml/commercial.consult.xml:3073: parser error : Extra content at the end of the document
</entries>
^
unable to parse /w/www/build/www/share/sgml/commercial.consult.xml
*** Error code 6

Stop in /w/www/build/www/en/commercial.
*** Error code 1

Stop in /w/www/build/www/en.
        1.03 real         0.18 user         0.21 sys
From www at FreeBSD.org  Tue Nov 10 15:09:58 2009
From: www at FreeBSD.org (World Wide Web Owner)
Date: Tue Nov 10 15:10:05 2009
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200911101509.nAAF9vkB019190@www.freebsd.org>

? relnotes7/doc/en_US.ISO8859-1/readme/contacting.html
? relnotes7/doc/en_US.ISO8859-1/readme/docbook.css
? relnotes7/doc/en_US.ISO8859-1/readme/index.html
? relnotes7/doc/en_US.ISO8859-1/readme/obtain.html
? relnotes7/doc/en_US.ISO8859-1/readme/seealso.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/HTML.manifest
? relnotes7/doc/en_US.ISO8859-1/relnotes/TRADEMARKS.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/article.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/docbook.css
? relnotes7/doc/en_US.ISO8859-1/relnotes/index.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/new.html
? relnotes7/doc/en_US.ISO8859-1/relnotes/upgrade.html
? relnotes7/doc/share/sgml/catalog-auto
? relnotes7/doc/share/sgml/dev-auto.sgml
===> FAQ
===> advocacy
===> commercial
env SGML_CATALOG_FILES= XML_CATALOG_FILES="file:///w/www/build/www/en/commercial/catalog-cwd.xml  file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml  file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml  file:///w/www/build/doc/share/sgml/catalog.xml  file:///w/www/build/doc/share/sgml/catalog-common.xml  file:///w/www/build/www/en/share/sgml/catalog.xml  file:///w/www/build/www/share/sgml/catalog.xml  file:///w/www/build/www/share/sgml/catalog-common.xml  file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc  --xinclude --stringparam LOCALBASE /usr/local --stringparam WEB_PREFIX /w/www/build/www --nonet --catalogs  -o consult.html --param pagename "'Consulting Services'"  --param basename "'consult.html'"    /w/www/build/www/share/sgml/templates.entries.xsl /w/www/build/www/share/sgml/commercial.consult.xml
/w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : error parsing attribute name
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                      ^
/w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : attributes construct error
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                      ^
/w/www/build/www/share/sgml/commercial.consult.xml:3065: namespace error : Namespace prefix mailto on opentech is not defined
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                      ^
/w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : Couldn't find end of Start Tag opentech line 3065
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                      ^
/w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : Opening and ending tag mismatch: description line 3059 and a
      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our
                                                           ^
/w/www/build/www/share/sgml/commercial.consult.xml:3071: parser error : Opening and ending tag mismatch: entry line 3056 and description
    </description>
                  ^
/w/www/build/www/share/sgml/commercial.consult.xml:3072: parser error : Opening and ending tag mismatch: entries line 6 and entry
  </entry>
          ^
/w/www/build/www/share/sgml/commercial.consult.xml:3073: parser error : Extra content at the end of the document
</entries>
^
unable to parse /w/www/build/www/share/sgml/commercial.consult.xml
*** Error code 6

Stop in /w/www/build/www/en/commercial.
*** Error code 1

Stop in /w/www/build/www/en.
        0.80 real         0.15 user         0.19 sys
From roam at ringlet.net  Tue Nov 10 15:14:20 2009
From: roam at ringlet.net (Peter Pentchev)
Date: Tue Nov 10 15:14:26 2009
Subject: FreeBSD web build failed on www.freebsd.org
In-Reply-To: <200911101454.nAAEsvGa016963@www.freebsd.org>
References: <200911101454.nAAEsvGa016963@www.freebsd.org>
Message-ID: <20091110151353.GA5535@straylight.m.ringlet.net>

On Tue, Nov 10, 2009 at 02:54:57PM +0000, World Wide Web Owner wrote:
[snip]
> ===> commercial
[snip]
> /w/www/build/www/share/sgml/commercial.consult.xml:3065: parser error : error parsing attribute name
>       <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit our

Fixed.

G'luck,
Peter

-- 
Peter Pentchev	roam@ringlet.net    roam@space.bg    roam@FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
This sentence would be seven words long if it were six words shorter.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20091110/8d08721c/attachment.pgp
From remko at elvandar.org  Tue Nov 10 16:29:20 2009
From: remko at elvandar.org (Remko Lodder)
Date: Tue Nov 10 16:29:28 2009
Subject: FreeBSD web build failed on www.freebsd.org
In-Reply-To: <20091110151353.GA5535@straylight.m.ringlet.net>
References: <200911101454.nAAEsvGa016963@www.freebsd.org>
	<20091110151353.GA5535@straylight.m.ringlet.net>
Message-ID: <BAB50463-7FD2-4487-88ED-DA10A617D842@elvandar.org>

Thanks!

pointhat:		remko

On Nov 10, 2009, at 4:13 PM, Peter Pentchev wrote:

> On Tue, Nov 10, 2009 at 02:54:57PM +0000, World Wide Web Owner wrote:
> [snip]
>> ===> commercial
> [snip]
>> /w/www/build/www/share/sgml/commercial.consult.xml:3065: parser  
>> error : error parsing attribute name
>>      <mailto:opentech@opentech.dk>opentech@opentech.dk</a>.  Visit  
>> our
>
> Fixed.
>
> G'luck,
> Peter
>
> -- 
> Peter Pentchev	roam@ringlet.net    roam@space.bg    roam@FreeBSD.org
> PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
> Key fingerprint	2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
> This sentence would be seven words long if it were six words shorter.

-- 
/"\   Best regards,                        | remko@FreeBSD.org
\ /   Remko Lodder                      | remko@EFnet
X    http://www.evilcoder.org/    |
/ \   ASCII Ribbon Campaign    | Against HTML Mail and News

From prizeclaim at freelotto.com  Tue Nov 10 23:58:08 2009
From: prizeclaim at freelotto.com (=?UTF-8?B?RnJlZUxvdHRv?=)
Date: Tue Nov 10 23:58:13 2009
Subject: Your email is not a recognized FreeLotto Member
Message-ID: <NM-455-22315--1257896588@mailgen-0-5>

Sorry, but the email address you wrote in on is not located in our database. 
In order to win you must be a registered FreeLotto member. 

To play FreeLotto in accordance with the Official rules of FreeLotto and to
never miss a chance at $11,000,000.00 in prizes click here: 
http://www.freelotto.com/offer.asp?offer=98123

Sincerely,
FreeLotto Prize Claim Department
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Wed Nov 11 04:50:03 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Wed Nov 11 04:50:15 2009
Subject: docs/140465: [UPDATE] Outdated doceng@ info in www and src
Message-ID: <20091111044130.CD4BD6FC45D@mx.hs.ntnu.edu.tw>


>Number:         140465
>Category:       docs
>Synopsis:       [UPDATE] Outdated doceng@ info in www and src
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 11 04:50:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Denny Lin
>Release:        FreeBSD 7.2-RELEASE-p4 amd64
>Organization:
>Environment:
System: FreeBSD cnmc32.hs.ntnu.edu.tw 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Mon Oct 26 19:41:45 CST 2009 root@cnmc32.hs.ntnu.edu.tw:/usr/obj/usr/src/sys/CNMC32 amd64


	
>Description:
Both http://www.freebsd.org/internal/doceng.html and src/share/misc/committers-doc.dot show that Murray Stokely is a doceng@ team member.

However, this commit (http://www.freebsd.org/cgi/cvsweb.cgi/www/en/             administration.sgml#rev1.28) shows that Murrary stepped down a while ago.

	
>How-To-Repeat:
	
>Fix:
See patches.

	

--- doceng.sgml.patch begins here ---
--- www/en/internal/doceng.sgml.orig	2009-11-11 12:34:12.888211558 +0800
+++ www/en/internal/doceng.sgml	2009-11-11 12:34:37.977538457 +0800
@@ -55,7 +55,7 @@
 <h2>Current Membership</h2>
 
 The current members of this team are Nik Clayton, Marc
-Fonvieille, Hiroki Sato, and Murray Stokely.  It is expected that the
+Fonvieille, Hiroki Sato, and Giorgos Keramidas.  It is expected that the
 membership of this list will increase as additional members from the
 various translation teams are added.
 
--- doceng.sgml.patch ends here ---

--- organization.dot.patch begins here ---
--- src/share/misc/organization.dot.orig	2009-11-11 12:36:21.723882626 +0800
+++ src/share/misc/organization.dot	2009-11-11 12:37:07.047471922 +0800
@@ -28,7 +28,7 @@
 core [label="Core Team\ncore@FreeBSD.org\nwilko, brooks, keramida, imp,\ngnn, wes, hrs, murray,\nrwatson"]
 coresecretary [label="Core Team Secretary\ncore-secretary@FreeBSD.org\njoel"]
 doccommitters [label="Doc/www Committers\ndoc-committers@FreeBSD.org"]
-doceng [label="Documentation Engineering Team\ndoceng@FreeBSD.org\nnik, blackend, hrs,\nmurray"]
+doceng [label="Documentation Engineering Team\ndoceng@FreeBSD.org\nnik, blackend, hrs,\nkeramida"]
 portscommitters [label="Ports Committers\nports-committers@FreeBSD.org"]
 portmgr [label="Port Management Team\nportmgr@FreeBSD.org\nmarcus, kris, erwin,\nlinimon, pav, krion"]
 portmgrsecretary [label="Port Management Team Secretary\nportmgr-secretary@FreeBSD.org\nerwin"]
--- organization.dot.patch ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From remko at FreeBSD.org  Wed Nov 11 08:43:39 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:43:44 2009
Subject: misc/140454: isblank(3) man-page grammar edit
Message-ID: <200911110843.nAB8hdjv016516@freefall.freebsd.org>

Synopsis: isblank(3) man-page grammar edit

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:43:38 UTC 2009
Responsible-Changed-Why: 
Over to maintainer.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140454
From remko at FreeBSD.org  Wed Nov 11 08:43:49 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:43:55 2009
Subject: misc/140455: Grammar fix for isgraph(3)
Message-ID: <200911110843.nAB8hn5j016603@freefall.freebsd.org>

Synopsis: Grammar fix for isgraph(3)

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:43:48 UTC 2009
Responsible-Changed-Why: 
Over to maintainer.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140455
From remko at FreeBSD.org  Wed Nov 11 08:44:03 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:44:20 2009
Subject: misc/14056: FreeBsd 3.3 Make world fails
Message-ID: <200911110844.nAB8i2Z0016702@freefall.freebsd.org>

Synopsis: FreeBsd 3.3 Make world fails

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:44:02 UTC 2009
Responsible-Changed-Why: 
Over to maintainer.

http://www.freebsd.org/cgi/query-pr.cgi?pr=14056
From remko at FreeBSD.org  Wed Nov 11 08:44:11 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:44:20 2009
Subject: ports/14057: new port: net/libunp
Message-ID: <200911110844.nAB8iA2s016791@freefall.freebsd.org>

Synopsis: new port: net/libunp

Responsible-Changed-From-To: freebsd-ports->freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:44:10 UTC 2009
Responsible-Changed-Why: 
Over to maintainer.

http://www.freebsd.org/cgi/query-pr.cgi?pr=14057
From remko at FreeBSD.org  Wed Nov 11 08:44:16 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:44:40 2009
Subject: ports/14058: new port: net/libunpipc
Message-ID: <200911110844.nAB8iFlR016878@freefall.freebsd.org>

Synopsis: new port: net/libunpipc

Responsible-Changed-From-To: freebsd-ports->freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:44:15 UTC 2009
Responsible-Changed-Why: 
Over to maintainer.

http://www.freebsd.org/cgi/query-pr.cgi?pr=14058
From remko at FreeBSD.org  Wed Nov 11 08:44:22 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:44:40 2009
Subject: ports/14059: New port: roottail-0.0.4B
Message-ID: <200911110844.nAB8iL7e016967@freefall.freebsd.org>

Synopsis: New port: roottail-0.0.4B

Responsible-Changed-From-To: freebsd-ports->freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:44:21 UTC 2009
Responsible-Changed-Why: 
Over to maintainer.

http://www.freebsd.org/cgi/query-pr.cgi?pr=14059
From remko at FreeBSD.org  Wed Nov 11 08:44:57 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:45:04 2009
Subject: misc/14056: FreeBsd 3.3 Make world fails
Message-ID: <200911110844.nAB8iv0Y017012@freefall.freebsd.org>

Synopsis: FreeBsd 3.3 Make world fails

Responsible-Changed-From-To: freebsd-doc->freebsd-bugs
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:44:45 UTC 2009
Responsible-Changed-Why: 
Typo, reassign to correct group

http://www.freebsd.org/cgi/query-pr.cgi?pr=14056
From remko at FreeBSD.org  Wed Nov 11 08:45:24 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:45:30 2009
Subject: ports/14057: new port: net/libunp
Message-ID: <200911110845.nAB8jOR9017108@freefall.freebsd.org>

Synopsis: new port: net/libunp

Responsible-Changed-From-To: freebsd-doc->freebsd-ports
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:45:03 UTC 2009
Responsible-Changed-Why: 
Reassign to ports.

http://www.freebsd.org/cgi/query-pr.cgi?pr=14057
From remko at FreeBSD.org  Wed Nov 11 08:45:42 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:45:49 2009
Subject: ports/14058: new port: net/libunpipc
Message-ID: <200911110845.nAB8jg6q017153@freefall.freebsd.org>

Synopsis: new port: net/libunpipc

Responsible-Changed-From-To: freebsd-doc->freebsd-ports
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:45:31 UTC 2009
Responsible-Changed-Why: 
Reassign to ports, typo.

http://www.freebsd.org/cgi/query-pr.cgi?pr=14058
From remko at FreeBSD.org  Wed Nov 11 08:46:05 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Nov 11 08:46:11 2009
Subject: ports/14059: New port: roottail-0.0.4B
Message-ID: <200911110846.nAB8k5TF017203@freefall.freebsd.org>

Synopsis: New port: roottail-0.0.4B

Responsible-Changed-From-To: freebsd-doc->freebsd-ports
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:45:46 UTC 2009
Responsible-Changed-Why: 
Reassign to ports, typo

http://www.freebsd.org/cgi/query-pr.cgi?pr=14059
From dfilter at FreeBSD.ORG  Wed Nov 11 09:00:06 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Wed Nov 11 09:00:15 2009
Subject: docs/140465: commit references a PR
Message-ID: <200911110900.nAB906mV025401@freefall.freebsd.org>

The following reply was made to PR docs/140465; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/140465: commit references a PR
Date: Wed, 11 Nov 2009 08:58:41 +0000 (UTC)

 roam        2009-11-11 08:58:28 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en/internal          doceng.sgml 
   Log:
   Update the information on the doceng@ team members - Murray Stokely
   stepped down some time ago, at about the same time as Giorgos Keramidas
   joining the team.
   
   PR:             140465
   Submitted by:   Denny Lin <dennylin93@cnmc32.hs.ntnu.edu.tw>
   
   Revision  Changes    Path
   1.14      +2 -2      www/en/internal/doceng.sgml
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
From roam at ringlet.net  Wed Nov 11 09:10:05 2009
From: roam at ringlet.net (Peter Pentchev)
Date: Wed Nov 11 09:10:14 2009
Subject: docs/140465: [UPDATE] Outdated doceng@ info in www and src
Message-ID: <200911110910.nAB9A4bh033526@freefall.freebsd.org>

The following reply was made to PR docs/140465; it has been noted by GNATS.

From: Peter Pentchev <roam@ringlet.net>
To: Denny Lin <dennylin93@cnmc32.hs.ntnu.edu.tw>
Cc: bugs-followup@FreeBSD.org
Subject: Re: docs/140465: [UPDATE] Outdated doceng@ info in www and src
Date: Wed, 11 Nov 2009 11:03:40 +0200

 --EVF5PPMfhYS0aIcm
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Wed, Nov 11, 2009 at 12:41:30PM +0800, Denny Lin wrote:
 >=20
 > >Number:         140465
 > >Category:       docs
 > >Synopsis:       [UPDATE] Outdated doceng@ info in www and src
 > >Originator:     Denny Lin
 > >Description:
 > Both http://www.freebsd.org/internal/doceng.html and
 > src/share/misc/committers-doc.dot show that Murray Stokely is
 > a doceng@ team member.
 >=20
 > However, this commit
 > (http://www.freebsd.org/cgi/cvsweb.cgi/www/en/administration.sgml#rev1.28)
 > shows that Murrary stepped down a while ago.
 
 Thanks for spotting this!
 
 Argh.  I committed the www/en/internal/doceng.sgml patch, but then it
 turned out that my commit privileges are not quite enough for the src/
 part.  I really should have thought about that before starting.
 
 Could some source committer apply the remaining part of the patch,
 the one that follows?
 
 > --- organization.dot.patch begins here ---
 > --- src/share/misc/organization.dot.orig	2009-11-11 12:36:21.723882626 +0=
 800
 > +++ src/share/misc/organization.dot	2009-11-11 12:37:07.047471922 +0800
 > @@ -28,7 +28,7 @@
 >  core [label=3D"Core Team\ncore@FreeBSD.org\nwilko, brooks, keramida, imp=
 ,\ngnn, wes, hrs, murray,\nrwatson"]
 >  coresecretary [label=3D"Core Team Secretary\ncore-secretary@FreeBSD.org\=
 njoel"]
 >  doccommitters [label=3D"Doc/www Committers\ndoc-committers@FreeBSD.org"]
 > -doceng [label=3D"Documentation Engineering Team\ndoceng@FreeBSD.org\nnik=
 , blackend, hrs,\nmurray"]
 > +doceng [label=3D"Documentation Engineering Team\ndoceng@FreeBSD.org\nnik=
 , blackend, hrs,\nkeramida"]
 >  portscommitters [label=3D"Ports Committers\nports-committers@FreeBSD.org=
 "]
 >  portmgr [label=3D"Port Management Team\nportmgr@FreeBSD.org\nmarcus, kri=
 s, erwin,\nlinimon, pav, krion"]
 >  portmgrsecretary [label=3D"Port Management Team Secretary\nportmgr-secre=
 tary@FreeBSD.org\nerwin"]
 > --- organization.dot.patch ends here ---
 
 G'luck,
 Peter
 
 --=20
 Peter Pentchev	roam@ringlet.net    roam@space.bg    roam@FreeBSD.org
 PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
 Key fingerprint	2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
 If wishes were fishes, the antecedent of this conditional would be true.
 
 --EVF5PPMfhYS0aIcm
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.13 (FreeBSD)
 
 iQIcBAEBCgAGBQJK+n3rAAoJEGUe77AlJ98TNE0P/1a86M5Ydr75yyXt609frKKm
 Xg5SB/IyHw9XCN3aWyyCz6TMNxcw1OC/hoHiDINPgdkqGKHAzhjU1dcL8/K5yI/3
 eeSeQrwDRUnWldgoTCcNNbXqtQgv/jQ8FTZ+05Fa9j3rbkDdfh46R/k0OZMW8dk8
 DT12EqVRL7BzK70iewpzknqK+foqGTQl9u22gkedQoaZYcxPsviniKKol8u92++Y
 4rdBLQfvp8F40BNfmuHdlU/ih7ZPZxQY+mnfT28vE0XtIrDM2dLkeuH7iVI8vdPM
 Y1ZwhyJ08R61QTPyvuQQofiTgIlBTocrsV/kedHbnFd0qOYoVqaW4vaRrRUC65Vh
 7kq/rc1F1G6Vygd+2E78KkIjuw71aT/ODVr3Wl0Wi93nv0Ooqi2J7URDabmS1MuF
 WucN8+JRGA80YsZjFmtgLa5eq0aE80ZFN8eK0ymLtG2s8IgKD6t2dcOv4ot72kTk
 FUgH9qZkir6RvyDLtl6uxY47cqOI+LA1RbVhV7tzPFZBl4XAMfdrB4+CB3ADtPmz
 tnNJd7UGsVYn2lrctPKIqXMvxShRpxIJwn9zwioBHsA8sNJL2whFSZPgJYKXjR0s
 r4cQiMPwVzxkhxDWnWrLCRAPzkDlOZjndo7VfJ6pA2DEcLyKM9TqQ1t/g+D3I2Tj
 AKJwC4AvetHDkBNTRlrV
 =0/be
 -----END PGP SIGNATURE-----
 
 --EVF5PPMfhYS0aIcm--
From roam at FreeBSD.org  Wed Nov 11 11:32:16 2009
From: roam at FreeBSD.org (roam@FreeBSD.org)
Date: Wed Nov 11 11:32:32 2009
Subject: misc/140454: isblank(3) man-page grammar edit
Message-ID: <200911111132.nABBWGnX064870@freefall.freebsd.org>

Synopsis: isblank(3) man-page grammar edit

State-Changed-From-To: open->patched
State-Changed-By: roam
State-Changed-When: Wed Nov 11 11:31:21 UTC 2009
State-Changed-Why: 
I've committed a similar change to -CURRENT, will merge it in two weeks.
Thanks for spotting this!


Responsible-Changed-From-To: freebsd-doc->roam
Responsible-Changed-By: roam
Responsible-Changed-When: Wed Nov 11 11:31:21 UTC 2009
Responsible-Changed-Why: 
MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140454
From roam at FreeBSD.org  Wed Nov 11 11:38:53 2009
From: roam at FreeBSD.org (roam@FreeBSD.org)
Date: Wed Nov 11 11:38:59 2009
Subject: docs/140465: [UPDATE] Outdated doceng@ info in www and src
Message-ID: <200911111138.nABBcrKo067600@freefall.freebsd.org>

Synopsis: [UPDATE] Outdated doceng@ info in www and src

State-Changed-From-To: open->patched
State-Changed-By: roam
State-Changed-When: Wed Nov 11 11:38:03 UTC 2009
State-Changed-Why: 
I've committed the organization.dot fix to -CURRENT, will merge it
in two weeks.
Again, thanks for spotting this!


Responsible-Changed-From-To: freebsd-doc->roam
Responsible-Changed-By: roam
Responsible-Changed-When: Wed Nov 11 11:38:03 UTC 2009
Responsible-Changed-Why: 
MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140465
From alexbestms at wwu.de  Wed Nov 11 16:10:01 2009
From: alexbestms at wwu.de (Alexander Best)
Date: Wed Nov 11 16:10:07 2009
Subject: docs/140474: signal(3) missing reference to NSIG
Message-ID: <200911111602.nABG2lxv077714@www.freebsd.org>


>Number:         140474
>Category:       docs
>Synopsis:       signal(3) missing reference to NSIG
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 11 16:10:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Alexander Best
>Release:        9.0-CURRENT
>Organization:
>Environment:
FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r199160M: Wed Nov 11 00:33:45 CET 2009     root@otaku:/usr/obj/usr/src/sys/ARUNDEL  i386
>Description:
signal(3) should mention the existence NSIG and that it's assigned the highest signal number available. this note should probably also include a hint to developers that NSIG shouldn't be used to cycle through all signals, assigning them to SIG_IGN e.g.

alex
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From linimon at FreeBSD.org  Wed Nov 11 17:24:37 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Nov 11 17:24:49 2009
Subject: docs/140456: [patch] Grammar fix for isprint(3)
Message-ID: <200911111724.nABHOafj067029@freefall.freebsd.org>

Old Synopsis: Grammar fix for isprint(3)
New Synopsis: [patch] Grammar fix for isprint(3)

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Nov 11 17:24:16 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=140456
From linimon at FreeBSD.org  Wed Nov 11 17:25:01 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Nov 11 17:25:08 2009
Subject: docs/140457: [patch] Grammar fix for isspace(3)
Message-ID: <200911111725.nABHP0GA067078@freefall.freebsd.org>

Old Synopsis: Grammar fix for isspace(3)
New Synopsis: [patch] Grammar fix for isspace(3)

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Nov 11 17:24:41 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=140457
From linimon at FreeBSD.org  Wed Nov 11 17:25:21 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Nov 11 17:25:28 2009
Subject: docs/140458: [patch] Grammar fix for to{upper,lower}(3)
Message-ID: <200911111725.nABHPLqi067131@freefall.freebsd.org>

Old Synopsis: Grammar fix for to{upper,lower}(3)
New Synopsis: [patch] Grammar fix for to{upper,lower}(3)

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Nov 11 17:25:04 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=140458
From linimon at FreeBSD.org  Wed Nov 11 17:25:41 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Nov 11 17:25:53 2009
Subject: docs/140459: [patch] Grammar fix for nl_langinfo(3)
Message-ID: <200911111725.nABHPfhU067176@freefall.freebsd.org>

Old Synopsis: Grammar fix for nl_langinfo(3)
New Synopsis: [patch] Grammar fix for nl_langinfo(3)

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Nov 11 17:25:24 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=140459
From jhelfman at e-e.com  Wed Nov 11 19:10:01 2009
From: jhelfman at e-e.com (Jason Helfman)
Date: Wed Nov 11 19:10:11 2009
Subject: docs/140490: Add custom kernel information to Release Engineering
	Article
Message-ID: <200911111905.nABJ5eQK001189@www.freebsd.org>


>Number:         140490
>Category:       docs
>Synopsis:       Add custom kernel information to Release Engineering Article
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 11 19:10:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Jason Helfman
>Release:        FreeBSD 7.2
>Organization:
Experts Exchange
>Environment:
FreeBSD eggman.experts-exchange.com 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct  2 12:21:39 UTC 2009     root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
Add custom kernel instructions to Releng Article.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- article.sgml.orig	2009-06-24 15:25:26.000000000 -0700
+++ article.sgml	2009-11-11 11:01:26.000000000 -0800
@@ -798,6 +798,17 @@
         should be made bootable so that users of modern PCs do not
         need to create installation floppy disks.</para>
 
+      <para>If a custom kernel of &os; is to be included, then
+        &man.sysinstall.8; and &man.release.7; must be updated to
+        include installation instructions. The relevant code is contained
+        in <filename>src/release</filename> and <filename>src/usr.sbin/sysinstall</filename>.
+        Specifically, the file <filename>src/release/Makefile</filename>, and 
+        <filename>dist.c</filename>, <filename>dist.h</filename>,
+        <filename>menus.c</filename>, <filename>install.c</filename>, and 
+        <filename>Makefile</filename> will need to be updated under
+        <filename>src/usr.sbin/sysinstall</filename>.  Optionally, you may choose 
+        to update <filename>sysinstall.8</filename>.</para>
+
       <para>If an alternate version of &xfree86; is to be provided, then
         &man.sysinstall.8; must be updated to reflect the new location
         and installation instructions. The relevant code is contained


>Release-Note:
>Audit-Trail:
>Unformatted:
From linimon at FreeBSD.org  Wed Nov 11 23:28:14 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Nov 11 23:28:26 2009
Subject: docs/140494: [patch] Man page fix for getc(3)
Message-ID: <200911112328.nABNSDPe077487@freefall.freebsd.org>

Old Synopsis: Man page fix for getc(3)
New Synopsis: [patch] Man page fix for getc(3)

Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Nov 11 23:27:20 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=140494
From tom at tomjudge.com  Thu Nov 12 00:20:02 2009
From: tom at tomjudge.com (Tom Judge)
Date: Thu Nov 12 00:20:08 2009
Subject: docs/140495: /etc/rc.conf.d is not documented in rc.conf(5)
Message-ID: <200911120013.nAC0DgY1070788@www.freebsd.org>


>Number:         140495
>Category:       docs
>Synopsis:       /etc/rc.conf.d is not documented in rc.conf(5)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 12 00:20:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Tom Judge
>Release:        9-Current
>Organization:
Mintel International Ltd
>Environment:
FreeBSD rita.nodomain 9.0-CURRENT FreeBSD 9.0-CURRENT #5 r197472M: Thu Sep 24 21:09:49 UTC 2009     root@rita.nodomain:/usr/obj/usr/src/sys/ME  i386

>Description:
There is no reference to /etc/rc.conf.d in rc.conf(5).

The patch adds info about that dir.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

Index: rc.conf.5
===================================================================
--- rc.conf.5	(revision 199205)
+++ rc.conf.5	(working copy)
@@ -63,7 +63,11 @@
 .Pa /etc/rc.conf.local
 is used to override settings in
 .Pa /etc/rc.conf
-for historical reasons.
+for historical reasons. In addition to 
+.Pa /etc/rc.conf.local
+you can also place smaller config files in the directory
+.Pa /etc/rc.conf.d
+which will be included by rc.subr's load_rc_config function.
 See the
 .Va rc_conf_files
 variable below.


>Release-Note:
>Audit-Trail:
>Unformatted:
From jamieken at sify.com  Thu Nov 12 00:21:43 2009
From: jamieken at sify.com (Mr Calab)
Date: Thu Nov 12 00:21:54 2009
Subject: CONTACT MONEYGRAM FOR YOUR $7,000.00
Message-ID: <200911120021.nAC0Leg6025396@beastie01.server.web3.nl>

THIS IS OUR CONDUCT CODE ( 303)
Welcome to money gram Send Money Worldwide
FROM OFFICE OF THE MONEY GRAM MONEY TRANSFER.
COTONOU, BENIN REPUBLIC /ADDRESS 455 AGBOKOU,ANKPA
ROAD OPPOSITE TUNED MOTORS COTONOU
WEB:https://www.moneygram.com   
EMAIL:(emoneygram@hotmail.com)
 
 Attn :Beneficiary,
This is to notify all our customers about the latest development concerning all the payment that are left in our custody,which yours are inclusive Besides, yours where given a bill of $435,in order to receive your payment of
which we didn嚙緣 hear from you for sometime now....Hence, our money gram  is now offering a Special BONUS to help all our customers that are having their payment  in our custody due to of prices. In order words we are now
requesting that those involve should pay only the sum of $100.00 to receive all their payment abandoned in our custody.
 
Besides, my dear, this is the opportunity for you and have to comply and your funds  shall be transfer to your designated address.But remember that after (3 DAYS) you did not make the payment then we will divert your funds to Government Fund, to avoid problem or we will cancel the payment for this year until next year  because this year is not like last year.
 
Again after (THREE DAYS ) We will enter A new project  for the year and that is the reason why we decided to help to all our customers before we enter into the new project.So be  advise to send the $100.00 immediately so that we will register your payment and for to start receive $7000.00 as from tomorrow. Be advise that there is no time again for we to call any person on phone unless you will call 0022998836885
After the payment of $100.00 you will start receiving your money every day $7000.00 through money gram and Western Union $7000.00 by western union until the full payment of $1.9m is completed. So what you will be receiving per day is $14,000.00
 
Beneficiary name----------------------------
Address--------------------------------
Telephone-----------------------------
occupation.......................
country......................
sex...........................
Contact me with this informations below:
CONTACT PERSON: MR.CHUKWU JOHN.
TEL: 0022998836885
EMAIL:(emoneygram@hotmail.com or moneygramm@sify.com)
Send the money through Western Union Money Transfer with the
information below:
RECEIVER NAME:.....NWABUNWANNE JAMES.
COUNTRY............. Cotonou, Benin Republic
Text Question...... In God
Answer...............We Trust.
Amount...............$100.
The moment i receive the payment of $100 i will release the first
payment informations of $7000.00 to you and you will pick up the money
and i will send you another money. Hoping to hear from you.
Please,contact MR.CHUKWU JOHN,for the transfer charge above
MR.CHUKWU JOHN.
FOREIGN OPERATION MANAGER
MONEYGRAM OFFICE
THIS IS OUR CONDUCT CODE ( 303)



From tom at tomjudge.com  Thu Nov 12 00:47:45 2009
From: tom at tomjudge.com (Tom Judge)
Date: Thu Nov 12 00:47:52 2009
Subject: docs/140495: /etc/rc.conf.d is not documented in rc.conf(5)
In-Reply-To: <200911120020.nAC0K16T020860@freefall.freebsd.org>
References: <200911120020.nAC0K16T020860@freefall.freebsd.org>
Message-ID: <4AFB5693.6070701@tomjudge.com>

Here is a better more accurate patch.

-------------- next part --------------
Index: rc.conf.5
===================================================================
--- rc.conf.5	(revision 199205)
+++ rc.conf.5	(working copy)
@@ -63,8 +63,16 @@
 .Pa /etc/rc.conf.local
 is used to override settings in
 .Pa /etc/rc.conf
-for historical reasons.
-See the
+for historical reasons. In addition to 
+.Pa /etc/rc.conf.local
+you can also place smaller configuration files for each rc script in 
+the directory
+.Pa /etc/rc.conf.d
+which will be included by the 
+.Va load_rc_config 
+function. For jail configuration you would use the file
+.Pa /etc/rc.conf.d/jail
+to store jail specific configuration options. Also see the
 .Va rc_conf_files
 variable below.
 .Pp
From tom at tomjudge.com  Thu Nov 12 00:50:04 2009
From: tom at tomjudge.com (Tom Judge)
Date: Thu Nov 12 00:50:10 2009
Subject: docs/140495: /etc/rc.conf.d is not documented in rc.conf(5)
Message-ID: <200911120050.nAC0o3Y9046865@freefall.freebsd.org>

The following reply was made to PR docs/140495; it has been noted by GNATS.

From: Tom Judge <tom@tomjudge.com>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org
Cc:  
Subject: Re: docs/140495: /etc/rc.conf.d is not documented in rc.conf(5)
Date: Thu, 12 Nov 2009 00:28:03 +0000

 This is a multi-part message in MIME format.
 --------------080900080505060605010203
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
 Content-Transfer-Encoding: 7bit
 
 Here is a better more accurate patch.
 
 
 --------------080900080505060605010203
 Content-Type: text/plain;
  name="rc.conf.5.txt"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline;
  filename="rc.conf.5.txt"
 
 Index: rc.conf.5
 ===================================================================
 --- rc.conf.5	(revision 199205)
 +++ rc.conf.5	(working copy)
 @@ -63,8 +63,16 @@
  .Pa /etc/rc.conf.local
  is used to override settings in
  .Pa /etc/rc.conf
 -for historical reasons.
 -See the
 +for historical reasons. In addition to 
 +.Pa /etc/rc.conf.local
 +you can also place smaller configuration files for each rc script in 
 +the directory
 +.Pa /etc/rc.conf.d
 +which will be included by the 
 +.Va load_rc_config 
 +function. For jail configuration you would use the file
 +.Pa /etc/rc.conf.d/jail
 +to store jail specific configuration options. Also see the
  .Va rc_conf_files
  variable below.
  .Pp
 
 --------------080900080505060605010203--
From murray at stokely.org  Thu Nov 12 02:50:05 2009
From: murray at stokely.org (Murray Stokely)
Date: Thu Nov 12 02:50:10 2009
Subject: docs/140490: Add custom kernel information to Release
	Engineering Article
Message-ID: <200911120250.nAC2o4mW049234@freefall.freebsd.org>

The following reply was made to PR docs/140490; it has been noted by GNATS.

From: Murray Stokely <murray@stokely.org>
To: Jason Helfman <jhelfman@e-e.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: docs/140490: Add custom kernel information to Release Engineering 
	Article
Date: Wed, 11 Nov 2009 18:19:58 -0800

 This looks like a good change to me.  Thanks for the submission.
 
          - Murray
 
 
 On Wed, Nov 11, 2009 at 11:05 AM, Jason Helfman <jhelfman@e-e.com> wrote:
 >
 >>Number: =A0 =A0 =A0 =A0 140490
 >>Category: =A0 =A0 =A0 docs
 >>Synopsis: =A0 =A0 =A0 Add custom kernel information to Release Engineerin=
 g Article
 >>Confidential: =A0 no
 >>Severity: =A0 =A0 =A0 non-critical
 >>Priority: =A0 =A0 =A0 low
 >>Responsible: =A0 =A0freebsd-doc
 >>State: =A0 =A0 =A0 =A0 =A0open
 >>Quarter:
 >>Keywords:
 >>Date-Required:
 >>Class: =A0 =A0 =A0 =A0 =A0change-request
 >>Submitter-Id: =A0 current-users
 >>Arrival-Date: =A0 Wed Nov 11 19:10:01 UTC 2009
 >>Closed-Date:
 >>Last-Modified:
 >>Originator: =A0 =A0 Jason Helfman
 >>Release: =A0 =A0 =A0 =A0FreeBSD 7.2
 >>Organization:
 > Experts Exchange
 >>Environment:
 > FreeBSD eggman.experts-exchange.com 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4=
  #0: Fri Oct =A02 12:21:39 UTC 2009 =A0 =A0 root@i386-builder.daemonology.n=
 et:/usr/obj/usr/src/sys/GENERIC =A0i386
 >>Description:
 > Add custom kernel instructions to Releng Article.
 >>How-To-Repeat:
 >
 >>Fix:
 >
 >
 > Patch attached with submission follows:
 >
 > --- article.sgml.orig =A0 2009-06-24 15:25:26.000000000 -0700
 > +++ article.sgml =A0 =A0 =A0 =A02009-11-11 11:01:26.000000000 -0800
 > @@ -798,6 +798,17 @@
 > =A0 =A0 =A0 =A0 should be made bootable so that users of modern PCs do no=
 t
 > =A0 =A0 =A0 =A0 need to create installation floppy disks.</para>
 >
 > + =A0 =A0 =A0<para>If a custom kernel of &os; is to be included, then
 > + =A0 =A0 =A0 =A0&man.sysinstall.8; and &man.release.7; must be updated t=
 o
 > + =A0 =A0 =A0 =A0include installation instructions. The relevant code is =
 contained
 > + =A0 =A0 =A0 =A0in <filename>src/release</filename> and <filename>src/us=
 r.sbin/sysinstall</filename>.
 > + =A0 =A0 =A0 =A0Specifically, the file <filename>src/release/Makefile</f=
 ilename>, and
 > + =A0 =A0 =A0 =A0<filename>dist.c</filename>, <filename>dist.h</filename>=
 ,
 > + =A0 =A0 =A0 =A0<filename>menus.c</filename>, <filename>install.c</filen=
 ame>, and
 > + =A0 =A0 =A0 =A0<filename>Makefile</filename> will need to be updated un=
 der
 > + =A0 =A0 =A0 =A0<filename>src/usr.sbin/sysinstall</filename>. =A0Optiona=
 lly, you may choose
 > + =A0 =A0 =A0 =A0to update <filename>sysinstall.8</filename>.</para>
 > +
 > =A0 =A0 =A0 <para>If an alternate version of &xfree86; is to be provided,=
  then
 > =A0 =A0 =A0 =A0 &man.sysinstall.8; must be updated to reflect the new loc=
 ation
 > =A0 =A0 =A0 =A0 and installation instructions. The relevant code is conta=
 ined
 >
 >
 >>Release-Note:
 >>Audit-Trail:
 >>Unformatted:
 > _______________________________________________
 > freebsd-doc@freebsd.org mailing list
 > http://lists.freebsd.org/mailman/listinfo/freebsd-doc
 > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"
 >
From brde at optusnet.com.au  Thu Nov 12 14:30:11 2009
From: brde at optusnet.com.au (Bruce Evans)
Date: Thu Nov 12 14:30:17 2009
Subject: misc/140494: Man page fix for getc(3)
Message-ID: <200911121430.nACEUAGx093563@freefall.freebsd.org>

The following reply was made to PR docs/140494; it has been noted by GNATS.

From: Bruce Evans <brde@optusnet.com.au>
To: Jeremy Huddleston <jeremyhu@apple.com>
Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: misc/140494: Man page fix for getc(3)
Date: Fri, 13 Nov 2009 01:29:46 +1100 (EST)

 On Wed, 11 Nov 2009, Jeremy Huddleston wrote:
 
 >> Fix:
 > --- getc.3.bsdnew	2009-11-11 13:33:11.000000000 -0800
 > +++ getc.3	2009-11-11 14:52:54.000000000 -0800
 > @@ -54,7 +54,7 @@
 > .Ft int
 > .Fn getc_unlocked "FILE *stream"
 > .Ft int
 > -.Fn getchar void
 > +.Fn getchar "void"
 
 This adds bogus quoting.
 
 > .Ft int
 > .Fn getchar_unlocked "void"
 
 It should remove this bogus quoting.
 
 > .Ft int
 
 Bogus quoting of "void" is used in about 1100 lines in section 3
 man pages (counting links multiply).  It is most common in man pages
 for software that doesn't use anything resembling BSD style (e.g.,
 VGL, archive, dialog and, readline account for about 2/3 of the 1100
 lines).
 
 Bruce
From fefo at gmail.com  Fri Nov 13 01:10:01 2009
From: fefo at gmail.com (Martin Baumann)
Date: Fri Nov 13 01:10:08 2009
Subject: docs/140520: Maybe mistake in description of networks in
	documentation
Message-ID: <200911130102.nAD12u2D099135@www.freebsd.org>


>Number:         140520
>Category:       docs
>Synopsis:       Maybe mistake in description of networks in documentation
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Nov 13 01:10:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Martin Baumann
>Release:        FreeBSD8-RC2
>Organization:
>Environment:
>Description:
Here 
http://www.freebsd.org/doc/en/articles/checkpoint/article.html

Chapter 1 - Prerequisites
On the picture there are protected network and internal network the same.
I think they shouldn't be. That internal network I think should be: 192.168.10.0/24




Thats all I've found right now.
>How-To-Repeat:

>Fix:
Change internal network to: 192.168.10.0/24


>Release-Note:
>Audit-Trail:
>Unformatted:
From roam at FreeBSD.org  Fri Nov 13 08:52:33 2009
From: roam at FreeBSD.org (roam@FreeBSD.org)
Date: Fri Nov 13 08:52:39 2009
Subject: docs/140520: Maybe mistake in description of networks in
	checkpoint article
Message-ID: <200911130852.nAD8qXoO082671@freefall.freebsd.org>

Synopsis: Maybe mistake in description of networks in checkpoint article

State-Changed-From-To: open->closed
State-Changed-By: roam
State-Changed-When: Fri Nov 13 08:51:44 UTC 2009
State-Changed-Why: 
I corrected the image as per your description.  Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=140520
From dfilter at FreeBSD.ORG  Fri Nov 13 09:00:13 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Fri Nov 13 09:00:20 2009
Subject: docs/140520: commit references a PR
Message-ID: <200911130900.nAD907co082817@freefall.freebsd.org>

The following reply was made to PR docs/140520; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/140520: commit references a PR
Date: Fri, 13 Nov 2009 08:51:23 +0000 (UTC)

 roam        2009-11-13 08:51:10 UTC
 
   FreeBSD doc repository
 
   Modified files:
     share/images/articles/checkpoint networks.pic 
   Log:
   Correct the address space of the internal network in the Checkpoint article.
   
   PR:             140520
   Submitted by:   Martin Baumann <fefo@gmail.com>
   
   Revision  Changes    Path
   1.2       +1 -1      doc/share/images/articles/checkpoint/networks.pic
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
From roam at FreeBSD.org  Fri Nov 13 09:05:37 2009
From: roam at FreeBSD.org (roam@FreeBSD.org)
Date: Fri Nov 13 09:05:43 2009
Subject: docs/140455: [patch] Grammar fix for isgraph(3)
Message-ID: <200911130905.nAD95axx090878@freefall.freebsd.org>

Synopsis: [patch] Grammar fix for isgraph(3)

State-Changed-From-To: open->patched
State-Changed-By: roam
State-Changed-When: Fri Nov 13 09:03:59 UTC 2009
State-Changed-Why: 
I committed half of your fix - the dash; I don't think the comma is really
suitable here.  Thanks for spotting this!
I'll merge the change into the stable branches in two weeks' time.


Responsible-Changed-From-To: freebsd-doc->roam
Responsible-Changed-By: roam
Responsible-Changed-When: Fri Nov 13 09:03:59 UTC 2009
Responsible-Changed-Why: 
MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140455
From roam at FreeBSD.org  Fri Nov 13 09:08:23 2009
From: roam at FreeBSD.org (roam@FreeBSD.org)
Date: Fri Nov 13 09:08:29 2009
Subject: docs/140456: [patch] Grammar fix for isprint(3)
Message-ID: <200911130908.nAD98Nj2090960@freefall.freebsd.org>

Synopsis: [patch] Grammar fix for isprint(3)

State-Changed-From-To: open->patched
State-Changed-By: roam
State-Changed-When: Fri Nov 13 09:07:53 UTC 2009
State-Changed-Why: 
I've committed your fix, will merge to stable in two weeks' time.
Thanks for spotting this!


Responsible-Changed-From-To: freebsd-doc->roam
Responsible-Changed-By: roam
Responsible-Changed-When: Fri Nov 13 09:07:53 UTC 2009
Responsible-Changed-Why: 
MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140456
From remko at FreeBSD.org  Fri Nov 13 10:21:39 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Fri Nov 13 10:21:47 2009
Subject: docs/140490: [patch] Add custom kernel information to Release
	Engineering Article
Message-ID: <200911131021.nADALdHc037845@freefall.freebsd.org>

Synopsis: [patch] Add custom kernel information to Release Engineering Article

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Fri Nov 13 10:21:38 UTC 2009
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=140490
From dfilter at FreeBSD.ORG  Fri Nov 13 10:30:04 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Fri Nov 13 10:30:10 2009
Subject: docs/140490: commit references a PR
Message-ID: <200911131030.nADAU2cl038099@freefall.freebsd.org>

The following reply was made to PR docs/140490; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/140490: commit references a PR
Date: Fri, 13 Nov 2009 10:21:43 +0000 (UTC)

 remko       2009-11-13 10:21:30 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en_US.ISO8859-1/articles/releng article.sgml 
   Log:
   Add information about custom kernels.
   
   PR:             140490
   Submitted by:   Jason Helfman <jhelfman at e-e dot com>
   Glanced at:     murray
   
   Revision  Changes    Path
   1.84      +11 -0     doc/en_US.ISO8859-1/articles/releng/article.sgml
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
From Rhubbell at iHubbell.com  Sun Nov 15 05:23:49 2009
From: Rhubbell at iHubbell.com (rhubbell)
Date: Sun Nov 15 05:23:55 2009
Subject: no US anoncvs
Message-ID: <20091114205923.9f624320.Rhubbell@iHubbell.com>


Seems like this docs needs to be revised, unless it's a coincidence that
both US anoncvs servers are down

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/anoncvs.html

I tried these, but have resorted to using the fr server.

anoncvs.FreeBSD.org
anoncvs1.FreeBSD.org
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Sun Nov 15 12:30:54 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Sun Nov 15 12:31:00 2009
Subject: Translation of FreeBSD Documentation
Message-ID: <20091115121113.GA21434@mx.hs.ntnu.edu.tw>

Hi, I intend to work on the Traditional Chinese translations of the
FreeBSD documentation, and I'm wondering if anyone else is working on it
at the moment. It seems to be inactive since the last commits were
roughly 2 to 3 years ago.

I have a few questions regarding the Traditional Chinese
translations, so I thought it might be better to ask before starting.

-- 
Denny Lin
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Sun Nov 15 13:00:05 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Sun Nov 15 13:00:15 2009
Subject: docs/140568: [UPDATE] Outdated Perl info in Developers' Handbook
Message-ID: <20091115125156.3615D6FC450@mx.hs.ntnu.edu.tw>


>Number:         140568
>Category:       docs
>Synopsis:       [UPDATE] Outdated Perl info in Developers' Handbook
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 15 13:00:03 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Denny Lin
>Release:        FreeBSD 7.2-RELEASE-p4 amd64
>Organization:
>Environment:
System: FreeBSD cnmc32.hs.ntnu.edu.tw 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Mon Oct 26 19:41:45 CST 2009 root@cnmc32.hs.ntnu.edu.tw:/usr/obj/usr/src/sys/CNMC32 amd64


	
>Description:
The Perl port (lang/perl5) specified in the Developers' Handbook no longer exists. It should be replaced with lang/perl5.8, the current default version of Perl.
	
>How-To-Repeat:
	
>Fix:
Patch (sed 's/perl5/perl5.8/g').

	

--- developers-handbook-tools-chapter.sgml.patch begins here ---
--- doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml.orig	2009-11-15 20:45:01.744614861 +0800
+++ doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml	2009-11-15 20:45:15.176791625 +0800
@@ -184,7 +184,7 @@
 	      writing <acronym>CGI</acronym> scripts.</para>
 
 	    <para>Perl is available in the Ports Collection as 
-	      <filename role="package">lang/perl5</filename> for all
+	      <filename role="package">lang/perl5.8</filename> for all
 	      &os; releases, and is installed as <command>/usr/bin/perl</command>
 	      in the base system 4.X releases.</para>
 	  </listitem>
--- developers-handbook-tools-chapter.sgml.patch ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Sun Nov 15 13:10:02 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Sun Nov 15 13:10:09 2009
Subject: docs/140569: [UPDATE] Updated info about Tcl in Developers' Handbook
Message-ID: <20091115130004.4CA396FC450@mx.hs.ntnu.edu.tw>


>Number:         140569
>Category:       docs
>Synopsis:       [UPDATE] Updated info about Tcl in Developers' Handbook
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 15 13:10:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Denny Lin
>Release:        FreeBSD 7.2-RELEASE-p4 amd64
>Organization:
>Environment:
System: FreeBSD cnmc32.hs.ntnu.edu.tw 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Mon Oct 26 19:41:45 CST 2009 root@cnmc32.hs.ntnu.edu.tw:/usr/obj/usr/src/sys/CNMC32 amd64


	
>Description:
Sorry, I should have included this in the previous PR I sent about Perl, but I didn't notice this problem until the PR had already been sent.

The latest stable of version is now Tcl 8.5.
	
>How-To-Repeat:
	
>Fix:
Patch.

	

--- tcl.patch begins here ---
--- doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml.orig	2009-11-15 20:55:53.412210016 +0800
+++ doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml	2009-11-15 20:56:09.544424044 +0800
@@ -284,8 +284,8 @@
 	      programs.</para>
 
 	    <para>Various versions of Tcl are available as ports 
-	      for &os;.  The latest version, Tcl 8.4, can be found in
-	      <filename role="package">lang/tcl84</filename>.</para>
+	      for &os;.  The latest version, Tcl 8.5, can be found in
+	      <filename role="package">lang/tcl85</filename>.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
--- tcl.patch ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From jhelfman at e-e.com  Sun Nov 15 19:40:02 2009
From: jhelfman at e-e.com (Jason Helfman)
Date: Sun Nov 15 19:40:09 2009
Subject: docs/140581: Link to Poly link doesn't work. Found a suitable
	replacement and named the full University. Go Poly.
Message-ID: <200911151934.nAFJYr16098111@www.freebsd.org>


>Number:         140581
>Category:       docs
>Synopsis:       Link to Poly link doesn't work. Found a suitable replacement and named the full University. Go Poly.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 15 19:40:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Jason Helfman
>Release:        FreeBSD 7.2-RELEASE-p4
>Organization:
Experts Exchange
>Environment:
FreeBSD 7.2-RELEASE-p4
>Description:
A bad reference link.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml.old	2009-11-15 11:15:51.000000000 -0800
+++ en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml	2009-11-15 11:19:20.000000000 -0800
@@ -483,7 +483,7 @@
 	<itemizedlist>
 	  <listitem>
 	    <para><ulink 
-		url="http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/">CVS Tutorial</ulink> from Cal Poly.</para>
+		url="http://users.csc.calpoly.edu/~gfisher/classes/205/handouts/cvs-basics.html">CVS Tutorial</ulink> from California Polytechnic State University.</para>
 	  </listitem>
 
 	  <listitem>


>Release-Note:
>Audit-Trail:
>Unformatted:
From jhelfman at e-e.com  Sun Nov 15 21:46:39 2009
From: jhelfman at e-e.com (Jason)
Date: Sun Nov 15 21:46:46 2009
Subject: bsdmag.org link placement
Message-ID: <20091115214610.GA17485@jason-helfmans-macbook-pro.local>

Hi

I was wondering where a link I would like to submit for BSD Magazine, would
be most appropriate?

It isn't specifically FreeBSD, however it is specific to all BSD's, so I
was thinking of putting under "International book & Magazines" found here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bibliography.html#BIBLIOGRAPHY-FREEBSD

or perhaps, here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bibliography-journals.html

Beyond this, I don't see the need for that latter link, as it could be
condensed into the first, and renamed. That is another path, though.

Any thoughts?

Thanks,
Jason
From gabor at FreeBSD.org  Sun Nov 15 23:09:33 2009
From: gabor at FreeBSD.org (gabor@FreeBSD.org)
Date: Sun Nov 15 23:09:39 2009
Subject: docs/140418: [patch] articles/custom-gcc: russian translation
	is missing
Message-ID: <200911152309.nAFN9XR1055792@freefall.freebsd.org>

Synopsis: [patch] articles/custom-gcc: russian translation is missing

State-Changed-From-To: open->closed
State-Changed-By: gabor
State-Changed-When: Sun Nov 15 23:09:13 UTC 2009
State-Changed-Why: 
Committed, thanks.


Responsible-Changed-From-To: freebsd-doc->gabor
Responsible-Changed-By: gabor
Responsible-Changed-When: Sun Nov 15 23:09:13 UTC 2009
Responsible-Changed-Why: 
Committed, thanks.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140418
From dirk.meyer at dinoex.sub.org  Mon Nov 16 06:00:07 2009
From: dirk.meyer at dinoex.sub.org (dirk.meyer@dinoex.sub.org)
Date: Mon Nov 16 06:00:13 2009
Subject: docs/140594: getprogname.3 misleading
Message-ID: <200911160556.nAG5uCec061860@home3.dinoex.sub.de>


>Number:         140594
>Category:       docs
>Synopsis:       getprogname.3 misleading
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 16 06:00:06 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Dirk Meyer
>Release:        FreeBSD 8.0-PRERELEASE
>Organization:
privat
>Environment:

FreeBSD libc manpage section 3.

>Description:

The manpage of getprogname seemms to contain an error.

[...]
     In FreeBSD, the name of the program is set by the start-up code that is
     run before main(); thus, running setprogname() is not necessary.  Pro-
     grams that desire maximum portability should still call it; on another
     operating system, these functions may be implemented in a portability
     library.  Calling setprogname() allows the aforementioned library to
     learn the program name without modifications to the start-up code.
[...]

I think the last part should be: 

Calling getprogname() allows  ...

>How-To-Repeat:

http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/gen/getprogname.3
man getprogname

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org  Mon Nov 16 11:06:08 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov 16 11:06:40 2009
Subject: Current unassigned doc problem reports
Message-ID: <200911161106.nAGB670Q010479@freefall.freebsd.org>

(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .)

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/140594  doc        getprogname.3 misleading
o docs/140581  doc        [mirrors] [patch] Link to Poly link doesn't work. Foun
o docs/140569  doc        [UPDATE] Updated info about Tcl in Developers' Handboo
o docs/140568  doc        [UPDATE] Outdated Perl info in Developers' Handbook
o docs/140495  doc        [patch] /etc/rc.conf.d is not documented in rc.conf(5)
o docs/140494  doc        [patch] Man page fix for getc(3)
o docs/140474  doc        signal(3) missing reference to NSIG
o docs/140459  doc        [patch] Grammar fix for nl_langinfo(3)
o docs/140458  doc        [patch] Grammar fix for to{upper,lower}(3)
o docs/140457  doc        [patch] Grammar fix for isspace(3)
o docs/140444  doc        [patch] New Traditional Chinese translation of custom-
o docs/140435  doc        man ls, section STANDARD: the -A is exception from POS
o docs/140375  doc        [UPDATE] Updated zh_TW.Big5/articles/nanobsd
o docs/140369  doc        [patch] src/contrib/pf/man/pf.4
o docs/140082  doc        handbook/jails: russian translation is missing
o docs/140075  doc        release notes: missing word "NOT", which changes all t
o docs/139682  doc        [PATCH] dialog(1) man page does not mention radiolist 
o docs/139603  doc        [patch] Clarify subpixel smoothing for fonts in Handbo
p docs/139370  doc        [PATCH] de(4) manual page typo
o docs/139336  doc        ZFS documentation suggestion
o docs/139165  doc        gssapi.3 man page out of sync with between crypto and 
o docs/139153  doc        the hier(7) man page needs to be updated
o docs/139018  doc        translation of submitting.sgml from docproj/submitting
o docs/138887  doc        manpage ports(7) incorrect
o docs/138845  doc        Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138663  doc        system(3) man page confuses users about "return value 
o docs/138485  doc        bpf(4) and ip(4) man pages missing important corner ca
o docs/138206  doc        [patch] ntp(1): not enabled function, and false manual
o docs/137762  doc        [handbook] proposed: mention "make delete-old" in sec 
o docs/137171  doc        [patch] replacement of k8temp(4) by amdtemp(4) isn't r
o docs/136918  doc        [patch] grammar fixes to locking.9
o docs/136712  doc        [handbook] [patch] draft new section on gmirror per pa
o docs/136666  doc        [handbook] Configure serial port for remote kernel deb
o docs/136100  doc        change FreeBSD Ports distfiles survey's url to portsco
o docs/136035  doc        ftpchroot(5) omits an important option
p docs/136029  doc        MALLOC_PRODUCTION knob should be mentioned somewhere, 
o docs/135999  doc        Netgear GS105v3 should be added to list of switches th
o docs/135676  doc        FAQ About The FreeBSD Mailing Lists doesn't mention ma
o docs/135516  doc        pax(1) manual not mentioning chflags unawareness
o docs/135475  doc        [patch] jot(1) manpage and behaviour differ
o docs/135165  doc        [patch] make(1) fixes: punctuation, typos, tweaks
o docs/134376  doc        pthread(3): pthread manpages don't mention that PTHREA
o docs/134226  doc        /usr/share/examples/ftpd/ftpd.conf does not exist.
o docs/134222  doc        installation failure of japanese docs
o docs/134123  doc        The RUNQUEUE(9) man page is out of date
o docs/134074  doc        [patch] locking.9 man page slight enhancements
o docs/133567  doc        [patch] doc/Makefile switch to csup
o docs/133245  doc        french handbook 27.3.5 amd.map amd.conf
o docs/133228  doc        handbook 23.3.5 screenmap section is confusing
o docs/133186  doc        [patch] powerd(8) man page errors
o docs/133118  doc        [patch] Error in getopt (1) manual EXAMPLES section
o docs/132959  doc        [patch] description mismatches on xterm/termcap, fortu
o docs/132884  doc        [request] No manpage for SYSINIT and SYSUNINIT
o docs/132839  doc        [patch] Fix example script in ldap-auth article
o docs/132718  doc        [handbook] Information about adding a new mirror is ou
o docs/132311  doc        [patch] man5/nsmb.conf.5
o docs/132260  doc        dhcpd(8) pid not stored in documented location
o docs/132190  doc        EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/132113  doc        [handbook] Update handbook jails creation
o docs/131918  doc        [patch] Fixes for the BPF(4) man page
o docs/131684  doc        [patch] articles/linux-comparison: replace Addenda by 
o docs/131590  doc        [patch] whitespace-only change of developers-handbook/
o docs/130895  doc        [patch] No man page installed for padlock(4) on amd64 
o docs/130364  doc        Man page for top needs explanation of CPU states
o docs/130238  doc        nfs.lockd man page doesn't mention NFSLOCKD option or 
o docs/129671  doc        New TCP chapter for Developer's Handbook (from rwatson
o docs/129095  doc        ipfw(8): Can not check that packet originating/destine
o docs/128524  doc        No geom documentation for loading gjournal(8)
s docs/128356  doc        [request] add Firefox plugin for FreeBSD manual pages
o docs/127908  doc        [patch] readdir(3) error documentation
s docs/127844  doc        Example code skeleton_capture_n.c in meteor(4) manpage
o docs/126590  doc        [patch] Write routine called forever in Sample Echo Ps
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
f docs/122052  doc        minor update on handbook section 20.7.1
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o bin/121424   doc        [patch] [ipfw] Rectify ambiguous English in manual
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
a docs/119536  doc        a few typos in French handbook (basics)
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118214  doc        close(2) error returns incomplete
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/117747  doc        'break' system call needs a man page
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/116116  doc        mktemp (3) re/move note
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111147  doc        hostapd.conf is not documented
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110061  doc        [patch] tuning(7) missing reference to vfs.read_max
o docs/109981  doc        No manual entry for post-grohtml
o docs/109977  doc        No manual entry for ksu
o docs/109973  doc        No manual entry for c++filt
o docs/109972  doc        No manual entry for zless/bzless
f docs/109226  doc        [request] No manual entry for sntp
o docs/109201  doc        [request]: manual for callbootd
a docs/108980  doc        list of missing man pages
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
o docs/107924  docs       [usb67] usbd(8) does not call detach
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/105608  doc        fdc(4) debugging description staled
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/91174   doc        [REQUEST] Handbook: Addition of Oracle 9i installation
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84271   doc        [patch] compress(1) doesn't warn about nasty link hand
o docs/83820   doc        getino(3) manpage not installed
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
o docs/63570   doc        [patch] Language cleanup for the Handbook's DNS sectio
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
o docs/53596   doc        Updates to mt(1) manual page
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/50211   doc        [patch] doc.docbook.mk: fix textfile creation
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/43823   doc        [patch] update to environ(7) manpage
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/38556   doc        EPS file of beastie, as addition to existing examples
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
a docs/30008   doc        [patch] French softupdates document should be translat
o docs/27605   doc        [patch] Cross-document references (<olink>)
o docs/26286   doc        *printf(3) etc should gain format string warnings
o docs/24786   doc        missing FILES descriptions in sa(4)
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc

174 problems total.

From brueffer at FreeBSD.org  Mon Nov 16 14:34:27 2009
From: brueffer at FreeBSD.org (brueffer@FreeBSD.org)
Date: Mon Nov 16 14:34:33 2009
Subject: docs/140459: [patch] Grammar fix for nl_langinfo(3)
Message-ID: <200911161434.nAGEYQ82097461@freefall.freebsd.org>

Synopsis: [patch] Grammar fix for nl_langinfo(3)

State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Mon Nov 16 15:33:41 CET 2009
State-Changed-Why: 
Committed, thanks!


Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Mon Nov 16 15:33:41 CET 2009
Responsible-Changed-Why: 
MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140459
From brueffer at FreeBSD.org  Mon Nov 16 16:11:38 2009
From: brueffer at FreeBSD.org (brueffer@FreeBSD.org)
Date: Mon Nov 16 16:11:45 2009
Subject: docs/140594: getprogname.3 misleading
Message-ID: <200911161611.nAGGBcOf081475@freefall.freebsd.org>

Synopsis: getprogname.3 misleading

State-Changed-From-To: open->closed
State-Changed-By: brueffer
State-Changed-When: Mon Nov 16 17:06:40 CET 2009
State-Changed-Why: 
After consulting with kib, the manpage is correct.  The sentence
you're citing means that calling setprogname() even though it is
not needed on FreeBSD allows getprogname() implementations
on other systems to retrieve and return the program name in any case.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140594
From jhelfman at e-e.com  Mon Nov 16 18:23:18 2009
From: jhelfman at e-e.com (Jason)
Date: Mon Nov 16 18:23:24 2009
Subject: bsdmag.org link placement
Message-ID: <20091115214610.GA17485@jason-helfmans-macbook-pro.local>

Hi

I was wondering where a link I would like to submit for BSD Magazine, would
be most appropriate?

It isn't specifically FreeBSD, however it is specific to all BSD's, so I
was thinking of putting under "International book & Magazines" found here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bibliography.html#BIBLIOGRAPHY-FREEBSD

or perhaps, here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bibliography-journals.html

Beyond this, I don't see the need for that latter link, as it could be
condensed into the first, and renamed. That is another path, though.

Any thoughts?

Thanks,
Jason
From jhelfman at e-e.com  Mon Nov 16 18:26:01 2009
From: jhelfman at e-e.com (Jason)
Date: Mon Nov 16 18:26:08 2009
Subject: bsdmag.org link placement
Message-ID: <20091116182457.GC36953@eggman.experts-exchange.com>

Hi

I was wondering where a link I would like to submit for BSD Magazine, would
be most appropriate?
  
It isn't specifically FreeBSD, however it is specific to all BSD's, so I
was thinking of putting under "International book & Magazines" found here:
  
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bibliography.html#BIBLIOGRAPHY-FREEBSD

or perhaps, here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bibliography-journals.html
  
Beyond this, I don't see the need for that latter link, as it could be
condensed into the first, and renamed. That is another path, though.

Any thoughts?

Thanks,
Jason
From bcr at FreeBSD.org  Mon Nov 16 21:13:41 2009
From: bcr at FreeBSD.org (bcr@FreeBSD.org)
Date: Mon Nov 16 21:13:48 2009
Subject: docs/140581: [mirrors] [patch] Link to Poly link doesn't work.
	Found a suitable replacement and named the full University. Go Poly.
Message-ID: <200911162113.nAGLDfpv040232@freefall.freebsd.org>

Synopsis: [mirrors] [patch] Link to Poly link doesn't work. Found a suitable replacement and named the full University. Go Poly.

Responsible-Changed-From-To: freebsd-doc->bcr
Responsible-Changed-By: bcr
Responsible-Changed-When: Mon Nov 16 21:11:44 UTC 2009
Responsible-Changed-Why: 
I take care of that.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140581
From rene at freebsd.org  Mon Nov 16 22:47:38 2009
From: rene at freebsd.org (Rene Ladan)
Date: Mon Nov 16 22:48:53 2009
Subject: [RFC] [patch] Clang section for Porters Handbook
Message-ID: <4B01D5C9.4080207@freebsd.org>

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20091116/d0be8a24/signature.pgp
From hinokind at gmail.com  Mon Nov 16 23:10:01 2009
From: hinokind at gmail.com (Andrius Morkunas)
Date: Mon Nov 16 23:11:06 2009
Subject: docs/140615: [patch] Typo in queue(3)
Message-ID: <200911162304.nAGN48Mn044470@www.freebsd.org>


>Number:         140615
>Category:       docs
>Synopsis:       [patch] Typo in queue(3)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 16 23:10:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Andrius Morkunas
>Release:        9-CURRENT
>Organization:
>Environment:
>Description:
queue(3) manual has a sentence beginning with "Each elements", where it should be "Each element".
>How-To-Repeat:

>Fix:
Patch attached.

Patch attached with submission follows:

--- share/man/man3/queue.3	(revision 199338)
+++ share/man/man3/queue.3	(working copy)
@@ -233,7 +233,7 @@
 However:
 .Bl -enum -compact -offset indent
 .It
-Each elements requires two pointers rather than one.
+Each element requires two pointers rather than one.
 .It
 Code size and execution time of operations (except for removal) is about
 twice that of the singly-linked data-structures.



>Release-Note:
>Audit-Trail:
>Unformatted:
From linimon at lonesome.com  Mon Nov 16 23:29:55 2009
From: linimon at lonesome.com (Mark Linimon)
Date: Mon Nov 16 23:30:02 2009
Subject: [RFC] [patch] Clang section for Porters Handbook
In-Reply-To: <4B01D5C9.4080207@freebsd.org>
References: <4B01D5C9.4080207@freebsd.org>
Message-ID: <20091116232954.GA6511@lonesome.com>

Looks nice.  Here are some ideas.

> 	<para>A future version of &os; will likely have the Clang C/C++
> 	  compiler as its base compiler.  Some modifications to the Ports
> 	  Collection are necessary.  In general, these are <quote>write proper
> 	    ports</quote> and <quote>write proper source code</quote>.

To me, this last sentence is worded a little awkwardly (partly because
of the tense).  How about:

  In general, these involve <quote>generalizing the port</quote> and
  <quote>making the source code portable</quote>.

> 	      so existing occurences have to be removed.  No concensus has yet

  consensus

> 	    <para>The maximum useable optimization level is 3.  Level 4 is

  usable (don't feel bad, I had to look it up)

> 	<para>Some temporary hacks that might be used if all else fails:</para>

I'm almost wondering if the c89 hack might be moved to here, but I'm not sure.

mcl
From brueffer at FreeBSD.org  Tue Nov 17 07:07:15 2009
From: brueffer at FreeBSD.org (brueffer@FreeBSD.org)
Date: Tue Nov 17 07:07:20 2009
Subject: docs/140615: [patch] Typo in queue(3)
Message-ID: <200911170707.nAH77EBh055464@freefall.freebsd.org>

Synopsis: [patch] Typo in queue(3)

State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Tue Nov 17 08:06:47 CET 2009
State-Changed-Why: 
Committed, thanks!


Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Tue Nov 17 08:06:47 CET 2009
Responsible-Changed-Why: 
MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140615
From gateway at jumeirah.com  Tue Nov 17 07:11:10 2009
From: gateway at jumeirah.com (Jumeirah Bab Al Shams Desert Resort & Spa)
Date: Tue Nov 17 07:11:17 2009
Subject: Exclusive Eid Festivities at Jumeirah Bab Al Shams Desert Resort &
	Spa
Message-ID: <20091117-11110239-16c0@eyeofdubai>


   Kindly [1]click here, If you are not able to view the content of this
                                  e-mail.


                       [2]Bab Al Shams Resort & Spa 
                       [3]Bab Al Shams Resort & Spa 
                                [_space.gif]

     Jumeirah Bab Al Shams Desert Resort & Spa is offering an array of
   endless activities to get your pulse racing during the time of Eid Al
      Adha. We have everything from camel riding and desert tours to a
    magnificent fireworks display, not to mention all the treatments at
          the Spa and the leisure activities around the pool area.

    How you spend your days at Jumeirah Bab Al Shams is completely up to
   you, the beauty of it, is that you can be as lazy or as active as you
                                   want.

             [4]CLICK HERE TO VIEW OUR OFFERS THIS EID AL ADHA

      To make a booking or for more information please contact us on:
                            Tel: +971 4 8096100
                      Email:[5]JBASinfo@jumeirah.com 
                                [_space.gif]
            [_space.gif] PO Box 8168, Al Qudra Road, Dubai, UAE
                 Tel: +971 4 809 6100 Fax: +971 4 809 6698
       Email: [6]JBASinfo@jumeirah.com [7]Stay Different [_space.gif]

       The information in this email is private & confidential. It is
    intended only for the use of the person(s) named. If you are not the
   intended recipient, you are notified that any dissemination or copying
   of this communication is prohibited and kindly requested to notify the
     sender and to then delete this message. Jumeirah International LLC
   gives no representation or guarantee with respect to the integrity of
                       any emails or attached files.
   We respect your online time and privacy and promise not to abuse this
                                  medium.
              To view Jumeirah's privacy policy please visit:
                    [8]www.jumeirah.com/privacy_policy/

              [9]Unsubscribe from Eyeofdubai.com mailing list
      You are currently subscribed to receive emails/newsletters from
                              Eyeofdubai.com.
           You can modify your subscription settings at any time.
      [10]Eyeofdubai.com respects your privacy and does not share any
                 information about you with other parties.

References

   1. http://www.eyeofdubai.com/emails/babshams.html
   2. http://www.eyeofdubai.com/bannerm/abmc.asp?b=545&z=17
   3. http://www.eyeofdubai.com/bannerm/abmc.asp?b=546&z=17
   4. http://www.eyeofdubai.com/bannerm/abmc.asp?b=547&z=17
   5. mailto:JBASinfo@jumeirah.com
   6. mailto:JBASinfo@jumeirah.com
   7. http://www.eyeofdubai.com/bannerm/abmc.asp?b=548&z=17
   8. http://www.jumeirah.com/privacy_policy/
   9. http://eyeofdubai.com/en/newsletter/unsubscribe.asp?email=freebsd-doc@FreeBSD.org&emailid=322756
  10. http://eyeofdubai.com/v1/about/privacy.asp
From rene at freebsd.org  Tue Nov 17 12:03:30 2009
From: rene at freebsd.org (Rene Ladan)
Date: Tue Nov 17 12:04:04 2009
Subject: [RFC] [patch] Clang section for Porters Handbook
In-Reply-To: <20091116232954.GA6511@lonesome.com>
References: <4B01D5C9.4080207@freebsd.org> <20091116232954.GA6511@lonesome.com>
Message-ID: <e890cae60911170403i234fda84t35ddddf7f27ff173@mail.gmail.com>

2009/11/17 Mark Linimon <linimon@lonesome.com>:
> Looks nice. ?Here are some ideas.
>
>> ? ? ? <para>A future version of &os; will likely have the Clang C/C++
>> ? ? ? ? compiler as its base compiler. ?Some modifications to the Ports
>> ? ? ? ? Collection are necessary. ?In general, these are <quote>write proper
>> ? ? ? ? ? ports</quote> and <quote>write proper source code</quote>.
>
> To me, this last sentence is worded a little awkwardly (partly because
> of the tense). ?How about:
>
> ?In general, these involve <quote>generalizing the port</quote> and
> ?<quote>making the source code portable</quote>.
>
This indeeds sounds better.

>> ? ? ? ? ? ? so existing occurences have to be removed. ?No concensus has yet
>
> ?consensus
>
aspell also found 'occurrences', I should have spell checked it earlier ...

>> ? ? ? ? ? <para>The maximum useable optimization level is 3. ?Level 4 is
>
> ?usable (don't feel bad, I had to look it up)
>
>> ? ? ? <para>Some temporary hacks that might be used if all else fails:</para>
>
> I'm almost wondering if the c89 hack might be moved to here, but I'm not sure.
>
Isn't this more like a flag to be able to compile old code?  In this
case the c89 flag
is not  a hack, given that the code is following the standard (here gnu89).

See p4 revision 170700

Regards,
Rene
From ray.kinsella at intel.com  Tue Nov 17 17:46:56 2009
From: ray.kinsella at intel.com (Kinsella, Ray)
Date: Tue Nov 17 17:47:29 2009
Subject: Programmers' Guides
In-Reply-To: <e890cae60911170403i234fda84t35ddddf7f27ff173@mail.gmail.com>
References: <4B01D5C9.4080207@freebsd.org> <20091116232954.GA6511@lonesome.com>
	<e890cae60911170403i234fda84t35ddddf7f27ff173@mail.gmail.com>
Message-ID: <E1685DC46A53EF42A31FC3251BFE4CF212B3B0EF60@irsmsx502.ger.corp.intel.com>

Skipped content of type multipart/signed-------------- next part --------------
--------------------------------------------------------------
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

From jhelfman at e-e.com  Tue Nov 17 20:10:02 2009
From: jhelfman at e-e.com (Jason Helfman)
Date: Tue Nov 17 20:10:08 2009
Subject: docs/140644: Add BSD Magazine to Bibliography
Message-ID: <200911172004.nAHK42dR054560@www.freebsd.org>


>Number:         140644
>Category:       docs
>Synopsis:       Add BSD Magazine to Bibliography
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 17 20:10:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Jason Helfman
>Release:        7.2-RELEASE-p4
>Organization:
Experts Exchange
>Environment:
FreeBSD eggman.experts-exchange.com 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct  2 12:21:39 UTC 2009     root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
Add BSD Magazine to Bibliography
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- en_US.ISO8859-1/books/handbook/bibliography/chapter.sgml.orig	2009-11-17 11:51:45.000000000 -0800
+++ en_US.ISO8859-1/books/handbook/bibliography/chapter.sgml	2009-11-17 12:01:05.000000000 -0800
@@ -209,6 +209,12 @@
 	  ISBN: 0072224096 </para>
       </listitem>
 
+      <listitem>
+	<para><ulink url="http://www.bsdmag.org">BSD Magazine</ulink>, published
+	  by Software Press Sp. z o.o. SK,
+          ISSN 1898-9144 </para>
+      </listitem>
+
     </itemizedlist>
   </sect1>


>Release-Note:
>Audit-Trail:
>Unformatted:
From jhelfman at e-e.com  Tue Nov 17 20:30:03 2009
From: jhelfman at e-e.com (Jason Helfman)
Date: Tue Nov 17 20:30:10 2009
Subject: docs/140644: Add BSD Magazine to Bibliography
Message-ID: <200911172030.nAHKU3sI077577@freefall.freebsd.org>

The following reply was made to PR docs/140644; it has been noted by GNATS.

From: Jason Helfman <jhelfman@e-e.com>
To: bug-followup@FreeBSD.org, jhelfman@e-e.com
Cc:  
Subject: Re: docs/140644: Add BSD Magazine to Bibliography
Date: Tue, 17 Nov 2009 12:22:15 -0800

 This is a multi-part message in MIME format.
 --------------030602060206090802080504
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
 Content-Transfer-Encoding: 7bit
 
 The "SK," should be a "SK."
 
 Go with this patch, please.
 
 Thank you,
 Jason
 
 --------------030602060206090802080504
 Content-Type: text/plain;
  name="patch.txt"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline;
  filename="patch.txt"
 
 --- en_US.ISO8859-1/books/handbook/bibliography/chapter.sgml.orig	2009-11-17 11:51:45.000000000 -0800
 +++ en_US.ISO8859-1/books/handbook/bibliography/chapter.sgml	2009-11-17 12:01:05.000000000 -0800
 @@ -209,6 +209,12 @@
  	  ISBN: 0072224096 </para>
        </listitem>
  
 +      <listitem>
 +	<para><ulink url="http://www.bsdmag.org">BSD Magazine</ulink>, published
 +	  by Software Press Sp. z o.o. SK.
 +          ISSN 1898-9144 </para>
 +      </listitem>
 +
      </itemizedlist>
    </sect1>
 
 --------------030602060206090802080504--
From bcr at FreeBSD.org  Tue Nov 17 22:13:14 2009
From: bcr at FreeBSD.org (bcr@FreeBSD.org)
Date: Tue Nov 17 22:13:25 2009
Subject: docs/140644: Add BSD Magazine to Bibliography
Message-ID: <200911172213.nAHMDELt072390@freefall.freebsd.org>

Synopsis: Add BSD Magazine to Bibliography

State-Changed-From-To: open->analyzed
State-Changed-By: bcr
State-Changed-When: Tue Nov 17 22:06:04 UTC 2009
State-Changed-Why: 
I'll look into it.


Responsible-Changed-From-To: freebsd-doc->bcr
Responsible-Changed-By: bcr
Responsible-Changed-When: Tue Nov 17 22:06:04 UTC 2009
Responsible-Changed-Why: 


http://www.freebsd.org/cgi/query-pr.cgi?pr=140644
From ben at wanderview.com  Wed Nov 18 02:00:10 2009
From: ben at wanderview.com (Ben Kelly)
Date: Wed Nov 18 02:00:34 2009
Subject: docs/140649: bad WITHOUT_MODULES example in handbook
Message-ID: <200911180152.nAI1qULT042968@www.freebsd.org>


>Number:         140649
>Category:       docs
>Synopsis:       bad WITHOUT_MODULES example in handbook
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 18 02:00:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Ben Kelly
>Release:        CURRENT
>Organization:
>Environment:
FreeBSD ianto.in.wanderview.com 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r254M: Fri Nov 13 23:26:25 UTC 2009     root@ianto.in.wanderview.com:/usr/obj/usr/src/sys/SERVER  i386

>Description:
The handbook currently incorrectly suggests you can specify module subdirectories in WITHOUT_MODULES.  See the second tip on this page:

  http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html

This is incorrect because the WITHOUT_MODULES logic in /usr/src/sys/modules/Makefile will only exclude items in the original SUBDIRS list.  Only the top level module directories are included in this list.
>How-To-Repeat:
Add the following to your /etc/make.conf:

  WITHOUT_MODULES=sound/driver/emu10k1

Build the kernel and see the emu10k1 module get built anyway.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From ben at wanderview.com  Wed Nov 18 03:50:03 2009
From: ben at wanderview.com (Ben Kelly)
Date: Wed Nov 18 03:51:15 2009
Subject: docs/140649: bad WITHOUT_MODULES example in handbook
Message-ID: <200911180350.nAI3o2fu056633@freefall.freebsd.org>

The following reply was made to PR docs/140649; it has been noted by GNATS.

From: Ben Kelly <ben@wanderview.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/140649: bad WITHOUT_MODULES example in handbook
Date: Tue, 17 Nov 2009 22:19:44 -0500

 I forgot to mention this was initially reported by Gonzalo Nemmi.  =
 (gnemmi gmail com)=
From ale at FreeBSD.org  Wed Nov 18 09:12:11 2009
From: ale at FreeBSD.org (Alex Dupre)
Date: Wed Nov 18 09:12:18 2009
Subject: Programmers' Guides
In-Reply-To: <E1685DC46A53EF42A31FC3251BFE4CF212B3B0EF60@irsmsx502.ger.corp.intel.com>
References: <4B01D5C9.4080207@freebsd.org>
	<20091116232954.GA6511@lonesome.com>	<e890cae60911170403i234fda84t35ddddf7f27ff173@mail.gmail.com>
	<E1685DC46A53EF42A31FC3251BFE4CF212B3B0EF60@irsmsx502.ger.corp.intel.com>
Message-ID: <4B03B429.8040605@FreeBSD.org>

Kinsella, Ray ha scritto:
> Would it be possible to add these papers to the FreeBSD Handbook's
> Programmers' Guides section? 

To begin with, I can add them to the "On other web sites - Articles"
section of the following page: http://www.freebsd.org/docs/books.html

-- 
Alex Dupre
From ray.kinsella at intel.com  Wed Nov 18 09:38:33 2009
From: ray.kinsella at intel.com (Kinsella, Ray)
Date: Wed Nov 18 09:38:39 2009
Subject: Programmers' Guides
In-Reply-To: <4B03B429.8040605@FreeBSD.org>
References: <4B01D5C9.4080207@freebsd.org> <20091116232954.GA6511@lonesome.com>
	<e890cae60911170403i234fda84t35ddddf7f27ff173@mail.gmail.com>
	<E1685DC46A53EF42A31FC3251BFE4CF212B3B0EF60@irsmsx502.ger.corp.intel.com>
	<4B03B429.8040605@FreeBSD.org>
Message-ID: <E1685DC46A53EF42A31FC3251BFE4CF212B3B0F1D2@irsmsx502.ger.corp.intel.com>

Skipped content of type multipart/signed-------------- next part --------------
--------------------------------------------------------------
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

From ben at wanderview.com  Wed Nov 18 12:30:04 2009
From: ben at wanderview.com (Ben Kelly)
Date: Wed Nov 18 12:30:13 2009
Subject: docs/140649: [handbook] bad WITHOUT_MODULES example in handbook
Message-ID: <200911181230.nAICU3Jo042968@freefall.freebsd.org>

The following reply was made to PR docs/140649; it has been noted by GNATS.

From: Ben Kelly <ben@wanderview.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/140649: [handbook] bad WITHOUT_MODULES example in handbook
Date: Wed, 18 Nov 2009 07:23:10 -0500

 On current@ on 11/17/2009 Doug Barton suggested that WITHOUT_MODULES and =
 MODULES_OVERRIDE should be documented in srcs.conf instead of make.conf:
 
 "You can add to the mix the fact that options like modules_override and
 without_modules are documented in make.conf(5) instead of in
 src.conf(5) which is where (arguably) they should be."=
From leslie at eskk.nu  Wed Nov 18 21:25:06 2009
From: leslie at eskk.nu (Leslie Jensen)
Date: Wed Nov 18 21:25:12 2009
Subject: Just a little correction
Message-ID: <4B045D2F.2080906@eskk.nu>

Hi

On the page

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-dhcp.html

Chapter 29.5.7.3 Configuring the DHCP Server

It says:
Then, you can proceed to start the server by issuing the following command:

# /usr/local/etc/rc.d/isc-dhcpd.sh start

I get an error with that command!!

root@machine01~:/usr/local/etc/rc.d/isc-dhcpd.sh start
/usr/local/etc/rc.d/isc-dhcpd.sh: Command not found.

The following works:

root@machine01~:/usr/local/etc/rc.d/isc-dhcpd start


It's not a big thing but I think it should be corrected.


-- 
Med v?nlig h?lsning / With Regards / Mit freundlichen gr??en

___________________________________________________________________
Leslie Jensen
Liljegatan 26
SE-262 57 ?ngelholm

Telephone +46 (0)431 19370      Mobile phone +46 (0)70 572 44 57

This E-mail is sent from leslie@eskk.nu
using http://www.mozilla.com/thunderbird/

http://www.spreadbsd.org/aff/162/3
___________________________________________________________________
From pluknet at gmail.com  Wed Nov 18 22:19:12 2009
From: pluknet at gmail.com (pluknet)
Date: Wed Nov 18 22:19:18 2009
Subject: Just a little correction
In-Reply-To: <4B045D2F.2080906@eskk.nu>
References: <4B045D2F.2080906@eskk.nu>
Message-ID: <a31046fc0911181354p5910c0efs6da5fbdbb60d98d7@mail.gmail.com>

2009/11/18 Leslie Jensen <leslie@eskk.nu>:
> Hi
>
> On the page
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-dhcp.html
>
> Chapter 29.5.7.3 Configuring the DHCP Server
>
> It says:
> Then, you can proceed to start the server by issuing the following command:
>
> # /usr/local/etc/rc.d/isc-dhcpd.sh start
>
> I get an error with that command!!
>
> root@machine01~:/usr/local/etc/rc.d/isc-dhcpd.sh start
> /usr/local/etc/rc.d/isc-dhcpd.sh: Command not found.
>
> The following works:
>
> root@machine01~:/usr/local/etc/rc.d/isc-dhcpd start
>
>
> It's not a big thing but I think it should be corrected.
>

Also the leftovers from pre rcng are:

16.15.6 Testing the Configuration
/usr/local/etc/rc.d/nagios.sh

30.5.9 Building the Rule Script with Symbolic Substitution
/usr/local/etc/rc.d/ipf.loadrules.sh (not 100% sure)


-- 
wbr,
pluknet
From eitanadlerlist at gmail.com  Thu Nov 19 12:24:21 2009
From: eitanadlerlist at gmail.com (Eitan Adler)
Date: Thu Nov 19 12:24:28 2009
Subject: Installing X11 - add xorg-minimal
Message-ID: <a0777e080911190358t353644f7v17a59334884f3a1f@mail.gmail.com>

I think it would be a good idea to include a reference to
x11/xorg-minimal into the handbook.
Perhaps under
Note: The examples above will install the complete X11 distribution
including the servers, clients, fonts etc. Separate packages and ports
of X11 are also available.
Something like:
If you just want to get X up and running install x11/xorg-minimal instead
Should be added.
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Thu Nov 19 14:30:04 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Thu Nov 19 14:30:16 2009
Subject: docs/140444: [patch] New Traditional Chinese translation of
	custom-gcc
Message-ID: <200911191430.nAJEU3mR027478@freefall.freebsd.org>

The following reply was made to PR docs/140444; it has been noted by GNATS.

From: Denny Lin <dennylin93@cnmc32.hs.ntnu.edu.tw>
To: bug-followup@FreeBSD.org, dennylin93@cnmc32.hs.ntnu.edu.tw
Cc:  
Subject: Re: docs/140444: [patch] New Traditional Chinese translation of custom-gcc
Date: Thu, 19 Nov 2009 22:28:01 +0800

 --fUYQa+Pmc3FrFX/N
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 Forgot to add new article to doc/zh_TW.Big5/articles/Makefile.
 
 --=20
 Denny Lin
 
 --fUYQa+Pmc3FrFX/N
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.13 (FreeBSD)
 
 iEYEARECAAYFAksFVfEACgkQtYH0ykp1KDwSTwCeJ9KPfJb4WFhbMS1NlaZx48dR
 dK4An2h4ojwjzuzDdcuPZsQlDP//p4SY
 =kZ27
 -----END PGP SIGNATURE-----
 
 --fUYQa+Pmc3FrFX/N--
From dennylin93 at cnmc32.hs.ntnu.edu.tw  Thu Nov 19 14:30:06 2009
From: dennylin93 at cnmc32.hs.ntnu.edu.tw (Denny Lin)
Date: Thu Nov 19 14:30:17 2009
Subject: docs/140444: [patch] New Traditional Chinese translation of
	custom-gcc
Message-ID: <200911191430.nAJEU6u0027619@freefall.freebsd.org>

The following reply was made to PR docs/140444; it has been noted by GNATS.

From: Denny Lin <dennylin93@cnmc32.hs.ntnu.edu.tw>
To: bug-followup@FreeBSD.org, dennylin93@cnmc32.hs.ntnu.edu.tw
Cc:  
Subject: Re: docs/140444: [patch] New Traditional Chinese translation of custom-gcc
Date: Thu, 19 Nov 2009 22:29:37 +0800

 --ftEhullJWpWg/VHq
 Content-Type: multipart/mixed; boundary="KsGdsel6WgEHnImy"
 Content-Disposition: inline
 
 
 --KsGdsel6WgEHnImy
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 Oops. Forgot to attach file.
 
 --=20
 Denny Lin
 
 --KsGdsel6WgEHnImy
 Content-Type: text/x-diff; charset=utf-8
 Content-Disposition: attachment; filename="zh_TW-articles-Makefile.patch"
 Content-Transfer-Encoding: quoted-printable
 
 --- doc/zh_TW.Big5/articles/Makefile.orig	2009-11-19 22:22:57.650325047 +08=
 00
 +++ doc/zh_TW.Big5/articles/Makefile	2009-11-19 22:23:33.914787810 +0800
 @@ -2,6 +2,7 @@
 =20
  SUBDIR =3D
  SUBDIR+=3D contributing
 +SUBDIR+=3D custom-gcc
  SUBDIR+=3D cvs-freebsd
  SUBDIR+=3D freebsd-questions
  SUBDIR+=3D hubs
 
 --KsGdsel6WgEHnImy--
 
 --ftEhullJWpWg/VHq
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.13 (FreeBSD)
 
 iEYEARECAAYFAksFVlEACgkQtYH0ykp1KDwMKgCgk+xrybLnKKXgiKhQDjUZGKSk
 RxcAn0r6/ylsUvhSK2bFgVwh/JYPFAW1
 =UiKU
 -----END PGP SIGNATURE-----
 
 --ftEhullJWpWg/VHq--
From jhelfman at e-e.com  Thu Nov 19 18:50:03 2009
From: jhelfman at e-e.com (Jason Helfman)
Date: Thu Nov 19 18:50:09 2009
Subject: docs/140703: add xorg-minimal as alternative for X11 Distribution
	installation
Message-ID: <200911191846.nAJIkZTB038110@www.freebsd.org>


>Number:         140703
>Category:       docs
>Synopsis:       add xorg-minimal as alternative for X11 Distribution installation
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 19 18:50:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Jason Helfman
>Release:        7.2-RELEASE
>Organization:
Experts Exchange
>Environment:
FreeBSD eggman.experts-exchange.com 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct  2 12:21:39 UTC 2009     root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
add xorg-minimal as alternative for X11 Distribution installation

-suggestion per maintainer of port

Attempted to fix this particular portion of document per standards I believe I met.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- en_US.ISO8859-1/books/handbook/x11/chapter.sgml.orig	2009-11-19 10:33:01.000000000 -0800
+++ en_US.ISO8859-1/books/handbook/x11/chapter.sgml	2009-11-19 10:42:19.000000000 -0800
@@ -339,11 +339,18 @@
 
     <screen>&prompt.root; <userinput>pkg_add -r xorg</userinput></screen>
 
-    <note><para>The examples above will install the complete
+    <note>
+      <para>The examples above will install the complete
       X11 distribution including the
       servers, clients, fonts etc.  Separate packages and ports of X11
-      are also
-      available.</para></note>
+      are also available.</para>
+
+      <para>To install an minimal X11 distribution you can 
+      alternatively install <filename role="package">x11/xorg-minimal
+      </filename></para>.
+    </note>
+
+</note>
 
     <para>The rest of this chapter will explain how to configure
       X11, and how to set up a productive desktop


>Release-Note:
>Audit-Trail:
>Unformatted:
From blackend at FreeBSD.org  Thu Nov 19 19:30:04 2009
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Thu Nov 19 19:30:26 2009
Subject: docs/140703: add xorg-minimal as alternative for X11
 Distribution installation
Message-ID: <200911191930.nAJJU39i085709@freefall.freebsd.org>

The following reply was made to PR docs/140703; it has been noted by GNATS.

From: Marc Fonvieille <blackend@FreeBSD.org>
To: Jason Helfman <jhelfman@e-e.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: docs/140703: add xorg-minimal as alternative for X11
 Distribution installation
Date: Thu, 19 Nov 2009 20:26:20 +0100

 On Thu, Nov 19, 2009 at 06:46:35PM +0000, Jason Helfman wrote:
 > 
 > >Description:
 > add xorg-minimal as alternative for X11 Distribution installation
 > 
 > -suggestion per maintainer of port
 > 
 > Attempted to fix this particular portion of document per standards I believe I met.
 
 [...]
 
 Hello,
 
 Most of time we avoid to mix content and whitespace changes.
 
 > 
 > --- en_US.ISO8859-1/books/handbook/x11/chapter.sgml.orig	2009-11-19 10:33:01.000000000 -0800
 > +++ en_US.ISO8859-1/books/handbook/x11/chapter.sgml	2009-11-19 10:42:19.000000000 -0800
 > @@ -339,11 +339,18 @@
 >  
 >      <screen>&prompt.root; <userinput>pkg_add -r xorg</userinput></screen>
 >  
 > -    <note><para>The examples above will install the complete
 > +    <note>
 > +      <para>The examples above will install the complete
 >        X11 distribution including the
 >        servers, clients, fonts etc.  Separate packages and ports of X11
 > -      are also
 > -      available.</para></note>
 > +      are also available.</para>
 
 All above are whitespace/wrapping/layout changes.
 
 > +
 > +      <para>To install an minimal X11 distribution you can 
 > +      alternatively install <filename role="package">x11/xorg-minimal
 > +      </filename></para>.
 
 	the closing </filename> should directly follow x11/xorg-minimal,
 	i.e., <filename role="package">x11/xorg-minimal</filename>.
 	You can break the tags like this:
 
 	blahblahblah blah blahblahblahblahblahblah <filename
 	role="package">x11/xorg-minimal</filename>
 
 	but not like:
 
 	blahblahblah blahblahblah <filename role="package">x11/xorg-minimal
 	</filename>
 
 
 -- 
 Marc
From jhelfman at e-e.com  Thu Nov 19 19:30:06 2009
From: jhelfman at e-e.com (Jason Helfman)
Date: Thu Nov 19 19:30:26 2009
Subject: docs/140703: add xorg-minimal as alternative for X11
 Distribution installation
Message-ID: <200911191930.nAJJU6LC085867@freefall.freebsd.org>

The following reply was made to PR docs/140703; it has been noted by GNATS.

From: Jason Helfman <jhelfman@e-e.com>
To: bug-followup@FreeBSD.org, jhelfman@e-e.com
Cc:  
Subject: Re: docs/140703: add xorg-minimal as alternative for X11 Distribution
 installation
Date: Thu, 19 Nov 2009 11:28:14 -0800

 That should be "a minimal..." not "an minimal..."
 
 -jgh
From manolis at FreeBSD.org  Thu Nov 19 21:35:10 2009
From: manolis at FreeBSD.org (Manolis Kiagias)
Date: Thu Nov 19 21:35:46 2009
Subject: [RFC] Article on freebsd-update-server
Message-ID: <4B05BA06.3010303@FreeBSD.org>

Hi all,

I am sending this to my usual reviewers and the doc@ list, everyone is
welcome to comment.

Jason Helfman (jhelfman@e-e.com) is  actively involved with our
documentation set and you may have seen some of his patches.

His initial contribution however is the article in this PR:

http://www.freebsd.org/cgi/query-pr.cgi?pr=139095

I've been working  on this article with Jason for quite some time, and
we think it's about time it gets a broader review.

The source is here:

http://people.freebsd.org/~manolis/patches/freebsd-update-server/article.sgml.txt

And the build:

http://people.freebsd.org/~manolis/patches/freebsd-update-server/index.html

Please send us any comments and suggestions  on content, format or whatever!

Thanks,
manolis@


From keramida at FreeBSD.org  Fri Nov 20 16:07:16 2009
From: keramida at FreeBSD.org (Giorgos Keramidas)
Date: Fri Nov 20 16:07:24 2009
Subject: [RFC] Article on freebsd-update-server
References: <4B05BA06.3010303@FreeBSD.org>
Message-ID: <87ws1luqmx.fsf@kobe.laptop>

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20091120/6fe22e66/attachment.pgp
From mickael.maillot at gmail.com  Fri Nov 20 16:40:01 2009
From: mickael.maillot at gmail.com (Fneufneu)
Date: Fri Nov 20 16:40:08 2009
Subject: docs/140725: wrong directory in ipnat(8) man page
Message-ID: <200911201632.nAKGWkkM059921@www.freebsd.org>


>Number:         140725
>Category:       docs
>Synopsis:       wrong directory in ipnat(8) man page
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Nov 20 16:40:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Fneufneu
>Release:        FreeBSD 8-STABLE
>Organization:
>Environment:
FreeBSD cg96.security-mail.net 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #1: Wed Nov 18 11:54:44 CET 2009     root@cg96.security-mail.net:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
in ipnat(8) man page, FILES part, the exemple directory is wrong:
/usr/share/examples/ipf  Directory with examples.
should be:
/usr/share/examples/ipfilter  Directory with examples.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From manolis at FreeBSD.org  Fri Nov 20 16:52:30 2009
From: manolis at FreeBSD.org (Manolis Kiagias)
Date: Fri Nov 20 16:52:37 2009
Subject: [RFC] Article on freebsd-update-server
In-Reply-To: <87ws1luqmx.fsf@kobe.laptop>
References: <4B05BA06.3010303@FreeBSD.org> <87ws1luqmx.fsf@kobe.laptop>
Message-ID: <4B06C94A.30600@FreeBSD.org>

Giorgos Keramidas wrote:
> <SNIP> - All changes look fine up to this point
> :      <note>
> : -      <para>Note down the generated KeyPrint; this value is entered into
> : -       <filename>/etc/freebsd-update.conf</filename> for binary
> : -       updates.</para>
> : +      <para>Keep a note of the generated key fingerpring.  This value is
> : +       entered into <filename>/etc/freebsd-update.conf</filename> for
> : +       binary updates.</para>
> :      </note>
>
> There are various places that the article refers to  "KeyPrint".  I think it
> means "key fingerpring", but I am not sure.  If that's what the real meaning
> should be, please use "key fingerprint".
>
>   

Probably, but we need some input from Jason here. I assume you are right.

> :      <screen>Mon Aug 24 17:54:07 PDT 2009 Extracting world+src for FreeBSD/amd64 7.2-RELEASE
> : @@ -411,10 +428,7 @@ to sign the release.</screen>
> :        file named <filename>USAGE</filename>.  Execute
> :        <filename>scripts/approve.sh</filename>, as directed.  This will sign
> :        the release, and move components into a staging area suitable for
> : -      uploading.  It is important to make sure that your key is mounted
> : -      during this process.  A simple <command>df</command> will show if it
> : -      is mounted.  If not mounted, mount the key with the passphrase supplied
> : -      when creating it earlier.</para>
> : +      uploading.</para>
>
> I don't know where the key mounting bits come from.  It seems to refer to
> those FreeBSD installations where PGP keys are stored in removable media, like
> a USB flash disk.  Why do we have to explicitly mention this here?  After all,
> we don't describe how gpg-agent(1) works, or how seahorse(1) integrates PGP
> with Gnome, or any other case of the dozens of PGP setups possible...
>
>   

Same here, I am not really sure what the key mounting refers to.

> : @@ -524,9 +547,11 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
> :      <note>
> :        <para>When running a patch level build, we are assuming that previous
> :         patches are in place.  When a patch build is run, it will run all
> : -       patches less than or equal to the number specified.  Beyond this,
> : -       you will have to take appropriate measures to verify authenticity
> : -       of the patch.</para>
> : +       patches less than or equal to the number specified.</para>
> : +
> : +      <para><emphasis>It is up to the administrator of the freebsd-update
> : +         server to take appropriate measures to verify the authenticity of
> : +         every patch.</emphasis></para>
>
> I think we ought to emphasize a bit the part about patch authenticity, but I
> am not sure if I chose the right way to do this.
>
>   

Or maybe use <warning> around it?

> : -    <para>Follow the same process as noted before for appoving a build.</para>
> : +    <para>Follow the same process as noted before for approving a build:</para>
>
> Typo.
>
> There are more changes, in the attached patch.  Most of them are attempts to
> improve the wording of various small parts of the article.  Please see the
> attached diff for all of them.
>
>   

The patch has been applied, the new version is available in mercurial
and also uploaded again to freefall.

> One more important detail.  We are still discussing at doceng@ how we can
> bring the final article into CVS.  So, please hold from committing this, until
> we have resolved all the remaining details.
>
>   

Yes, I am aware of this. 
Jason has thought of something like this (copied from email):

<sect1 id="afterword">
    <title>Afterword</title>

    <para>This <ulink
url="http://www.experts-exchange.com/articles/OS/Unix/BSD/FreeBSD/Build-Your-Own-FreeBSD-Update-Server.html">FreeBSD

Update </ulink> article was originally published at <ulink
url="http://www.experts-exchange.com">Experts-Exchange</ulink>.</para>
</sect1>

and I thought we could turn this into  something like "Acknowledgements
/ Further Reading" section (will probably need to be expanded a bit).
Does this make any sense?

> I'm sure that a lot of people will love reading an article that describes in
> detail how to set up a local freebsd-update server.  Thanks for all the work
> done so far on what seems to be an excellent article! :-D
>   

And we thank you for the thorough review :)
From jhelfman at e-e.com  Fri Nov 20 18:17:41 2009
From: jhelfman at e-e.com (Jason)
Date: Fri Nov 20 18:17:48 2009
Subject: [RFC] Article on freebsd-update-server
In-Reply-To: <4B06C94A.30600@FreeBSD.org>
References: <4B05BA06.3010303@FreeBSD.org> <87ws1luqmx.fsf@kobe.laptop>
	<4B06C94A.30600@FreeBSD.org>
Message-ID: <20091120181631.GF6241@eggman.experts-exchange.com>

On Fri, Nov 20, 2009 at 06:52:26PM +0200, Manolis Kiagias thus spake:
>Giorgos Keramidas wrote:
>> <SNIP> - All changes look fine up to this point
>> :      <note>
>> : -      <para>Note down the generated KeyPrint; this value is entered into
>> : -       <filename>/etc/freebsd-update.conf</filename> for binary
>> : -       updates.</para>
>> : +      <para>Keep a note of the generated key fingerpring.  This value is
>> : +       entered into <filename>/etc/freebsd-update.conf</filename> for
>> : +       binary updates.</para>
>> :      </note>
>>
>> There are various places that the article refers to  "KeyPrint".  I think it
>> means "key fingerpring", but I am not sure.  If that's what the real meaning
>> should be, please use "key fingerprint".
That is correct. It is a "key fingerprint," in this case, and it becomes the
KeyPrint value in /etc/freebsd-update.com
>>
>>
>
>Probably, but we need some input from Jason here. I assume you are right.
>
>> :      <screen>Mon Aug 24 17:54:07 PDT 2009 Extracting world+src for FreeBSD/amd64 7.2-RELEASE
>> : @@ -411,10 +428,7 @@ to sign the release.</screen>
>> :        file named <filename>USAGE</filename>.  Execute
>> :        <filename>scripts/approve.sh</filename>, as directed.  This will sign
>> :        the release, and move components into a staging area suitable for
>> : -      uploading.  It is important to make sure that your key is mounted
>> : -      during this process.  A simple <command>df</command> will show if it
>> : -      is mounted.  If not mounted, mount the key with the passphrase supplied
>> : -      when creating it earlier.</para>
>> : +      uploading.</para>
>>
>> I don't know where the key mounting bits come from.  It seems to refer to
>> those FreeBSD installations where PGP keys are stored in removable media, like
>> a USB flash disk.  Why do we have to explicitly mention this here?  After all,
>> we don't describe how gpg-agent(1) works, or how seahorse(1) integrates PGP
>> with Gnome, or any other case of the dozens of PGP setups possible...

In order to a sign a release, the key generated at the beginning of the
process needs to be mounted in order to properly approve the release and
update to code so it will work for updates. If the key is not mounted,
approving the release won't work, and then updates can't be uploaded.

>>
>>
>
>Same here, I am not really sure what the key mounting refers to.
>
>> : @@ -524,9 +547,11 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
>> :      <note>
>> :        <para>When running a patch level build, we are assuming that previous
>> :         patches are in place.  When a patch build is run, it will run all
>> : -       patches less than or equal to the number specified.  Beyond this,
>> : -       you will have to take appropriate measures to verify authenticity
>> : -       of the patch.</para>
>> : +       patches less than or equal to the number specified.</para>
>> : +
>> : +      <para><emphasis>It is up to the administrator of the freebsd-update
>> : +         server to take appropriate measures to verify the authenticity of
>> : +         every patch.</emphasis></para>
>>
>> I think we ought to emphasize a bit the part about patch authenticity, but I
>> am not sure if I chose the right way to do this.
>>
>>
>
>Or maybe use <warning> around it?
>
>> : -    <para>Follow the same process as noted before for appoving a build.</para>
>> : +    <para>Follow the same process as noted before for approving a build:</para>
>>
>> Typo.
>>
>> There are more changes, in the attached patch.  Most of them are attempts to
>> improve the wording of various small parts of the article.  Please see the
>> attached diff for all of them.
>>
>>
>
>The patch has been applied, the new version is available in mercurial
>and also uploaded again to freefall.
>
>> One more important detail.  We are still discussing at doceng@ how we can
>> bring the final article into CVS.  So, please hold from committing this, until
>> we have resolved all the remaining details.
>>
>>
>
>Yes, I am aware of this.
>Jason has thought of something like this (copied from email):
>
><sect1 id="afterword">
>    <title>Afterword</title>
>
>    <para>This <ulink
>url="http://www.experts-exchange.com/articles/OS/Unix/BSD/FreeBSD/Build-Your-Own-FreeBSD-Update-Server.html">FreeBSD
>
>Update </ulink> article was originally published at <ulink
>url="http://www.experts-exchange.com">Experts-Exchange</ulink>.</para>
></sect1>
>
>and I thought we could turn this into  something like "Acknowledgements
>/ Further Reading" section (will probably need to be expanded a bit).
>Does this make any sense?
>
>> I'm sure that a lot of people will love reading an article that describes in
>> detail how to set up a local freebsd-update server.  Thanks for all the work
>> done so far on what seems to be an excellent article! :-D
>>
>
>And we thank you for the thorough review :)
>
Thank you and I will take a look at the included file.

Jason
From jhelfman at e-e.com  Fri Nov 20 20:27:53 2009
From: jhelfman at e-e.com (Jason)
Date: Fri Nov 20 20:28:01 2009
Subject: [RFC] Article on freebsd-update-server
In-Reply-To: <87ws1luqmx.fsf@kobe.laptop>
References: <4B05BA06.3010303@FreeBSD.org>
 <87ws1luqmx.fsf@kobe.laptop>
Message-ID: <20091120202642.GK6241@eggman.experts-exchange.com>

Hi Everyone,

I've made comments inline to the patch. I would not want to make any changes
to the formatting, as I believe it is good as it stands now.

I very much appreciate everyones input, time and comments on my article,
and have learned so much in this process.

I have attached the diff with comments.

Thanks, again
Jason

On Fri, Nov 20, 2009 at 06:07:02PM +0200, Giorgos Keramidas thus spake:
>On Thu, 19 Nov 2009 23:35:02 +0200, Manolis Kiagias <manolis@FreeBSD.org> wrote:
>> Hi all,
>>
>> I am sending this to my usual reviewers and the doc@ list, everyone is
>> welcome to comment.
>>
>> Jason Helfman (jhelfman@e-e.com) is  actively involved with our
>> documentation set and you may have seen some of his patches.
>>
>> His initial contribution however is the article in this PR:
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=139095
>>
>> I've been working  on this article with Jason for quite some time, and
>> we think it's about time it gets a broader review.
>>
>> The source is here:
>>
>> http://people.freebsd.org/~manolis/patches/freebsd-update-server/article.sgml.txt
>
>Some of the changes I made locally while reading the source are shown in
>diff format below.  They are based on the latest revision of the article
>source at http://mercurial.dyndns.org/mercurial/freebsd-doc-el (the last
>change I pulled was 6d8923ea5ca3 from 2009-11-20 10:05:02 +0200).
>
>Some of the changes I made to the article are rewording, formatting,
>spell checking fixes, or other tiny nits I noticed.  Others are merely
>adding inline SGML comments.  Most of them are things we can fix before
>committing this to CVS.  There are also a few that are probably ok to
>fix later.
>
>: diff -r 6d8923ea5ca3 en_US.ISO8859-1/articles/freebsd-update-server/article.sgml
>: --- a/en_US.ISO8859-1/articles/freebsd-update-server/article.sgml       Fri Nov 20 10:05:02 2009 +0200
>: +++ b/en_US.ISO8859-1/articles/freebsd-update-server/article.sgml       Fri Nov 20 17:47:40 2009 +0200
>: @@ -80,11 +80,11 @@
>:        </listitem>
>:
>:        <listitem>
>: -       <para>An <ulink
>: -           url="&url.books.handbook;/network-apache.html">Apache
>: -           web server</ulink>, with over half of the space required for the
>: -         build.  For instance, our test builds total 4&nbsp;GB, and the
>: -         webserver space needed to distribute updates is 2.6&nbsp;GB.</para>
>: +       <para>A web server, like <ulink
>: +           url="&url.books.handbook;/network-apache.html">Apache</ulink>,
>: +         with over half of the space required for the build.  For instance,
>: +         our test builds total 4&nbsp;GB, and the webserver space needed to
>: +         distribute updates is 2.6&nbsp;GB.</para>
>:        </listitem>
>
>If freebsd-update can work with other HTTP servers, it is a good idea to avoid
>writing Apache-specific instructions.  I know a few installations of FreeBSD
>that prefer lighttpd or nginx, for example.
>
>:      <title>Configuration: Installation & Setup</title>
>:
>: -    <para>Download <ulink url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink>
>: +    <para>Download
>: +      the <ulink url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink>
>:        software.  A tarball may be downloaded, or use &man.csup.1; and the
>
>Tiny nit.
>
>:         <listitem>
>: -         <para>This is where the subroutine <function>fetchiso()</function>
>: -           declared in <filename>scripts/build.subr</filename> will contact
>: -           the configured source for downloading the &os; ISO.  This setting
>: -           is not limited to <application>ftp</application>, it may also be
>: -           a web (<application>httpd</application>) address as well.
>: -           For our purposes, ISO's are on the same server as our internal
>: -           http server that will be serving updates.  The software has been
>: -           configured to look in that location.  For this setup, we have to
>: -           alter the routine to fetch the ISO.  By copying the source
>: -           <filename>build.subr</filename> to
>: -           <filename>scripts/RELEASE/ARCHITECTURE/build.subr</filename> this
>: -           file will be sourced instead of the released source for
>: -           <filename>build.subr</filename>.</para>
>: +         <para>This is the location where ISO images are downloaded from (by
>: +           the <function>fetchiso()</function> subroutine
>: +           of <filename>scripts/build.subr</filename>).  The location
>: +           configured here is not limited to FTP URIs.  Any URI scheme
>: +           supported by the standard &man.fetch.1; utility should work fine.
>: +           In our own setup the ISO images are on the same internal http
>: +           server that will be serving the updates.</para>
>: +
>: +         <para>Customizations to the <function>fetchiso()</function> code can
>: +           be installed by copying the
>: +           default <filename>build.subr</filename> script to the release- and
>: +           architecture-specific area
>: +           at <filename>scripts/RELEASE/ARCHITECTURE/build.subr</filename>
>: +           and applying local edits.</para>
>
>I tried to reword the original text here.  If you like the new version, please
>feel free to keep it.  If not, we have to find a good way to simplify the
>large sentences of the original.
>
>:         <term><literal>BUILDHOSTNAME</literal></term>
>:
>:         <listitem>
>: -         <para>Host where software will be built.  Coincidentally, this
>: -           information will be displayed on updated systems when
>: -           issuing:</para>
>: +         <para>The name of the build host.  This information will be
>: +           displayed on updated systems when issuing:</para>
>
>"Coincidentally" seems superfluous here.
>
>:         <term><literal>SSHKEY</literal></term>
>:
>:         <listitem>
>: -         <para>Key used when uploading data to an update server which will
>: -           provide patches or upgrades to clients.  A key pair may be
>: -           created using <command>ssh-keygen -t dsa</command>.  Alteration
>: -           of this parameter is not required as stadnard password
>: -           authentication through <application>ssh</application> will be
>: -           used.</para>
>: +         <para>The <application>SSH</application> key for uploading files to
>: +           the update server.  A key pair can be created by
>: +           typing <command>ssh-keygen -t dsa</command>.  This parameter is
>: +           optional; standard password authentication will be used as a
>: +           fallback authentication method when <literal>SSHKEY</literal> is
>: +           not defined.</para>
>:
>: -         <para>&man.ssh-keygen.1; has more detailed information in creating
>: -           a key pair.</para>
>: +         <para>&man.ssh-keygen.1; has more detailed information
>: +           about <application>SSH</application> and the appropriate steps for
>: +           creating and using one.</para>
>
>Another suggestion for rewording the text, writing smaller sentences, and
>other minor wording nits.
>
>:         <listitem>
>: -         <para>Account that files are uploaded to on remote system.</para>
>: +         <para>Account that files are uploaded to on the update
>: +           server.</para>
>:         </listitem>
>:        </varlistentry>
>:
>: @@ -194,54 +197,68 @@ MASTERDIR=update-master.freebsd.org</pro
>:         <term><literal>MASTERDIR</literal></term>
>:
>:         <listitem>
>: -         <para>Directory where files are uploaded to on remote
>: -           system.</para>
>: +         <para>Directory where files are uploaded to on the update
>: +           server.</para>
>
>I think I like "update server" better than "remote system" here.  The update
>server may be the same machine that builds the snapshots.  By removing the
>unstated assumption that it is *not*, the text sounds more accurate.
>
>:        </varlistentry>
>:      </variablelist>
>:
>: -    <para>Now that build directives are set, the installation files are
>: -      configured for a build.  For this example, we will use
>: -      <literal>RELEASE-7.2</literal> under <literal>amd64</literal>
>: -      architecture.  Configuration files for &i386;
>: -      architecture are available with downloaded source.</para>
>: +     <para>The default <filename>build.conf</filename> file shipped with
>: +       the <application>freebsd-update-server</application> sources are
>: +       suitable for building &i386; releases of &os;.  As an example of
>: +       building an update server for other architectures we will show in
>: +       the following paragraphs the configuration changes needed for an
>: +       AMD64 update server:</para>
>
>We haven't actually described *any* installation so far.  So I changed this
>part to describe what freebsd-update-server defaults seem to be, and switched
>the rest of the section from alternating text and <screen> samples to a
><procedure> with separate steps:
>
>: -    <para>Create build environment directory under <filename
>: -       class="directory">scripts/RELEASE-7.2/amd64</filename>.</para>
>: +    <procedure>
>: +      <step>
>: +        <para>Create a build environment for AMD64:</para>
>:
>: -    <informalexample>
>: -      <screen>&prompt.user; <userinput>mkdir -p /usr/local/freebsd-update-server/scripts/RELEASE-7.2/amd64</userinput></screen>
>: -    </informalexample>
>: +        <informalexample>
>: +          <screen>&prompt.user; <userinput>mkdir -p /usr/local/freebsd-update-server/scripts/RELEASE-7.2/amd64</userinput></screen>
>: +        </informalexample>
>: +      </step>
>:
>: -    <para>This is the <filename>build.conf</filename> file that should be
>: -      placed in the directory just created.</para>
>: +      <step>
>:
>: -    <programlisting># SHA256 hash of RELEASE disc1.iso image.
>: +        <para>Install a <filename>build.conf</filename> file in the
>: +          newly created build directory.  The build configuration
>: +          options for &os; 7.2-RELEASE on AMD64 should be similar
>: +          to:</para>
>: +
>: +        <programlisting># SHA256 hash of RELEASE disc1.iso image.
>:  export RELH=1ea1f6f652d7c5f5eab7ef9f8edbed50cb664b08ed761850f95f48e86cc71ef5
>:
>:  # Components of the world, source, and kernels
>:  export WORLDPARTS="base catpages dict doc games info manpages proflibs lib32"
>: -export SOURCEPARTS="base bin contrib crypto etc games gnu include krb5 \
>: -               lib libexec release rescue sbin secure share sys tools  \
>: -               ubin usbin cddl"
>: +export SOURCEPARTS="base bin contrib crypto etc games gnu include krb5  \
>: +                lib libexec release rescue sbin secure share sys tools  \
>: +                ubin usbin cddl"
>:  export KERNELPARTS="generic"
>:
>:  # EOL date
>:  export EOL=1275289200</programlisting>
>:
>: -    <note>
>: -      <para>To generate the "End of Life" number for
>: -       <filename>build.conf</filename>, refer to the "Estimated EOL" posted
>: -       on the <ulink url="&url.base;/security/security.html">&os;
>: -       Security Website</ulink>.  Based on this date, you can issue
>: -       <command>date -j -f '%Y%m%d-%H%M%S' '20090401-000000' +%s</command>,
>: -       and substitute actual date parameters for those stated by
>: -       &os;.</para>
>: +        <note>
>: +          <para>To generate the "End of Life" number for
>: +            <filename>build.conf</filename>, refer to the "Estimated
>: +            EOL" posted on
>: +            the <ulink url="&url.base;/security/security.html">&os;
>: +              Security Website</ulink>.  You can derive the value
>: +            of <literal>EOL</literal> from the date listed on the web
>: +            site, using the &man.date.1; utility, e.g.:</para>
>:
>: -      <para>The &man.sha256.1; hash key for the desired release, is
>: -       published within the respective <ulink
>: -         url="&url.base;/releases/">release announcement </ulink>.</para>
>: -    </note>
>: +          <screen>&prompt.user; <userinput>date -j -f '%Y%m%d-%H%M%S' '20090401-000000' '+%s'</userinput></screen>
>: +        </note>
>: +
>: +        <note>
>: +          <para>The &man.sha256.1; hash key for the desired release, is
>: +            published within the
>: +            respective <ulink url="&url.base;/releases/">release
>: +              announcement</ulink>.</para>
>: +        </note>
>: +      </step>
>: +    </procedure>
>:    </sect1>
>
>NOTE: The <notes> above can probably stand on their own, outside of the
><procedure> element.
>
>:    <sect1 id="build">
>: @@ -273,9 +290,9 @@ enter aes-256-cbc encryption password:
>:  Verifying - enter aes-256-cbc encryption password:</screen>
>:
>:      <note>
>: -      <para>Note down the generated KeyPrint; this value is entered into
>: -       <filename>/etc/freebsd-update.conf</filename> for binary
>: -       updates.</para>
>: +      <para>Keep a note of the generated key fingerpring.  This value is
>: +       entered into <filename>/etc/freebsd-update.conf</filename> for
>: +       binary updates.</para>
>:      </note>
>
>There are various places that the article refers to  "KeyPrint".  I think it
>means "key fingerpring", but I am not sure.  If that's what the real meaning
>should be, please use "key fingerprint".
>
>:      <screen>Mon Aug 24 17:54:07 PDT 2009 Extracting world+src for FreeBSD/amd64 7.2-RELEASE
>: @@ -411,10 +428,7 @@ to sign the release.</screen>
>:        file named <filename>USAGE</filename>.  Execute
>:        <filename>scripts/approve.sh</filename>, as directed.  This will sign
>:        the release, and move components into a staging area suitable for
>: -      uploading.  It is important to make sure that your key is mounted
>: -      during this process.  A simple <command>df</command> will show if it
>: -      is mounted.  If not mounted, mount the key with the passphrase supplied
>: -      when creating it earlier.</para>
>: +      uploading.</para>
>
>I don't know where the key mounting bits come from.  It seems to refer to
>those FreeBSD installations where PGP keys are stored in removable media, like
>a USB flash disk.  Why do we have to explicitly mention this here?  After all,
>we don't describe how gpg-agent(1) works, or how seahorse(1) integrates PGP
>with Gnome, or any other case of the dozens of PGP setups possible...
>
>: @@ -524,9 +547,11 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
>:      <note>
>:        <para>When running a patch level build, we are assuming that previous
>:         patches are in place.  When a patch build is run, it will run all
>: -       patches less than or equal to the number specified.  Beyond this,
>: -       you will have to take appropriate measures to verify authenticity
>: -       of the patch.</para>
>: +       patches less than or equal to the number specified.</para>
>: +
>: +      <para><emphasis>It is up to the administrator of the freebsd-update
>: +         server to take appropriate measures to verify the authenticity of
>: +         every patch.</emphasis></para>
>
>I think we ought to emphasize a bit the part about patch authenticity, but I
>am not sure if I chose the right way to do this.
>
>: -    <para>Follow the same process as noted before for appoving a build.</para>
>: +    <para>Follow the same process as noted before for approving a build:</para>
>
>Typo.
>
>There are more changes, in the attached patch.  Most of them are attempts to
>improve the wording of various small parts of the article.  Please see the
>attached diff for all of them.
>
>One more important detail.  We are still discussing at doceng@ how we can
>bring the final article into CVS.  So, please hold from committing this, until
>we have resolved all the remaining details.
>
>I'm sure that a lot of people will love reading an article that describes in
>detail how to set up a local freebsd-update server.  Thanks for all the work
>done so far on what seems to be an excellent article! :-D
>

>diff -r 6d8923ea5ca3 en_US.ISO8859-1/articles/freebsd-update-server/article.sgml
>--- a/en_US.ISO8859-1/articles/freebsd-update-server/article.sgml	Fri Nov 20 10:05:02 2009 +0200
>+++ b/en_US.ISO8859-1/articles/freebsd-update-server/article.sgml	Fri Nov 20 17:48:23 2009 +0200
>@@ -80,11 +80,11 @@
>       </listitem>
> 
>       <listitem>
>-	<para>An <ulink
>-	    url="&url.books.handbook;/network-apache.html">Apache
>-	    web server</ulink>, with over half of the space required for the
>-	  build.  For instance, our test builds total 4&nbsp;GB, and the
>-	  webserver space needed to distribute updates is 2.6&nbsp;GB.</para>
>+	<para>A web server, like <ulink
>+	    url="&url.books.handbook;/network-apache.html">Apache</ulink>,
>+	  with over half of the space required for the build.  For instance,
>+	  our test builds total 4&nbsp;GB, and the webserver space needed to
>+	  distribute updates is 2.6&nbsp;GB.</para>
>       </listitem>
> 
>       <listitem>
>@@ -97,7 +97,8 @@
>   <sect1 id="Configuration">
>     <title>Configuration: Installation & Setup</title>
> 
>-    <para>Download <ulink url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink>
>+    <para>Download
>+      the <ulink url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink>
>       software.  A tarball may be downloaded, or use &man.csup.1; and the
>       <literal>projects-all</literal> collection.</para>
> 
>@@ -138,19 +139,20 @@ MASTERDIR=update-master.freebsd.org</pro
> 	<term><literal>FTP</literal></term>
> 
> 	<listitem>
>-	  <para>This is where the subroutine <function>fetchiso()</function>
>-	    declared in <filename>scripts/build.subr</filename> will contact
>-	    the configured source for downloading the &os; ISO.  This setting
>-	    is not limited to <application>ftp</application>, it may also be
>-	    a web (<application>httpd</application>) address as well.
>-	    For our purposes, ISO's are on the same server as our internal
>-	    http server that will be serving updates.  The software has been
>-	    configured to look in that location.  For this setup, we have to
>-	    alter the routine to fetch the ISO.  By copying the source
>-	    <filename>build.subr</filename> to
>-	    <filename>scripts/RELEASE/ARCHITECTURE/build.subr</filename> this
>-	    file will be sourced instead of the released source for
>-	    <filename>build.subr</filename>.</para>
>+	  <para>This is the location where ISO images are downloaded from (by
>+	    the <function>fetchiso()</function> subroutine
>+	    of <filename>scripts/build.subr</filename>).  The location
>+	    configured here is not limited to FTP URIs.  Any URI scheme
>+	    supported by the standard &man.fetch.1; utility should work fine.
>+	    In our own setup the ISO images are on the same internal http
>+	    server that will be serving the updates.</para>
>+
>+	  <para>Customizations to the <function>fetchiso()</function> code can
>+	    be installed by copying the
>+	    default <filename>build.subr</filename> script to the release- and
>+	    architecture-specific area
>+	    at <filename>scripts/RELEASE/ARCHITECTURE/build.subr</filename>
>+	    and applying local edits.</para>
> 	</listitem>
>       </varlistentry>
> 
>@@ -158,9 +160,8 @@ MASTERDIR=update-master.freebsd.org</pro
> 	<term><literal>BUILDHOSTNAME</literal></term>
> 
> 	<listitem>
>-	  <para>Host where software will be built.  Coincidentally, this
>-	    information will be displayed on updated systems when
>-	    issuing:</para>
>+	  <para>The name of the build host.  This information will be
>+	    displayed on updated systems when issuing:</para>
> 
> 	  <screen>&prompt.user; <userinput>uname -v</userinput></screen>
> 	</listitem>
>@@ -170,15 +171,16 @@ MASTERDIR=update-master.freebsd.org</pro
> 	<term><literal>SSHKEY</literal></term>
> 
> 	<listitem>
>-	  <para>Key used when uploading data to an update server which will
>-	    provide patches or upgrades to clients.  A key pair may be
>-	    created using <command>ssh-keygen -t dsa</command>.  Alteration
>-	    of this parameter is not required as stadnard password
>-	    authentication through <application>ssh</application> will be
>-	    used.</para>
>+	  <para>The <application>SSH</application> key for uploading files to
>+	    the update server.  A key pair can be created by
>+	    typing <command>ssh-keygen -t dsa</command>.  This parameter is
>+	    optional; standard password authentication will be used as a
>+	    fallback authentication method when <literal>SSHKEY</literal> is
>+	    not defined.</para>
> 
>-	  <para>&man.ssh-keygen.1; has more detailed information in creating
>-	    a key pair.</para>
>+	  <para>&man.ssh-keygen.1; has more detailed information
>+	    about <application>SSH</application> and the appropriate steps for
>+	    creating and using one.</para>
> 	</listitem>
>       </varlistentry>
> 
>@@ -186,7 +188,8 @@ MASTERDIR=update-master.freebsd.org</pro
> 	<term><literal>MASTERACCT</literal></term>
> 
> 	<listitem>
>-	  <para>Account that files are uploaded to on remote system.</para>
>+	  <para>Account that files are uploaded to on the update
>+	    server.</para>
> 	</listitem>
>       </varlistentry>
> 
>@@ -194,54 +197,68 @@ MASTERDIR=update-master.freebsd.org</pro
> 	<term><literal>MASTERDIR</literal></term>
> 
> 	<listitem>
>-	  <para>Directory where files are uploaded to on remote
>-	    system.</para>
>+	  <para>Directory where files are uploaded to on the update
>+	    server.</para>
> 	</listitem>
>       </varlistentry>
>     </variablelist>
> 
>-    <para>Now that build directives are set, the installation files are
>-      configured for a build.  For this example, we will use
>-      <literal>RELEASE-7.2</literal> under <literal>amd64</literal>
>-      architecture.  Configuration files for &i386;
>-      architecture are available with downloaded source.</para>
>+     <para>The default <filename>build.conf</filename> file shipped with
>+       the <application>freebsd-update-server</application> sources are
>+       suitable for building &i386; releases of &os;.  As an example of
>+       building an update server for other architectures we will show in
>+       the following paragraphs the configuration changes needed for an
>+       AMD64 update server:</para>
> 
>-    <para>Create build environment directory under <filename
>-	class="directory">scripts/RELEASE-7.2/amd64</filename>.</para>
>+    <procedure>
>+      <step>
>+        <para>Create a build environment for AMD64:</para>
> 
>-    <informalexample>
>-      <screen>&prompt.user; <userinput>mkdir -p /usr/local/freebsd-update-server/scripts/RELEASE-7.2/amd64</userinput></screen>
>-    </informalexample>
>+        <informalexample>
>+          <screen>&prompt.user; <userinput>mkdir -p /usr/local/freebsd-update-server/scripts/RELEASE-7.2/amd64</userinput></screen>
>+        </informalexample>
>+      </step>
> 
>-    <para>This is the <filename>build.conf</filename> file that should be
>-      placed in the directory just created.</para>
>+      <step>
> 
>-    <programlisting># SHA256 hash of RELEASE disc1.iso image.
>+        <para>Install a <filename>build.conf</filename> file in the
>+          newly created build directory.  The build configuration
>+          options for &os; 7.2-RELEASE on AMD64 should be similar
>+          to:</para>
>+
>+        <programlisting># SHA256 hash of RELEASE disc1.iso image.
> export RELH=1ea1f6f652d7c5f5eab7ef9f8edbed50cb664b08ed761850f95f48e86cc71ef5
> 
> # Components of the world, source, and kernels
> export WORLDPARTS="base catpages dict doc games info manpages proflibs lib32"
>-export SOURCEPARTS="base bin contrib crypto etc games gnu include krb5	\
>-		lib libexec release rescue sbin secure share sys tools	\
>-		ubin usbin cddl"
>+export SOURCEPARTS="base bin contrib crypto etc games gnu include krb5  \
>+                lib libexec release rescue sbin secure share sys tools  \
>+                ubin usbin cddl"
> export KERNELPARTS="generic"
> 
> # EOL date
> export EOL=1275289200</programlisting>
> 
>-    <note>
>-      <para>To generate the "End of Life" number for
>-	<filename>build.conf</filename>, refer to the "Estimated EOL" posted
>-	on the <ulink url="&url.base;/security/security.html">&os;
>-	Security Website</ulink>.  Based on this date, you can issue
>-	<command>date -j -f '%Y%m%d-%H%M%S' '20090401-000000' +%s</command>,
>-	and substitute actual date parameters for those stated by
>-	&os;.</para>
>+        <note>
>+          <para>To generate the "End of Life" number for
>+            <filename>build.conf</filename>, refer to the "Estimated
>+            EOL" posted on
>+            the <ulink url="&url.base;/security/security.html">&os;
>+              Security Website</ulink>.  You can derive the value
>+            of <literal>EOL</literal> from the date listed on the web
>+            site, using the &man.date.1; utility, e.g.:</para>
> 
>-      <para>The &man.sha256.1; hash key for the desired release, is
>-	published within the respective <ulink
>-	  url="&url.base;/releases/">release announcement </ulink>.</para>
>-    </note>
>+          <screen>&prompt.user; <userinput>date -j -f '%Y%m%d-%H%M%S' '20090401-000000' '+%s'</userinput></screen>
>+        </note>
>+
>+        <note>
>+          <para>The &man.sha256.1; hash key for the desired release, is
>+            published within the
>+            respective <ulink url="&url.base;/releases/">release
>+              announcement</ulink>.</para>
>+        </note>
>+      </step>
>+    </procedure>
>   </sect1>
> 
>   <sect1 id="build">
>@@ -273,9 +290,9 @@ enter aes-256-cbc encryption password:
> Verifying - enter aes-256-cbc encryption password:</screen>
> 
>     <note>
>-      <para>Note down the generated KeyPrint; this value is entered into
>-	<filename>/etc/freebsd-update.conf</filename> for binary
>-	updates.</para>
>+      <para>Keep a note of the generated key fingerpring.  This value is
>+	entered into <filename>/etc/freebsd-update.conf</filename> for
>+	binary updates.</para>
>     </note>
> 
>     <para>At this point, we are ready to stage a build.</para>
>@@ -330,8 +347,8 @@ world|base|/usr/lib/libalias_ftp.a
> 
>     <note>
>       <para>Then the build of the world is performed again, with world
>-	patches.  A more detailed explanation may be found in
>-	<filename>scripts/build.subr</filename>.</para>
>+	patches.  A more detailed explanation may be found
>+	in <filename>scripts/build.subr</filename>.</para>
>     </note>
> 
>     <screen>Mon Aug 24 17:54:07 PDT 2009 Extracting world+src for FreeBSD/amd64 7.2-RELEASE
>@@ -411,10 +428,7 @@ to sign the release.</screen>
>       file named <filename>USAGE</filename>.  Execute
>       <filename>scripts/approve.sh</filename>, as directed.  This will sign
>       the release, and move components into a staging area suitable for
>-      uploading.  It is important to make sure that your key is mounted
>-      during this process.  A simple <command>df</command> will show if it
>-      is mounted.  If not mounted, mount the key with the passphrase supplied
>-      when creating it earlier.</para>
>+      uploading.</para>
> 
>     <informalexample>
>       <screen>&prompt.root; <userinput>cd /usr/local/freebsd-update-server</userinput>
>@@ -436,6 +450,8 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
> &prompt.root; <userinput>sh scripts/upload.sh <replaceable>amd64 RELEASE-7.2</replaceable></userinput></screen>
>     </informalexample>
> 
>+    <!-- If freebsd-update works with other http servers too, we should
>+	 avoid making the instructions Apache-specific here. -->
>     <para>The uploaded files will need to be in the
>       <literal>DocumentRoot</literal> of the webserver in order for updates
>       to be distributed.  For further explanation, please refer to the
>@@ -443,6 +459,10 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
> 	url="&url.books.handbook;/network-apache.html">Apache
> 	documentation</ulink>.</para>
> 
>+    <!-- This note seems either out of place.  I find it hard to read and it
>+	 is a bit difficult to understand why it is related to the rest of
>+	 this section.  It looks like something that would fit nicely in an
>+	 introductory section about the way a freebsd-update server works. -->
>     <note>
>       <para>Updates for the current release of the &os; system you are
> 	updating, and what you want to upgrade <emphasis>to</emphasis> need
>@@ -453,11 +473,14 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
> 	&os; 7.2-RELEASE.</para>
>     </note>
> 
>+    <!-- What is a 'KeyPrint'? -->
>     <para>Update client's <literal>KeyPrint</literal> and
>       <literal>ServerName</literal> in
>       <filename>/etc/freebsd-update.conf</filename>, and perform updates as
>       instructed in the <ulink
> 	url="&url.books.handbook;/updating-freebsdupdate.html">&os; Update</ulink>
>+      <!-- One sentence, two instances of 'in'.  We can probably reword this
>+	   part to avoid repetition. -->
>       instructions in the Handbook.</para>
> 
>     <para>For reference, here is the entire run of <ulink
>@@ -467,9 +490,9 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
>   <sect1 id="patch">
>     <title>Building a Patch</title>
> 
>-    <para>In the event a <ulink
>+    <para>Every time a <ulink
> 	url="&url.base;/security/advisories.html">security advisory</ulink>
>-      is posted, a patch update can be built.</para>
>+      is announced, a patch update can be built.</para>
> 
>     <para>For this example, we will be using 7.1-RELEASE.</para>
> 
>@@ -487,8 +510,8 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
>       </listitem>
>     </itemizedlist>
> 
>-    <para>Create patch directory under
>-      <filename class="directory">/usr/local/freebsd-update-server/patches/</filename> for the respective release.</para>
>+    <para>Create the patch directory of the respective release
>+      under <filename class="directory">/usr/local/freebsd-update-server/patches/</filename>.</para>
> 
>     <informalexample>
>       <screen>&prompt.user; <userinput>mkdir -p /usr/local/freebsd-update-server/patches/RELEASE-7.1/</userinput></screen>
>@@ -507,8 +530,8 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
>       we can see it is called <literal>SA-09:12.bind</literal>.  After
>       downloading the file, it is required to rename the file to an
>       appropriate patch level.  It is suggested to keep this inline with
>-      official &os; patch levels, however, this is just a suggestion.
>-      For this build, let us follow the brief and call this
>+      official &os; patch levels, but you are free to choose any name you prefer.
>+      For this build, let us follow the currently established practice of &os; and call this
>       <literal>p7</literal>.  Rename the file:</para>
> 
>     <informalexample>
>@@ -524,9 +547,11 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st
>     <note>
>       <para>When running a patch level build, we are assuming that previous
> 	patches are in place.  When a patch build is run, it will run all
>-	patches less than or equal to the number specified.  Beyond this,
>-	you will have to take appropriate measures to verify authenticity
>-	of the patch.</para>
>+	patches less than or equal to the number specified.</para>
>+
>+      <para><emphasis>It is up to the administrator of the freebsd-update
>+	  server to take appropriate measures to verify the authenticity of
>+	  every patch.</emphasis></para>
> 
>       <para>You can also add your own patches to any build.  Use the number
> 	zero, or any other number.</para>
>@@ -642,7 +667,7 @@ files to confirm that they look sensible
> # sh -e approve.sh amd64 7.1-RELEASE
> to sign the build.</screen>
> 
>-    <para>Follow the same process as noted before for appoving a build.</para>
>+    <para>Follow the same process as noted before for approving a build:</para>
> 
>     <screen>&prompt.root; <userinput>sh -e scripts/approve.sh amd64 7.1-RELEASE</userinput>
> Wed Aug 26 12:50:06 PDT 2009 Signing build for FreeBSD/amd64 7.1-RELEASE
>@@ -657,7 +682,7 @@ ready to be uploaded.  Remember to run
> to unmount the decrypted key once you have finished signing all
> the new builds.</screen>
> 
>-    <para>After approving the build, upload the software.</para>
>+    <para>After approving the build, upload the software:</para>
> 
>     <informalexample>
>       <screen>&prompt.root; <userinput>cd /usr/local/freebsd-update-server</userinput>
>@@ -671,21 +696,40 @@ the new builds.</screen>
>   <sect1 id="tips">
>     <title>Tips</title>
> 
>+    <!-- These are nice tips, but there are only a few of them and they need a
>+	 bit of rewording to make sense.  I'd like to see something that
>+	 explains at least the following for every tip:
>+
>+	 * Why is this tip necessary?  What is the original problem it tries
>+	   to solve?
>+	 * How to install the changes of the tip (preferrably in a <procedure>
>+	   element, with clearly separated steps.
>+	 * How to check that the changes of the tip had a measurable and
>+	   noticeable effect.
>+
>+	 We can do this in a followup commit.  It doesn't have to be completed
>+	 *before* we commit this to CVS. -->
>+
>     <itemizedlist>
>       <listitem>
> 	<para>If you build your own release using the native
>-	  <command>make release</command>,
>+	  <command>make release</command> procedure, the
> 	  <application>freebsd-update-server</application> code will work
>+	  <!-- "from your release" seems a bit odd.  I think this part means
>+	       that the freebsd-update code can be tweaked to build custom,
>+	       locally tuned release snapshots.  Is that so? -->
> 	  from your release.  As an example, you may build a release without
> 	  ports or documentation and add a custom kernel.  After removing
> 	  functionality pertaining to the documentation subroutine and
>-	  altering the <literal>buildworld()</literal> subroutine in
>-	  <filename>scripts/build.subr</filename> the
>+	  altering the <function>buildworld()</function> subroutine in
>+	  <filename>scripts/build.subr</filename>, the
> 	  <application>freebsd-update-code</application> will successfully
> 	  build update code on this release.</para>
>       </listitem>
> 
>       <listitem>
>+	<!-- We seem to be contradicting ourselves here.  Is it safe to add -j
>+	     or other flags?  If not, why are we recommending it? -->
> 	<para>Add <command>make -j <replaceable>NUMBER</replaceable></command>
> 	  to <filename>scripts/build.subr</filename> to speed up processing.
> 	  Adding flags to anything other than
>@@ -695,6 +739,10 @@ the new builds.</screen>
>       </listitem>
> 
>       <listitem>
>+	<!-- Parse error.  I don't understand what this paragraph suggests or
>+	     recommends.  Also, why do we need to block RSTs?  I don't really
>+	     like gratuitous blocking of RST, ICMP or other packets.  Our
>+	     kernel can rate-limit most of the "strange" packets alredy. -->
> 	<para>Create a firewall rule to block outgoing RST packets.  Due to
> 	  a bug noted <ulink
> 	    url="http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2009-04/msg00365.html">in this posting</ulink>,




-- 
i am a mutthead
-------------- next part --------------
A non-text attachment was scrubbed...
Name: freebsd-update.6d8923ea5ca3.diff
Type: text/x-diff
Size: 20879 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20091120/a1ef3ac9/freebsd-update.6d8923ea5ca3.bin
From glen.j.barber at gmail.com  Sat Nov 21 03:30:02 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Sat Nov 21 03:30:08 2009
Subject: docs/140733: [patch] Broken Link to "The Design and Implementation
	of the 4.4BSD Operating System" book
Message-ID: <200911210327.nAL3RN4n088173@www.freebsd.org>


>Number:         140733
>Category:       docs
>Synopsis:       [patch] Broken Link to "The Design and Implementation of the 4.4BSD Operating System" book
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 21 03:30:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Glen Barber
>Release:        8.0-PRERELEASE
>Organization:
>Environment:
FreeBSD orion 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #2 r199595: Fri Nov 20 20:58:23 EST 2009     root@orion:/usr/obj/usr/src/sys/ORION  amd64
>Description:
Link to external resource for the book "The Design and Implementation of the 4.4BSD Operating System" is broken.

http://www.freebsd.org/doc/en/books/design-44bsd/
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- books/design-44bsd/book.sgml.orig	2004-08-08 09:43:57.000000000 -0400
+++ books/design-44bsd/book.sgml	2009-11-20 22:20:32.000000000 -0500
@@ -50,9 +50,9 @@
 	may be further reproduced or distributed without the publisher's
 	express written
 	<ulink url="mailto:peter.gordon@awl.com">permission</ulink>.  The
-	rest of
-	<ulink url="http://cseng.aw.com/book/0,3828,0201549794,00.html">the
-	  book</ulink> explores the concepts introduced in this chapter in
+	rest of <ulink 
+	url="http://cseng.aw.com/catalog/academic/product/0,1144,0201549794,00.html">
+	the book</ulink> explores the concepts introduced in this chapter in
 	incredible detail and is an excellent reference for anyone with an
 	interest in BSD UNIX.  More information about this book is available
 	from the publisher, with whom you can also sign up to receive news


>Release-Note:
>Audit-Trail:
>Unformatted:
From trhodes at FreeBSD.org  Sat Nov 21 04:06:59 2009
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Sat Nov 21 04:07:05 2009
Subject: [RFC] Article on freebsd-update-server
In-Reply-To: <87ws1luqmx.fsf@kobe.laptop>
References: <4B05BA06.3010303@FreeBSD.org>
	<87ws1luqmx.fsf@kobe.laptop>
Message-ID: <20091120230650.1bbc849e.trhodes@FreeBSD.org>

On Fri, 20 Nov 2009 18:07:02 +0200
Giorgos Keramidas <keramida@FreeBSD.org> wrote:

[BIG SNIP]: Patch explanation, patch, review request, not in that
order.  :)

> 
> One more important detail.  We are still discussing at doceng@ how we can
> bring the final article into CVS.  So, please hold from committing this, until
> we have resolved all the remaining details.

This makes me feel funny.  And not the kind of good funny that
earns someone a candybar when it's all over, but a strange kind of
decisions in the back room by a select few kind of funny ...

> 
> I'm sure that a lot of people will love reading an article that describes in
> detail how to set up a local freebsd-update server.  Thanks for all the work
> done so far on what seems to be an excellent article! :-D
> 
> 

Several years ago, when the freebsd-update software came out,
I investigated using it to distribute software and patches
to a large cluster of machines.  Unfortunately I didn't get
that far because the internal bits were a closely guarded
secret, Colin only asked why anyone would need to run one.

That said, I think it's awesome we can do this now, and I'll
definitely be trying out the article in the future.  :)

Cheers,

-- 
Tom Rhodes
From miwi at FreeBSD.org  Sat Nov 21 09:13:25 2009
From: miwi at FreeBSD.org (miwi@FreeBSD.org)
Date: Sat Nov 21 09:13:31 2009
Subject: docs/140733: [patch] Broken Link to "The Design and
	Implementation of the 4.4BSD Operating System" book
Message-ID: <200911210913.nAL9DOX1097075@freefall.freebsd.org>

Synopsis: [patch] Broken Link to "The Design and Implementation of the 4.4BSD Operating System" book

State-Changed-From-To: open->closed
State-Changed-By: miwi
State-Changed-When: Sat Nov 21 09:13:24 UTC 2009
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=140733
From dfilter at FreeBSD.ORG  Sat Nov 21 09:20:05 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sat Nov 21 09:20:32 2009
Subject: docs/140733: commit references a PR
Message-ID: <200911210920.nAL9K5in097749@freefall.freebsd.org>

The following reply was made to PR docs/140733; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/140733: commit references a PR
Date: Sat, 21 Nov 2009 09:12:39 +0000 (UTC)

 miwi        2009-11-21 09:12:25 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en_US.ISO8859-1/books/design-44bsd book.sgml 
   Log:
   - Fix a broken link
   
   PR:             140733
   Submitted by:   Glen Barber <glen.j.barber@gmail.com>
   
   Revision  Changes    Path
   1.9       +1 -1      doc/en_US.ISO8859-1/books/design-44bsd/book.sgml
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
From gabor at FreeBSD.org  Sat Nov 21 12:43:43 2009
From: gabor at FreeBSD.org (Gabor Kovesdan)
Date: Sat Nov 21 12:43:49 2009
Subject: [RFC] Article on freebsd-update-server
In-Reply-To: <20091120181631.GF6241@eggman.experts-exchange.com>
References: <4B05BA06.3010303@FreeBSD.org>
	<87ws1luqmx.fsf@kobe.laptop>	<4B06C94A.30600@FreeBSD.org>
	<20091120181631.GF6241@eggman.experts-exchange.com>
Message-ID: <4B07E077.3010609@FreeBSD.org>


>>> One more important detail.  We are still discussing at doceng@ how 
>>> we can
>>> bring the final article into CVS.  So, please hold from committing 
>>> this, until
>>> we have resolved all the remaining details.
Could someone please elaborate what these details are? Why this case is 
different from the usual practice? (cvs add && cvs commit)

-- 
Gabor Kovesdan
FreeBSD Volunteer

EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org
WEB:   http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org

From killasmurf86 at gmail.com  Sat Nov 21 14:40:02 2009
From: killasmurf86 at gmail.com (Aldis Berjoza)
Date: Sat Nov 21 14:40:09 2009
Subject: docs/140754: Bad example in handbook 18.5.2
Message-ID: <1258814165.3370@killasmurf86.pc>


>Number:         140754
>Category:       docs
>Synopsis:       Bad example in handbook 18.5.2
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 21 14:40:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Aldis Berjoza
>Release:        FreeBSD 8.0-RC3 i386
>Organization:
>Environment:


System: FreeBSD 8.0-RC3 #0: Fri Nov 13 16:14:51 EET 2009
    killasmurf86@killasmurf86.pc:/usr/obj/usr/src/sys/ANTIGENERIC



>Description:


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/usb-disks.html#AEN24782

Handbook:
The final step is to create a directory where the file system is to be mounted. This directory needs to be owned by the user that is to mount the file system. One way to do that is for root to create a subdirectory owned by that user as /mnt/username (replace username by the login name of the actual user and usergroup by the user's primary group):
# mkdir /mnt/username
# chown username:usergroup /mnt/username

This isn't good. Because in most cases /mnt is just directory on root partition, and noone will probably want to create new slice/partition for /mnt if it's not used.

I think a much better example would be to recommed create ~/mnt instead:
# mkdir /home/username/mnt
# chown username:usergroup /home/username/mnt

Because usually /home is on separate slice partition.

Why original example is bad?
Because if for some reason destination is not mounted (/mnt/username), user still can copy files there. This way user can make root ful (willingly or unwillingly)

Since /home is usually on separate slice/partition user can do whatever he wants.

I hope you understand what I'm trying to say


>How-To-Repeat:





>Fix:


s/\/mnt\/username/\/home\/username\/mnt/



>Release-Note:
>Audit-Trail:
>Unformatted:
From newsletter at carproperty.com  Sat Nov 21 22:56:49 2009
From: newsletter at carproperty.com (CarProperty.com)
Date: Sat Nov 21 22:57:05 2009
Subject: Ford 400 AD Sale - Save 35% until 11/30/2009
Message-ID: <20091121225218.6008.1381523437.swift@mail.carproperty.com>

Use Promo Code: Ford400 ... to save 35% off all CarProperty.com listings ... this 0ffer expires November 30, 2009 @  11:59pm PST

GO HERE FOR THE FULL DETAILS:  http://www.carproperty.com/page.php?id=33


Try the CarProperty.com Map Search at this link http://www.carproperty.com/mapsearch.php

Your AD will show up on this incredible map searching tool and it will be very easy to find!

We love these guys ... check them out:

America's Car Show http://www.AmericasCarShow.com, broadcast live on Sirius XM Radio ... listen to it live on Sundays 10pm EST - 12AM EST .... this is the world's best automotive broadcast bar none!!

New Monthly Feature: Car Tips, brought to you by Americas Car Show, hosted by Tom Torbjornsen and heard on Sirius 108 and XM 139
Read the full articles here http://eliteautorepairshops.wordpress.com

Sports Car Market Magazine Family and Internet Resources http://www.sportscarmarket.com/family

________________________________________________________________________________________________________________________________
CarProperty.com sent this informational newsletter to doc@freebsd.org based on your CarProperty.com optional user preferences. Click here to update your profile http://letters.carproperty.com/p_m.php?mi=218&nl=4&ei=ZG9jQGZyZWVic2Qub3Jn&eid=MjQ1Nzc5.  Send this to a friend http://letters.carproperty.com/p_f.php?mi=218&nl=4&ei=ZG9jQGZyZWVic2Qub3Jn&eid=MjQ1Nzc5

If you no longer wish to receive our non-system messages, you can remove yourself from our mailing list by clicking here 
http://letters.carproperty.com/box.php?funcml=unsub2&nl=4&mi=218&email=doc%40freebsd.org   or mail your request to Car Property Group. 1620 Central Ave, Suite 202, Cheyenne, WY  82001(please allow 3 - 4 weeks using this unsubscribe method).  Toll Free: 1-888-628-3683.

If you received a forwarded copy of the Car Property News, you can subscribe by registering on www.CarProperty.com. Car Property News is sent from time to time but not on a set schedule.

To help make sure you get our emails, please put our domain address of @carproperty.com in your email programs address book or safe senders list that monitors your inbox. You may have to forward this information to a systems administrator who runs your email systems so they can put us on your safe list. Please give them our domain address of @carproperty.com. If you need help putting our domain address in your email programs address book or safe senders list, please click on this link: How to Add an Address to Your Address Book or Safe Senders List

CarProperty.com is a registered Trademark as are the phrases Car Property and Car Properties, by the Car Property Group.  This notice is compliant with the US Governments regulations regarding emails.


















To Unsubscribe, please click here :
http://letters.carproperty.com/box.php?funcml=unsub2&nl=4&mi=218&email=doc%40freebsd.org
From pgj at FreeBSD.org  Sun Nov 22 00:08:25 2009
From: pgj at FreeBSD.org (Gabor PALI)
Date: Sun Nov 22 00:08:31 2009
Subject: [RFC] Article on freebsd-update-server
In-Reply-To: <4B05BA06.3010303@FreeBSD.org>
References: <4B05BA06.3010303@FreeBSD.org>
Message-ID: <685a6ef80911211608p794f2fby35e294b4223a09c1@mail.gmail.com>

Hello there,

2009/11/19 Manolis Kiagias <manolis@freebsd.org>:
> The source is here:
>
> http://people.freebsd.org/~manolis/patches/freebsd-update-server/article.sgml.txt
>
> And the build:
>
> http://people.freebsd.org/~manolis/patches/freebsd-update-server/index.html
>
> Please send us any comments and suggestions  on content, format or whatever!

I have created a modified version of your version on freefall, and I put there:

http://people.freebsd.org/~pgj/patches/2009/11/22/article.html

You can find the modified sources as well as a diff against the
original one (my comments are added inline as comments) here:

http://people.freebsd.org/~pgj/patches/2009/11/22/article.sgml.txt
http://people.freebsd.org/~pgj/patches/2009/11/22/article.diff

I hope it helps.

Cheers,
:g
From glen.j.barber at gmail.com  Sun Nov 22 19:19:13 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Sun Nov 22 19:19:27 2009
Subject: [draft][comments] File-Backed Jails Article
Message-ID: <4ad871310911221119i6f3f426bv23b5695c8cfd0e70@mail.gmail.com>

Hello,

I have recently started using file-backed md(4) devices for my jails,
primarily to gain greater control over space usage on a per-jail
basis.  I believe this information may be useful to others, so I have
written an article outlining the necessary steps.  Comments and
criticisms alike are welcome, as I plan to submit a patch for
inclusion into the official Documentation.

Normally, I would include a patch, but my mailer always breaks them.
The patch is located at:

     http://freebsd.dev-urandom.com/ports/patch/doc.article.file-backed-jails.txt



-- 
Glen Barber
From glen.j.barber at gmail.com  Sun Nov 22 22:42:54 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Sun Nov 22 22:43:01 2009
Subject: [draft][comments] File-Backed Jails Article
In-Reply-To: <4ad871310911221119i6f3f426bv23b5695c8cfd0e70@mail.gmail.com>
References: <4ad871310911221119i6f3f426bv23b5695c8cfd0e70@mail.gmail.com>
Message-ID: <4ad871310911221442h5bf42c2cy79301a87db820abd@mail.gmail.com>

Hello,

In response to an off-list reply, I have modified the patch for
inclusion to the Handbook's Jails chapter.

     http://freebsd.dev-urandom.com/ports/patch/handbook.jail.file-backed-jails.txt

Opinions are welcome.

-- 
Glen Barber
From newsletter at email.pctools.com  Mon Nov 23 05:04:15 2009
From: newsletter at email.pctools.com (PC Tools)
Date: Mon Nov 23 05:04:22 2009
Subject: PC Tools November Newsletter
Message-ID: <4B0A17CE.00000452@omp.email.pctools.com>

PC Tools Newsletter
----------------
To ensure you always get our emails, please add the domain @email.pctools.com to your Safe Sender list.

View online please click the link below:

http://email.pctools.com/servlet/cc6?iJltkQBADQSVKhJxMjLLIkKQhjnV2VDVwgtpgLyHnL30eV%0D%0Aollik%3A%2F%2FLuHptQiJlhhtkQJhu%2FkLjNtLl%2FOLIkplL%2F0LkihgkLzghju%3FpcuktGmeytkeuuesXmonXOaidX2833XQTAmGdoczgfseebtd9osg

-------------------------------------------------------------------------------
Spyware Doctor? with AntiVirus 2010 wins PCMag.com Editors' Choice Award 

In this edition we'll be covering: 

? PCMag.com Editors' Choice Award 

? AntiMalware testing and how we compare

? Recent Malware threats to look out for 

Each year we strive to develop more effective software to meet our 
customers? changing needs. One way we measure our effectiveness is by 
listening to independent industry experts when they review our latest 
release. Neil J. Rubenking from PCMag.com recently completed his 
review of Spyware Doctor with AntiVirus 2010 and we?re thrilled to 
announce it won the PCMag.com Editors? Choice Award. 

PCMag.com Editors' Choice Award
"The latest Spyware Doctor proved effective in every area of malware 
removal and blocking. It?s a great product.? - pcmag.com October 15, 2009. 

This accolade confirms that the 2010 release of Spyware Doctor with 
AntiVirus delivers what customers need, highly effective detection, 
elimination and blocking of Malware. 

Read the full review

http://email.pctools.com/servlet/cc6?iJltkQBADQSVKhJxMjLLIkKQhjnV2VR
 

AntiMalware testing and how we compared "Spyware Doctor also set a 
new record in the malware blocking test, scoring 9.7 of 10 possible points."
- pcmag.com October 15, 2009 .

Testing product effectiveness involves two stages; the detection and 
elimination of current Malware infections and the blocking of new 
Malware threats. The effectiveness of the product is tracked via a 
points system and Spyware Doctor with AntiVirus performed 
outstandingly scoring 9.7 out of 10 points. 

Read more about the testing approach

http://email.pctools.com/servlet/cc6?iJltkQBADQSVKhJxMjLLIkKQhjnV2VS
 

See how Spyware Doctor with AntiVirus 2010 compared against other 
products 
http://email.pctools.com/servlet/cc6?iJltkQBADQSVKhJxMjLLIkKQhjnV2VT
 
Recent Malware threats to look out for Malware Spam Blasts.

Cybercriminals are currently sending out mass email blasts 
impersonating popular companies to install password stealing malware 
on to users PCs. The emails look like they?re coming from a legitimate 
source, as demonstrated in the recent ?Facebook Password Reset Scam? 
discussed on the ThreatFire? blog. The purpose of this scam is to 
deliver malware packages designed to infiltrate users PC with 
malicious programs including; Koobface, Bredolab, and Zbot. 

Learn more about this Malware threat on the ThreatFire? Blog

http://email.pctools.com/servlet/cc6?iJltkQBADQSVKhJxMjLLIkKQhjnV2VU
 

? Net-Worm.Koobface is a network-aware worm that attempts to replicate 
across the existing network(s) and also can be used to hijack certain 
aspects of users' web browser functionality (such as homepage, search 
page, and security settings).
? Trojan-Spy.Zbot.YETH is a rootkit trojan which steals online banking 
information and downloads other malware as well. 

Top Threats Below are some of the latest threats identified by PC Tools 
Malware Research Center 
http://email.pctools.com/servlet/cc6?iJltkQBADQSVKhJxMjLLIkKQhjnV2VSR
.

WORLD CYBERGAMES 2009
PC Tools is one of the official partners for the World Cyber Games 
2009. Heats have recently been held around the world and national 
finalists are now headed to the grand finals in Beijing on the 11th 
November 2009. 

-------------------------------------------------------------------------------
PCMag.com Editors? Choice Award Logo is a trademark of Ziff Davis 
Publishing Holdings Inc. Used under license. Reprinted from 
http://www.pcmag.com, October 15, 2009, with permission. Copyright 2009 Ziff Davis 
Publishing Holdings Inc. All rights reserved. 

Login to MyAccount

http://email.pctools.com/servlet/cc6?iJltkQBADQSVKhJxMjLLIkKQhjnV2VSSVGf6beVKhJxMjLLIkKQhjnVKpkJhmglVVIHggLjV
 

To contact us please email reply-subscriptions@email.pctools.com
mailto:reply-subscriptions@email.pctools.com?subject=RE: Mid-Life Renewal Offer 

Unsubscribe

http://email.pctools.com/servlet/cc6?iJltkQBADQSVKhJxMjLLIkKQhjnV2VSTVGf6beVKhJxMjLLIkKQhjnVKpkJhmglVVIHggLjV


PC Tools Limited
Brookvale Plaza, Unit 3 East Park Shannon Co Clare Ireland.. 
Copyright ? 2009 PC Tools. All rights reserved. 


From mail at ozzmosis.com  Mon Nov 23 07:55:17 2009
From: mail at ozzmosis.com (andrew clarke)
Date: Mon Nov 23 07:55:24 2009
Subject: dummynet man page
Message-ID: <20091123072834.GA68166@ozzmosis.com>

The dummynet man page should probably mention you can use "kldload
dummynet" instead of recompiling the kernel.
From bugmaster at FreeBSD.org  Mon Nov 23 11:06:07 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov 23 11:06:38 2009
Subject: Current unassigned doc problem reports
Message-ID: <200911231106.nANB66L1069430@freefall.freebsd.org>

(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .)

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/140754  doc        [handbook] Bad example in handbook 18.5.2
o docs/140725  doc        wrong directory in ipnat(8) man page
o docs/140703  doc        add xorg-minimal as alternative for X11 Distribution i
o docs/140649  doc        [handbook] bad WITHOUT_MODULES example in handbook
o docs/140569  doc        [UPDATE] Updated info about Tcl in Developers' Handboo
o docs/140568  doc        [UPDATE] Outdated Perl info in Developers' Handbook
o docs/140495  doc        [patch] /etc/rc.conf.d is not documented in rc.conf(5)
o docs/140494  doc        [patch] Man page fix for getc(3)
o docs/140474  doc        signal(3) missing reference to NSIG
o docs/140458  doc        [patch] Grammar fix for to{upper,lower}(3)
o docs/140457  doc        [patch] Grammar fix for isspace(3)
o docs/140444  doc        [patch] New Traditional Chinese translation of custom-
o docs/140435  doc        man ls, section STANDARD: the -A is exception from POS
o docs/140375  doc        [UPDATE] Updated zh_TW.Big5/articles/nanobsd
o docs/140369  doc        [patch] src/contrib/pf/man/pf.4
o docs/140082  doc        handbook/jails: russian translation is missing
o docs/140075  doc        release notes: missing word "NOT", which changes all t
o docs/139682  doc        [PATCH] dialog(1) man page does not mention radiolist 
o docs/139603  doc        [patch] Clarify subpixel smoothing for fonts in Handbo
p docs/139370  doc        [PATCH] de(4) manual page typo
o docs/139336  doc        ZFS documentation suggestion
o docs/139165  doc        gssapi.3 man page out of sync with between crypto and 
o docs/139153  doc        the hier(7) man page needs to be updated
o docs/139018  doc        translation of submitting.sgml from docproj/submitting
o docs/138887  doc        manpage ports(7) incorrect
o docs/138845  doc        Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138663  doc        system(3) man page confuses users about "return value 
o docs/138485  doc        bpf(4) and ip(4) man pages missing important corner ca
o docs/138206  doc        [patch] ntp(1): not enabled function, and false manual
o docs/137762  doc        [handbook] proposed: mention "make delete-old" in sec 
o docs/137171  doc        [patch] replacement of k8temp(4) by amdtemp(4) isn't r
o docs/136918  doc        [patch] grammar fixes to locking.9
o docs/136712  doc        [handbook] [patch] draft new section on gmirror per pa
o docs/136666  doc        [handbook] Configure serial port for remote kernel deb
o docs/136100  doc        change FreeBSD Ports distfiles survey's url to portsco
o docs/136035  doc        ftpchroot(5) omits an important option
p docs/136029  doc        MALLOC_PRODUCTION knob should be mentioned somewhere, 
o docs/135999  doc        Netgear GS105v3 should be added to list of switches th
o docs/135676  doc        FAQ About The FreeBSD Mailing Lists doesn't mention ma
o docs/135516  doc        pax(1) manual not mentioning chflags unawareness
o docs/135475  doc        [patch] jot(1) manpage and behaviour differ
o docs/135165  doc        [patch] make(1) fixes: punctuation, typos, tweaks
o docs/134376  doc        pthread(3): pthread manpages don't mention that PTHREA
o docs/134226  doc        /usr/share/examples/ftpd/ftpd.conf does not exist.
o docs/134222  doc        installation failure of japanese docs
o docs/134123  doc        The RUNQUEUE(9) man page is out of date
o docs/134074  doc        [patch] locking.9 man page slight enhancements
o docs/133567  doc        [patch] doc/Makefile switch to csup
o docs/133245  doc        french handbook 27.3.5 amd.map amd.conf
o docs/133228  doc        handbook 23.3.5 screenmap section is confusing
o docs/133186  doc        [patch] powerd(8) man page errors
o docs/133118  doc        [patch] Error in getopt (1) manual EXAMPLES section
o docs/132959  doc        [patch] description mismatches on xterm/termcap, fortu
o docs/132884  doc        [request] No manpage for SYSINIT and SYSUNINIT
o docs/132839  doc        [patch] Fix example script in ldap-auth article
o docs/132718  doc        [handbook] Information about adding a new mirror is ou
o docs/132311  doc        [patch] man5/nsmb.conf.5
o docs/132260  doc        dhcpd(8) pid not stored in documented location
o docs/132190  doc        EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/132113  doc        [handbook] Update handbook jails creation
o docs/131918  doc        [patch] Fixes for the BPF(4) man page
o docs/131684  doc        [patch] articles/linux-comparison: replace Addenda by 
o docs/131590  doc        [patch] whitespace-only change of developers-handbook/
o docs/130895  doc        [patch] No man page installed for padlock(4) on amd64 
o docs/130364  doc        Man page for top needs explanation of CPU states
o docs/130238  doc        nfs.lockd man page doesn't mention NFSLOCKD option or 
o docs/129671  doc        New TCP chapter for Developer's Handbook (from rwatson
o docs/129095  doc        ipfw(8): Can not check that packet originating/destine
o docs/128524  doc        No geom documentation for loading gjournal(8)
s docs/128356  doc        [request] add Firefox plugin for FreeBSD manual pages
o docs/127908  doc        [patch] readdir(3) error documentation
s docs/127844  doc        Example code skeleton_capture_n.c in meteor(4) manpage
o docs/126590  doc        [patch] Write routine called forever in Sample Echo Ps
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
f docs/122052  doc        minor update on handbook section 20.7.1
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o bin/121424   doc        [patch] [ipfw] Rectify ambiguous English in manual
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
a docs/119536  doc        a few typos in French handbook (basics)
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118214  doc        close(2) error returns incomplete
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/117747  doc        'break' system call needs a man page
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/116116  doc        mktemp (3) re/move note
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111147  doc        hostapd.conf is not documented
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110061  doc        [patch] tuning(7) missing reference to vfs.read_max
o docs/109981  doc        No manual entry for post-grohtml
o docs/109977  doc        No manual entry for ksu
o docs/109973  doc        No manual entry for c++filt
o docs/109972  doc        No manual entry for zless/bzless
f docs/109226  doc        [request] No manual entry for sntp
o docs/109201  doc        [request]: manual for callbootd
a docs/108980  doc        list of missing man pages
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
o docs/107924  docs       [usb67] usbd(8) does not call detach
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/105608  doc        fdc(4) debugging description staled
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/91174   doc        [REQUEST] Handbook: Addition of Oracle 9i installation
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84271   doc        [patch] compress(1) doesn't warn about nasty link hand
o docs/83820   doc        getino(3) manpage not installed
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
o docs/63570   doc        [patch] Language cleanup for the Handbook's DNS sectio
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
o docs/53596   doc        Updates to mt(1) manual page
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/50211   doc        [patch] doc.docbook.mk: fix textfile creation
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/43823   doc        [patch] update to environ(7) manpage
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/38556   doc        EPS file of beastie, as addition to existing examples
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
a docs/30008   doc        [patch] French softupdates document should be translat
o docs/27605   doc        [patch] Cross-document references (<olink>)
o docs/26286   doc        *printf(3) etc should gain format string warnings
o docs/24786   doc        missing FILES descriptions in sa(4)
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc

175 problems total.

From rupesh.agrawal at verveos2i.com  Mon Nov 23 11:24:06 2009
From: rupesh.agrawal at verveos2i.com (Rupesh Agrawal )
Date: Mon Nov 23 11:25:29 2009
Subject: Christmas Administrators - Recruitment Support Services
Message-ID: <20091123105442.4D3DA398043@mdreg2.mailserve.net>







?
Most of our recruitment clients recognise Christmas time as being the ideal opportunity to undertake an annual clean up of their databases to have their back offices ship shape for the New Year.
?
?45.00 per day
?
This is the cost of a FULL-TIME administrator
This is the cost of a FULL-TIME administrator working 8 hrs per day
This is the cost of a FULL-TIME administrator working 8 hrs per day with only you as a client
?
?
Verveoffshore Recruitment Process Outsourcing
?
We offer flexible solutions to fit around your business
?
?
?
Kind Regards,
?
Rupesh Agrawal | Manager - Client Services
?
VerveOS2i?? |? India? |? Phone:+91 20-41056789?Ext. 6712 |? E-mail: rupesh.agrawal@verveos2i.com |? Website: www.verveos2i.com
?
CONFIDENTIALITY & DISCLAIMER: This E-mail from VerveOS2i ?is confidential. It may also be legally privileged. If you are not the intended receiver, you may not copy, reproduce, forward, disclose, disseminate or use any part of it. If you have received this message by slip, delete it and all copies from your system and notify the sender immediately by return E-mail. We do not guarantee the security of Internet communications and are not liable for any errors or omissions. 
?
We are a responsible email marketing team and comply with necessary regulations. Most often we buy email lists from opt-in repositories and carry our necessary checks. If this email has come to you by error or if you need us to remove your ID from our emailing list, please reply to this email with "REMOVE" on the subject line.



From manolis at FreeBSD.org  Mon Nov 23 18:35:39 2009
From: manolis at FreeBSD.org (Manolis Kiagias)
Date: Mon Nov 23 18:35:45 2009
Subject: [RFC] Article on freebsd-update-server
In-Reply-To: <685a6ef80911211608p794f2fby35e294b4223a09c1@mail.gmail.com>
References: <4B05BA06.3010303@FreeBSD.org>
	<685a6ef80911211608p794f2fby35e294b4223a09c1@mail.gmail.com>
Message-ID: <4B0AD5F6.5080407@FreeBSD.org>

Gabor PALI wrote:
> Hello there,
>
> 2009/11/19 Manolis Kiagias <manolis@freebsd.org>:
>   
>> The source is here:
>>
>> http://people.freebsd.org/~manolis/patches/freebsd-update-server/article.sgml.txt
>>
>> And the build:
>>
>> http://people.freebsd.org/~manolis/patches/freebsd-update-server/index.html
>>
>> Please send us any comments and suggestions  on content, format or whatever!
>>     
>
> I have created a modified version of your version on freefall, and I put there:
>
> http://people.freebsd.org/~pgj/patches/2009/11/22/article.html
>
> You can find the modified sources as well as a diff against the
> original one (my comments are added inline as comments) here:
>
> http://people.freebsd.org/~pgj/patches/2009/11/22/article.sgml.txt
> http://people.freebsd.org/~pgj/patches/2009/11/22/article.diff
>
> I hope it helps.
>
> Cheers,
> :g
>
>   
Thanks Gabor,

I will integrate this patch, probably later on tonight.
Anyone who would like to comment on this version, please do.
By request of Jason (and other people) the final title will be "Build
Your Own FreeBSD Update Server".

Any ideas on how to provide the link to experts-exchange? Is the
"Acknowledgments" idea acceptable?
We could also add @cperciva here, I think Jason mentioned he got some
info from him.

From jhelfman at e-e.com  Mon Nov 23 21:29:39 2009
From: jhelfman at e-e.com (Jason)
Date: Mon Nov 23 21:29:47 2009
Subject: lsi controller, mfi(4)
Message-ID: <20091123212833.GJ15411@eggman.experts-exchange.com>

Hi,

In doing extensive testing with the LSI MegaRaid SAS 9260 Controller, we
have found that it "passes" a hardware test on 7.2-RELEASE.

Is there anything needed to add this to the mfi man page, or does anything
need to be put past the manufacturer?

http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/mfi.4

Thanks,
Jason
From glen.j.barber at gmail.com  Tue Nov 24 01:00:12 2009
From: glen.j.barber at gmail.com (Glen Barber)
Date: Tue Nov 24 01:00:18 2009
Subject: docs/140814: [handbook][patch] Chapter 15 - Jails: add section on
	creating file-backed jails
Message-ID: <200911240051.nAO0png6032970@www.freebsd.org>


>Number:         140814
>Category:       docs
>Synopsis:       [handbook][patch] Chapter 15 - Jails: add section on creating file-backed jails
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 24 01:00:12 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Glen Barber
>Release:        8.0-PRERELEASE
>Organization:
>Environment:
FreeBSD orion 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #3 r199595: Fri Nov 20 23:08:22 EST 2009     root@orion:/usr/obj/usr/src/sys/ORION  amd64
>Description:
The jail(8) utility alone does not contain a mechanism to control disk space on a per-jail basis, thus all jails on one system view all free space on the mountpoint as free space.

Solutions for this exist; for example, creating separate filesystem slices per-jail.  The problem with this solution is the need for planning ahead in avoidance of reallocation disk space.

vnode-backed md(4) devices can remedy this solution, allowing administrators to create chunks of a filesystem on-the-fly, while maintaining space quotas within their jails.

The attached patch explains how to create space limitations for jails using vnode-backed md(4) devices.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- doc/en_US.ISO8859-1/books/handbook/jails/chapter.sgml.orig	2009-11-10 18:17:21.000000000 -0500
+++ doc/en_US.ISO8859-1/books/handbook/jails/chapter.sgml	2009-11-23 19:35:10.000000000 -0500
@@ -964,4 +964,117 @@
       </sect3>
     </sect2>
   </sect1>
+
+  <sect1 id="jail-file-backed">
+    <title>File-Backed Jails</title>
+
+      <sect2 id="jail-creating-file-backed">
+      <sect2info>
+	<authorgroup>
+	  <author>
+	    <firstname>Glen</firstname>
+	    <surname>Barber</surname>
+	    <contrib>Contributed by </contrib>
+	    <!-- 23 November 2009 -->
+	  </author>
+	</authorgroup>
+      </sect2info>
+      
+      <title>Creating a File-Backed Jail</title>
+      
+      <para>
+        The &man.jail.8; environment alone provides no mechanism to restrict disk
+        space used by the &man.jail.8;.  Though there are many way to achieve this,
+        for example, using separate disk slices for each &man.jail.8;, this section
+        will show you how to create file-backed jails using &man.md.4; devices.</para>
+
+      <sect3 id="jail-creating-memory-file">
+       <title>Creating the Memory File</title>
+
+        <para>In this section, there will be one &man.jail.8; created in the <filename
+          class="directory">/usr/jails/www</filename> directory, using <filename
+          class="directory">/usr/jails/images</filename> as the directory 
+          containing the image file.</para>
+   
+        <procedure>
+          <step>
+            <para>Create the directories and image file for the jail:</para>
+              <screen>&prompt.root; <userinput>mkdir /usr/jails</userinput>
+&prompt.root; <userinput>cd /usr/jails</userinput>
+&prompt.root; <userinput>mkdir images www</userinput></screen></step>
+   
+          <step>
+            <para>Create the vnode-backed &man.md.4; device using &man.mdmfs.8;,
+              backed by <filename>www.img</filename>.  In the below example, the
+              image file is 10 gigabytes in size:</para>
+   
+            <screen>&prompt.root; <userinput>touch images/www.img</userinput>
+&prompt.root; <userinput>mdmfs -F images/www.img -s 10g md101 /usr/jails/www</userinput></screen>
+            <note>
+	      <para>Please note, although the <filename>www.img</filename> file
+	        was created as a 10 Gigabyte file, only 8 Gigabytes will be shown
+		as available.  On default UFS filesystems, the system reserves 8 
+		percent of the filesystem.  For more information, please read 
+		&man.tunefs.8;.
+              </para>
+            </note>
+          </step>
+   
+          <step>
+            <para>&man.df.1; output should present output similar to the following:</para>
+   
+            <screen>Filesystem         1K-blocks      Used     Avail Capacity  Mounted on
+/dev/mirror/gm0s1a   4058062    478866   3254552    13%    /
+devfs                      1         1         0   100%    /dev
+/dev/mirror/gm0s1e    507630       398    466622     0%    /tmp
+/dev/mirror/gm0s1f 461439472 115610770 308913546    27%    /usr
+/dev/mirror/gm0s1d   3008142    137834   2629658     5%    /var
+/dev/md101           9159102         4   8426370     0%    /usr/jails/www</screen>
+          </step>
+        </procedure>
+      </sect3>
+
+       <sect3 id="jail-file-backed-fstab">
+        <title>Edit <filename>/etc/fstab</filename></title>
+    
+         <procedure>
+           <step>
+             <para>The memory devices will not be automatically recreated after rebooting
+               the system.  To achieve this, edit <filename>/etc/fstab</filename>.  An
+               example &man.fstab.5; configuration:</para>
+    
+             <screen># Device                Mountpoint      FStype  Options         Dump    Pass#
+/dev/mirror/gm0s1b      none            swap    sw              0       0
+/dev/mirror/gm0s1a      /               ufs     rw              1       1
+/dev/mirror/gm0s1e      /tmp            ufs     rw              2       2
+/dev/mirror/gm0s1f      /usr            ufs     rw              2       2
+/dev/mirror/gm0s1d      /var            ufs     rw              2       2
+/dev/acd0               /cdrom          cd9660  ro,noauto       0       0
+# www jail
+md101      /usr/jails/www mfs rw,-P,-F/usr/jails/images/www.img 0       0</screen>
+           </step>
+    
+           <step>
+             <para>To verify the system will &man.mount.8; the device successfully 
+	       after a system reboot, verify there are no &man.fstab.5; 
+	       errors:</para>
+    
+             <screen><userinput>&prompt.root; mount -a </userinput></screen>
+    
+           </step>
+         </procedure>
+    
+           <para>Following the steps outlined in the beginning of this chapter,
+	     create the &man.jail.8; using <filename 
+	     class="directory">/usr/jails/www</filename> as the destination
+             directory.</para>
+    
+           <para>Should you find the need to move this jail to another machine, 
+	     stop the &man.jail.8;, &man.umount.8; <filename 
+	     class="directory">/usr/jails/www</filename>, and copy the 
+	     <filename>www.img</filename> file to the remote machine.</para>
+    
+      </sect3>
+    </sect2> 
+  </sect1>
 </chapter>


>Release-Note:
>Audit-Trail:
>Unformatted:
From brueffer at FreeBSD.org  Tue Nov 24 08:29:05 2009
From: brueffer at FreeBSD.org (Christian Brueffer)
Date: Tue Nov 24 08:29:12 2009
Subject: lsi controller, mfi(4)
In-Reply-To: <20091123212833.GJ15411@eggman.experts-exchange.com>
References: <20091123212833.GJ15411@eggman.experts-exchange.com>
Message-ID: <20091124081613.GA1476@serenity>

On Mon, Nov 23, 2009 at 01:28:34PM -0800, Jason wrote:
> Hi,
> 
> In doing extensive testing with the LSI MegaRaid SAS 9260 Controller, we
> have found that it "passes" a hardware test on 7.2-RELEASE.
> 
> Is there anything needed to add this to the mfi man page, or does anything
> need to be put past the manufacturer?
> 
> http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/mfi.4
> 

I just added it to the manpage, thanks for the report!

Usually it's best to submit a PR, so reports like this aren't forgotten
or lost.

- Christian

-- 
Christian Brueffer	chris@unixpages.org	brueffer@FreeBSD.org
GPG Key:	 http://people.freebsd.org/~brueffer/brueffer.key.asc
GPG Fingerprint: A5C8 2099 19FF AACA F41B  B29B 6C76 178C A0ED 982D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20091124/6855b054/attachment.pgp
From jhelfman at e-e.com  Tue Nov 24 15:25:18 2009
From: jhelfman at e-e.com (Jason)
Date: Tue Nov 24 15:25:24 2009
Subject: lsi controller, mfi(4)
In-Reply-To: <20091124081613.GA1476@serenity>
References: <20091123212833.GJ15411@eggman.experts-exchange.com>
	<20091124081613.GA1476@serenity>
Message-ID: <20091124152516.GA2864@jason-helfmans-macbook-pro.local>

On Tue, Nov 24, 2009 at 09:16:14AM +0100, Christian Brueffer thus spake:
>On Mon, Nov 23, 2009 at 01:28:34PM -0800, Jason wrote:
>> Hi,
>>
>> In doing extensive testing with the LSI MegaRaid SAS 9260 Controller, we
>> have found that it "passes" a hardware test on 7.2-RELEASE.
>>
>> Is there anything needed to add this to the mfi man page, or does anything
>> need to be put past the manufacturer?
>>
>> http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/mfi.4
>>
>
>I just added it to the manpage, thanks for the report!
>
>Usually it's best to submit a PR, so reports like this aren't forgotten
>or lost.

That was my intention, along with a documentation patch, but I didn't know
if the manufacturer needed to involved somehow in a driver related
documentation change for "supported hardwore."

Thank you.

>
>- Christian
>
>--
>Christian Brueffer	chris@unixpages.org	brueffer@FreeBSD.org
>GPG Key:	 http://people.freebsd.org/~brueffer/brueffer.key.asc
>GPG Fingerprint: A5C8 2099 19FF AACA F41B  B29B 6C76 178C A0ED 982D


From lpos1972 at gmail.com  Tue Nov 24 15:56:56 2009
From: lpos1972 at gmail.com (Luiz Paulo de Oliveira Santos)
Date: Tue Nov 24 15:57:02 2009
Subject: Site translation to portuguese
Message-ID: <4B0C0DD3.7080605@gmail.com>

Hi!
My name is Luiz Paulo, I am Brasilian.
I am a FreeBSD user and I can to translate the site to portuguese.
We have a lot of users in Brasil, but we can not to find any information 
about FreeBSD in portuguese.
Is there some interesting?
thanks.

Lluiz
From eksffa at freebsdbrasil.com.br  Tue Nov 24 16:31:54 2009
From: eksffa at freebsdbrasil.com.br (Patrick Tracanelli)
Date: Tue Nov 24 16:32:02 2009
Subject: Site translation to portuguese
In-Reply-To: <4B0C0DD3.7080605@gmail.com>
References: <4B0C0DD3.7080605@gmail.com>
Message-ID: <4B0C0428.6030605@freebsdbrasil.com.br>

Luiz Paulo de Oliveira Santos escreveu:
> Hi!
> My name is Luiz Paulo, I am Brasilian.
> I am a FreeBSD user and I can to translate the site to portuguese.
> We have a lot of users in Brasil, but we can not to find any information
> about FreeBSD in portuguese.
> Is there some interesting?
> thanks.

Hello Luiz,

There is a community effort which was recently revamped. You can contact
the people envolved here:

http://doc.fug.com.br/
https://www.fug.com.br/mailman/listinfo/doc/


-- 
Patrick Tracanelli

FreeBSD Brasil LTDA.
Tel.: (31) 3516-0800
316601@sip.freebsdbrasil.com.br
http://www.freebsdbrasil.com.br
"Long live Hanin Elias, Kim Deal!"

From linimon at FreeBSD.org  Tue Nov 24 22:22:19 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Tue Nov 24 22:22:31 2009
Subject: docs/140847: [request] add documentation on ECMP and new route
	args (nostick, sticky, )weight
Message-ID: <200911242222.nAOMMJCI083936@freefall.freebsd.org>

Old Synopsis: Documentation on ECMP and new route args (nostick,sticky,)weight
New Synopsis: [request] add documentation on ECMP and new route args (nostick,sticky,)weight

State-Changed-From-To: open->suspended
State-Changed-By: linimon
State-Changed-When: Tue Nov 24 22:21:22 UTC 2009
State-Changed-Why: 
Mark suspended awaiting a patch.


Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Nov 24 22:21:22 UTC 2009
Responsible-Changed-Why: 
Reclassify this request.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140847