From owner-freebsd-doc@FreeBSD.ORG Sun Dec 14 04:50:01 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EF431065675 for ; Sun, 14 Dec 2008 04:50:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 339C88FC18 for ; Sun, 14 Dec 2008 04:50:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBE4o1Pb078175 for ; Sun, 14 Dec 2008 04:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBE4o1R0078174; Sun, 14 Dec 2008 04:50:01 GMT (envelope-from gnats) Resent-Date: Sun, 14 Dec 2008 04:50:01 GMT Resent-Message-Id: <200812140450.mBE4o1R0078174@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, Ben Kaduk Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E28581065673 for ; Sun, 14 Dec 2008 04:49:41 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id D26C18FC1E for ; Sun, 14 Dec 2008 04:49:41 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id mBE4nfUf087004 for ; Sun, 14 Dec 2008 04:49:41 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id mBE4nf2R087003; Sun, 14 Dec 2008 04:49:41 GMT (envelope-from nobody) Message-Id: <200812140449.mBE4nf2R087003@www.freebsd.org> Date: Sun, 14 Dec 2008 04:49:41 GMT From: Ben Kaduk To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/129623: suser(9) claims that the interface is still exported, though deprecated 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, 14 Dec 2008 04:50:01 -0000 >Number: 129623 >Category: docs >Synopsis: suser(9) claims that the interface is still exported, though deprecated >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Dec 14 04:50:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Ben Kaduk >Release: 8-current >Organization: MIT SIPB >Environment: pleonasm# uname -a FreeBSD pleonasm.mit.edu 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Fri Dec 12 18:37:53 UTC 2008 kaduk@pleonasm.mit.edu:/usr/obj/usr/src/sys/PLEONASM i386 >Description: compare the contents of suser(9) and /usr/include/sys/priv.h ... the latter no longer has the definition of the function. It's not clear to me if the man page for suser(9) should just be removed, or retained as a pointer to priv_check(9). >How-To-Repeat: Try to compile a module that uses suser, and get "No such file or directory" when trying to load it. >Fix: Remove the suser(9) manpage? >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sun Dec 14 05:46:06 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A87E106568A for ; Sun, 14 Dec 2008 05:46:06 +0000 (UTC) (envelope-from murray@stokely.org) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.178]) by mx1.freebsd.org (Postfix) with ESMTP id 0A8468FC2F for ; Sun, 14 Dec 2008 05:46:05 +0000 (UTC) (envelope-from murray@stokely.org) Received: by ik-out-1112.google.com with SMTP id c21so560827ika.3 for ; Sat, 13 Dec 2008 21:46:04 -0800 (PST) Received: by 10.210.116.14 with SMTP id o14mr6238833ebc.90.1229233564516; Sat, 13 Dec 2008 21:46:04 -0800 (PST) Received: by 10.210.71.14 with HTTP; Sat, 13 Dec 2008 21:46:04 -0800 (PST) Message-ID: <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> Date: Sat, 13 Dec 2008 21:46:04 -0800 From: "Murray Stokely" To: "Tom Rhodes" In-Reply-To: <20081113185333.25a73ebf.trhodes@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> Cc: freebsd-doc@freebsd.org Subject: Re: Preface need update. 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, 14 Dec 2008 05:46:06 -0000 Hi Tom, I've just committed a new section to the preface with pointers to the Filesystems and DTrace chapters you committed, and also the Virtualization chapter I committed in 2007. There are others (e.g. updating) but I wasn't sure if some of that content was moved from other chapters (cutting edge?) as if so we'd want to mention that in the preface item for that new chapter. Please take a look when you get a chance and add a few more items to this section about some of the work you've done recently. We presumably also need something about the security event auditing chapter. Thanks, - Murray On Thu, Nov 13, 2008 at 3:53 PM, Tom Rhodes wrote: > On Thu, 13 Nov 2008 16:29:59 +0200 > Manolis Kiagias wrote: > >> Tom Rhodes wrote: >> > On Wed, 12 Nov 2008 16:05:55 -0800 >> > "Murray Stokely" wrote: >> > >> > >> >> Thanks Manolis. Maybe we should add a comment to the Makefile so that >> >> when authors commit new chapters they remember to also update the >> >> preface summary. Or alternatively, we could put some kind of one >> >> sentence chapter description in of each chapter and pull >> >> it out of each file dynamically when building the preface. I'd >> >> probably recommend the low tech first suggestion as good enough. >> >> >> >> - Murray >> >> >> > >> > Yea, because I forget this every time I add a new chapter. :( >> > >> > >> > >> To take this idea one step further, I suggest we add the following >> comment to the Makefile: >> >> ----------------------------------------------------------------------------------------------------------------- >> To add a new chapter to the Handbook: >> >> - Update this Makefile, chapters.ent and book.sgml >> - Add a descriptive entry for the new chapter in preface/preface.sgml >> ----------------------------------------------------------------------------------------------------------------- >> >> Do you think this is good enough? > > Yes. And I need to look at the "changes since the third > edition" data as well. :) > > -- > Tom Rhodes > From owner-freebsd-doc@FreeBSD.ORG Sun Dec 14 05:50:04 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91623106564A for ; Sun, 14 Dec 2008 05:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 80ECE8FC19 for ; Sun, 14 Dec 2008 05:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBE5o3Rt029743 for ; Sun, 14 Dec 2008 05:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBE5o3Ya029742; Sun, 14 Dec 2008 05:50:03 GMT (envelope-from gnats) Date: Sun, 14 Dec 2008 05:50:03 GMT Message-Id: <200812140550.mBE5o3Ya029742@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Ganbold Cc: Subject: Re: docs/129623: suser(9) claims that the interface is still exported, though deprecated X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ganbold List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 05:50:04 -0000 The following reply was made to PR docs/129623; it has been noted by GNATS. From: Ganbold To: Ben Kaduk Cc: bug-followup@FreeBSD.org Subject: Re: docs/129623: suser(9) claims that the interface is still exported, though deprecated Date: Sun, 14 Dec 2008 13:01:21 +0800 Ben Kaduk wrote: -- A person forgives only when they are in the wrong. >> Number: 129623 >> Category: docs >> Synopsis: suser(9) claims that the interface is still exported, though deprecated >> Confidential: no >> Severity: non-critical >> Priority: low >> Responsible: freebsd-doc >> State: open >> Quarter: >> Keywords: >> Date-Required: >> Class: doc-bug >> Submitter-Id: current-users >> Arrival-Date: Sun Dec 14 04:50:00 UTC 2008 >> Closed-Date: >> Last-Modified: >> Originator: Ben Kaduk >> Release: 8-current >> Organization: >> > MIT SIPB > >> Environment: >> > pleonasm# uname -a > FreeBSD pleonasm.mit.edu 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Fri Dec 12 18:37:53 UTC 2008 kaduk@pleonasm.mit.edu:/usr/obj/usr/src/sys/PLEONASM i386 > > >> Description: >> > compare the contents of suser(9) and /usr/include/sys/priv.h ... > the latter no longer has the definition of the function. > > It's not clear to me if the man page for suser(9) should just > be removed, or retained as a pointer to priv_check(9). > >> How-To-Repeat: >> > Try to compile a module that uses suser, and get "No such file or directory" when trying to load it. > >> Fix: >> > Remove the suser(9) manpage? > I don't see suser(9) man page in my CURRENT (FreeBSD devil.micom.mng.net 8.0-CURRENT FreeBSD 8.0-CURRENT #13 r185928: Thu Dec 11 21:12:36 ULAT 2008), but I see it in RELENG_7. Are you sure that it is in CURRENT not a leftover from RELENG_X? thanks, Ganbold > >> Release-Note: >> Audit-Trail: >> Unformatted: >> > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > > > From owner-freebsd-doc@FreeBSD.ORG Sun Dec 14 14:20:07 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A68D1065676 for ; Sun, 14 Dec 2008 14:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 289698FC14 for ; Sun, 14 Dec 2008 14:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBEEK783062723 for ; Sun, 14 Dec 2008 14:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBEEK6dV062722; Sun, 14 Dec 2008 14:20:06 GMT (envelope-from gnats) Date: Sun, 14 Dec 2008 14:20:06 GMT Message-Id: <200812141420.mBEEK6dV062722@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Ben Kaduk" Cc: Subject: Re: docs/129623: suser(9) claims that the interface is still exported, though deprecated X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ben Kaduk List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 14:20:07 -0000 The following reply was made to PR docs/129623; it has been noted by GNATS. From: "Ben Kaduk" To: Ganbold Cc: bug-followup@freebsd.org Subject: Re: docs/129623: suser(9) claims that the interface is still exported, though deprecated Date: Sun, 14 Dec 2008 08:52:52 -0500 On Sun, Dec 14, 2008 at 12:01 AM, Ganbold wrote: > Ben Kaduk wrote: > -- > A person forgives only when they are in the wrong. >>> Number: 129623 >>> Category: docs >>> Synopsis: suser(9) claims that the interface is still exported, though deprecated >>> Confidential: no >>> Severity: non-critical >>> Priority: low >>> Responsible: freebsd-doc >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: doc-bug >>> Submitter-Id: current-users >>> Arrival-Date: Sun Dec 14 04:50:00 UTC 2008 >>> Closed-Date: >>> Last-Modified: >>> Originator: Ben Kaduk >>> Release: 8-current >>> Organization: >>> >> MIT SIPB >> >>> Environment: >>> >> pleonasm# uname -a >> FreeBSD pleonasm.mit.edu 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Fri Dec 12 18:37:53 UTC 2008 kaduk@pleonasm.mit.edu:/usr/obj/usr/src/sys/PLEONASM i386 >> >> >>> Description: >>> >> compare the contents of suser(9) and /usr/include/sys/priv.h ... >> the latter no longer has the definition of the function. >> >> It's not clear to me if the man page for suser(9) should just >> be removed, or retained as a pointer to priv_check(9). >> >>> How-To-Repeat: >>> >> Try to compile a module that uses suser, and get "No such file or directory" when trying to load it. >> >>> Fix: >>> >> Remove the suser(9) manpage? >> > > I don't see suser(9) man page in my CURRENT (FreeBSD devil.micom.mng.net > 8.0-CURRENT FreeBSD 8.0-CURRENT #13 r185928: Thu Dec 11 21:12:36 ULAT > 2008), but I see it in RELENG_7. > Are you sure that it is in CURRENT not a leftover from RELENG_X? > > thanks, > Ah, yes, it would be a leftover ... this is an old box. Sorry for the noise. -Ben From owner-freebsd-doc@FreeBSD.ORG Sun Dec 14 19:32:46 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2047D1065677; Sun, 14 Dec 2008 19:32:46 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E91048FC19; Sun, 14 Dec 2008 19:32:45 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBEJWjFj011564; Sun, 14 Dec 2008 19:32:45 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBEJWjb7011560; Sun, 14 Dec 2008 19:32:45 GMT (envelope-from linimon) Date: Sun, 14 Dec 2008 19:32:45 GMT Message-Id: <200812141932.mBEJWjb7011560@freefall.freebsd.org> To: minimarmot@gmail.com, linimon@FreeBSD.org, freebsd-doc@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: docs/129623: suser(9) claims that the interface is still exported, though deprecated 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, 14 Dec 2008 19:32:46 -0000 Synopsis: suser(9) claims that the interface is still exported, though deprecated State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun Dec 14 19:32:02 UTC 2008 State-Changed-Why: Closed at submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=129623 From owner-freebsd-doc@FreeBSD.ORG Sun Dec 14 23:51:06 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1B76106567D for ; Sun, 14 Dec 2008 23:51:05 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 9D1AE8FC1A for ; Sun, 14 Dec 2008 23:51:05 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (c-68-83-213-214.hsd1.va.comcast.net [68.83.213.214]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBENp4oX024651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 14 Dec 2008 18:51:04 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Sun, 14 Dec 2008 18:50:58 -0500 From: Tom Rhodes To: "Murray Stokely" Message-Id: <20081214185058.48a7c2c2.trhodes@FreeBSD.org> In-Reply-To: <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org Subject: Re: Preface need update. 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, 14 Dec 2008 23:51:06 -0000 Hi Murray, On Sat, 13 Dec 2008 21:46:04 -0800 "Murray Stokely" wrote: > Hi Tom, I've just committed a new section to the preface with pointers > to the Filesystems and DTrace chapters you committed, and also the > Virtualization chapter I committed in 2007. There are others (e.g. > updating) but I wasn't sure if some of that content was moved from > other chapters (cutting edge?) as if so we'd want to mention that in > the preface item for that new chapter. Please take a look when you > get a chance and add a few more items to this section about some of > the work you've done recently. > > We presumably also need something about the security event auditing chapter. Thanks for that! I definitely slacked here, but I'll keep this in mind for the future. About the updating chapter, I am unable to find any information on portsnap in my printed copy of the Handbook (third edition). They could have existed (I see a 2006 commit date for freebsd-update in src) but seem to have not been documented in the handbook. Anyway, how does this patch look to you?: diff -u -r1.44 preface.sgml --- preface.sgml 14 Dec 2008 05:42:48 -0000 1.44 +++ preface.sgml 14 Dec 2008 23:45:05 -0000 @@ -47,6 +47,19 @@ + , Updating, has been added to + cover various methods of keeping the system up to date with + the latest in security patches and changes in the Ports + Collection. + + + + , Security Event Auditing, has + been added to cover the new auditing capabilities in &os; + and explain its use. + + + , Virtualization, has been added with information about installing &os; on virtualization software. Thanks, > > Thanks, > > - Murray > > On Thu, Nov 13, 2008 at 3:53 PM, Tom Rhodes wrote: > > On Thu, 13 Nov 2008 16:29:59 +0200 > > Manolis Kiagias wrote: > > > >> Tom Rhodes wrote: > >> > On Wed, 12 Nov 2008 16:05:55 -0800 > >> > "Murray Stokely" wrote: > >> > > >> > > >> >> Thanks Manolis. Maybe we should add a comment to the Makefile so that > >> >> when authors commit new chapters they remember to also update the > >> >> preface summary. Or alternatively, we could put some kind of one > >> >> sentence chapter description in of each chapter and pull > >> >> it out of each file dynamically when building the preface. I'd > >> >> probably recommend the low tech first suggestion as good enough. > >> >> > >> >> - Murray > >> >> > >> > > >> > Yea, because I forget this every time I add a new chapter. :( > >> > > >> > > >> > > >> To take this idea one step further, I suggest we add the following > >> comment to the Makefile: > >> > >> ----------------------------------------------------------------------------------------------------------------- > >> To add a new chapter to the Handbook: > >> > >> - Update this Makefile, chapters.ent and book.sgml > >> - Add a descriptive entry for the new chapter in preface/preface.sgml > >> ----------------------------------------------------------------------------------------------------------------- > >> > >> Do you think this is good enough? > > > > Yes. And I need to look at the "changes since the third > > edition" data as well. :) > > > > -- > > Tom Rhodes > > > -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 00:32:30 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F772106564A; Mon, 15 Dec 2008 00:32:30 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 552258FC29; Mon, 15 Dec 2008 00:32:30 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF0WUbO047663; Mon, 15 Dec 2008 00:32:30 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF0WUTg047659; Mon, 15 Dec 2008 00:32:30 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 00:32:30 GMT Message-Id: <200812150032.mBF0WUTg047659@freefall.freebsd.org> To: murray@FreeBSD.org, murray@FreeBSD.org, freebsd-doc@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/119404: [request] events page should list only last 2 years worth of events, link to archives 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, 15 Dec 2008 00:32:30 -0000 Synopsis: [request] events page should list only last 2 years worth of events, link to archives State-Changed-From-To: suspended->closed State-Changed-By: murray State-Changed-When: Mon Dec 15 00:31:29 UTC 2008 State-Changed-Why: I committed this functionality back with r1.15 of www/en/events/Makefile in June of 2008 but forgot to close this PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=119404 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 00:43:45 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D27861065676 for ; Mon, 15 Dec 2008 00:43:45 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id E42F28FC1F for ; Mon, 15 Dec 2008 00:43:44 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by ewy14 with SMTP id 14so3210171ewy.19 for ; Sun, 14 Dec 2008 16:43:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:x-enigmail-version:content-type :content-transfer-encoding; bh=EgGjY8Pb6DOGiji08BKBHIfhaGblePPLnibCUh8Y+mM=; b=jVsv7pndHkKqHG4MfKsv5N2YrkonO8XvgapVsU9/o8eva0fixUbLL+FdAdrycrJQJb D6sKbOxWBHrFrtEy8rX+lAoteRY2bUR4RZNyHPpqn48unUYrTtfrXJUr9RuARkwmCSJz ucje+oXsTxoMsOZjyYBEpBpNZXyriK/eDDz7o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; b=MNASC6YwPIOwF1XWQzljUNKHUqsHDtQmfOon0EtTs/+jze/v4h6lj79eucM2KegOQC TKHGgjquvLtlwR/zrdMd+/XJPgB2C66UNMRGUGGC0cEcLQeIOo5zUrxO0axcLsDz0t6R FWmx8wrbK1/Dq95ZOgZCFZu7QNGuuRXFaOfj4= Received: by 10.210.59.3 with SMTP id h3mr7064441eba.98.1229301823562; Sun, 14 Dec 2008 16:43:43 -0800 (PST) Received: from self.rene-ladan.nl ([77.163.174.49]) by mx.google.com with ESMTPS id d26sm538423nfh.66.2008.12.14.16.43.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 14 Dec 2008 16:43:42 -0800 (PST) Sender: Rene Ladan Message-ID: <4945A83B.7020302@freebsd.org> Date: Mon, 15 Dec 2008 01:43:39 +0100 From: Rene Ladan User-Agent: Thunderbird 2.0.0.18 (X11/20081123) MIME-Version: 1.0 To: doc@freebsd.org X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Committer's Guide: fix nits 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, 15 Dec 2008 00:43:45 -0000 Hi, below is a patch which fixes a lot of tiny nits in the Committer's Guide, based on revision 1.279 + perforce change 154510 (http://perforce.freebsd.org/chv.cgi?CH=154510) Would this be suitable to commit? Thanks, Rene -------- Originele bericht -------- Onderwerp: PERFORCE change 154670 for review Datum: Mon, 15 Dec 2008 00:20:25 GMT Van: Rene Ladan Aan: Perforce Change Reviews http://perforce.freebsd.org/chv.cgi?CH=154670 Change 154670 by rene@rene_self on 2008/12/15 00:20:10 Fix a lot of nits in the Committers Guide, like capitalization, entity usage, language fixes, and some tiny content fixes. Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#8 edit Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#8 (text+ko) ==== @@ -9,7 +9,7 @@ - The FreeBSD Documentation Project + The &os; Documentation Project @@ -25,7 +25,8 @@ 2005 2006 2007 - The FreeBSD Documentation Project + 2008 + The &os; Documentation Project @@ -39,18 +40,18 @@ - This document provides information for the FreeBSD committer + This document provides information for the &os; committer community. All new committers should read this document before they start, and existing committers are strongly encouraged to review it from time to time. - Almost all FreeBSD developers have commmit rights to one or + Almost all &os; developers have commmit rights to one or more repositories. However, a few developers do not, and some of the information here applies to them as well. (For instance, some people only have rights to work with the Problem Report database). Please see for more information. - This document may also be of interest to members of the FreeBSD + This document may also be of interest to members of the &os; community who want to learn more about how the project works. @@ -86,7 +87,7 @@ &a.bugmeister; - &a.ceri; &a.linimon;, and &a.remko + &a.ceri; &a.linimon;, and &a.remko; @@ -139,10 +140,10 @@ Commit Bit Types - The FreeBSD CVS repository has a number of components which, + The &os; CVS repository has a number of components which, when combined, support the basic operating system source, documentation, third party application ports infrastructure, and - various maintained utilities. When FreeBSD commit bits are + various maintained utilities. When &os; commit bits are allocated, the areas of the tree where the bit may be used are specified. Generally, the areas associated with a bit reflect who authorized the allocation of the commit bit. Additional areas of @@ -185,9 +186,9 @@ Commit bits allocated prior to the development of the notion of areas of authority may be appropriate for use in many parts of the tree. However, common sense dictates that a committer who has not - previously worked in an area of the tree seek review prior to - committing, seek approval from the appropriate responsible party, - and/or work with a mentor. Since the rules regarding code + previously worked in an area of the tree seeks review prior to + committing, seeks approval from the appropriate responsible party, + and/or works with a mentor. Since the rules regarding code maintenance differ by area of the tree, this is as much for the benefit of the committer working in an area of less familiarity as it is for others working on the tree. @@ -281,7 +282,7 @@ via CVSup for the convenience of our users. Note that the www module containing sources - for the FreeBSD website is + for the &os; website is contained within the doc repository. The CVS repositories are hosted on the repository machines. @@ -382,7 +383,7 @@ linkend="repomeisters">repomeister will copy the file(s) to their new name and/or location and let you know when it is done. The purpose of a repository copy is to preserve file - change history, or logs. We in the FreeBSD Project greatly + change history, or logs. We in the &os; Project greatly value the change history that CVS gives to the project. CVS reference information, tutorials, and FAQs can be found at: @@ -435,7 +436,7 @@ - Practical FreeBSD examples: + Practical &os; examples: @@ -690,7 +691,7 @@ Merging is what happens if you check out a copy of - some source code, modify it, then someone else commits a + some file, modify it, then someone else commits a change, and you run cvs update. CVS notices that you have made local changes, and tries to merge your changes with the changes between the version you originally @@ -750,7 +751,7 @@ You will almost certainly get a conflict because - of the $Id$ (or in FreeBSD's case, + of the $Id$ (or in &os;'s case, $FreeBSD$) lines, so you will have to edit the file to resolve the conflict (remove the marker lines and the second $Id$ line, @@ -1187,7 +1188,7 @@ will have any idea who you are or what you are working on. You do not have to write a comprehensive biography, just write a paragraph or two about who you are and what you plan to be working on as a - developer in FreeBSD. (You should also mention who your mentor + developer in &os;. (You should also mention who your mentor will be). Email this to the &a.developers; and you will be on your way! @@ -1213,7 +1214,7 @@ check in place but that may change. Some people blame these checks for bouncing valid email. If you want these checks turned off for your email you can place a file named - ~/.spam_lover in your home directory + ~/.spam_lover on freefall.FreeBSD.org to disable the checks for your email. @@ -1232,7 +1233,7 @@ All new developers also have a mentor assigned to them for the first few months. Your mentor is responsible for teaching you the rules and conventions of the project and guiding your - first steps in the developer community. He or she is also + first steps in the developer community. Your mentor is also personally responsible for your actions during this initial period. @@ -1339,7 +1340,7 @@ person has made. It can be found on freefall at ~fenner/bin/whodid. If your queries go unanswered or the committer otherwise indicates a lack of - proprietary interest in the area affected, go ahead and commit + interest in the area affected, go ahead and commit it. If you are unsure about a commit for any reason at @@ -1355,7 +1356,7 @@ If they see a different solution to a problem than you, or even a different problem, it is not because they are stupid, because they have questionable parentage, or because they are trying to - destroy your hard work, personal image, or FreeBSD, but simply + destroy your hard work, personal image, or &os;, but simply because they have a different outlook on the world. Different is good. @@ -1379,7 +1380,7 @@ GNATS - The FreeBSD Project utilizes + The &os; Project utilizes GNATS for tracking bugs and change requests. Be sure that if you commit a fix or suggestion found in a GNATS PR, you use @@ -1408,8 +1409,8 @@ - You can run a local copy of GNATS, and then integrate the FreeBSD - GNATS tree in to it using CVSup. Then you can run GNATS commands + You can run a local copy of GNATS, and then integrate the &os; + GNATS tree in to it using CVSup. Then you can run the GNATS commands locally. This lets you query the PR database without needing to be connected to the Internet. @@ -1427,7 +1428,7 @@ gnats release=current prefix=/usr - This will place the FreeBSD GNATS tree in + This will place the &os; GNATS tree in /usr/gnats. You can use a refuse file to control which categories to receive. For example, to only receive docs PRs, @@ -1471,7 +1472,7 @@ # This category is mandatory pending:Category for faulty PRs:gnats-admin: # -# FreeBSD categories +# &os; categories # docs:Documentation Bug:freebsd-doc: @@ -1511,7 +1512,7 @@ Who's Who Besides the repository - meisters, there are other FreeBSD project members and teams whom you will + meisters, there are other &os; project members and teams whom you will probably get to know in your role as a committer. Briefly, and by no means all-inclusively, these are: @@ -1524,7 +1525,7 @@ John is the manager of the SMPng Project, and has authority over the architectural design and implementation of the move to fine-grained kernel threading and locking. - He's also the editor of the SMPng Architecture Document. + He is also the editor of the SMPng Architecture Document. If you are working on fine-grained SMP and locking, please coordinate with John. You can learn more about the SMPng Project on its home page: @@ -1538,7 +1539,7 @@ doceng is the group responsible for the documentation build infrastructure, approving new documentation committers, and - ensuring that the FreeBSD website and documentation on the FTP + ensuring that the &os; website and documentation on the FTP site is up to date with respect to the CVS tree. It is not a conflict resolution body. The vast majority of documentation related discussion takes place on the &a.doc;. More details regarding the doceng team can be found in its charter. Committers @@ -1567,7 +1568,7 @@ When you do a commit that could have been done better, Bruce will be there to tell you. Be thankful that someone is. Bruce is also very knowledgeable on the various - standards applicable to FreeBSD. + standards applicable to &os;. @@ -1603,7 +1604,7 @@ Colin is the - FreeBSD Security + &os; Security Officer and oversees the &a.security-officer;. @@ -1618,7 +1619,7 @@ are not sure of some potential change to the networking subsystem you have in mind, Garrett is someone to talk to. Garrett is also very knowledgeable on the various - standards applicable to FreeBSD. + standards applicable to &os;. @@ -1643,12 +1644,12 @@ voting, announcements, etc. The &a.developers; is for the exclusive use of - FreeBSD committers. In order to develop FreeBSD, committers must + &os; committers. In order to develop &os;, committers must have the ability to openly discuss matters that will be resolved before they are publicly announced. Frank discussions of work in - progress are not suitable for open publication and may harm FreeBSD. + progress are not suitable for open publication and may harm &os;. - All FreeBSD committers are reminded to obey the copyright of the + All &os; committers are reminded to obey the copyright of the original author(s) of &a.developers; mail. Do not publish or forward messages from the &a.developers; outside the list membership without permission of all of the authors. @@ -1661,12 +1662,12 @@ This list is not intended as a place for code reviews or a replacement for the &a.arch; or the &a.audit;. In fact - using it as such hurts the FreeBSD Project as it gives a sense of a - closed list where general decisions affecting all of the FreeBSD + using it as such hurts the &os; Project as it gives a sense of a + closed list where general decisions affecting all of the &os; using community are made without being open. Last, but not least never, never ever, email - the &a.developers; and CC:/BCC: another FreeBSD list. - Never, ever email another FreeBSD email list and CC:/BCC: + the &a.developers; and CC:/BCC: another &os; list. + Never, ever email another &os; email list and CC:/BCC: the &a.developers;. Doing so can greatly diminish the benefits of this list. @@ -1679,7 +1680,7 @@ - If you do not wish to type your password in every + If you do not wish to type in your password every time you use &man.ssh.1;, and you use RSA or DSA keys to authenticate, &man.ssh-agent.1; is there for your convenience. If you want to use &man.ssh-agent.1;, make @@ -1702,7 +1703,7 @@ ($HOME/.ssh/id_dsa.pub or $HOME/.ssh/id_rsa.pub) to the person setting you up as a committer so it can be put - into yourlogin file in + into yourlogin in /etc/ssh-keys/ on freefall. @@ -1789,7 +1790,7 @@ - The FreeBSD Committers' Big List of Rules + The &os; Committers' Big List of Rules @@ -1858,7 +1859,7 @@ Do not commit to anything under the src/contrib, - src/crypto, and + src/crypto, or src/sys/contrib trees without explicit approval from the respective maintainer(s). @@ -1997,7 +1998,7 @@ Respect existing maintainers if listed. - Many parts of FreeBSD are not owned in + Many parts of &os; are not owned in the sense that any specific individual will jump up and yell if you commit a change to their area, but it still pays to check first. One convention we use @@ -2016,8 +2017,8 @@ question and see if someone has been working recently or predominantly in that area. - Other areas of FreeBSD fall under the control of - someone who manages an overall category of FreeBSD + Other areas of &os; fall under the control of + someone who manages an overall category of &os; evolution, such as internationalization or networking. See @@ -2111,7 +2112,7 @@ flame-o-gram at least had the grace to send it privately, then have the grace to keep it private yourself. If you feel you are being unfairly treated by another developer, - and it is causing you anguish, bring the matter up with + and it is causing you anguish, bring up the matter with core rather than taking it public. Core will do its best to play peace makers and get things back to sanity. In cases where the dispute involves a change to the codebase and @@ -2134,7 +2135,7 @@ and committing 10 megabytes worth of accumulated stuff. People who abuse this on a regular basis will have their commit privileges suspended until they get back from the - FreeBSD Happy Reeducation Camp we run in Greenland. + &os; Happy Reeducation Camp we run in Greenland. @@ -2167,9 +2168,9 @@ running that code. If you have a change which also may break another architecture, be sure and test on all supported architectures. Please refer to the FreeBSD Internal + url="http://www.FreeBSD.org/internal/">&os; Internal Page for a list of available resources. As other - architectures are added to the FreeBSD supported platforms + architectures are added to the &os; supported platforms list, the appropriate shared testing resources will be made available. @@ -2194,7 +2195,7 @@ Please note that this does not mean you should not try to improve the software in question; you are still more than welcome to do so. Ideally, you should submit your patches to - the vendor. If your changes are FreeBSD-specific, talk to the + the vendor. If your changes are &os;-specific, talk to the maintainer; they may be willing to apply them locally. But whatever you do, do not commit there by yourself! @@ -2208,9 +2209,9 @@ Policy on Multiple Architectures - FreeBSD has added several new arch ports during recent + &os; has added several new architecture ports during recent release cycles and is truly no longer an &i386; centric operating - system. In an effort to make it easier to keep FreeBSD portable + system. In an effort to make it easier to keep &os; portable across the platforms we support, core has developed the following mandate: @@ -2223,7 +2224,7 @@ to the source tree. - The i386 and Sparc64 platforms were chosen due to being more + The Sparc64 and i386 platforms were chosen due to being more readily available to developers and as representatives of more diverse processor and system designs - big vs little endian, register file vs register stack, different DMA and cache @@ -2306,39 +2307,39 @@ Support for Multiple Architectures - FreeBSD is a highly portable operating system intended to + &os; is a highly portable operating system intended to function on many different types of hardware architectures. Maintaining clean separation of Machine Dependent (MD) and Machine Independent (MI) code, as well as minimizing MD code, is an important part of our strategy to remain agile with regards to current hardware trends. Each new hardware architecture supported by - FreeBSD adds substantially to the cost of code maintenance, + &os; adds substantially to the cost of code maintenance, toolchain support, and release engineering. It also dramatically increases the cost of effective testing of kernel changes. As such, there is strong motivation to differentiate between classes of support for various architectures while remaining strong in a few - key architectures that are seen as the FreeBSD "target audience". + key architectures that are seen as the &os; "target audience". Statement of General Intent - The FreeBSD Project targets "production quality commercial + The &os; Project targets "production quality commercial off-the-shelf (COTS) workstation, server, and high-end embedded systems". By retaining a focus on a narrow set of architectures - of interest in these environments, the FreeBSD Project is able + of interest in these environments, the &os; Project is able to maintain high levels of quality, stability, and performance, as well as minimize the load on various support teams on the project, such as the ports team, documentation team, security officer, and release engineering teams. Diversity in - hardware support broadens the options for FreeBSD consumers by + hardware support broadens the options for &os; consumers by offering new features and usage opportunities (such as support - for 64-bit CPUs, use in embedded environments, etc.), but these + for 64 bit CPUs, use in embedded environments, etc.), but these benefits must always be carefully considered in terms of the real-world maintenance cost associated with additional platform support. - The FreeBSD Project differentiates platform targets into + The &os; Project differentiates platform targets into four tiers. Each tier includes a specification of the requirements for an architecture to be in that tier, as well as specifying the obligations of developers with @@ -2357,13 +2358,13 @@ (features which are inherently architecture-specific, such as support for hardware device drivers, may be exempt from this requirement). In general, all Tier 1 platforms must have build - and tinderbox support either in the FreeBSD.org cluster, or + and Tinderbox support either in the FreeBSD.org cluster, or be easily available for all developers. Embedded platforms may - substitute an emulator available in the FreeBSD cluster for + substitute an emulator available in the &os; cluster for actual hardware. Tier 1 architectures are expected to be Production Quality - with respects to all aspects of the FreeBSD operating system, + with respects to all aspects of the &os; operating system, including installation and development environments. Tier 1 architectures are expected to be completely @@ -2377,12 +2378,12 @@ platform, or have the appropriate filters to prevent the inappropriate ones from building there. The packaging system must support all Tier 1 architectures. To ensure an - architectures Tier 1 status, proponents of that architecture + architecture's Tier 1 status, proponents of that architecture must show that all relevant packages can be built on that platform. Tier 1 embedded architectures must be able to cross-build - packages on at least one other tier 1 architecture. The + packages on at least one other Tier 1 architecture. The packages must be the most relevant for the platform, but may be a non-empty subset of those that build natively. @@ -2403,19 +2404,19 @@ maintainer is expected to work with the platform maintainers to refine these changes. Major new toolchain components are allowed to break support for Tier 2 architectures if the - FreeBSD-local changes haven't been incorporated upstream. The + &os;-local changes have not been incorporated upstream. The toolchain maintainers are expected to provide prompt review of any proposed changes and cannot block, through their inaction, - changes going into the tree. New features added to FreeBSD + changes going into the tree. New features added to &os; should be feasible to implement on these platforms, but an implementation is not required before the feature may be added - to the FreeBSD source tree. New features that may be difficult + to the &os; source tree. New features that may be difficult to implement on Tier 2 architectures should provide a means of disabling them on those architectures. The implementation of - a Tier 2 architecture may be committed to the main FreeBSD + a Tier 2 architecture may be committed to the main &os; tree as long as it does not interfere with production work on Tier 1 platforms, or substantially with other Tier 2 platforms. - Before a Tier 2 platform can be added to the FreeBSD base + Before a Tier 2 platform can be added to the &os; base source tree, the platform must be able to boot multi-user on actual hardware. Generally, there must be at least three active developers working on the platform. @@ -2425,22 +2426,22 @@ reaching end of life may also be moved from Tier 1 status to Tier 2 status as the availability of resources to continue to maintain the system in a Production Quality state diminishes. Well supported - niche architectures may also be tier 2. + niche architectures may also be Tier 2. Tier 2 architectures may have some support for them integrated into the ports infrastructure. They may have cross compilation support added, at the discretion of portmgr. Some - ports must built natively, into packages if the package system + ports must built natively into packages if the package system supports that architecture. If not integrated into the base system, some external patches for the architecture for ports must be available. - Tier 2 architectures can be integrated into the FreeBSD + Tier 2 architectures can be integrated into the &os; handbook. The basics for how to get a system running must be documented, although not necessarily for every single board or - system a tier 2 architecture supports. The supported hardware + system a Tier 2 architecture supports. The supported hardware list must exist and should be no more than a couple of months - old. It should be integrated into the FreeBSD + old. It should be integrated into the &os; documentation. Current Tier 2 platforms are ARM, PowerPC, ia64, Sparc64 and @@ -2456,13 +2457,13 @@ Tier 3 platforms are architectures in the early stages of development, for non-mainstream hardware platforms, or which are considered legacy systems unlikely to see broad future - use. New tier 3 systems will not be committed to the base + use. New Tier 3 systems will not be committed to the base source tree. Support for Tier 3 systems may be worked on in - the FreeBSD Perforce Repository, providing source control and - easier change integration from the main FreeBSD tree. + the &os; Perforce Repository, providing source control and + easier change integration from the main &os; tree. Platforms that transition to Tier 3 status may be removed from the tree if they are no longer actively supported by the - FreeBSD developer community at the discretion of the release + &os; developer community at the discretion of the release engineer. Tier 3 platforms may have ports support, either integrated @@ -2471,7 +2472,7 @@ Tier 3 platforms must have the basics documented for how to build a kernel and how to boot it on at least one target hardware or emulation environment. This documentation need - not be integrated into the FreeBSD tree. + not be integrated into the &os; tree. Current Tier 3 platforms are MIPS and &s390;. @@ -2490,7 +2491,7 @@ Policy on Changing the Tier of an Architecture Systems may only be moved from one tier to another by - approval of the FreeBSD Core Team, which shall make that + approval of the &os; Core Team, which shall make that decision in collaboration with the Security Officer, Release Engineering, and toolchain maintenance teams. @@ -2555,10 +2556,10 @@ make sure you have fixed the simple ones. If the port came from a submitter who has not - contributed to the project before, add that person's + contributed to the Project before, add that person's name to the Additional - Contributors section of the FreeBSD Contributors + Contributors section of the &os; Contributors List. Close the PR if the port came in as a PR. To close @@ -3232,7 +3233,7 @@ Issues Specific To Developers Who Are Not Committers - A few people who have access to the FreeBSD machines do not + A few people who have access to the &os; machines do not have commit bits. For instance, the project is willing to give access to the GNATS database to contributors who have shown interest and dedication in working on Problem Reports. @@ -3276,7 +3277,7 @@ - The FreeBSD Committers' Big List of Rules + The &os; Committers' Big List of Rules @@ -3392,7 +3393,7 @@ well. This information consists of one or more lines containing the - key word or phrase, a colon, tabs for formatting, and then the + key word or phrase, a colon, tabs and/or spaces for formatting, and then the additional information. The key words or phrases are: @@ -3410,14 +3411,14 @@ Submitted by: The name and e-mail address of the person that submitted the fix; for committers, just the username on - the FreeBSD cluster. + the &os; cluster. Reviewed by: The name and e-mail address of the person or people that reviewed the change; for committers, just the - username on the FreeBSD cluster. If a patch was + username on the &os; cluster. If a patch was submitted to a mailing list for review, and the review was favorable, then just include the list name. @@ -3426,7 +3427,7 @@ Approved by: The name and e-mail address of the person or people that approved the change; for committers, just the - username on the FreeBSD cluster. It is customary to get + username on the &os; cluster. It is customary to get prior approval for a commit if it is to an area of the tree to which you do not usually commit. In addition, during the run up to a new release all commits @@ -3586,7 +3587,7 @@ The mailing lists are archived under /g/mail which will show up as /hub/g/mail with &man.pwd.1;. - This location is accessible from any machine on the FreeBSD cluster. + This location is accessible from any machine on the &os; cluster. -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 00:52:37 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 274881065673; Mon, 15 Dec 2008 00:52:37 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F05B38FC1E; Mon, 15 Dec 2008 00:52:36 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF0qa44063078; Mon, 15 Dec 2008 00:52:36 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF0qa0M063074; Mon, 15 Dec 2008 00:52:36 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 00:52:36 GMT Message-Id: <200812150052.mBF0qa0M063074@freefall.freebsd.org> To: murray@FreeBSD.org, freebsd-doc@FreeBSD.org, mckusick@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/128325: README.snapshots still refers to snaphots as "alpha-test" code 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, 15 Dec 2008 00:52:37 -0000 Synopsis: README.snapshots still refers to snaphots as "alpha-test" code Responsible-Changed-From-To: freebsd-doc->mckusick Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 00:51:55 UTC 2008 Responsible-Changed-Why: Kirk, can you take a look at this readme and suggest some new text about snapshots? Things have progressed quite a bit since 2000 I am sure. http://www.freebsd.org/cgi/query-pr.cgi?pr=128325 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 00:55:10 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A76AD1065670; Mon, 15 Dec 2008 00:55:10 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7D41C8FC0C; Mon, 15 Dec 2008 00:55:10 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF0tABc063316; Mon, 15 Dec 2008 00:55:10 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF0tARQ063312; Mon, 15 Dec 2008 00:55:10 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 00:55:10 GMT Message-Id: <200812150055.mBF0tARQ063312@freefall.freebsd.org> To: murray@FreeBSD.org, freebsd-doc@FreeBSD.org, delphij@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/128768: Missing documentation about tmpfs mount options 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, 15 Dec 2008 00:55:10 -0000 Synopsis: Missing documentation about tmpfs mount options Responsible-Changed-From-To: freebsd-doc->delphij Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 00:54:41 UTC 2008 Responsible-Changed-Why: Xin LI wrote the tmpfs man page. Can you take a look at this PR about the appropriate section and mount options? http://www.freebsd.org/cgi/query-pr.cgi?pr=128768 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 01:05:11 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 919521065675; Mon, 15 Dec 2008 01:05:11 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 66BDE8FC21; Mon, 15 Dec 2008 01:05:11 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF15BxV070669; Mon, 15 Dec 2008 01:05:11 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF15BFN070665; Mon, 15 Dec 2008 01:05:11 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 01:05:11 GMT Message-Id: <200812150105.mBF15BFN070665@freefall.freebsd.org> To: frank@solensky.org, murray@FreeBSD.org, freebsd-doc@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/129263: Obsolete info on collecting a crash dump prior to "dumpon" 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, 15 Dec 2008 01:05:11 -0000 Synopsis: Obsolete info on collecting a crash dump prior to "dumpon" State-Changed-From-To: open->closed State-Changed-By: murray State-Changed-When: Mon Dec 15 01:04:17 UTC 2008 State-Changed-Why: This obsolete note has been removed from the chapter. Thanks for the submission. The website will be updated within 6 hours to reflect this change. http://www.freebsd.org/cgi/query-pr.cgi?pr=129263 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 01:10:07 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB6F41065670 for ; Mon, 15 Dec 2008 01:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C74288FC08 for ; Mon, 15 Dec 2008 01:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF1A746070958 for ; Mon, 15 Dec 2008 01:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF1A7R7070957; Mon, 15 Dec 2008 01:10:07 GMT (envelope-from gnats) Date: Mon, 15 Dec 2008 01:10:07 GMT Message-Id: <200812150110.mBF1A7R7070957@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: docs/129263: commit references a PR X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 01:10:08 -0000 The following reply was made to PR docs/129263; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/129263: commit references a PR Date: Mon, 15 Dec 2008 01:04:16 +0000 (UTC) murray 2008-12-15 01:04:07 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/developers-handbook/kerneldebug chapter.sgml Log: The config dump syntax for hard-coding the dump location before dumpon(8) can be executed has been deprecated since FreeBSD 4.x and no longer works. Use the loader instead. PR: docs/129263 Revision Changes Path 1.78 +0 -5 doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 01:20:05 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16D751065688 for ; Mon, 15 Dec 2008 01:20:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EF37A8FC0C for ; Mon, 15 Dec 2008 01:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF1K4hr079451 for ; Mon, 15 Dec 2008 01:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF1K4Qh079450; Mon, 15 Dec 2008 01:20:04 GMT (envelope-from gnats) Date: Mon, 15 Dec 2008 01:20:04 GMT Message-Id: <200812150120.mBF1K4Qh079450@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Murray Stokely" Cc: Subject: Re: docs/128356: [request] add Firefox plugin for FreeBSD manual pages X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Murray Stokely List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 01:20:05 -0000 The following reply was made to PR docs/128356; it has been noted by GNATS. From: "Murray Stokely" To: bug-followup@freebsd.org, alexander.pohoyda@gmx.net Cc: Subject: Re: docs/128356: [request] add Firefox plugin for FreeBSD manual pages Date: Sun, 14 Dec 2008 17:10:39 -0800 I like this, and I think it would make sense to host something like this somewhere on freebsd.org, but I'm not sure this is the best solution. This provides me with a dropdown freebsd icon on the search box in my Firefox browser. I expect to be able to type search terms that match single-line fields of open PRs in such a field, but instead it only works if I enter the exact PR number of something I am looking for. I don't think that is what people would expect from a search bar. Can you update the patch to search single-line fields of open PRs instead? - Murray From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 01:26:53 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E57961065686; Mon, 15 Dec 2008 01:26:53 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BA16C8FC0C; Mon, 15 Dec 2008 01:26:53 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF1Qr5g086923; Mon, 15 Dec 2008 01:26:53 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF1Qr4H086919; Mon, 15 Dec 2008 01:26:53 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 01:26:53 GMT Message-Id: <200812150126.mBF1Qr4H086919@freefall.freebsd.org> To: boris.hollas@gmx.de, murray@FreeBSD.org, freebsd-doc@FreeBSD.org, murray@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/128129: Sysinstall color problem in xterm 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, 15 Dec 2008 01:26:54 -0000 Synopsis: Sysinstall color problem in xterm State-Changed-From-To: open->closed State-Changed-By: murray State-Changed-When: Mon Dec 15 01:26:03 UTC 2008 State-Changed-Why: I've added a Q/A entry to the troubleshooting section about this. Thanks for the submission. The website may take up to 6 hours before it reflects this change. Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:26:03 UTC 2008 Responsible-Changed-Why: I've added a Q/A entry to the troubleshooting section about this. Thanks for the submission. The website may take up to 6 hours before it reflects this change. http://www.freebsd.org/cgi/query-pr.cgi?pr=128129 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 01:28:41 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 291401065672; Mon, 15 Dec 2008 01:28:41 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F26258FC14; Mon, 15 Dec 2008 01:28:40 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF1SeEo094552; Mon, 15 Dec 2008 01:28:40 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF1Sehd094548; Mon, 15 Dec 2008 01:28:40 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 01:28:40 GMT Message-Id: <200812150128.mBF1Sehd094548@freefall.freebsd.org> To: murray@FreeBSD.org, freebsd-doc@FreeBSD.org, loader@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/127923: Please mention qemu in the FreeBSD 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: Mon, 15 Dec 2008 01:28:41 -0000 Synopsis: Please mention qemu in the FreeBSD Handbook Responsible-Changed-From-To: freebsd-doc->loader Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:28:02 UTC 2008 Responsible-Changed-Why: Loader, didn't you have some patchecs to add qemu here? Can you add something about it to the virtualization chapter? http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 01:50:50 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CABB1065679; Mon, 15 Dec 2008 01:50:50 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EDB2B8FC13; Mon, 15 Dec 2008 01:50:49 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF1on71021875; Mon, 15 Dec 2008 01:50:49 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF1onJL021871; Mon, 15 Dec 2008 01:50:49 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 01:50:49 GMT Message-Id: <200812150150.mBF1onJL021871@freefall.freebsd.org> To: boris.hollas@gmx.de, murray@FreeBSD.org, freebsd-doc@FreeBSD.org, murray@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/128128: Sysinstall not mentioned in 4.4 "Using the Packages System" 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, 15 Dec 2008 01:50:50 -0000 Synopsis: Sysinstall not mentioned in 4.4 "Using the Packages System" State-Changed-From-To: open->closed State-Changed-By: murray State-Changed-When: Mon Dec 15 01:49:59 UTC 2008 State-Changed-Why: I've just submitted an introduction to this section which also mentions sysinstall and links to the post installation section of chapter 2. Thanks for the submission. The website may take up to 6 hours before it reflects this change. Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:49:59 UTC 2008 Responsible-Changed-Why: I've just submitted an introduction to this section which also mentions sysinstall and links to the post installation section of chapter 2. Thanks for the submission. The website may take up to 6 hours before it reflects this change. http://www.freebsd.org/cgi/query-pr.cgi?pr=128128 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 01:55:32 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA4A61065675; Mon, 15 Dec 2008 01:55:32 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9E4BD8FC18; Mon, 15 Dec 2008 01:55:32 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF1tWal035162; Mon, 15 Dec 2008 01:55:32 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF1tWUf035158; Mon, 15 Dec 2008 01:55:32 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 01:55:32 GMT Message-Id: <200812150155.mBF1tWUf035158@freefall.freebsd.org> To: nick@anywi.com, murray@FreeBSD.org, freebsd-doc@FreeBSD.org, n_hibma@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/127406: [patch] update umodem man page: Sony Ericsson W810i 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, 15 Dec 2008 01:55:32 -0000 Synopsis: [patch] update umodem man page: Sony Ericsson W810i State-Changed-From-To: open->patched State-Changed-By: murray State-Changed-When: Mon Dec 15 01:55:00 UTC 2008 State-Changed-Why: Nick already submitted this to HEAD, this is his MFC reminder. Responsible-Changed-From-To: freebsd-doc->n_hibma Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:55:00 UTC 2008 Responsible-Changed-Why: Nick already submitted this to HEAD, this is his MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=127406 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 01:58:11 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5E541065676; Mon, 15 Dec 2008 01:58:11 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8AD568FC14; Mon, 15 Dec 2008 01:58:11 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF1wBwP035371; Mon, 15 Dec 2008 01:58:11 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF1wBxl035367; Mon, 15 Dec 2008 01:58:11 GMT (envelope-from murray) Date: Mon, 15 Dec 2008 01:58:11 GMT Message-Id: <200812150158.mBF1wBxl035367@freefall.freebsd.org> To: murray@FreeBSD.org, freebsd-doc@FreeBSD.org, murray@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/122470: [patch] exit status on fetch(1) manual 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: Mon, 15 Dec 2008 01:58:11 -0000 Synopsis: [patch] exit status on fetch(1) manual page Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:57:39 UTC 2008 Responsible-Changed-Why: I have an outstanding patch to fetch out for review. I will make this change in a follow up submit. http://www.freebsd.org/cgi/query-pr.cgi?pr=122470 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 02:32:09 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AA541065670; Mon, 15 Dec 2008 02:32:09 +0000 (UTC) (envelope-from murray@stokely.org) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id AEA5A8FC0C; Mon, 15 Dec 2008 02:32:08 +0000 (UTC) (envelope-from murray@stokely.org) Received: by ewy14 with SMTP id 14so3242193ewy.19 for ; Sun, 14 Dec 2008 18:32:07 -0800 (PST) Received: by 10.210.70.14 with SMTP id s14mr4971009eba.151.1229308327372; Sun, 14 Dec 2008 18:32:07 -0800 (PST) Received: by 10.210.71.14 with HTTP; Sun, 14 Dec 2008 18:32:07 -0800 (PST) Message-ID: <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> Date: Sun, 14 Dec 2008 18:32:07 -0800 From: "Murray Stokely" To: "Tom Rhodes" In-Reply-To: <20081214185058.48a7c2c2.trhodes@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> Cc: freebsd-doc@freebsd.org Subject: Re: Preface need update. 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, 15 Dec 2008 02:32:09 -0000 On Sun, Dec 14, 2008 at 3:50 PM, Tom Rhodes wrote: > Thanks for that! I definitely slacked here, but I'll keep this > in mind for the future. About the updating chapter, I am unable > to find any information on portsnap in my printed copy of the > Handbook (third edition). They could have existed (I see a > 2006 commit date for freebsd-update in src) but seem to have > not been documented in the handbook. Ahh, I see, nothing was moved over from the Cutting Edge chapter. This chapter has just about the exact same purpose as the new Updating chapter, they just describe different tools. The first chapter Updating, even references the latter chapter (Cutting Edge) as a pre-requisite in the synopsis by saying one needs to read it to learn about Mergemaster. There should only be one updating chapter. Cutting Edge was there first, but updating is maybe a better name. How do you feel about merging them back into one chapter? > Anyway, how does this patch look to you?: Everything else looks good, except I don't like that we now have two chapters for updating instead of one. I wasn't paying attention when that happened. =) Maybe just submit the new item for auditing while we sort out what to do about updating? - Murray From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 04:00:12 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 088041065670 for ; Mon, 15 Dec 2008 04:00:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BC52E8FC14 for ; Mon, 15 Dec 2008 04:00:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF40BAx029327 for ; Mon, 15 Dec 2008 04:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF40Ba5029326; Mon, 15 Dec 2008 04:00:11 GMT (envelope-from gnats) Date: Mon, 15 Dec 2008 04:00:11 GMT Message-Id: <200812150400.mBF40Ba5029326@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Murray Stokely" Cc: Subject: Re: docs/102148: The description of which Intel chips have EM64T is out of date X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Murray Stokely List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 04:00:12 -0000 The following reply was made to PR docs/102148; it has been noted by GNATS. From: "Murray Stokely" To: bug-followup@freebsd.org, mwm@mired.org Cc: Subject: Re: docs/102148: The description of which Intel chips have EM64T is out of date Date: Sun, 14 Dec 2008 19:51:36 -0800 After 2 years the description is even more out of date. Here is a proposed patch : http://people.freebsd.org/~murray/patches/hardware-amd64.diff - Murray From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 10:30:36 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B95C1065673 for ; Mon, 15 Dec 2008 10:30:36 +0000 (UTC) (envelope-from no-reply@tradeandstock.it) Received: from smtp4.aruba.it (smtpd3.aruba.it [62.149.128.208]) by mx1.freebsd.org (Postfix) with SMTP id 6F2AF8FC12 for ; Mon, 15 Dec 2008 10:30:34 +0000 (UTC) (envelope-from no-reply@tradeandstock.it) Received: (qmail 4728 invoked by uid 89); 15 Dec 2008 10:30:29 -0000 Received: from unknown (HELO host62-90-static.106-82-b.business.telecomitalia.it) (newsletter@tradeandstock.it@82.106.90.62) by smtp4.aruba.it with SMTP; 15 Dec 2008 10:30:29 -0000 From: "1click1stock" To: doc@freebsd.org Content-Transfer-Encoding: quoted-printable X-Mailer: SendBlaster.1.4.9 Date: Mon, 15 Dec 2008 11:30:30 +0100 Message-ID: <984620743361995473@lorenzo> X-Spam-Rating: smtp4.aruba.it 1.6.2 0/1000/N MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Comunicato Sampa 1clik1stok X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: no-reply@tradeandstock.it List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 10:30:36 -0000 Se non riesc= i a vedere correttamente questo messaggio puoi visualizzarlo con un browser= all'indirizzo: [1]www.1click1stoc= k.com/ [2]3D1click1= [xma=] Alcune delle nostre offerte per i tuoi re= gali di natale [3]3D"Nautica [4]3D"Brail [5]3D"Sector [6]3D"Entra <= /TR> Ti preghiam= o di NON RISPONDERE A QUESTA E-MAIL in quanto non sar=E0 presa in considera= zione. Hai ricevuto questa e-mail perch=E8 sei un utente registrato 1click1= stock. Se desideri contattarci accedi al sito e clicca su "[7]Contattaci". Se = desideri conoscere in dettaglio come 1click1stock tratta i tuoi dati person= ali, per favore leggi la nostra [8]Privacy References 1. 3D"http://www.1click1stock.it/newsletter/2008_1= 2. 3D"http://1click1stock.com/" 3. 3D"http://www.1click1stock.it/products/43/nautica-challenge-a235= 4. 3D"http://www.1click1stock.it/products/80/breil-griffe-el= 5. 3D"http://www.1click1stock.it/products/83/sec= 6. 3D"http://1click1stock.com/" 7. 3D"http:= 8. 3D"http://www.1click1stock.it/priva= From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 11:06:05 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5DCE1065673 for ; Mon, 15 Dec 2008 11:06:05 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 97EA68FC17 for ; Mon, 15 Dec 2008 11:06:05 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBFB65vr003340 for ; Mon, 15 Dec 2008 11:06:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBFB65Ye003336 for freebsd-doc@FreeBSD.org; Mon, 15 Dec 2008 11:06:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Dec 2008 11:06:05 GMT Message-Id: <200812151106.mBFB65Ye003336@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats 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, 15 Dec 2008 11:06:05 -0000 (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/129464 doc using packages system o docs/129428 doc ntp.conf(5) is incorrect - you can only use IP address o docs/129400 doc [patch] Remove comments that have snook into three man o docs/129398 doc [patch] ddb(8): various tweaks to ddb-related man page o docs/129196 doc Inconsistent errno in strtol() o docs/129095 doc ipfw(8): Can not check that packet originating/destine o docs/129024 doc [patch] ipfw(8) improvements p docs/128968 doc [patch] rwlock(9) man page typo o docs/128804 doc Gmirror handbook instructions convert boot-drive to gm o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t o docs/128032 doc pthread(3) mentions libkse which has been removed in 8 o docs/127952 doc man for locate(1) is missing o docs/127908 doc [PATCH] readdir(3) error documentation o docs/127890 doc socket(2) man page should explain that protocol can be p docs/127866 doc Typos found in ifconfig(8) man page o docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/127842 doc list of hardware devices missing from the relnotes o docs/127840 doc [patch] fix entity references in release/doc/en_US.ISO o docs/127602 doc [patch] Incomplete information in nsswitch.conf(5) o docs/127575 doc [patch] Update to ports (7) as it is missing a few mak o docs/126934 doc missing 'crit' in usr.sbin/syslogd/syslog.conf.5 o docs/126921 doc [patch] History section of cpuset(1) incorrect o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126487 doc fix language on atol(3) manpage o docs/126484 doc libc function res-zonscut2 is not documented o docs/126445 doc discussion on WEP settings in wpa_supplicant.conf(5) m o docs/126227 doc [patch] kthread(9) refers to non-existent manpage, des o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125896 doc [PATCH] arp manual and syntax synchronisation o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete o docs/125639 doc [patch] kldunloadf(2) does not mention about possible p docs/124166 doc fortune: instant-workstation tip should go o docs/123400 doc gvinum startup in handbook o docs/123035 doc [patch] bugs in refuse.README o docs/122053 doc [patch] update on vinum(4) reference to newfs(8) o docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121871 doc ftpd does not interpret configuration files as documen o docs/121585 doc [handbook] Wrong multicast specification o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting s docs/121541 doc [request] no man pages for wlan_scan_ap o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121197 doc [patch] edits to books/porters-handbook o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120628 doc PAE documentation errror in handbook o docs/120539 doc Inconsistent ipfw's man page o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120040 doc handbook: diskless operation: populate root doesn't po o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119907 doc Ports compatibility o docs/119746 doc l10n chapter of handbook (Russian Language) o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) o docs/119338 doc gprof(1) refers to unmentioned option "-c" o docs/119329 doc [patch] Fix misleading man 1 split o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu o docs/118332 doc man page for top does not describe STATE column wait e o docs/118214 doc close(2) error returns incomplete o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/117798 doc formatting oddity in sysmouse(4) o docs/117747 doc 'break' system call needs a man page o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument o docs/116480 doc sysctl(3) description of kern.file no longer applies s o docs/116116 doc mktemp (3) re/move note o docs/116080 doc PREFIX is documented, but not the more important LOCAL o docs/115921 doc Booting from pst(4) is not supported o docs/115065 doc [patch] sync ps.1 with p_flag and keywords o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114184 doc [patch] [ndis]: add info to man 4 ndis o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/112804 doc groff(1) command should be called to explicitly use "p o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat o docs/112481 doc bug in ppp.linkup example o docs/111425 doc Missing chunks of text in historical manpages o docs/111265 doc [request] Clarify how to set common shell variables o docs/111263 doc [request] Information on $EDITOR variable in section 3 o docs/111147 doc hostapd.conf is not documented o docs/110999 doc carp(4) should document unsupported interface types o docs/110692 doc wi(4) man page doesn't say WPA is not supported o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir o docs/110253 doc [patch] rtprio(1): remove processing starvation commen o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit o docs/110061 doc [PATCH] tuning(7) missing reference to vfs.read_max o docs/109983 doc No manual entry for protoize o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109975 doc No manual entry for elf2aout o docs/109973 doc No manual entry for c++filt o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd o docs/109115 doc add Ultra 450 to hardware list for sparc64 a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/104403 doc man security should mention that the usage of the X Wi o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/102148 doc The description of which Intel chips have EM64T is out o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym o docs/100196 doc man login.conf does explain not "unlimited" o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings o docs/98974 doc Missing tunables in loader(8) manpage o docs/98759 doc [patch] sbp_targ(4) man page missing reference to devi o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/95139 doc FAQ to move filesystem to new disk fails: incorrect pe o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91506 doc ndis(4) man page should be more specific about support o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/86342 doc bikeshed entry of Handbook is wrong o docs/85187 doc [patch] find(1) manpage missing block info for -ls o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1) o docs/85100 doc NOTES: ICH audio device support statement is ambiguous o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84806 doc mdoc(7) manpage has section ordering problems o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84538 doc [patch] sk(4) driver supports Marvell 88E800x chip too o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c o docs/84265 doc [patch] chmod(1) manpage omits implication of setting f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/78240 doc [patch] handbook: replace with aroun o docs/78138 doc [patch] Error in pre-installation section of installat o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not o docs/75865 doc comments on "backup-basics" in handbook o docs/70652 doc [patch] New man page: portindex(5) o docs/70583 doc [patch] Update freebsd-glossary o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio o docs/61605 doc [request] Improve documentation for i386 disk geometry o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/50211 doc [PATCH] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ o docs/47818 doc [patch] ln(1) manpage is confusing o docs/43823 doc [PATCH] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/38982 doc [patch] developers-handbook/Jail fix o docs/38556 doc EPS file of beastie, as addition to existing examples o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc. s docs/35678 doc docproj Makefiles for web are broken for paths with sp s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. a docs/30008 doc [patch] French softupdates document should be translat o docs/27605 doc [patch] Cross-document references () o docs/26286 doc *printf(3) etc should gain format string warnings o docs/24786 doc missing FILES descriptions in sa(4) s docs/20028 doc ASCII docs should reflect tags in the sourc 172 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 11:29:06 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DB66106564A for ; Mon, 15 Dec 2008 11:29:06 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 628348FC0C for ; Mon, 15 Dec 2008 11:29:06 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (c-68-83-213-214.hsd1.va.comcast.net [68.83.213.214]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBFBT4nb027594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Dec 2008 06:29:05 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Mon, 15 Dec 2008 06:28:58 -0500 From: Tom Rhodes To: "Murray Stokely" Message-Id: <20081215062858.6c76fb33.trhodes@FreeBSD.org> In-Reply-To: <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org Subject: Re: Preface need update. 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, 15 Dec 2008 11:29:06 -0000 On Sun, 14 Dec 2008 18:32:07 -0800 "Murray Stokely" wrote: > On Sun, Dec 14, 2008 at 3:50 PM, Tom Rhodes wrote: > > Thanks for that! I definitely slacked here, but I'll keep this > > in mind for the future. About the updating chapter, I am unable > > to find any information on portsnap in my printed copy of the > > Handbook (third edition). They could have existed (I see a > > 2006 commit date for freebsd-update in src) but seem to have > > not been documented in the handbook. > > Ahh, I see, nothing was moved over from the Cutting Edge chapter. > > This chapter has just about the exact same purpose as the new Updating > chapter, they just describe different tools. The first chapter > Updating, even references the latter chapter (Cutting Edge) as a > pre-requisite in the synopsis by saying one needs to read it to learn > about Mergemaster. > > There should only be one updating chapter. Cutting Edge was there > first, but updating is maybe a better name. > > How do you feel about merging them back into one chapter? > > > Anyway, how does this patch look to you?: > > Everything else looks good, except I don't like that we now have two > chapters for updating instead of one. I wasn't paying attention when > that happened. =) Maybe just submit the new item for auditing while > we sort out what to do about updating? > > - Murray > Works for me. Let me work over a patch today (I should have enough time) and get it out. :) -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 13:03:04 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FDF6106567C; Mon, 15 Dec 2008 13:03:04 +0000 (UTC) (envelope-from loader@freebsdmall.com) Received: from mail.freebsdmall.com (mail.freebsdmall.com [69.50.233.168]) by mx1.freebsd.org (Postfix) with ESMTP id 903B38FC1A; Mon, 15 Dec 2008 13:03:04 +0000 (UTC) (envelope-from loader@freebsdmall.com) Received: by mail.freebsdmall.com (Postfix, from userid 2136) id B5E051D703EF; Mon, 15 Dec 2008 05:02:36 -0800 (PST) To: murray@FreeBSD.org References: <200812150128.mBF1Sehd094548@freefall.freebsd.org> From: loader In-Reply-To: <200812150128.mBF1Sehd094548@freefall.freebsd.org> (murray@freebsd.org's message of "Mon\, 15 Dec 2008 01\:28\:40 GMT") MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <20081215130236.B5E051D703EF@mail.freebsdmall.com> Date: Mon, 15 Dec 2008 05:02:36 -0800 (PST) Cc: freebsd-doc@FreeBSD.org Subject: Re: docs/127923: Please mention qemu in the FreeBSD 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: Mon, 15 Dec 2008 13:03:04 -0000 murray@FreeBSD.org wrote: > Synopsis: Please mention qemu in the FreeBSD Handbook > > Responsible-Changed-From-To: freebsd-doc->loader > Responsible-Changed-By: murray > Responsible-Changed-When: Mon Dec 15 01:28:02 UTC 2008 > Responsible-Changed-Why: > Loader, didn't you have some patchecs to add qemu here? Can you add > something about it to the virtualization chapter? > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 Okay, I will try to add a section about Qemu these days. Regards, loader From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 14:36:15 2008 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4847F1065675 for ; Mon, 15 Dec 2008 14:36:15 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 09E4B8FC27 for ; Mon, 15 Dec 2008 14:36:14 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (c-68-83-213-214.hsd1.va.comcast.net [68.83.213.214]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBFEaEB1028317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Dec 2008 09:36:14 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Mon, 15 Dec 2008 09:36:07 -0500 From: Tom Rhodes To: Rene Ladan Message-Id: <20081215093607.71a509f8.trhodes@FreeBSD.org> In-Reply-To: <4945A83B.7020302@freebsd.org> References: <4945A83B.7020302@freebsd.org> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: doc@FreeBSD.org Subject: Re: Committer's Guide: fix nits 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, 15 Dec 2008 14:36:15 -0000 On Mon, 15 Dec 2008 01:43:39 +0100 Rene Ladan wrote: > Hi, > > below is a patch which fixes a lot of tiny nits in the Committer's Guide, > based on revision 1.279 + perforce change 154510 (http://perforce.freebsd.org/chv.cgi?CH=154510) > > Would this be suitable to commit? You may want to investigate, but I believe Ceri has run out of available time for FreeBSD. So he may not be part of the bugmeister team any longer. Also, I agree with a lot of the wording changes, in the future though, can simple FreeBSD->&os; changes be done outside of wording changes? I know it's still whitespace, but those changes need no real review beyond your normal second glance, and make diffs longer to read. :) Thanks, -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 18:49:27 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82D951065670; Mon, 15 Dec 2008 18:49:27 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 28E0A8FC16; Mon, 15 Dec 2008 18:49:27 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (c-68-83-213-214.hsd1.va.comcast.net [68.83.213.214]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBFInPde029193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Dec 2008 13:49:26 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Mon, 15 Dec 2008 13:49:19 -0500 From: Tom Rhodes To: Tom Rhodes Message-Id: <20081215134919.51a88d90.trhodes@FreeBSD.org> In-Reply-To: <20081215062858.6c76fb33.trhodes@FreeBSD.org> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org, murray@stokely.org Subject: Re: Preface need update. 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, 15 Dec 2008 18:49:27 -0000 On Mon, 15 Dec 2008 06:28:58 -0500 Tom Rhodes wrote: > On Sun, 14 Dec 2008 18:32:07 -0800 > "Murray Stokely" wrote: > > > On Sun, Dec 14, 2008 at 3:50 PM, Tom Rhodes wrote: > > > Thanks for that! I definitely slacked here, but I'll keep this > > > in mind for the future. About the updating chapter, I am unable > > > to find any information on portsnap in my printed copy of the > > > Handbook (third edition). They could have existed (I see a > > > 2006 commit date for freebsd-update in src) but seem to have > > > not been documented in the handbook. > > > > Ahh, I see, nothing was moved over from the Cutting Edge chapter. > > > > This chapter has just about the exact same purpose as the new Updating > > chapter, they just describe different tools. The first chapter > > Updating, even references the latter chapter (Cutting Edge) as a > > pre-requisite in the synopsis by saying one needs to read it to learn > > about Mergemaster. > > > > There should only be one updating chapter. Cutting Edge was there > > first, but updating is maybe a better name. > > > > How do you feel about merging them back into one chapter? > > > > > Anyway, how does this patch look to you?: > > > > Everything else looks good, except I don't like that we now have two > > chapters for updating instead of one. I wasn't paying attention when > > that happened. =) Maybe just submit the new item for auditing while > > we sort out what to do about updating? > > > > - Murray > > > > Works for me. Let me work over a patch today (I should have > enough time) and get it out. :) This patch merges both chapters in a way I thought worked out best. Could probably use a bit of text in the intro but I'm not 100% sure. http://people.freebsd.org/~trhodes/patches/cutting-edge.diff Though I do remember why I started another chapter though, primarily because cutting-edge came off to me as "using CURRENT and/or test versions" rather than stable with bug fixes. :) Thanks, -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 19:07:09 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 310631065677 for ; Mon, 15 Dec 2008 19:07:09 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id AE5C58FC16 for ; Mon, 15 Dec 2008 19:07:08 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so166908ugs.39 for ; Mon, 15 Dec 2008 11:07:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=YShe/YBgkI+BSRD7qAJewIDxZawLz2KP03i7j0aamCg=; b=CAdM+Tvuum95bQuZ+Iao+cAWqPL4siebWntCNmhMXtoGssHEWxmfQ5BgOfTYCmSXAn 4rGYd6rcZoqwzSgPoYlkoIUO6/09pJHSD5sP4XmbMUwcUJ5Qz6X1BKB1fS5fzQ6N7LX2 EE3ZVEBc+XBIs531osl1LOGP2jHYyNKT27Mtk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=mmxeyKjjhpcSJVmyWvcehGfk7WWlAOuvcgxzLlUrMAlb1p1i1y/lUqHlmqChYIjZ5W hDqSjDUiblUGDXXuxrlCeN+f9SDdeTmXZAVrmyL3J+M+Eti9Ni0qjg8CQ0S7pZK2saWJ EezouOJwSkOqwvQFlnJuAmjGcp6QoGzp42sqc= Received: by 10.67.119.8 with SMTP id w8mr2142143ugm.3.1229368027361; Mon, 15 Dec 2008 11:07:07 -0800 (PST) Received: from atlantis.dyndns.org (athedsl-4376521.home.otenet.gr [79.130.55.185]) by mx.google.com with ESMTPS id a1sm711899ugf.50.2008.12.15.11.07.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Dec 2008 11:07:06 -0800 (PST) Message-ID: <4946AAD6.6050300@gmail.com> Date: Mon, 15 Dec 2008 21:07:02 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Tom Rhodes References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> In-Reply-To: <20081215134919.51a88d90.trhodes@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org, murray@stokely.org Subject: Re: Preface need update. 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, 15 Dec 2008 19:07:09 -0000 Tom Rhodes wrote: >> >> Works for me. Let me work over a patch today (I should have >> enough time) and get it out. :) >> > > This patch merges both chapters in a way I thought worked out > best. Could probably use a bit of text in the intro but I'm > not 100% sure. > > http://people.freebsd.org/~trhodes/patches/cutting-edge.diff > > Though I do remember why I started another chapter though, > primarily because cutting-edge came off to me as "using CURRENT > and/or test versions" rather than stable with bug fixes. :) > > Thanks, > > If these chapters are merged, I think we will have to rethink the "The Cutting Edge" title. The title is by itself intimidating for the beginning-intermediate user who is already convinced it is best for him to use "RELEASE" until he is comfortable with the system. And using freebsd-update is essential (and a rather easy task) at any user level. How about changing the chapter to something like "Updating and Upgrading FreeBSD"? The first sections could deal with security updates and minor / major version upgrades using freebsd-update. Later sections could deal with -STABLE and -CURRENT It would probably need more than a few rewrites and reorganization though From owner-freebsd-doc@FreeBSD.ORG Mon Dec 15 23:36:45 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FAAC1065672 for ; Mon, 15 Dec 2008 23:36:45 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 2BD288FC18 for ; Mon, 15 Dec 2008 23:36:44 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (c-68-83-213-214.hsd1.va.comcast.net [68.83.213.214]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBFNacPx030186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Dec 2008 18:36:39 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Mon, 15 Dec 2008 18:36:32 -0500 From: Tom Rhodes To: Manolis Kiagias Message-Id: <20081215183632.553d194b.trhodes@FreeBSD.org> In-Reply-To: <4946AAD6.6050300@gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org, murray@stokely.org Subject: Re: Preface need update. 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, 15 Dec 2008 23:36:45 -0000 On Mon, 15 Dec 2008 21:07:02 +0200 Manolis Kiagias wrote: > Tom Rhodes wrote: > >> > >> Works for me. Let me work over a patch today (I should have > >> enough time) and get it out. :) > >> > > > > This patch merges both chapters in a way I thought worked out > > best. Could probably use a bit of text in the intro but I'm > > not 100% sure. > > > > http://people.freebsd.org/~trhodes/patches/cutting-edge.diff > > > > Though I do remember why I started another chapter though, > > primarily because cutting-edge came off to me as "using CURRENT > > and/or test versions" rather than stable with bug fixes. :) > > > > Thanks, > > > > > If these chapters are merged, I think we will have to rethink the "The > Cutting Edge" title. The title is by itself intimidating for the > beginning-intermediate user who is already convinced it is best for him > to use "RELEASE" until he is comfortable with the system. And using > freebsd-update is essential (and a rather easy task) at any user level. > > How about changing the chapter to something like "Updating and Upgrading > FreeBSD"? > The first sections could deal with security updates and minor / major > version upgrades using freebsd-update. > Later sections could deal with -STABLE and -CURRENT > It would probably need more than a few rewrites and reorganization though I'm all about that. -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Tue Dec 16 02:35:54 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 009E71065673; Tue, 16 Dec 2008 02:35:54 +0000 (UTC) (envelope-from murray@stokely.org) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6612A8FC08; Tue, 16 Dec 2008 02:35:53 +0000 (UTC) (envelope-from murray@stokely.org) Received: by ewy14 with SMTP id 14so3987052ewy.19 for ; Mon, 15 Dec 2008 18:35:52 -0800 (PST) Received: by 10.210.124.8 with SMTP id w8mr8618480ebc.92.1229394952022; Mon, 15 Dec 2008 18:35:52 -0800 (PST) Received: by 10.210.71.14 with HTTP; Mon, 15 Dec 2008 18:35:51 -0800 (PST) Message-ID: <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> Date: Mon, 15 Dec 2008 18:35:51 -0800 From: "Murray Stokely" To: "Manolis Kiagias" In-Reply-To: <4946AAD6.6050300@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> Cc: Tom Rhodes , freebsd-doc@freebsd.org Subject: Re: Preface need update. 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, 16 Dec 2008 02:35:54 -0000 On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: > If these chapters are merged, I think we will have to rethink the "The > Cutting Edge" title. The title is by itself intimidating for the > beginning-intermediate user who is already convinced it is best for him > to use "RELEASE" until he is comfortable with the system. And using > freebsd-update is essential (and a rather easy task) at any user level. > > How about changing the chapter to something like "Updating and Upgrading > FreeBSD"? > The first sections could deal with security updates and minor / major > version upgrades using freebsd-update. > Later sections could deal with -STABLE and -CURRENT > It would probably need more than a few rewrites and reorganization though Yea I think this sounds good. Tom, can you include a link to the HTML with your next diff -- I find it easier to review big reorganizations in the built html form rather than the diffs. If there is really just too much content for one chapter then maybe the updating and upgrading chapter could still be split into two adjacent chapters -- one for the basics of updrading between releases with mergemaster and such, and a second with more complicated source upgrades to -CURRENT. - Murray From owner-freebsd-doc@FreeBSD.ORG Tue Dec 16 02:47:48 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D0B91065680; Tue, 16 Dec 2008 02:47:48 +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 67A248FC24; Tue, 16 Dec 2008 02:47:46 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl75-59.kln.forthnet.gr [77.49.122.59]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBG2lbD6000874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Dec 2008 04:47:43 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBG2lb54015556; Tue, 16 Dec 2008 04:47:37 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBG2law1015536; Tue, 16 Dec 2008 04:47:36 +0200 (EET) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: Hiroki Sato References: <87k5a63z2d.fsf@kobe.laptop> <871vwdahna.fsf@kobe.laptop> <20081213.014606.247395509.hrs@allbsd.org> Date: Tue, 16 Dec 2008 04:47:31 +0200 In-Reply-To: <20081213.014606.247395509.hrs@allbsd.org> (Hiroki Sato's message of "Sat, 13 Dec 2008 01:46:06 +0900 (JST)") Message-ID: <87myewygxo.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-MailScanner-ID: mBG2lbD6000874 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.294, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.10, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook 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: Tue, 16 Dec 2008 02:47:48 -0000 --=-=-= On Sat, 13 Dec 2008 01:46:06 +0900 (JST), Hiroki Sato wrote: > Giorgos Keramidas wrote > in <871vwdahna.fsf@kobe.laptop>: > ke> On Fri, 12 Dec 2008 09:58:28 +0100, Gabor PALI wrote: > ke> > Maybe you can have different versions in the .ent file, like you did > ke> > in case of mailing lists (defer the design decisions :)): > ke> > > ke> > WEP'> > ke> > WEP'> > ke> > ke> Heh, cool! I'll try to update the patch to include entities like this. > > Hmm, this is not directly related to your idea, but I did not noticed > that role attrib is used for adding the description so far. I think > this is incorrect from viewpoint of DocBook because it is for > classification of the element, not real content. In DocBook > vocabulary, cannot have such a expanded text, > unfortunately. > > As a workaround, how about using the following phrase: > > WEPWired Equivalent Privacy > > I use with role attrib here (probably this is the only > option which looks reasonable). The necessary changes to the > stylesheet and an SGML example of vm-design/article.sgml are attached > (indentation is incomplete, though). We need to rewrite the existing > elements, too. > > For entity definition, I like the following: > > FOODESC OF FOO'> > > Generating link to glossary, suppressing rendering of , or so > on can be controlled by stylesheet, so multiple definitions are not > needed at the level, IMHO. Very nice, thank you! :-) I like the idea of moving content from role="xxx" attributes to real content too. What would our next steps be for this? Perhaps something like this? * Commit this to doc/share/sgml/freebsd.dsl * Add share/sgml/acronyms.ent with some of the common entities * Update the existing role="" attributes to use the entities for those acronyms that need a tooltip, but a plain FOO for all the rest. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklHFsgACgkQ1g+UGjGGA7auKgCfQ2q6OYhw1WD7IBzd922f4pnu wcwAoLidPyoFF6xP63ZPvjtiKfBfvduJ =4gz6 -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-doc@FreeBSD.ORG Tue Dec 16 09:11:10 2008 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1286106564A for ; Tue, 16 Dec 2008 09:11:10 +0000 (UTC) (envelope-from claymore@eml.cc) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 702A78FC08 for ; Tue, 16 Dec 2008 09:11:10 +0000 (UTC) (envelope-from claymore@eml.cc) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id A77C91E7D25 for ; Tue, 16 Dec 2008 03:54:40 -0500 (EST) Received: from web6.messagingengine.com ([10.202.2.215]) by compute1.internal (MEProxy); Tue, 16 Dec 2008 03:54:40 -0500 Received: by web6.messagingengine.com (Postfix, from userid 99) id 7A02412834; Tue, 16 Dec 2008 03:54:40 -0500 (EST) Message-Id: <1229417680.20949.1290294601@webmail.messagingengine.com> X-Sasl-Enc: vLS+LLuoSYcxPrtz9FmRVpun4iqCtFL/mmjrgHqFk71t 1229417680 From: "mr g" To: doc@FreeBSD.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface Date: Tue, 16 Dec 2008 00:54:40 -0800 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: handbook question 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, 16 Dec 2008 09:11:10 -0000 Why isn't part 26 included in part4? Both seem to have to do with adding the latest code to freebsd. I don't get why part 26 is near networking? I only say because I was hunting around and then fond it with help of a friend on chat. I think it might be a good idea to roll it into part 4 so all updating of programs and the os are covered together. Thanks. -g -- http://www.fastmail.fm - I mean, what is it about a decent email service? From owner-freebsd-doc@FreeBSD.ORG Tue Dec 16 09:20:02 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AA9E106567B for ; Tue, 16 Dec 2008 09:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E6BC18FC1C for ; Tue, 16 Dec 2008 09:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBG9K1sQ087625 for ; Tue, 16 Dec 2008 09:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBG9K1hR087624; Tue, 16 Dec 2008 09:20:01 GMT (envelope-from gnats) Resent-Date: Tue, 16 Dec 2008 09:20:01 GMT Resent-Message-Id: <200812160920.mBG9K1hR087624@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, Murray Stokely Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4AD7106564A for ; Tue, 16 Dec 2008 09:15:34 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 937918FC18 for ; Tue, 16 Dec 2008 09:15:34 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id mBG9FYDu098685 for ; Tue, 16 Dec 2008 09:15:34 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id mBG9FYYg098684; Tue, 16 Dec 2008 09:15:34 GMT (envelope-from nobody) Message-Id: <200812160915.mBG9FYYg098684@www.freebsd.org> Date: Tue, 16 Dec 2008 09:15:34 GMT From: Murray Stokely To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/129671: New TCP chapter for Developer's Handbook (from rwatson meetbsd slides) 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, 16 Dec 2008 09:20:02 -0000 >Number: 129671 >Category: docs >Synopsis: New TCP chapter for Developer's Handbook (from rwatson meetbsd slides) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Dec 16 09:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Murray Stokely >Release: >Organization: FreeBSD Project >Environment: >Description: The Slides from Robert Watson's networking talk at MeetBSD 2008 would make the start of a nice TCP chapter to the Developer's Handbook. This should probably go in the Interprocess Communication of the book. Robert is exporting the diagrams from his slides into EPS so they could be used for this purpose. If someone has time to work with Robert, and to a lesser extent, myself, I think this would be a great addition to our online documentation corpus. http://www.watson.org/~robert/freebsd/2008meetbsd/ The arrival of high CPU core density, with commodity quad-core notebooks and 32-core servers, combined with 10gbps networking have transformed network design principles for operating systems. This talk will describe changes in the FreeBSD 6.x, 7.x, and forthcoming 8.x network stacks required to exploit multiple cores and serve 10gbps networks. The goal of the session will be to introduce the audience to general strategies used to improve performance, their rationales, and their impact on applications and users: Introduction to the SMPng Project and the follow-on Netperf Project Workloads and performance measurement Efficient primitives to support modern network stacks Multi-core and cache-aware network memory allocator Fine-grained network stack locking Load-balancing and contention-avoidance across multiple CPUs CPU affinity for network stack data structures TCP performance enhancements including TSO, LRO, and TOE Zero-copy Berkely Packet Filter (BPF) buffers Direct network stack dispatch from interrupt handlers Multiple input and output queues >How-To-Repeat: >Fix: Take the content from those slides, mark it up in DocBook, and submit it as a new chapter to the developers handbook covering TCP. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Tue Dec 16 09:47:35 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D38B1065672 for ; Tue, 16 Dec 2008 09:47:35 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id 200268FC0C for ; Tue, 16 Dec 2008 09:47:34 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so483424nfh.33 for ; Tue, 16 Dec 2008 01:47:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=AirbFLYUh6RVsiogebffBVyWTIBsUjZwpM1IhZffv1s=; b=Xl7/OTfIoVduqTnHlFvpGwkpzg+E1I2O+q6/TfeYo+wXaBZngcFpBrj7Vs3HTG1RUD 89Ij8UfdjU6RebPZKlEWtXimN2nW8j7IybBpFfOUN1mpivTl5tsYPHlPwBk+dH+gNNC3 wFWdv2LxbY++aI/E3MV3NtanQhoX5wxVrA0PU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=oOSIKmcQxd/4wp05zZuSAddvqXDmLAKudhgurwFpatxgJDF/b9dAQE/MzSytNWPRFA fVGvIR9De6OagkwvRqj2cZzIX8XgLaMDJWSQmi5/gibqysUVMxAgC7t21n1G+2sUNozE uKjiq+WQdX7YQPLmsgKEMqVoBDZpaTbwF+I3Y= Received: by 10.210.30.10 with SMTP id d10mr2253936ebd.127.1229420853617; Tue, 16 Dec 2008 01:47:33 -0800 (PST) Received: from theone.dyndns.org ([81.186.52.90]) by mx.google.com with ESMTPS id 5sm677043eyf.38.2008.12.16.01.47.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 16 Dec 2008 01:47:30 -0800 (PST) Message-ID: <49477925.50902@gmail.com> Date: Tue, 16 Dec 2008 11:47:17 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: mr g References: <1229417680.20949.1290294601@webmail.messagingengine.com> In-Reply-To: <1229417680.20949.1290294601@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: doc@FreeBSD.org Subject: Re: handbook question 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, 16 Dec 2008 09:47:35 -0000 mr g wrote: > Why isn't part 26 included in part4? Both seem to have to do with > adding the latest code to freebsd. I don't get why part 26 is > near networking? I only say because I was hunting around and then > fond it with help of a friend on chat. I think it might be a good > idea to roll it into part 4 so all updating of programs and the > os are covered together. Thanks. -g > > Chapter 4 refers to upgrading and ports and packages, which are third party applications as fas as FreeBSD is concerned. Chapter 26 deals with freebsd-update which updates the base system and portsnap which updates the Ports tree (but not installed programs). There is currently a discussion on merging chapter 26 with "The Cutting Edge" which also refers to base system upgrades. The resulting chapter will also be more appropriately named (something like Updating and Upgrading FreeBSD). From owner-freebsd-doc@FreeBSD.ORG Tue Dec 16 17:30:01 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 779F81065670 for ; Tue, 16 Dec 2008 17:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 53DC58FC0C for ; Tue, 16 Dec 2008 17:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBGHU1Jj055974 for ; Tue, 16 Dec 2008 17:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBGHU17g055971; Tue, 16 Dec 2008 17:30:01 GMT (envelope-from gnats) Resent-Date: Tue, 16 Dec 2008 17:30:01 GMT Resent-Message-Id: <200812161730.mBGHU17g055971@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, Geoff Fritz Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9784F1065670 for ; Tue, 16 Dec 2008 17:26:00 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 8640E8FC1F for ; Tue, 16 Dec 2008 17:26:00 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id mBGHQ03D004671 for ; Tue, 16 Dec 2008 17:26:00 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id mBGHQ0QV004669; Tue, 16 Dec 2008 17:26:00 GMT (envelope-from nobody) Message-Id: <200812161726.mBGHQ0QV004669@www.freebsd.org> Date: Tue, 16 Dec 2008 17:26:00 GMT From: Geoff Fritz To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/129684: gcache.8 man page 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, 16 Dec 2008 17:30:01 -0000 >Number: 129684 >Category: docs >Synopsis: gcache.8 man page missing >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 16 17:30:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Geoff Fritz >Release: 7.1-RC1 >Organization: >Environment: FreeBSD dev.null 7.1-RC1 FreeBSD 7.1-RC1 #0: Sun Dec 14 17:51:25 MST 2008 root@dev.null:/usr/obj/usr/src/sys/DESKTOP amd64 >Description: The man page, or any documentation, for the geom_cache/gcache program appears to be missing. >How-To-Repeat: type "man gcache" >Fix: I was able to locate a man page in the posted tarball attachment: http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20060704/9c368150/geom_cache.obj gcache.8 is dated Jul 04, 2006 The man page as it exists in that archive could be more informative, maybe including more of its stated purpose. Information about gcache can be found in the following thread: http://lists.freebsd.org/pipermail/freebsd-geom/2006-July/001342.html and also in the following commit message: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/geom/cache/g_cache.c#rev1.1 >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Wed Dec 17 03:19:38 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37E66106564A; Wed, 17 Dec 2008 03:19:38 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0E77F8FC1E; Wed, 17 Dec 2008 03:19:38 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBH3JbnX000915; Wed, 17 Dec 2008 03:19:37 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBH3JbS8000911; Wed, 17 Dec 2008 03:19:37 GMT (envelope-from murray) Date: Wed, 17 Dec 2008 03:19:37 GMT Message-Id: <200812170319.mBH3JbS8000911@freefall.freebsd.org> To: murray@FreeBSD.org, freebsd-doc@FreeBSD.org, murray@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/127842: list of hardware devices missing from the relnotes 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, 17 Dec 2008 03:19:38 -0000 Synopsis: list of hardware devices missing from the relnotes Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Wed Dec 17 03:19:26 UTC 2008 Responsible-Changed-Why: Will take a look. http://www.freebsd.org/cgi/query-pr.cgi?pr=127842 From owner-freebsd-doc@FreeBSD.ORG Wed Dec 17 03:20:45 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04144106564A; Wed, 17 Dec 2008 03:20:45 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CE48E8FC1A; Wed, 17 Dec 2008 03:20:44 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBH3Kiip007416; Wed, 17 Dec 2008 03:20:44 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBH3KilY007406; Wed, 17 Dec 2008 03:20:44 GMT (envelope-from murray) Date: Wed, 17 Dec 2008 03:20:44 GMT Message-Id: <200812170320.mBH3KilY007406@freefall.freebsd.org> To: murray@FreeBSD.org, freebsd-doc@FreeBSD.org, murray@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/127840: [patch] fix entity references in release/doc/en_US.ISO8859-1/hardware/article.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, 17 Dec 2008 03:20:45 -0000 Synopsis: [patch] fix entity references in release/doc/en_US.ISO8859-1/hardware/article.sgml Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Wed Dec 17 03:20:16 UTC 2008 Responsible-Changed-Why: Will build test this patch and submit to head after I get another pending change in. http://www.freebsd.org/cgi/query-pr.cgi?pr=127840 From owner-freebsd-doc@FreeBSD.ORG Wed Dec 17 03:25:43 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6614F1065670; Wed, 17 Dec 2008 03:25:43 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3B5F88FC0C; Wed, 17 Dec 2008 03:25:43 +0000 (UTC) (envelope-from murray@FreeBSD.org) Received: from freefall.freebsd.org (murray@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBH3PgZ6007898; Wed, 17 Dec 2008 03:25:42 GMT (envelope-from murray@freefall.freebsd.org) Received: (from murray@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBH3PgqA007894; Wed, 17 Dec 2008 03:25:42 GMT (envelope-from murray) Date: Wed, 17 Dec 2008 03:25:42 GMT Message-Id: <200812170325.mBH3PgqA007894@freefall.freebsd.org> To: mwm@mired.org, murray@FreeBSD.org, freebsd-doc@FreeBSD.org, murray@FreeBSD.org From: murray@FreeBSD.org Cc: Subject: Re: docs/102148: The description of which Intel chips have EM64T is out of date 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, 17 Dec 2008 03:25:43 -0000 Synopsis: The description of which Intel chips have EM64T is out of date State-Changed-From-To: open->patched State-Changed-By: murray State-Changed-When: Wed Dec 17 03:25:08 UTC 2008 State-Changed-Why: Commited to head. Will insta-mfc to 7.x and 7.1 branches momentarily. Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Wed Dec 17 03:25:08 UTC 2008 Responsible-Changed-Why: Commited to head. Will insta-mfc to 7.x and 7.1 branches momentarily. http://www.freebsd.org/cgi/query-pr.cgi?pr=102148 From owner-freebsd-doc@FreeBSD.ORG Wed Dec 17 05:14:41 2008 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83E0A1065675; Wed, 17 Dec 2008 05:14:41 +0000 (UTC) (envelope-from hrs@allbsd.org) Received: from mail.allbsd.org (unknown [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id F00138FC1B; Wed, 17 Dec 2008 05:14:40 +0000 (UTC) (envelope-from hrs@allbsd.org) Received: from delta.allbsd.org (p2191-ipbf1403funabasi.chiba.ocn.ne.jp [118.7.161.191]) (authenticated bits=128) by mail.allbsd.org (8.14.2/8.14.2) with ESMTP id mBH5ERCN096192; Wed, 17 Dec 2008 14:14:39 +0900 (JST) (envelope-from hrs@allbsd.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 mBH572JE005338; Wed, 17 Dec 2008 14:07:03 +0900 (JST) (envelope-from hrs@allbsd.org) Date: Wed, 17 Dec 2008 14:06:58 +0900 (JST) Message-Id: <20081217.140658.33303067.hrs@allbsd.org> To: keramida@FreeBSD.org From: Hiroki Sato In-Reply-To: <87myewygxo.fsf@kobe.laptop> References: <871vwdahna.fsf@kobe.laptop> <20081213.014606.247395509.hrs@allbsd.org> <87myewygxo.fsf@kobe.laptop> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.1 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Wed_Dec_17_14_06_58_2008_731)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.allbsd.org [133.31.130.32]); Wed, 17 Dec 2008 14:14:39 +0900 (JST) Cc: doc@FreeBSD.org Subject: Re: [PATCH] Adding elements to wlan Handbook 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: Wed, 17 Dec 2008 05:14:41 -0000 ----Security_Multipart(Wed_Dec_17_14_06_58_2008_731)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Giorgos Keramidas wrote in <87myewygxo.fsf@kobe.laptop>: ke> What would our next steps be for this? ke> ke> Perhaps something like this? ke> ke> * Commit this to doc/share/sgml/freebsd.dsl ke> ke> * Add share/sgml/acronyms.ent with some of the common entities ke> ke> * Update the existing role="" attributes to use the entities for those ke> acronyms that need a tooltip, but a plain FOO for ke> all the rest. Yes, after committing the bits to freebsd.dsl, generating title="foo" attr from will be stopped but no build error should occur. Adding acronyms.ent and updating existing elements must be atomic. I will send you another patch of freebsd.dsl tonight since the previous one is not commit-ready. -- | Hiroki SATO ----Security_Multipart(Wed_Dec_17_14_06_58_2008_731)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAklIiPIACgkQTyzT2CeTzy3jiwCdFOzqo3X38DxmxlszZF4WHH5p 3zYAn1JaXoCnfINyy55KmzK7FdffTgUE =plBN -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Dec_17_14_06_58_2008_731)---- From owner-freebsd-doc@FreeBSD.ORG Wed Dec 17 16:22:07 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56EE11065676; Wed, 17 Dec 2008 16:22:07 +0000 (UTC) (envelope-from loader@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3DBD88FC13; Wed, 17 Dec 2008 16:22:07 +0000 (UTC) (envelope-from loader@FreeBSD.org) Received: from freefall.freebsd.org (loader@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBHGM793035017; Wed, 17 Dec 2008 16:22:07 GMT (envelope-from loader@freefall.freebsd.org) Received: (from loader@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBHGM6b5035016; Wed, 17 Dec 2008 16:22:06 GMT (envelope-from loader) Date: Wed, 17 Dec 2008 16:22:06 GMT Message-Id: <200812171622.mBHGM6b5035016@freefall.freebsd.org> To: murray@FreeBSD.org References: <200812150128.mBF1Sehd094548@freefall.freebsd.org> <20081215130236.B5E051D703EF@mail.freebsdmall.com> From: loader In-Reply-To: <20081215130236.B5E051D703EF@mail.freebsdmall.com> (loader@freebsdmall.com's message of "Mon\, 15 Dec 2008 05\:02\:36 -0800 \(PST\)") MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: freebsd-doc@FreeBSD.org Subject: Re: docs/127923: Please mention qemu in the FreeBSD 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: Wed, 17 Dec 2008 16:22:07 -0000 --=-=-= loader wrote: > murray@FreeBSD.org wrote: > >> Synopsis: Please mention qemu in the FreeBSD Handbook >> >> Responsible-Changed-From-To: freebsd-doc->loader >> Responsible-Changed-By: murray >> Responsible-Changed-When: Mon Dec 15 01:28:02 UTC 2008 >> Responsible-Changed-Why: >> Loader, didn't you have some patchecs to add qemu here? Can you add >> something about it to the virtualization chapter? >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 > > Okay, I will try to add a section about Qemu these days. Juergen Lock sent me a patch. --=-=-= Content-Type: text/x-diff Content-Disposition: inline; filename=virtualization.diff Index: virtualization/chapter.sgml =================================================================== RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml,v retrieving revision 1.17 diff -u -p -r1.17 chapter.sgml --- virtualization/chapter.sgml 28 Jul 2008 14:33:51 -0000 1.17 +++ virtualization/chapter.sgml 18 Aug 2008 17:36:31 -0000 @@ -54,6 +54,11 @@ virtualization. + + How to run FreeBSD as guest in qemu + and as a qemu host. + + Before reading this chapter, you should: @@ -958,6 +963,211 @@ xenbr1 8000.feffffffffff no + + + What you should know about qemu + qemu's homepage is + http://bellard.org/qemu/, documentation gets + installed (on &os;) as + /usr/local/share/doc/qemu/qemu-doc.html and + /usr/local/share/doc/qemu/qemu-tech.html, and + there also is a manpage. + Places to check other than the official documentation: + + + The pkg-message of the relevant &os; + port (can also be displayed via + &prompt.user; pkg_info -D qemu\* |less + if a qemu port is installed.) + + + The + unofficial #qemu FAQ (many of the Linux-related notes + there also apply to &os; hosts.). + + + The + qemu forum that also has howtos/patches/svn snapshots. + (actually at the time of writing the snapshots are apparently + still checked out from cvs and are old as such, you can go + to a + git mirror of the qemu svn to get snapshots, note + however that upstream qemu sources don't build on &os; without + changes.) + + + The + qemu-devel mailing list archive. + + + The + freebsd-emulation mailing list archive. + + + If you still have a question after checking the above you can + join the official qemu irc channel + + #qemu on freenode irc (see maybe the + + Wikipedia article on irc and + + http://freenode.net/using_the_network.shtml + if you are new to irc), or post a question on the + freebsd-emulation mailing list if the question is + &os;-specific, or on the + qemu-devel mailing list if it concerns qemu in general. + Or you can join the mentioned + qemu webforum and post the question there. + General things you should know: + + + For best results always try the latest version + (0.9.1 as of this writing) + or even an svn checkout or on &os; the + emulators/qemu-devel + port. + + + qemu's userland networking (-net user, + also called slirp, + which is the default) is not really stable on 64 bit hosts, + so you probably need to use tuntap there (see also + + if this is for a &os; host.) + + + You need to use qemu-system-x86_64 + if you want to emulate + amd64 guests, or if you want to use kqemu on amd64 hosts. + (actually the latter is no longer true for qemu svn and the + emulators/qemu-devel + port at the time of writing.) + + + You can try pcnet, + i82557b or e1000 + (the latter not yet + in 0.9.1), especially with BSD/Linux guests as alternate + emulated nics in place of the default + ne2kpci, they should be a little faster/use less guest cpu. + + + You can also try -drive if=scsi,file=.. + instead of -hdb ... + to specify additional image files (qemu's bios can't boot + from SCSI yet at the time of writing), SCSI should perform + better than IDE (especially with Linux guests, less + with &os;.) + + + And you can try -vnc ... if the host + or qemu build lacks X and + -nographic or -curses + (the latter not yet in 0.9.1) isn't enough + (-nographic needs the guest configured for + serial console.) + -vnc works best with an en-us keymap on the host. + You can + use e.g. the &os; net/tightvnc + port with qemu. The X keymap on the host can be changed + temporarily using + setxkbmap, see its manpage for details. + + + iso images are faster than physical CD/DVD drives. + + + + + + &os; as a qemu guest + + First a few things you should know: + + + &os;/amd64 guests may need a patch to qemu: + i386-hard-interrupt-generation-bug-fix + (unfortunately not yet committed to mainline qemu, or + I missed it... the &os; + emulators/qemu-devel port + has it tho.) + + + Debian/Ubuntu (and their offsprings) have a record of + shipping partially broken + qemu bioses, so if you have problems using a packaged qemu on + these distros also try using the bios found in that qemu + version's(!) source tarball (pc-bios/bios.bin + in there) instead of the one installed by your distro + package. + + + + + An example how to install &os; 7.0 as a qemu guest + First, we create an empty raw 5 GB image: + &prompt.user; qemu-img create 7.0.img 5G + (You may want -f qcow2 for qcow2 format + if you have to/want to avoid sparse files on the host - + some backup apps like &man.bsdtar.1; + don't support them properly, others like gtar or star do if passed + appropriate flags - qcow2 might be slower than raw.) + Next, we boot sysinstall with the image: + &prompt.user; qemu -m 256 -cdrom 7.0-RELEASE-i386-disc1.iso -hda 7.0.img -boot d -monitor stdio + Now follow the instructions in like + as if you would install a real machine using CD media... + Click into the guest window to access the guest mouse pointer + and hit Alt + Ctrl to leave the guest window + mouse grab. If you use the default usermode networking (aka slirp) + like in the above example the guest should have network if you + configure it to use DHCP, so if you want you could probably + also use a bootonly iso instead of disc1 and do a network install. + (&man.ping.8 doesn't work with slirp tho.) + When finished, select `exit install' in sysinstall to reboot, + and when you see the guest booting the iso again, type + q in qemu's monitor (or + killall qemu on another host shell if you are + using -curses, like + when you have no X on the host.) + Now, we should be able to boot the installed image: + &prompt.user; qemu -m 256 -cdrom 7.0-RELEASE-i386-disc1.iso -hda 7.0.img -boot c -monitor stdio + (You can omit -cdrom if you don't plan to + access the install iso from the installed guest.) + Now you should see a normal boot like on a freshly installed + box, all the way up to your first login: prompt. If you plan to + use this guest with -nographic later on, + now is the time to configure it for a serial console: + (both in the guest:) + &prompt.root; echo console=\"comconsole\" >>/boot/loader.conf + &prompt.root; sed -i -e '/^ttyd0/s/off/on/' /etc/ttys + As always with virtualization, lowering + helps performance also with qemu, so you might want to do that too: + (in the guest:) + &prompt.root; echo kern.hz=100 >>/boot/loader.conf + When you are finished with the guest, shut it down, this should + make qemu quit gracefully (in the guest:) + &prompt.root; shutdown -p now + If you just configured for serial console, you can now boot the + guest with -nographic: + &prompt.user; qemu -m 256 -hda 7.0.img -boot c -nographic + With -nographic, the guest console and qemu's + monitor are multiplexed on qemu's tty, hit + Ctrl + a and then h + to show a small help. + + @@ -968,7 +1178,149 @@ xenbr1 8000.feffffffffff no use older versions of VMware in this capacity. Work is also ongoing in getting &xen; to work as a host environment on FreeBSD. + qemu also often works, although some guests + work better than others, and the kqemu accellerator kernel module + still works better (i.e. with more guests) on i386 hosts than + on amd64 - although the latter has improved with qemu svn at the time of + writing, a snapshot of which is available as the + emulators/qemu-devel port. + (But it is still slower than VMware.) + Also kqemu was broken for a long time on amd64 SMP, so + be sure to use recent qemu and kqemu ports if your host is such. + + &os; as a qemu Host + + Notes about the current state of affairs re. qemu on &os; hosts + can always be found in the pkg-message + of the relevant qemu port (there are two at the moment, + emulators/qemu and + emulators/qemu-devel, + the first is usually the latest release and the latter is an + svn snapshot). If you already have a qemu port installed you can + also view those notes via: + &prompt.user; pkg_info -D qemu\* |less + Here are a few facts that are noted there which are unlikely to + change: + + + If you want to use qemu with -m 512 + or larger on i386 &os; 6.x hosts you need to increase the + kern.maxdsiz + tunable in the host's &man.loader.conf.5 since the default + is 512 MB, and qemu needs memory for itself also. + (&os; 7.0 and up use jemalloc which uses &man.mmap.2 and + isn't affected by kern.maxdsiz anymore.) + + + If you use kqemu make sure your kqemu.ko + is always in sync + with the kernel (like with any kld installed outside of base), + i.e. rebuild the + emulators/kqemu-kmod + port (or + emulators/kqemu-kmod-devel + depending on which qemu port you use) whenever you update + the kernel - especially + if you are switching branches or are following a -stable or even + -current branch! + + + qemu now uses &man.aio.4 at least for ide dma, so if you get + `Invalid system call' crashes that is because aio is not + (kld)loaded. + + + You can enable autoloading of kqemu (and aio) at boot by + adding a line + kqemu_enable=YES + to /etc/rc.conf (assuming you have built + the qemu port with the kqemu knob enabled of course). + + + + Simple Linux guest examples + As an example, we run the well known Knoppix Linux live-CD/DVD in qemu: + &prompt.user; qemu -m 256 -cdrom KNOPPIX_V5.3.1DVD-2008-03-26-EN.iso -boot d -monitor stdio -soundhw es1370 + (Omit -soundhw es1370 if you don't have sound + configured on the host.) + If you want a smaller download you can also try Damn Small Linux + (around 50 MB): + &prompt.user; qemu -m 256 -cdrom dsl-4.3.iso -boot d -monitor stdio -soundhw es1370 + Again, click into the guest window to access the guest + mouse pointer and + hit Alt + Ctrl to leave the guest window + mouse grab. + + + Simple Example for using qemu tuntap networking on + &os; Hosts + In cases where you want a qemu guest to appear as a seperate + (virtual) host on your network, or when you are on an amd64 host + where the default usermode networking doesn't quite work, or + when you are simply concerned about virtual network performance, + you may want to use tuntap networking. + The idea here is to have qemu talk to a &man.tap.4; interface, + which you (usually) bridge with your host's physical interface, + and that qemu then passes the traffic of the emulated nic that + the guest uses on. Since you (usually) don't want to run qemu + as root you first need to setup permissions on the tap device in + &man.devfs.conf.5; so that qemu running as your user can acess it. + For example add: + own tap0 <username or uid> + Next you figure out two IPs in an unused sub-subnet of your + host's network, one for the tap interface and the other for the + guest (this is important so the host itself can talk to the guest's + emulated nic properly), and then edit qemu's tuntap setup script + that gets executed after qemu opens a tap device, + /usr/local/etc/qemu-ifup to read something + like this: + #!/bin/sh +sudo /sbin/ifconfig $1 <IP for the tap interface> netmask <sub-subnet's netmask> +case "`/sbin/ifconfig bridge0`" in + *" $1 "*) ;; # already in the bridge + *) sudo /sbin/ifconfig bridge0 addm $1 ;; +esac + (sudo is in ports as + security/sudo, if your user + is in the wheel group you can add a line + %wheel ALL=/sbin/ifconfig + to /usr/local/etc/sudoers for this to work.) + Then you load the if_tap and if_bridge klds, restart devfs, set the + net.link.tap.user_open sysctl, create + the bridge and add your host's physical interface to it: + &prompt.root; kldload if_tap if_bridge + &prompt.root; /etc/rc.d/devfs restart + &prompt.root; sysctl net.link.tap.user_open=1 + &prompt.root; ifconfig bridge0 create + &prompt.root; ifconfig bridge0 addm <host's physical interface> up + Now you should be ready to start qemu: + &prompt.user; qemu -m 256 -hda guest.img -boot c -net nic -net tap,ifname=tap0 + In the guest configure the emulated nic with the IP you selected + above (different than the tap interface's IP) and the netmask of + your host's physical interface, and the rest (gateway, dns) like you + would configure any other host on your physical network. + (Note that if you have more than one qemu guest on a network + you need to make sure they each use a different macaddress, + the macaddress can be set via + -net nic,macaddr=....) + If you would like to make these settings permanent, add + the following to + &man.loader.conf.5; to load if_tap.ko and + if_bridge.ko at boot: + if_tap_load=YES +if_bridge_load=YES + (or put them in your kernel config), add + net.link.tap.user_open=1 + to &man.sysctl.conf.5;, and add the bridge configuration to + &man.rc.conf.5;: + cloned_interfaces="bridge0" +ifconfig_bridge0="addm <host's physical interface> up" + + --=-=-=-- From owner-freebsd-doc@FreeBSD.ORG Wed Dec 17 16:26:24 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 246E81065676; Wed, 17 Dec 2008 16:26:24 +0000 (UTC) (envelope-from loader@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0BCD48FC17; Wed, 17 Dec 2008 16:26:24 +0000 (UTC) (envelope-from loader@FreeBSD.org) Received: from freefall.freebsd.org (loader@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBHGQO7W035214; Wed, 17 Dec 2008 16:26:24 GMT (envelope-from loader@freefall.freebsd.org) Received: (from loader@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBHGQL0K035212; Wed, 17 Dec 2008 16:26:21 GMT (envelope-from loader) Date: Wed, 17 Dec 2008 16:26:21 GMT Message-Id: <200812171626.mBHGQL0K035212@freefall.freebsd.org> To: murray@FreeBSD.org References: <200812150128.mBF1Sehd094548@freefall.freebsd.org> <20081215130236.B5E051D703EF@mail.freebsdmall.com> From: loader In-Reply-To: <20081215130236.B5E051D703EF@mail.freebsdmall.com> (loader@freebsdmall.com's message of "Mon\, 15 Dec 2008 05\:02\:36 -0800 \(PST\)") MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: freebsd-doc@FreeBSD.org Subject: Re: docs/127923: Please mention qemu in the FreeBSD 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: Wed, 17 Dec 2008 16:26:24 -0000 --=-=-= loader wrote: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 And I reworded some parts of Juergen's patch with the help of murray@. --=-=-= Content-Type: text/x-diff Content-Disposition: inline; filename=virtualization.diff Index: chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml,v retrieving revision 1.17 diff -u -r1.17 chapter.sgml --- chapter.sgml 28 Jul 2008 14:33:51 -0000 1.17 +++ chapter.sgml 17 Dec 2008 16:13:40 -0000 @@ -54,6 +54,11 @@ virtualization. + + How to run FreeBSD as guest in qemu + and as a qemu host. + + Before reading this chapter, you should: @@ -969,6 +974,327 @@ Work is also ongoing in getting &xen; to work as a host environment on FreeBSD. + + + + + Juergen + Lock + Contributed by + + + + <application>QEMU</application> on &os; as Host + + QEMU + is a generic processor emulator using dynamic binary translation + to achieve a reasonable emulation speed. + + + Installation + + There are two QEMU ports in the &os; + Ports tree at the moment: + emulators/qemu + is usually the latest release, and + emulators/qemu-devel. + is an svn snapshot. For best results try the latest version + available as a &os; package, or alternatively try the + emulators/qemu-devel. + + Install emulators/qemu-devel + with the following commands: + + &prompt.root; cd /usr/ports/emulators/qemu-devel +&prompt.root; make install clean + + If the QEMU port is built with the + kqemu knob enabled, load the kqemu kernel module: + + &prompt.root; kldload kqemu + + And kqemu can be loaded automatically at boot by adding + the following line to /etc/rc.conf: + + kqemu_enable="YES" + + Please make sure the kqemu.ko is always in sync + with the kernel like with any kld installed outside of the base. Rebuild + the port emulators/kqemu-kmod or + emulators/kqemu-kmod-devel + whenever you update the kernel. + + QEMU now uses &man.aio.4; at least + for IDE DMA, otherwise QEMU crashes + with Invalid system call: + + &prompt.root; kldload aio + + + If you want to run QEMU with + 512 or larger on &os; 6.3 i386 hosts, + kern.maxdsiz needs to be increased in + /boot/loader.conf since the default + value is 512 MB, and QEMU needs + memory for itself also. &os; 7.0 and up use jemalloc which uses + &man.mmap.2; and isn't affected by + kern.maxdsiz anymore. + + + + + An example of installing &os; 7.0 as a + <application>QEMU</application> guest + + First, create an empty raw 5 GB image: + + &prompt.user; qemu-img create 7.0.img 5G + + + qcow2 is the QEMU image format, + use the qcow2 option to avoid sparse files + on the host. Some backup applications like &man.bsdtar.1; don't + support them properly, others like gtar + or star do if passed appropriate flags, + qcow2 format might be slower than raw format. + + + Next, boot sysinstall with the image: + + &prompt.user; qemu -m 256 -cdrom 7.0-RELEASE-i386-disc1.iso -hda 7.0.img -boot d -monitor stdio + + + You need to run qemu-system-x86_64 + if you want to emulate a amd64 guest. + + + Now follow the instructions in like + as if you would install a real machine using CD media. + Click into the guest window to access the guest mouse pointer + and hit Alt + Ctrl to leave the guest window + mouse grab. If you use the default usermode networking (aka slirp) + like in the above example the guest should have network if you + configure it to use DHCP, so if you want you could probably + also use a bootonly iso instead of disc1 and do a network install. + (&man.ping.8; doesn't work with slirp though.) + + When finished, select exit install in sysinstall to reboot, + and when the guest booting the ISO again, type + q in QEMU's monitor or + killall qemu on another host shell if you are + using , like when you have no X11 on the + host. + + Now, boot the installed image: + + &prompt.user; qemu -m 256 -cdrom 7.0-RELEASE-i386-disc1.iso -hda 7.0.img -boot c -monitor stdio + + Now you should see a normal boot like on a freshly installed + box, all the way up to your first login prompt. If you plan to + use this guest with later on, + now is the time to configure it for a serial console in the guest: + + &prompt.root; echo console=\"comconsole\" >>/boot/loader.conf +&prompt.root; sed -i -e '/^ttyu0/s/off/on/' /etc/ttys + + As always with virtualization, lowering kern.hz + helps performance also with QEMU: + + &prompt.root; echo kern.hz=100 >>/boot/loader.conf + + When you are finished with the guest, shut it down, this should + make QEMU quit gracefully: + + &prompt.root; shutdown -p now + + If the serial console is configured, now you can boot the + guest with : + + &prompt.user; qemu -m 256 -hda 7.0.img -boot c -nographic + + With , the guest console and + QEMU's monitor are multiplexed on + QEMU's tty, hit + Ctrl + a and then + h to show a small help. + + + Qemu can emulate several different mode of network card, + try , + or , they should be faster + and use less guest CPU than the + default . + + With the display + option, QEMU will listen on + VNC display display + and redirect the VGA display over the + VNC session. If the host or + QEMU build lacks X11 and + or + is not an available option. works best with + an en-us keymap on the host. + Use the port net/tightvnc + with QEMU. The X keymap on the host + can be changed temporarily using setxkbmap, + see the manual pages for more information. + + + + + &linux; guest examples + + As an example, we run the well known Knoppix &linux; live-CD/DVD in qemu: + + &prompt.user; qemu -m 256 -cdrom KNOPPIX_V5.3.1DVD-2008-03-26-EN.iso -boot d -monitor stdio -soundhw es1370 + + In this example we launched QEMU + with an ES1370 sound card enabled for the guest OS. + + Click into the guest window to access the guest + mouse pointer and hit Alt + Ctrl to leave the guest window + mouse grab. + + + Debian/Ubuntu (and their offsprings) have a record of + shipping partially broken QEMU + bioses, so if you have problems using a packaged + QEMU these distros also try + using the bios found in that QEMU + version's source tarball (pc-bios/bios.bin + in there) instead of the one installed by your distro + package. + + + + + Simple Example for using <application>QEMU</application> + tuntap networking on &os; Hosts + + In cases where you want a QEMU + guest to appear as a seperate (virtual) host on your network, + or when you are on an amd64 host where the default usermode + networking doesn't quite work, or when you are simply concerned + about virtual network performance, you may want to use tuntap + networking. + + The idea here is to have QEMU + talk to a &man.tap.4; interface, which bridge with your host's + physical interface, and that QEMU + then passes the traffic of the emulated NIC that the guest + uses on. Since you don't want to run QEMU + as root you first need to setup permissions on the tap device in + &man.devfs.conf.5; so that QEMU + running as your user can acess it. For example add: + + own tap0 <username or uid> + + Next figure out two IPs in an unused sub-subnet of your + host's network, one for the tap interface and the other for the + guest (this is important so the host itself can talk to the guest's + emulated nic properly), and then edit qemu's tuntap setup script + that gets executed after qemu opens a tap device, + /usr/local/etc/qemu-ifup to read something + like this: + + #!/bin/sh +sudo /sbin/ifconfig $1 <IP for the tap interface> netmask <sub-subnet's netmask> +case "`/sbin/ifconfig bridge0`" in + *" $1 "*) ;; # already in the bridge + *) sudo /sbin/ifconfig bridge0 addm $1 ;; +esac + + sudo is in ports as + security/sudo, if your user + is in the wheel group you can add the following line to + /usr/local/etc/sudoers: + + %wheel ALL=/sbin/ifconfig + + Then load the kernel modules if_tap.ko and + if_bridge.ko, restart devfs, set the + net.link.tap.user_open sysctl, create + the bridge and add your host's physical interface to it: + + &prompt.root; kldload if_tap if_bridge +&prompt.root; /etc/rc.d/devfs restart +&prompt.root; sysctl net.link.tap.user_open=1 +&prompt.root; ifconfig bridge0 create +&prompt.root; ifconfig bridge0 addm <host's physical interface> up + + Now start the QEMU: + + &prompt.user; qemu -m 256 -hda guest.img -boot c -net nic -net tap,ifname=tap0 + + Then configure the NIC in the guest like + other hosts on your physical network. + + + If you have more than one QEMU + guest on a network you need to make sure they use different + MAC addresses, the MAC address can be set via + . + + + To make the settings permanent, add the following lines + in /boot/loader.conf: + + if_tap_load="YES" +if_bridge_load="YES" + + Add the following line in /etc/sysctl.conf: + + net.link.tap.user_open=1 + + And add the bridge configuration in /etc/rc.conf: + + cloned_interfaces="bridge0" +ifconfig_bridge0="addm <host's physical interface> up" + + + + User Documentation and Resources + + The QEMU package + includes qemu(1) man page and the following locally installed html + documents: + + + /usr/local/share/doc/qemu/qemu-doc.html + /usr/local/share/doc/qemu/qemu-tech.html + + + Places to check other than the official documentation: + + + + emulators/qemu-devel + + pkg-message + + + The + freebsd-emulation mailing list archive. + + + The + qemu forum + has howtos, patches, and code snapshots. Note, however + that the qemu sources won't build on &os; without some changes. + + + The + qemu-devel mailing list archive. + + + --=-=-=-- From owner-freebsd-doc@FreeBSD.ORG Wed Dec 17 22:30:03 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 866A81065675 for ; Wed, 17 Dec 2008 22:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 57C258FC19 for ; Wed, 17 Dec 2008 22:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBHMU3HR017832 for ; Wed, 17 Dec 2008 22:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBHMU3g8017829; Wed, 17 Dec 2008 22:30:03 GMT (envelope-from gnats) Resent-Date: Wed, 17 Dec 2008 22:30:03 GMT Resent-Message-Id: <200812172230.mBHMU3g8017829@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, Dmitry Marakasov Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9047D1065670 for ; Wed, 17 Dec 2008 22:28:16 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 0CEDB8FC13 for ; Wed, 17 Dec 2008 22:28:15 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LD4sI-0007lL-3e for FreeBSD-gnats-submit@freebsd.org; Thu, 18 Dec 2008 01:28:14 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 224D8C9F for ; Thu, 18 Dec 2008 01:26:45 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id C42191702D; Thu, 18 Dec 2008 01:27:47 +0300 (MSK) Message-Id: <20081217222747.C42191702D@hades.panopticon> Date: Thu, 18 Dec 2008 01:27:47 +0300 (MSK) From: Dmitry Marakasov To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: docs/129723: [PATCH] fix 5 typos X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dmitry Marakasov List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Dec 2008 22:30:03 -0000 >Number: 129723 >Category: docs >Synopsis: [PATCH] fix 5 typos >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 17 22:30:02 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Dmitry Marakasov >Release: FreeBSD 7.0-RELEASE-p1 i386 >Organization: >Environment: System: FreeBSD hades.panopticon 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #1: Wed Jun 25 15:36:22 MSD 2008 root@hades.panopticon:/usr/obj/usr/src/sys/HADES i386 >Description: Fix 2 typos in English docs and 3 typos in Russian. >How-To-Repeat: >Fix: --- doc.patch begins here --- Index: en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v retrieving revision 1.417 diff -u -r1.417 chapter.sgml --- en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml 12 Dec 2008 06:06:03 -0000 1.417 +++ en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml 17 Dec 2008 21:47:27 -0000 @@ -1719,7 +1719,7 @@ IBSS mode, also called ad-hoc mode, is designed for point to point connections. For example, to establish an ad-hoc network between the machine A and the machine - B we will just need to choose two IP adresses + B we will just need to choose two IP addresses and a SSID. On the box A: Index: en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml,v retrieving revision 1.110 diff -u -r1.110 chapter.sgml --- en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml 4 Dec 2008 15:21:04 -0000 1.110 +++ en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml 17 Dec 2008 21:47:47 -0000 @@ -4175,7 +4175,7 @@ www/mod_perl and a statically compiled version is available in www/apache13-modperl. - mod_perl 2.0 is avaliable in + mod_perl 2.0 is available in www/mod_perl2. Index: ru_RU.KOI8-R/articles/multi-os/article.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/ru_RU.KOI8-R/articles/multi-os/article.sgml,v retrieving revision 1.1 diff -u -r1.1 article.sgml --- ru_RU.KOI8-R/articles/multi-os/article.sgml 10 Jun 2005 08:26:32 -0000 1.1 +++ ru_RU.KOI8-R/articles/multi-os/article.sgml 17 Dec 2008 22:17:45 -0000 @@ -654,7 +654,7 @@ ÓÒÁÚÕ ÐÏÓÌÅ MBR (0 ÃÉÌÉÎÄÒ, 0 ÇÏÌÏ×ËÁ, 2 ÓÅËÔÏÒ). åÓÌÉ × ÐÒÏÇÒÁÍÍÅ sysinstall ×Ù ÕËÁÖÉÔÅ ÐÏÌÎÏÓÔØÀ Ó×ÏÂÏÄÎÙÊ ÄÉÓË ÉÌÉ Ó Ó×ÏÂÏÄÎÙÍ ÐÒÏÓÔÒÁÎÓÔ×ÏÍ × ÎÁÞÁÌÅ, ÔÏ FreeBSD ÓÏÚÄÁÓÔ - ÒÁÄÅÌ, ÎÁÞÉÎÁÀÝÉÊÓÑ ÉÍÅÎÎÏ Ó ÓÁÍÏÇÏ ÎÁÞÁÌÁ ÄÉÓËÁ (ÔÁË ÂÙÌÏ, + ÒÁÚÄÅÌ, ÎÁÞÉÎÁÀÝÉÊÓÑ ÉÍÅÎÎÏ Ó ÓÁÍÏÇÏ ÎÁÞÁÌÁ ÄÉÓËÁ (ÔÁË ÂÙÌÏ, ËÏÇÄÁ Ñ × ÐÏÓÌÅÄÎÉÊ ÒÁÚ ÚÁÎÉÍÁÌÓÑ ÜÔÉÍ ×ÏÐÒÏÓÏÍ). úÁÔÅÍ, ËÏÇÄÁ ×Ù ÂÕÄÅÔÅ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ ÍÅÎÅÄÖÅÒ ÚÁÇÒÕÚËÉ, ÔÒÅÂÕÀÝÉÊ ÎÅÓËÏÌØËÏ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÓÅËÔÏÒÏ×, ÔÏ ×Ù ÚÁÔÒÅÔÅ ÎÁÞÁÌØÎÙÅ Index: ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml,v retrieving revision 1.2 diff -u -r1.2 chapter.sgml --- ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml 6 May 2005 18:56:15 -0000 1.2 +++ ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml 17 Dec 2008 22:15:40 -0000 @@ -49,7 +49,7 @@ ÏÞÅÎØ ÓÉÌØÎÏ ÕÐÒÏÝÁÅÔ ÒÁÂÏÔÕ ÐÏ ÉÈ ÕÓÔÁÎÏ×ËÅ . ðÅÒÅÄ ÔÅÍ, ËÁË ×Ù ÓÍÏÖÅÔÅ ÒÁÂÏÔÁÔØ Ó ËÁËÉÍÉ-ÌÉÂÏ ÐÒÉÍÅÒÁÍÉ ÉÚ - ÐÏÓÌÅÄÕÀÝÉÈ ÇÌÁ×, ×ÁÍ ÎÕÄÎÏ ÕÓÔÁÎÏ×ÉÔØ ÜÔÉ ÐÒÏÇÒÁÍÍÎÙÅ ÓÒÅÄÓÔ×Á. òÅÁÌØÎÏÅ + ÐÏÓÌÅÄÕÀÝÉÈ ÇÌÁ×, ×ÁÍ ÎÕÖÎÏ ÕÓÔÁÎÏ×ÉÔØ ÜÔÉ ÐÒÏÇÒÁÍÍÎÙÅ ÓÒÅÄÓÔ×Á. òÅÁÌØÎÏÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÜÔÉÈ ÉÎÓÔÒÕÍÅÎÔÏ× ÏÓ×ÅÝÅÎÏ × ÓÌÅÄÕÀÝÉÈ ÇÌÁ×ÁÈ. Index: ru_RU.KOI8-R/books/porters-handbook/book.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/ru_RU.KOI8-R/books/porters-handbook/book.sgml,v retrieving revision 1.25 diff -u -r1.25 book.sgml --- ru_RU.KOI8-R/books/porters-handbook/book.sgml 20 Oct 2006 09:24:16 -0000 1.25 +++ ru_RU.KOI8-R/books/porters-handbook/book.sgml 17 Dec 2008 22:13:18 -0000 @@ -7078,7 +7078,7 @@ - 5.1-CURRENT aÐÏÓÌÅ ÄÏÂÁ×ÌÅÎÉÑ ÐÏÌÅÊ lockfunc É lockfuncarg + 5.1-CURRENT ÐÏÓÌÅ ÄÏÂÁ×ÌÅÎÉÑ ÐÏÌÅÊ lockfunc É lockfuncarg × &man.bus.dma.tag.create.9;. 501102 --- doc.patch ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Thu Dec 18 04:22:16 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF63C1065673 for ; Thu, 18 Dec 2008 04:22:16 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id B61EA8FC16 for ; Thu, 18 Dec 2008 04:22:16 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (net-ix.gw.ai.net [205.134.160.6]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBI4MFSr046734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Dec 2008 23:22:15 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Wed, 17 Dec 2008 23:22:07 -0500 From: Tom Rhodes To: "Murray Stokely" Message-Id: <20081217232207.53615962.trhodes@FreeBSD.org> In-Reply-To: <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org Subject: Cutting edge -> Upgrading (was: Re: Preface need update.) 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, 18 Dec 2008 04:22:17 -0000 Hi Murray, Manolis, On Mon, 15 Dec 2008 18:35:51 -0800 "Murray Stokely" wrote: > On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: > > If these chapters are merged, I think we will have to rethink the "The > > Cutting Edge" title. The title is by itself intimidating for the > > beginning-intermediate user who is already convinced it is best for him > > to use "RELEASE" until he is comfortable with the system. And using > > freebsd-update is essential (and a rather easy task) at any user level. > > > > How about changing the chapter to something like "Updating and Upgrading > > FreeBSD"? > > The first sections could deal with security updates and minor / major > > version upgrades using freebsd-update. > > Later sections could deal with -STABLE and -CURRENT > > It would probably need more than a few rewrites and reorganization though > > Yea I think this sounds good. Tom, can you include a link to the HTML > with your next diff -- I find it easier to review big reorganizations > in the built html form rather than the diffs. > > If there is really just too much content for one chapter then maybe > the updating and upgrading chapter could still be split into two > adjacent chapters -- one for the basics of updrading between releases > with mergemaster and such, and a second with more complicated source > upgrades to -CURRENT. > > - Murray > Apologies for this tardy reply, but I've recently come down with some kind of a bug. Anyway, this is what I have right now: http://people.freebsd.org/~trhodes/doc/latest-handbook.diff http://people.freebsd.org/~trhodes/doc/handbook/ The diff contains my Updating chapter placed above the current cutting-edge content along with some alterations to make the documentation flow a bit. Surely another update or two will be needed to perfect this version, but I think it looks pretty decent as it is now. This also contains some things I've been working on lately: o Added a warning about loss of data in GEOM chapter, covers a PR about gmirror; o Add a new section on syslog network monitoring to network-servers; o Add the Audit chapter to preface.sgml and mark up DTrace with &dtrace. The "additional" parts have already been reviewed by rene and pgj. An earlier version of the preface.sgml part was reviewed by Murray already. The handbook/ directory has a built version of the handbook with that diff applied. If there are no objections I'm perfectly cool with: Patching the preface, geom, and network-servers chapters; Putting in a repo copy request for cutting-edge/chapter.sgml to upgrading/chapter.sgml; Commit follow up to note the repocopy; Commit this version of cutting edge to upgrading/chapter.sgml; Final commit to remove cutting-edge and updating chapters from the build and the like. I'm positive someone will come up with a better way of handling this but I'm tired and a bit off. -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Thu Dec 18 09:34:54 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A77C1065677; Thu, 18 Dec 2008 09:34:54 +0000 (UTC) (envelope-from maxim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1C5E58FC12; Thu, 18 Dec 2008 09:34:54 +0000 (UTC) (envelope-from maxim@FreeBSD.org) Received: from freefall.freebsd.org (maxim@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBI9YswK023730; Thu, 18 Dec 2008 09:34:54 GMT (envelope-from maxim@freefall.freebsd.org) Received: (from maxim@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBI9YswM023726; Thu, 18 Dec 2008 09:34:54 GMT (envelope-from maxim) Date: Thu, 18 Dec 2008 09:34:54 GMT Message-Id: <200812180934.mBI9YswM023726@freefall.freebsd.org> To: amdmi3@FreeBSD.org, maxim@FreeBSD.org, freebsd-doc@FreeBSD.org From: maxim@FreeBSD.org Cc: Subject: Re: docs/129723: [PATCH] fix 5 typos 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, 18 Dec 2008 09:34:54 -0000 Synopsis: [PATCH] fix 5 typos State-Changed-From-To: open->closed State-Changed-By: maxim State-Changed-When: Thu Dec 18 09:34:38 UTC 2008 State-Changed-Why: Fixed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=129723 From owner-freebsd-doc@FreeBSD.ORG Thu Dec 18 09:40:03 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE57F1065670 for ; Thu, 18 Dec 2008 09:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E72048FC14 for ; Thu, 18 Dec 2008 09:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBI9e3pK024261 for ; Thu, 18 Dec 2008 09:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBI9e3xv024260; Thu, 18 Dec 2008 09:40:03 GMT (envelope-from gnats) Date: Thu, 18 Dec 2008 09:40:03 GMT Message-Id: <200812180940.mBI9e3xv024260@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: docs/129723: commit references a PR X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2008 09:40:04 -0000 The following reply was made to PR docs/129723; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/129723: commit references a PR Date: Thu, 18 Dec 2008 09:31:04 +0000 (UTC) maxim 2008-12-18 09:30:50 UTC FreeBSD doc repository Modified files: ru_RU.KOI8-R/articles/multi-os article.sgml ru_RU.KOI8-R/books/fdp-primer/tools chapter.sgml ru_RU.KOI8-R/books/porters-handbook book.sgml Log: o Fix typos. PR: docs/129723 (a part of) Submitted by: Dmitry Marakasov Obtained from: FreeBSD Russian Doc Project Revision Changes Path 1.2 +1 -1 doc/ru_RU.KOI8-R/articles/multi-os/article.sgml 1.3 +1 -1 doc/ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml 1.26 +1 -1 doc/ru_RU.KOI8-R/books/porters-handbook/book.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From owner-freebsd-doc@FreeBSD.ORG Thu Dec 18 09:40:06 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD58D1065675 for ; Thu, 18 Dec 2008 09:40:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A57E98FC1C for ; Thu, 18 Dec 2008 09:40:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBI9e6rT024285 for ; Thu, 18 Dec 2008 09:40:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBI9e6cS024284; Thu, 18 Dec 2008 09:40:06 GMT (envelope-from gnats) Date: Thu, 18 Dec 2008 09:40:06 GMT Message-Id: <200812180940.mBI9e6cS024284@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: docs/129723: commit references a PR X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2008 09:40:06 -0000 The following reply was made to PR docs/129723; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/129723: commit references a PR Date: Thu, 18 Dec 2008 09:34:36 +0000 (UTC) maxim 2008-12-18 09:34:23 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/handbook/advanced-networking chapter.sgml en_US.ISO8859-1/books/handbook/network-servers chapter.sgml Log: o Grammar. PR: docs/129723 Submitted by: amdmi3 Revision Changes Path 1.418 +1 -1 doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml 1.111 +1 -1 doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From owner-freebsd-doc@FreeBSD.ORG Thu Dec 18 11:31:12 2008 Return-Path: Delivered-To: freebsd-docs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 989431065673 for ; Thu, 18 Dec 2008 11:31:12 +0000 (UTC) (envelope-from mailingm2-bounce@mmmail.co.uk) Received: from mta13.mailmserver.co.uk (mta13.mailmserver.co.uk [85.92.88.13]) by mx1.freebsd.org (Postfix) with ESMTP id 175FB8FC1C for ; Thu, 18 Dec 2008 11:31:11 +0000 (UTC) (envelope-from mailingm2-bounce@mmmail.co.uk) Received: from www.mailingm.co.uk (85.92.88.2) by mta13.mailmserver.co.uk (PowerMTA(TM) v3.5r7) id h98p560ms0oo for ; Thu, 18 Dec 2008 11:21:52 +0000 (envelope-from ) To: freebsd-docs@FreeBSD.org Message-ID: <5aded8c1158c21245c62d628c7cc0602@www.mailingm.co.uk> Date: Thu, 18 Dec 2008 11:30:19 +0000 From: "=?UTF-8?B?Si4gUmVldmVz?=" MIME-Version: 1.0 X-Mailer-LID: 210 X-Mailer-SID: 1638 X-Mailer-Sent-By: 6 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Reduce Excess Inventory X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: management@methodeefficace.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2008 11:31:12 -0000 Your email client cannot read this email. To view it online, please go here: http://www.mailingm.co.uk/2/display.php?M=563873&C=ed43102b6c204e3b5b5d25cf9acf393d&S=1638&L=210&N=1290 To stop receiving these emails:http://www.mailingm.co.uk/2/unsubscribe.php?M=563873&N=1638&L=210&C=ed43102b6c204e3b5b5d25cf9acf393d From owner-freebsd-doc@FreeBSD.ORG Thu Dec 18 19:07:39 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59D5E1065674 for ; Thu, 18 Dec 2008 19:07:39 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id B94B28FC1D for ; Thu, 18 Dec 2008 19:07:38 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by ewy14 with SMTP id 14so774171ewy.19 for ; Thu, 18 Dec 2008 11:07:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=o6+SrVYAF8vfljVpKCm9f+TAQmMD6xYKuQ27fLYFz2A=; b=YxxOZo+cmiPCn1I9ePuPQ8iaozBVf03i3txxiCAiIWh/HMAcBHSnicx/bYmWeduflA /jyep+0doiVELtpdncEE75W0BUa0djnC2j+d1XVgqSl+vFXg19PeuVSeUy3SWUWK1x7+ 4uzS4B3JnbdRh6DFJuBnk11v53JMuJfujexU8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Ed8oTDcPPTXm7qIk2I+bEgtKYY73ZgclmTHoyHKvDyuqI70uZVBWv9kqkHqYMJ30aH R9c1y1orrOhsjqep/OOjcPC3T2J0yZ2sW9/N5Fvd2sRZG//WMp+54U4t2I1wiknUGY9F cjVJki3ZIutfq6/xzA/DPj8CGVw6yAGVBmX+k= Received: by 10.210.43.11 with SMTP id q11mr2710623ebq.48.1229627257533; Thu, 18 Dec 2008 11:07:37 -0800 (PST) Received: from atlantis.dyndns.org (athedsl-279638.home.otenet.gr [85.73.139.244]) by mx.google.com with ESMTPS id i7sm6833977nfh.53.2008.12.18.11.07.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 18 Dec 2008 11:07:36 -0800 (PST) Message-ID: <494A9F76.2020401@gmail.com> Date: Thu, 18 Dec 2008 21:07:34 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Tom Rhodes References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> <20081217232207.53615962.trhodes@FreeBSD.org> In-Reply-To: <20081217232207.53615962.trhodes@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org, Murray Stokely Subject: Re: Cutting edge -> Upgrading 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, 18 Dec 2008 19:07:39 -0000 Tom Rhodes wrote: > Hi Murray, Manolis, > > > On Mon, 15 Dec 2008 18:35:51 -0800 > "Murray Stokely" wrote: > > >> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: >> >>> If these chapters are merged, I think we will have to rethink the "The >>> Cutting Edge" title. The title is by itself intimidating for the >>> beginning-intermediate user who is already convinced it is best for him >>> to use "RELEASE" until he is comfortable with the system. And using >>> freebsd-update is essential (and a rather easy task) at any user level. >>> >>> How about changing the chapter to something like "Updating and Upgrading >>> FreeBSD"? >>> The first sections could deal with security updates and minor / major >>> version upgrades using freebsd-update. >>> Later sections could deal with -STABLE and -CURRENT >>> It would probably need more than a few rewrites and reorganization though >>> >> Yea I think this sounds good. Tom, can you include a link to the HTML >> with your next diff -- I find it easier to review big reorganizations >> in the built html form rather than the diffs. >> >> If there is really just too much content for one chapter then maybe >> the updating and upgrading chapter could still be split into two >> adjacent chapters -- one for the basics of updrading between releases >> with mergemaster and such, and a second with more complicated source >> upgrades to -CURRENT. >> >> - Murray >> >> > > Apologies for this tardy reply, but I've recently come down > with some kind of a bug. Anyway, this is what I have right now: > > http://people.freebsd.org/~trhodes/doc/latest-handbook.diff > > http://people.freebsd.org/~trhodes/doc/handbook/ > > The diff contains my Updating chapter placed above the current > cutting-edge content along with some alterations to make the > documentation flow a bit. Surely another update or two will > be needed to perfect this version, but I think it looks pretty > decent as it is now. > > Thanks Tom, this is more or less what I had in mind for the updating-upgrading chapter :) Having read the synopsis, I feel we need to change it a bit so it matches more closely the updated content. Something like this: http://people.freebsd.org/~manolis/updating-upgrading.html#UPDATING-UPGRADING-SYNOPSIS and the patch: http://people.freebsd.org/~manolis/cutting-edge.txt Basically this rephrases the original a bit, and also reorders the itemized list to more or less match the order the info is presented in the chapter. Feel free to change it as you see fit ;) Thanks, manolis From owner-freebsd-doc@FreeBSD.ORG Fri Dec 19 03:03:14 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A15D1065673 for ; Fri, 19 Dec 2008 03:03:14 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 573858FC08 for ; Fri, 19 Dec 2008 03:03:14 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (net-ix.gw.ai.net [205.134.160.6]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBJ33DQ1052659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Dec 2008 22:03:13 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Thu, 18 Dec 2008 22:03:03 -0500 From: Tom Rhodes To: Manolis Kiagias Message-Id: <20081218220303.36017fa2.trhodes@FreeBSD.org> In-Reply-To: <494A9F76.2020401@gmail.com> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> <20081217232207.53615962.trhodes@FreeBSD.org> <494A9F76.2020401@gmail.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org, murray@stokely.org Subject: Re: Cutting edge -> Upgrading 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, 19 Dec 2008 03:03:14 -0000 On Thu, 18 Dec 2008 21:07:34 +0200 Manolis Kiagias wrote: > Tom Rhodes wrote: > > Hi Murray, Manolis, > > > > > > On Mon, 15 Dec 2008 18:35:51 -0800 > > "Murray Stokely" wrote: > > > > > >> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: > >> > >>> If these chapters are merged, I think we will have to rethink the "The > >>> Cutting Edge" title. The title is by itself intimidating for the > >>> beginning-intermediate user who is already convinced it is best for him > >>> to use "RELEASE" until he is comfortable with the system. And using > >>> freebsd-update is essential (and a rather easy task) at any user level. > >>> > >>> How about changing the chapter to something like "Updating and Upgrading > >>> FreeBSD"? > >>> The first sections could deal with security updates and minor / major > >>> version upgrades using freebsd-update. > >>> Later sections could deal with -STABLE and -CURRENT > >>> It would probably need more than a few rewrites and reorganization though > >>> > >> Yea I think this sounds good. Tom, can you include a link to the HTML > >> with your next diff -- I find it easier to review big reorganizations > >> in the built html form rather than the diffs. > >> > >> If there is really just too much content for one chapter then maybe > >> the updating and upgrading chapter could still be split into two > >> adjacent chapters -- one for the basics of updrading between releases > >> with mergemaster and such, and a second with more complicated source > >> upgrades to -CURRENT. > >> > >> - Murray > >> > >> > > > > Apologies for this tardy reply, but I've recently come down > > with some kind of a bug. Anyway, this is what I have right now: > > > > http://people.freebsd.org/~trhodes/doc/latest-handbook.diff > > > > http://people.freebsd.org/~trhodes/doc/handbook/ > > > > The diff contains my Updating chapter placed above the current > > cutting-edge content along with some alterations to make the > > documentation flow a bit. Surely another update or two will > > be needed to perfect this version, but I think it looks pretty > > decent as it is now. > > > > > Thanks Tom, this is more or less what I had in mind for the > updating-upgrading chapter :) > Having read the synopsis, I feel we need to change it a bit so it > matches more closely the updated content. > Something like this: > > http://people.freebsd.org/~manolis/updating-upgrading.html#UPDATING-UPGRADING-SYNOPSIS > > and the patch: > > http://people.freebsd.org/~manolis/cutting-edge.txt > > Basically this rephrases the original a bit, and also reorders > the itemized list to more or less match the order the info is presented > in the chapter. Feel free to change it as you see fit ;) This version of the patch has been applied to my try, and integrated with the latest changes done by Murray today. The latest patch and build handbook version is up here: http://people.FreeBSD.org/~trhodes/doc Please let me know how you feel about it. Other than the directory name issue (cutting edge v. updating-upgrading), I think it's pretty nice. We should consider moving forward should no one object. Thanks, -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Fri Dec 19 06:15:19 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BC061065673; Fri, 19 Dec 2008 06:15:19 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 701838FC13; Fri, 19 Dec 2008 06:15:18 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so450075ugs.39 for ; Thu, 18 Dec 2008 22:15:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=k24x/i+dRZWOLa9RmLPlq84VLDj7Xm5JOgn0Xqq7+/I=; b=c+uAwX+LtDy8PL/zwmZkXZ87H6VHSsyjytyjrdEcq7h6U/P2bgrIh3qOilpdNp+dO9 8eyY9CJi3xLlRHQsn7POsPsx6InuiNNYDmSmPXZgan+/hhM9O+97B2MgBur7zxqCCji2 WI0A/4LUbsryhpW9abrRxeKTo16OEQ5lvm+gk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=jh4ZFMZPsAWdvp4pm+pzWS3RLlCkWCdnoLfnNsSL4SJL/eBmkairSZy1aWDWNX8v7o 44n7KsC6ULs52HhWNaD7gJ7dQpJi3Dy3AgcH6VOLC3iHTuedI4p+oqTMkn1yTLUCi/xH 9R/5RH7gz+8eOoWvZSUn7rVXYRqH5Hzv3IvtM= Received: by 10.67.106.19 with SMTP id i19mr4624464ugm.46.1229667316900; Thu, 18 Dec 2008 22:15:16 -0800 (PST) Received: from atlantis.dyndns.org (athedsl-279638.home.otenet.gr [85.73.139.244]) by mx.google.com with ESMTPS id m1sm6087799uge.48.2008.12.18.22.15.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 18 Dec 2008 22:15:16 -0800 (PST) Message-ID: <494B3BF2.8050600@gmail.com> Date: Fri, 19 Dec 2008 08:15:14 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Tom Rhodes References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> <20081217232207.53615962.trhodes@FreeBSD.org> <494A9F76.2020401@gmail.com> <20081218220303.36017fa2.trhodes@FreeBSD.org> In-Reply-To: <20081218220303.36017fa2.trhodes@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org, murray@stokely.org Subject: Re: Cutting edge -> Upgrading 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, 19 Dec 2008 06:15:19 -0000 Tom Rhodes wrote: > On Thu, 18 Dec 2008 21:07:34 +0200 > Manolis Kiagias wrote: > > >> Tom Rhodes wrote: >> >>> Hi Murray, Manolis, >>> >>> >>> On Mon, 15 Dec 2008 18:35:51 -0800 >>> "Murray Stokely" wrote: >>> >>> >>> >>>> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: >>>> >>>> >>>>> If these chapters are merged, I think we will have to rethink the "The >>>>> Cutting Edge" title. The title is by itself intimidating for the >>>>> beginning-intermediate user who is already convinced it is best for him >>>>> to use "RELEASE" until he is comfortable with the system. And using >>>>> freebsd-update is essential (and a rather easy task) at any user level. >>>>> >>>>> How about changing the chapter to something like "Updating and Upgrading >>>>> FreeBSD"? >>>>> The first sections could deal with security updates and minor / major >>>>> version upgrades using freebsd-update. >>>>> Later sections could deal with -STABLE and -CURRENT >>>>> It would probably need more than a few rewrites and reorganization though >>>>> >>>>> >>>> Yea I think this sounds good. Tom, can you include a link to the HTML >>>> with your next diff -- I find it easier to review big reorganizations >>>> in the built html form rather than the diffs. >>>> >>>> If there is really just too much content for one chapter then maybe >>>> the updating and upgrading chapter could still be split into two >>>> adjacent chapters -- one for the basics of updrading between releases >>>> with mergemaster and such, and a second with more complicated source >>>> upgrades to -CURRENT. >>>> >>>> - Murray >>>> >>>> >>>> >>> Apologies for this tardy reply, but I've recently come down >>> with some kind of a bug. Anyway, this is what I have right now: >>> >>> http://people.freebsd.org/~trhodes/doc/latest-handbook.diff >>> >>> http://people.freebsd.org/~trhodes/doc/handbook/ >>> >>> The diff contains my Updating chapter placed above the current >>> cutting-edge content along with some alterations to make the >>> documentation flow a bit. Surely another update or two will >>> be needed to perfect this version, but I think it looks pretty >>> decent as it is now. >>> >>> >>> >> Thanks Tom, this is more or less what I had in mind for the >> updating-upgrading chapter :) >> Having read the synopsis, I feel we need to change it a bit so it >> matches more closely the updated content. >> Something like this: >> >> http://people.freebsd.org/~manolis/updating-upgrading.html#UPDATING-UPGRADING-SYNOPSIS >> >> and the patch: >> >> http://people.freebsd.org/~manolis/cutting-edge.txt >> >> Basically this rephrases the original a bit, and also reorders >> the itemized list to more or less match the order the info is presented >> in the chapter. Feel free to change it as you see fit ;) >> > > This version of the patch has been applied to my try, and > integrated with the latest changes done by Murray today. > > The latest patch and build handbook version is up here: > > http://people.FreeBSD.org/~trhodes/doc > > Please let me know how you feel about it. Other than the > directory name issue (cutting edge v. updating-upgrading), I > think it's pretty nice. We should consider moving forward > should no one object. Thanks, > > Yes, it looks fine to me. As a final touch, maybe it would be nice to change the title of section 24.4 from: 24.4 FreeBSD-CURRENT vs. FreeBSD-STABLE to 24.4 Tracking a Development Branch I think this flows better now that the chapter does not exclusively deal with CURRENT and STABLE. From owner-freebsd-doc@FreeBSD.ORG Fri Dec 19 13:12:45 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 950881065675 for ; Fri, 19 Dec 2008 13:12:45 +0000 (UTC) (envelope-from eitanadlerlist@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id 6716C8FC12 for ; Fri, 19 Dec 2008 13:12:45 +0000 (UTC) (envelope-from eitanadlerlist@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2340758rvf.43 for ; Fri, 19 Dec 2008 05:12:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:user-agent :mime-version:to:subject:x-enigmail-version:openpgp:content-type :content-transfer-encoding:from; bh=b8XFnu2mcvRC52z0sQzCnDV/xCakTGEkMofImdXMkmM=; b=x9MNuXJq8qdPnzT9ltRVIe88bL/oMclv/ECrGU/Xky4Xy5pl76A/LGBVEMf1r3Apr5 7ZG7Zi9w8FgYdhnHfcuvniE8pzqIqvxP5lgLSumqP5ln14X/9qhP+YZP03uOkYPW9cFJ d04tgfEyoYrod+dlt3m1HVlv3BWq7GX2SALdI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:user-agent:mime-version:to:subject :x-enigmail-version:openpgp:content-type:content-transfer-encoding :from; b=n3zaJkg9P0JiSN+B/e4g+kJb1J/RUCnaZaZpeICwtxbV8m+Zz1w+9sCPn87//XAzRH u/PR/cyjgB9ucdSpp71KUr0thYN8Ozgk/bKx0mOU74IYH7HlJhZRaXIAtNJ3ZYLO1Nti a98QnWt7h3OXs7IhFGBeNIIfBj+GptaNIp6sY= Received: by 10.142.52.9 with SMTP id z9mr1319891wfz.82.1229692364984; Fri, 19 Dec 2008 05:12:44 -0800 (PST) Received: from aargh.lan (ool-182fcc8b.dyn.optonline.net [24.47.204.139]) by mx.google.com with ESMTPS id 30sm8320133wfg.45.2008.12.19.05.12.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Dec 2008 05:12:43 -0800 (PST) Message-ID: <494B9DC4.8040301@gmail.com> Date: Fri, 19 Dec 2008 08:12:36 -0500 User-Agent: Mozilla (X11; U; FreeBSD i386; en-US; ) Gecko Thunderbird Mnenhy/0.7.5.666 MIME-Version: 1.0 To: freebsd-doc@freebsd.org X-Enigmail-Version: 0.95.7 OpenPGP: id=E9C2CCD1; url=pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit From: Eitan Adler Subject: Additional Contributers - questions && suggestions 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, 19 Dec 2008 13:12:45 -0000 I have some questions comments about the "additional contributers" page. I am aware that some (if not all) of these are bikeshed questions and I urge you to IGNORE them if you feel that they are. No need to flood the mailing list. I'm just putting out some thoughts I had when looking through the article. 1) Who goes on it? Port maintainers? People who send patches? Only if they are very active? 2) If its more than one of the above should we indicate what each person did to make it on the list? (starting now) 3) Should we should have a list at the top with A B C... which links to the first person in that list that starts with the letter. 5) The last 5 entries are out of order (my guess is that someone used "sort" as they begin with a lowercase letter. 5.5) The first three names are out of order for the same reason. 6) All the "No Name"s should be at the end in alphabetical order by email address 7) Section 5 should be the last section. 8) We should have a list like http://www.openbsd.org/donations.html which lists people that donate. Section 1 only lists major donors. 9) There should be links to "how to contribute" for code and documentation. If I come to this page I have no clue how to contribute. -- Eitan Adler GNU Key fingerprint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 From owner-freebsd-doc@FreeBSD.ORG Fri Dec 19 09:55:37 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88C39106564A for ; Fri, 19 Dec 2008 09:55:37 +0000 (UTC) (envelope-from bootiack@yahoo.com) Received: from web110608.mail.gq1.yahoo.com (web110608.mail.gq1.yahoo.com [67.195.13.199]) by mx1.freebsd.org (Postfix) with SMTP id 468C98FC16 for ; Fri, 19 Dec 2008 09:55:37 +0000 (UTC) (envelope-from bootiack@yahoo.com) Received: (qmail 50286 invoked by uid 60001); 19 Dec 2008 09:28:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=F4Gffkwan90jXjWd8x4WVVdyNzSV5FduGhj1faq5ZMFdlEf5CZYqwuEZauFiJ3vIIdRJBxH8IEN1RsSbDcaOVchreKn6UfVcm1fNNuc29XPfbUdxdYhfv+i5Pn+dKmwdAjeabbDyp3+n5brY6Nw8DyR0amCIrkh5ILLjNWE1aD0=; X-YMail-OSG: 4_x3LegVM1ng59x47KozaVvuUm8hKCnSW9DinahD9mvq28jloxGhVioktHT1Qwl9TrDdb.mMJ_pytYcj5ShDBQvlNH1iG9WKHd5Thh1hnYbU3XGvZrPhJPvVhcgJX5PIVagZ3OI5owUF7nxGtUU9pIozIQ-- Received: from [76.174.30.243] by web110608.mail.gq1.yahoo.com via HTTP; Fri, 19 Dec 2008 01:28:55 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Fri, 19 Dec 2008 01:28:55 -0800 (PST) From: G To: doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <329017.49550.qm@web110608.mail.gq1.yahoo.com> X-Mailman-Approved-At: Fri, 19 Dec 2008 14:07:56 +0000 Cc: Subject: section 4.5.1 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bootiack@yahoo.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2008 09:55:37 -0000 I was schooled in IRC about how 'portsnap fetch update' is the best way to update ports, not 'portsnap update' as listed in section 4.5.1. Perhaps that section could be changed to 'portsnap fetch update'. Just an idea. thx From owner-freebsd-doc@FreeBSD.ORG Fri Dec 19 17:00:07 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB35A1065675 for ; Fri, 19 Dec 2008 17:00:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8940D8FC18 for ; Fri, 19 Dec 2008 17:00:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBJH02TD061939 for ; Fri, 19 Dec 2008 17:00:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBJH02nu061938; Fri, 19 Dec 2008 17:00:02 GMT (envelope-from gnats) Resent-Date: Fri, 19 Dec 2008 17:00:02 GMT Resent-Message-Id: <200812191700.mBJH02nu061938@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, "Ben C. O. Grimm" Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB1091065675 for ; Fri, 19 Dec 2008 16:57:27 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id CBC868FC16 for ; Fri, 19 Dec 2008 16:57:27 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id mBJGvRG7068124 for ; Fri, 19 Dec 2008 16:57:27 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id mBJGvRCn068123; Fri, 19 Dec 2008 16:57:27 GMT (envelope-from nobody) Message-Id: <200812191657.mBJGvRCn068123@www.freebsd.org> Date: Fri, 19 Dec 2008 16:57:27 GMT From: "Ben C. O. Grimm" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/129765: man 8 shutdown does not explain operation without command-line options 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, 19 Dec 2008 17:00:07 -0000 >Number: 129765 >Category: docs >Synopsis: man 8 shutdown does not explain operation without command-line options >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 19 17:00:02 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Ben C. O. Grimm >Release: 7.1-PRERELEASE >Organization: None >Environment: FreeBSD hail.bengrimm.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon Dec 1 17:04:32 CET 2008 root@hail.bengrimm.net:/usr/obj/usr/src/sys/HAIL i386 >Description: The manual for shutdown(8) describes how the command behaves using command-line options like -h or -p, but not the behavior when omitting these options, like in 'shutdown now'. There is a brief mention of 'bringing the system down to single-user state' (which is what 'shutdown now' actually does), but it is not explained. See how this might confuse users: http://forums.freebsd.org/showthread.php?p=6273 >How-To-Repeat: >Fix: Add a one-liner to the manual about the effect of not using command-line switches in the shutdown command. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sat Dec 20 00:28:02 2008 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D577B1065675 for ; Sat, 20 Dec 2008 00:28:02 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 98B848FC1B for ; Sat, 20 Dec 2008 00:28:02 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (net-ix.gw.ai.net [205.134.160.6]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBK0Rt9R058177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Dec 2008 19:27:56 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Fri, 19 Dec 2008 19:27:47 -0500 From: Tom Rhodes To: bootiack@yahoo.com Message-Id: <20081219192747.1edea542.trhodes@FreeBSD.org> In-Reply-To: <329017.49550.qm@web110608.mail.gq1.yahoo.com> References: <329017.49550.qm@web110608.mail.gq1.yahoo.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: doc@FreeBSD.org Subject: Re: section 4.5.1 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, 20 Dec 2008 00:28:02 -0000 Hi, On Fri, 19 Dec 2008 01:28:55 -0800 (PST) G wrote: > I was schooled in IRC about how 'portsnap fetch update' is the best way to update ports, not 'portsnap update' as listed in section 4.5.1. Perhaps that section could be changed to 'portsnap fetch update'. > > Just an idea. > thx Looking at my local source, I am unable to find an actual "portsnap update" in the section; however, I have appened the following to the end of that section: To run both processes consecutively, issue the following command: &prompt.root; portsnap fetch update This change is in my local tree and should go in later on this week. Thanks, -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Sat Dec 20 00:29:57 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43949106564A; Sat, 20 Dec 2008 00:29:57 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id EFE7F8FC08; Sat, 20 Dec 2008 00:29:56 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (net-ix.gw.ai.net [205.134.160.6]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBK0ToOe058188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Dec 2008 19:29:51 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Fri, 19 Dec 2008 19:29:42 -0500 From: Tom Rhodes To: Manolis Kiagias Message-Id: <20081219192942.2590ef9b.trhodes@FreeBSD.org> In-Reply-To: <494B3BF2.8050600@gmail.com> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> <20081217232207.53615962.trhodes@FreeBSD.org> <494A9F76.2020401@gmail.com> <20081218220303.36017fa2.trhodes@FreeBSD.org> <494B3BF2.8050600@gmail.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: trhodes@FreeBSD.org, freebsd-doc@FreeBSD.org, murray@stokely.org Subject: Re: Cutting edge -> Upgrading 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, 20 Dec 2008 00:29:57 -0000 On Fri, 19 Dec 2008 08:15:14 +0200 Manolis Kiagias wrote: > Tom Rhodes wrote: > > On Thu, 18 Dec 2008 21:07:34 +0200 > > Manolis Kiagias wrote: > > > > > >> Tom Rhodes wrote: > >> > >>> Hi Murray, Manolis, > >>> > >>> > >>> On Mon, 15 Dec 2008 18:35:51 -0800 > >>> "Murray Stokely" wrote: > >>> > >>> > >>> > >>>> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: > >>>> > >>>> > >>>>> If these chapters are merged, I think we will have to rethink the "The > >>>>> Cutting Edge" title. The title is by itself intimidating for the > >>>>> beginning-intermediate user who is already convinced it is best for him > >>>>> to use "RELEASE" until he is comfortable with the system. And using > >>>>> freebsd-update is essential (and a rather easy task) at any user level. > >>>>> > >>>>> How about changing the chapter to something like "Updating and Upgrading > >>>>> FreeBSD"? > >>>>> The first sections could deal with security updates and minor / major > >>>>> version upgrades using freebsd-update. > >>>>> Later sections could deal with -STABLE and -CURRENT > >>>>> It would probably need more than a few rewrites and reorganization though > >>>>> > >>>>> > >>>> Yea I think this sounds good. Tom, can you include a link to the HTML > >>>> with your next diff -- I find it easier to review big reorganizations > >>>> in the built html form rather than the diffs. > >>>> > >>>> If there is really just too much content for one chapter then maybe > >>>> the updating and upgrading chapter could still be split into two > >>>> adjacent chapters -- one for the basics of updrading between releases > >>>> with mergemaster and such, and a second with more complicated source > >>>> upgrades to -CURRENT. > >>>> > >>>> - Murray > >>>> > >>>> > >>>> > >>> Apologies for this tardy reply, but I've recently come down > >>> with some kind of a bug. Anyway, this is what I have right now: > >>> > >>> http://people.freebsd.org/~trhodes/doc/latest-handbook.diff > >>> > >>> http://people.freebsd.org/~trhodes/doc/handbook/ > >>> > >>> The diff contains my Updating chapter placed above the current > >>> cutting-edge content along with some alterations to make the > >>> documentation flow a bit. Surely another update or two will > >>> be needed to perfect this version, but I think it looks pretty > >>> decent as it is now. > >>> > >>> > >>> > >> Thanks Tom, this is more or less what I had in mind for the > >> updating-upgrading chapter :) > >> Having read the synopsis, I feel we need to change it a bit so it > >> matches more closely the updated content. > >> Something like this: > >> > >> http://people.freebsd.org/~manolis/updating-upgrading.html#UPDATING-UPGRADING-SYNOPSIS > >> > >> and the patch: > >> > >> http://people.freebsd.org/~manolis/cutting-edge.txt > >> > >> Basically this rephrases the original a bit, and also reorders > >> the itemized list to more or less match the order the info is presented > >> in the chapter. Feel free to change it as you see fit ;) > >> > > > > This version of the patch has been applied to my try, and > > integrated with the latest changes done by Murray today. > > > > The latest patch and build handbook version is up here: > > > > http://people.FreeBSD.org/~trhodes/doc > > > > Please let me know how you feel about it. Other than the > > directory name issue (cutting edge v. updating-upgrading), I > > think it's pretty nice. We should consider moving forward > > should no one object. Thanks, > > > > > > Yes, it looks fine to me. > As a final touch, maybe it would be nice to change the title of section > 24.4 from: > > 24.4 FreeBSD-CURRENT vs. FreeBSD-STABLE > > to > > 24.4 Tracking a Development Branch > > I think this flows better now that the chapter does not exclusively deal > with CURRENT and STABLE. Actually sounds rather nice, updated in my local patch. Let me run around with Giorgos a bit here and I'll have a new handbook and diff posted. Thanks, -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Sat Dec 20 00:32:57 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 120C0106564A for ; Sat, 20 Dec 2008 00:32:57 +0000 (UTC) (envelope-from bounces@bounces.jaxtr.com) Received: from smtp151.sv.jaxtr.com (smtp151.sv.jaxtr.com [74.201.86.151]) by mx1.freebsd.org (Postfix) with ESMTP id E417A8FC22 for ; Sat, 20 Dec 2008 00:32:56 +0000 (UTC) (envelope-from bounces@bounces.jaxtr.com) DKIM-Signature: v=1; a=rsa-sha1; d=jaxtr.com; s=dkim1024; c=simple/simple; q=dns/txt; i=@jaxtr.com; t=1229731976; h=From:Resent-From; bh=w4qxITMpJrgRcpJoaXOFsS3YPOc=; b=V+Jktmw1fSvb31UqK5n0HASLiYwt19tFhtZwqls7JlCoIRBBr94xLL0Wl5ggnTgH SPRyVDpne5yuriASSSq18jflDcK0Tpwp/ADAYa4DA0cPw1eOiyKmNZ4K1kGbMhyk nXYPVK96KSbk97G703qbwMq/uNQp2duW6AGcz7NakCc=; DomainKey-Signature: q=dns; a=rsa-sha1; c=nofws; s=dk1024; d=jaxtr.com; h=Received:Resent-From:Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:X-Sysflow; b=bk6Ahcc5Edy/4THRao8BvjNP+5bxi2fUj46oTJEEFmj6T1NeIDUlw5k1tIxJMzaM crhaq1GiibZuJVI0NpIUU2hptdYM2VL+lGdkjMwyhcviyQoeUiHEcb6u3vNFpZvh OgfpS9i31Mbiefpod5akHGbBvoM1hJRvGuNte4mq7jE= Received: from [74.201.86.160] ([74.201.86.160:44358] helo=que1.sv.jaxtr.com) by smtp1.sv.jaxtr.com (envelope-from ) (ecelerity 2.2.2.31 r(24168/24420)) with ESMTP id 29/AB-09639-8883C494; Sat, 20 Dec 2008 00:12:56 +0000 Resent-From: bounces@jaxtr.com Date: Sat, 20 Dec 2008 00:12:56 +0000 (GMT) From: jaxtr To: freebsd-doc@freebsd.org Message-ID: <1684769848.11525551229731976576.JavaMail.tomcat@que1.sv.jaxtr.com> MIME-Version: 1.0 X-Sysflow: cv,20081125t0134,qi7if4.cp0ryf,311775345 Resent-Message-Id: <20081220003256.E417A8FC22@mx1.freebsd.org> Resent-Date: Sat, 20 Dec 2008 00:32:56 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Call India at 2.4 cents/minute and many other places below 1 cent 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, 20 Dec 2008 00:32:57 -0000 Hello preman, Save money with our new low rates for making international calls on your phone using a local jaxtr number: India US$ 0.024 / min USA US$ 0.008 / min Canada US$ 0.008 / min China US$ 0.008 / min UK US$ 0.008 / min Click here to see more: http://www.jaxtr.com/user/rates.jsp?tId=311775345_399_452 Happy Holidays, -The jaxtr team P.S. Share these savings with friends and family worldwide by telling them about jaxtr! jaxtr, 855 Oak Grove Avenue, Suite 100, Menlo Park, CA 94025 To stop receiving emails, send email to blockme@jaxtr.com From owner-freebsd-doc@FreeBSD.ORG Sat Dec 20 10:08:54 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB9261065670 for ; Sat, 20 Dec 2008 10:08:54 +0000 (UTC) (envelope-from ydoty@michigansworried.com) Received: from hi6b.michigansworried.com (hi6b.michigansworried.com [72.13.16.37]) by mx1.freebsd.org (Postfix) with ESMTP id 6434A8FC1B for ; Sat, 20 Dec 2008 10:08:54 +0000 (UTC) (envelope-from ydoty@michigansworried.com) Message-ID: <61946.286756087.1229764695@michigansworried.com> Date: 20 Dec 2008 04:55:06 -0500 From: Cash prizes. To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Over $100,000 won daily - Play Bejeweled 2 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rsreply.61946.286756087.1229764695@michigansworried.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Dec 2008 10:08:54 -0000 or for CASH prizes playing Bejeweled 2online Play Bejeweled 2online...but with a brand-new twist! To win, simply get the highesttotal score - it's that simple! There are over $250,000 in prizes wondaily on WorldWinner, so what are you waiting for? To stop receiving emails from WorldWinner, email us at WorldWinner | Suite 3-110 | 275 Grove Street | Newton, MA 02466 | www.worldwinner.com From owner-freebsd-doc@FreeBSD.ORG Sat Dec 20 17:50:03 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9852D1065678 for ; Sat, 20 Dec 2008 17:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 749F28FC1E for ; Sat, 20 Dec 2008 17:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBKHo3w9013149 for ; Sat, 20 Dec 2008 17:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBKHo3uN013148; Sat, 20 Dec 2008 17:50:03 GMT (envelope-from gnats) Resent-Date: Sat, 20 Dec 2008 17:50:03 GMT Resent-Message-Id: <200812201750.mBKHo3uN013148@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, Chris Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE037106564A for ; Sat, 20 Dec 2008 17:45:54 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id AC56A8FC16 for ; Sat, 20 Dec 2008 17:45:54 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id mBKHjsi5028289 for ; Sat, 20 Dec 2008 17:45:54 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id mBKHjsr9028288; Sat, 20 Dec 2008 17:45:54 GMT (envelope-from nobody) Message-Id: <200812201745.mBKHjsr9028288@www.freebsd.org> Date: Sat, 20 Dec 2008 17:45:54 GMT From: Chris To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/129792: mount_msdosfs(8) man page is missing the -o large option 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, 20 Dec 2008 17:50:03 -0000 >Number: 129792 >Category: docs >Synopsis: mount_msdosfs(8) man page is missing the -o large option >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Dec 20 17:50:03 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Chris >Release: 7.1-PRERELEASE >Organization: >Environment: FreeBSD eco 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Tue Dec 16 18:28:48 GMT 2008 root@eco:/usr/obj/usr/src/sys/GENERIC i386 >Description: /usr/src/sys/fs/msdosfs/msdosfs_vfsops.c lists 'large' as an option to mount_msdosfs but it is not described in the mount_msdosfs(8) man page. >How-To-Repeat: man 8 mount_msdosfs >Fix: Suggested change: --- mount_msdosfs.8.orig 2005-09-14 17:36:19.000000000 +0100 +++ mount_msdosfs.8 2008-12-20 17:40:11.000000000 +0000 @@ -79,6 +79,8 @@ Force only the old MS-DOS 8.3 style filenames to be visible. .It Cm nowin95 Completely ignore Windows 95 extended file information. +.It Cm large +Mount a file system larger than 128 GB. See CAVEATS section. .El .It Fl u Ar uid Set the owner of the files in the file system to @@ -208,6 +210,18 @@ Cluster sizes larger than 16K are unavoidable for file system sizes larger than 1G, and also occur when file systems larger than 1G are shrunk to smaller than 1G using FIPS. +.Pp +The +.Nm large +option uses at least 32 bytes of kernel memory (which is not +reclaimed until the FS is unmounted) for each file on disk to map +between the 32-bit inode numbers used by VFS and the 64-bit +pseudo-inode numbers used internally by msdosfs. This is only +safe to use in certain controlled situations (e.g. read-only FS +with less than 1 million files). +Since the mappings do not persist across unmounts (or reboots), these +filesystems are not suitable for exporting through NFS, or any other +application that requires fixed inode numbers. .Sh HISTORY The .Nm >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sat Dec 20 17:38:00 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FCB6106564A for ; Sat, 20 Dec 2008 17:38:00 +0000 (UTC) (envelope-from elshaymaa_nassar@yahoo.com) Received: from n55.bullet.mail.sp1.yahoo.com (n55.bullet.mail.sp1.yahoo.com [98.136.44.188]) by mx1.freebsd.org (Postfix) with SMTP id 1F8FE8FC14 for ; Sat, 20 Dec 2008 17:38:00 +0000 (UTC) (envelope-from elshaymaa_nassar@yahoo.com) Received: from [69.147.84.145] by n55.bullet.mail.sp1.yahoo.com with NNFMP; 20 Dec 2008 17:24:09 -0000 Received: from [67.195.9.83] by t8.bullet.mail.sp1.yahoo.com with NNFMP; 20 Dec 2008 17:24:09 -0000 Received: from [67.195.9.109] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 20 Dec 2008 17:24:09 -0000 Received: from [127.0.0.1] by omp113.mail.gq1.yahoo.com with NNFMP; 20 Dec 2008 17:24:09 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 527825.34151.bm@omp113.mail.gq1.yahoo.com Received: (qmail 24172 invoked by uid 60001); 20 Dec 2008 17:24:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=Q3lCdjeesznERKdnW9Sc0uKqeLgNhHzY9QtSo3aK5LyYYxsQErgkehYFcM1hlis6jwoSTW9HHUZR/xj+vB1Jt4nEP6K958Y9jZXSqhDiqKKDJ1pHVFtBtO5y0+kksfA1qL4ob3wMjlMJqpRhFssXmWHCR8bJmHK8uGi370sH+68=; X-YMail-OSG: SZxYAi4VM1mGZi.sSgZjukQuTqYxtcE25_as.My9wpsepTG5Kf3y65_cAlu9vwO9sSxpJFgNvdaBtoNXDd2wSrW0Vw7ZSH8yaIX_.WoDI5tv3fkwVfj0z3rTwd1rzBs9rFLmgj_jP9vITFsUIyw90sDdHw-- Received: from [217.54.144.75] by web112207.mail.gq1.yahoo.com via HTTP; Sat, 20 Dec 2008 09:24:09 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Sat, 20 Dec 2008 09:24:09 -0800 (PST) From: El-Shaymaa Nassar To: doc@FreeBSD.org MIME-Version: 1.0 Message-ID: <342201.1694.qm@web112207.mail.gq1.yahoo.com> X-Mailman-Approved-At: Sat, 20 Dec 2008 17:56:27 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Advanced printing settup X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: elshaymaa_nassar@yahoo.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Dec 2008 17:38:00 -0000 Hello, =A0 In input ,and out put filters , document didn't mention how to detect escap= e sequence specidied for such printer and how it controls data printing =A0 thanks =A0=0A=0A=0A From owner-freebsd-doc@FreeBSD.ORG Sat Dec 20 19:55:10 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32E8F106564A for ; Sat, 20 Dec 2008 19:55:10 +0000 (UTC) (envelope-from david.a.rogers@gmail.com) Received: from mail-bw0-f19.google.com (mail-bw0-f19.google.com [209.85.218.19]) by mx1.freebsd.org (Postfix) with ESMTP id 821BB8FC19 for ; Sat, 20 Dec 2008 19:55:09 +0000 (UTC) (envelope-from david.a.rogers@gmail.com) Received: by bwz12 with SMTP id 12so4210506bwz.19 for ; Sat, 20 Dec 2008 11:55:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=icmfKRwkhy6ZQqdnnlaT2VuzLOStoB5AJ8dHIvkh5WI=; b=oWn3uLA5ngW1CT8p0Z9zEADynHUODbf1t//OvTzvwdSXJyi/zyeriRgL4gZ7J3bpJk 82tZBciS+o4kAb7JHZQhU3oxTGkruD8pFfWUdOSSib3nUNsA8vRAOx+/ip6B7aD2XZiu sIOuj3S3mQRbaXlHSVx7NSyScOGNmlRIfAaaM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=H4tmYQ1TVac7xBFuM68iAttJKktJWOwzADi2bNHZjs89PV6nBTDbf3Qupd/NvUTtBk kyHB2n6tlpmUAvcfMX66vbg7+dCFgUgM++vwsogfYCxCBZj5b+snjOET89f8g7keCAxh c2jTUpQ+/4lDEjCgIEqiaQpYQ2/gNkBv7IGaM= Received: by 10.181.134.12 with SMTP id l12mr1596767bkn.80.1229801009268; Sat, 20 Dec 2008 11:23:29 -0800 (PST) Received: by 10.180.232.7 with HTTP; Sat, 20 Dec 2008 11:23:29 -0800 (PST) Message-ID: <8f7da5f40812201123t19c6cabj2d11b62345a27db8@mail.gmail.com> Date: Sat, 20 Dec 2008 13:23:29 -0600 From: "David A. Rogers" To: doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: handbook suggestion 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, 20 Dec 2008 19:55:10 -0000 First, let me say that I find FreeBSD to be the best of all the free Unices -- and it is due to the excellent and practical documentation. That said, there is an easy way to make FreeBSD easier for the home user. There are a number of suggestions/methods of doing things in the handbook that are appropriate for the business user that are not needed or useful for the home user. As an example, both the usb drive and scanner sections give instructions for allowing others besides root to mount/use the respective hardware. Both suggestions give advice that restrict the enabling to just one group. For home use it would be easier to just allow any user to mount/use hardware. A sidebar or some such giving alternatives for personal/home users would be nice. Thanks, --dr