From owner-freebsd-doc@FreeBSD.ORG Sun Dec 3 08:43:36 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EE53C16A40F for ; Sun, 3 Dec 2006 08:43:36 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from lab.alexdupre.com (lab.alexdupre.com [81.174.31.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 807E143C9D for ; Sun, 3 Dec 2006 08:43:10 +0000 (GMT) (envelope-from ale@FreeBSD.org) Received: (qmail 93605 invoked from network); 3 Dec 2006 08:43:32 -0000 Received: from unknown (HELO ?192.168.178.2?) (192.168.178.2) by lab.alexdupre.com with SMTP; 3 Dec 2006 08:43:32 -0000 Message-ID: <45728E33.9000907@FreeBSD.org> Date: Sun, 03 Dec 2006 09:43:31 +0100 From: Alex Dupre User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: "Bruce A. Mah" References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> <45634E53.1020609@freebsd.org> <20061122162848.GC2043@haakonia.hitnet.RWTH-Aachen.DE> <456641B2.2020502@freebsd.org> <457211BE.8010402@freebsd.org> In-Reply-To: <457211BE.8010402@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org Subject: Re: RFC: Release notes rearrangement X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 08:43:37 -0000 Bruce A. Mah wrote: > Any thoughts? There is no particular deadline for this work but I'd > like to do this before I forget about it. :-) I like it. -- Alex Dupre From owner-freebsd-doc@FreeBSD.ORG Sun Dec 3 08:49:16 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 038B716A403; Sun, 3 Dec 2006 08:49:16 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: from av9-2-sn3.vrr.skanova.net (av9-2-sn3.vrr.skanova.net [81.228.9.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CC7F43CA2; Sun, 3 Dec 2006 08:48:50 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502) id B9A4338131; Sun, 3 Dec 2006 09:49:14 +0100 (CET) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 9ADDD38124; Sun, 3 Dec 2006 09:49:14 +0100 (CET) Received: from dude.automatvapen.se (81-234-214-163-no68.tbcn.telia.com [81.234.214.163]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 7CCED37E57; Sun, 3 Dec 2006 09:49:14 +0100 (CET) From: Joel Dahl To: Alex Dupre In-Reply-To: <45728E33.9000907@FreeBSD.org> References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> <45634E53.1020609@freebsd.org> <20061122162848.GC2043@haakonia.hitnet.RWTH-Aachen.DE> <456641B2.2020502@freebsd.org> <457211BE.8010402@freebsd.org> <45728E33.9000907@FreeBSD.org> Content-Type: text/plain Date: Sun, 03 Dec 2006 09:49:14 +0100 Message-Id: <1165135754.675.0.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "Bruce A. Mah" , freebsd-doc@freebsd.org Subject: Re: RFC: Release notes rearrangement X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 08:49:16 -0000 On Sun, 2006-12-03 at 09:43 +0100, Alex Dupre wrote: > Bruce A. Mah wrote: > > Any thoughts? There is no particular deadline for this work but I'd > > like to do this before I forget about it. :-) > > I like it. +1 -- Joel From owner-freebsd-doc@FreeBSD.ORG Sun Dec 3 09:14:42 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD6E216A407; Sun, 3 Dec 2006 09:14:42 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8E0043CA2; Sun, 3 Dec 2006 09:14:16 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 09D3878C9E; Sun, 3 Dec 2006 09:14:14 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 3189511437; Sun, 3 Dec 2006 10:14:39 +0100 (CET) Date: Sun, 3 Dec 2006 10:14:39 +0100 From: "Simon L. Nielsen" To: "Bruce A. Mah" Message-ID: <20061203091438.GA1000@zaphod.nitro.dk> References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> <45634E53.1020609@freebsd.org> <20061122162848.GC2043@haakonia.hitnet.RWTH-Aachen.DE> <456641B2.2020502@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <456641B2.2020502@freebsd.org> User-Agent: Mutt/1.5.11 Cc: freebsd-doc@freebsd.org, Christian Brueffer Subject: Re: RFC: Release notes rearrangement X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 09:14:42 -0000 On 2006.11.23 16:49:54 -0800, Bruce A. Mah wrote: > If memory serves me right, Christian Brueffer wrote: > > > Ok, I assume you have a prototype in the works. When that's out, we can > > still decide whether or not this is an issue. Let's see how it looks :-) > > Well I didn't at the time but I threw something together (this took > about 30 minutes). Sources, based on HEAD from today: > > http://people.freebsd.org/~bmah/relnotes2.tar.gz > > (Untar this into src/release/doc/en_US.ISO8859-1/ on a HEAD machine, so > that it's a sibling of the existing relnotes directory.) > > PDF rendering: > > http://people.freebsd.org/~bmah/relnotes2.pdf > > I might want to entity-ize the names of architectures and sort them into > some consistent order, but this is roughly what I'd expect it to look like. Go for it :-). -- Simon L. Nielsen From owner-freebsd-doc@FreeBSD.ORG Sun Dec 3 11:38:26 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1CE8B16A412; Sun, 3 Dec 2006 11:38:26 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9B1043CA3; Sun, 3 Dec 2006 11:37:59 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB3BcPL4063896; Sun, 3 Dec 2006 11:38:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB3BcPgP063892; Sun, 3 Dec 2006 11:38:25 GMT (envelope-from linimon) Date: Sun, 3 Dec 2006 11:38:25 GMT From: Mark Linimon Message-Id: <200612031138.kB3BcPgP063892@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: Subject: Re: docs/106234: confstr(3) man page incorrectly documents return value X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 11:38:26 -0000 Synopsis: confstr(3) man page incorrectly documents return value Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Sun Dec 3 11:38:03 UTC 2006 Responsible-Changed-Why: docs PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=106234 From owner-freebsd-doc@FreeBSD.ORG Sun Dec 3 19:47:35 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0082616A865; Sun, 3 Dec 2006 19:47:35 +0000 (UTC) (envelope-from blackend@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F22843CA7; Sun, 3 Dec 2006 19:47:05 +0000 (GMT) (envelope-from blackend@FreeBSD.org) Received: from freefall.freebsd.org (blackend@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB3JlXj7033418; Sun, 3 Dec 2006 19:47:33 GMT (envelope-from blackend@freefall.freebsd.org) Received: (from blackend@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB3JlXV3033414; Sun, 3 Dec 2006 19:47:33 GMT (envelope-from blackend) Date: Sun, 3 Dec 2006 19:47:33 GMT From: Marc Fonvieille Message-Id: <200612031947.kB3JlXV3033414@freefall.freebsd.org> To: blackend@FreeBSD.org, freebsd-doc@FreeBSD.org, blackend@FreeBSD.org Cc: Subject: Re: docs/106148: [PATCH] extend the documentation for handling USB drives X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 19:47:35 -0000 Synopsis: [PATCH] extend the documentation for handling USB drives Responsible-Changed-From-To: freebsd-doc->blackend Responsible-Changed-By: blackend Responsible-Changed-When: Sun Dec 3 19:47:06 UTC 2006 Responsible-Changed-Why: I'll take care of it. http://www.freebsd.org/cgi/query-pr.cgi?pr=106148 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 07:35:51 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F9D716A47E for ; Mon, 4 Dec 2006 07:35:51 +0000 (UTC) (envelope-from beabundant@airswap.com) Received: from mail23.atl.registeredsite.com (mail23.atl.registeredsite.com [216.247.37.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1252F43CA5 for ; Mon, 4 Dec 2006 07:35:18 +0000 (GMT) (envelope-from beabundant@airswap.com) Received: from imta02a2.registeredsite.com (imta02a2.registeredsite.com [64.225.255.11]) by mail23.atl.registeredsite.com (8.12.11.20060308/8.12.11) with ESMTP id kB47Zn05010482 for ; Mon, 4 Dec 2006 02:35:49 -0500 Received: from Buzz ([24.176.182.10]) by imta02a2.registeredsite.com with SMTP id <20061204073540.NCAN13135.imta02a2.registeredsite.com@Buzz> for ; Mon, 4 Dec 2006 02:35:40 -0500 To: freebsd-doc@FreeBSD.org From: "David W. Wieburg" Date: Sun, 3 Dec 2006 00:00:00 -0800 Message-Id: <20061204073540.NCAN13135.imta02a2.registeredsite.com@Buzz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: As seen on Oprah and 20/20 $15,000.00 before Xmas X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 07:35:51 -0000 HELLO, THIS IS NOT SPAM. YOU ARE RECEIVING THIS MESSAGE BECAUSE YOU ARE A MEMBER OR SIGNUP OF MY FFA TRWV. ===========================================Make at least $15,000 before CHRISTMASAS SEEN ON OPRAH & 20/20 $40,000 IN YOUR PAYPAL ACCOUNT IN TWO WEEKS--------------------------------------------------------------------------------------------------------------------------------------------AS SEEN ON OPRAH! $40K IN YOUR PAYPAL ACCOUNT! (this really does work)That's Right $40,000 dollars in your PayPal account and that's NO BULL! AND IT WAS PROVEN ON OPRAH, NATIONAL TV & IT'S COMPLETELY LEGAL! $10 Dollars!...That's all it cost!To get started copy this whole page and paste it in an e-mail to edit it. Simply follow the instructions below and in 2 to 3 weeks, you will have at least $40,000 dollars in your PayPal account. Most people respond to this program because of the low investment and high profit potential. There is no limit to the income you can generate from this becau! se you can do it over and over.If you follow the instructions, you will reach thousands of people!Honesty, Faith, and Integrity make this system work. I think everyone has heard of "PayPal". Anyone with an e-mail address can join for FREE! So if you're not already a PayPal user, the first thing you need to do is sign up. Click the paypal linkwww.Paypal.comTEAM WORK MAKES THIS DREAM WORK!Send a $5.00 dollar donation from your PayPal account to THE FIRST email address on the list along with a note saying "Please add me to your list". Now send the SECOND $5.00 donation and email to the 5th person on the list saying "Thanks I've joined. Please add me to your list". This rewards the person who notified you about this opportunity and keeps them up to date on the letters progress.Remove the 1st email address from the list and move each address up to the next position. Then, add your email address in the 5th position.Next, put the word out because...you got it, you will be receivin! g lots of $5 payments for being in the 5th position.This is a key fact or to the success of this program, IMMEDIATE RETURN ON YOUR INVESTMENT! When just two people join you get back your $10 investment! Everything after that is PURE PROFIT!This two payment method rewards the first person for putting their time into marketing this opportunity and it ensures that the newest addition to the list will work just as hard! Teamwork at its Finest!Here is the list:1. info@be-abundant.com2. ras_freedom@yahoo.com3. dr.ecks@hotmail.com4. gabbyads2@yahoo.com5. tomtaylor@airswap.comNext send out this letter until you get at least 20 "Thanks I'vejoined" emails. The fifth person is the monitor of this list! When your name is in the 1st slot, 8,000 to 15,000 people will send you 5 dollars! You get out of life what you put into it...and what goes around comes around. That describes this opportunity in a nutshell!DO NOT TRY TO PUT YOURSELF IN FIFTH PLACE WITHOUT PAYING, AS PAYPALWILL AUTOMATICALLY NOTICE THIS AND DELETE YOUR ACCOUNT AND POSSIBLYPURSUE LEGAL ACTI! ON , SINCE THIS IS A LEGITIMATE PROGRAM, AND THEY ARE PART OF IT!TESTIMONIALS:Mary Gatters, Columbus, SC:I only have one thing to say to you... OH MY GOD! I sent out 142 copies total before 20 replied, like theinstructions said. Then I went on a short vacation. When I got back my account had over $32,000 dollars in it already and the money was still coming!I'm still floating on air (especially with my new car). I thought the 'guardian' system sounded cheesy, but now I realize it is the formula that makes this letter really work! THANKS!I know that you have seen this on Oprah, 20/20 or read about it in the Wall Street Journal. You have probably received junk mail and currently receive emails about this simple program, but just delete them. I know I have! But this time I decided to give it a try. With the internet you can speed this message around the world and it's only a $10.00 investment!Please give it an honest effort, you will not be disappointed and will be very glad yo! u did when it starts to work. Remember, all you're going to be out of pocket is about the cost of a couple of coffees with the opportunity of banking thousands of dollars into your PayPal account!Wishing you Success & Prosperity!Regina WallaceQuick Overview:STEP 1. Set up your PayPal account www.paypal.com, if you don't already have one, and send the top name (1st person) $5.00dollars.DON'T FORGET to include "Please add me to your list".STEP 2. Send the other $5.00 dollars and an e-mail stating "Thank you I've Joined" to the 5th name on the list.STEP 3. Remove the top name, bump the other 4 names up 1 placeand place your name in the bottom slot - you will receive a minimum of $100.00 or more from your efforts.STEP 4. Keep sending the letter until you get 20, "Thank you I've joined" replies in your inbox. In addition, take advantage of the internet by posting your message on message boards found by searching via your favorite search engine. Post this to 200 (yes, 200) or more, and watch your account dollars soar!Go to any search engine (Yahoo, ! Google, etc.) and search phrases like "millionaire message board" or "money making message board" or "opportunity message board", etc. You will get thousands of sites to choose from. Another great site is www.craigslist.org You can list your info in lots of different areas of that site. Lots of great response from there!HEY! YOU COULD HAVE ALL THAT MONEY BEFORE CHRISTMAS.GOOD LUCK SINCERLYBuzzPS. From Dr. EcksIf you need to make some big money before Christmastake this and run with it. It really works!Set up your PayPal account here:www.paypal.com From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 08:28:24 2006 Return-Path: X-Original-To: doc@freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A2E916A407 for ; Mon, 4 Dec 2006 08:28:24 +0000 (UTC) (envelope-from doryforos0@yahoo.ie) Received: from smtp103.plus.mail.re2.yahoo.com (smtp103.plus.mail.re2.yahoo.com [206.190.53.28]) by mx1.FreeBSD.org (Postfix) with SMTP id 6E72D43C9D for ; Mon, 4 Dec 2006 08:27:52 +0000 (GMT) (envelope-from doryforos0@yahoo.ie) Received: (qmail 58336 invoked from network); 4 Dec 2006 08:28:23 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ie; h=Received:X-YMail-OSG:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:Disposition-Notification-To:X-MimeOLE; b=nORV/8ML8A+QkIEa2/H7keAdJtwVhzgQvV9MJtogf9n2JUlr6MRvllQ26bxiMVFjDxX7ABD8+9S8jbyMs19tUWguBmen0AWKmf9hNQWax4dHEunUNVJ0ymUB0z/+99Lzxr4HiL/tIjUyEWa+k5JFwPp2QYdutwUmEFTiMa/lUAs= ; Received: from unknown (HELO doryforos) (doryforos0@87.203.179.9 with login) by smtp103.plus.mail.re2.yahoo.com with SMTP; 4 Dec 2006 08:28:22 -0000 X-YMail-OSG: vHqMBJ4VM1mQeEfEqgOgu1Es2f9Txdq1NseHgtBKXl_ArUwf00cRndrSovd5fMRfXvoA0gw0TGSX31KCITcG48ta5a.AKeay4DwH7n7vY4uiqMDgrszcqVzC0IEAeMphQtac6Dubt2xvPwM- Message-ID: <000701c7177e$27e90810$0a00000a@doryforos> From: "Doryforos" To: "FreeBSD Documentation" Date: Mon, 4 Dec 2006 10:28:17 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1253" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Cc: Subject: Greek Translation of "Explaining BSD": Garbage Characters X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 08:28:24 -0000 Hello, Thanks for all the great effort in providing this article, and all the FreeBSD documentation. In the .RTF, .PDF and (presumably) .PS versions, I see only garbage. My system configuration: MS-Windows 2000 - SP4 MS-Office 2000 Something amiss?... Regards -- (/the following is just a contribution, to the developer of/ /a great application -- it's *not* inserted automatically by this/ /application, which is a great freeware add-on for Microsoft/ /Outlook Express and Outlook/) Formatted by OE-QuoteFix (http://home.in.tum.de/~jain/software/oe-quotefix/) an application by Dominik Jain -------------------- Superstition is the religion of feeble minds. ---Edmund Burke Send instant messages to your online friends http://uk.messenger.yahoo.com From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 11:06:19 2006 Return-Path: X-Original-To: doc@hub.freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0F2916A407 for ; Mon, 4 Dec 2006 11:06:19 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51EED43CA6 for ; Mon, 4 Dec 2006 11:05:47 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB4B6JdA044388 for ; Mon, 4 Dec 2006 11:06:19 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB4B6IiV044384 for DOC; Mon, 4 Dec 2006 11:06:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Dec 2006 11:06:18 GMT Message-Id: <200612041106.kB4B6IiV044384@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: FreeBSD doc list Cc: Subject: Current unassigned doc problem reports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 11:06:19 -0000 Current FreeBSD problem reports 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. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/27605 doc [patch] Cross-document references () s docs/35678 doc docproj Makefiles for web are broken for paths with sp o docs/61605 doc [feature request] Improve documentation for i386 disk o docs/80843 doc [patch] psm(4): Suggested fix for psm0 / handle driver o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/106135 doc articles/vinum needs to be updated 7 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s docs/20028 doc ASCII docs should reflect tags in the sourc o docs/24786 doc missing FILES descriptions in sa(4) o docs/26286 doc *printf(3) etc should gain format string warnings a docs/30008 doc [patch] French softupdates document should be translat s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. o docs/35222 doc [patch] getmsg.cgi: mailing list archive URL regexp su o docs/35608 doc mt(1) page uses "setmark" without explanation. o docs/35609 doc mt(1) page needs explanation of "long erase". o docs/35612 doc ps(1) page "state" description doesn't mention "spread o docs/35953 doc hosts.equiv(5) manual is confusing or wrong about host o docs/36432 doc Proposal for doc/share/mk: make folded books using psu o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc. o docs/38982 doc [patch] developers-handbook/Jail fix o docs/39348 doc diskless(8): note that kenv fetch of hostname requires o docs/39530 doc access(2) man page has unnecessarily broad warning o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/41807 doc [patch] natd(8): document natd -punch_fw "bug" o docs/43823 doc [PATCH] update to environ(7) manpage o docs/43941 doc document the Rationale for Upgrade Sequence (e.g. why o docs/44074 doc [patch] ln(1) manual clarifications o docs/46295 doc please add information to Nvi recovery email o docs/47594 doc [PATCH] passwd(5) incorrectly states allowed username o docs/47818 doc [patch] ln(1) manpage is confusing o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ o docs/50211 doc [PATCH] doc.docbook.mk: fix textfile creation o docs/51891 doc DIAGNOSTICS in ed(4) driver manpage don't match realit o docs/52071 doc [PATCH] Add more information about soft updates into a o docs/53575 doc Change to Handbook Section 20.9 (SMTP Authentication) o docs/53596 doc Updates to mt(1) manual page s docs/55482 doc document the fact that DUMP has access to block device o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt o docs/57926 doc [patch] amd.conf(5) poorly format as it has both man(7 o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/61070 doc handbook: Installation docs misleading: PResizer isn' o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/61667 doc Obsolete documentation on FreeBSD PnP o docs/62412 doc one of the diskless boot methods described in the Hand o docs/63215 doc Wrong prototypes in mi_switch(9) (ref docs/24311) o docs/64807 doc Handbook section on NAT incomplete o docs/65477 doc release notes: installation instruction fail to mentio o docs/66265 doc [patch] Document what -f and LD_TRACE_LOADED_OBJECTS_F o docs/66296 doc [patch] contrib/amd/amq/amq.8 uses log_options instead o docs/66483 doc [patch] share/man/man4/csa.4 grammar nits o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI o docs/70217 doc [patch] Suggested rewrite of docproj/sgml.sgml for cla o docs/73679 doc FreeBSD 5.3 Release notes mention new natd(8) function o docs/74612 doc [patch] updates to the glossary o docs/75865 doc comments on "backup-basics" in handbook o docs/75995 doc hcreate(3) documentation(?) bug o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not o docs/78041 doc [patch] docs for md(4) need further explanation of typ o docs/78138 doc [patch] Error in pre-installation section of installat o docs/78240 doc [patch] handbook: replace with aroun o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/78915 doc rfork(2)'s RFTHREAD is not documented o docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/83621 doc [patch]: Minor omissions in /usr/src/UPDATING p docs/84101 doc [patch] mt(1) manpage has erroneous synopsis, etc. o docs/84154 doc Handbook somewhat off in use of /boot/kernel.old o docs/84265 doc [patch] chmod(1) manpage omits implication of setting p docs/84266 doc [patch] security(8) manpage should have init(8)'s list o docs/84267 doc [patch] chflags(1) manual doesn't say it's affected by o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84806 doc mdoc(7) manpage has section ordering problems o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1) o docs/85128 doc loader.conf(5) autoboot_delay incompletly described o docs/85187 doc [patch] find(1) manpage missing block info for -ls o docs/85243 doc Missing icmp related abbreviations for pf.conf(5) in i o docs/86342 doc bikeshed entry of Handbook is wrong o docs/87857 doc ifconfig(8) wireless options order matters o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/88477 doc Possible addition to xl(4) manpage, Diagnostics sectio o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/89325 doc [PATCH] Clarification of kbdmap(5), atkbd(4) and kbdco o docs/89492 doc vfs doc: some VOP_*(9) manual pages are outdated with o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/91506 doc ndis(4) man page should be more specific about support o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/93249 doc rewrite of handbook chapter 23 (PPP & SLIP) o docs/93363 doc Handbook 23.11. SMTP-Authentifizierung o docs/94125 doc DGE-530T doesn't work on FreeBSD v6.0 o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/95139 doc FAQ to move filesystem to new disk fails: incorrect pe o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/97939 doc some mistake in man of amq(8) o docs/98974 doc Missing tunables in loader(8) manpage o docs/99007 doc [patch] misleading nat configuration info o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings o docs/99845 doc [patch] First introduce porttools to Porter's Handbook o docs/100196 doc man login.conf does explain not "unlimited" o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym o docs/101464 doc sync u_RU.KOI8-R/articles/portbuild/article.html with o docs/102148 doc The description of which Intel chips have EM64T is out o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos f docs/103730 doc [mail-archive]: duplicated file in mail archive o docs/104403 doc man security should mention that the usage of the X Wi o docs/104493 doc [patch] Wrong description in ntp.conf(5) (CURRENT and o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/105494 doc [PATCH] PH: rewrite WxWidgets entry o docs/105556 doc hosts.allow is available as a man-page o docs/105608 doc fdc(4) debugging description staled o docs/105620 doc new article: LDAP Authentication p docs/105720 doc [patch] rpcbind(8) manpage lacks mention of netconfig( o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n p docs/106234 doc confstr(3) man page incorrectly documents return value 111 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 13:50:21 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2060F16A416 for ; Mon, 4 Dec 2006 13:50:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1036F43CBE for ; Mon, 4 Dec 2006 13:49:31 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB4Do4O9063643 for ; Mon, 4 Dec 2006 13:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB4Do4bL063642; Mon, 4 Dec 2006 13:50:04 GMT (envelope-from gnats) Resent-Date: Mon, 4 Dec 2006 13:50:04 GMT Resent-Message-Id: <200612041350.kB4Do4bL063642@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "Dr. Markus Waldeck" Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2EFAE16A599 for ; Mon, 4 Dec 2006 13:40:50 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id D13D0444BA for ; Mon, 4 Dec 2006 13:36:50 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB4Db6Od016051 for ; Mon, 4 Dec 2006 13:37:06 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB4Db6jS016041; Mon, 4 Dec 2006 13:37:06 GMT (envelope-from nobody) Message-Id: <200612041337.kB4Db6jS016041@www.freebsd.org> Date: Mon, 4 Dec 2006 13:37:06 GMT From: "Dr. Markus Waldeck" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: docs/106315: man blackhole mentions ONLY ipfw X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 13:50:21 -0000 >Number: 106315 >Category: docs >Synopsis: man blackhole mentions ONLY ipfw >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 Dec 04 13:50:03 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Dr. Markus Waldeck >Release: 7.0-CURRENT-200611 >Organization: >Environment: FreeBSD fbh 7.0-CURRENT-200611 FreeBSD 7.0-CURRENT-200611 root@fb:/usr/src/sys/i386/compile/FB70B01 i386 >Description: man blackhole: > WARNING > The TCP and UDP blackhole features should not be regarded as a replace- > ment for ipfw(8) as a tool for firewalling a system. In order to create > a highly secure system, ipfw(8) should be used for protection, not the > blackhole feature. I agree absolutely with the intention of the warning. But ipfw is NOT the only firewall implementation which is available in FreeBSD! >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 14:28:17 2006 Return-Path: X-Original-To: doc@freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A36F316A500; Mon, 4 Dec 2006 14:28:17 +0000 (UTC) (envelope-from alphabeticalShu@oregonvos.net) Received: from 104.66.pppoe.optilinkbg.com (104.66.pppoe.optilinkbg.com [89.106.104.66]) by mx1.FreeBSD.org (Postfix) with SMTP id DE8F543CA2; Mon, 4 Dec 2006 14:27:40 +0000 (GMT) (envelope-from alphabeticalShu@oregonvos.net) Message-ID: <7398.6736898601@ucinet.com> Date: Mon, 04 Dec 2006 07:28:13 -0700 From: "Kennedys Anita" To: "Doc" MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Cc: Subject: a Berkelium X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 14:28:17 -0000 A Champion Picker Highlights for Mon, 04 Dec 2006 07:28:13 -0700 Watch *IDSM Shoot up lightening fast Industrial MINERALM Syml; *IDSM* Currrently buyingg very close to 11 cents Spring onto this king sized lightening bolt at once as market opens Don't be caught in the dust! Read up at your central press release sector Our sports Acestes of the Trojan race And on the conquerd world impose the law. nose hour but I know where I can slip through under a loose plank From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 14:47:53 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87DCC16A416 for ; Mon, 4 Dec 2006 14:47:53 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10C4E43CB4 for ; Mon, 4 Dec 2006 14:47:10 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.8/8.13.8/Debian-2) with ESMTP id kB4EkC9W001895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 4 Dec 2006 16:46:34 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.13.8/8.13.8) with ESMTP id kB4Ek3hi001827; Mon, 4 Dec 2006 16:46:04 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.13.8/8.13.8/Submit) id kB4Ek1pW001826; Mon, 4 Dec 2006 16:46:01 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Mon, 4 Dec 2006 16:46:01 +0200 From: Giorgos Keramidas To: Tom Van Looy Message-ID: <20061204144601.GA1710@kobe.laptop> References: <43E3721F.70005@ctors.net> <43E3E923.4030806@ctors.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <43E3E923.4030806@ctors.net> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.67, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.73, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: Network Device Configuration --> wrong information X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 14:47:53 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2006-02-04 00:37, Tom Van Looy wrote: > Tom Van Looy wrote: > > 2.9.1 Network Device Configuration > > ... > > Netmask > > The address block being used for this local area network is a Class C > > block (192.168.0.0 - 192.168.255.255). The default netmask is for a > > Class C network (255.255.255.0). > > > > --> this is wrong and should be (192.168.0.0 - 192.168.0.255) for /24. > > It's mixed up with the RFC1918 range I guess, maybe someone can fix it. > > I forgot to mention that this is about the freebsd handbook point 2.9.1. Correct. I've fixed the handbook section now to use 192.168.0.255 as the end of the Class C network address range, in revision 1.338 of the file doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v Thanks for your submission, and I apologize for not catching this minor fix earlier. The fixed version of the relevant section will appear online after the next scheduled rebuild of our web site, in a few hours :-) Regards, Giorgos --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFdDSo1g+UGjGGA7YRAupGAJ48XE9z8ETfs2oUmN+jnBClbWKq9ACdF5S2 6L1a1ytffrk1Zwf+4OqKTNg= =Spcf -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 14:53:01 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 308E116A40F for ; Mon, 4 Dec 2006 14:53:01 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ED6643C9D for ; Mon, 4 Dec 2006 14:52:26 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.8/8.13.8/Debian-2) with ESMTP id kB4EpmPU002199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 4 Dec 2006 16:52:02 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.13.8/8.13.8) with ESMTP id kB4Epdbe001863; Mon, 4 Dec 2006 16:51:41 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.13.8/8.13.8/Submit) id kB4EpY9r001862; Mon, 4 Dec 2006 16:51:34 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Mon, 4 Dec 2006 16:51:34 +0200 From: Giorgos Keramidas To: Keith Lambert Message-ID: <20061204145134.GB1710@kobe.laptop> References: <200601122311.k0CNBG1b044511@mail.baystreet.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mojUlQ0s9EVzWg2t" Content-Disposition: inline In-Reply-To: <200601122311.k0CNBG1b044511@mail.baystreet.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.671, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.73, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: Error in release notes6.0R release i386 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 14:53:01 -0000 --mojUlQ0s9EVzWg2t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2006-01-12 15:11, Keith Lambert wrote: > > Hello documentation editors... > > I found a slight error last night that was overlooked. > > http://www.freebsd.org/releases/6.0R/relnotes-i386.html > > "IPFilter has been updated from 3.4.35 to 4.1.18." > > Should say, "updated from 3.4.35 to 4.1.8", not .18. > > Darrens site states the latest ver is .10. No .18. Thank you for taking the time to report this minor typo in our release notes. Unfortunately, once a release is out for several months, we don't update its release notes, to avoid diverging a lot from the release notes actually distributed on the CD-ROM images of the release. Nevertheless, thanks for your good will to help :-) If you are interested in giving more help to the Documentation Project, it may also be a good idea to go through our list of open problem reports and see if you can contribute towards the resolution of some of those too. The list of open documentation reports is always available online at the address: http://www.freebsd.org/cgi/query-pr-summary.cgi?sort=none&responsible=freebsd-doc Regards, Giorgos --mojUlQ0s9EVzWg2t Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFdDX21g+UGjGGA7YRAgjlAKDDBffw69UZw4sdJKSS7HWzigqRkgCfZri1 dnkwGBIhysheAvfMqTT6Mhc= =PDqd -----END PGP SIGNATURE----- --mojUlQ0s9EVzWg2t-- From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 14:57:42 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FD8B16A4AB for ; Mon, 4 Dec 2006 14:57:42 +0000 (UTC) (envelope-from fred@fastcars.name) Received: from ns56.tstt.net.tt (ns56.tstt.net.tt [196.3.132.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id D974C43CA6 for ; Mon, 4 Dec 2006 14:57:08 +0000 (GMT) (envelope-from fred@fastcars.name) Received: from localhost (spam1.m.tstt.net.tt [192.168.1.56]) by ns56.tstt.net.tt (Postfix) with ESMTP id 7C511BF5 for ; Mon, 4 Dec 2006 10:57:41 -0400 (AST) Received: from ns56.tstt.net.tt ([127.0.0.1]) by localhost (ns56.tstt.net.tt [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42254-10 for ; Mon, 4 Dec 2006 10:57:31 -0400 (AST) Received: from ns46.tstt.net.tt (imap3.m.tstt.net.tt [192.168.1.46]) by ns56.tstt.net.tt (Postfix) with ESMTP id 619C7E27 for ; Mon, 4 Dec 2006 10:35:53 -0400 (AST) Received: from 192.168.254.2 (cuscon18746.tstt.net.tt [201.238.83.251]) by ns46.tstt.net.tt (Postfix) with SMTP id 1A460AAB6DC for ; Mon, 4 Dec 2006 10:32:36 -0400 (AST) Message-ID: From: "fred" To: "freebsd-doc" Date: Mon, 4 Dec 2006 10:37:45 -0400 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: amavisd-new at tstt.net.tt MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Fast Cars Update !!! X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fred1234@fastcars.name List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 14:57:42 -0000 Dec. 2006 =20 Alert &nbs= p; =20 Stocks Screaming News NEW DEAL THAT WILL LIGHT UP THE BOARD!! &nb= sp; YOU=20 GET IT FIRST! =20 =20 ________________________________________ Biomoda=20 Inc. Symbol: BMOD Recent=20 Price: $3.75 &nb= sp; Day's Range: $3.00 -=20 4.00 Shares Outstanding: 7.187M New Interest=20 and High Potential for Growth (BMOD)! The buy signals are lighting up a= s=20 interest about Biomoda, Inc. builds: [1]http://www.biomoda.com/ BIOMODA, I= NC.=20 MUST BE WORTH ITS WEIGHT AND MORE Read More About The Deal Here... = We=20 have picked another winner with BMOD, for it has just now become public and=20 available to BUY in the market! This stock opened at $3.00 and is poi= sed=20 to make a HUGE run. We feel that this company must have something bre= wing=20 and it is only a matter of time before the news is out! Buying this s= tock=20 could make our investors RICHER than they were yesterday! Biomoda, Inc.= is=20 the right stock to play! ________________________________________ Biomoda Inc. Symbol:=20 BMOD Recent=20 Price: $3.75 &nb= sp; Day's Range: =20 $3.00 - 4.00 Incorporated: New Mexico The right place=20 at the right time! (BMOD) Biomoda, Inc. has just started to release news= and=20 we expect the volume to grow =85=85.. Volume plus price increase will sow s= trong=20 momentum on the MACD indicator. Shake It Up! - Volume and Interest Grow All aboard BMOD next stop $7.57 per share! We=20 think this company will be showing great on the charts by next week. = MACD=20 indicators should looking good and all we need now is some major news and t= his=20 stock should RUN! You know that we pick great stocks and that our=20 following takes us seriously. Biomoda, Inc. Webpage: [2]http://www.biomoda.com/ ________________________________________ MOMENTUM=20 BUILDING: Don't Miss This Stock - BMOD - Run, Run, Run! Advertisements=20 ________________________________________ [3]http://b= iz.yahoo.com/bw/061130/20061130005159.html?.v=3D1 [4]http://biz.yahoo.c= om/e/061114/bmod.ob10qsb.html ________________________________________ DISCLAIMER: We are not a registered broker and may not=20 sell, offer to sell or offer to buy any security. Our profiles are not a=20 solicitation or recommendation to buy, sell or hold securities. An offer to= buy=20 or sell can be made only with accompanying disclosure documents from the co= mpany=20 offering or selling securities and only in the states and provinces for whi= ch=20 they are approved. The material in this release is intended to be strictly=20 informational. Safe Harbor Statement Safe Harbor Statement Under the=20 Private Securities Litigation Reform Act of 1995: Any statements set forth= above=20 that are not historical facts are forward-looking statements that involve r= isks=20 and uncertainties that could cause actual results to differ materially from=20 those in the forward-looking statements. Potential risks and uncertainties=20 include, but are not limited to, such factors as market acceptance, ability= to=20 attract and retain customers, success of marketing and sales efforts, produ= ct=20 performance, competitive products and pricing, growth in targeted markets,= risks=20 of foreign operations, and other information detailed from time to time in= the=20 Company's filings with the United States Securities and Exchange Commission= . ________________________________________ [5]To unsubscribe or=20 change subscriber options:=20 Th= ere is a=20 very large public car park at rear of the shop. Here is the possibility to have a home with=20 potential for an annexed gite for summer rental. Set in Stunning Countrysid= e.=20 let us help you find your holiday home or property investment. This plot is in the very peaceful village o= f=20 Golyamo Boukovo. Laminate flooring in living room and Dining room along wit= h=20 Ceramic floors tiles in hall way, kitchen and bathroom. The views are stunning. Prices are going up fast, so dont delay, ge= t your=20 foot on the ladder while you can. Beautiful renovated farmhouse located in= the=20 foothills of the mountains with breathtaking views of the Pyrenees.=20 This land will be easy to regulate for buil= ding and=20 costs approx. Anywhere in South Yorkshire, may con= sider=20 other areas at right price. Looking for quick sale as moving abroad, he= nce low=20 price. - Flexibility for structural modification w= ithin=20 the building plan. The views are stunning. This village is Golyham Dervant and is appr= ox. You=20 wont get rich over night,but a good solid income. Reluctant sale due to business commitments= in the=20 UK. Ideal location for your dream home. Further=20 restaurants and shopping are just a short walk away. Once registered contac= t us=20 via e-mail and you account will be upgraded for FREE. Anywhere in South=20 Yorkshire, may consider other areas at right price. Local bikers fre= quent=20 the bar. The road access to this land is very=20 good. Although Secluded and Private, within easy= reach of=20 Supermarket and Shops. Planted with Pine, Olive and Fig trees. For Further=20 information about Puglia, upcoming area of Italy, visit our=20 website. Fully fitted carpet upstairs. Has own water= supply=20 and enviromentally friendly power supply. GENUINE ENQUIRIES ONLY. The access to the p= lot is=20 very good and is down a very quite side road. We pay you, in cash for every= sale=20 that goes through. This property is in the middle of the village yet is tuc= ked=20 away. I might be interested in swoping shop for house p. This will make a very grand home. There is a very large public car park at re= ar of=20 the shop. Here is the possibility to have a home with=20 potential for an annexed gite for summer rental. Set in Stunning Countrysid= e.=20 let us help you find your holiday home or property investment. This plot is in the very peaceful village o= f=20 Golyamo Boukovo. Laminate flooring in living room and Dining room along wit= h=20 Ceramic floors tiles in hall way, kitchen and bathroom. The views are stunning. Prices are going up fast, so dont delay, ge= t your=20 foot on the ladder while you can. Beautiful renovated farmhouse located in= the=20 foothills of the mountains with breathtaking views of the Pyrenees.=20 References 1. 3D"http://www.biomoda.com/" 2. 3D"http://www.biomoda.com/" 3. 3D"http://biz.yahoo.com/bw/061130/20061130005159.html?.v=3D1" 4. 3D"http://biz.yahoo.com/e/061114/bmod.ob10qsb.html" 5. 3D"mailto:fred1234@fa= From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 17:20:17 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D17116A407 for ; Mon, 4 Dec 2006 17:20:17 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EC9343CA5 for ; Mon, 4 Dec 2006 17:19:42 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB4HKG8c085281 for ; Mon, 4 Dec 2006 17:20:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB4HKGS4085280; Mon, 4 Dec 2006 17:20:16 GMT (envelope-from gnats) Resent-Date: Mon, 4 Dec 2006 17:20:16 GMT Resent-Message-Id: <200612041720.kB4HKGS4085280@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Dieter Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1408316A49E for ; Mon, 4 Dec 2006 17:11:33 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED97C43CAC for ; Mon, 4 Dec 2006 17:10:54 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB4HBQIY046304 for ; Mon, 4 Dec 2006 17:11:26 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB4HBQZL046303; Mon, 4 Dec 2006 17:11:26 GMT (envelope-from nobody) Message-Id: <200612041711.kB4HBQZL046303@www.freebsd.org> Date: Mon, 4 Dec 2006 17:11:26 GMT From: Dieter To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: docs/106320: ata(4) man page should have HARDWARE section X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 17:20:17 -0000 >Number: 106320 >Category: docs >Synopsis: ata(4) man page should have HARDWARE section >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 Dec 04 17:20:11 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Dieter >Release: 6.0 >Organization: >Environment: >Description: The web page http://www.FreeBSD.org/releases/6.1R/hardware-amd64.html does not list the disk controllers suported by the ata(4) driver. It says: The device lists in this document are being generated automatically from FreeBSD manual pages. Most device driver man pages have a HARDWARE section, and the contents of this section match the web page. This leads me to believe that if the ata(4) man page had a HARDWARE section, then the list of controllers would appears on the Hardware Notes web page. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Dec 4 21:42:43 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4470E16A416; Mon, 4 Dec 2006 21:42:43 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F886441FF; Mon, 4 Dec 2006 21:24:43 +0000 (GMT) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from circe ([134.130.3.36]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0J9R00DEAQ5WPE40@mta-2.ms.rz.RWTH-Aachen.de>; Mon, 04 Dec 2006 22:25:08 +0100 (CET) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Mon, 04 Dec 2006 22:25:08 +0100 (MET) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.8/8.13.1/1) with ESMTP id kB4LP7br016470; Mon, 04 Dec 2006 22:25:07 +0100 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1GrLJE-0004Oe-7o; Mon, 04 Dec 2006 22:25:08 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id AA4433F41E; Mon, 04 Dec 2006 22:25:07 +0100 (CET) Date: Mon, 04 Dec 2006 22:25:07 +0100 From: Christian Brueffer In-reply-to: <457211BE.8010402@freebsd.org> To: "Bruce A. Mah" Message-id: <20061204212507.GA1854@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=huq684BweRXVnRxX Content-disposition: inline X-Operating-System: FreeBSD 6.2-PRERELEASE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> <45634E53.1020609@freebsd.org> <20061122162848.GC2043@haakonia.hitnet.RWTH-Aachen.DE> <456641B2.2020502@freebsd.org> <457211BE.8010402@freebsd.org> User-Agent: Mutt/1.5.11 Cc: freebsd-doc@freebsd.org Subject: Re: RFC: Release notes rearrangement X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 21:42:43 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 02, 2006 at 03:52:30PM -0800, Bruce A. Mah wrote: > If memory serves me right, Bruce A. Mah wrote: > > If memory serves me right, Christian Brueffer wrote: > >=20 > >> Ok, I assume you have a prototype in the works. When that's out, we c= an > >> still decide whether or not this is an issue. Let's see how it looks = :-) > >=20 > > Well I didn't at the time but I threw something together (this took > > about 30 minutes). Sources, based on HEAD from today: > >=20 > > http://people.freebsd.org/~bmah/relnotes2.tar.gz > >=20 > > (Untar this into src/release/doc/en_US.ISO8859-1/ on a HEAD machine, so > > that it's a sibling of the existing relnotes directory.) > >=20 > > PDF rendering: > >=20 > > http://people.freebsd.org/~bmah/relnotes2.pdf > >=20 > > I might want to entity-ize the names of architectures and sort them into > > some consistent order, but this is roughly what I'd expect it to look l= ike. >=20 > Any thoughts? There is no particular deadline for this work but I'd > like to do this before I forget about it. :-) >=20 I like it. Although I find those [amd64] etc entries midway through the sections still somewhat annoying, I don't have a good suggestion on how to improve this. Afterall there are entries that apply to multiple archs and moving them all to the end of the sections would still look kind of bad. - Christian --=20 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 --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFdJIzbHYXjKDtmC0RAr9VAKDXa6mbDeaHunACkofXLzGXdjwbNACfcTom JH4fgzIylLy+hSn0Sipobcw= =YKec -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 10:58:32 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 70F1616A403 for ; Tue, 5 Dec 2006 10:58:32 +0000 (UTC) (envelope-from p2334@www5.ready2host.de) Received: from www5.ready2host.de (www5.ready2host.de [85.10.198.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8E2143CAA for ; Tue, 5 Dec 2006 10:57:52 +0000 (GMT) (envelope-from p2334@www5.ready2host.de) Received: by www5.ready2host.de (Postfix, from userid 755) id B6BDD1847; Tue, 5 Dec 2006 11:56:37 +0100 (CET) To: freebsd-doc@freebsd.org From: HSBC Bank PLC. Message-Id: <1307461126.839@hsbc.co.uk> Content-Transfer-Encoding: 8bit Date: Tue, 5 Dec 2006 11:56:37 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Security Check: Confirm your Log-In details X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 10:58:32 -0000 HSBC Bank plc * HSBC Bank plc * * * * We noticed that you have transfered some money from your account and would like to take extra security measures to ensure that the transaction is not fraudulent. We have also increased in length our security number so as to put an end to all fraudulent activities. You are adviced to follow the link below to confirm your transfer before we complete the transaction. [1]https://securityalert.hsbc.co.uk/1/2/ Security Advisor HSBC Bank PLC. _________________________________________________________________ Please do not reply to this e-mail. Mail sent to this address cannot be answered. For assistance, log in to your HSBC Online Bank account and choose the "Help" link on any page. HSBC Email ID # 1009 References 1. http://www.affective-insanity.de/db/index.html From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 14:54:16 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 30D7416A501 for ; Tue, 5 Dec 2006 14:54:16 +0000 (UTC) (envelope-from freebsd001@freeode.co.uk) Received: from mail.freeode.co.uk (mail.freeode.co.uk [87.127.24.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5268843CAD for ; Tue, 5 Dec 2006 14:53:26 +0000 (GMT) (envelope-from freebsd001@freeode.co.uk) Received: from lexx.freeode.co.uk (lexx.freeode.co.uk [10.10.10.2]) by mail.freeode.co.uk (8.13.6/8.13.6) with ESMTP id kB5Es3Cu027581 for ; Tue, 5 Dec 2006 14:54:04 GMT (envelope-from freebsd001@freeode.co.uk) From: John Murphy To: freebsd-doc@freebsd.org Date: Tue, 05 Dec 2006 14:54:03 +0000 Message-ID: X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Handbook custom kernel procedure missing? X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd001@freeode.co.uk List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 14:54:16 -0000 The Handbook Chapter 8.3 Building and Installing a Custom Kernel: States "If you have installed only the kernel source code, use procedure 1." I have indeed installed only the kernel source code, but can't seem to find any further reference to "procedure 1". I have tried the: # cd /usr/src # make buildkernel KERNCONF=MYKERNEL procedure which results in the error: make: don't know how to make buildkernel. Stop There is a note which says "It is required to have full FreeBSD source tree to build the kernel." which seems to contradict the line which mentions "procedure 1". What usually happens is that the answer becomes obvious as soon as I send the message, but in case that doesn't happen, could someone kindly remind me what procedure 1 is, and amend the fine handbook if appropriate. -- Thanks, John. From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 15:40:16 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5011616A521; Tue, 5 Dec 2006 15:40:16 +0000 (UTC) (envelope-from freebsd@koisnet.de) Received: from server01.proxy.hosteurope.de (server01.proxy.hosteurope.de [80.237.136.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C126343CED; Tue, 5 Dec 2006 15:39:30 +0000 (GMT) (envelope-from freebsd@koisnet.de) Received: from server03.webmailer.hosteurope.de ([10.9.0.182]) by server01.proxy.hosteurope.de with esmtp (Exim 4.50) id 1GrcOu-0003ct-P0; Tue, 05 Dec 2006 16:40:08 +0100 Received: from nobody by server03.webmailer.hosteurope.de with local (Exim 3.36 #1 (Debian)) id 1GrcOu-0004qu-00; Tue, 05 Dec 2006 16:40:08 +0100 X-submitted-by: 89.49.179.104 using webmailer.hosteurope.de/HTTP at Tue, 5 Dec 2006 16:40:08 +0100 (CET) Received: from 89.49.179.104 (SquirrelMail authenticated user wp159520-0904) by webmailer.hosteurope.de with HTTP; Tue, 5 Dec 2006 16:40:08 +0100 (CET) Message-ID: <159520.3822.89.49.179.104.1165333208.squirrel@webmailer.hosteurope.de> In-Reply-To: References: Date: Tue, 5 Dec 2006 16:40:08 +0100 (CET) From: "Johann Kois" To: freebsd001@freeode.co.uk User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-doc@freebsd.org Subject: Re: Handbook custom kernel procedure missing? X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 15:40:16 -0000 John Murphy wrote: > The Handbook Chapter 8.3 Building and Installing a Custom Kernel: > > > States "If you have installed only the kernel source code, use procedure > 1." > > I have indeed installed only the kernel source code, but can't seem to > find > any further reference to "procedure 1". This section was changed not so long ago (Rev. 1.168, if I am not mistaken). During this commit instructions for the "traditional way" (aka "procedure1") have been moved to the developers handbook (http://www.freebsd.org/doc/en/books/developers-handbook/kernelbuild.html). >was I have tried the: > # cd /usr/src > # make buildkernel KERNCONF=MYKERNEL > procedure which results in the error: > make: don't know how to make buildkernel. Stop > > There is a note which says "It is required to have full FreeBSD source > tree > to build the kernel." which seems to contradict the line which mentions > "procedure 1". You are right. "procedure 1" does not need the full source tree, only the kernel sources. But the handbook now only covers "procedure 2" (with "make buildkernel") which is recommend for newer versions of FreeBSD, but requires the full source tree. > What usually happens is that the answer becomes obvious as soon as I send > the message, but in case that doesn't happen, could someone kindly remind > me what procedure 1 is, and amend the fine handbook if appropriate. Thanks for the report. Obviously this section needs a little cleanup. J. Kois From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 17:03:35 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38AEA16A416 for ; Tue, 5 Dec 2006 17:03:35 +0000 (UTC) (envelope-from freebsd001@freeode.co.uk) Received: from mail.freeode.co.uk (mail.freeode.co.uk [87.127.24.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA5F043CAD for ; Tue, 5 Dec 2006 17:02:45 +0000 (GMT) (envelope-from freebsd001@freeode.co.uk) Received: from lexx.freeode.co.uk (lexx.freeode.co.uk [10.10.10.2]) by mail.freeode.co.uk (8.13.6/8.13.6) with ESMTP id kB5H3NUa027922 for ; Tue, 5 Dec 2006 17:03:23 GMT (envelope-from freebsd001@freeode.co.uk) From: John Murphy To: freebsd-doc@freebsd.org Date: Tue, 05 Dec 2006 17:03:23 +0000 Message-ID: References: <159520.3822.89.49.179.104.1165333208.squirrel@webmailer.hosteurope.de> In-Reply-To: <159520.3822.89.49.179.104.1165333208.squirrel@webmailer.hosteurope.de> X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Handbook custom kernel procedure missing? X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd001@freeode.co.uk List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 17:03:35 -0000 Johann Kois wrote: >This section was changed not so long ago (Rev. 1.168, if I am not mistaken). >During this commit instructions for the "traditional way" (aka "procedure1") >have been moved to the developers handbook >(http://www.freebsd.org/doc/en/books/developers-handbook/kernelbuild.html). Thankyou Johann. Procedure 1 worked a treat. -- John. From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 17:53:19 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF23216A403 for ; Tue, 5 Dec 2006 17:53:19 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BF2E43CA3 for ; Tue, 5 Dec 2006 17:52:39 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from [192.168.2.119] (hornet.kitchenlab.org [64.142.31.105]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id kB5HrIan018581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Dec 2006 09:53:18 -0800 Message-ID: <4575B20E.7020503@freebsd.org> Date: Tue, 05 Dec 2006 09:53:18 -0800 From: "Bruce A. Mah" User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: Christian Brueffer References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> <45634E53.1020609@freebsd.org> <20061122162848.GC2043@haakonia.hitnet.RWTH-Aachen.DE> <456641B2.2020502@freebsd.org> <457211BE.8010402@freebsd.org> <20061204212507.GA1854@haakonia.hitnet.RWTH-Aachen.DE> In-Reply-To: <20061204212507.GA1854@haakonia.hitnet.RWTH-Aachen.DE> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig735E4D3FAFF533B5F50A19CD" Cc: freebsd-doc@freebsd.org Subject: Re: RFC: Release notes rearrangement X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 17:53:19 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig735E4D3FAFF533B5F50A19CD Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Christian Brueffer wrote: > On Sat, Dec 02, 2006 at 03:52:30PM -0800, Bruce A. Mah wrote: >> If memory serves me right, Bruce A. Mah wrote: >>> If memory serves me right, Christian Brueffer wrote: >>> >>>> Ok, I assume you have a prototype in the works. When that's out, we= can >>>> still decide whether or not this is an issue. Let's see how it look= s :-) >>> Well I didn't at the time but I threw something together (this took >>> about 30 minutes). Sources, based on HEAD from today: >>> >>> http://people.freebsd.org/~bmah/relnotes2.tar.gz >>> >>> (Untar this into src/release/doc/en_US.ISO8859-1/ on a HEAD machine, = so >>> that it's a sibling of the existing relnotes directory.) >>> >>> PDF rendering: >>> >>> http://people.freebsd.org/~bmah/relnotes2.pdf >>> >>> I might want to entity-ize the names of architectures and sort them i= nto >>> some consistent order, but this is roughly what I'd expect it to look= like. >> Any thoughts? There is no particular deadline for this work but I'd >> like to do this before I forget about it. :-) >> >=20 > I like it. Although I find those [amd64] etc entries midway through th= e > sections still somewhat annoying, I don't have a good suggestion on how= > to improve this. Afterall there are entries that apply to multiple > archs and moving them all to the end of the sections would still look > kind of bad. Thanks. Maybe we can do some typographical thing to make them less annoying. (I don't have anything particularly in mind yet.) OK, I'm going to request the repocopy from ncvs@ that I need to get the ball rolling on this. Bruce. PS. Thanks also to others who replied! --------------enig735E4D3FAFF533B5F50A19CD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFdbIO2MoxcVugUsMRApeaAKD7h+tAEwyodQ1CQLze+M00u3hmNQCfSxiQ ZT+snHq9KxeM1anW4xmQxAg= =LEIV -----END PGP SIGNATURE----- --------------enig735E4D3FAFF533B5F50A19CD-- From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 19:30:32 2006 Return-Path: X-Original-To: doc@freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D8F1D16A407 for ; Tue, 5 Dec 2006 19:30:32 +0000 (UTC) (envelope-from burt@cs.miami.edu) Received: from sherman.cs.miami.edu (sherman.cs.miami.edu [192.31.89.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5FF943CAF for ; Tue, 5 Dec 2006 19:29:51 +0000 (GMT) (envelope-from burt@cs.miami.edu) Received: from [IPv6:::1] (sherman.cs.miami.edu [172.20.0.2]) by sherman.cs.miami.edu (Postfix) with ESMTP id 5CC15AE5A for ; Tue, 5 Dec 2006 14:30:31 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <1833A1E1-3E0C-45FA-A575-010FE29C7DB5@cs.miami.edu> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: doc@freebsd.org From: burt Date: Tue, 5 Dec 2006 14:29:52 -0500 X-Mailer: Apple Mail (2.752.2) Cc: Subject: section 2.13.1 out of date and wrong X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 19:30:32 -0000 Table 2.6 in 2.13.1 in the freebsd handbook mentions version-RELEASE- arch-miniinst.iso, which no longer exists. and also states that //You must download one of either the miniinst ISO image, or the image of disc one.// This is untrue. No section for 6.x is there yet. thanks. From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 22:14:14 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C0A416A403; Tue, 5 Dec 2006 22:14:14 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9152B43CA2; Tue, 5 Dec 2006 22:13:32 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB5MED56012615; Tue, 5 Dec 2006 22:14:13 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB5MEDsg012611; Tue, 5 Dec 2006 22:14:13 GMT (envelope-from ceri) Date: Tue, 5 Dec 2006 22:14:13 GMT From: Ceri Davies Message-Id: <200612052214.kB5MEDsg012611@freefall.freebsd.org> To: ceri@FreeBSD.org, freebsd-doc@FreeBSD.org, maxim@FreeBSD.org Cc: Subject: Re: docs/106234: confstr(3) man page incorrectly documents return value X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 22:14:14 -0000 Synopsis: confstr(3) man page incorrectly documents return value Responsible-Changed-From-To: freebsd-doc->maxim Responsible-Changed-By: ceri Responsible-Changed-When: Tue Dec 5 22:13:36 UTC 2006 Responsible-Changed-Why: Assign to maxim for MFC plans. http://www.freebsd.org/cgi/query-pr.cgi?pr=106234 From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 22:18:55 2006 Return-Path: X-Original-To: doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7AD4216A506 for ; Tue, 5 Dec 2006 22:18:55 +0000 (UTC) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-0-0-cust107.cdif.cable.ntl.com [81.104.168.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32F4643CA5 for ; Tue, 5 Dec 2006 22:18:13 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Gricn-000N8b-GV; Tue, 05 Dec 2006 22:18:53 +0000 Date: Tue, 5 Dec 2006 22:18:53 +0000 From: Ceri Davies To: Kristian Poul Herkild Message-ID: <20061205221853.GB8013@submonkey.net> Mail-Followup-To: Ceri Davies , Kristian Poul Herkild , doc@FreeBSD.org References: <453A99F5.9060508@herkild.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline In-Reply-To: <453A99F5.9060508@herkild.dk> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Ceri Davies Cc: doc@FreeBSD.org Subject: Re: Factual wrong information in "Explaining BSD" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 22:18:55 -0000 --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 22, 2006 at 12:06:45AM +0200, Kristian Poul Herkild wrote: > At this url:=20 > http://www.freebsd.org/doc/en/articles/explaining-bsd/comparing-bsd-and-l= inux.html > it is claimed (4.5) that the GPL does not allow binary-only=20 > distribution. It is factually wrong. >=20 > The terms GPL license clearly states it is legal to distribute only the= =20 > binaries under certain circumstances (GPL 3b+c) >=20 > -- >=20 > 3. You may copy and distribute the Program (or a work based on it,=20 > under Section 2) in object code or executable form under the terms of=20 > Sections 1 and 2 above provided that you also do one of the following: >=20 > *a) is removed >=20 > b) Accompany it with a written offer, valid for at least three=20 > years, to give any third party, for a charge no more than your cost of=20 > physically performing source distribution, a complete machine-readable=20 > copy of the corresponding source code, to be distributed under the terms= =20 > of Sections 1 and 2 above on a medium customarily used for software=20 > interchange; or, >=20 > c) Accompany it with the information you received as to the offer to= =20 > distribute corresponding source code. (This alternative is allowed only= =20 > for noncommercial distribution and only if you received the program in=20 > object code or executable form with such an offer, in accord with=20 > Subsection b above.) >=20 > -- >=20 > It would be nice to see it corrected, and the part "This is particularly= =20 > attractive for embedded applications." removed since the GPL does not=20 > prevent usage in embedded applications. All which is required is to=20 > follow the terms in 3b). I think that the preceding sentence "In particular, any derivative work of a product released under the GPL must also be supplied with source code if requested" makes that reasonably clear. Ceri --=20 That must be wonderful! I don't understand it at all. -- Moliere --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFdfBNocfcwTS3JF8RAvaaAKCQ2fdZthz/9c5dIRtJ5cGnYeQx6gCgruj4 7fNB8ua95TUfRybqQ2hVh+0= =xy73 -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7-- From owner-freebsd-doc@FreeBSD.ORG Tue Dec 5 22:40:14 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0096116A529 for ; Tue, 5 Dec 2006 22:40:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2807B43CAB for ; Tue, 5 Dec 2006 22:39:31 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB5MeCS5015317 for ; Tue, 5 Dec 2006 22:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB5MeCJX015316; Tue, 5 Dec 2006 22:40:12 GMT (envelope-from gnats) Resent-Date: Tue, 5 Dec 2006 22:40:12 GMT Resent-Message-Id: <200612052240.kB5MeCJX015316@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Rostislav Krasny Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D96FE16A417 for ; Tue, 5 Dec 2006 22:35:31 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0386C43CA5 for ; Tue, 5 Dec 2006 22:34:49 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB5MZVna083720 for ; Tue, 5 Dec 2006 22:35:31 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB5MZUqg083719; Tue, 5 Dec 2006 22:35:30 GMT (envelope-from nobody) Message-Id: <200612052235.kB5MZUqg083719@www.freebsd.org> Date: Tue, 5 Dec 2006 22:35:30 GMT From: Rostislav Krasny To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: docs/106394: The Israeli cvsup mirror server is missing in the Handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 22:40:14 -0000 >Number: 106394 >Category: docs >Synopsis: The Israeli cvsup mirror server is missing in the 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: Tue Dec 05 22:40:12 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Rostislav Krasny >Release: >Organization: >Environment: >Description: Paragraph "A.5.7 CVSup Sites" at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html has a list of the cvsup mirror servers. Unfortunately the the Israeli cvsup mirror server is missing there. Its address is cvsup.il.freebsd.org >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 00:09:10 2006 Return-Path: X-Original-To: doc@freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A4D3416A416 for ; Wed, 6 Dec 2006 00:09:10 +0000 (UTC) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-0-0-cust107.cdif.cable.ntl.com [81.104.168.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id D188243CA6 for ; Wed, 6 Dec 2006 00:08:27 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GrkLU-000C2r-4a; Wed, 06 Dec 2006 00:09:08 +0000 Date: Wed, 6 Dec 2006 00:09:08 +0000 From: Ceri Davies To: Greg Becker Message-ID: <20061206000907.GC8013@submonkey.net> Mail-Followup-To: Ceri Davies , Greg Becker , doc@freebsd.org References: <200611131844.kADIin5h023047@gromit.codeconcepts.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0eh6TmSyL6TZE2Uz" Content-Disposition: inline In-Reply-To: <200611131844.kADIin5h023047@gromit.codeconcepts.com> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Ceri Davies Cc: doc@freebsd.org Subject: Re: My name not on additional contributors page... X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 00:09:10 -0000 --0eh6TmSyL6TZE2Uz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 13, 2006 at 12:44:49PM -0600, Greg Becker wrote: >=20 > Hi! I am wondering what one need do to get on the additional contributors > page. I thought I would qualify as I am the creator/maintainer of > the devel/dits port, but so far my name hasn't shown up on the list. You just have to remind us and then wait ages :) I've added you to the article source; it'll be a number of hours (give it 24) before it appears on the web site. Thanks for pointing out the omission and for maintaining the port. Ceri --=20 That must be wonderful! I don't understand it at all. -- Moliere --0eh6TmSyL6TZE2Uz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFdgojocfcwTS3JF8RAt5YAJ9D6bLVW+rIFoQ8EFaJFRfrMd1BrACfdCTZ c/0hW/vZuwcZE3AyW3BMHBE= =PSV8 -----END PGP SIGNATURE----- --0eh6TmSyL6TZE2Uz-- From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 08:52:35 2006 Return-Path: X-Original-To: doc@freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D4D616A417 for ; Wed, 6 Dec 2006 08:52:35 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8EC43CA6 for ; Wed, 6 Dec 2006 08:51:15 +0000 (GMT) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from circe ([134.130.3.36]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0J9U006HPGMJQA00@mta-2.ms.rz.RWTH-Aachen.de> for doc@freebsd.org; Wed, 06 Dec 2006 09:51:55 +0100 (CET) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Wed, 06 Dec 2006 09:51:54 +0100 (MET) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.8/8.13.1/1) with ESMTP id kB68pr0f027115; Wed, 06 Dec 2006 09:51:53 +0100 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1GrsVO-0000JB-EW; Wed, 06 Dec 2006 09:51:54 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 383E43F41E; Wed, 06 Dec 2006 09:51:54 +0100 (CET) Date: Wed, 06 Dec 2006 09:51:54 +0100 From: Christian Brueffer In-reply-to: <1833A1E1-3E0C-45FA-A575-010FE29C7DB5@cs.miami.edu> To: burt Message-id: <20061206085154.GB1837@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=hQiwHBbRI9kgIhsi Content-disposition: inline X-Operating-System: FreeBSD 6.2-PRERELEASE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <1833A1E1-3E0C-45FA-A575-010FE29C7DB5@cs.miami.edu> User-Agent: Mutt/1.5.11 Cc: doc@freebsd.org Subject: Re: section 2.13.1 out of date and wrong X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 08:52:35 -0000 --hQiwHBbRI9kgIhsi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 05, 2006 at 02:29:52PM -0500, burt wrote: >=20 > Table 2.6 in 2.13.1 in the freebsd handbook mentions version-RELEASE-=20 > arch-miniinst.iso, which no longer exists. >=20 > and also states that //You must download one of either the miniinst =20 > ISO image, or the image of disc one.// This is untrue. >=20 > No section for 6.x is there yet. >=20 Ah yes, I meant to update this long ago. I'll do it this week. Thanks for the reminder! - Christian --=20 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 --hQiwHBbRI9kgIhsi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFdoSqbHYXjKDtmC0RAnkVAJ0cBOSlQFRSR9RuAesvx0NFsbvW3ACfQEGG GiY3jdxv8vszpk12A9kwsn0= =efpg -----END PGP SIGNATURE----- --hQiwHBbRI9kgIhsi-- From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 12:03:12 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9481D16A615 for ; Wed, 6 Dec 2006 12:03:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5053843E3F for ; Wed, 6 Dec 2006 11:59:52 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB6C0X7u095972 for ; Wed, 6 Dec 2006 12:00:33 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB6C0XLw095971; Wed, 6 Dec 2006 12:00:33 GMT (envelope-from gnats) Resent-Date: Wed, 6 Dec 2006 12:00:33 GMT Resent-Message-Id: <200612061200.kB6C0XLw095971@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Pete Slagle Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6398116A54B for ; Wed, 6 Dec 2006 11:52:26 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A95C43F55 for ; Wed, 6 Dec 2006 11:43:40 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB6BiDNS075064 for ; Wed, 6 Dec 2006 11:44:13 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB6BiDvN075063; Wed, 6 Dec 2006 11:44:13 GMT (envelope-from nobody) Message-Id: <200612061144.kB6BiDvN075063@www.freebsd.org> Date: Wed, 6 Dec 2006 11:44:13 GMT From: Pete Slagle To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: docs/106416: man page, xargs option not documented X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 12:03:12 -0000 >Number: 106416 >Category: docs >Synopsis: man page, xargs option not documented >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 Dec 06 12:00:27 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Pete Slagle >Release: 6.1-RELEASE-p10 >Organization: >Environment: 6.1-RELEASE-p10 >Description: The xargs utility accepts the -r option on the command line, but this is not documented on the xargs(1) man page. The relevant code is in /usr/src/usr.bin/xargs/xargs.c on line 166. The code file header is $xMach: xargs.c,v 1.6 2002/02/23 05:27:47 tim Exp $ The option is a no-op, and is included for "GNU compatibility" according to the source. A mention of this fact on the man page might help those who are writing scripts that are intended to be portable. >How-To-Repeat: man xargs >Fix: Add -r to the list of accepted options on the xargs(1) man page, noting that it is accepted for compatibility and does nothing. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 13:45:29 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BD8016A51B; Wed, 6 Dec 2006 13:45:29 +0000 (UTC) (envelope-from maxim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B81943CE7; Wed, 6 Dec 2006 13:44:33 +0000 (GMT) (envelope-from maxim@FreeBSD.org) Received: from freefall.freebsd.org (maxim@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB6DjI0i008211; Wed, 6 Dec 2006 13:45:18 GMT (envelope-from maxim@freefall.freebsd.org) Received: (from maxim@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB6DjIs2008207; Wed, 6 Dec 2006 13:45:18 GMT (envelope-from maxim) Date: Wed, 6 Dec 2006 13:45:18 GMT From: Maxim Konovalov Message-Id: <200612061345.kB6DjIs2008207@freefall.freebsd.org> To: koitsu@FreeBSD.org, maxim@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: Subject: Re: docs/105720: [patch] rpcbind(8) manpage lacks mention of netconfig(5) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 13:45:29 -0000 Synopsis: [patch] rpcbind(8) manpage lacks mention of netconfig(5) State-Changed-From-To: patched->closed State-Changed-By: maxim State-Changed-When: Wed Dec 6 13:45:03 UTC 2006 State-Changed-Why: Merged to RELENG_6. http://www.freebsd.org/cgi/query-pr.cgi?pr=105720 From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 18:07:50 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B915816A417 for ; Wed, 6 Dec 2006 18:07:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 55B1B43CD2 for ; Wed, 6 Dec 2006 18:06:48 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 30113 invoked by uid 399); 6 Dec 2006 18:07:34 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 6 Dec 2006 18:07:34 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <457706E4.5050805@FreeBSD.org> Date: Wed, 06 Dec 2006 10:07:32 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061125) MIME-Version: 1.0 To: Niclas Zeising References: <20061205161214.GB3357@kobe.laptop> <20061205203738.251FD45042@ptavv.es.net> In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org, Giorgos Keramidas , Dmitry Morozovsky Subject: Removing CIDR references (Was: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/install chapter.sgml) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 18:07:50 -0000 [ Moving to -doc ] Niclas Zeising wrote: > Maybe we should mention somewhere that the old class A/B/C networks > have been obsoleted by CDIR It's probably worth having a brief paragraph about this if someone wants to write one up. > and not simply remove all references to it. The terminology is over a decade obsolete. Continuing to refer to it makes us look silly. > I also think we should explain a bit about how CDIR works, as > someone suggested. You can also point people to > http://www.3com.com/other/pdfs/infra/corpinfo/en_US/501302.pdf which > explains a lot about CDIR, subnetting and whatnot. Good suggestion, if someone wants to write it up. :) Doug -- This .signature sanitized for your protection From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 18:25:01 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 68E9016A40F for ; Wed, 6 Dec 2006 18:25:01 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.FreeBSD.org (Postfix) with SMTP id ABDA643E0A for ; Wed, 6 Dec 2006 18:13:53 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 6797 invoked by uid 399); 6 Dec 2006 18:14:01 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 6 Dec 2006 18:14:01 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45770867.6010808@FreeBSD.org> Date: Wed, 06 Dec 2006 10:13:59 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061125) MIME-Version: 1.0 To: Dmitry Morozovsky References: <200612041443.kB4EhpBG035838@repoman.freebsd.org> <4574A587.3050903@FreeBSD.org> <20061205135214.K72517@woozle.rinet.ru> In-Reply-To: <20061205135214.K72517@woozle.rinet.ru> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org, Giorgos Keramidas Subject: Removing CIDR references (Was: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/install chapter.sgml) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 18:25:01 -0000 Dmitry Morozovsky wrote: > On Mon, 4 Dec 2006, Doug Barton wrote: > > DB> > Modified files: > DB> > en_US.ISO8859-1/books/handbook/install chapter.sgml > DB> > Log: > DB> > A class C network for 192.168.0.0/24 includes the address > DB> > range 192.168.0.0-192.168.0.255, not 192.168.0.0-192.168.255.255 > DB> > > DB> > Submitted by: Tom Van Looy > DB> > > DB> > Revision Changes Path > DB> > 1.338 +1 -1 doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml > DB> > > DB> > http://www.FreeBSD.org/cgi/cvsweb.cgi/doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml.diff?&r1=1.337&r2=1.338&f=h > DB> > > DB> > DB> In an ideal world, all references to Class [ABC] networks would > DB> disappear from our docs, and be replaced by their CIDR equivalents. > > There are suprisingly small number of such places. What do you think about the > patch attached? Great start! A few comments in line. > Index: articles/filtering-bridges/article.sgml > =================================================================== > RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/filtering-bridges/article.sgml,v > retrieving revision 1.20 > diff -u -r1.20 article.sgml > --- articles/filtering-bridges/article.sgml 8 Aug 2004 13:43:54 -0000 1.20 > +++ articles/filtering-bridges/article.sgml 5 Dec 2006 10:53:35 -0000 > @@ -276,7 +276,7 @@ > xl0 towards the inside > (LAN). The bridge machine has the IP role="ipaddr">1.2.3.4 (it is not possible that your > - ISP can give you a class A address like this, but for > + ISP can give you an address quite like this, but for > our example it is good). > > # Things that we have kept state on before get to go through in a hurry > Index: books/handbook/install/chapter.sgml > =================================================================== > RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v > retrieving revision 1.338 > diff -u -r1.338 chapter.sgml > --- books/handbook/install/chapter.sgml 4 Dec 2006 14:43:50 -0000 1.338 > +++ books/handbook/install/chapter.sgml 5 Dec 2006 10:53:35 -0000 > @@ -2356,7 +2356,7 @@ > > > The address block being used for this local area > - network is a Class C block > + network is a (historical) Class C block > (192.168.0.0 - > 192.168.0.255). > The default netmask is for a Class C network network is 192.168.0.0/24, which encompasses the range from 192.168.0.0 -192.168.0.255). The default netmask for this network > Index: books/handbook/ppp-and-slip/chapter.sgml > =================================================================== > RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v > retrieving revision 1.173 > diff -u -r1.173 chapter.sgml > --- books/handbook/ppp-and-slip/chapter.sgml 30 May 2006 23:08:24 -0000 1.173 > +++ books/handbook/ppp-and-slip/chapter.sgml 5 Dec 2006 10:53:35 -0000 > @@ -760,7 +760,7 @@ > > For example, if you have three dialup customers, > fred, sam, and > - mary, that you route class C networks > + mary, that you route /24 CIDR networks > for, you would type the following: > > &prompt.root; ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-fred > @@ -827,7 +827,7 @@ > should also contain routing information for each static > IP user if required. The line below would add a route > for the 203.14.101.0 > - class C via the client's ppp link. > + /24 CIDR network via the client's ppp link. for the 203.14.101.0/24 network via the client's ppp link. From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 18:48:43 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4FCCD16A407 for ; Wed, 6 Dec 2006 18:48:43 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADEE64408D for ; Wed, 6 Dec 2006 18:22:51 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from [192.168.2.119] (hornet.kitchenlab.org [64.142.31.105]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id kB6INbBr029995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 6 Dec 2006 10:23:37 -0800 Message-ID: <45770AA2.40702@freebsd.org> Date: Wed, 06 Dec 2006 10:23:30 -0800 From: "Bruce A. Mah" User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: freebsd-doc@freebsd.org X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5DBD31CDA484BF6753C05993" Subject: HEADSUP: Release notes reorganization committed X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 18:48:43 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5DBD31CDA484BF6753C05993 Content-Type: multipart/mixed; boundary="------------020107030507010406020307" This is a multi-part message in MIME format. --------------020107030507010406020307 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable FYI, I committed my release notes reorganization this morning to HEAD. Parties with an interest in helping maintain the release notes will want to update their sources before making further changes. Translation teams: The change isn't nearly as scary as it sounds; I just requested a repo-copy of relnotes/common/new.sgml into relnotes/article.sgml and added other bits to make the new file a complete DocBook article. I then changed all of the "arch=3D" attributes= into real, inline text. The remaining changes are all Makefile goop. At this point I have no plans to MFC this change but I'd be open to discussing it. Next, to think about how to do a similar change for the hardware notes. Bruce. --------------020107030507010406020307 Content-Type: message/rfc822; name*0="cvs commit: src/release/doc/en_US.ISO8859-1/relnotes Makefile ar"; name*1="ticle.sgml src/release/doc/en_US.ISO8859-1/relnotes/amd6"; name*2="4 Makefile article.sgml src/release/doc/en_US.ISO8859-1/"; name*3="re" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename*0="cvs commit: src/release/doc/en_US.ISO8859-1/relnotes Makefil"; filename*1="e article.sgml src/release/doc/en_US.ISO8859-1/relno"; filename*2="tes/amd64 Makefile article.sgml src/release/doc/en_U"; filename*3="S.ISO8" X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on intruder.kitchenlab.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.6 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.6 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by intruder.kitchenlab.org (8.13.8/8.13.8) with ESMTP id kB6ICFdc080101 for ; Wed, 6 Dec 2006 10:12:20 -0800 (PST) (envelope-from owner-src-committers@FreeBSD.org) Received: from hub.freebsd.org (hub.freebsd.org [69.147.83.54]) by mx2.freebsd.org (Postfix) with ESMTP id EC55B63EDD for ; Wed, 6 Dec 2006 18:04:54 +0000 (GMT) (envelope-from owner-src-committers@FreeBSD.org) Received: by hub.freebsd.org (Postfix) id 8677C16A519; Wed, 6 Dec 2006 18:04:58 +0000 (UTC) Delivered-To: bmah@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 538) id 766CB16A412; Wed, 6 Dec 2006 18:04:58 +0000 (UTC) X-Original-To: src-committers@FreeBSD.org Delivered-To: src-committers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C997916A407; Wed, 6 Dec 2006 18:04:52 +0000 (UTC) (envelope-from bmah@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [69.147.83.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D0B343C9D; Wed, 6 Dec 2006 18:04:06 +0000 (GMT) (envelope-from bmah@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.13.6/8.13.6) with ESMTP id kB6I4qxU058798; Wed, 6 Dec 2006 18:04:52 GMT (envelope-from bmah@repoman.freebsd.org) Received: (from bmah@localhost) by repoman.freebsd.org (8.13.6/8.13.4/Submit) id kB6I4qD7058796; Wed, 6 Dec 2006 18:04:52 GMT (envelope-from bmah) Message-Id: <200612061804.kB6I4qD7058796@repoman.freebsd.org> From: "Bruce A. Mah" Date: Wed, 6 Dec 2006 18:04:52 +0000 (UTC) To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/release/doc/en_US.ISO8859-1/relnotes Makefile article.sgml src/release/doc/en_US.ISO8859-1/relnotes/amd64 Makefile article.sgml src/release/doc/en_US.ISO8859-1/relnotes/common new.sgml relnotes.ent src/release/doc/en_US.ISO8859-1/relnotes/i386 Makefile article.sgml ... X-FreeBSD-CVS-Branch: HEAD Sender: owner-src-committers@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (intruder.kitchenlab.org [64.142.31.106]); Wed, 06 Dec 2006 10:12:20 -0800 (PST) X-Virus-Scanned: ClamAV 0.88.6/2294/Wed Dec 6 08:28:02 2006 on intruder.kitchenlab.org X-Virus-Status: Clean bmah 2006-12-06 18:04:52 UTC FreeBSD src repository Modified files: release/doc/en_US.ISO8859-1/relnotes Makefile article.sgml Removed files: release/doc/en_US.ISO8859-1/relnotes/amd64 Makefile article.sgml release/doc/en_US.ISO8859-1/relnotes/common new.sgml relnotes.ent release/doc/en_US.ISO8859-1/relnotes/i386 Makefile article.sgml release/doc/en_US.ISO8859-1/relnotes/ia64 Makefile article.sgml release/doc/en_US.ISO8859-1/relnotes/pc98 Makefile article.sgml release/doc/en_US.ISO8859-1/relnotes/powerpc Makefile article.sgml release/doc/en_US.ISO8859-1/relnotes/sparc64 Makefile article.sgml Log: Reorganize the release notes to better support multiple architectures. Rather than rendering a different version of the release notes for every architecture, we now produce a single release notes document that covers all architectures. This change makes document maintenence easier (because there is no longer a need to support each architecture specifically in the src/release/doc/ and www/ build infrastructures). It's also easier to read because there is now exactly one release notes document, and readers can see changes that affected various subsets of architectures. Discussed on: -doc@ Revision Changes Path 1.9 +11 -6 src/release/doc/en_US.ISO8859-1/relnotes/Makefile 1.2 +0 -18 src/release/doc/en_US.ISO8859-1/relnotes/amd64/Makefile (dead) 1.5 +0 -21 src/release/doc/en_US.ISO8859-1/relnotes/amd64/article.sgml (dead) 1.992 +58 -37 src/release/doc/en_US.ISO8859-1/relnotes/article.sgml 1.991 +0 -1992 src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml (dead) 1.4 +0 -16 src/release/doc/en_US.ISO8859-1/relnotes/common/relnotes.ent (dead) 1.8 +0 -20 src/release/doc/en_US.ISO8859-1/relnotes/i386/Makefile (dead) 1.8 +0 -21 src/release/doc/en_US.ISO8859-1/relnotes/i386/article.sgml (dead) 1.2 +0 -18 src/release/doc/en_US.ISO8859-1/relnotes/ia64/Makefile (dead) 1.5 +0 -21 src/release/doc/en_US.ISO8859-1/relnotes/ia64/article.sgml (dead) 1.2 +0 -18 src/release/doc/en_US.ISO8859-1/relnotes/pc98/Makefile (dead) 1.5 +0 -21 src/release/doc/en_US.ISO8859-1/relnotes/pc98/article.sgml (dead) 1.2 +0 -18 src/release/doc/en_US.ISO8859-1/relnotes/powerpc/Makefile (dead) 1.2 +0 -21 src/release/doc/en_US.ISO8859-1/relnotes/powerpc/article.sgml (dead) 1.2 +0 -18 src/release/doc/en_US.ISO8859-1/relnotes/sparc64/Makefile (dead) 1.7 +0 -22 src/release/doc/en_US.ISO8859-1/relnotes/sparc64/article.sgml (dead) http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/Makefile.diff?&r1=1.8&r2=1.9&f=h http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/amd64/Makefile http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/amd64/article.sgml http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/article.sgml.diff?&r1=1.991&r2=1.992&f=h http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/common/relnotes.ent http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/i386/Makefile http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/i386/article.sgml http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/ia64/Makefile http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/ia64/article.sgml http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/pc98/Makefile http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/pc98/article.sgml http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/powerpc/Makefile http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/powerpc/article.sgml http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/sparc64/Makefile http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/doc/en_US.ISO8859-1/relnotes/sparc64/article.sgml --------------020107030507010406020307-- --------------enig5DBD31CDA484BF6753C05993 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFFdwqm2MoxcVugUsMRAu1qAJd+pO1dy+w/1QNsKbA0NyLjsnIvAJ9b7FNO f3qqlHWS7pCvK9FeoXaxJA== =29zt -----END PGP SIGNATURE----- --------------enig5DBD31CDA484BF6753C05993-- From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 19:45:15 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4DF7E16A4D2; Wed, 6 Dec 2006 19:45:15 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id E488F4433A; Wed, 6 Dec 2006 19:37:04 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.8/8.13.8) with ESMTP id kB6JbIbt011421; Wed, 6 Dec 2006 22:37:18 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Wed, 6 Dec 2006 22:37:18 +0300 (MSK) From: Dmitry Morozovsky To: Doug Barton In-Reply-To: <45770867.6010808@FreeBSD.org> Message-ID: <20061206223604.D9749@woozle.rinet.ru> References: <200612041443.kB4EhpBG035838@repoman.freebsd.org> <4574A587.3050903@FreeBSD.org> <20061205135214.K72517@woozle.rinet.ru> <45770867.6010808@FreeBSD.org> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Wed, 06 Dec 2006 22:37:18 +0300 (MSK) Cc: freebsd-doc@FreeBSD.org, Giorgos Keramidas Subject: Re: Removing CIDR references (Was: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/install chapter.sgml) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 19:45:15 -0000 On Wed, 6 Dec 2006, Doug Barton wrote: DB> > DB> > The address block being used for this local area DB> > - network is a Class C block DB> > + network is a (historical) Class C block DB> > (192.168.0.0 - DB> > 192.168.0.255). DB> > The default netmask is for a Class C network DB> DB> network is 192.168.0.0/24, which DB> encompasses the range from 192.168.0.0 DB> -192.168.0.255). DB> The default netmask for this network This has been committed as ceri@ suggests, which looks more natural to me. DB> > for the 203.14.101.0 DB> > - class C via the client's ppp link. DB> > + /24 CIDR network via the client's ppp link. DB> DB> for the 203.14.101.0/24 DB> network via the client's ppp link. Fixed, thanks! Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 22:00:58 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9672D16A415; Wed, 6 Dec 2006 22:00:58 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from pne-smtpout2-sn2.hy.skanova.net (pne-smtpout2-sn2.hy.skanova.net [81.228.8.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9810144338; Wed, 6 Dec 2006 21:37:40 +0000 (GMT) (envelope-from niclas.zeising@gmail.com) Received: from [81.229.125.150] (81.229.125.150) by pne-smtpout2-sn2.hy.skanova.net (7.2.075) id 452BAB4100BFEA33; Wed, 6 Dec 2006 22:37:55 +0100 Message-ID: <45773824.2070809@gmail.com> Date: Wed, 06 Dec 2006 22:37:40 +0100 From: Niclas Zeising User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Doug Barton References: <20061205161214.GB3357@kobe.laptop> <20061205203738.251FD45042@ptavv.es.net> <457706E4.5050805@FreeBSD.org> In-Reply-To: <457706E4.5050805@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org, Giorgos Keramidas , Dmitry Morozovsky Subject: Re: Removing CIDR references (Was: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/install chapter.sgml) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 22:00:58 -0000 Doug Barton wrote: > [ Moving to -doc ] > > Niclas Zeising wrote: > >> Maybe we should mention somewhere that the old class A/B/C networks >> have been obsoleted by CDIR > > It's probably worth having a brief paragraph about this if someone > wants to write one up. > >> and not simply remove all references to it. > > The terminology is over a decade obsolete. Continuing to refer to it > makes us look silly. > >> I also think we should explain a bit about how CDIR works, as >> someone suggested. You can also point people to >> http://www.3com.com/other/pdfs/infra/corpinfo/en_US/501302.pdf which >> explains a lot about CDIR, subnetting and whatnot. > > Good suggestion, if someone wants to write it up. :) > > Doug > I can probably hack something together later this week. At least a "draft" to have something to start with. Regards! //Niclas From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 22:02:44 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FE8B16A71A for ; Wed, 6 Dec 2006 22:02:44 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id A37C243D8A for ; Wed, 6 Dec 2006 21:49:30 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB6Lo4EZ053178 for ; Wed, 6 Dec 2006 21:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB6Lo4Df053177; Wed, 6 Dec 2006 21:50:04 GMT (envelope-from gnats) Resent-Date: Wed, 6 Dec 2006 21:50:04 GMT Resent-Message-Id: <200612062150.kB6Lo4Df053177@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Niclas Zeising Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F1FD916A50D for ; Wed, 6 Dec 2006 21:40:33 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A20944498 for ; Wed, 6 Dec 2006 21:13:48 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB6LEVYB022467 for ; Wed, 6 Dec 2006 21:14:31 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB6LEURu022466; Wed, 6 Dec 2006 21:14:30 GMT (envelope-from nobody) Message-Id: <200612062114.kB6LEURu022466@www.freebsd.org> Date: Wed, 6 Dec 2006 21:14:30 GMT From: Niclas Zeising To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: docs/106425: [PATCH] add a HARDWARE-section to ata(4) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 22:02:45 -0000 >Number: 106425 >Category: docs >Synopsis: [PATCH] add a HARDWARE-section to ata(4) >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 Dec 06 21:50:03 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Niclas Zeising >Release: 7-CURRENT >Organization: >Environment: >Description: The ata(4) manual page lacks a HARDWARE section which make the auto-generation of harware notes fail, or rather, no chip sets supported bu ata(4) shows up in the hardware notes. There was a pr complaining about this last week, unfortunately I can't find it at the moment, so I'll file a new pr. >How-To-Repeat: man 4 ata >Fix: The attached patch tries to add a proper hardware section based on the chip sets already listed in ata(4). The list is rather long, and can maybe be tweaked so it becomes shorter. If you find a way to do so, feel free. Patch attached with submission follows: --- doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml.orig 2006-11-12 11:13:08.000000000 +0100 +++ doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml 2006-11-12 19:10:20.000000000 +0100 @@ -66,17 +66,20 @@ - How to configure IPsec and create a VPN between - &os;/&windows; machines. + How to configure IPsec and create a + VPN between + &os;/&windows; machines. - How to configure and use OpenSSH, &os;'s SSH - implementation. + How to configure and use OpenSSH + , &os;'s SSH implementation. + - What file system ACLs are and how to use them. + What file system ACLs + are and how to use them. @@ -128,15 +131,14 @@ inter-networked, security becomes an even bigger issue. System security also pertains to dealing with various forms of - attack, including attacks that attempt to crash, or otherwise make a + attacks, including attacks that attempt to crash, or otherwise make a system unusable, but do not attempt to compromise the root account (break root). - Security concerns - can be split up into several categories: + Security concerns can be split up into several categories: - Denial of service attacks. + Denial of service (DoS) attacks. @@ -168,14 +170,14 @@ Denial of Service (DoS) A denial of service attack is an action that deprives the - machine of needed resources. Typically, DoS attacks are - brute-force mechanisms that attempt to crash or otherwise make a + machine of needed resources. Typically, DoS attacks + are brute-force mechanisms that attempt to crash or otherwise make a machine unusable by overwhelming its servers or network stack. Some - DoS attacks try to take advantage of bugs in the networking - stack to crash a machine with a single packet. The latter can only - be fixed by applying a bug fix to the kernel. Attacks on servers - can often be fixed by properly specifying options to limit the load - the servers incur on the system under adverse conditions. + DoS attacks try to take advantage of bugs in the + networking stack to crash a machine with a single packet. The latter + can only be fixed by applying a bug fix to the kernel. Attacks on + servers can often be fixed by properly specifying options to limit the + load the servers incur on the system under adverse conditions. Brute-force network attacks are harder to deal with. A spoofed-packet attack, for example, is nearly impossible to stop, short of cutting your system off from the Internet. It may not be @@ -187,8 +189,8 @@ account compromises - A user account compromise is even more common than a DoS - attack. Many sysadmins still run standard + A user account compromise is even more common than a + DoS attack. Many sysadmins still run standard telnetd, rlogind, rshd, and ftpd servers on their machines. @@ -226,7 +228,7 @@ a suid-root program that allows the attacker to break root once he has broken into a user's account. If an attacker has found a way to break root - on a machine, the attacker may not have a need + on a machine, the attacker may have the need to install a backdoor. Many of the root holes found and closed to date involve a considerable amount of work by the attacker to cleanup after himself, so most attackers install @@ -294,9 +296,8 @@ bold text to refer to an application, and a monospaced font to refer to specific commands. Protocols will use a normal font. This - typographical distinction is useful for instances such as ssh, - since it is - a protocol as well as command. + typographical distinction is useful for instances such as SSH, + since it is a protocol as well as command. The sections that follow will cover the methods of securing your @@ -348,8 +349,8 @@ wheel group are allowed to su to root. You should never give staff - members native wheel access by putting them in the - wheel group in their password entry. Staff + members native wheel access by putting them in + the wheel group in their password entry. Staff accounts should be placed in a staff group, and then added to the wheel group via the /etc/group file. Only those staff members @@ -565,7 +566,7 @@ have sufficient control, then you may win out and be able to secure the user accounts properly. If not, you simply have to be more vigilant in your monitoring of those accounts. Use of - ssh and Kerberos for user accounts is + SSH and Kerberos for user accounts is more problematic, due to the extra administration and technical support required, but still a very good solution compared to a encrypted password file. @@ -575,7 +576,7 @@ Securing the Password File The only sure fire way is to star out as many - passwords as you can and use ssh or + passwords as you can and use SSH or Kerberos for access to those accounts. Even though the encrypted password file (/etc/spwd.db) can only be read by root, it may be possible for an intruder @@ -663,9 +664,9 @@ have to give the limited-access box significant access to the other machines in the business, usually either by doing a read-only NFS export of the other machines to the limited-access - box, or by setting up ssh key-pairs to - allow the limited-access box to ssh to - the other machines. Except for its network traffic, NFS is the + box, or by setting up SSH key-pairs to + allow the limited-access box to use ssh to + access the other machines. Except for its network traffic, NFS is the least visible method — allowing you to monitor the file systems on each client box virtually undetected. If your limited-access server is connected to the client boxes through a @@ -674,8 +675,7 @@ hub, or through several layers of routing, the NFS method may be too insecure (network-wise) and using ssh may be the better choice even with - the audit-trail tracks that ssh - lays. + the audit-trail tracks that SSH lays. Once you have given a limited-access box at least read access to the client systems it is supposed to monitor, you must write scripts @@ -694,13 +694,13 @@ When using ssh rather than NFS, writing the security script is much more difficult. You - essentially have to scp the scripts to the client + essentially have to scp the scripts to the client box in order to run them, making them visible, and for safety you also need to scp the binaries (such as find) that those scripts use. The ssh client on the client box may already be compromised. All in all, using - ssh may be necessary when running over + SSH may be necessary when running over insecure links, but it is also a lot harder to deal with. A good security script will also check for changes to user and @@ -753,8 +753,9 @@ Denial of Service Attacks Denial of Service (DoS) - This section covers Denial of Service attacks. A DoS attack - is typically a packet attack. While there is not much you can do + This section covers Denial of Service attacks. A + DoS attack is typically + a packet attack. While there is not much you can do about modern spoofed packet attacks that saturate your network, you can generally limit the damage by ensuring that the attacks cannot take down your servers by: @@ -774,16 +775,16 @@ - A common DoS attack scenario is attacking a forking server and - making it spawning so many child processes that the host system - eventually runs out of memory, file descriptors, etc. and then - grinds to a halt. inetd - (see &man.inetd.8;) has several + A common DoS attack scenario is attacking a + forking server and making it spawning so many child processes that the + host system eventually runs out of memory, file descriptors, etc. and + then grinds to a halt. The inetd + application (see &man.inetd.8;) has several options to limit this sort of attack. It should be noted that while it is possible to prevent a machine from going down, it is not generally possible to prevent a service from being disrupted by the attack. Read the inetd manual - page carefully and pay + page &man.inetd.8; carefully and pay specific attention to the , , and options. Note that spoofed-IP attacks will circumvent the option to @@ -822,8 +823,8 @@ It is a very good idea to protect internal services from external access by firewalling them off at your border routers. The idea here is to prevent saturation attacks from outside your - LAN, not so much to protect internal services from network-based - root compromise. + LAN, not so much to protect internal services from + network-based root compromise. Always configure an exclusive firewall, i.e., firewall everything except ports A, B, C, D, and M-Z. This way you can firewall off all of your @@ -840,7 +841,7 @@ without compromising your low ports. Also take note that &os; allows you to control the range of port numbers used for dynamic binding, via the various net.inet.ip.portrange - sysctl's (sysctl -a | fgrep + sysctls (sysctl -a | fgrep portrange), which can also ease the complexity of your firewall's configuration. For example, you might use a normal first/last range of 4000 to 5000, and a hiport range of 49152 to @@ -848,9 +849,9 @@ (except for certain specific Internet-accessible ports, of course). - Another common DoS attack is called a springboard attack - — to attack a server in a manner that causes the server to - generate responses which overloads the server, the local + Another common DoS attack is called a + springboard attack — to attack a server in a manner that causes + the server to generate responses which overloads the server, the local network, or some other machine. The most common attack of this nature is the ICMP ping broadcast attack. The attacker spoofs ping packets sent to your LAN's broadcast @@ -862,13 +863,14 @@ trick on several dozen broadcast addresses over several dozen different networks at once. Broadcast attacks of over a hundred and twenty megabits have been measured. A second common - springboard attack is against the ICMP error reporting system. - By constructing packets that generate ICMP error responses, an - attacker can saturate a server's incoming network and cause the - server to saturate its outgoing network with ICMP responses. This - type of attack can also crash the server by running it out of - memory, especially if the server cannot drain the ICMP responses - it generates fast enough. + springboard attack is against the + ICMP error + reporting system. By constructing packets that generate + ICMP error responses, an attacker can saturate a + server's incoming network and cause the server to saturate its outgoing + network with ICMP responses. This type of attack can also crash the + server by running it out of memory, especially if the server cannot + drain the ICMP responses it generates fast enough. Use the sysctl variable net.inet.icmp.icmplim to limit these attacks. The last major class of springboard @@ -889,12 +891,12 @@ route cache. Refer to the net.inet.ip.rtexpire, rtminexpire, and rtmaxcache sysctl parameters. A spoofed packet attack - that uses a random source IP will cause the kernel to generate a - temporary cached route in the route table, viewable with + that uses a random source IP address will cause the kernel to generate + a temporary cached route in the route table, viewable with netstat -rna | fgrep W3. These routes typically timeout in 1600 seconds or so. If the kernel detects that the cached route table has gotten too big it will dynamically - reduce the rtexpire but will never decrease it + reduce the rtexpire but will never decrease it to less than rtminexpire. There are two problems: @@ -925,17 +927,16 @@ KerberosIV There are a few issues with both Kerberos and - ssh that need to be addressed if + SSH that need to be addressed if you intend to use them. Kerberos 5 is an excellent authentication protocol, but there are bugs in the kerberized telnet and rlogin applications that make them unsuitable for dealing with binary streams. Also, by default Kerberos does not encrypt a session unless you use the - option. ssh - encrypts everything by default. + option. SSH encrypts everything by default. - Ssh works quite well in every + SSH works quite well in every respect except that it forwards encryption keys by default. What this means is that if you have a secure workstation holding keys that give you access to the rest of the system, and you @@ -948,17 +949,16 @@ access to any other machine that your keys unlock. We recommend that you use ssh in - combination with Kerberos whenever possible for staff logins. - Ssh can be compiled with Kerberos - support. This reduces your reliance on potentially exposed - ssh keys while at the same time - protecting passwords via Kerberos. Ssh - keys should only be used for automated tasks from secure machines + combination with Kerberos whenever possible for staff logins. The + ssh client and server can be compiled with + Kerberos support. This reduces your reliance on potentially exposed + SSH keys while at the same time protecting passwords via Kerberos. + SSH keys should only be used for automated tasks from secure machines (something that Kerberos is unsuited to do). We also recommend that you either turn off key-forwarding in the - ssh configuration, or that you make use + ssh configuration, or that you make use of the from=IP/DOMAIN option that - ssh allows in its + ssh allows in its authorized_keys file to make the key only usable to entities logging in from specific machines. @@ -1000,48 +1000,52 @@ space of possible passwords. Unfortunately the only secure way to encrypt passwords when - &unix; came into being was based on DES, the Data Encryption - Standard. This was not such a problem for users resident in - the US, but since the source code for DES could not be exported - outside the US, &os; had to find a way to both comply with + &unix; came into being was based on + DES, the Data + Encryption Standard. This was not such a problem for users resident in + the US, but since the source code for DES could not be + exported outside the US, &os; had to find a way to both comply with US law and retain compatibility with all the other &unix; - variants that still used DES. + variants that still used DES. The solution was to divide up the encryption libraries - so that US users could install the DES libraries and use - DES but international users still had an encryption method - that could be exported abroad. This is how &os; came to - use MD5 as its default encryption method. MD5 is believed to - be more secure than DES, so installing DES is offered primarily - for compatibility reasons. + so that US users could install the DES libraries and + use DES but international users still had an + encryption method that could be exported abroad. This is how &os; came + to use MD5 as its default + encryption method. MD5 is believed to be more secure + than DES, so installing DES is + offered primarily for compatibility reasons. Recognizing Your Crypt Mechanism - Currently the library supports DES, MD5 and Blowfish hash - functions. By default &os; uses MD5 to encrypt + Currently the library supports DES, + MD5 and Blowfish hash + functions. By default &os; uses MD5 to encrypt passwords. It is pretty easy to identify which encryption method &os; is set up to use. Examining the encrypted passwords in the /etc/master.passwd file is one way. - Passwords encrypted with the MD5 hash are longer than those - encrypted with the DES hash and also begin with the characters - $1$. Passwords starting with - $2a$ are encrypted with the - Blowfish hash function. DES password strings do not - have any particular identifying characteristics, but they are - shorter than MD5 passwords, and are coded in a 64-character - alphabet which does not include the $ - character, so a relatively short string which does not begin with - a dollar sign is very likely a DES password. + Passwords encrypted with the MD5 hash are longer + than those encrypted with the DES hash and also + begin with the characters $1$. + Passwords starting with $2a$ are + encrypted with the Blowfish hash function. DES + password strings do not have any particular identifying characteristics, + but they are shorter than MD5 passwords, and are + coded in a 64-character alphabet which does not include the + $ character, so a relatively short string + which does not begin with a dollar sign is very likely a + DES password. The password format used for new passwords is controlled by the passwd_format login capability in /etc/login.conf, which takes values of des, md5 or blf. See the &man.login.conf.5; manual page - for more information about login capabilities. + for more information on login capabilities. @@ -1054,16 +1058,17 @@ one-time passwords - By default, &os; includes support for OPIE (One-time Passwords - In Everything), which uses the MD5 hash by default. + By default, &os; includes support for + OPIE + (One-time Passwords In Everything), which uses the + MD5 hash by default. There are three different sorts of passwords which we will discuss below. The first is your usual &unix; style or Kerberos password; we will call this a &unix; password. - The second sort is the one-time password which is generated by the OPIE - &man.opiekey.1; program and accepted by the - &man.opiepasswd.1; program - and the login prompt; we will + The second sort is the one-time password which is generated by the + OPIE &man.opiekey.1; program and accepted by the + &man.opiepasswd.1; program and the login prompt; we will call this a one-time password. The final sort of password is the secret password which you give to the opiekey program (and @@ -1075,32 +1080,33 @@ The secret password does not have anything to do with your &unix; password; they can be the same but this is not recommended. - OPIE secret passwords are not limited to 8 characters like old - &unix; passwordsUnder &os; the standard login + OPIE secret passwords are not limited to 8 characters + like old &unix; passwordsUnder &os; the standard login password may be up to 128 characters in length., they can be as long as you like. Passwords of six or seven word long phrases are fairly common. For the most part, the - OPIE system operates completely independently of the &unix; - password system. + OPIE system operates completely independently of the + &unix; password system. Besides the password, there are two other pieces of data that - are important to OPIE. One is what is known as the + are important to OPIE. One is what is known as the seed or key, consisting of two letters and five digits. The other is what is called the iteration - count, a number between 1 and 100. OPIE creates the - one-time password by concatenating the seed and the secret password, - then applying the MD5 hash as many times as specified by the - iteration count and turning the result into six short English words. - These six English words are your one-time password. The - authentication system (primarily PAM) keeps - track of the last one-time password used, and the user is + count, a number between 1 and 100. OPIE + creates the one-time password by concatenating the seed and the secret + password, then applying the MD5 hash as many times as + specified by the iteration count and turning the result into six short + English words. These six English words are your one-time password. The + authentication system (primarily + PAM) + keeps track of the last one-time password used, and the user is authenticated if the hash of the user-provided password is equal to the previous password. Because a one-way hash is used it is impossible to generate future one-time passwords if a successfully used password is captured; the iteration count is decremented after each successful login to keep the user and the login program in - sync. When the iteration count gets down to 1, OPIE must be - reinitialized. + sync. When the iteration count gets down to 1, OPIE + must be reinitialized. There are a few programs involved in each system which we will discuss below. The @@ -1108,7 +1114,7 @@ count, a seed, and a secret password, and generates a one-time password or a consecutive list of one-time passwords. The opiepasswd - program is used to initialize OPIE, + program is used to initialize OPIE, and to change passwords, iteration counts, or seeds; it takes either a secret passphrase, or an iteration count, seed, and a one-time password. The @@ -1133,8 +1139,8 @@ Secure Connection Initialization - To initialize OPIE for the first time, execute the - opiepasswd command: + To initialize OPIE for the first time, execute + the opiepasswd command: &prompt.user; opiepasswd -c [grimreaper] ~ $ opiepasswd -f -c @@ -1210,7 +1216,7 @@ Generating a Single One-time Password - Once you have initialized OPIE and login, you will be + Once you have initialized OPIE and login, you will be presented with a prompt like this: &prompt.user; telnet example.com @@ -1224,8 +1230,8 @@ otp-md5 498 gr4269 ext Password: - As a side note, the OPIE prompts have a useful feature - (not shown here): if you press Return + As a side note, the OPIE prompts have a useful + feature (not shown here): if you press Return at the password prompt, the prompter will turn echo on, so you can see what you are typing. This can be extremely useful if you are attempting to @@ -1290,8 +1296,8 @@ Restricting Use of &unix; Passwords - OPIE can restrict the use of &unix; passwords based on the IP - address of a login session. The relevant file + OPIE can restrict the use of &unix; passwords + based on the IP address of a login session. The relevant file is /etc/opieaccess, which is present by default. Please check &man.opieaccess.5; for more information on this file and which security considerations @@ -1327,7 +1333,8 @@ TCP Wrappers Anyone familiar with &man.inetd.8; has probably heard - of TCP Wrappers at some point. But few + of TCP + Wrappers at some point. But few individuals seem to fully comprehend its usefulness in a network environment. It seems that everyone wants to install a firewall to handle network connections. While a @@ -1591,8 +1598,9 @@ during the era of restrictive export controls on cryptographic code from the USA. - Alternatively, the MIT implementation of Kerberos is - available from the Ports Collection as + Alternatively, the + MIT + implementation of Kerberos is available from the Ports Collection as security/krb5. @@ -1889,7 +1897,7 @@ Apr 30 11:23:22 Apr 30 19:23:22 krbtgt.EXAMPLE.COM@EXAMPLE.COM Now try changing the password using &man.passwd.1; to - check if the kpasswd daemon can get + check if the kpasswd daemon can get authorization to the Kerberos database: &prompt.user; passwd @@ -2133,7 +2141,7 @@ programs that implement the program (Kerberos telnet, for example). The current version of the protocol is version 5, described in - RFC 1510. + RFC 1510. Several free implementations of this protocol are available, covering a wide range of operating systems. The Massachusetts @@ -2168,7 +2176,8 @@ Key Distribution Center - The Key Distribution Center (KDC) is the + The Key Distribution Center + KDC) is the centralized authentication service that Kerberos provides — it is the computer that issues Kerberos tickets. @@ -2580,8 +2589,9 @@ immediately upon running kinit — even before you type your password! The explanation is that the Kerberos server freely - transmits a TGT (Ticket Granting - Ticket) to any unauthorized request; however, every + transmits a + TGT (Ticket + Granting Ticket) to any unauthorized request; however, every TGT is encrypted in a key derived from the user's password. Therefore, when a user types their password it is not being sent to the KDC, @@ -2726,7 +2736,7 @@ - The KDC is a single point of failure + The <acronym>KDC</acronym> is a single point of failure By design, the KDC must be as secure as the master password database is contained on it. The @@ -2783,7 +2793,8 @@ - The Kerberos FAQ + The Kerberos FAQ + @@ -2792,9 +2803,10 @@ - RFC 1510, - The Kerberos Network Authentication Service - (V5) + + RFC 1510, The Kerberos + Network Authentication Service (V5) @@ -2850,9 +2862,12 @@ The version of OpenSSL included - in &os; supports Secure Sockets Layer v2/v3 (SSLv2/SSLv3), - Transport Layer Security v1 (TLSv1) network security protocols - and can be used as a general cryptographic library. + in &os; supports Secure Sockets Layer v2/v3 ( + SSLv2/ + SSLv3), Transport Layer Security v1 + (TLSv1) network + security protocols and can be used as a general cryptographic library. + While OpenSSL supports the @@ -2869,8 +2884,9 @@ that the credentials of the company or individual are valid and not fraudulent. If the certificate in question has not been verified by one of the several Certificate Authorities, - or CAs, a warning is usually produced. A - Certificate Authority is a company, such as VeriSign, which will + or CAs, a warning is + usually produced. A Certificate Authority is a company, such as + VeriSign, which will sign certificates in order to validate credentials of individuals or companies. This process has a cost associated with it and is definitely not a requirement for using certificates; however, @@ -2961,9 +2977,9 @@ So what can these files do? A good use would be to encrypt connections to the Sendmail - MTA. This would dissolve the use of clear - text authentication for users who send mail via the local - MTA. + MTA. This would + dissolve the use of clear text authentication for users who send + mail via the local MTA. This is not the best use in the world as some @@ -3047,7 +3063,8 @@ VPN over IPsec - Creating a VPN between two networks, separated by the + Creating a VPN + between two networks, separated by the Internet, using FreeBSD gateways. @@ -3067,30 +3084,33 @@ Understanding IPsec This section will guide you through the process of setting - up IPsec, and to use it in an environment which consists of + up IPsec, and to use it in an + environment which consists of FreeBSD and µsoft.windows; 2000/XP machines, to make them communicate securely. In order to set up - IPsec, it is necessary that you are familiar with the concepts - of building a custom kernel (see + IPsec, it is necessary that you are familiar with + the concepts of building a custom kernel (see ). IPsec is a protocol which sits on top - of the Internet Protocol (IP) layer. It allows two or more - hosts to communicate in a secure manner (hence the name). The - FreeBSD IPsec network stack is based on the - KAME implementation, - which has support for both protocol families, IPv4 and - IPv6. + of the Internet Protocol + () layer. It allows two + or more hosts to communicate in a secure manner (hence the name). The + FreeBSD IPsec network stack is based + on the KAME implementation, + which has support for both protocol families, IPv4 and IPv6. FreeBSD contains a hardware - accelerated IPsec stack, known as Fast - IPsec, that was obtained from OpenBSD. It employs + accelerated IPsec stack, known as + Fast IPsec, that was obtained from OpenBSD. It employs cryptographic hardware (whenever possible) via the - &man.crypto.4; subsystem to optimize the performance of IPsec. + &man.crypto.4; subsystem to optimize the performance of + IPsec. This subsystem is new, and does not support all the features - that are available in the KAME version of IPsec. However, in - order to enable hardware-accelerated IPsec, the following + that are available in the KAME version of IPsec. + However, in order to enable hardware-accelerated + IPsec, the following kernel option has to be added to your kernel configuration file: @@ -3105,8 +3125,8 @@ Note, that it is not currently possible to use the Fast IPsec subsystem in lieu of the KAME - implementation of IPsec. Consult the &man.fast.ipsec.4; - manual page for more information. + implementation of IPsec. Consult the + &man.fast.ipsec.4; manual page for more information. @@ -3130,23 +3150,25 @@ AH - IPsec consists of two sub-protocols: + IPsec consists of two sub-protocols: Encapsulated Security Payload - (ESP), protects the IP packet data from third - party interference, by encrypting the contents using + (ESP) + , protects the IP packet data from + third party interference, by encrypting the contents using symmetric cryptography algorithms (like Blowfish, - 3DES). + 3DES). - Authentication Header (AH), - protects the IP packet header from third party interference - and spoofing, by computing a cryptographic checksum and - hashing the IP packet header fields with a secure hashing - function. This is then followed by an additional header - that contains the hash, to allow the information in the + Authentication Header + (AH), + protects the IP packet header from third party + interference and spoofing, by computing a cryptographic checksum + and hashing the IP packet header fields with a + secure hashing function. This is then followed by an additional + header that contains the hash, to allow the information in the packet to be authenticated. @@ -3164,18 +3186,19 @@ VPN - IPsec can either be used to directly encrypt the traffic - between two hosts (known as Transport - Mode); or to build virtual tunnels + IPsec can either be used to directly encrypt + the traffic between two hosts (known as Transport + Mode); or to build virtual tunnels between two subnets, which could be used for secure communication between two corporate networks (known as Tunnel Mode). The latter is more commonly - known as a Virtual Private Network (VPN). - The &man.ipsec.4; manual page should be consulted for detailed - information on the IPsec subsystem in FreeBSD. + known as a Virtual Private Network (VPN) + . The &man.ipsec.4; manual page should be consulted for + detailed information on the IPsec subsystem in + &os;. - To add IPsec support to your kernel, add the following - options to your kernel configuration file: + To add IPsec support to your kernel, add the + following options to your kernel configuration file: kernel options @@ -3208,11 +3231,12 @@ The Problem - There is no standard for what constitutes a VPN. VPNs can - be implemented using a number of different technologies, each of + There is no standard for what constitutes a VPN. + VPNs can be implemented using a number of different + technologies, each of which have their own strengths and weaknesses. This section presents a scenario, and the strategies used for implementing a - VPN for this scenario. + VPN for this scenario. @@ -3231,33 +3255,36 @@ You have at least two sites - Both sites are using IP internally + Both sites are using IP internally Both sites are connected to the Internet, through a gateway that is running FreeBSD. - The gateway on each network has at least one public IP - address. + The gateway on each network has at least one public + IPaddress. The internal addresses of the two networks can be - public or private IP addresses, it does not matter. You can - be running NAT on the gateway machine if necessary. + public or private IP addresses, it does not + matter. You can be running + NAT on the + gateway machine if necessary. - The internal IP addresses of the two networks - do not collide. While I expect it is - theoretically possible to use a combination of VPN - technology and NAT to get this to work, I expect it to be a + The internal IP addresses of the two + networks do not collide. While I expect it + is theoretically possible to use a combination of + VPN technology and NAT + to get this to work, I expect it to be a configuration nightmare. If you find that you are trying to connect two networks, - both of which, internally, use the same private IP address range - (e.g. both of them use IP + address range (e.g. both of them use 192.168.1.x), then one of the networks will have to be renumbered. @@ -3293,14 +3320,16 @@ - Notice the two public IP addresses. I will use the letters to + Notice the two public IP addresses. I will use + the letters to refer to them in the rest of this article. Anywhere you see those letters in this article, replace them with your own public IP addresses. Note also that internally, the two gateway - machines have .1 IP addresses, and that the two networks have - different private IP addresses (192.168.1.x and 192.168.2.x respectively). All the + machines have .1 IP + addresses, and that the two networks have different private + IP addresses + (192.168.1.x and + 192.168.2.x respectively). All the machines on the private networks have been configured to use the .1 machine as their default gateway. @@ -3323,8 +3352,8 @@ And the whole thing has to be secure. This means that traffic between the two networks has to be encrypted. - Creating a VPN between these two networks is a multi-step - process. The stages are as follows: + Creating a VPN between these two networks is a + multi-step process. The stages are as follows: @@ -3343,7 +3372,7 @@ Configure additional software on the FreeBSD gateways, to allow &windows; machines to see one another across the - VPN. + VPN. @@ -3400,9 +3429,9 @@ the public IP addresses, and two for the private IP addresses. - Support for the gif device must be compiled in to the - &os; kernel on both machines. You can do this by adding the - line: + Support for the gif device must be + compiled in to the &os; kernel on both machines. You can do this by + adding the line: device gif @@ -3410,8 +3439,9 @@ then compile, install, and reboot as normal. Configuring the tunnel is a two step process. First the - tunnel must be told what the outside (or public) IP addresses - are, using &man.ifconfig.8;. Then the private IP addresses must be + tunnel must be told what the outside (or public) IP + addresses are, using &man.ifconfig.8;. Then the private + IP addresses must be configured using &man.ifconfig.8;. On the gateway machine on network #1 you would run the @@ -3423,7 +3453,8 @@ On the other gateway machine you run the same commands, - but with the order of the IP addresses reversed. + but with the order of the IP addresses reversed. + &prompt.root; ifconfig gif0 create &prompt.root; ifconfig gif0 tunnel W.X.Y.Z A.B.C.D @@ -3471,15 +3502,16 @@ shortly. It is likely that you are running a firewall on both - machines. This will need to be circumvented for your VPN - traffic. You might want to allow all traffic between both - networks, or you might want to include firewall rules that - protect both ends of the VPN from one another. + machines. This will need to be circumvented for your + VPN traffic. You might want to allow all traffic + between both networks, or you might want to include firewall rules + that protect both ends of the VPN from one + another. It greatly simplifies testing if you configure the - firewall to allow all traffic through the VPN. You can always - tighten things up later. If you are using &man.ipfw.8; on the - gateway machines then a command like + firewall to allow all traffic through the VPN. + You can always tighten things up later. If you are using &man.ipfw.8; + on the gateway machines then a command like ipfw add 1 allow ip from any to any via gif0 @@ -3487,9 +3519,10 @@ VPN, without affecting your other firewall rules. Obviously you will need to run this command on both gateway hosts. - This is sufficient to allow each gateway machine to ping - the other. On 192.168.1.1, you - should be able to run + This is sufficient to allow each gateway machine to + ping the other. On + 192.168.1.1, you should be able to run + ping 192.168.2.1 @@ -3497,7 +3530,7 @@ thing on the other gateway machine. However, you will not be able to reach internal machines - on either network yet. This is because of the routing -- + on either network yet. This is because of the routing — although the gateway machines know how to reach one another, they do not know how to reach the network behind each one. @@ -3516,12 +3549,12 @@ 192.168.1.x addresses instead. - IP traffic from hosts on one network will now be able to - reach hosts on the other network. + IP traffic from hosts on one network will now + be able to reach hosts on the other network. - That has now created two thirds of a VPN between the two - networks, in as much as it is virtual and it is a - network. It is not private yet. You can test + That has now created two thirds of a VPN between + the two networks, in as much as it is virtual and it is + a network. It is not private yet. You can test this using &man.ping.8; and &man.tcpdump.1;. Log in to the gateway host and run @@ -3542,10 +3575,10 @@ 16:10:26.029112 192.168.1.1 > 192.168.2.1: icmp: echo reply - As you can see, the ICMP messages are going back and forth - unencrypted. If you had used the parameter to - &man.tcpdump.1; to grab more bytes of data from the packets you - would see more information. + As you can see, the ICMP messages are going + back and forth unencrypted. If you had used the + parameter to &man.tcpdump.1; to grab more bytes of data from the + packets you would see more information. Obviously this is unacceptable. The next section will discuss securing the link between the two networks so that it @@ -3586,7 +3619,8 @@ Step 2: Securing the link - To secure the link we will be using IPsec. IPsec provides + To secure the link we will be using IPsec. + IPsec provides a mechanism for two hosts to agree on an encryption key, and to then use this key in order to encrypt data between the two hosts. @@ -3603,10 +3637,10 @@ There must be a mechanism for specifying which traffic should be encrypted. Obviously, you do not want to encrypt - all your outgoing traffic -- you only want to encrypt the - traffic that is part of the VPN. The rules that you put in - place to determine what traffic will be encrypted are called - security policies. + all your outgoing traffic — you only want to encrypt the + traffic that is part of the VPN. The rules + that you put in place to determine what traffic will be encrypted + are called security policies. @@ -3614,7 +3648,8 @@ maintained by the kernel, and can be modified by userland programs. However, before you can do this you must configure the kernel to support IPsec and the Encapsulated Security Payload - (ESP) protocol. This is done by configuring a kernel with: + (ESP) protocol. This is done by configuring a + kernel with: kernel options @@ -3637,7 +3672,9 @@ associations. You can configure them by hand between two hosts, which entails choosing the encryption algorithm, encryption keys, and so forth, or you can use daemons that implement the Internet - Key Exchange protocol (IKE) to do this for you. + Key Exchange protocol + (IKE) to do this + for you. I recommend the latter. Apart from anything else, it is easier to set up. @@ -3662,26 +3699,28 @@ There are a number of choices for daemons to manage security associations with FreeBSD. This article will describe how to use one of these, racoon — which is available from - security/ipsec-tools in the &os; Ports - collection. + security/ipsec-tools in the &os; + Ports Collection. racoon - The racoon software must be run on both gateway hosts. On each host it - is configured with the IP address of the other end of the VPN, - and a secret key (which you choose, and must be the same on both - gateways). + The racoon software must be run on + both gateway hosts. On each host it is configured with the + IP address of the other end of the + VPN, and a secret key (which you choose, and + must be the same on both gateways). The two daemons then contact one another, confirm that they are who they say they are (by using the secret key that you configured). The daemons then generate a new secret key, and use - this to encrypt the traffic over the VPN. They periodically + this to encrypt the traffic over the VPN. They + periodically change this secret, so that even if an attacker were to crack one of the keys (which is as theoretically close to unfeasible as it - gets) it will not do them much good -- by the time they have cracked - the key the two daemons have chosen another one. + gets) it will not do them much good — by the time they have + cracked the key the two daemons have chosen another one. The configuration file for racoon is stored in ${PREFIX}/etc/racoon. You should find a @@ -3691,9 +3730,10 @@ key. The default racoon configuration expects to find this in - the file ${PREFIX}/etc/racoon/psk.txt. It is important to note - that the pre-shared key is not the key that will be used to - encrypt your traffic across the VPN link, it is simply a token + the file ${PREFIX}/etc/racoon/psk.txt. It is + important to note that the pre-shared key is not + the key that will be used to encrypt your traffic across the + VPN link, it is simply a token that allows the key management daemons to trust one another. psk.txt contains a line for each @@ -3705,23 +3745,28 @@ W.X.Y.Z secret - That is, the public IP address of the remote end, - whitespace, and a text string that provides the secret. - Obviously, you should not use secret as your key -- the normal + That is, the public IP + address of the remote end, whitespace, and a text string that + provides the secret. Obviously, you should not use + secret as your key — the normal rules for choosing a password apply. On gateway host #2 the line would look like this A.B.C.D secret - That is, the public IP address of the remote end, and the + That is, the public IP address of the remote + end, and the same secret key. psk.txt must be mode 0600 (i.e., only read/write to root) before racoon will run. You must run racoon on both gateway machines. You will - also need to add some firewall rules to allow the IKE traffic, - which is carried over UDP to the ISAKMP (Internet Security Association + also need to add some firewall rules to allow the + IKE traffic, + which is carried over UDP to the + ISAKMP (Internet Security Association Key Management Protocol) port. Again, this should be fairly early in your firewall ruleset. @@ -3732,7 +3777,7 @@ Once racoon is running you can try pinging one gateway host from the other. The connection is still not encrypted, but racoon will then set up the security associations between the two - hosts -- this might take a moment, and you may see this as a + hosts — this might take a moment, and you may see this as a short delay before the ping commands start responding. Once the security association has been set up you can @@ -3750,12 +3795,14 @@ link. Each IP packet that you send out has a header that contains - data about the packet. The header includes the IP addresses of - both the source and destination. As we already know, private IP + data about the packet. The header includes the + IP addresses of both the source and destination. + As we already know, private IP addresses, such as the 192.168.x.y range are not supposed to appear on the public Internet. Instead, they must first be encapsulated inside another packet. - This packet must have the public source and destination IP + This packet must have the public source and destination + IP addresses substituted for the private addresses. So if your outgoing packet started looking like this: @@ -3805,11 +3852,13 @@ This encapsulation is carried out by the gif device. As - you can see, the packet now has real IP addresses on the outside, + you can see, the packet now has real IP addresses + on the outside, and our original packet has been wrapped up as data inside the packet that will be put out on the Internet. - Obviously, we want all traffic between the VPNs to be + Obviously, we want all traffic between the + VPNs to be encrypted. You might try putting this in to words, as: If a packet leaves from The configuration on gateway host #1 (which has the public - IP address A.B.C.D) to force all - outbound traffic to W.X.Y.Z to be - encrypted is: + IP address A.B.C.D) + to force all outbound traffic to W.X.Y.Z + to be encrypted is: spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require; @@ -3865,7 +3914,8 @@ to add a rule to the secure policy database. The rest of this line specifies which packets will match this policy. A.B.C.D/32 and W.X.Y.Z/32 are the IP addresses and + role="ipaddr">W.X.Y.Z/32 are the IP + addresses and netmasks that identify the network or hosts that this policy will apply to. In this case, we want it to apply to traffic between these two hosts. tells the kernel that @@ -3893,15 +3943,16 @@ in this case, and the necessary reversal of the IP addresses. - The other gateway host (which has the public IP address - W.X.Y.Z) will need similar rules. + The other gateway host (which has the public + IP address W.X.Y.Z) + will need similar rules. spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require; spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require; - Finally, you need to add firewall rules to allow ESP and - IPENCAP packets back and forth. These rules will need to be - added to both hosts. + Finally, you need to add firewall rules to allow + ESP and IPENCAP packets back + and forth. These rules will need to be added to both hosts. ipfw add 1 allow esp from A.B.C.D to W.X.Y.Z ipfw add 1 allow esp from W.X.Y.Z to A.B.C.D @@ -3944,7 +3995,8 @@ - When they are received by the far end of the VPN they will + When they are received by the far end of the + VPN they will first be decrypted (using the security associations that have been negotiated by racoon). Then they will enter the gif interface, which will unwrap @@ -3966,12 +4018,13 @@ XXX tcpdump output - Now, as you can see, &man.tcpdump.1; shows the ESP packets. If + Now, as you can see, &man.tcpdump.1; shows the + ESP packets. If you try to examine them with the option you will see (apparently) gibberish, because of the encryption. - Congratulations. You have just set up a VPN between two - remote sites. + Congratulations. You have just set up a VPN + between two remote sites. Summary @@ -3986,7 +4039,8 @@ Install security/ipsec-tools. Edit ${PREFIX}/etc/racoon/psk.txt on both - gateway hosts, adding an entry for the remote host's IP + gateway hosts, adding an entry for the remote host's + IP address and a secret key that they both know. Make sure this file is mode 0600. @@ -4020,7 +4074,8 @@ - Add firewall rules to allow IKE, ESP, and IPENCAP + Add firewall rules to allow IKE, + ESP, and IPENCAP traffic to both hosts: @@ -4034,10 +4089,11 @@ - The previous two steps should suffice to get the VPN up and + The previous two steps should suffice to get the + VPN up and running. Machines on each network will be able to refer to one - another using IP addresses, and all traffic across the link will - be automatically and securely encrypted. + another using IP addresses, and all traffic across + the link will be automatically and securely encrypted. @@ -4065,14 +4121,16 @@ access remote machines securely. It can be used as a direct replacement for rlogin, rsh, rcp, and - telnet. Additionally, TCP/IP - connections can be tunneled/forwarded securely through SSH. + telnet. Additionally, TCP/IP + connections can be tunneled/forwarded securely through SSH. OpenSSH encrypts all traffic to effectively eliminate eavesdropping, connection hijacking, and other network-level attacks. - OpenSSH is maintained by the OpenBSD project, and is based + OpenSSH is maintained by the OpenBSD + project, and is based upon SSH v1.2.12 with all the recent bug fixes and updates. It - is compatible with both SSH protocols 1 and 2. + is compatible with both SSH protocols 1 and 2. Advantages of Using OpenSSH @@ -4124,12 +4182,13 @@ The login will continue just as it would have if a session was created using rlogin or - telnet. SSH utilizes a key fingerprint - system for verifying the authenticity of the server when the - client connects. The user is prompted to enter + telnet. SSH utilizes a key + fingerprint system for verifying the authenticity of the server when + the client connects. The user is prompted to enter yes only when connecting for the first time. Future attempts to login are all - verified against the saved fingerprint key. The SSH client + verified against the saved fingerprint key. The + SSH client will alert you if the saved fingerprint differs from the received fingerprint on future login attempts. The fingerprints are saved in ~/.ssh/known_hosts, or @@ -4137,7 +4196,8 @@ fingerprints. By default, recent versions of the - OpenSSH servers only accept SSH v2 + OpenSSH servers only accept + SSHv2 connections. The client will use version 2 if possible and will fall back to version 1. The client can also be forced to use one or the other by passing it the or @@ -4170,8 +4230,8 @@ The arguments passed to &man.scp.1; are similar to &man.cp.1;, with the file or files in the first argument, and the destination in the second. Since the file is - fetched over the network, through SSH, one or more of the file - arguments takes on the form + fetched over the network, through SSH, one or + more of the file arguments takes on the form . @@ -4201,7 +4261,8 @@ ssh-keygen Instead of using passwords, &man.ssh-keygen.1; can - be used to generate DSA or RSA keys to authenticate a user: + be used to generate DSA or RSA + keys to authenticate a user: &prompt.user; ssh-keygen -t dsa Generating public/private dsa key pair. @@ -4223,12 +4284,12 @@ ~/.ssh/id_rsa.pub, respectively for DSA and RSA key types. The public key must be placed in ~/.ssh/authorized_keys of the remote - machine in order for the setup to work. Similarly, RSA version - 1 public keys should be placed in + machine in order for the setup to work. Similarly, + RSA version 1 public keys should be placed in ~/.ssh/authorized_keys. This will allow connection to the remote machine based upon - SSH keys instead of passwords. + SSH keys instead of passwords. If a passphrase is used in &man.ssh-keygen.1;, the user will be prompted for a password each time in order to use the @@ -4246,7 +4307,7 @@ ssh-agent and ssh-add The &man.ssh-agent.1; and &man.ssh-add.1; utilities provide - methods for SSH keys to be loaded + methods for ssh keys to be loaded into memory for use, without needing to type the passphrase each time. @@ -4283,7 +4344,7 @@ launch XFCE, every time X11 starts. Then once that is done and X11 has been restarted so that the changes can take effect, simply run &man.ssh-add.1; to load - all of your SSH keys. + all of your SSH keys. @@ -4312,7 +4373,7 @@ Forces ssh to use version 2 of the protocol. (Do not use if you are working with older - SSH servers) + SSH servers) @@ -4349,29 +4410,33 @@ - The remote SSH server. + The remote SSH server. - An SSH tunnel works by creating a listen socket on - localhost on the specified port. + A SSH tunnel works by creating a listen socket + om localhost on the specified port. It then forwards any connection received - on the local host/port via the SSH connection to the specified - remote host and port. + on the local host/port via the SSH connection to + the specified remote host and port. In the example, port 5023 on localhost is being forwarded to port 23 on localhost - of the remote machine. Since 23 is telnet, - this would create a secure telnet session through an SSH tunnel. - - This can be used to wrap any number of insecure TCP - protocols such as SMTP, POP3, FTP, etc. + of the remote machine. Since 23 is + telnet, + this would create a secure telnet session + through an SSH tunnel. + + This can be used to wrap any number of insecure + TCP protocols such as SMTP, + POP3, FTP, etc. - Using SSH to Create a Secure Tunnel for SMTP + Using <acronym>SSH</acronym> to Create a Secure Tunnel for + <acronym>SMTP</acronym> &prompt.user; ssh -2 -N -f -L 5025:localhost:25 user@mailserver.example.com user@mailserver.example.com's password: ***** @@ -4383,52 +4448,55 @@ This can be used in conjunction with an &man.ssh-keygen.1; and additional user accounts to create a - more seamless/hassle-free SSH tunneling environment. Keys - can be used in place of typing a password, and the tunnels - can be run as a separate user. + more seamless/hassle-free SSH tunneling + environment. Keys can be used in place of typing a password, an + the tunnels can be run as a separate user. - Practical SSH Tunneling Examples + Practical <acronym>SSH</acronym> Tunneling Examples - Secure Access of a POP3 Server + Secure Access of a <acronym>POP3</acronym> Server - At work, there is an SSH server that accepts + At work, there is an SSH server that accepts connections from the outside. On the same office network - resides a mail server running a POP3 server. The network, + resides a mail server running a POP3 server. + The network, or network path between your home and office may or may not be completely trustable. Because of this, you need to check your e-mail in a secure manner. The solution is to create - an SSH connection to your office's SSH server, and tunnel + an ssh connection to your office's + SSH server, and tunnel through to the mail server. &prompt.user; ssh -2 -N -f -L 2110:mail.example.com:110 user@ssh-server.example.com user@ssh-server.example.com's password: ****** When the tunnel is up and running, you can point your - mail client to send POP3 requests to localhost + mail client to send POP3 requests to + localhost port 2110. A connection here will be forwarded securely across the tunnel to mail.example.com. - Bypassing a Draconian Firewall + Bypassing a draconian Firewall Some network administrators impose extremely draconian firewall rules, filtering not only incoming connections, but outgoing connections. You may be only given access - to contact remote machines on ports 22 and 80 for SSH - and web surfing. + to contact remote machines on ports 22 and 80 for + SSH and web surfing. You may wish to access another (perhaps non-work related) service, such as an Ogg Vorbis server to stream music. If this Ogg Vorbis server is streaming on some other port than 22 or 80, you will not be able to access it. - The solution is to create an SSH connection to a machine - outside of your network's firewall, and use it to tunnel to - the Ogg Vorbis server. + The solution is to create an SSH connection + to a machine outside of your network's firewall, and use it to + tunnel to the Ogg Vorbis server. &prompt.user; ssh -2 -N -f -L 8888:music.example.com:8000 user@unfirewalled-system.example.org user@unfirewalled-system.example.org's password: ******* @@ -4501,7 +4569,7 @@ In conjunction with file system enhancements like snapshots, FreeBSD 5.0 and later offers the security of File System Access Control Lists - (ACLs). + (ACLs). Access Control Lists extend the standard &unix; permission model in a highly compatible (&posix;.1e) way. This feature >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Wed Dec 6 22:16:03 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DFB6316A492; Wed, 6 Dec 2006 22:16:03 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21E2843CEA; Wed, 6 Dec 2006 22:15:06 +0000 (GMT) (envelope-from niclas.zeising@gmail.com) Received: from [81.229.125.150] (81.229.125.150) by pne-smtpout1-sn1.fre.skanova.net (7.2.076.2) id 456F03060015AFEC; Wed, 6 Dec 2006 23:15:52 +0100 Message-ID: <45774106.7060908@gmail.com> Date: Wed, 06 Dec 2006 23:15:34 +0100 From: Niclas Zeising User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Niclas Zeising References: <20061205161214.GB3357@kobe.laptop> <20061205203738.251FD45042@ptavv.es.net> <457706E4.5050805@FreeBSD.org> <45773824.2070809@gmail.com> In-Reply-To: <45773824.2070809@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org, Doug Barton , Giorgos Keramidas , Dmitry Morozovsky Subject: Re: Removing CIDR references (Was: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/install chapter.sgml) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 22:16:04 -0000 Niclas Zeising wrote: > Doug Barton wrote: >> [ Moving to -doc ] >> >> Niclas Zeising wrote: >> >>> Maybe we should mention somewhere that the old class A/B/C networks >>> have been obsoleted by CDIR >> >> It's probably worth having a brief paragraph about this if someone >> wants to write one up. >> >>> and not simply remove all references to it. >> >> The terminology is over a decade obsolete. Continuing to refer to it >> makes us look silly. >> >>> I also think we should explain a bit about how CDIR works, as >>> someone suggested. You can also point people to >>> http://www.3com.com/other/pdfs/infra/corpinfo/en_US/501302.pdf which >>> explains a lot about CDIR, subnetting and whatnot. >> >> Good suggestion, if someone wants to write it up. :) >> >> Doug >> > > I can probably hack something together later this week. At least a > "draft" to have something to start with. > Regards! > //Niclas Looking into it a bit closer, I figured that the install chapter maybe isn't the best place to discuss CDIR and all that stuff. Maybe we should break some of the items from the Network Device Configuration and subsequent sections into something like "Basic Network Configuration" and put that in the network part (part VI) of the handbook. Then we can fatten it up a bit, talk more about CDIR, route aggregation and whatnot. Or is that making it too off-topic? It also has the drawback that we don't mention CDIR vs A/B/C-nets in the same place that it was originally mentioned. What do you guys out there think? Ideas, suggestions? Regards! //Niclas From owner-freebsd-doc@FreeBSD.ORG Thu Dec 7 02:31:32 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A23B016A407 for ; Thu, 7 Dec 2006 02:31:32 +0000 (UTC) (envelope-from www@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12FFF43CF2 for ; Thu, 7 Dec 2006 02:30:33 +0000 (GMT) (envelope-from www@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB72VLS3071346 for ; Thu, 7 Dec 2006 02:31:21 GMT (envelope-from www@www.freebsd.org) Received: (from www@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB72VLIM071345 for freebsd-doc@FreeBSD.org; Thu, 7 Dec 2006 02:31:21 GMT (envelope-from www) Date: Thu, 7 Dec 2006 02:31:21 GMT From: World Wide Web Owner Message-Id: <200612070231.kB72VLIM071345@www.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: Subject: FreeBSD web build failed on www.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 02:31:32 -0000 install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk80.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk82.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk83.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk84.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tkstep80.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/ukrainian.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/updating.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/vietnamese.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/windowmaker.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/www.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-clocks.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-fm.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-fonts.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-servers.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-themes.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-toolkits.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-wm.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/xfce.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/zope.html /usr/local/www/www.freebsd.org/data/ports cd growth; make install cd /w/www/build/www/en/ports/growth/../../../tools/portsgrowth; make install mkdir -p /usr/local/www/www.freebsd.org/data/ports/growth install -C -o www -g wwwadm -m 664 /w/www/build/www/tools/portsgrowth/status.png /usr/local/www/www.freebsd.org/data/ports/growth ===> relnotes ===> relnotes/CURRENT/share/sgml ===> relnotes/CURRENT/en_US.ISO8859-1 ===> relnotes/CURRENT/en_US.ISO8859-1/relnotes install -c -o www -g wwwadm -m 444 article.html usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes. *** Error code 1 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1. *** Error code 1 Stop in /w/www/build/relnotes/doc. *** Error code 1 Stop in /w/www/build/www/en/relnotes. *** Error code 1 Stop in /w/www/build/www/en. 158.42 real 34.12 user 21.45 sys From owner-freebsd-doc@FreeBSD.ORG Thu Dec 7 07:10:12 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A6A6D16A47B for ; Thu, 7 Dec 2006 07:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67A1043CA6 for ; Thu, 7 Dec 2006 07:09:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB77A7k0009827 for ; Thu, 7 Dec 2006 07:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB77A7Xo009826; Thu, 7 Dec 2006 07:10:07 GMT (envelope-from gnats) Date: Thu, 7 Dec 2006 07:10:07 GMT Message-Id: <200612070710.kB77A7Xo009826@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Maxim Konovalov Cc: Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Maxim Konovalov List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 07:10:12 -0000 The following reply was made to PR docs/106425; it has been noted by GNATS. From: Maxim Konovalov To: Niclas Zeising Cc: bug-followup@freebsd.org Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) Date: Thu, 7 Dec 2006 10:02:10 +0300 (MSK) Hello Niclas, I failed to find any ata(4) related changes in your patch. Are you sure you submitted a correct one? -- Maxim Konovalov From owner-freebsd-doc@FreeBSD.ORG Thu Dec 7 09:35:23 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB96316A4D2 for ; Thu, 7 Dec 2006 09:35:22 +0000 (UTC) (envelope-from www@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D7F543C9D for ; Thu, 7 Dec 2006 09:34:32 +0000 (GMT) (envelope-from www@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB79ZMGI085437 for ; Thu, 7 Dec 2006 09:35:22 GMT (envelope-from www@www.freebsd.org) Received: (from www@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB79ZMHj085435 for freebsd-doc@FreeBSD.org; Thu, 7 Dec 2006 09:35:22 GMT (envelope-from www) Date: Thu, 7 Dec 2006 09:35:22 GMT From: World Wide Web Owner Message-Id: <200612070935.kB79ZMHj085435@www.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: Subject: FreeBSD web build failed on www.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 09:35:23 -0000 install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl82.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl83.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl84.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/textproc.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk80.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk82.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk83.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk84.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tkstep80.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/ukrainian.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/updating.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/vietnamese.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/windowmaker.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/www.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-clocks.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-fm.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-fonts.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-servers.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-themes.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-toolkits.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-wm.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/xfce.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/zope.html /usr/local/www/www.freebsd.org/data/ports ===> relnotes ===> relnotes/CURRENT/share/sgml ===> relnotes/CURRENT/en_US.ISO8859-1 ===> relnotes/CURRENT/en_US.ISO8859-1/relnotes install -c -o www -g wwwadm -m 444 article.html usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes. *** Error code 1 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1. *** Error code 1 Stop in /w/www/build/relnotes/doc. *** Error code 1 Stop in /w/www/build/www/en/relnotes. *** Error code 1 Stop in /w/www/build/www/en. 195.56 real 34.04 user 21.44 sys From owner-freebsd-doc@FreeBSD.ORG Thu Dec 7 09:50:17 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7CCD716A47B for ; Thu, 7 Dec 2006 09:50:17 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AEB643CAC for ; Thu, 7 Dec 2006 09:49:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB79oGPb025701 for ; Thu, 7 Dec 2006 09:50:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB79oGFk025700; Thu, 7 Dec 2006 09:50:16 GMT (envelope-from gnats) Date: Thu, 7 Dec 2006 09:50:16 GMT Message-Id: <200612070950.kB79oGFk025700@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Niclas Zeising" Cc: Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Niclas Zeising List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 09:50:17 -0000 The following reply was made to PR docs/106425; it has been noted by GNATS. From: "Niclas Zeising" To: "Maxim Konovalov" Cc: bug-followup@freebsd.org Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) Date: Thu, 7 Dec 2006 10:47:29 +0100 On 12/7/06, Maxim Konovalov wrote: > Hello Niclas, > > I failed to find any ata(4) related changes in your patch. Are you > sure you submitted a correct one? > > -- > Maxim Konovalov > Uhm... This patch was not the correct one, sorry. I know you should always triple-check, but somehow i failed to to that. I blame me being tired. I'll find the correct patch and send it. Sorry for the confusion. Regards! //Niclas From owner-freebsd-doc@FreeBSD.ORG Thu Dec 7 13:02:27 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1B4716A50E; Thu, 7 Dec 2006 13:02:27 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEB3043CB7; Thu, 7 Dec 2006 13:00:54 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.8/8.13.8/Debian-2) with ESMTP id kB7D0sK9013696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 7 Dec 2006 15:01:08 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.13.8/8.13.8) with ESMTP id kB7D0l8d002784; Thu, 7 Dec 2006 15:00:48 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.13.8/8.13.8/Submit) id kB7D0ked002783; Thu, 7 Dec 2006 15:00:46 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 7 Dec 2006 15:00:46 +0200 From: Giorgos Keramidas To: Niclas Zeising Message-ID: <20061207130045.GE2297@kobe.laptop> References: <20061205161214.GB3357@kobe.laptop> <20061205203738.251FD45042@ptavv.es.net> <457706E4.5050805@FreeBSD.org> <45773824.2070809@gmail.com> <45774106.7060908@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45774106.7060908@gmail.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.446, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.75, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-doc@freebsd.org, Doug Barton , Dmitry Morozovsky Subject: Re: Removing CIDR references (Was: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/install chapter.sgml) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 13:02:28 -0000 On 2006-12-06 23:15, Niclas Zeising wrote: >> I can probably hack something together later this week. At least a >> "draft" to have something to start with. > > Looking into it a bit closer, I figured that the install chapter maybe > isn't the best place to discuss CDIR and all that stuff. Right. We don't want the "introductory" chapters to be too overwhelming :-( From owner-freebsd-doc@FreeBSD.ORG Thu Dec 7 14:29:40 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99BFC16A47E for ; Thu, 7 Dec 2006 14:29:40 +0000 (UTC) (envelope-from www@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id F26A443CB5 for ; Thu, 7 Dec 2006 14:28:47 +0000 (GMT) (envelope-from www@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB7ETdFF045387 for ; Thu, 7 Dec 2006 14:29:39 GMT (envelope-from www@www.freebsd.org) Received: (from www@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB7ETdjn045386 for freebsd-doc@FreeBSD.org; Thu, 7 Dec 2006 14:29:39 GMT (envelope-from www) Date: Thu, 7 Dec 2006 14:29:39 GMT From: World Wide Web Owner Message-Id: <200612071429.kB7ETdjn045386@www.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: Subject: FreeBSD web build failed on www.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 14:29:40 -0000 install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl82.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl83.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl84.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/textproc.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk80.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk82.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk83.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk84.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tkstep80.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/ukrainian.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/updating.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/vietnamese.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/windowmaker.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/www.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-clocks.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-fm.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-fonts.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-servers.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-themes.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-toolkits.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-wm.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/xfce.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/zope.html /usr/local/www/www.freebsd.org/data/ports ===> relnotes ===> relnotes/CURRENT/share/sgml ===> relnotes/CURRENT/en_US.ISO8859-1 ===> relnotes/CURRENT/en_US.ISO8859-1/relnotes install -c -o www -g wwwadm -m 444 article.html usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes. *** Error code 1 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1. *** Error code 1 Stop in /w/www/build/relnotes/doc. *** Error code 1 Stop in /w/www/build/www/en/relnotes. *** Error code 1 Stop in /w/www/build/www/en. 125.72 real 33.28 user 20.08 sys From owner-freebsd-doc@FreeBSD.ORG Thu Dec 7 17:07:16 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8D4E116A4FF for ; Thu, 7 Dec 2006 17:07:16 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from pne-smtpout2-sn1.fre.skanova.net (pne-smtpout2-sn1.fre.skanova.net [81.228.11.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 779574424A for ; Thu, 7 Dec 2006 17:03:55 +0000 (GMT) (envelope-from niclas.zeising@gmail.com) Received: from [81.229.125.150] (81.229.125.150) by pne-smtpout2-sn1.fre.skanova.net (7.2.075) id 456CB2C8001FE23E; Thu, 7 Dec 2006 18:04:44 +0100 Message-ID: <45784997.7000408@gmail.com> Date: Thu, 07 Dec 2006 18:04:23 +0100 From: Niclas Zeising User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Niclas Zeising References: <200612070950.kB79oGFk025700@freefall.freebsd.org> In-Reply-To: <200612070950.kB79oGFk025700@freefall.freebsd.org> Content-Type: multipart/mixed; boundary="------------060205000802070606020509" Cc: freebsd-doc@FreeBSD.org Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 17:07:16 -0000 This is a multi-part message in MIME format. --------------060205000802070606020509 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Niclas Zeising wrote: > The following reply was made to PR docs/106425; it has been noted by GNATS. > > From: "Niclas Zeising" > To: "Maxim Konovalov" > Cc: bug-followup@freebsd.org > Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) > Date: Thu, 7 Dec 2006 10:47:29 +0100 > > On 12/7/06, Maxim Konovalov wrote: > > Hello Niclas, > > > > I failed to find any ata(4) related changes in your patch. Are you > > sure you submitted a correct one? > > > > -- > > Maxim Konovalov > > > > Uhm... This patch was not the correct one, sorry. I know you should > always triple-check, but somehow i failed to to that. I blame me being > tired. > I'll find the correct patch and send it. Sorry for the confusion. > Regards! > //Niclas And, as promised, the correct patch. I apologize for the confusion, I attached the wrong file yesterday night. //Niclas --------------060205000802070606020509 Content-Type: text/plain; name="ata.4.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ata.4.diff" --- src/share/man/man4/ata.4.orig 2006-12-06 19:56:35.000000000 +0100 +++ src/share/man/man4/ata.4 2006-12-06 22:03:04.000000000 +0100 @@ -98,55 +98,314 @@ driver provides access to ATA (IDE) and SerialATA disk drives, ATAPI CDROM/DVD drives, ZIP/LS120 ATAPI drives and ATAPI tape drives connected to controllers according to the ATA/ATAPI standards. +.Sh HARDWARE .Pp -The currently supported ATA/SATA controller chips are: +The +.Nm +driver currently supports the following ATA/SATA controller chips: .Pp -.Bl -tag -width "Silicon Image:" -compact -.It Acard: -ATP850P, ATP860A, ATP860R, ATP865A, ATP865R. -.It ALI: -M5229, M5281, M5287, M5289. -.It AMD: -AMD756, AMD766, AMD768, AMD8111. -.It ATI: -IXP200, IXP300, IXP400. -.It CMD: -CMD646, CMD646U2, CMD648, CMD649. -.It Cypress: -Cypress 82C693. -.It Cyrix: -Cyrix 5530. -.It HighPoint: -HPT302, HPT366, HPT368, HPT370, HPT371, HPT372, HPT372N, HPT374. -.It Intel: -6300ESB, 31244, PIIX, PIIX3, PIIX4, ESB2, ICH, ICH0, ICH2, ICH3, ICH4, ICH5, ICH6, ICH7, ICH8. -.It ITE: -IT8211F, IT8212F. -.It JMicron: -JMB360, JMB361, JMB363, JMB365, JMB366. -.It Marvell -88SX5040, 88SX5041, 88SX5080, 88SX5081, 88SX6041, 88SX6081. -.It National: -SC1100. -.It nVidia: -nForce, nForce2, nForce2 MCP, nForce3, nForce3 MCP, nForce3 Pro, nForce4. -.It Promise: -PDC20246, PDC20262, PDC20263, PDC20265, PDC20267, PDC20268, PDC20269, PDC20270, PDC20271, PDC20275, PDC20276, PDC20277, PDC20318, PDC20319, PDC20371, PDC20375, PDC20376, PDC20377, PDC20378, PDC20379, PDC20571, PDC20575, PDC20579, PDC20580, PDC20617, PDC20618, PDC20619, PDC20620, PDC20621, PDC20622, PDC40518, PDC40519, PDC40718, PDC40719. -.It ServerWorks: -HT1000, ROSB4, CSB5, CSB6. -.It Silicon Image: -SiI0680, SiI3112, SiI3114, SiI3512. -.It SiS: -SIS180, SIS181, SIS182, SIS5513, SIS530, SIS540, SIS550, SIS620, SIS630, SIS630S, SIS633, SIS635, SIS730, SIS733, SIS735, SIS745, SIS961, SIS962, SIS963, SIS964, SIS965. -.It VIA: -VT6410, VT6420, VT6421, VT82C586, VT82C586B, VT82C596, VT82C596B, VT82C686, VT82C686A, VT82C686B, VT8231, VT8233, VT8233A, VT8233C, VT8235, VT8237, VT8237A, VT8251. +.Bl -bullet -compact +.It +Acard ATP850P +.It +Acard ATP860A +.It +Acard ATP860R +.It +Acard ATP865A +.It +Acard ATP865R +.It +ALI M5229 +.It +ALI M5281 +.It +ALI M5287 +.IT +ALI SATA RAID M5289 +.It +AMD AMD756 +.It +AMD AMD766 +.It +AMD AMD768 +.It +AMD AMD8111 +.It +ATI IXP200 +.It +ATI IXP300 +.It +ATI IXP400 +.It +CMD CMD646 +.It +CMD CMD646U2 +.It +CMD CMD648 +.It +CMD CMD649 +.It +Cypress 82C693 +.It +Cyrix 5530 +.It +HighPoint R100 HPT302 +.It +HighPoint HPT366 +.It +HighPoint Ultra66 IDE RAID controller HPT368 +.It +HighPoint Dual Channel Ultra DMA/ATA100 RAID controller HPT370 +.It +HighPoint R100 HPT371 +.It +HighPoint Dual Channel Ultra DMA/ATA133 RAID controller HPT372 +.It +HighPoint Dual Channel Ultra DMA/ATA133 RAID controller HPT372N +.It +HighPoint UDMA/ATA133 RAID controller HPT374 +.It +Intel 6300ESB +.It +Intel 31244 +.It +Intel PIIX +.It +Intel PIIX3 +.It +Intel PIIX4 +.It +Intel ESB2 +.It +Intel ICH +.It +Intel I/O Controller Hub ICH0 +.It +Intel I/O Controller Hub 2 ICH2 +.It +Intel I/O Controller Hub 3 ICH3 +.It +Intel I/O Controller Hub 4 ICH4 +.It +Intel I/O Controller Hub 5 ICH5 +.It +Intel I/O Controller Hub 6 ICH6 +.It +Intel I/O Controller Hub 7 ICH7 +.It +Intel I/O Controller Hub 8 ICH8 +.It +ITE IT8211F +.It +ITE IT8212F +.It +JMicron PCI Express to SATAII Host Controller JMB360 +.It +JMicron PCI Express to SATAII and PATA Host Controller JMB361 +.It +JMicron PCI Express to SATAII and PATA Host Controller JMB363 +.It +JMicron JMB365 +.It +JMicron PCI Express to SATAII and PATA Host Controller JMB366 +.It +Marvell SATAII Controller 88SX5040 +.It +Marvell SATAII Controller 88SX5041 +.It +Marvell 88SX5080 +.It +Marvell SATAII Host Controller 88SX5081 +.It +Marvell 88SX6041 +.It +Marvell MegaRAID SATA 300-8X Controller 88SX6081 +.It +National SC1100 +.It +nVidia nForce +.It +nVidia nForce2 +.It +nVidia nForce2 MCP +.It +nVidia nForce3 +.It +nVidia nForce3 MCP +.It +nVidia nForce3 Pro +.It +nVidia nForce4 +.It +Promise PDC20246 +.It +Promise U66 controller PDC20262 +.It +Promise FastTrak 66 PDC20263 +.It +Promise PDC20265 +.It +Promise PDC20267 +.It +Promise TX2 PDC20268 +.It +Promise Ultra133 TX2 PDC20269 +.It +Promise FastTrak TX4 PDC20270 +.It +Promise FastTrak TX2000 PDC20271 +.It +Promise PDC20275 +.It +Promise PDC20276 +.It +Promise FastTrak TX2000 PDC20277 +.It +Promise Serial ATA TX4 PDC20318 +.It +Promise FastTrak S150 TX4 PDC20319 +.It +Promise FastTrak SATA RAID Controller PDC20371 +.It +Promise SATA150 TX2plus PDC20375 +.It +Promise PDC20376 +.It +Promise PDC20377 +.It +Promise PDC20378 +.It +Promise PDC20379 +.It +Promise TX2200 PDC20571 +.It +Promise SATA300 TX4 PDC20575 +.It +Promise PDC20579 +.It +Promise FastTrak TX2300 PDC20580 +.It +Promise PDC20617 +.It +Promise PDC20618 +.It +Promise PDC20619 +.It +Promise PDC20620 +.It +Promise sx4100 PDC20621 +.It +Promise PDC20622 +.It +Promise PDC40518 +.It +Promise TX42000 PDC40519 +.It +Promise TX4 SATA300 controller PDC40718 +.It +Promise PDC40719 +.It +ServerWorks HT1000 +.It +ServerWorks ROSB4 +.It +ServerWorks CSB5 +.It +ServerWorks CSB6 +.It +Silicon Image SiI0680 +.It +Silicon Image SiI3112 +.It +Silicon Image SiI3114 +.It +Silicon Image SiI3512 +.It +SiS SIS180 +.It +SiS SIS181 +.It +SiS SIS182 +.It +SiS SIS5513 +.It +SiS SIS530 +.It +SiS SIS540 +.It +SiS SIS550 +.It +SiS SIS620 +.It +SiS SIS630 +.It +SiS SIS630S +.It +SiS SIS633 +.It +SiS SIS635 +.It +SiS SIS730 +.It +SiS SIS733 +.It +SiS SIS735 +.It +SiS SIS745 +.It +SiS SIS961 +.It +SiS SIS962 +.It +SiS SIS963 +.It +SiS SIS964 +.It +SiS SIS965 +.It +VIA VT6410 +.It +VIA VT6420 +.It +VIA VT6421 +.It +VIA VT82C586 +.It +VIA VT82C586B +.It +VIA VT82C596 +.It +VIA VT82C596B +.It +VIA VT82C686 +.It +VIA VT82C686A +.It +VIA VT82C686B +.It +VIA VT8231 +.It +VIA VT8233 +.It +VIA VT8233A +.I +VIA VT8233C +.It +VIA VT8235 +.It +VIA VT8237 +.It +VIA VT8237A +.IT +VIA VT8251. .El .Pp Unknown ATA chipsets are supported in PIO modes, and if the standard busmaster DMA registers are present and contain valid setup, DMA is also enabled, although the max mode is limited to UDMA33, as it is not known what the chipset can do and how to program it. -.Pp +.Sh CONFIGURATION AND TUNING The .Nm driver can change the transfer mode and various other parameters @@ -202,7 +461,7 @@ Please remember that in order to use UDMA4/ATA66 and above modes you .Em must use 80 conductor cables. -Please assure that ribbon cables are no longer than 45cm. +Please assure that ribbon cables are no longer than 45cm/18in. In case of rounded ATA cables, the length depends on the quality of the cables. SATA cables can be up to 1m long according to the specification. @@ -216,7 +475,7 @@ This is useful in hotswap scenarios where disks should always show up as the same numbered device, and not depend on attach order. -.Pp +.Sh BUGS Native Command Queuing (NCQ) on SATA drives is not yet supported. .Sh SEE ALSO .Xr ataraid 4 , --------------060205000802070606020509-- From owner-freebsd-doc@FreeBSD.ORG Thu Dec 7 17:32:45 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5610E16A4FD for ; Thu, 7 Dec 2006 17:32:45 +0000 (UTC) (envelope-from www@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id D32BB43D6B for ; Thu, 7 Dec 2006 17:27:52 +0000 (GMT) (envelope-from www@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB7HSbks028624 for ; Thu, 7 Dec 2006 17:28:37 GMT (envelope-from www@www.freebsd.org) Received: (from www@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB7HSb6X028623 for freebsd-doc@FreeBSD.org; Thu, 7 Dec 2006 17:28:37 GMT (envelope-from www) Date: Thu, 7 Dec 2006 17:28:37 GMT From: World Wide Web Owner Message-Id: <200612071728.kB7HSb6X028623@www.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: Subject: FreeBSD web build failed on www.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 17:32:45 -0000 install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl82.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl83.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tcl84.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/textproc.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk80.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk82.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk83.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tk84.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/tkstep80.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/ukrainian.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/updating.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/vietnamese.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/windowmaker.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/www.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-clocks.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-fm.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-fonts.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-servers.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-themes.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-toolkits.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11-wm.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/x11.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/xfce.html /usr/local/www/www.freebsd.org/data/ports install -C -o www -g wwwadm -m 664 /w/www/build/www/en/ports/zope.html /usr/local/www/www.freebsd.org/data/ports ===> relnotes ===> relnotes/CURRENT/share/sgml ===> relnotes/CURRENT/en_US.ISO8859-1 ===> relnotes/CURRENT/en_US.ISO8859-1/relnotes install -c -o www -g wwwadm -m 444 article.html usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes. *** Error code 1 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1. *** Error code 1 Stop in /w/www/build/relnotes/doc. *** Error code 1 Stop in /w/www/build/www/en/relnotes. *** Error code 1 Stop in /w/www/build/www/en. 97.01 real 33.86 user 19.34 sys From owner-freebsd-doc@FreeBSD.ORG Fri Dec 8 01:03:37 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8B36216A403 for ; Fri, 8 Dec 2006 01:03:37 +0000 (UTC) (envelope-from nunoauboulot@aim.com) Received: from imo-m19.mx.aol.com (imo-m19.mx.aol.com [64.12.137.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 603E843CA3 for ; Fri, 8 Dec 2006 01:02:42 +0000 (GMT) (envelope-from nunoauboulot@aim.com) Received: from nunoauboulot@aim.com by imo-m19.mx.aol.com (mail_out_v38_r7.6.) id n.ce3.51a8a42 (57882) for ; Thu, 7 Dec 2006 20:03:31 -0500 (EST) Received: from MBLK-M06 (mblk-m06.mblk.aol.com [64.12.136.39]) by air-ia04.mail.aol.com (v114.2) with ESMTP id MAILINIA44-e21a4578b9e02ce; Thu, 07 Dec 2006 20:03:28 -0500 To: freebsd-doc@freebsd.org Content-Transfer-Encoding: 7bit Date: Thu, 07 Dec 2006 20:03:27 -0500 X-MB-Message-Source: WebUI MIME-Version: 1.0 From: nunoauboulot@aim.com X-MB-Message-Type: User Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailer: AIM WebMail 22250 Received: from 20.137.2.51 by MBLK-M06.sysops.aol.com (64.12.136.39) with HTTP (WebMailUI); Thu, 07 Dec 2006 20:03:27 -0500 Message-Id: <8C8E87BCDB33FDD-AC4-584C@MBLK-M06.sysops.aol.com> X-AOL-IP: 64.12.136.39 X-Spam-Flag: NO Subject: update on section 7.6.1 of the handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2006 01:03:37 -0000 May I suggest a review in that section as the hyperlink "supported devices" links to: http://sane-project.org/sane-supported-devices.html And the above page is re-directed to: http://alioth.debian.org/sane-supported-devices.html And there, we have a "PAGE NOT FOUND" being displayed. Thanks ________________________________________________________________________ Check Out the new free AIM(R) Mail -- 2 GB of storage and industry-leading spam and email virus protection. From owner-freebsd-doc@FreeBSD.ORG Fri Dec 8 07:29:43 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C541F16A40F for ; Fri, 8 Dec 2006 07:29:43 +0000 (UTC) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (blackend.org [212.11.35.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE4EB43CA2 for ; Fri, 8 Dec 2006 07:28:46 +0000 (GMT) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (localhost [127.0.0.1]) by abigail.blackend.org (8.13.4/8.13.3) with ESMTP id kB87TbvP038875; Fri, 8 Dec 2006 08:29:37 +0100 (CET) (envelope-from marc@abigail.blackend.org) Received: (from marc@localhost) by abigail.blackend.org (8.13.4/8.13.3/Submit) id kB87TbVn038874; Fri, 8 Dec 2006 08:29:37 +0100 (CET) (envelope-from marc) Date: Fri, 8 Dec 2006 08:29:36 +0100 From: Marc Fonvieille To: nunoauboulot@aim.com Message-ID: <20061208072936.GA38794@abigail.blackend.org> Mail-Followup-To: nunoauboulot@aim.com, freebsd-doc@freebsd.org References: <8C8E87BCDB33FDD-AC4-584C@MBLK-M06.sysops.aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8C8E87BCDB33FDD-AC4-584C@MBLK-M06.sysops.aol.com> X-Useless-Header: blackend.org X-Operating-System: FreeBSD 4.11-STABLE User-Agent: Mutt/1.5.9i Cc: freebsd-doc@freebsd.org Subject: Re: update on section 7.6.1 of the handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2006 07:29:43 -0000 On Thu, Dec 07, 2006 at 08:03:27PM -0500, nunoauboulot@aim.com wrote: > May I suggest a review in that section as the hyperlink > "supported devices" links to: > http://sane-project.org/sane-supported-devices.html > [...] Now, it's http://www.sane-project.org/sane-supported-devices.html I just fixed the page, the change should appear after next web site build. Thanks for the report. -- Marc From owner-freebsd-doc@FreeBSD.ORG Fri Dec 8 16:38:24 2006 Return-Path: X-Original-To: doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 656B816A49E; Fri, 8 Dec 2006 16:38:24 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (vlsi00.si.noda.tus.ac.jp [133.31.130.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ECD743CA5; Fri, 8 Dec 2006 16:37:24 +0000 (GMT) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p3098-ipbf401funabasi.chiba.ocn.ne.jp [124.86.53.98]) (authenticated bits=128) by mail.allbsd.org (8.13.1/8.13.4) with ESMTP id kB8GcAA8038302; Sat, 9 Dec 2006 01:38:21 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id kB8Gbkfb003646; Sat, 9 Dec 2006 01:37:47 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sat, 09 Dec 2006 01:36:25 +0900 (JST) Message-Id: <20061209.013625.74532875.hrs@allbsd.org> To: doc@FreeBSD.org From: Hiroki Sato X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 5.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Sat_Dec__9_01_36_25_2006_525)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.allbsd.org [133.31.130.32]); Sat, 09 Dec 2006 01:38:21 +0900 (JST) Cc: doceng@FreeBSD.org, developers@FreeBSD.org Subject: HEADS UP: doc tree tagging being done for 6.2R X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2006 16:38:24 -0000 ----Security_Multipart(Sat_Dec__9_01_36_25_2006_525)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, I am sorry for the short notice, but doc tree tagging for 6.2R has been done *tentatively*. The release schedule was delayed and I originally thought the tagging should be done just before (or after) the final release candidate, so I could not announce the date in good time. I apologize I did not handle it well this time. As I wrote above, the tag has been laid down but it has not been fixed yet. If you have (or commit) changes you want to put into the release, please let me know. I will do a test and slip the tag. However, please slow down the rate of change for the English documents in the tree this weekend, to allow the translation teams time to catch up with the latest English documents. Thank you for your cooperation and keep up the good work! -- | Hiroki SATO ----Security_Multipart(Sat_Dec__9_01_36_25_2006_525)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBFeZSMTyzT2CeTzy0RAiWkAKCZ73ncwdQf5WMSakwy5fV2qz+0swCgqLt0 0I2HCBkNbeWa15grYAIEdNQ= =4u2p -----END PGP SIGNATURE----- ----Security_Multipart(Sat_Dec__9_01_36_25_2006_525)---- From owner-freebsd-doc@FreeBSD.ORG Fri Dec 8 16:43:54 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88F9F16A417; Fri, 8 Dec 2006 16:43:54 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 956F843C9D; Fri, 8 Dec 2006 16:42:55 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB8Ghs2K001048; Fri, 8 Dec 2006 16:43:54 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB8GhrfG001044; Fri, 8 Dec 2006 16:43:53 GMT (envelope-from ceri) Date: Fri, 8 Dec 2006 16:43:53 GMT From: Ceri Davies Message-Id: <200612081643.kB8GhrfG001044@freefall.freebsd.org> To: dieter@sopwith.solgatos.com, ceri@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: Subject: Re: docs/106320: ata(4) man page should have HARDWARE section X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2006 16:43:54 -0000 Synopsis: ata(4) man page should have HARDWARE section State-Changed-From-To: open->closed State-Changed-By: ceri State-Changed-When: Fri Dec 8 16:43:39 UTC 2006 State-Changed-Why: Being followed up in docs/106320. http://www.freebsd.org/cgi/query-pr.cgi?pr=106320 From owner-freebsd-doc@FreeBSD.ORG Fri Dec 8 19:36:26 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DBBA316A40F; Fri, 8 Dec 2006 19:36:26 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from pne-smtpout2-sn2.hy.skanova.net (pne-smtpout2-sn2.hy.skanova.net [81.228.8.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92A5443CAF; Fri, 8 Dec 2006 19:35:24 +0000 (GMT) (envelope-from niclas.zeising@gmail.com) Received: from [90.224.59.97] (90.224.59.97) by pne-smtpout2-sn2.hy.skanova.net (7.2.075) id 452BAB4100C75B2D; Fri, 8 Dec 2006 20:36:22 +0100 Message-ID: <4579BE99.2060208@gmail.com> Date: Fri, 08 Dec 2006 20:35:53 +0100 From: Niclas Zeising User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Ceri Davies References: <200612081643.kB8GhrfG001044@freefall.freebsd.org> In-Reply-To: <200612081643.kB8GhrfG001044@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org, dieter@sopwith.solgatos.com Subject: Re: docs/106320: ata(4) man page should have HARDWARE section X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2006 19:36:26 -0000 Ceri Davies wrote: > Synopsis: ata(4) man page should have HARDWARE section > > State-Changed-From-To: open->closed > State-Changed-By: ceri > State-Changed-When: Fri Dec 8 16:43:39 UTC 2006 > State-Changed-Why: > Being followed up in docs/106320. ^^^^^^^^^^^^ You are sure you don't mean that it will be followed up in pr docs/106425, since you just closed docs/106320? //Niclas -- From owner-freebsd-doc@FreeBSD.ORG Fri Dec 8 20:10:09 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A49F16A412 for ; Fri, 8 Dec 2006 20:10:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2DC643CA3 for ; Fri, 8 Dec 2006 20:09:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB8KA8mf020571 for ; Fri, 8 Dec 2006 20:10:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB8KA8jj020570; Fri, 8 Dec 2006 20:10:08 GMT (envelope-from gnats) Resent-Date: Fri, 8 Dec 2006 20:10:08 GMT Resent-Message-Id: <200612082010.kB8KA8jj020570@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Niclas Zeising Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A1ED16A416 for ; Fri, 8 Dec 2006 20:07:06 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5367E43CA7 for ; Fri, 8 Dec 2006 20:06:06 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kB8K75F1013645 for ; Fri, 8 Dec 2006 20:07:05 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kB8K75LG013644; Fri, 8 Dec 2006 20:07:05 GMT (envelope-from nobody) Message-Id: <200612082007.kB8K75LG013644@www.freebsd.org> Date: Fri, 8 Dec 2006 20:07:05 GMT From: Niclas Zeising To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: docs/106494: [patch] add a note regarding the status of the "security profile" setting in sysinstall X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2006 20:10:09 -0000 >Number: 106494 >Category: docs >Synopsis: [patch] add a note regarding the status of the "security profile" setting in sysinstall >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 Dec 08 20:10:07 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Niclas Zeising >Release: 7-CURRENT >Organization: >Environment: >Description: The security profile option in sysinstall which used to pop up during install is no more. Update docs accordingly, adding a note saying that the option is gone. Maybe we can delete the whole section, the option has been gone since 5.2 Note: The whole install chapter probably needs a facelift. >How-To-Repeat: Read the install chapter of the handbook. >Fix: The attached patch adds a note saying that the security option is no more. Patch attached with submission follows: --- doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml.orig 2006-12-08 19:46:36.000000000 +0100 +++ doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml 2006-12-08 19:59:49.000000000 +0100 @@ -2653,6 +2653,12 @@ Security Profile + + The security profile setting in sysinstall + has been deprecated and does not exist in &os; versions after 5.2. + + + A security profile is a set of configuration options that attempts to achieve the desired ratio of security to convenience by enabling and disabling >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sat Dec 9 13:40:13 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C734116A415 for ; Sat, 9 Dec 2006 13:40:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34D1643CA1 for ; Sat, 9 Dec 2006 13:39:09 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB9DeD2v031962 for ; Sat, 9 Dec 2006 13:40:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB9DeDPe031959; Sat, 9 Dec 2006 13:40:13 GMT (envelope-from gnats) Date: Sat, 9 Dec 2006 13:40:13 GMT Message-Id: <200612091340.kB9DeDPe031959@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Simon L. Nielsen" Cc: Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Simon L. Nielsen" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 13:40:13 -0000 The following reply was made to PR docs/106425; it has been noted by GNATS. From: "Simon L. Nielsen" To: Niclas Zeising Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) Date: Sat, 9 Dec 2006 14:31:10 +0100 On 2006.12.07 18:04:23 +0100, Niclas Zeising wrote: > And, as promised, the correct patch. I apologize for the confusion, I > attached the wrong file yesterday night. > //Niclas > --- src/share/man/man4/ata.4.orig 2006-12-06 19:56:35.000000000 +0100 > +++ src/share/man/man4/ata.4 2006-12-06 22:03:04.000000000 +0100 > @@ -98,55 +98,314 @@ [cut] Just for historic info... I didn't commit my change to add a HARDWARE section for ata(4), though I did do the conversion, since it just didn't see that useful to list chipsets in the Hardware notes. I'm not against adding a hardware section, that just why there isn't one today. Anyway, if this is to be committed it should be OK'ed by sos@ IMO. -- Simon L. Nielsen From owner-freebsd-doc@FreeBSD.ORG Sat Dec 9 13:40:19 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1504216A52B for ; Sat, 9 Dec 2006 13:40:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A02F43C9E for ; Sat, 9 Dec 2006 13:39:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB9DeHn1032013 for ; Sat, 9 Dec 2006 13:40:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB9DeHl9032012; Sat, 9 Dec 2006 13:40:17 GMT (envelope-from gnats) Date: Sat, 9 Dec 2006 13:40:17 GMT Message-Id: <200612091340.kB9DeHl9032012@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Simon L. Nielsen" Cc: Subject: Re: docs/106494: [patch] add a note regarding the status of the "security profile" setting in sysinstall X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Simon L. Nielsen" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 13:40:19 -0000 The following reply was made to PR docs/106494; it has been noted by GNATS. From: "Simon L. Nielsen" To: Niclas Zeising Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/106494: [patch] add a note regarding the status of the "security profile" setting in sysinstall Date: Sat, 9 Dec 2006 14:32:47 +0100 On 2006.12.08 20:07:05 +0000, Niclas Zeising wrote: > The security profile option in sysinstall which used to pop up > during install is no more. Update docs accordingly, adding a note > saying that the option is gone. > > Maybe we can delete the whole section, the option has been gone since 5.2 I think it would be better to delete it - the handbook doesn't document that old releases. > Note: The whole install chapter probably needs a facelift. That sounds likely. -- Simon L. Nielsen From owner-freebsd-doc@FreeBSD.ORG Sat Dec 9 14:10:11 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 47E6C16A407 for ; Sat, 9 Dec 2006 14:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EBC043CA1 for ; Sat, 9 Dec 2006 14:09:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB9EAA3c034095 for ; Sat, 9 Dec 2006 14:10:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB9EAAj7034092; Sat, 9 Dec 2006 14:10:10 GMT (envelope-from gnats) Date: Sat, 9 Dec 2006 14:10:10 GMT Message-Id: <200612091410.kB9EAAj7034092@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Niclas Zeising Cc: Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Niclas Zeising List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 14:10:11 -0000 The following reply was made to PR docs/106425; it has been noted by GNATS. From: Niclas Zeising To: "Simon L. Nielsen" Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/106425: [PATCH] add a HARDWARE-section to ata(4) Date: Sat, 09 Dec 2006 15:00:56 +0100 Simon L. Nielsen wrote: > On 2006.12.07 18:04:23 +0100, Niclas Zeising wrote: > >> And, as promised, the correct patch. I apologize for the confusion, I >> attached the wrong file yesterday night. >> //Niclas > >> --- src/share/man/man4/ata.4.orig 2006-12-06 19:56:35.000000000 +0100 >> +++ src/share/man/man4/ata.4 2006-12-06 22:03:04.000000000 +0100 >> @@ -98,55 +98,314 @@ > > [cut] > > Just for historic info... I didn't commit my change to add a HARDWARE > section for ata(4), though I did do the conversion, since it just > didn't see that useful to list chipsets in the Hardware notes. I'm > not against adding a hardware section, that just why there isn't one > today. Okay, I didn't look through the archives to see if anyone already done the work once. I just noticed the section missing when someone filed a PR about no devices supported by ata(4) was present in the hardware notes. I am also not sure if I really like the long list that I've made in the hardware section, I just didn't know a better way to do it and get them generated properly in the hardware notes. Maybe we should just add the list manually in the hardware notes. I think we should have the supported chipsets listed somewhere though, so you know what piece of hardware you should buy. > > Anyway, if this is to be committed it should be OK'ed by sos@ IMO. > That sounds reasonable. Regards! //Niclas From owner-freebsd-doc@FreeBSD.ORG Sat Dec 9 14:20:16 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A34A16A415 for ; Sat, 9 Dec 2006 14:20:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2666143CA0 for ; Sat, 9 Dec 2006 14:19:04 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB9EK8tC035000 for ; Sat, 9 Dec 2006 14:20:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB9EK8eO034993; Sat, 9 Dec 2006 14:20:08 GMT (envelope-from gnats) Date: Sat, 9 Dec 2006 14:20:08 GMT Message-Id: <200612091420.kB9EK8eO034993@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Niclas Zeising Cc: Subject: Re: docs/106494: [patch] add a note regarding the status of the "security profile" setting in sysinstall X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Niclas Zeising List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 14:20:16 -0000 The following reply was made to PR docs/106494; it has been noted by GNATS. From: Niclas Zeising To: "Simon L. Nielsen" Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/106494: [patch] add a note regarding the status of the "security profile" setting in sysinstall Date: Sat, 09 Dec 2006 15:09:51 +0100 This is a multi-part message in MIME format. --------------000405050905060004040600 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Simon L. Nielsen wrote: > On 2006.12.08 20:07:05 +0000, Niclas Zeising wrote: > >> The security profile option in sysinstall which used to pop up >> during install is no more. Update docs accordingly, adding a note >> saying that the option is gone. >> >> Maybe we can delete the whole section, the option has been gone since 5.2 > > I think it would be better to delete it - the handbook doesn't > document that old releases. I thought so, wasn't 100% sure so i added the note instead. Attached is a patch that removes the section entirely instead. > >> Note: The whole install chapter probably needs a facelift. > > That sounds likely. > It will take some thinking through, and new screen shots i think. But we need a decent install chapter, so people know how to install FreeBSD. Regards! //Niclas --------------000405050905060004040600 Content-Type: text/plain; name="install.chapter.sgml.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="install.chapter.sgml.diff" --- doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml.orig 2006-12-08 19:46:36.000000000 +0100 +++ doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml 2006-12-09 15:04:18.000000000 +0100 @@ -2650,184 +2650,6 @@ - - Security Profile - - A security profile is a set of - configuration options that attempts to achieve the desired - ratio of security to convenience by enabling and disabling - certain programs and other settings. The more severe the - security profile, the fewer programs will be enabled by - default. This is one of the basic principles of security: do - not run anything except what you must. - - Please note that the security profile is just a default - setting. All programs can be enabled and disabled after you - have installed FreeBSD by editing or adding the appropriate - line(s) to /etc/rc.conf. For more - information, please see the &man.rc.conf.5; manual - page. - - The following table describes what each of the security - profiles does. The columns are the choices you have for a - security profile, and the rows are the program or feature that - the profile enables or disables. - - - Possible Security Profiles - - - - - - - Extreme - - Moderate - - - - - - - &man.sendmail.8; - - NO - - YES - - - - &man.sshd.8; - - NO - - YES - - - - &man.portmap.8; - - NO - - MAYBE - - The portmapper is enabled if the machine has - been configured as an NFS client or server earlier - in the installation. - - - - - - NFS server - - NO - - YES - - - - &man.securelevel.8; - - YES - - If you choose a security profile that sets the - securelevel to Extreme or - High, you must be aware of the - implications. Please read the &man.init.8; - manual page and pay particular attention to the - meanings of the security levels, or you may have - significant trouble later! - - - - NO - - - -
- - User Confirmation Requested - Do you want to select a default security profile for this host (select - No for "medium" security)? - - [ Yes ] No - - Selecting &gui.no; and pressing - Enter will set the security profile to medium. - - Selecting &gui.yes; and pressing - Enter will allow selecting a different security - profile. - -
- Security Profile Options - - - - - - -
- - Press F1 to display the help. Press - Enter to return to selection menu. - - Use the arrow keys to choose Medium - unless your are sure that another level is required for your needs. - With &gui.ok; highlighted, press - Enter. - - An appropriate confirmation message will display depending on - which security setting was chosen. - - Message - -Moderate security settings have been selected. - -Sendmail and SSHd have been enabled, securelevels are -disabled, and NFS server setting have been left intact. -PLEASE NOTE that this still does not save you from having -to properly secure your system in other ways or exercise -due diligence in your administration, this simply picks -a standard set of out-of-box defaults to start with. - -To change any of these settings later, edit /etc/rc.conf - - [OK] - - Message - -Extreme security settings have been selected. - -Sendmail, SSHd, and NFS services have been disabled, and -securelevels have been enabled. -PLEASE NOTE that this still does not save you from having -to properly secure your system in other ways or exercise -due diligence in your administration, this simply picks -a more secure set of out-of-box defaults to start with. - -To change any of these settings later, edit /etc/rc.conf - - [OK] - - Press Enter to continue with the - post-installation configuration. - - - The security profile is not a silver bullet! Even if - you use the extreme setting, you need to keep up with - security issues by reading an appropriate mailing - list (), - using good passwords and passphrases, and - generally adhering to good security practices. It simply - sets up the desired security to convenience ratio out of the - box. - - - - System Console Settings --------------000405050905060004040600-- From owner-freebsd-doc@FreeBSD.ORG Sat Dec 9 18:41:20 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9762516A40F for ; Sat, 9 Dec 2006 18:41:20 +0000 (UTC) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-0-0-cust107.cdif.cable.ntl.com [81.104.168.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id B051743C9F for ; Sat, 9 Dec 2006 18:40:14 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Gt78N-000Kf2-Tx; Sat, 09 Dec 2006 18:41:15 +0000 Date: Sat, 9 Dec 2006 18:41:15 +0000 From: Ceri Davies To: Niclas Zeising Message-ID: <20061209184115.GO86282@submonkey.net> Mail-Followup-To: Ceri Davies , Niclas Zeising , dieter@sopwith.solgatos.com, freebsd-doc@FreeBSD.org References: <200612081643.kB8GhrfG001044@freefall.freebsd.org> <4579BE99.2060208@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x1F0m3RQhDZyj8sd" Content-Disposition: inline In-Reply-To: <4579BE99.2060208@gmail.com> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Ceri Davies Cc: freebsd-doc@FreeBSD.org, dieter@sopwith.solgatos.com Subject: Re: docs/106320: ata(4) man page should have HARDWARE section X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 18:41:20 -0000 --x1F0m3RQhDZyj8sd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 08, 2006 at 08:35:53PM +0100, Niclas Zeising wrote: > Ceri Davies wrote: > >Synopsis: ata(4) man page should have HARDWARE section > > > >State-Changed-From-To: open->closed > >State-Changed-By: ceri > >State-Changed-When: Fri Dec 8 16:43:39 UTC 2006 > >State-Changed-Why:=20 > >Being followed up in docs/106320. > ^^^^^^^^^^^^ > > You are sure you don't mean that it will be followed up in pr=20 > docs/106425, since you just closed docs/106320? > That's what you get for creating a new PR instead of following up to the original ;-p Ceri --=20 That must be wonderful! I don't understand it at all. -- Moliere --x1F0m3RQhDZyj8sd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFewNLocfcwTS3JF8RAqvlAJ4r4eh4c9T+rXHlKfTmjiR2DmC3nACgyYa4 c6AsfI/qVY8NFNpTvHtcgCg= =lPjq -----END PGP SIGNATURE----- --x1F0m3RQhDZyj8sd-- From owner-freebsd-doc@FreeBSD.ORG Sat Dec 9 18:41:46 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DBAB716A597; Sat, 9 Dec 2006 18:41:46 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEDA643C9E; Sat, 9 Dec 2006 18:40:40 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB9Ifka6062032; Sat, 9 Dec 2006 18:41:46 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB9IfkJN062028; Sat, 9 Dec 2006 18:41:46 GMT (envelope-from ceri) Date: Sat, 9 Dec 2006 18:41:46 GMT From: Ceri Davies Message-Id: <200612091841.kB9IfkJN062028@freefall.freebsd.org> To: dieter@sopwith.solgatos.com, ceri@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: Subject: Re: docs/106320: ata(4) man page should have HARDWARE section X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 18:41:47 -0000 Synopsis: ata(4) man page should have HARDWARE section State-Changed-From-To: closed->open State-Changed-By: ceri State-Changed-When: Sat Dec 9 18:41:24 UTC 2006 State-Changed-Why: Bah, re-open this for a second. http://www.freebsd.org/cgi/query-pr.cgi?pr=106320 From owner-freebsd-doc@FreeBSD.ORG Sat Dec 9 18:42:05 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D58B216A49E; Sat, 9 Dec 2006 18:42:05 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A63243C9E; Sat, 9 Dec 2006 18:41:00 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB9Ig5gf062101; Sat, 9 Dec 2006 18:42:05 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB9Ig5qo062097; Sat, 9 Dec 2006 18:42:05 GMT (envelope-from ceri) Date: Sat, 9 Dec 2006 18:42:05 GMT From: Ceri Davies Message-Id: <200612091842.kB9Ig5qo062097@freefall.freebsd.org> To: dieter@sopwith.solgatos.com, ceri@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: Subject: Re: docs/106320: ata(4) man page should have HARDWARE section X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 18:42:05 -0000 Synopsis: ata(4) man page should have HARDWARE section State-Changed-From-To: open->closed State-Changed-By: ceri State-Changed-When: Sat Dec 9 18:41:51 UTC 2006 State-Changed-Why: Being followed up in docs/106425, duh. http://www.freebsd.org/cgi/query-pr.cgi?pr=106320