From owner-freebsd-doc@FreeBSD.ORG Sun Jun 18 20:52:26 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 055DD16A47C; Sun, 18 Jun 2006 20:52:26 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3589B43D46; Sun, 18 Jun 2006 20:52:25 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5IKqPTc003778; Sun, 18 Jun 2006 20:52:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5IKqPAx003774; Sun, 18 Jun 2006 20:52:25 GMT (envelope-from linimon) Date: Sun, 18 Jun 2006 20:52:25 GMT From: Mark Linimon Message-Id: <200606182052.k5IKqPAx003774@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-doc@FreeBSD.org, linimon@FreeBSD.org Cc: Subject: Re: docs/99084: doc update for new mailing list freebsd-embedded 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, 18 Jun 2006 20:52:26 -0000 Synopsis: doc update for new mailing list freebsd-embedded Responsible-Changed-From-To: freebsd-doc->linimon Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jun 18 20:52:16 UTC 2006 Responsible-Changed-Why: take. http://www.freebsd.org/cgi/query-pr.cgi?pr=99084 From owner-freebsd-doc@FreeBSD.ORG Sun Jun 18 21:10:21 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01C2716A49E; Sun, 18 Jun 2006 21:10:20 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E64C43D5C; Sun, 18 Jun 2006 21:10:18 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5ILAI3Q004539; Sun, 18 Jun 2006 21:10:18 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5ILAHIB004535; Sun, 18 Jun 2006 21:10:17 GMT (envelope-from linimon) Date: Sun, 18 Jun 2006 21:10:17 GMT From: Mark Linimon Message-Id: <200606182110.k5ILAHIB004535@freefall.freebsd.org> To: duane@dwlabs.ca, linimon@FreeBSD.org, freebsd-doc@FreeBSD.org, linimon@FreeBSD.org Cc: Subject: Re: docs/98344: [patch] An update of the article "Choosing the FreeBSD Version that is Right for You" 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, 18 Jun 2006 21:10:21 -0000 Synopsis: [patch] An update of the article "Choosing the FreeBSD Version that is Right for You" State-Changed-From-To: open->feedback State-Changed-By: linimon State-Changed-When: Sun Jun 18 21:07:55 UTC 2006 State-Changed-Why: Unfortunately you have mixed whitespace changes (tabs) with content changes, and this makes it very difficult to see exactly what has changed. The Style Guide says both that whitespace changes should be committed separately from content changes, and that the standard for indentation is two spaces for each level, with each instance of 8 spaces, starting at the beginning of the line, changed to a tab. Can you please revise the patch according to this indentation and resubmit? Responsible-Changed-From-To: freebsd-doc->linimon Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jun 18 21:07:55 UTC 2006 Responsible-Changed-Why: Since I wrote the original article, I'll take this. http://www.freebsd.org/cgi/query-pr.cgi?pr=98344 From owner-freebsd-doc@FreeBSD.ORG Sun Jun 18 23:08:50 2006 Return-Path: X-Original-To: doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 357E816A479; Sun, 18 Jun 2006 23:08:50 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FFF343D45; Sun, 18 Jun 2006 23:08:49 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.6) with ESMTP id k5IN8mO4024226; Mon, 19 Jun 2006 03:08:48 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Mon, 19 Jun 2006 03:08:48 +0400 (MSD) From: Dmitry Morozovsky To: doc@FreeBSD.org Message-ID: <20060619025709.W13558@woozle.rinet.ru> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-483619118-1150671888=:13558" Content-ID: <20060619030715.W13558@woozle.rinet.ru> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Mon, 19 Jun 2006 03:08:48 +0400 (MSD) Cc: trhodes@FreeBSD.org Subject: disk Handbook chapter, backups, and MINI kernel 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, 18 Jun 2006 23:08:50 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-483619118-1150671888=:13558 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: <20060619030715.L13558@woozle.rinet.ru> Colleagues, in process of trhodes' 4.X handbook cleanup I found the following: MINI kernel config in disks chapter is seriously out of date. I'd tried to bring it up to date (attached), but even after this kernel is about 2.4 M in size, hence useless for floppy boot. Disabling SCSI and enabling ata/atadisk does not help much - 2.1M I suppose the whole process should be reorganized to CD/PXE boot standard fixit media which does not suffer from such space restrictions, allows module loading, etc? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ --0-483619118-1150671888=:13558 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=MICRO Content-Transfer-Encoding: BASE64 Content-ID: <20060619030848.K13558@woozle.rinet.ru> Content-Description: Content-Disposition: attachment; filename=MICRO Iw0KIyBNSU5JIC0tIEEga2VybmVsIHRvIGdldCBGcmVlQlNEIG9udG8gYSBk aXNrLg0KIw0KbWFjaGluZSAgICAgICAgICJpMzg2Ig0KY3B1ICAgICAgICAg ICAgICJJNjg2X0NQVSINCmlkZW50ICAgICAgICAgICBNSU5JDQptYXh1c2Vy cyAgICAgICAgNQ0KDQpvcHRpb25zCQlTQ0hFRF80QlNEDQpvcHRpb25zICAg ICAgICAgSU5FVCAgICAgICAgICAgICAgICAgICAgIyBuZWVkZWQgZm9yIF90 Y3AgX2ljbXBzdGF0IF9pcHN0YXQNCiAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAjICAgICAgICAgICAgX3VkcHN0YXQgX3RjcHN0 YXQgX3VkYg0Kb3B0aW9ucyAgICAgICAgIEZGUyAgICAgICAgICAgICAgICAg ICAgICNCZXJrZWxleSBGYXN0IEZpbGUgU3lzdGVtDQpvcHRpb25zICAgICAg ICAgRkFUX0NVUlNPUiAgICAgICAgICAgICAgI2Jsb2NrIGN1cnNvciBpbiBz eXNjb25zIG9yIHBjY29ucw0Kb3B0aW9ucyAgICAgICAgIFNDU0lfREVMQVk9 MTUwMDAgICAgICAgICNCZSBwZXNzaW1pc3RpYyBhYm91dCBKb2UgU0NTSSBk ZXZpY2UNCg0KZGV2aWNlICAgICAgICAgIHBjaQ0KDQpkZXZpY2UgICAgICAg ICAgZmRjDQoNCmRldmljZSAgICAgICAgICBuY3INCg0KZGV2aWNlICAgICAg ICAgIHNjYnVzDQoNCmRldmljZSAgICAgICAgICBzYw0KZGV2aWNlICAgICAg ICAgIHZnYQ0KZGV2aWNlICAgICAgICAgIGF0a2JkYw0KZGV2aWNlICAgICAg ICAgIGF0a2JkDQoNCmRldmljZSAgICAgICAgICBucHgNCg0KZGV2aWNlICAg ICAgICAgIGRhDQpkZXZpY2UgICAgICAgICAgc2ENCg0KZGV2aWNlICAgICAg ICAgIGxvb3AgICAgICAgICAgICAjIHJlcXVpcmVkIGJ5IElORVQNCmRldmlj ZSAgICAgICAgICBldGhlciAgICAgICAgICAgIyByZXF1aXJlZCBieSBJTkVU DQpkZXZpY2UgICAgICAgICAgcmFuZG9tDQo= --0-483619118-1150671888=:13558-- From owner-freebsd-doc@FreeBSD.ORG Mon Jun 19 00:02:47 2006 Return-Path: X-Original-To: doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 313D016A47A; Mon, 19 Jun 2006 00:02:47 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (ns1.pittgoth.com [216.38.206.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB20B43D4C; Mon, 19 Jun 2006 00:02:46 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost (ip70-177-190-239.dc.dc.cox.net [70.177.190.239]) (authenticated bits=0) by pittgoth.com (8.13.4/8.13.4) with ESMTP id k5J072j4007529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 18 Jun 2006 20:07:03 -0400 (EDT) (envelope-from trhodes@FreeBSD.org) Date: Sun, 18 Jun 2006 20:02:39 -0400 From: Tom Rhodes To: Dmitry Morozovsky Message-Id: <20060618200239.553aabad.trhodes@FreeBSD.org> In-Reply-To: <20060619025709.W13558@woozle.rinet.ru> References: <20060619025709.W13558@woozle.rinet.ru> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: trhodes@FreeBSD.org, doc@FreeBSD.org Subject: Re: disk Handbook chapter, backups, and MINI kernel 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, 19 Jun 2006 00:02:47 -0000 On Mon, 19 Jun 2006 03:08:48 +0400 (MSD) Dmitry Morozovsky wrote: > Colleagues, > > in process of trhodes' 4.X handbook cleanup I found the following: > > MINI kernel config in disks chapter is seriously out of date. I'd tried to > bring it up to date (attached), but even after this kernel is about 2.4 M in > size, hence useless for floppy boot. Disabling SCSI and enabling ata/atadisk > does not help much - 2.1M Actually, I almost completely removed this section. But since others might complain about discussing Nano or Pico BSD to do things like this, I backed off. -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Mon Jun 19 00:04:24 2006 Return-Path: X-Original-To: doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E34716A47F; Mon, 19 Jun 2006 00:04:24 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (ns1.pittgoth.com [216.38.206.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFA5A43D53; Mon, 19 Jun 2006 00:04:23 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost (ip70-177-190-239.dc.dc.cox.net [70.177.190.239]) (authenticated bits=0) by pittgoth.com (8.13.4/8.13.4) with ESMTP id k5J08dpX007539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 18 Jun 2006 20:08:40 -0400 (EDT) (envelope-from trhodes@FreeBSD.org) Date: Sun, 18 Jun 2006 20:04:19 -0400 From: Tom Rhodes To: Dmitry Morozovsky Message-Id: <20060618200419.1be3a3fb.trhodes@FreeBSD.org> In-Reply-To: <20060619025709.W13558@woozle.rinet.ru> References: <20060619025709.W13558@woozle.rinet.ru> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: trhodes@FreeBSD.org, doc@FreeBSD.org Subject: Re: disk Handbook chapter, backups, and MINI kernel 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, 19 Jun 2006 00:04:24 -0000 On Mon, 19 Jun 2006 03:08:48 +0400 (MSD) Dmitry Morozovsky wrote: > Colleagues, > > in process of trhodes' 4.X handbook cleanup I found the following: > > MINI kernel config in disks chapter is seriously out of date. I'd tried to > bring it up to date (attached), but even after this kernel is about 2.4 M in > size, hence useless for floppy boot. Disabling SCSI and enabling ata/atadisk > does not help much - 2.1M Ooops! Almost forgot, this rehashes a discussion from perhaps two years ago. The original members of the discussion, IIRC, was ceri, keramida, murray, and myself. My facts and memory is a bit distorted, but a search on the mailing lists should help. No agreement was reached. -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Mon Jun 19 11:01:24 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E41616A47A for ; Mon, 19 Jun 2006 11:01:24 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DF6643D79 for ; Mon, 19 Jun 2006 11:01:15 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5JB1ESx063281 for ; Mon, 19 Jun 2006 11:01:14 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5JB1Cc2063274 for freebsd-doc@freebsd.org; Mon, 19 Jun 2006 11:01:12 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 19 Jun 2006 11:01:12 GMT Message-Id: <200606191101.k5JB1Cc2063274@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: FreeBSD doc list 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, 19 Jun 2006 11:01:24 -0000 Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/24] docs/27605 doc [patch] Cross-document references ( tags o [2001/02/02] docs/24786 doc missing FILES descriptions in sa(4) o [2001/04/02] docs/26286 doc *printf(3) etc should gain format string a [2001/08/23] docs/30008 doc [patch] French softupdates document shoul s [2001/10/07] docs/31109 doc [patch] replace gif images w/ png ones du s [2002/01/05] docs/33589 doc [patch] to doc.docbook.mk to post process o [2002/01/14] docs/33852 doc split(1) man page implies that input file a [2002/02/16] docs/35011 doc There are no commands called "diskless" o o [2002/02/22] docs/35222 doc [patch] getmsg.cgi: mailing list archive o [2002/03/06] docs/35608 doc mt(1) page uses "setmark" without explana o [2002/03/06] docs/35609 doc mt(1) page needs explanation of "long era o [2002/03/06] docs/35612 doc ps(1) page "state" description doesn't me o [2002/03/16] docs/35943 doc at(1) config files are misplaced in /var/ o [2002/03/16] docs/35953 doc hosts.equiv(5) manual is confusing or wro o [2002/03/28] docs/36432 doc Proposal for doc/share/mk: make folded bo o [2002/03/29] docs/36449 doc symlink(7) manual doesn't mention trailin o [2002/05/27] docs/38620 doc suggestion: minor rework of question in C o [2002/06/07] docs/38982 doc [patch] developers-handbook/Jail fix o [2002/06/15] docs/39348 doc diskless(8): note that kenv fetch of host o [2002/06/19] docs/39530 doc access(2) man page has unnecessarily broa o [2002/07/10] docs/40423 doc Keyboard(4)'s definition of parameters to o [2002/07/28] docs/41089 doc pax(1) -B option does not mention interac o [2002/08/20] docs/41807 doc [patch] natd(8): document natd -punch_fw o [2002/08/20] docs/41820 doc Device driver confusion in Handbook (sect o [2002/10/04] docs/43651 doc stab(5) incorrectly states to include jus o [2002/10/08] docs/43823 doc [PATCH] update to environ(7) manpage o [2002/10/09] docs/43861 doc non-trivial typo in wicontrol(8) man page o [2002/10/11] docs/43941 doc document the Rationale for Upgrade Sequen o [2002/10/15] docs/44074 doc [patch] ln(1) manual clarifications o [2002/10/29] docs/44594 doc Handbook doesn't mention drivers.flp for o [2002/12/02] docs/45940 doc burncd(1) missing info o [2002/12/11] docs/46196 doc [patch] menu_format(3): Missing return va o [2002/12/16] docs/46291 doc correlation between HZ kernel config para o [2002/12/16] docs/46295 doc please add information to Nvi recovery em o [2003/01/28] docs/47594 doc [PATCH] passwd(5) incorrectly states allo o [2003/02/02] docs/47818 doc [patch] ln(1) manpage is confusing o [2003/02/08] docs/48101 doc [patch] add documentation on the fixit di o [2003/03/06] docs/48980 doc [patch] nsgmls -s errors and sect. 3.2.1 o [2003/03/23] docs/50211 doc [PATCH] doc.docbook.mk: fix textfile crea o [2003/04/03] docs/50573 doc resolver(3): return values for res_query/ o [2003/05/06] docs/51875 doc [patch] atkbd(4) adjustment o [2003/05/06] docs/51891 doc DIAGNOSTICS in ed(4) driver manpage don't o [2003/05/07] docs/51921 doc [patch] ls(1) manpage lacks some informat o [2003/05/11] docs/52071 doc [PATCH] Add more information about soft u o [2003/06/21] docs/53575 doc Change to Handbook Section 20.9 (SMTP Aut o [2003/06/21] docs/53596 doc Updates to mt(1) manual page o [2003/06/25] docs/53732 doc quota output and quota(1) man page do not o [2003/07/13] docs/54451 doc [patch] i386_get_ldt(2): i386_{get|set}_l o [2003/07/26] docs/54879 doc jot(1) -r description s [2003/08/12] docs/55482 doc document the fact that DUMP has access to o [2003/09/24] docs/57153 doc S_IRWXU missing in fstat(2) man page? o [2003/09/30] docs/57388 doc [patch] INSTALL.TXT enhancement: mention o [2003/10/04] docs/57569 doc error on gensetdefs(8) man page o [2003/10/13] docs/57926 doc [patch] amd.conf(5) poorly format as it h o [2003/10/13] docs/57974 doc man page apropos for select macros (FD_SE o [2003/10/30] docs/58710 doc killpg(2) contains an error regarding sen o [2003/11/07] docs/59044 doc [patch] doc.docbook.mk does not properly o [2003/11/19] docs/59477 doc Outdated Info Documents at http://docs.fr o [2003/11/30] docs/59835 doc ipfw(8) man page does not warn about acce o [2003/12/23] docs/60529 doc resolver(5) man page is badly out of date o [2003/12/24] docs/60544 doc [patch] getenv(3) manpage doesn't state t o [2004/01/08] docs/61070 doc handbook: Installation docs misleading: o [2004/01/13] docs/61301 doc [patch] Manpage patch for aue(4) to enabl o [2004/01/21] docs/61667 doc Obsolete documentation on FreeBSD PnP o [2004/01/25] docs/61859 doc ddb(4): Incorrect informaiton about trace o [2004/02/06] docs/62412 doc one of the diskless boot methods describe o [2004/02/12] docs/62719 doc cross-reference pccardd(8) and devd(8) o [2004/02/12] docs/62724 doc [patch] host(1) manpage does not include o [2004/02/22] docs/63215 doc Wrong prototypes in mi_switch(9) (ref doc o [2004/03/27] docs/64807 doc Handbook section on NAT incomplete o [2004/04/02] docs/65065 doc [patch] improper language ntpd(8) man pag o [2004/04/13] docs/65477 doc release notes: installation instruction f o [2004/04/14] docs/65530 doc [patch] minor improvement to getgrent(3) o [2004/05/04] docs/66265 doc [patch] Document what -f and LD_TRACE_LOA o [2004/05/05] docs/66296 doc [patch] contrib/amd/amq/amq.8 uses log_op o [2004/05/07] docs/66343 doc [patch] unlisted supported card on man pa o [2004/05/10] docs/66483 doc [patch] share/man/man4/csa.4 grammar nits o [2004/05/17] docs/66770 doc [patch] share/man/man4/ng_pppoe.4 tyops, o [2004/05/23] docs/67078 doc [patch] MFC of a rtld(1) man page is inco f [2004/06/10] docs/67806 doc [patch] Let 5.x users know how to boot in o [2004/07/09] docs/68843 doc Dates on rc.subr(8) & rc(8) are whack. o [2004/07/09] docs/68845 doc The .At macro produces unexpected results o [2004/08/01] docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not o [2004/08/09] docs/70217 doc [patch] Suggested rewrite of docproj/sgml o [2004/08/20] docs/70697 doc pcm(4) is out of date o [2004/09/10] docs/71555 doc handbook: changes for how to run matlab o o [2004/09/13] docs/71690 doc [patch] inaccurate information in systat( f [2004/09/21] docs/71980 doc Handbook says that no other software is k o [2004/10/06] docs/72383 doc manpage for awk(1) is terribly small and o [2004/11/06] docs/73583 doc [patch] add missing instructions to ndis( o [2004/11/07] docs/73638 doc ipfw(8): Clarify syntax for use of tables o [2004/11/08] docs/73679 doc FreeBSD 5.3 Release notes mention new nat o [2004/11/28] docs/74477 doc [patch] Correct several links in the cont o [2004/12/02] docs/74612 doc [patch] updates to the glossary o [2004/12/14] docs/75068 doc login.conf(5) manual page says nothing ab o [2004/12/28] docs/75577 doc [patch] typos in man3 manual pages, login o [2005/01/05] docs/75865 doc comments on "backup-basics" in handbook o [2005/01/09] docs/75995 doc hcreate(3) documentation(?) bug o [2005/01/11] docs/76094 doc handbook: incorrect statement about parti o [2005/01/17] docs/76333 doc [patch] ferror(3): EOF indicator can be c o [2005/01/20] docs/76515 doc [patch] misleading use of make -j flag in o [2005/02/04] docs/77087 doc [patch] the bootvinum script given in the o [2005/02/24] docs/78041 doc [patch] docs for md(4) need further expla o [2005/02/27] docs/78138 doc [patch] Error in pre-installation section o [2005/03/01] docs/78240 doc [patch] handbook: replace with f [2005/03/05] docs/78440 doc POSIX semaphores don't work by default in o [2005/03/06] docs/78480 doc Networked printer setup unnecessarily com o [2005/03/07] docs/78520 doc error in man(5) lpd.conf, lpd.perms pages o [2005/03/16] docs/78915 doc rfork(2)'s RFTHREAD is not documented o [2005/03/23] docs/79156 doc buffersize knob for sound(4) is a tunable o [2005/04/20] docs/80159 doc [patch] rtld(1) mentions "%m" but it's no o [2005/05/11] docs/80871 doc terminfo(5) man page source corrupted o [2005/06/01] docs/81776 doc ifconfig(8) man page not updated with car o [2005/06/10] docs/82114 doc ndisapi(9) manual page cross-referenced b o [2005/06/21] docs/82481 doc tar(1)/gtar(1) man page mod request o [2005/06/22] docs/82508 doc misleading man page for basename(3)/dirna o [2005/06/24] docs/82595 doc 25.5.3 Configuring a bridge section of th o [2005/06/29] docs/82779 doc [patch] Kill entry for ddb manpage o [2005/07/17] docs/83621 doc [patch]: Minor omissions in /usr/src/UPDA p [2005/07/26] docs/84101 doc [patch] mt(1) manpage has erroneous synop o [2005/07/27] docs/84154 doc Handbook somewhat off in use of /boot/ker o [2005/07/29] docs/84265 doc [patch] chmod(1) manpage omits implicatio p [2005/07/29] docs/84266 doc [patch] security(8) manpage should have i o [2005/07/29] docs/84267 doc [patch] chflags(1) manual doesn't say it' o [2005/07/29] docs/84268 doc chmod(1) manpage's BUGS entry is either w o [2005/07/29] docs/84317 doc fdp-primer doesn't show class=USERNAME di o [2005/07/31] docs/84408 doc [patch] dump(8) manpage doesn't require a o [2005/08/02] docs/84467 doc [patch] bsdlabel(8) manpage uses archaic s [2005/08/03] docs/84519 doc [patch] mdoc(7) manpage needs more about o [2005/08/04] docs/84538 doc sk(4) driver supports Marvell 88E800x chi o [2005/08/04] docs/84549 doc [patch] errno(2) manpage uses "<...>" for s [2005/08/04] docs/84550 doc mdoc(7) manpage erroneously requires SYNO o [2005/08/07] docs/84645 doc intro(6) manpage should always be install o [2005/08/08] docs/84670 doc [patch] tput(1) manpage missing ENVIRONME o [2005/08/10] docs/84764 doc [patch] hosts.equiv(5) manpage should SEE o [2005/08/11] docs/84806 doc mdoc(7) manpage has section ordering prob o [2005/08/12] docs/84849 doc [patch] fdisk(8) manpage doesn't warn fdi o [2005/08/14] docs/84913 doc bsdlabel(8) manpage seems wrong about fsi o [2005/08/15] docs/84955 doc [patch] mdoc(7) manpage should mention mi o [2005/08/15] docs/84956 doc [patch] intro(5) manpage doesn't mention o [2005/08/17] docs/85062 doc [patch] tr(1) manpage omits several chara o [2005/08/17] docs/85063 doc [patch] expand(1) manpage needs to clarif o [2005/08/17] docs/85066 doc [patch] builtin(1) manpage has incomplete o [2005/08/18] docs/85097 doc [patch] devd.conf.5 lacks a lot of vital o [2005/08/18] docs/85100 doc NOTES: ICH audio device support statement o [2005/08/19] docs/85118 doc [PATCH] opiekey(1) references non-existin o [2005/08/19] docs/85127 doc [patch] loader(8) manpage uses too-rare " o [2005/08/19] docs/85128 doc loader.conf(5) autoboot_delay incompletly o [2005/08/21] docs/85186 doc [patch] ktrace(1) manpage doesn't warn ab o [2005/08/21] docs/85187 doc [patch] find(1) manpage missing block inf o [2005/08/23] docs/85243 doc Missing icmp related abbreviations for pf o [2005/08/27] docs/85353 doc [patch] minor cosmetic/punctuation change o [2005/09/19] docs/86342 doc bikeshed entry of Handbook is wrong o [2005/09/29] docs/86733 doc [patch] handbook: add using kldload as an o [2005/10/23] docs/87857 doc ifconfig(8) wireless options order matter o [2005/10/24] docs/87936 doc Handbook chapter on NIS/YP lacks good inf o [2005/11/04] docs/88477 doc Possible addition to xl(4) manpage, Diagn o [2005/11/04] docs/88503 doc mkuzip(8) references nonexistant geom_uzi o [2005/11/05] docs/88512 doc [patch] mount_ext2fs(8) man page has no d o [2005/11/20] docs/89325 doc [PATCH] Clarification of kbdmap(5), atkbd o [2005/11/24] docs/89492 doc vfs doc: some VOP_*(9) manual pages are o o [2005/11/30] docs/89747 doc [PATCH] faq: s/kbd0/ukbd0/ when USB keybo o [2005/12/16] docs/90498 doc [patch] wrong parameter name to function o [2005/12/31] docs/91149 doc read(2) can return EINVAL for unaligned a o [2006/01/04] docs/91297 doc restore(8) man page not accurate? o [2006/01/08] docs/91506 doc ndis(4) man page should be more specific o [2006/01/31] docs/92626 doc jail manpage should mention disabling som o [2006/02/12] docs/93249 doc rewrite of handbook chapter 23 (PPP & SLI o [2006/02/14] docs/93363 doc Handbook 23.11. SMTP-Authentifizierung o [2006/02/17] docs/93491 doc discrepancy man page for pam_unix(8) f [2006/02/18] docs/93517 doc Presented usage of Ports in Handbook lack o [2006/02/20] docs/93590 doc [patch] pf.conf's man page mentions route o [2006/03/06] docs/94125 doc DGE-530T doesn't work on FreeBSD v6.0 o [2006/03/17] docs/94625 doc [patch] growfs man page -- document "pani o [2006/03/21] docs/94803 doc Slightly confusing/misleading man page fo o [2006/03/28] docs/95039 doc [patch] small cosmetic syslog.conf(5) fix o [2006/03/30] docs/95104 doc tsleep() man page mentions nonexistent 'm o [2006/03/31] docs/95139 doc FAQ to move filesystem to new disk fails: o [2006/04/21] docs/96127 doc add hint to pass arp packets through filt o [2006/04/23] docs/96207 doc Comments of a sockaddr_un structure could o [2006/05/13] docs/97231 doc [patch] ndis(4) man page outdated o [2006/05/14] docs/97237 doc [patch] Fix dead links in FAQ o [2006/05/17] docs/97375 doc [PATCH] remove nonexistent man page refer o [2006/05/17] docs/97409 doc Incorrect command name in Kerberos sectio o [2006/05/26] docs/97939 doc some mistake in man of amq(8) o [2006/05/30] docs/98129 doc older versions of the handbook not easy t o [2006/06/09] docs/98759 doc [patch] sbp_targ(4) man page missing refe o [2006/06/11] docs/98801 doc [patch] gmirror(8) and glabel(8) manpages o [2006/06/12] docs/98842 doc misc requests for gdbe o [2006/06/14] docs/98941 doc Partitioning resize - only commercial pro o [2006/06/15] docs/98974 doc Missing tunables in loader(8) manpage o [2006/06/16] docs/99007 doc [patch] misleading nat configuration info 192 problems total. From owner-freebsd-doc@FreeBSD.ORG Tue Jun 20 04:33:16 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A8BA16A474 for ; Tue, 20 Jun 2006 04:33:16 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAD0D43D46 for ; Tue, 20 Jun 2006 04:33:15 +0000 (GMT) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.13.6/8.13.6) with ESMTP id k5K4XEda074354 for ; Tue, 20 Jun 2006 00:33:14 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.13.6/8.13.6/Submit) with ESMTP id k5K4XEpK074350 for ; Tue, 20 Jun 2006 00:33:14 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Tue, 20 Jun 2006 00:33:14 -0400 (EDT) From: doug To: freebsd-doc@FreeBSD.org Message-ID: <20060620002333.X70608@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: sshd_config directive processing 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, 20 Jun 2006 04:33:16 -0000 The OpenSSH man page for sshd_config specifies that the allow/deny directives are processed in the following order: DenyUsers, AllowUsers, DenyGroups, and finally AllowGroups. This should be specified in the FreeBSD man pages to prevent attempts such as: AllowUsers root@specific-host DenyUsers root* While I think processing AllowUsers before DenyUsers allows some very useful things to be done, OpenSSH defines the processing in the listed order. Specifying the order in the man page lets admins avoid useless attempts. Doug Denault From owner-freebsd-doc@FreeBSD.ORG Tue Jun 20 14:53:33 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA2F216A474 for ; Tue, 20 Jun 2006 14:53:33 +0000 (UTC) (envelope-from Andrea.Bledsoe@pearsoned.com) Received: from exprod6og56.obsmtp.com (exprod6og56.obsmtp.com [64.18.1.208]) by mx1.FreeBSD.org (Postfix) with SMTP id 2688143D68 for ; Tue, 20 Jun 2006 14:53:30 +0000 (GMT) (envelope-from Andrea.Bledsoe@pearsoned.com) Received: from source ([12.29.228.5]) by exprod6ob56.postini.com ([64.18.5.12]) with SMTP; Tue, 20 Jun 2006 07:46:35 PDT Received: from oldtms031.prenhall.com ([168.146.24.75]) by oldtms704.pearsontc.com (Sun Java System Messaging Server 6.1 (built Apr 28 2004)) with ESMTP id <0J1500L6HYDTSX10@oldtms704.pearsontc.com> for freebsd-doc@FreeBSD.org; Tue, 20 Jun 2006 10:46:41 -0400 (EDT) Received: by OLDTMS031 with Internet Mail Service (5.5.2657.72) id ; Tue, 20 Jun 2006 10:51:42 -0400 Content-return: allowed Date: Tue, 20 Jun 2006 10:50:05 -0400 From: "Bledsoe, Andrea" To: "'freebsd-doc@FreeBSD.org'" Message-id: <5753A9B81DE9D211AAC6006008176ED90E399FAD@CARMMS102> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: FreeBSD 6 Unleashed 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, 20 Jun 2006 14:53:33 -0000 Hope you are doing well! Just wondering if you would be interested in posting excerpts on your site of our new book FreeBSD 6 Unleashed, Sams Publishing? I've included the TOC below, just let me know which chapter you would like and the format and I'll get that over to you. I. Introduction to FreeBSD 1. What Is FreeBSD? 2. Installing FreeBSD 3. Advanced Installation Tasks II. FreeBSD on the Desktop 4. Your First Session with FreeBSD 5. Working with X Windows 6. Working with Applications 7. Advanced X Windows Configuration III. FreeBSD on the Command Line 8. Working with the Shell 9. Customizing the Shell 10. Shell Programming 11. Introduction to Perl Programming III. System Administration 12. The FreeBSD Filesystem 13. Users, Groups, and Permissions 14. System Configuration and Startup Scripts 15. Performance Monitoring, Process Control, and Job Automation 16. Installing Additional Software 17. Printing 18. Kernel Configuration 19. Keeping Up to Date with FreeBSD 20. Understanding Hard Disks and Filesystems 21. FreeBSD Survival Guide IV. FreeBSD Networking 22. Networking with FreeBSD 23. Configuring Basic Networking Services 24. Connecting to the Internet with PPP 25. Configuring E-mail Services 26. Configuring a Web Server 27. Configuring an FTP Server 28. Configuring an Internet Gateway 29. Configuring a Database Server 30. Network Security 31. Virtual Private Networks (VPNs) 32. The Domain Name Server 33. The Network Filesystem (NFS) 34. File and Print Sharing with Microsoft Windows 35. Dynamic Host Configuration Protocol (DHCP) VI. Appendices A. Command Reference and Configuration File Reference B. Hardware Compatibility Lists C. Troubleshooting Installation and Boot Problems D. Sources for More Information Look forward to working with you! Andrea Bledsoe, Publicist Addison-Wesley Professional | Cisco Press| Prentice Hall Professional | Que Publishing | Sams Publishing Publishing Imprints of Pearson Education 800 East 96th Street, 2nd Floor, Indianapolis, IN 46240 T. 317.428.3168 E. andrea.bledsoe@pearsoned.com *********************************************************************** This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. We may monitor email to and from our network. *********************************************************************** From owner-freebsd-doc@FreeBSD.ORG Tue Jun 20 16:10:19 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8E8716A474 for ; Tue, 20 Jun 2006 16:10:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15FF143D55 for ; Tue, 20 Jun 2006 16:10:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5KGAIjO078346 for ; Tue, 20 Jun 2006 16:10:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5KGAI57078345; Tue, 20 Jun 2006 16:10:18 GMT (envelope-from gnats) Resent-Date: Tue, 20 Jun 2006 16:10:18 GMT Resent-Message-Id: <200606201610.k5KGAI57078345@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, Christoph Weber-Fahr Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9F7116A474 for ; Tue, 20 Jun 2006 16:08:56 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9A3543D45 for ; Tue, 20 Jun 2006 16:08:56 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k5KG8u6F017321 for ; Tue, 20 Jun 2006 16:08:56 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k5KG8ua6017320; Tue, 20 Jun 2006 16:08:56 GMT (envelope-from nobody) Message-Id: <200606201608.k5KG8ua6017320@www.freebsd.org> Date: Tue, 20 Jun 2006 16:08:56 GMT From: Christoph Weber-Fahr To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: docs/99209: non working reference in FAQ about Change Xfree -> Xorg 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, 20 Jun 2006 16:10:19 -0000 >Number: 99209 >Category: docs >Synopsis: non working reference in FAQ about Change Xfree -> Xorg >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 Jun 20 16:10:18 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Christoph Weber-Fahr >Release: various >Organization: Arcor >Environment: >Description: the FAQ says: --- (in Q 11.2) ------ Note: The above describes the default X implementation installed. It is still possible to install either implementation by following the instructions in the entry for 20040723 in /usr/ports/UPDATING. ----------------------- Problems: - there is no such entry in UPDATING. There probably never was. certainly not in any of today's version, nor in any HEAD version of that time, (if you can trust CVS on that) - given the multitude of parallel versions of this file and the high frequency and opaque and seemingly arbitrary way entries come and go on these lists, a reference to this document from the FAQ is not useful. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Tue Jun 20 19:43:07 2006 Return-Path: X-Original-To: docs@freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C113A16A474 for ; Tue, 20 Jun 2006 19:43:07 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24AA743D49 for ; Tue, 20 Jun 2006 19:43:04 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.3) with ESMTP id k5KJh3Rx051303 for ; Tue, 20 Jun 2006 23:43:03 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Tue, 20 Jun 2006 23:43:03 +0400 (MSD) From: Maxim Konovalov To: docs@freebsd.org Message-ID: <20060620234139.X47887@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Subject: what releng does arch-book describe? 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, 20 Jun 2006 19:43:07 -0000 Hello, Sorry for my ignorance but what branch does our arch book tries to describe? -- Maxim Konovalov From owner-freebsd-doc@FreeBSD.ORG Tue Jun 20 20:10:20 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF50716A47A for ; Tue, 20 Jun 2006 20:10:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FA8543D48 for ; Tue, 20 Jun 2006 20:10:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5KKAKUd094314 for ; Tue, 20 Jun 2006 20:10:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5KKAKu3094308; Tue, 20 Jun 2006 20:10:20 GMT (envelope-from gnats) Resent-Date: Tue, 20 Jun 2006 20:10:20 GMT Resent-Message-Id: <200606202010.k5KKAKu3094308@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, Douglas Denault Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2E5416A47A for ; Tue, 20 Jun 2006 20:02:44 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8549343D49 for ; Tue, 20 Jun 2006 20:02:44 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k5KK2iWH082475 for ; Tue, 20 Jun 2006 20:02:44 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k5KK2isL082474; Tue, 20 Jun 2006 20:02:44 GMT (envelope-from nobody) Message-Id: <200606202002.k5KK2isL082474@www.freebsd.org> Date: Tue, 20 Jun 2006 20:02:44 GMT From: Douglas Denault To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: docs/99215: Documentation change for sshd_config 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, 20 Jun 2006 20:10:21 -0000 >Number: 99215 >Category: docs >Synopsis: Documentation change for sshd_config >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 Jun 20 20:10:19 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Douglas Denault >Release: 6.1 >Organization: Safeport Network Services >Environment: FreeBSD artemis.boltsys.com 6.1-STABLE FreeBSD 6.1-STABLE #6: Tue Jun 6 03:36:37 EDT 2006 doug@artemis.boltsys.com:/usr/obj/usr/src/sys/ARTEMIS i386 >Description: OpenSSH implements a specific order in processing the directives. The following should be added to shd_config: The allow/deny directives are processed in the following order: DenyUsers, AllowUsers, DenyGroups, and finally AllowGroups. >How-To-Repeat: man sshd_config >Fix: The following should be added to shd_config: The allow/deny directives are processed in the following order: DenyUsers, AllowUsers, DenyGroups, and finally AllowGroups. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Tue Jun 20 20:30:36 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B633116A479 for ; Tue, 20 Jun 2006 20:30:36 +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 BEEE543D73 for ; Tue, 20 Jun 2006 20:30:29 +0000 (GMT) (envelope-from keramida@FreeBSD.org) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k5KKUBpx003861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Jun 2006 23:30:13 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k5KKU511011635; Tue, 20 Jun 2006 23:30:05 +0300 (EEST) (envelope-from keramida@FreeBSD.org) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k5KKU0wg011634; Tue, 20 Jun 2006 23:30:00 +0300 (EEST) (envelope-from keramida@FreeBSD.org) Date: Tue, 20 Jun 2006 23:30:00 +0300 From: Giorgos Keramidas To: "Bledsoe, Andrea" Message-ID: <20060620203000.GC11347@gothmog.pc> References: <5753A9B81DE9D211AAC6006008176ED90E399FAD@CARMMS102> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <5753A9B81DE9D211AAC6006008176ED90E399FAD@CARMMS102> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.251, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.15, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: "'freebsd-doc@FreeBSD.org'" Subject: Re: FreeBSD 6 Unleashed 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, 20 Jun 2006 20:30:36 -0000 --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2006-06-20 10:50, "Bledsoe, Andrea" wrote: > Hope you are doing well! Just wondering if you would be > interested in posting excerpts on your site of our new book > FreeBSD 6 Unleashed, Sams Publishing? I've included the TOC > below, just let me know which chapter you would like and the > format and I'll get that over to you. It sure sounds interesting. Thanks for the offer :-) > I. Introduction to FreeBSD > 1. What Is FreeBSD? > 2. Installing FreeBSD > 3. Advanced Installation Tasks > II. FreeBSD on the Desktop > 4. Your First Session with FreeBSD > 5. Working with X Windows > 6. Working with Applications > 7. Advanced X Windows Configuration > III. FreeBSD on the Command Line > 8. Working with the Shell > 9. Customizing the Shell > 10. Shell Programming > 11. Introduction to Perl Programming > III. System Administration > 12. The FreeBSD Filesystem > 13. Users, Groups, and Permissions > 14. System Configuration and Startup Scripts > 15. Performance Monitoring, Process Control, and Job Automation > 16. Installing Additional Software > 17. Printing > 18. Kernel Configuration > 19. Keeping Up to Date with FreeBSD > 20. Understanding Hard Disks and Filesystems > 21. FreeBSD Survival Guide > IV. FreeBSD Networking > 22. Networking with FreeBSD > 23. Configuring Basic Networking Services > 24. Connecting to the Internet with PPP > 25. Configuring E-mail Services > 26. Configuring a Web Server > 27. Configuring an FTP Server > 28. Configuring an Internet Gateway > 29. Configuring a Database Server > 30. Network Security > 31. Virtual Private Networks (VPNs) > 32. The Domain Name Server > 33. The Network Filesystem (NFS) > 34. File and Print Sharing with Microsoft Windows > 35. Dynamic Host Configuration Protocol (DHCP) > VI. Appendices > A. Command Reference and Configuration File Reference > B. Hardware Compatibility Lists > C. Troubleshooting Installation and Boot Problems > D. Sources for More Information All of these chapters look interesting. I am really hard-pressed choosing one of all these interesting titles. My own preference would be for one of the chapters of the ``FreeBSD on the Desktop'' part, i.e. the introductory one: ``FreeBSD on the Desktop'' I'll let the rest of the freebsd-doc team choose too though. Whatever the majority of us prefers is also the one I will support as a choise :) Regards, Giorgos --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEmFrI1g+UGjGGA7YRAju8AJ9qd/8HnXBACpPX9H+XH0ikrBTuhgCfR994 ZaJytn6dK+w2T+Y6UvFLPmo= =0inH -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- From owner-freebsd-doc@FreeBSD.ORG Tue Jun 20 22:30:21 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5881116A4CD for ; Tue, 20 Jun 2006 22:30:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7702943D53 for ; Tue, 20 Jun 2006 22:30:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5KMUKP8003547 for ; Tue, 20 Jun 2006 22:30:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5KMUKAH003546; Tue, 20 Jun 2006 22:30:20 GMT (envelope-from gnats) Resent-Date: Tue, 20 Jun 2006 22:30:20 GMT Resent-Message-Id: <200606202230.k5KMUKAH003546@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, Dan Lukes Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF76816A479; Tue, 20 Jun 2006 22:26:34 +0000 (UTC) (envelope-from dan@kulesh.obluda.cz) Received: from smtp1.kolej.mff.cuni.cz (smtp1.kolej.mff.cuni.cz [195.113.24.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54BE143D45; Tue, 20 Jun 2006 22:26:33 +0000 (GMT) (envelope-from dan@kulesh.obluda.cz) Received: from kulesh.obluda.cz (openvpn.ms.mff.cuni.cz [195.113.20.87]) by smtp1.kolej.mff.cuni.cz (8.13.1/8.13.1) with ESMTP id k5KMQrx0000193; Wed, 21 Jun 2006 00:26:54 +0200 (CEST) (envelope-from dan@kulesh.obluda.cz) Received: from kulesh.obluda.cz (localhost [127.0.0.1] (may be forged)) by kulesh.obluda.cz (8.13.6/8.13.6) with ESMTP id k5KMQUQn001793; Wed, 21 Jun 2006 00:26:30 +0200 (CEST) (envelope-from dan@kulesh.obluda.cz) Received: (from root@localhost) by kulesh.obluda.cz (8.13.6/8.13.6/Submit) id k5KMQTYx001792; Wed, 21 Jun 2006 00:26:29 +0200 (CEST) (envelope-from dan) Message-Id: <200606202226.k5KMQTYx001792@kulesh.obluda.cz> Date: Wed, 21 Jun 2006 00:26:29 +0200 (CEST) From: Dan Lukes To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: keramida@FreeBSD.org Subject: docs/99231: [ PATCH ] malloc(3): options J and Z DOESN'T imply option R X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dan Lukes List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2006 22:30:21 -0000 >Number: 99231 >Category: docs >Synopsis: [ PATCH ] malloc(3): options J and Z DOESN'T imply option R >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 Jun 20 22:30:19 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Dan Lukes >Release: FreeBSD 6.1-STABLE i386 >Organization: Obludarium >Environment: System: FreeBSD, RELENG-6 src/lib/libc/stdlib/malloc.3,v 1.63 >Description: The malloc(3) manual page claim the options 'J' and 'Z' imply 'R' option. It's not true (see grep malloc_realloc lib/libc/stdlib/malloc.c) Beware, it apply to RELENG-6 only, not CURRENT. >How-To-Repeat: N/A >Fix: --- lib/libc/stdlib/malloc.3.ORIG Fri Jul 15 16:40:52 2005 +++ lib/libc/stdlib/malloc.3 Wed Jun 21 00:15:43 2006 @@ -36,7 +36,7 @@ .\" @(#)malloc.3 8.1 (Berkeley) 6/4/93 .\" $FreeBSD: src/lib/libc/stdlib/malloc.3,v 1.63 2005/01/20 09:17:04 ru Exp $ .\" -.Dd August 19, 2004 +.Dd June 21, 2006 .Dt MALLOC 3 .Os .Sh NAME @@ -192,9 +192,6 @@ or .Fn reallocf will be initialized to 0xd0. -This options also sets the -.Dq R -option. This is intended for debugging and will impact performance negatively. .It H Pass a hint to the kernel about pages unused by the allocation functions. @@ -241,9 +238,7 @@ .It Z This option implicitly sets the .Dq J -and -.Dq R -options, and then zeros out the bytes that were requested. +option, and then zeros out the bytes that were requested. This is intended for debugging and will impact performance negatively. .It < Reduce the size of the cache by a factor of two. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Tue Jun 20 23:43:43 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6D2516A47A; Tue, 20 Jun 2006 23:43:43 +0000 (UTC) (envelope-from keramida@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BFDC43D6A; Tue, 20 Jun 2006 23:43:43 +0000 (GMT) (envelope-from keramida@FreeBSD.org) Received: from freefall.freebsd.org (keramida@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5KNhhoh008822; Tue, 20 Jun 2006 23:43:43 GMT (envelope-from keramida@freefall.freebsd.org) Received: (from keramida@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5KNhgCr008818; Tue, 20 Jun 2006 23:43:42 GMT (envelope-from keramida) Date: Tue, 20 Jun 2006 23:43:42 GMT From: Giorgos Keramidas Message-Id: <200606202343.k5KNhgCr008818@freefall.freebsd.org> To: dan@obluda.cz, keramida@FreeBSD.org, freebsd-doc@FreeBSD.org, keramida@FreeBSD.org Cc: Subject: Re: docs/99231: [ PATCH ] malloc(3): options J and Z DOESN'T imply option R 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, 20 Jun 2006 23:43:43 -0000 Synopsis: [ PATCH ] malloc(3): options J and Z DOESN'T imply option R State-Changed-From-To: open->closed State-Changed-By: keramida State-Changed-When: Tue Jun 20 23:42:55 UTC 2006 State-Changed-Why: Committed in revision 1.63.2.1 or file http://cvsweb.freebsd.org/src/lib/libc/stdlib/malloc.3,v Thanks :) Responsible-Changed-From-To: freebsd-doc->keramida Responsible-Changed-By: keramida Responsible-Changed-When: Tue Jun 20 23:42:55 UTC 2006 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=99231 From owner-freebsd-doc@FreeBSD.ORG Wed Jun 21 14:15:16 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B79716A474; Wed, 21 Jun 2006 14:15:16 +0000 (UTC) (envelope-from Andrea.Bledsoe@pearsoned.com) Received: from exprod6og56.obsmtp.com (exprod6og56.obsmtp.com [64.18.1.208]) by mx1.FreeBSD.org (Postfix) with SMTP id EFE5743D48; Wed, 21 Jun 2006 14:15:13 +0000 (GMT) (envelope-from Andrea.Bledsoe@pearsoned.com) Received: from source ([12.29.228.5]) by exprod6ob56.postini.com ([64.18.5.12]) with SMTP; Wed, 21 Jun 2006 07:14:41 PDT Received: from oldtms031.prenhall.com ([168.146.24.75]) by oldtms704.pearsontc.com (Sun Java System Messaging Server 6.1 (built Apr 28 2004)) with ESMTP id <0J1700A5XRD0BJ00@oldtms704.pearsontc.com>; Wed, 21 Jun 2006 10:10:12 -0400 (EDT) Received: by OLDTMS031 with Internet Mail Service (5.5.2657.72) id ; Wed, 21 Jun 2006 10:15:14 -0400 Content-return: allowed Date: Wed, 21 Jun 2006 10:13:47 -0400 From: "Bledsoe, Andrea" To: 'Giorgos Keramidas' Message-id: <5753A9B81DE9D211AAC6006008176ED90E399FD3@CARMMS102> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-type: text/plain Cc: "'freebsd-doc@FreeBSD.org'" Subject: RE: FreeBSD 6 Unleashed 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, 21 Jun 2006 14:15:16 -0000 Sounds good, I'd be happy to offer the whole section: > II. FreeBSD on the Desktop > 4. Your First Session with FreeBSD > 5. Working with X Windows > 6. Working with Applications > 7. Advanced X Windows Configuration Just let me know if PDF version is ok! -----Original Message----- From: Giorgos Keramidas [mailto:keramida@FreeBSD.org] Sent: Tuesday, June 20, 2006 4:30 PM To: Bledsoe, Andrea Cc: 'freebsd-doc@FreeBSD.org' Subject: Re: FreeBSD 6 Unleashed On 2006-06-20 10:50, "Bledsoe, Andrea" wrote: > Hope you are doing well! Just wondering if you would be > interested in posting excerpts on your site of our new book > FreeBSD 6 Unleashed, Sams Publishing? I've included the TOC > below, just let me know which chapter you would like and the > format and I'll get that over to you. It sure sounds interesting. Thanks for the offer :-) > I. Introduction to FreeBSD > 1. What Is FreeBSD? > 2. Installing FreeBSD > 3. Advanced Installation Tasks > II. FreeBSD on the Desktop > 4. Your First Session with FreeBSD > 5. Working with X Windows > 6. Working with Applications > 7. Advanced X Windows Configuration > III. FreeBSD on the Command Line > 8. Working with the Shell > 9. Customizing the Shell > 10. Shell Programming > 11. Introduction to Perl Programming > III. System Administration > 12. The FreeBSD Filesystem > 13. Users, Groups, and Permissions > 14. System Configuration and Startup Scripts > 15. Performance Monitoring, Process Control, and Job Automation > 16. Installing Additional Software > 17. Printing > 18. Kernel Configuration > 19. Keeping Up to Date with FreeBSD > 20. Understanding Hard Disks and Filesystems > 21. FreeBSD Survival Guide > IV. FreeBSD Networking > 22. Networking with FreeBSD > 23. Configuring Basic Networking Services > 24. Connecting to the Internet with PPP > 25. Configuring E-mail Services > 26. Configuring a Web Server > 27. Configuring an FTP Server > 28. Configuring an Internet Gateway > 29. Configuring a Database Server > 30. Network Security > 31. Virtual Private Networks (VPNs) > 32. The Domain Name Server > 33. The Network Filesystem (NFS) > 34. File and Print Sharing with Microsoft Windows > 35. Dynamic Host Configuration Protocol (DHCP) > VI. Appendices > A. Command Reference and Configuration File Reference > B. Hardware Compatibility Lists > C. Troubleshooting Installation and Boot Problems > D. Sources for More Information All of these chapters look interesting. I am really hard-pressed choosing one of all these interesting titles. My own preference would be for one of the chapters of the ``FreeBSD on the Desktop'' part, i.e. the introductory one: ``FreeBSD on the Desktop'' I'll let the rest of the freebsd-doc team choose too though. Whatever the majority of us prefers is also the one I will support as a choise :) Regards, Giorgos *********************************************************************** This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. We may monitor email to and from our network. *********************************************************************** From owner-freebsd-doc@FreeBSD.ORG Wed Jun 21 16:19:04 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1394116A4CC for ; Wed, 21 Jun 2006 16:19:04 +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 8500E43D67 for ; Wed, 21 Jun 2006 16:18:55 +0000 (GMT) (envelope-from keramida@FreeBSD.org) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k5LGIbRL010925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Jun 2006 19:18:39 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k5LGIU6q076513; Wed, 21 Jun 2006 19:18:31 +0300 (EEST) (envelope-from keramida@FreeBSD.org) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k5LGISor076492; Wed, 21 Jun 2006 19:18:28 +0300 (EEST) (envelope-from keramida@FreeBSD.org) Date: Wed, 21 Jun 2006 19:18:28 +0300 From: Giorgos Keramidas To: "Bledsoe, Andrea" Message-ID: <20060621161828.GB55720@gothmog.pc> References: <5753A9B81DE9D211AAC6006008176ED90E399FD3@CARMMS102> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5/uDoXvLw7AC5HRs" Content-Disposition: inline In-Reply-To: <5753A9B81DE9D211AAC6006008176ED90E399FD3@CARMMS102> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.248, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.15, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@FreeBSD.org Subject: Re: FreeBSD 6 Unleashed 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, 21 Jun 2006 16:19:04 -0000 --5/uDoXvLw7AC5HRs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2006-06-21 10:13, "Bledsoe, Andrea" wrote: >Giorgos Keramidas [mailto:keramida@FreeBSD.org] wrote: >>On 2006-06-20 10:50, "Bledsoe, Andrea" wrote: >>> Hope you are doing well! Just wondering if you would be >>> interested in posting excerpts on your site of our new book >>> FreeBSD 6 Unleashed, Sams Publishing? I've included the TOC >>> below, just let me know which chapter you would like and the >>> format and I'll get that over to you. >> >> It sure sounds interesting. Thanks for the offer :-) >> [...] >> All of these chapters look interesting. I am really >> hard-pressed choosing one of all these interesting titles. My >> own preference would be for one of the chapters of the >> ``FreeBSD on the Desktop'' part, i.e. the introductory one: >> >> ``FreeBSD on the Desktop'' >> >> I'll let the rest of the freebsd-doc team choose too though. >> Whatever the majority of us prefers is also the one I will >> support as a choise :) > > Sounds good, I'd be happy to offer the whole section: > > II. FreeBSD on the Desktop > 4. Your First Session with FreeBSD > 5. Working with X Windows > 6. Working with Applications > 7. Advanced X Windows Configuration > > Just let me know if PDF version is ok! Yes, IMHO, a PDF version would be fine. Thanks again :) --5/uDoXvLw7AC5HRs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEmXFU1g+UGjGGA7YRApluAJ9jALlxneDjJjZp4INze49523vpHACgkDh8 0iptG0ymPCJOuYuLddtHQEc= =Fcck -----END PGP SIGNATURE----- --5/uDoXvLw7AC5HRs-- From owner-freebsd-doc@FreeBSD.ORG Wed Jun 21 16:40:20 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FCA916A47C for ; Wed, 21 Jun 2006 16:40:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5979643D55 for ; Wed, 21 Jun 2006 16:40:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5LGeJKt080552 for ; Wed, 21 Jun 2006 16:40:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5LGeJGo080550; Wed, 21 Jun 2006 16:40:19 GMT (envelope-from gnats) Resent-Date: Wed, 21 Jun 2006 16:40:19 GMT Resent-Message-Id: <200606211640.k5LGeJGo080550@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, Intron Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76A7F16A474 for ; Wed, 21 Jun 2006 16:37:10 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AC9D43D55 for ; Wed, 21 Jun 2006 16:37:10 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k5LGb9bk054724 for ; Wed, 21 Jun 2006 16:37:09 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k5LGb9gg054720; Wed, 21 Jun 2006 16:37:09 GMT (envelope-from nobody) Message-Id: <200606211637.k5LGb9gg054720@www.freebsd.org> Date: Wed, 21 Jun 2006 16:37:09 GMT From: Intron To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: docs/99260: Make Traditional Chinese PDF/PostScript of FreeBSD Documents 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, 21 Jun 2006 16:40:20 -0000 >Number: 99260 >Category: docs >Synopsis: Make Traditional Chinese PDF/PostScript of FreeBSD Documents >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jun 21 16:40:18 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Intron >Release: 7.0-CURRENT >Organization: China >Environment: 7.0-CURRENT i386 >Description: Please forward this PR to vanilla@freebsd.org Apply the following patch. And remove "zh_TW.Big5" after "NO_TEX_LANG?=" in doc/share/mk/doc.docbook.mk. If you have any question, please contact me or delphij@freebsd.org. See: 1. The port chinese/docproj. 2. Comments of revision 1.125 on http://www.freebsd.org/cgi/cvsweb.cgi/doc/share/mk/doc.docbook.mk 3. http://www.freebsd.org/cgi/cvsweb.cgi/doc/zh_CN.GB2312/share/mk/doc.local.mk >How-To-Repeat: >Fix: Index: doc.local.mk =================================================================== RCS file: /cvsroot/ncvs/doc/zh_TW.Big5/share/mk/doc.local.mk,v retrieving revision 1.1 diff -u -r1.1 doc.local.mk --- doc.local.mk 26 Jan 2006 16:13:46 -0000 1.1 +++ doc.local.mk 21 Jun 2006 16:27:06 -0000 @@ -2,4 +2,9 @@ SP_ENCODING?= ${LANGCODE:C,^.*\.,,} -SGMLFLAGS+= -D ${IMAGES_EN_DIR}/${DOC}s/${.CURDIR:T} +CJKTEXSTY?= ${PREFIX}/bin/cjktexsty +CJKTEXSTY_TEX_FLAGS?= -e ${SP_ENCODING} -f t1song +CJKTEXSTY_PDFTEX_FLAGS?= -c -e ${SP_ENCODING} -f song + +PDFJADETEX_PREPROCESS= ${CJKTEXSTY} ${CJKTEXSTY_PDFTEX_FLAGS} +JADETEX_PREPROCESS= ${CJKTEXSTY} ${CJKTEXSTY_TEX_FLAGS} >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Thu Jun 22 20:56:54 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF37F16A529 for ; Thu, 22 Jun 2006 20:56:54 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EC2945485 for ; Thu, 22 Jun 2006 20:27:07 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k5MKQCgM011816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 22 Jun 2006 23:26:30 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k5MKPqhm002988; Thu, 22 Jun 2006 23:26:02 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k5MKPoEx002987; Thu, 22 Jun 2006 23:25:50 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 22 Jun 2006 23:25:50 +0300 From: Giorgos Keramidas To: Rich Morin Message-ID: <20060622202550.GB2655@gothmog.pc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.386, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 1.01, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: checking man page includes and prototypes? 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, 22 Jun 2006 20:56:54 -0000 On 2006-06-14 09:15, Rich Morin wrote: > I'm doing a lot of editing of section 2 and 3 man pages, concentrating > on the includes and prototypes. Although I'm trying to be careful, > it's quite likely that some errors will slip past me. So, I'm casting > about for a way to do an automated sanity check. Here's one idea: > > For each man page > For each prototype > Construct a C test file. > Compile the test file. > Look for nastygrams, etc. > > For example, the sysconf(3) SYNOPSIS contains the lines: > > #include > > long > sysconf(int name); > > I can turn this into the file test.c: > > #include > > main() { > > int name; > sysconf(name); > } > > Compiling this (e.g., "cc test.c") finishes silently. So far, so > good... > > Editing "sysconf" into "sysconfx" produces a promising nastygram: > > /usr/bin/ld: Undefined symbols: > _sysconfx > collect2: ld returned 1 exit status > > > However, editing "int name;" into "float name;' does NOT cause a > nastygram. So, it appears that prototype checking is not being done. > The gcc(1) man page gave me the idea of trying > > gcc -pedantic -ansi test.c > > but this didn't make any visible difference. I see a bazillion other > options, including a bunch of "-W..." goodies, but I'd rather not try > them all at random. I tried "gcc -pedantic -ansi -Wstrict-prototypes > test.c", but it only complained about my "main" statement (?): > > test.c:3: warning: function declaration isn't a prototype > > Any suggestions (general or specific) on how I might be able to cajole > gcc (or whatever) into helping me? This is a _great_ idea! If it's not too much trouble to generate a `Makefile' along with your test source file, you can generate something like: # giorgos@gothmog:/var/tmp/testimdR$ cat -n Makefile # 1 PROG= test-sysconf # 2 NO_MAN= No manpage generated for automated test. # 3 # 4 WARNS?= 6 # 5 # 6 .include # giorgos@gothmog:/var/tmp/testimdR$ cat -n test-sysconf.c # 1 #include # 2 # 3 int # 4 main(void) # 5 { # 6 int name = 0; # 7 # 8 sysconf(name); # 9 return 0; # 10 } # giorgos@gothmog:/var/tmp/testimdR$ This will let you catch *some* of the potential bugs, by reusing the makefile magic of the bsd.prog.mk suite, i.e.: # giorgos@gothmog:/var/tmp/testimdR$ env CFLAGS='-O -pipe -ansi -pedantic' make clean # rm -f test-sysconf test-sysconf.o # giorgos@gothmog:/var/tmp/testimdR$ env CFLAGS='-O -pipe -ansi -pedantic' make # Warning: Object directory not changed from original /var/tmp/testimdR # cc -O -pipe -ansi -pedantic -g -Wsystem-headers -Werror -Wall \ # -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes \ # -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual \ # -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter \ # -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls \ # -c test-sysconf.c # cc -O -pipe -ansi -pedantic -g -Wsystem-headers -Werror -Wall \ # -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes \ # -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual \ # -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter \ # -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls \ # -o test-sysconf test-sysconf.o # giorgos@gothmog:/var/tmp/testimdR$ Alas, this will not catch all type-errors too, because the compiler may implicitly convert values. For instance, it doesn't catch the bug of passing a `double' argument to sysconf() here: # giorgos@gothmog:/var/tmp/testimdR$ cat -n test-sysconf.c # 1 #include # 2 # 3 int # 4 main(void) # 5 { # 6 double name = 123456789.0E10L; # 7 # 8 sysconf(name); # 9 return 0; # 10 } # giorgos@gothmog:/var/tmp/testimdR$ env CFLAGS='-O -pipe -ansi -pedantic' make clean all # rm -f test-sysconf test-sysconf.o # Warning: Object directory not changed from original /var/tmp/testimdR # cc -O -pipe -ansi -pedantic -g -Wsystem-headers -Werror -Wall \ # -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes \ # -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual \ # -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter \ # -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls \ # -c test-sysconf.c # cc -O -pipe -ansi -pedantic -g -Wsystem-headers -Werror -Wall \ # -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes \ # -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual \ # -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter \ # -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls \ # -o test-sysconf test-sysconf.o # giorgos@gothmog:/var/tmp/testimdR$ The only good things about generating a temporary regression test in `/var/tmp/testXXXX'-style directories, full with a minimal `Makefile' and `test-foo.c' file are that: * You can take advantage of the `clean' and `cleandir' targets to rerun the test manually if it fails (as long as the test directory is left untouched for inspection). * You can take advantage of the existing `makefile magic' for compiler options, flags, warning levels, etc. * You can auto-generate the LDADD and DPADD parts of the Makefile from the LIBRARY section of the manpage and see if that one os correct too. * etc. There are probably other good reasons why a Makefile-based approach is good, but unfortunately it still doesn't catch all possible errors (as you can see above). Regards, Giorgos From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 02:08:07 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54CFC16A47B; Fri, 23 Jun 2006 02:08:07 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E630143D46; Fri, 23 Jun 2006 02:08:06 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5N286pQ014629; Fri, 23 Jun 2006 02:08:06 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5N286Sm014625; Fri, 23 Jun 2006 02:08:06 GMT (envelope-from linimon) Date: Fri, 23 Jun 2006 02:08:06 GMT From: Mark Linimon Message-Id: <200606230208.k5N286Sm014625@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-www@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: Subject: Re: docs/99336: Unclear handbook wording about firewall_enable 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, 23 Jun 2006 02:08:07 -0000 Old Synopsis: Unclear handbook wording New Synopsis: Unclear handbook wording about firewall_enable Responsible-Changed-From-To: freebsd-www->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jun 23 02:06:41 UTC 2006 Responsible-Changed-Why: This is actually a 'docs' PR; 'www' is for things that only appear on the website. http://www.freebsd.org/cgi/query-pr.cgi?pr=99336 From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 10:00:35 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA01716A4DE for ; Fri, 23 Jun 2006 10:00:35 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0295743D45 for ; Fri, 23 Jun 2006 10:00:34 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5NA0YdR047354 for ; Fri, 23 Jun 2006 10:00:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5NA0Yfn047353; Fri, 23 Jun 2006 10:00:34 GMT (envelope-from gnats) Resent-Date: Fri, 23 Jun 2006 10:00:34 GMT Resent-Message-Id: <200606231000.k5NA0Yfn047353@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, Valerio.Daelli.valerio.daelli@gmail.com Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7207316A49A for ; Fri, 23 Jun 2006 09:58:54 +0000 (UTC) (envelope-from eldon@dbs.ifom-firc.it) Received: from mail.ifom-firc.it (mail.ifom-firc.it [85.239.175.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id A10A843D45 for ; Fri, 23 Jun 2006 09:58:53 +0000 (GMT) (envelope-from eldon@dbs.ifom-firc.it) Received: (qmail 6693 invoked by uid 811); 23 Jun 2006 09:59:34 -0000 Received: from 85.239.175.67 by mail.ifom-firc.it (envelope-from , uid 803) with qmail-scanner-1.25 (clamdscan: 0.88.2/1562. f-prot: 4.4.2/3.14.11. spamassassin: 3.1.3. Clear:RC:1(85.239.175.67):. Processed in 0.163549 secs); 23 Jun 2006 09:59:34 -0000 Received: from unknown (HELO dbs.ifom-firc.it) ([85.239.175.67]) (envelope-sender ) by smtp.ifom-firc.it (qmail-ldap-1.03) with SMTP for ; 23 Jun 2006 09:59:34 -0000 Received: (from eldon@dbs.ifom-firc.it) by dbs.ifom-firc.it (mini_sendmail/1.3.6 29jun2005); Fri, 23 Jun 2006 11:58:51 CEST (sender eldon@dbs.ifom-firc.it) Message-Id: <20060623095853.A10A843D45@mx1.FreeBSD.org> Date: Fri, 23 Jun 2006 09:58:53 +0000 (GMT) From: Valerio.Daelli.valerio.daelli@gmail.com To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: docs/99356: man page of sendmsg(2) does not include EINVAL X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Valerio.Daelli.valerio.daelli@gmail.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2006 10:00:36 -0000 >Number: 99356 >Category: docs >Synopsis: man page of sendmsg(2) does not include EINVAL >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 Jun 23 10:00:34 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Valerio Daelli >Release: FreeBSD 5.4-RELEASE-p12 i386 >Organization: IFOM >Environment: System: FreeBSD dbs.ifom-firc.it 5.4-RELEASE-p12 FreeBSD 5.4-RELEASE-p12 #0: Thu Mar 2 15:40:11 CET 2006 root@dbs.ifom-firc.it:/usr/obj/usr/src/sys/DBS i386 >Description: The man page of sendmsg(2) does not include EINVAL as possible error value. EINVAL is a possible error value as it appears in then sendit() function in /usr/src/sys/kern/uipc_syscalls.c >How-To-Repeat: man sendmsg >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 12:50:22 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3018C16A4AB for ; Fri, 23 Jun 2006 12:50:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5FF843D45 for ; Fri, 23 Jun 2006 12:50:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5NCoL1w056831 for ; Fri, 23 Jun 2006 12:50:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5NCoLsr056830; Fri, 23 Jun 2006 12:50:21 GMT (envelope-from gnats) Date: Fri, 23 Jun 2006 12:50:21 GMT Message-Id: <200606231250.k5NCoLsr056830@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Giorgos Keramidas Cc: Subject: Re: docs/99336: Unclear handbook wording X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Giorgos Keramidas List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2006 12:50:22 -0000 The following reply was made to PR docs/99336; it has been noted by GNATS. From: Giorgos Keramidas To: Merijn Verstraaten Cc: bug-followup@freebsd.org Subject: Re: docs/99336: Unclear handbook wording Date: Fri, 23 Jun 2006 15:41:16 +0300 On 2006-06-23 00:16, Merijn Verstraaten wrote: > Firewall chapter, IPFW configuration (26.6) > > "If you do not have IPFW compiled into your kernel you will need to > load it with the following statement in your /etc/rc.conf: > > firewall_enable="YES"" > > It's not clear that while IPFW will start fine without > firewall_enable="YES" in rc.conf if you have it compiled into your > kernel, the rules script provided with firewall_script won't run if > firewall_enable="YES" isn't set. Hmmm, well the text is unclear. It doesn't matter if you compile `IPFW' support into your kernel or not these days. The /etc/rc.d/ipfw script will take care of loading the module automatically. Even `DUMMYNET' can be loaded as a module in FreeBSD 7.0-CURRENT now. Can someone from the freebsd-doc people who has access to a STABLE system check if auto-loading of ipfw.ko and dummynet.ko modules works as expected in FreeBSD 6.X too? Then we should remove this confusing part about ``having IPFW compiled into your kernel''. - Giorgos From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 13:26:25 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39B5516A4A0 for ; Fri, 23 Jun 2006 13:26:25 +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 5CFC243D45 for ; Fri, 23 Jun 2006 13:26:24 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k5NDQ5s7014503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 23 Jun 2006 16:26:07 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k5NDPwlv007916; Fri, 23 Jun 2006 16:25:59 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k5NDPw1J007915; Fri, 23 Jun 2006 16:25:58 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Fri, 23 Jun 2006 16:25:58 +0300 From: Giorgos Keramidas To: Kostik Belousov Message-ID: <20060623132558.GD7062@gothmog.pc> References: <20060607084346.GA21391@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060607084346.GA21391@deviant.kiev.zoral.com.ua> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.268, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.13, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: [patch] deadlock debugging 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, 23 Jun 2006 13:26:25 -0000 On 2006-06-07 11:43, Kostik Belousov wrote: > Reports of the deadlocks are reccurrent topic on the current- > and stable- lists. Many of us have to repeat the instructions > on how to provide the useful initial bug report from them. > > Please, comment proposed addition to the kernel debugging > chapter of the developer handbook. Hi Kostik, > Obviously, I am not an english native speaker. Your corrections > for both factual material and grammar/style are very much > welcome ! > > P.S. I'm not on the list, do not remove CC: to me on replying. Ok :) This seems like a useful addition to the developer's handbook, but I have some minor comments. See inline text below: > Index: en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml > =================================================================== > RCS file: /usr/local/arch/ncvs/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml,v > retrieving revision 1.64 > diff -u -r1.64 chapter.sgml > --- en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml 5 Jan 2006 20:03:34 -0000 1.64 > +++ en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml 7 Jun 2006 08:39:20 -0000 > @@ -821,6 +821,41 @@ > on any configured console driver, including a serial > console. > > + > + > + Debugging the Deadlocks `Debugging Kernel Deadlocks' is probably a better title here, since deadlocks can only occur in the kernel and `the Deadlocks' doesn't really make this as obvious as I'd probably want it to be. > + You may experience so called deadlocks, the situation where > + system stops doing useful work. To provide the useful bug report > + in this situation, you shall use ddb as described above. Please, > + include the output of ps and > + trace for suspected processes in the > + report. This paragraph has a few minor syntax buglets. English is not my native language, but I would probably rewrite this as: | Modern &os; releases have been extended with support for | Symmetric Multiprocessing (SMP). To support highly parallel | processing, the &os; kernel uses a lot of internal locking and | synchronization primitives, to allow multiple kernel threads | to run concurrently on systems that can support such a mode of | operation. Bugs in the use of these internal locking | mechanisms can lead to a situation where one or more kernel | threads block compete for the same resources and block | indefinitely waiting for each other. When this happens, the | system may become unstable, leading either to a crash or | appear to hang. This hang is called a | deadlock. | | Debugging a deadlock may be a tricky and difficult thing, | but &os; provides some tools that may assist you in tracking | down the problem or collect information about the deadlock | when it occurs. | | One of these tools is the kernel debugger, | DDB, which you can use as described | in the previous sections to collect useful information for | such a bug. DDB commands that are | very useful and may provide information that helps debugging a | deadlock are: | | | ps | trace | | | Use the ps command to list all the | processes and then use trace on processes | that are suspects for having caused the deadlock. | | Other commands that can provide useful information for | tracking down the cause of a deadlock are: | | | show allcpu | show alllocks | show lockedvnods | | | Useful information about what each process was doing, at | the time the deadlock occured, can be listed with: | | | where PID | | | The output of the where command tends | to be very useful for the processes listed in the output of | the show commands. | | To obtain meaningful backtraces for threaded processes, | use thread thread-id first, to switch to | the correct thread, and then get a backtrace | with where. Does this version look ok to you? I can handle the merging of this change with your initial diff/patch > + If possible, consider doing further investigation. Receipt > + below is especially usefull if you suspect deadlock occurs in the > + VFS layer. Add the options > + makeoptions DEBUG=-g > + options INVARIANTS > + options INVARIANT_SUPPORT > + options WITNESS > + options DEBUG_LOCKS > + options DEBUG_VFS_LOCKS > + options DIAGNOSTIC > + > + to the kernel config. When deadlock occurs, in addition to the > + output of the ps command, provide information > + from the show allpcpu, show > + alllocks and show > + lockedvnods. More, please provide output of the > + where pid for each process id mentioned in > + the output of the show commands. > + > + > + For threaded processes, to obtain meaningful backtraces, use > + thread thread-id to switch to the thread > + stack, and do backtrace with where. > + > This part is also nice, but IMHO it would be even nicer if we could expand it a bit more. How about something like this? | | | Deadlocks are pretty nasty bugs, since they are not very | easy to reproduce. Their occurence depends on specific | timing, synchronization, system load and many more factors. | This makes it hard to reliably reproduce a deadlock bug. | Since reproducing a bug is some times a crucial part of | gathering all the necessary information, you may have to spend | some time investigating the deadlock. Naturally, this is not | always possible for production systems, but if you can | reproduce the deadlock on a test system which can afford | staying off-line for extended periods of time, then consider | staying inside DDB while you are | investigating the deadlock further. | | A serial console can be extremely helpful in collecting | DDB output. | | If it's impossible to set up a serial console | (i.e. because you cannot find or afford a second system to | configure as a testbed), emulators like | emulators/qemu, | emulators/vmware2 or | emulators/bochs may prove a | very efficient way of debugging kernel issues, like a | deadlock. Part #2 ... | | | Apart from the usual kernel options that are useful for | debugging kernel problems, there are some options that are | prticularly useful and targetted at debugging locking | problems. These options are: | | options INVARIANTS | options INVARIANT_SUPPORT | options WITNESS | options DEBUG_LOCKS | options DEBUG_VFS_LOCKS | options DIAGNOSTIC Any help in expanding these parts (especially the second one) is more than welcome :-) From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 13:37:52 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED37016A4B3; Fri, 23 Jun 2006 13:37:52 +0000 (UTC) (envelope-from keramida@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E3C243D48; Fri, 23 Jun 2006 13:37:47 +0000 (GMT) (envelope-from keramida@FreeBSD.org) Received: from freefall.freebsd.org (keramida@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5NDblYU060229; Fri, 23 Jun 2006 13:37:47 GMT (envelope-from keramida@freefall.freebsd.org) Received: (from keramida@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5NDblPQ060225; Fri, 23 Jun 2006 13:37:47 GMT (envelope-from keramida) Date: Fri, 23 Jun 2006 13:37:47 GMT From: Giorgos Keramidas Message-Id: <200606231337.k5NDblPQ060225@freefall.freebsd.org> To: vd@datamax.bg, keramida@FreeBSD.org, freebsd-doc@FreeBSD.org, keramida@FreeBSD.org Cc: Subject: Re: docs/90498: [patch] wrong parameter name to function twalk in tseatch(3) 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, 23 Jun 2006 13:37:53 -0000 Synopsis: [patch] wrong parameter name to function twalk in tseatch(3) State-Changed-From-To: open->closed State-Changed-By: keramida State-Changed-When: Fri Jun 23 13:36:52 UTC 2006 State-Changed-Why: Committed in revision 1.14 of src/lib/libc/stdlib/tsearch.3,v Thanks :-) Responsible-Changed-From-To: freebsd-doc->keramida Responsible-Changed-By: keramida Responsible-Changed-When: Fri Jun 23 13:36:52 UTC 2006 Responsible-Changed-Why: I'll handle the MFC of this patch http://www.freebsd.org/cgi/query-pr.cgi?pr=90498 From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 13:58:45 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EA2E16A492; Fri, 23 Jun 2006 13:58:45 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1489843D46; Fri, 23 Jun 2006 13:58:43 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k5NDwb6j049688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Jun 2006 16:58:37 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k5NDwbhe073870; Fri, 23 Jun 2006 16:58:37 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k5NDwbHE073869; Fri, 23 Jun 2006 16:58:37 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 23 Jun 2006 16:58:37 +0300 From: Kostik Belousov To: Giorgos Keramidas Message-ID: <20060623135837.GI5115@deviant.kiev.zoral.com.ua> References: <20060607084346.GA21391@deviant.kiev.zoral.com.ua> <20060623132558.GD7062@gothmog.pc> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KZLWU/9q3evlN4nQ" Content-Disposition: inline In-Reply-To: <20060623132558.GD7062@gothmog.pc> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-0.1 required=5.0 tests=ALL_TRUSTED,SPF_NEUTRAL autolearn=failed version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-doc@freebsd.org Subject: Re: [patch] deadlock debugging 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, 23 Jun 2006 13:58:45 -0000 --KZLWU/9q3evlN4nQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 23, 2006 at 04:25:58PM +0300, Giorgos Keramidas wrote: > On 2006-06-07 11:43, Kostik Belousov wrote: > > Reports of the deadlocks are reccurrent topic on the current- > > and stable- lists. Many of us have to repeat the instructions > > on how to provide the useful initial bug report from them. > > > > Please, comment proposed addition to the kernel debugging > > chapter of the developer handbook. >=20 > Hi Kostik, >=20 > > Obviously, I am not an english native speaker. Your corrections > > for both factual material and grammar/style are very much > > welcome ! > > > > P.S. I'm not on the list, do not remove CC: to me on replying. >=20 > Ok :) >=20 > This seems like a useful addition to the developer's handbook, > but I have some minor comments. See inline text below: >=20 > > Index: en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sg= ml > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > RCS file: /usr/local/arch/ncvs/doc/en_US.ISO8859-1/books/developers-han= dbook/kerneldebug/chapter.sgml,v > > retrieving revision 1.64 > > diff -u -r1.64 chapter.sgml > > --- en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml = 5 Jan 2006 20:03:34 -0000 1.64 > > +++ en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml = 7 Jun 2006 08:39:20 -0000 > > @@ -821,6 +821,41 @@ > > on any configured console driver, including a serial > > console. > > > > + > > + > > + Debugging the Deadlocks >=20 > `Debugging Kernel Deadlocks' is probably a better title here, since > deadlocks can only occur in the kernel and `the Deadlocks' doesn't > really make this as obvious as I'd probably want it to be. >=20 > > + You may experience so called deadlocks, the situation where > > + system stops doing useful work. To provide the useful bug report > > + in this situation, you shall use ddb as described above. Please, > > + include the output of ps and > > + trace for suspected processes in the > > + report. >=20 > This paragraph has a few minor syntax buglets. English is not my native > language, but I would probably rewrite this as: >=20 > | Modern &os; releases have been extended with support for > | Symmetric Multiprocessing (SMP). To support highly parallel > | processing, the &os; kernel uses a lot of internal locking and > | synchronization primitives, to allow multiple kernel threads > | to run concurrently on systems that can support such a mode of > | operation. Bugs in the use of these internal locking > | mechanisms can lead to a situation where one or more kernel > | threads block compete for the same resources and block > | indefinitely waiting for each other. When this happens, the > | system may become unstable, leading either to a crash or > | appear to hang. This hang is called a > | deadlock. > | > | Debugging a deadlock may be a tricky and difficult thing, > | but &os; provides some tools that may assist you in tracking > | down the problem or collect information about the deadlock > | when it occurs. > | > | One of these tools is the kernel debugger, > | DDB, which you can use as described > | in the previous sections to collect useful information for > | such a bug. DDB commands that are > | very useful and may provide information that helps debugging a > | deadlock are: > | > | > | ps > | trace > | > | > | Use the ps command to list all the > | processes and then use trace on processes > | that are suspects for having caused the deadlock. > | > | Other commands that can provide useful information for > | tracking down the cause of a deadlock are: > | > | > | show allcpu > | show alllocks > | show lockedvnods > | > | > | Useful information about what each process was doing, at > | the time the deadlock occured, can be listed with: > | > | > | where PID > | > | > | The output of the where command tends > | to be very useful for the processes listed in the output of > | the show commands. > | > | To obtain meaningful backtraces for threaded processes, > | use thread thread-id first, to switch to > | the correct thread, and then get a backtrace > | with where. >=20 > Does this version look ok to you? I can handle the merging of this > change with your initial diff/patch >=20 > > + If possible, consider doing further investigation. Receipt > > + below is especially usefull if you suspect deadlock occurs in the > > + VFS layer. Add the options > > + makeoptions DEBUG=3D-g > > + options INVARIANTS > > + options INVARIANT_SUPPORT > > + options WITNESS > > + options DEBUG_LOCKS > > + options DEBUG_VFS_LOCKS > > + options DIAGNOSTIC > > + > > + to the kernel config. When deadlock occurs, in addition to the > > + output of the ps command, provide information > > + from the show allpcpu, show > > + alllocks and show > > + lockedvnods. More, please provide output of the > > + where pid for each process id mentioned in > > + the output of the show commands. > > + > > + > > + For threaded processes, to obtain meaningful backtraces, use > > + thread thread-id to switch to the thread > > + stack, and do backtrace with where. > > + > > >=20 > This part is also nice, but IMHO it would be even nicer if we could > expand it a bit more. How about something like this? >=20 > | > | > | Deadlocks are pretty nasty bugs, since they are not very > | easy to reproduce. Their occurence depends on specific > | timing, synchronization, system load and many more factors. > | This makes it hard to reliably reproduce a deadlock bug. > | Since reproducing a bug is some times a crucial part of > | gathering all the necessary information, you may have to spend > | some time investigating the deadlock. Naturally, this is not > | always possible for production systems, but if you can > | reproduce the deadlock on a test system which can afford > | staying off-line for extended periods of time, then consider > | staying inside DDB while you are > | investigating the deadlock further. > | > | A serial console can be extremely helpful in collecting > | DDB output. > | > | If it's impossible to set up a serial console > | (i.e. because you cannot find or afford a second system to > | configure as a testbed), emulators like > | emulators/qemu, > | emulators/vmware2 or > | emulators/bochs may prove a > | very efficient way of debugging kernel issues, like a > | deadlock. >=20 > Part #2 ... >=20 > | > | > | Apart from the usual kernel options that are useful for > | debugging kernel problems, there are some options that are > | prticularly useful and targetted at debugging locking > | problems. These options are: > | > | options INVARIANTS > | options INVARIANT_SUPPORT > | options WITNESS > | options DEBUG_LOCKS > | options DEBUG_VFS_LOCKS > | options DIAGNOSTIC >=20 > Any help in expanding these parts (especially the second one) is more > than welcome :-) I like you changes, they provide useful context and give the proper exposure to the problems. My intent for the addition was to have the place for pointing out when asked "how to debug deadlocks" ? Could you additions and my do-it guide coexist side-by-side ? For instance, by summarizing the information developers want to obtain from the problem machine, at the end of section ? --KZLWU/9q3evlN4nQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEm/OMC3+MBN1Mb4gRAsYDAJ9WmXYJ4BDgs8SmDpe37e5EF6gKSQCfRWVc kKjbgq1fC5RMzZMPVk9mUDo= =6ydb -----END PGP SIGNATURE----- --KZLWU/9q3evlN4nQ-- From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 14:18:22 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A704A16A492 for ; Fri, 23 Jun 2006 14:18:22 +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 D325A43D53 for ; Fri, 23 Jun 2006 14:18:21 +0000 (GMT) (envelope-from keramida@FreeBSD.org) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k5NEI3R7020488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 23 Jun 2006 17:18:05 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k5NEHvQL009334; Fri, 23 Jun 2006 17:17:57 +0300 (EEST) (envelope-from keramida@FreeBSD.org) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k5NEHuvU009333; Fri, 23 Jun 2006 17:17:56 +0300 (EEST) (envelope-from keramida@FreeBSD.org) Date: Fri, 23 Jun 2006 17:17:56 +0300 From: Giorgos Keramidas To: Kostik Belousov Message-ID: <20060623141756.GA9283@gothmog.pc> References: <20060607084346.GA21391@deviant.kiev.zoral.com.ua> <20060623132558.GD7062@gothmog.pc> <20060623135837.GI5115@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060623135837.GI5115@deviant.kiev.zoral.com.ua> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.284, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.12, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@FreeBSD.org Subject: Re: [patch] deadlock debugging 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, 23 Jun 2006 14:18:22 -0000 On 2006-06-23 16:58, Kostik Belousov wrote: > On Fri, Jun 23, 2006 at 04:25:58PM +0300, Giorgos Keramidas wrote: > > This seems like a useful addition to the developer's handbook, > > but I have some minor comments. See inline text below: > > [...] > > Does this version look ok to you? I can handle the merging of this > > change with your initial diff/patch > > I like you changes, they provide useful context and give the > proper exposure to the problems. Thanks :) > My intent for the addition was to have the place for pointing out when > asked "how to debug deadlocks" ? Could you additions and my do-it > guide coexist side-by-side ? For instance, by summarizing the > information developers want to obtain from the problem machine, at the > end of section ? That's a good idea. Do you think it makes sense to split the addition to sub-sections, i.e.: + Debugging Kernel Deadlocks - What is a deadlock - Using DDB to gather deadlock information - Kernel options useful for deadlock debugging - Summary I didn't add elements around the text I sent, but this shouldn't be very hard to do, I guess. From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 14:32:10 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3391E16A494; Fri, 23 Jun 2006 14:32:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2074C43D49; Fri, 23 Jun 2006 14:32:08 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k5NEW1d0050536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Jun 2006 17:32:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k5NEW01g074453; Fri, 23 Jun 2006 17:32:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k5NEW0RH074452; Fri, 23 Jun 2006 17:32:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 23 Jun 2006 17:32:00 +0300 From: Kostik Belousov To: Giorgos Keramidas Message-ID: <20060623143200.GJ5115@deviant.kiev.zoral.com.ua> References: <20060607084346.GA21391@deviant.kiev.zoral.com.ua> <20060623132558.GD7062@gothmog.pc> <20060623135837.GI5115@deviant.kiev.zoral.com.ua> <20060623141756.GA9283@gothmog.pc> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TC23+W66xmFESAX" Content-Disposition: inline In-Reply-To: <20060623141756.GA9283@gothmog.pc> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-0.1 required=5.0 tests=ALL_TRUSTED,SPF_NEUTRAL autolearn=failed version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-doc@freebsd.org Subject: Re: [patch] deadlock debugging 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, 23 Jun 2006 14:32:10 -0000 --6TC23+W66xmFESAX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 23, 2006 at 05:17:56PM +0300, Giorgos Keramidas wrote: > On 2006-06-23 16:58, Kostik Belousov wrote: > > My intent for the addition was to have the place for pointing out when > > asked "how to debug deadlocks" ? Could you additions and my do-it > > guide coexist side-by-side ? For instance, by summarizing the > > information developers want to obtain from the problem machine, at the > > end of section ? >=20 > That's a good idea. Do you think it makes sense to split the addition > to sub-sections, i.e.: >=20 > + Debugging Kernel Deadlocks > - What is a deadlock > - Using DDB to gather deadlock information > - Kernel options useful for deadlock debugging > - Summary >=20 > I didn't add elements around the text I sent, but this shouldn't > be very hard to do, I guess. Exactly! This structuring going to be the best. --6TC23+W66xmFESAX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEm/tfC3+MBN1Mb4gRAqJhAJ9AKpn33Xx/9pqr0ocW3qA20pItxACgu1S2 N8TI6u8HlE0vxblC+dzb96U= =Du9n -----END PGP SIGNATURE----- --6TC23+W66xmFESAX-- From owner-freebsd-doc@FreeBSD.ORG Fri Jun 23 16:38:24 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A9A916A492 for ; Fri, 23 Jun 2006 16:38:24 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66FAA43D53 for ; Fri, 23 Jun 2006 16:38:22 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k5NGc8qM000860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 23 Jun 2006 19:38:10 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k5NGc2AM078003; Fri, 23 Jun 2006 19:38:02 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k5NGc10Z077990; Fri, 23 Jun 2006 19:38:01 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Fri, 23 Jun 2006 19:38:01 +0300 From: Giorgos Keramidas To: Max Laier Message-ID: <20060623163801.GA54335@gothmog.pc> References: <200606020950.14480.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200606020950.14480.max@love2party.net> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.416, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.98, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: kern/97057: IPSEC + pf needs note? 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, 23 Jun 2006 16:38:24 -0000 On 2006-06-02 09:50, Max Laier wrote: > Hi, > anyone up for taking responsibility for this? I don't think we > should change GENERIC for it, but it should clearly be > documented somewhere somehow. > > Thanks. Copying the text of the report here too: # Message-Id: <200605092157.k49LvPN1061507@www.freebsd.org> # Date: Tue, 9 May 2006 21:57:25 GMT # From: Dmitry Andrianov # # When IPSEC is configured according to handbook # ( http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html ) # but pf is us ed instead of ipfw, users experience very strange # TCP connection stalls. # # In addition to me experiencing that problem # ( http://lists.freebsd.org/pipermail/freebsd-pf/2006-May/002129.html ) # # I believe followi ng reports also refer the same problem I had: # http://lists.freebsd.org/pipermail/freebsd-net/2005-October/008812.html # http://lists.freebsd.org/pipermail/freebsd-net/2005-October/008745.html # # The problem is caused by the fact PF can not properly track state # because it does not see packets coming from the tunnel to gif # inte rface. The problem is resolved by rebuilding kernel with # IPSEC_FILTERGIF. And the real challenge is to find that solution # because al l the references to that option say that it is needed # if you want filtering on gif. I do NOT want filtering on gif, I # want filtering on other interfaces but it does not work either. # # In my opinion, IPSEC_FILTERGIF option should be on by default. If # it is absolutely unacceptable, documentation should be fixed to # re flect "side effect" of enabling IPSEC/FAST_IPSEC without # IPSEC_FILTERGIF Since the problem described can be a side-effect of the IPSEC setup the Handbook describes, I guess we should fix the Handbook to mention the IPSEC_FILTERGIF option. Does the following look ok? # giorgos@gothmog:/home/giorgos/ws/doc/en_US.ISO8859-1/books/handbook/security$ svk log -v -r 8:9 # ---------------------------------------------------------------------- # r9: giorgos | 2006-06-23 19:36:51 +0300 # Changed paths: # M /trunk/doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml # # Mention that IPSEC_FILTERGIF is needed to successfully use some of our # firewalls and IPSEC at the same time. # ---------------------------------------------------------------------- # giorgos@gothmog:/home/giorgos/ws/doc/en_US.ISO8859-1/books/handbook/security$ svk diff -v -r 8:9 # === chapter.sgml # ================================================================== # --- chapter.sgml (revision 8) # +++ chapter.sgml (revision 9) # @@ -3117,7 +3117,17 @@ # Fast IPsec subsystem in lieu of the KAME # implementation of IPsec. Consult the &man.fast.ipsec.4; # manual page for more information. # + # # + # + To let firewalls properly track state for &man.gif.4; # + tunnels too, you have to enable the # + in your kernel # + configuration: # + # + # +options IPSEC_FILTERGIF #filter ipsec packets from a tunnel # + # # # # giorgos@gothmog:/home/giorgos/ws/doc/en_US.ISO8859-1/books/handbook/security$ From owner-freebsd-doc@FreeBSD.ORG Sat Jun 24 00:57:59 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C10416A492 for ; Sat, 24 Jun 2006 00:57:59 +0000 (UTC) (envelope-from rdm@cfcl.com) Received: from cfcl.com (cpe-24-221-172-174.ca.sprintbbd.net [24.221.172.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7AB343D46 for ; Sat, 24 Jun 2006 00:57:58 +0000 (GMT) (envelope-from rdm@cfcl.com) Received: from [192.168.254.205] ([192.168.254.205]) by cfcl.com (8.12.6/8.12.6) with ESMTP id k5O141vF049711 for ; Fri, 23 Jun 2006 18:04:02 -0700 (PDT) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: Date: Fri, 23 Jun 2006 17:57:51 -0700 To: freebsd-doc@FreeBSD.org From: Rich Morin Content-Type: text/plain; charset="us-ascii" Cc: Subject: mdoc editing caveats? 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, 24 Jun 2006 00:57:59 -0000 I'm inserting "LEGACY SYNOPSIS" sections to some mdoc-based man pages. Using .Fo and .Fa in these sections, I find that they act differently than they do in the SYNOPSIS section: * .Fo does not force a blank line. * .Fa (just after .Fo) does not cause a line break. Before I edit the macros to act "just like they do in the SYNOPSIS section" for the LEGACY SYNOPSIS section, I thought I should ask if anyone has any caveats to offer. Nu? -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume rdm@cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Technical editing and writing, programming, and web development From owner-freebsd-doc@FreeBSD.ORG Sat Jun 24 03:06:20 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B64C116A47B for ; Sat, 24 Jun 2006 03:06:20 +0000 (UTC) (envelope-from joseph.koshy@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 1F80243D48 for ; Sat, 24 Jun 2006 03:06:19 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so136195uge for ; Fri, 23 Jun 2006 20:06:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=j3ZjvTAVJBEslh1ulsyqkmhNToGO6Mm8cmMWWNYvIXu9BgUtCD66WrzuJfPRvw4nLa4G/x3rhqW5w2TfzQ/2JDkLs2OIo5bpHsrq8vvymJzucT/F1/7cBA58Vf/PVh71DsLk3OWTRnB4IHeIGR37zMOT7rarXXkKBe2MJtEmVm8= Received: by 10.78.122.11 with SMTP id u11mr1502112huc; Fri, 23 Jun 2006 20:06:18 -0700 (PDT) Received: by 10.78.50.15 with HTTP; Fri, 23 Jun 2006 20:06:18 -0700 (PDT) Message-ID: <84dead720606232006lec9bde4g4e5b3d0d6326e5f9@mail.gmail.com> Date: Sat, 24 Jun 2006 08:36:18 +0530 From: "Joseph Koshy" To: "Rich Morin" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-doc@freebsd.org Subject: Re: mdoc editing caveats? 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, 24 Jun 2006 03:06:20 -0000 > I'm inserting "LEGACY SYNOPSIS" sections to some mdoc-based > man pages. What is a "LEGACY SYNOPSIS"? -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-doc@FreeBSD.ORG Sat Jun 24 03:24:22 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8689D16A492 for ; Sat, 24 Jun 2006 03:24:22 +0000 (UTC) (envelope-from rdm@cfcl.com) Received: from cfcl.com (cpe-24-221-172-174.ca.sprintbbd.net [24.221.172.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC84643D46 for ; Sat, 24 Jun 2006 03:24:21 +0000 (GMT) (envelope-from rdm@cfcl.com) Received: from [192.168.254.205] ([192.168.254.205]) by cfcl.com (8.12.6/8.12.6) with ESMTP id k5O3UQvF092421 for ; Fri, 23 Jun 2006 20:30:27 -0700 (PDT) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: In-Reply-To: <84dead720606232006lec9bde4g4e5b3d0d6326e5f9@mail.gmail.com> References: <84dead720606232006lec9bde4g4e5b3d0d6326e5f9@mail.gmail.com> Date: Fri, 23 Jun 2006 20:22:11 -0700 To: freebsd-doc@freebsd.org From: Rich Morin Content-Type: text/plain; charset="us-ascii" Subject: Re: mdoc editing caveats? 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, 24 Jun 2006 03:24:22 -0000 At 8:36 AM +0530 6/24/06, Joseph Koshy wrote: >> I'm inserting "LEGACY SYNOPSIS" sections to some mdoc-based >> man pages. > > What is a "LEGACY SYNOPSIS"? Not that it's relevant to the technical question, but... The behavior of some commands and functions is being brought into line with POSIXish standards, but the old behavior is still available (in "legacy" mode). So, the client wants to have both documented. -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume rdm@cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Technical editing and writing, programming, and web development From owner-freebsd-doc@FreeBSD.ORG Sat Jun 24 12:21:07 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1D8616A4AB; Sat, 24 Jun 2006 12:21:07 +0000 (UTC) (envelope-from vanilla@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8239943D6B; Sat, 24 Jun 2006 12:21:04 +0000 (GMT) (envelope-from vanilla@FreeBSD.org) Received: from freefall.freebsd.org (vanilla@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5OCL4X3059219; Sat, 24 Jun 2006 12:21:04 GMT (envelope-from vanilla@freefall.freebsd.org) Received: (from vanilla@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5OCL1Q0059215; Sat, 24 Jun 2006 12:21:01 GMT (envelope-from vanilla) Date: Sat, 24 Jun 2006 12:21:01 GMT From: "Vanilla I. Shu" Message-Id: <200606241221.k5OCL1Q0059215@freefall.freebsd.org> To: intron@intron.ac, vanilla@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: Subject: Re: docs/99260: [patch] Make Traditional Chinese PDF/PostScript of FreeBSD Documents 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, 24 Jun 2006 12:21:07 -0000 Synopsis: [patch] Make Traditional Chinese PDF/PostScript of FreeBSD Documents State-Changed-From-To: open->closed State-Changed-By: vanilla State-Changed-When: Sat Jun 24 12:21:01 UTC 2006 State-Changed-Why: Committed, thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=99260 From owner-freebsd-doc@FreeBSD.ORG Sat Jun 24 19:06:05 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBE7416A4C2 for ; Sat, 24 Jun 2006 19:06:05 +0000 (UTC) (envelope-from cezarym@data.pl) Received: from v00058.home.net.pl (data.pl [212.85.96.58]) by mx1.FreeBSD.org (Postfix) with SMTP id E35BE43D45 for ; Sat, 24 Jun 2006 19:06:04 +0000 (GMT) (envelope-from cezarym@data.pl) Received: from localhost (HELO ?192.168.1.11?) (cezarym.data@home@127.0.0.1) by mail01.home.net.pl with SMTP; Sat, 24 Jun 2006 19:06:00 -0000 From: Cezary Morga To: freebsd-doc@freebsd.org Date: Sat, 24 Jun 2006 21:11:41 +0200 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200606242111.43579.cezarym@data.pl> Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Subject: The FreeBSD Polish Documentation Project 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, 24 Jun 2006 19:06:06 -0000 Hi there, I'm having some problems contacting the team working on Polish translation. So I'm wondering if anyone 'round here know what's going on with this project? Best regards, -- Cezary Morga GG# 169903 ICQ# 328-700-565 Jabber: thereidos(at)jabber.autocom.pl http://thereidos.co.nr/