From owner-freebsd-doc@FreeBSD.ORG Sun Oct 16 02:39:37 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 438F2106564A for ; Sun, 16 Oct 2011 02:39:37 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 02C488FC12 for ; Sun, 16 Oct 2011 02:39:36 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id p9G2davO008194; Sat, 15 Oct 2011 20:39:36 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id p9G2dZSJ008191; Sat, 15 Oct 2011 20:39:36 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 15 Oct 2011 20:39:35 -0600 (MDT) From: Warren Block To: John-Mark Gurney In-Reply-To: <20111015174641.GQ14645@funkthat.com> Message-ID: References: <20111015174641.GQ14645@funkthat.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sat, 15 Oct 2011 20:39:36 -0600 (MDT) Cc: freebsd-doc@freebsd.org Subject: Re: minor rewording for committers guide 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, 16 Oct 2011 02:39:37 -0000 On Sat, 15 Oct 2011, John-Mark Gurney wrote: > I was trying to find the repo for the www, but the note IMO was poorly > worded, so I have this patch. Should I go ahead and commit? > > P.S. I'm not on the list, so please include me in the reply. > > Thanks. > > Index: article.sgml > =================================================================== > RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v > retrieving revision 1.303 > diff -u -r1.303 article.sgml > --- article.sgml 11 Sep 2011 18:04:15 -0000 1.303 > +++ article.sgml 15 Oct 2011 17:40:26 -0000 > @@ -304,9 +304,10 @@ > CVS but in Subversion. The official > and exported trees are not necessarily equal. > > - Note that the www module containing sources > - for the FreeBSD website is > - contained within the doc repository. > + Note that the sources for the > + FreeBSD website are I think that should be &os; website are (untested) From owner-freebsd-doc@FreeBSD.ORG Sun Oct 16 07:15:41 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C6391065673; Sun, 16 Oct 2011 07:15:41 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0379B8FC15; Sun, 16 Oct 2011 07:15:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9G7FeEG074663; Sun, 16 Oct 2011 07:15:40 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9G7Fepc074658; Sun, 16 Oct 2011 07:15:40 GMT (envelope-from eadler) Date: Sun, 16 Oct 2011 07:15:40 GMT Message-Id: <201110160715.p9G7Fepc074658@freefall.freebsd.org> To: aiza21@comclark.com, eadler@FreeBSD.org, freebsd-doc@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: docs/145067: Remove all reference to floppy installs 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, 16 Oct 2011 07:15:41 -0000 Synopsis: Remove all reference to floppy installs State-Changed-From-To: open->closed State-Changed-By: eadler State-Changed-When: Sun Oct 16 07:15:40 UTC 2011 State-Changed-Why: see docs/155982 http://www.freebsd.org/cgi/query-pr.cgi?pr=145067 From owner-freebsd-doc@FreeBSD.ORG Sun Oct 16 07:16:26 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5A471065670; Sun, 16 Oct 2011 07:16:26 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9DBCB8FC15; Sun, 16 Oct 2011 07:16:26 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9G7GQRx074846; Sun, 16 Oct 2011 07:16:26 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9G7GQsJ074842; Sun, 16 Oct 2011 07:16:26 GMT (envelope-from eadler) Date: Sun, 16 Oct 2011 07:16:26 GMT Message-Id: <201110160716.p9G7GQsJ074842@freefall.freebsd.org> To: lists@eitanadler.com, eadler@FreeBSD.org, freebsd-doc@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: docs/155982: [handbook] reaper of the dead: remove reference to floppy installations 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, 16 Oct 2011 07:16:26 -0000 Synopsis: [handbook] reaper of the dead: remove reference to floppy installations State-Changed-From-To: open->closed State-Changed-By: eadler State-Changed-When: Sun Oct 16 07:16:26 UTC 2011 State-Changed-Why: give (based on 145067) http://www.freebsd.org/cgi/query-pr.cgi?pr=155982 From owner-freebsd-doc@FreeBSD.ORG Sun Oct 16 07:16:43 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8149E1065673; Sun, 16 Oct 2011 07:16:43 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 58B618FC19; Sun, 16 Oct 2011 07:16:43 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9G7GhTM074980; Sun, 16 Oct 2011 07:16:43 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9G7Gh40074975; Sun, 16 Oct 2011 07:16:43 GMT (envelope-from eadler) Date: Sun, 16 Oct 2011 07:16:43 GMT Message-Id: <201110160716.p9G7Gh40074975@freefall.freebsd.org> To: lists@eitanadler.com, eadler@FreeBSD.org, freebsd-doc@FreeBSD.org, pgj@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: docs/155982: [handbook] reaper of the dead: remove reference to floppy installations 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, 16 Oct 2011 07:16:43 -0000 Synopsis: [handbook] reaper of the dead: remove reference to floppy installations State-Changed-From-To: closed->open State-Changed-By: eadler State-Changed-When: Sun Oct 16 07:16:40 UTC 2011 State-Changed-Why: give (based on 145067) Responsible-Changed-From-To: freebsd-doc->pgj Responsible-Changed-By: eadler Responsible-Changed-When: Sun Oct 16 07:16:40 UTC 2011 Responsible-Changed-Why: give (based on 145067) http://www.freebsd.org/cgi/query-pr.cgi?pr=155982 From owner-freebsd-doc@FreeBSD.ORG Sun Oct 16 11:13:02 2011 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32929106564A for ; Sun, 16 Oct 2011 11:13:02 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxout1.bln1.prohost.de (mxout1.bln1.prohost.de [213.160.84.47]) by mx1.freebsd.org (Postfix) with ESMTP id 9BC0F8FC08 for ; Sun, 16 Oct 2011 11:13:01 +0000 (UTC) Received: from mx1bln1.prossl.de (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.14.1/8.14.1) with ESMTP id p9GB29RI001678; Sun, 16 Oct 2011 13:02:09 +0200 Received: from 79.199.42.180 (SquirrelMail authenticated user benedict) by mx1bln1.prossl.de with HTTP; Sun, 16 Oct 2011 13:02:09 +0200 (CEST) Message-ID: <61046.79.199.42.180.1318762929.squirrel@mx1bln1.prossl.de> In-Reply-To: References: <201110121030.p9CAUDxd032245@freefall.freebsd.org> Date: Sun, 16 Oct 2011 13:02:09 +0200 (CEST) From: "Benedict Reuschling" To: "Garrett Cooper" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Null-Tag: 2240acf00c09c67e6daf6b565241aed4 Cc: freebsd-doc@FreeBSD.org, Niclas Zeising Subject: Re: docs/160696: style(9) should be mentioned in the devs' handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2011 11:13:02 -0000 > On Sat, Oct 15, 2011 at 3:53 PM, Benjamin Kaduk wrote: >> On Fri, 14 Oct 2011, Garrett Cooper wrote: >> >>> On Thu, Oct 13, 2011 at 11:37 PM, Warren Block >>> wrote: >>>> >>>> On Thu, 13 Oct 2011, Garrett Cooper wrote: >>>> >>>>> On Thu, Oct 13, 2011 at 9:13 PM, Warren Block >>>>> wrote: >>>>>> >>>>>> On Fri, 14 Oct 2011, Benjamin Kaduk wrote: >>>>>> >>>>>>> The overall paragraph feels a bit odd, though; maybe like it's >>>>>>> written >>>>>>> in >>>>>>> a more informal style than I would expect?  A more standard dry, >>>>>>> technical >>>>>>> writing version might be: >>>>>>> %%%%%%%%%% >>>>>>> When working in a large codebase such as the &os; source, it >>>>>>> is >>>>>>> important to adhere to a common coding style.  This provides >>>>>>> uniformity >>>>>> >>>>>>               ^^^^^^ >>>>>> "conform" might be better here. >>>>> >>>>> I'm usually not touchy feely about wording like this, but unless the >>>>> rest of the document is worded in such a standoffish / cold manner, I >>>>> would just keep things polite and neutral. "Conform" sounds really >>>>> pushy and "When working in a..." sounds condescending in my opinion. >>>> >>>> Here's a rewrite: >>>> >>>> Consistent coding style is extremely important, particularly >>>> with >>>>  large projects like &os;.  Code should follow the &os; coding styles >>>>  described in &man.style.9;, and &man.style.Makefile.5;. >>> >>> Sounds ok. >> >> No arguments, here. >> (Well, except for Garrett's mailer's mangling of the whitespace ...) > > I think we can all agree that Gmail is pretty braindead when used from > the web interface.. > -Garrett ;-) It is. Can one of you post the latest patch with the corrections (whitespace, wording, etc.) you discussed to the GNATS audit trail of this PR, so I can commit it? Thanks! Regards Benedict From owner-freebsd-doc@FreeBSD.ORG Sun Oct 16 17:15:10 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB0D41065672; Sun, 16 Oct 2011 17:15:10 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C2F1B8FC1D; Sun, 16 Oct 2011 17:15:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9GHFAJE057437; Sun, 16 Oct 2011 17:15:10 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9GHFAj1057433; Sun, 16 Oct 2011 17:15:10 GMT (envelope-from eadler) Date: Sun, 16 Oct 2011 17:15:10 GMT Message-Id: <201110161715.p9GHFAj1057433@freefall.freebsd.org> To: eadler@FreeBSD.org, pgj@FreeBSD.org, freebsd-doc@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: docs/155982: [handbook] reaper of the dead: remove reference to floppy installations 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, 16 Oct 2011 17:15:11 -0000 Synopsis: [handbook] reaper of the dead: remove reference to floppy installations Responsible-Changed-From-To: pgj->freebsd-doc Responsible-Changed-By: eadler Responsible-Changed-When: Sun Oct 16 17:14:48 UTC 2011 Responsible-Changed-Why: return to the pool. sorry for the GNATS spam http://www.freebsd.org/cgi/query-pr.cgi?pr=155982 From owner-freebsd-doc@FreeBSD.ORG Mon Oct 17 01:03:52 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E04B4106564A; Mon, 17 Oct 2011 01:03:52 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B8FFF8FC0A; Mon, 17 Oct 2011 01:03:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9H13qJ4094395; Mon, 17 Oct 2011 01:03:52 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9H13qAc094391; Mon, 17 Oct 2011 01:03:52 GMT (envelope-from eadler) Date: Mon, 17 Oct 2011 01:03:52 GMT Message-Id: <201110170103.p9H13qAc094391@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-doc@FreeBSD.org, eadler@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: docs/144408: [patch] update makefs(8) (remove device option) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2011 01:03:53 -0000 Synopsis: [patch] update makefs(8) (remove device option) Responsible-Changed-From-To: freebsd-doc->eadler Responsible-Changed-By: eadler Responsible-Changed-When: Mon Oct 17 01:03:52 UTC 2011 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=144408 From owner-freebsd-doc@FreeBSD.ORG Mon Oct 17 11:06:07 2011 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C25361065670 for ; Mon, 17 Oct 2011 11:06:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B07F48FC1A for ; Mon, 17 Oct 2011 11:06:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9HB67hk098451 for ; Mon, 17 Oct 2011 11:06:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9HB67M1098449 for freebsd-doc@FreeBSD.org; Mon, 17 Oct 2011 11:06:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 17 Oct 2011 11:06:07 GMT Message-Id: <201110171106.p9HB67M1098449@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: FreeBSD doc list Cc: Subject: Current unassigned doc problem reports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2011 11:06:07 -0000 (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/161588 doc Missing "-l name" option from pw(8) USER section o docs/161496 doc zfs(1): Please document that sysctl vfs.usermount must o docs/161057 doc [handbook] Error in section 18.17.4 of the handbook o docs/160698 doc Remove outdated FreeBSD Jumpstart guide o docs/160491 doc [patch] reaper of the dead: remove ancient FAQ entries o docs/160447 doc [handbook] Developer's Handbook contains some outdated o docs/160446 doc [handbook] Handbook sound setup seems outdated o docs/160445 doc [handbook] Handbook does not mention ACL o docs/160399 doc Man page for re(4) missing jumbo frames info o docs/160269 doc [patch] Handbook wireless section: sand off some rough o docs/159898 doc [patch] libusb.3 whitespace, markup, grammar fixes o docs/159897 doc [handbook] [patch] improve HAST section of Handbook o docs/159854 doc [patch] grammar updates for carp.4 o docs/159551 doc [patch] ports(7) makes no mention of LOCALBASE o docs/159307 doc [patch] lpd smm chapter unconditionally installed o docs/159298 doc [handbook] document Konqueror with Webkit support to i o docs/158813 doc [patch] grammar updates for jme(4) o docs/158388 doc Incorrect documentation of LOCAL_SCRIPT in release(7) o docs/158387 doc The tree(3) man should mention the RB_FOREACH_SAFE() A o docs/158378 doc cpio/bsdcpio(1) man page does not document -0 and --nu o docs/157908 doc [handbook] Description of post-install should include o docs/157698 doc [patch] gpart(8) man page contains old/incorrect size o docs/157453 doc [patch] document 16-fib cap in setfib.2 o docs/157452 doc [patch] grammar and style nits in ipfw.8 o docs/157337 doc [handbook] [patch] Indentation changes to network serv o docs/157316 doc [patch] update devstat(9) man page o docs/157234 doc [patch] nullfs(5): //proc/curproc/file returns "unknow o docs/157049 doc FreeBSD Handbook: Chapter 14 (Security) Inaccuracy o docs/156955 doc bug in share/man/man2/setsockopt.2 a docs/156920 doc isspecial(3) is not helpful o docs/156815 doc chmod(1): manpage should describe that chmod kicks +t o docs/156689 doc stf(4) output-only documentation gives bad configurati f docs/156187 doc [handbook] [patch] Add bsnmpd to handbook o docs/156081 doc troff falls with troff.core with UTF-8 man with incorr o docs/155989 doc [patch] Fix offset in boot.config(5) o docs/155982 doc [handbook] reaper of the dead: remove reference to flo o docs/155773 doc dialog(1): dialog manpages not updated o docs/155149 doc [patch] don't encourage using xorg.conf outside of PRE o docs/154838 doc update cvs-tags information on releng_* to reflect sup o docs/153958 doc ksu man-page documented, but not installed o docs/153738 doc [patch] Docuement requirement to alter some sysctls wh a docs/153012 doc [patch] iostat(8) requires an argument to -c option o docs/151752 doc pw.conf(5) doesn't define format for file clearly o docs/151367 doc [patch] Update for puc.4 man page o docs/150991 doc [patch] Install upgtfw using pkg_add as advised in upg o docs/150917 doc [patch] icmp.4, wrong description of icmplim and icmpl o docs/150877 doc ambiguity in newsyslog(8) man page about zfs with comp o docs/150365 doc [make.conf] [patch] remove BDECFLAGS from make.conf(5) o docs/150255 doc dtrace description should mention makeoptions DEBUG=-g o docs/150219 doc zfs(8) manual page misses jail/unjail o docs/149574 doc [patch] update mi_switch(9) man page o docs/149522 doc Russian network article: incorrect translation about n o docs/149051 doc [request] No document for clang or clang++ o docs/149047 doc [patch] tcsh(1) bears no mention of brace expansion in o docs/148987 doc [patch] {MD[245]|SHA_|SHA1_|SHA256_}{End|File|FileChun o docs/148984 doc [handbook] Mistake in section 16.15.4 of the handbook o docs/148680 doc [sysctl][patch] Document some sys/kern sysctls o docs/148071 doc Failover mode between wired and wireless interfaces o docs/147995 doc elf.5 man page has has missing reference o docs/146958 doc bad link to "XaQti XMAC II datasheet" in sk(4) manual o docs/146521 doc [handbook] Update IPv6 system handbook section to ment o docs/145719 doc [patch] 7.3 relnotes erroneously describes new getpage o docs/145699 doc hexdump(1) mutes all format qualifier output following o docs/145644 doc Add artical about creating manpage from scratch o docs/145069 doc Dialup firewalling with FreeBSD article out dated. o docs/145066 doc Update for new uart dev names for serial port. s docs/144818 doc all mailinglist archives dated 19970101 contain traili o docs/144630 doc [patch] domainname(1) manpage contains old information o docs/144537 doc Missing _mdconfig_list and _mdconfig2_list explanation o docs/144515 doc [handbook] Expand handbook Table of contents o docs/144488 doc share/examples/etc/make.conf: contains dangerous examp o docs/143850 doc procfs(5) manpage for status > controlling terminal is o docs/143416 doc [handbook] IPFW handbook page issues o docs/143408 doc man filedesc(9) is missing o docs/142168 doc [patch] ld(1): ldd(1) not mentioned in ld(1) manpage o docs/141032 doc misleading documentation for rtadvd.conf(5) raflags se s docs/140847 doc [request] add documentation on ECMP and new route args p docs/140457 doc [patch] Grammar fix for isspace(3) o docs/140444 doc [patch] New Traditional Chinese translation of custom- o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd o docs/139336 doc [request] ZFS documentation suggestion o docs/139165 doc gssapi.3 man page out of sync with between crypto and o docs/139018 doc translation of submitting.sgml from docproj/submitting o docs/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic o docs/138663 doc system(3) man page confuses users about "return value o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa o docs/136666 doc [handbook] Configure serial port for remote kernel deb o docs/136035 doc ftpchroot(5) omits an important option o docs/135516 doc [patch] pax(1) manual not mentioning chflags unawarene o docs/135475 doc [patch] jot(1) manpage and behaviour differ o docs/134123 doc The RUNQUEUE(9) man page is out of date o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132718 doc [handbook] Information about adding a new mirror is ou o docs/132260 doc dhcpd(8) pid not stored in documented location o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg( o docs/131918 doc [patch] Fixes for the BPF(4) man page o docs/131626 doc [patch] dump(8) "recommended" cache option confusing o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson o docs/129464 doc using packages system o docs/129095 doc ipfw(8): Can not check that packet originating/destine s docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/127908 doc [patch] readdir(3) error documentation s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126484 doc libc function res-zonscut2 is not documented o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121585 doc [handbook] Wrong multicast specification s docs/121541 doc [request] no man pages for wlan_scan_ap o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120539 doc Inconsistent ipfw's man page o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118214 doc close(2) error returns incomplete o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/116116 doc mktemp (3) re/move note o docs/116080 doc PREFIX is documented, but not the more important LOCAL p docs/115065 doc [patch] sync ps.1 with p_flag and keywords o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/112804 doc groff(1) command should be called to explicitly use "p o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat o docs/111425 doc Missing chunks of text in historical manpages o docs/111265 doc [request] Clarify how to set common shell variables o docs/111147 doc hostapd.conf is not documented o docs/110999 doc carp(4) should document unsupported interface types o docs/110692 doc wi(4) man page doesn't say WPA is not supported o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir o docs/110253 doc [patch] rtprio(1): remove processing starvation commen o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit p docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109973 doc No manual entry for c++filt o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/106135 doc [request] articles/vinum needs to be updated o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/100196 doc man login.conf does explain not "unlimited" o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings o docs/98974 doc Missing tunables in loader(8) manpage o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91506 doc ndis(4) man page should be more specific about support o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand o docs/83820 doc getino(3) manpage not installed o docs/81611 doc [patch] natd runs with -same_ports by default o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/61605 doc [request] Improve documentation for i386 disk geometry o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour o docs/57298 doc [patch] add using compact flash cards info to handbook s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/51480 doc Multiple undefined references in the FreeBSD manual pa o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] Add documentation on the fixit disk o docs/43823 doc [patch] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/38982 doc [patch] developers-handbook/Jail fix o docs/38556 doc EPS file of beastie, as addition to existing examples s docs/35678 doc docproj Makefiles for web are broken for paths with sp s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. a docs/30008 doc [patch] French softupdates document should be translat o docs/27605 doc [patch] Cross-document references () o docs/26286 doc *printf(3) etc should gain format string warnings o docs/24786 doc missing FILES descriptions in sa(4) s docs/20028 doc ASCII docs should reflect tags in the sourc 196 problems total. From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 00:05:16 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 064B7106566B for ; Wed, 19 Oct 2011 00:05:16 +0000 (UTC) (envelope-from root@ns6.wowcardeals.com) Received: from ns6.wowcardeals.com (ns6.wowcardeals.com [217.23.9.146]) by mx1.freebsd.org (Postfix) with ESMTP id 836FB8FC0C for ; Wed, 19 Oct 2011 00:05:15 +0000 (UTC) Received: by ns6.wowcardeals.com (Postfix, from userid 0) id CCE4D90A16C; Wed, 19 Oct 2011 03:26:19 +0400 (MSD) To: freebsd-doc@freebsd.org From: 'Drive a New BMW for R4999 P/M' Content-Disposition: inline Message-Id: <20111018232619.CCE4D90A16C@ns6.wowcardeals.com> Date: Wed, 19 Oct 2011 03:26:19 +0400 (MSD) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Drive A New BMW for R4999 P/M 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, 19 Oct 2011 00:05:16 -0000 wowbmw.com Drive a new BMW from R4999 per month! Can't see the pictures? [1]Click here to view this email online. Save up to R1 411.54 per month [2]BMW E90 320i BMW E90 320i Petrol (Manual) * From R4 999.00 per month. * Manual * 2.0L Petrol * Radio/CD * Aircon Climate Control * Central Locking * ABS/ASC + T&CBC * Fog Lamps * Cruise Control * Alloy Wheels * Isofix * Multifunction Steering Wheel * Cruise Control * Run Flat Tyres * 5 Year / 100 000km Motorplan Are you Interested? [3]YES / [4]NO Save up to R1 463.76 per month [5]BMW E90 Auto BMW E90 320i Petrol (Automatic) * From R5 299.00 per month. * Automatic * 2.0L Petrol * Radio/CD * Aircon Climate Control * Central Locking * ABS/ASC + T&CBC * Fog Lamps * Cruise Control * Alloy Wheels * Isofix * Multifunction Steering Wheel * Cruise Control * Run Flat Tyres * 5 Year / 100 000km Motorplan Are you Interested? [6]YES / [7]NO Subject to availability of stock. Extra's not factory fitted will be charged Terms and conditions and cost of credit General terms and conditions and cost of credit Duration of contract 72 months. Once off initiation fee of R1140.00 VAT inclusive, already included in contract. Monthly service fee of R57.00 VAT inclusive. Rate at prime +2% variable. All delivery, lic, registration and number plates included in cost of credit. No residual value or deposit. Cost of credit and repayments may vary due to your credit risk profile. Application subject (at all times) to approval from our credit providers partners. Pre quote and pre contract available at all times. Terms and conditions and cost of credit available or request of contract in all official languages To qualify, the applicant must comply with the following basic conditions: * Earn a minimum salary of R5 500.00 nett (take home); * Not listed on the ITC; * Have a SA Driver's license and ID; * The rest of our terms and conditions are set out in the example [8]Advertising Contract. Advertising initiative cost of credit: * BMW E90 320i Petrol (Manual) = R359 928.00 * BMW E90 320i Petrol (Automatic) = R381 528.00 Please note that your repayment and cost of credit may vary as per terms and conditions of the advertising agreement. Advertised payment reduction is governed by a advertising program. Re-payments exclude monthly services charged and include initiation fee as allowed by the NCR. To view an example of an advertising contract please [9]click here. Example adverts on the back of the vehicles: Branding Branding Cost of credit and repayment if you opt not to enter into the advertising initiative: * BMW E90 320i Petrol (Manual) = R465 662.88 Repayment = R6 467.54 per month * BMW E90 320i Petrol (Automatic) = R491 022.72 Repayment = R6 819.76 per month Repayments and cost of credit includes initiation and monthly service fees as prescribed by the [10]NCR. To stop receiving emails, please [11]UNSUBSCRIBE here References 1. http://www.wowbmw.com/mailer/002/agent.php?page=online&agent=002&campaign=bmw&vehicle=1 2. http://www.wowbmw.com/mailer/002/agent.php?page=apply&agent=002&campaign=bmw&vehicle=25 3. http://www.wowbmw.com/mailer/002/agent.php?page=apply&agent=002&campaign=bmw&vehicle=25 4. http://www.wowbmw.com/mailer/002/agent.php?page=decline&agent=002&campaign=bmw&vehicle=25 5. http://www.wowbmw.com/mailer/002/agent.php?page=apply&agent=002&campaign=bmw&vehicle=26 6. http://www.wowbmw.com/mailer/002/agent.php?page=apply&agent=002&campaign=bmw&vehicle=26 7. http://www.wowbmw.com/mailer/002/agent.php?page=decline&agent=002&campaign=bmw&vehicle=26 8. http://www.wowbmw.com/contract.pdf 9. http://www.wowbmw.com/contract.pdf 10. http://www.ncr.org.za/ 11. http://www.wowbmw.com/site/decline.php From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 11:20:07 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC4BE1065673 for ; Wed, 19 Oct 2011 11:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7F4598FC19 for ; Wed, 19 Oct 2011 11:20:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JBK7Cx089555 for ; Wed, 19 Oct 2011 11:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9JBK7ho089554; Wed, 19 Oct 2011 11:20:07 GMT (envelope-from gnats) Resent-Date: Wed, 19 Oct 2011 11:20:07 GMT Resent-Message-Id: <201110191120.p9JBK7ho089554@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, Frederic Culot Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D382D106566C for ; Wed, 19 Oct 2011 11:11:00 +0000 (UTC) (envelope-from culot@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C11E18FC0A for ; Wed, 19 Oct 2011 11:11:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JBB04E084776 for ; Wed, 19 Oct 2011 11:11:00 GMT (envelope-from culot@freefall.freebsd.org) Received: (from culot@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9JBB08Q084770; Wed, 19 Oct 2011 11:11:00 GMT (envelope-from culot) Message-Id: <201110191111.p9JBB08Q084770@freefall.freebsd.org> Date: Wed, 19 Oct 2011 11:11:00 GMT From: Frederic Culot To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: docs/161804: New documentation: French translation for building-products article X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Frederic Culot List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2011 11:20:07 -0000 >Number: 161804 >Category: docs >Synopsis: New documentation: French translation for building-products article >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Oct 19 11:20:07 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Frederic Culot >Release: FreeBSD 8.2-STABLE i386 >Organization: >Environment: System: FreeBSD freefall.freebsd.org 8.2-STABLE FreeBSD 8.2-STABLE #4 r220774: Mon Apr 18 13:56:14 UTC 2011 simon@freefall.freebsd.org:/usr/obj/usr/src/sys/FREEFALL i386 >Description: Hi, Attached is my attempt at translating the building-products article in French. The sgml source could also be found at: http://people.freebsd.org/~culot/doc/building-products/article.sgml and the resulting html page is available at: http://people.freebsd.org/~culot/doc/building-products/article.html Regards, culot@ >How-To-Repeat: >Fix: --- article.sgml begins here --- %man; %freebsd; %urls.ent; %urls; %abstract; %artheader; %translators; %authors; %mailing-lists; %trademarks; ]>
Construire des Produits avec FreeBSD Joseph Koshy Le Projet FreeBSD
jkoshy@FreeBSD.org
 $FreeBSD$ &tm-attrib.freebsd; &tm-attrib.general; Résumé Le projet FreeBSD est un projet international, collaboratif et basé sur le volontariat, qui développe un système d'exploitation portable et de grande qualité. Le projet FreeBSD distribue le code source de ses produits avec une licence libérale dans l'intention d'encourager l'utilisation de son code. Collaborer avec le project FreeBSD peut aider les organisations à réduire leur délai de mise sur le marché, leurs coûts de développement, et améliorer la qualité de leurs produits. Cet article se penche sur les questions relatives à l'utilisation du code de FreeBSD dans les appareils informatiques et les logiciels. Il met en évidence les caractéristiques de FreeBSD qui en font un excellent support pour le développement de produits. Cet article conclut en suggérant quelques bonnes pratiques pour les organisations qui collaborent avec le projet FreeBSD. Introduction FreeBSD est reconnu aujourd'hui comme un système d'exploitation haute performances pour serveurs. Il est deployé sur des millions de serveurs web et de machines connectées à internet de part le monde. Le code de FreeBSD fait aussi partie intégrante de beaucoup de produits depuis des appareils comme les routeurs réseau, pare-feux, et dispositifs de stockage, jusqu'aux ordinateurs personnels. Des parties de FreeBSD ont également été utilisées dans des produits commerciaux (voir ). Dans cet article nous nous intéressons au projet FreeBSD en tant que ressource pour la conception logicielle—une collection de briques de base et de processus que vous pouvez utiliser pour construire d'autres produits. Bien que les sources de FreeBSD soient distribuées librement au public, les organisations ont besoin de collaborer avec le projet pour pouvoir pleinement apprécier les bénéfices de ce travail. Dans les sections suivantes de cet article nous présentons les moyens efficaces qui existent afin de collaborer avec le projet, ainsi que les pièges à éviter. Avertissement au Lecteur L'auteur pense que les caractéristiques du Projet FreeBSD telles que décrites dans cet article sont en grande partie vraies au moment où cet article a été conçu et rédigé (2005). Cependant, le lecteur doit garder en tête que les pratiques et processus utilisés par les communautées open-source peuvent changer au cours du temps, et que les informations contenues dans cet article devraient donc être considérées comme étant indicatives plutôt que prescriptives. Public Visé Ce document pourrait présenter un intérêt pour les groupes de personnes suivants: Les preneurs de décisions dans les entreprises qui recherchent à amélirer la qualité de leurs produits, à réduire leur délai de mise sur le marché, et réduire leurs coûts de développement sur le long terme. Les consultants en technologie à la recherche de bonnes pratiques pour tirer profit de l' open-source. Les spécialistes de l'industrie interessés par la compréhension de la dynamique des projets open-source. Les développeurs logiciels cherchant à utiliser FreeBSD et désirant contribuer au projet en retour. Buts de l'Article La lecture de cet article devrait vous apporter : Une compréhension des buts du Projet FreeBSD ainsi que de la structure de son organisation. Un aperçu des technologies disponibles dans le projet. Une compréhension de son modèle de développement et de ses processus d'ingénierie. Une compréhension des différences entre les processus de développement conventionnels que l'on retrouve chez les éditeurs de logiciels et ceux utilisés par le projet FreeBSD. Une sensibilisation aux canaux de communication utilisés par le projet et le niveau de transparence auquel vous pouvez vous attendre. Une connaissance des moyens optimaux qui existent pour travailler avec le projet—comment réduire au maximum les coûts de développement, améliorer le délai de mise sur le marché, gérer les failles de sécurité, et préserver la compatibilité future de votre produit avec les évolutions du projet FreeBSD. Structure de l'Article La suite de l'article est structurée de la façon suivante: introduit le projet FreeBSD, présente sa structure organisationnelle, ses technologies clés et ses processus de développement. décrit les moyens de collaborer avec le projet FreeBSD. Les pièges les plus courants rencontrés par les companies travaillant avec les projets basés sur le volontariat comme FreeBSD sont également présentés. conclut. FreeBSD en tant que brique constitutive FreeBSD représente une excellente fondation sur laquelle construire des produits : Le source code de FreeBSD est distribué avec une licence BSD libérale qui facilite grandement son utilisation dans les produits commerciaux Mon2005. Le projet FreeBSD a d'excellentes pratiques de développement qui peuvent être mises à profit. Le projet offre une transparence exceptionnelle eu égard à son fonctionnement, permettant aux companies utilisant son code de planifier efficacement l'avenir. La culture du projet FreeBSD, héritée du Groupe de Recherche sur la Science Informatique de l'Université de Berkeley en Californie McKu1999-1, encourage le travail de grande qualité. Certaines fonctionalités de FreeBSD sont considérés comme des références. GoldGab2005 examine avec plus de détails les raisons commerciales qui justifient l'utilisation de l'open-source. Les bénéfices que les sociétés peuvent tirer de l'utilisation de composants FreeBSD dans leurs produits comprennent un délai réduit de mise sur le marché, ainsi qu'une réduction des coûts et des risques liés au développement. Construire avec FreeBSD Voici quelques utilisations que des companies ont faites de FreeBSD : Comme source de code testé pour des librairies ou utilitaires. En étant en aval du projet, les organisations tirent profit des nouvelles fonctionnalités, corrections de bogues et tests dont le code en amont bénéficie. En tant que système d'exploitation embarqué (par exemple, pour un routeur OEM ou un appareil servant de pare-feu). Dans ce modèle, les organisations utilisent un noyau FreeBSD adapté ainsi qu'un ensemble de logiciels appropriés conjointement avec une couche propriétaire de gestion de leur appareil. Les OEMs bénéficient des nouveaux supports matériels ajoutés par le projet FreeBSD en amont, ainsi que des tests effectués sur le système de base. FreeBSD est diffusé avec un environnement de développement auto-hébergé qui permet de créer facilement de telles configurations. En tant qu'environnement compatible Unix pour les fonctions de gestion des environnements de stockage et les appareils réseau, fonctionant sur un serveur lame séparé. FreeBSD fournit les outils nécessaires pour créer des systèmes d'exploitation dédiés et des images d'applications. Son implémentation basée sur une API BSD Unix est mature et testée. FreeBSD peut aussi fournir un environnement de développement croisé stable pour les autres composants de l'appareil final. En tant que moyen d'obtenir une large base de tests et du support de la part d'une équipe de développeurs internationale pour tout ce qui a trait à la propriété intellectuelle non critique. Dans ce modèle, les organisations apportent un ensemble d'infrastructures utiles au projet FreeBSD (voir par exemple &man.netgraph.3;). L'importante exposition que le code acquiert aide pour l'identification rapide de problèmes de performance et de bogues. L'implication d'excellents développeurs apporte aussi des ajouts utiles à la base existante, ce dont l'organisation contributrice bénéficie également. En tant qu'environnement de développement autorisant le développement croisé pour des systèmes embarqués tels que RTEMS et eCOS. Il existe une pléthore d'environnements de développement très complets dans la collection des &os.numports; applications portées et empaquetées pour FreeBSD. Comme moyen de fournir une API Unix dans un système propriétaire par ailleurs, augmentant ainsi son attractivité pour les développeurs d'applications. Dans ce cas des parties du noyau FreeBSD et des applications sont portées pour tourner conjointement avec d'autres tâches du système d'exploitation propriétaire. La disponibilité de l'implémentation d'une API Unix stable et bien testée peut réduire l'effort nécessaire pour porter des applications populaires sur le système propriétaire. Comme FreeBSD est fournit avec une documentation de grande qualité concernant ses mécanismes internes et assure une gestion efficace des vulnérabilités et des cycles de développement, les coûts pour se maintenir à jour sont bas. Technologies Le projet FreeBSD supporte un grand nombre de technologies dont une sélection est présentée ci-dessous : Un système complet qui peut faire de l'auto-hébergement croisé pour les architectures suivantes : alpha (jusqu'à &os; version 6.X), amd64, ia64, i386, sparc64, powerpc (voir &man.build.7;). Le support pour les technologies, protocoles et standards suivants : ATA, ATAPI, ATM, Bluetooth, CAM, CardBus, DHCP, DNS, EISA, Ethernet, FDDI, Fibre Channel, GPIB, IEEE 1394, IPv4, IPv6, IPSEC, IPX, ISDN, MAC, NIS, NFS, OpenSSH, OPIE, PAM, PCI, PCMCIA, POSIX, PnP, RAID, RPC, SATA, SCSI, SMB, TCP, USB, VESA, VLAN, VLB, WebNFS. Un noyau modulaire permettant le traitement symétrique multiprocesseurs, avec chargement possible de modules noyau et un système de configuration facile à utiliser. Le support pour l'émulation de Linux et des binaires SVR4 à vitesse quasi-native et le support pour les pilotes réseau Windows (NDIS). Des librairies pour de nombreuses tâches liées à la programmation : archivage, support FTP et HTTP, support des processus légers en plus d'un environnement de programmation POSIX. Des dispositifs de sécurité avancés : Mandatory Access Control (&man.mac.9;), jails (&man.jail.2;), ACLs, ainsi que le support d'un dispositif cryptographique au niveau noyau. Des caractéristiques réseau avancées : dispositifs pares-feu, gestion de Qos, communications TCP/IP hautes performances avec support de nombreuses caractéristiques avancées. Le système Netgraph (&man.netgraph.4;) présent dans le noyau FreeBSD permet à des modules noyau de gestion des communications réseau d'être interconnectés de manière flexible. Le support pour des technologies de stockage avancées : fibre, SCSI, RAID logiciel et matériel, ATA et SATA. FreeBSD est capable de gérer plusieurs systèmes de fichiers différents, et son support natif du système de fichiers UFS2 autorise les soft updates, les sauvegardes instantanées, ainsi que les systèmes de fichiers très volumineux (16TB par système) McKu1999. Le système GEOM (&man.geom.4;) présent dans le noyau FreeBSD permet de composer de manière flexible des modules noyau dédiés à la gestion du stockage. L'accès à plus de &os.numports; applications portées, qu'elles soient commerciales ou open-source, gérées grâce à la collection des portages de FreeBSD. Structure Organisationelle La structure organisationelle de FreeBSD n'est pas hiérarchique. Il existe essentiellement deux types de contributeurs à FreeBSD, les utilisateurs de FreeBSD, et les développeurs qui ont les droits en écriture (connus sous le terme committers dans notre jargon) et peuvent modifier les sources. Il existe plusieurs milliers de contributeurs dans le premier groupe, la vaste majorité des contributions à FreeBSD proviennent de personnes faisant partie de ce groupe. Les droits de commit (droits d'accès en écriture) sont accordés aux personnes qui contribuent au projet de manière récurrente. Ces droits viennent avec des responsabilités supplémentaires, et les nouveaux committers se voient attribuer des mentors pour les aider à apprendre les bases.
L'Organisation FreeBSD
La résolution des conflits est assurée par une équipe (Core Team) de neuf membres qui est élue par le groupe des committers. Les committers ne sont pas employés par FreeBSD. Il est exigé de la part des committers qu'ils prennent la responsabilité des changements qu'ils introduisent dans le code. Le Guide du Committer FreeBSD ComGuide documente les règles et responsabilités des committers. Le modèle de projet de FreeBSD est examiné en détails dans Nik2005. Les processus de développement des versions de FreeBSD Les processus de développement des versions de FreeBSD jouent un rôle majeur en assurant que les versions qui sont délivrées sont de grande qualité. À n'importe quel moment que l'on considère, les volontaires de FreeBSD assurent le développement de plusieurs branches de code (): Les nouvelles fonctionnalités et le code expérimental sont incorporés sur la branche de développement, aussi connue sous le nom de branche -CURRENT. Les branches -STABLE représentent les lignes de code qui sont reprises de la HEAD à des intervalles de temps réguliers. Seul le code testé est autorisé sur une branche -STABLE. Les nouvelles fonctionnalités sont autorisées une fois qu'elles ont été testées et stabilisées sur la branche -CURRENT. Les branches -RELEASE sont maintenues par l'équipe sécurité de FreeBSD. Seuls les correctifs de bogues pour les problèmes critiques sont autorisés sur les branches -RELEASE.
Les Branches FreeBSD
Les lignes de code sont maintenues aussi longtemps qu'il existe des utilisateurs et des développeurs qui s'y intéressent. Les architectures machine sont groupées en niveaux. Les architectures de premier niveau (Tier 1) sont entièrement supportées par l'équipe en charge des versions et l'équipe sécurité. Les architectures de second niveau (Tier 2) sont supportées dans la mesure du possible, et les architectures expérimentales représentent le Tier 3. La liste des architectures supportées est incluse dans la documentation FreeBSD. L'équipe en charge des versions publie une feuille de route pour les futures versions de FreeBSD sur la page web du projet. Les dates qui sont mentionnées sur la feuille de route ne sont pas des dates butoires : les versions de FreeBSD sont délivrées lorsque son code et sa documentation sont prêts. Les processus de développement des versions de FreeBSD sont décrits dans RelEngDoc. Collaborer avec FreeBSD Les projets Open-source tels que FreeBSD offrent un code de très grande qualité Cov2005. Des études ont examiné les effets de la disponibilité du code source sur le développement logiciel Com2004. Alors que l'accès à du code source de qualité peut réduire les coûts initiaux de développement, les coûts liés à la gestion des changements deviennent prédominants par la suite. Comme les environnements informatiques changent au fil du temps et que de nouvelles failles de sécurité sont découvertes, votre produit lui aussi a besoin de changements et d'adaptations. Utiliser du code open-source se conçoit plus comme un processus continu dans le temps que comme quelque chose de ponctuel. Les meilleurs projets avec lesquels collaborer sont ceux qui sont actifs, c'est-à-dire ceux qui ont une communauté active, des objectifs clairs et des méthodes de travail transparentes. FreeBSD possède une communauté active de développeurs gravitant autour du projet. Au moment de l'écriture de cet article, il existe plusieurs milliers de contributeurs vivant sur tous les continents peuplés de la planète et plus de 300 personnes possédant les droits d'accès aux dépôts des sources du projet. Les objectifs du projet FreeBSD sont Hub1994: De développer un système d'exploitation de grande qualité pour les architectures informatiques populaires, et Mettre notre travail à la disposition de tous sous couvert d'une licence libérale. FreeBSD bénéficie d'une culture ouverte et transparente. Quasiment toutes les discussions au sein du projet se font par courrier électronique, sur les listes publiques qui sont aussi archivées pour la postérité. Les règles et pratiques du projet sont documentées et maintenues en utilisant un système de gestion de versions. Participer au projet est ouvert à tous. Comprendre la culture FreeBSD Afin de pouvoir travailler de manière efficace avec le projet FreeBSD, vous devez comprendre la culture qui règne au sein du projet. Les projets menés par des volontaires fonctionnent avec des règles différentes de celles utilisées par des organisations commerciales. Une des erreurs récurrentes faite par les entreprises lorsqu'elles s'aventurent dans le monde de l'open-source est de sous-estimer ces différences. Motivation La plupart des contributions à FreeBSD sont faites de manière volontaire et aucune rétribution financière n'entre en jeu. Les facteurs qui motivent les contributeurs sont complexes, et parmi ceux-ci on peut citer l'altruisme ou un intérêt pour résoudre les genres de problèmes que FreeBSD tente de résoudre. Dans cette environnement, l'élégance n'est jamais optionnelle Nor1993. La Vision à Long Terme Les origines de FreeBSD remontent à presque vingt ans dans le passé avec le travail effectué au Groupe de Recherche en Science Informatique (CSRG) de l'Université de Berkeley en Californie. Le dépôt des sources de FreeBSD contient l'historique du projet depuis sa création, et il existe des CDROMs qui contiennent du code plus ancien en provenance du CSRG. Certains des développeurs originaux du CSRG sont toujours associés au projet. Le projet met l'accent sur les perspectives à long terme Nor2001. Un acronyme fréquemment rencontré au sein du projet est DTRT qui signifie Do The Right Thing (Faites les Choses Correctement). Les Processus de Développement Les programmes informatiques sont des outils de communication : à un certain niveau les programmeurs communiquent leurs intentions, en utilisant une notation précise, à un outil (un compilateur) qui traduit ces instructions en code exécutable. À un autre niveau, la même notation est utilisée entre deux programmeurs pour communiquer leurs intentions. Les spécifications formelles et les documents d'architecture sont rarement utilisés dans le projet. Du code clair et bien écrit ainsi que des rapports de changements () eux aussi bien écrits sont utilisés à la place. Le développement de FreeBSD commence par une ébauche de consensus et en faisant tourner du code Carp1996.
Un example de rapport de changement bde 2005-10-29 16:34:50 UTC FreeBSD src repository Modified files: lib/msun/src e_rem_pio2f.c Log: Use double precision to simplify and optimize arg reduction for small and medium size args too: instead of conditionally subtracting a float 17+24, 17+17+24 or 17+17+17+24 bit approximation to pi/2, always subtract a double 33+53 bit one. The float version is now closer to the double version than to old versions of itself — it uses the same 33+53 bit approximation as the simplest cases in the double version, and where the float version had to switch to the slow general case at |x| == 2^7*pi/2, it now switches at |x| == 2^19*pi/2 the same as the double version. This speeds up arg reduction by a factor of 2 for |x| between 3*pi/4 and 2^7*pi/4, and by a factor of 7 for |x| between 2^7*pi/4 and 2^19*pi/4. Revision Changes Path 1.14 +22 -97 src/lib/msun/src/e_rem_pio2f.c
La communication entre programmeurs est facilitée par l'utilisation d'un standard commun concernant le code &man.style.9;. Canaux de Communication Les contributeurs FreeBSD sont répartis dans le monde entier. Le courrier électronique (et dans une moindre mesure, IRC) est le moyen de communication prépondérant au sein du projet. Les Meilleures pratiques pour collaborer avec le projet FreeBSD Nous nous intéressons maintenant à quelques bonnes pratiques utiles pour tirer profit au maximum de l'utilisation de FreeBSD pour le développement de produits. Plan à long terme Mettre en place des processus qui simplifient le suivi du développement de FreeBSD. Par example : Suivre les changements dans le code source de FreeBSD Le projet rend la copie de son dépôt CVS aisée grâce à l'utilisation de CVSup. Avoir l'historique complet des sources est utile lors du déboguage de problèmes complexes et offre des indications utiles sur les intentions des développeurs. Utilisez un système de contrôle de sources efficace qui vous permette de facilement fusionner les changements entre le code FreeBSD et votre propre code. La montre une partie d'un listing annoté du fichier dont le rapport de changement de la fait référence. L'origine de chacune des lignes du code source est clairement affichée. Les listings annotés montrant l'historique de chacun des fichiers faisant partie de FreeBSD sont disponibles sur Internet.
Un listing annoté généré par <command>cvs annotate</command> #LINE #REV #WHO #DATE #TEXT 62 1.1 (jkh 19-Aug-94): int32_t __ieee754_rem_pio2f(float x, float *y) 63 1.1 (jkh 19-Aug-94): { 64 1.14 (bde 29-Oct-05): double z,w,t,r,fn; 65 1.13 (bde 29-Oct-05): double tx[3]; 66 1.14 (bde 29-Oct-05): int32_t e0,i,nx,n,ix,hx; 67 1.1 (jkh 19-Aug-94): 68 1.1 (jkh 19-Aug-94): GET_FLOAT_WORD(hx,x); 69 1.1 (jkh 19-Aug-94): ix = hx&0x7fffffff; 70 1.1 (jkh 19-Aug-94): if(ix<=0x3f490fd8) /* |x| ~<= pi/4 , no need for reduction */ 71 1.1 (jkh 19-Aug-94): {y[0] = x; y[1] = 0; return 0;} 72 1.14 (bde 29-Oct-05): /* 33+53 bit pi is good enough for special and medium size cases */ 73 1.2 (bde 07-Apr-95): if(ix<0x4016cbe4) { /* |x| < 3pi/4, special case with n=+-1 */ 74 1.14 (bde 29-Oct-05): if(hx>0) { 75 1.15 (bde 06-Nov-05): z = x - pio2; 76 1.15 (bde 06-Nov-05): n = 1; 77 1.15 (bde 06-Nov-05): } else { 78 1.15 (bde 06-Nov-05): z = x + pio2; 79 1.15 (bde 06-Nov-05): n = 3; 80 1.9 (bde 08-Oct-05): } 81 1.15 (bde 06-Nov-05): y[0] = z; 82 1.15 (bde 06-Nov-05): y[1] = z - y[0]; 83 1.15 (bde 06-Nov-05): return n; 84 1.15 (bde 06-Nov-05): } 85 1.15 (bde 06-Nov-05): if(ix<0x407b53d1) { /* |x| < 5*pi/4, special case with n=+-2 */
Utilisez un observateur Nommez un observateur pour monitorer les développements de FreeBSD, pour déceler les changements qui pourraient potentiellement impacter vos produits. Remontez les bogues en amont Si vous détectez un bogue dans le code FreeBSD que vous utilisez, remplissez un rapport de bogue. Cette étape permet de faire en sorte que vous n'ayez pas à fixer le même bogue la prochaine fois que vous récupérerez les sources en amont. Tirez profit des efforts portés sur la gestion des versions Utilisez du code d'une branche de développement -STABLE de FreeBSD. Ces branches de développement sont officiellement supportées par les équipes en charge des versions et les équipes sécurité de FreeBSD et sont constituées de code testé. Donnez du code pour réduire les coûts La majeure partie des coûts associés au développement est liée à la maintenance. En donnant du code non critique au projet, vous bénéficiez du fait que votre code aura une diffusion bien plus importante que celle qu'il aurait eu sans ça. Ceci amène à ce que plus de bogues et de failles de sécurité soient éliminés et que les problèmes de performance soient identifiés et résolus. Recevez un soutien efficace Pour les produits avec des dates butoires rapprochées, il est recommendé d'embaucher ou de s'attacher les services d'un développeur ou d'une firme qui a de l'expérience avec FreeBSD. La &a.jobs est un canal de communication utile si vous êtes à la recherche de talents dans le domaine. Le projet FreeBSD maintient une galerie des consultants et des firmes de consulting assurant des travaux liés à FreeBSD. Le Groupe de Certification FreeBSD propose des certifications pour la majorité des systèmes d'exploitation dérivés de BSD. Pour les besoins moins critiques, vous pouvez demander de l'aide sur les listes de diffusion du projet. Un guide utile à suivre si vous souhaitez demander de l'aide est celui de Ray2004. Faites de la publicité sur votre engagement Vous n'êtes pas obligé de faire de la publicité sur votre utilisation de FreeBSD, mais le faire permet à la fois de vous aider vous mais aussi le projet. Faire valoir auprès de la communauté FreeBSD que votre companie utilise FreeBSD améliore vos chances de pouvoir attirer des personnes talentueuses. Une longue liste de personnes abilitées à faire du support sur FreeBSD signifie aussi plus d'échanges d'idées entre les développeurs. Ceci permet de construire des fondations plus seines pour votre futur. Soutenez les développeurs de FreeBSD Parfois la manière la plus directe pour qu'une fonctionnalité dont on a besoin soit incluse dans FreeBSD est d'aider un développeur qui travaille déjà sur un problème ayant un rapport avec cette fonctionnalité. Ces aides peuvent prendre plusieurs formes, depuis le don de matériel jusqu'à des donations financières. Dans certains pays, les donations au projet FreeBSD peuvent bénéficier d'avantages au niveau des taxes. Le projet a un interlocuteur dédié pour assister les donateurs. Le projet maintien également une page web sur laquelle les développeurs recensent leurs besoins. Le projet FreeBSD met un point d'honneur à remercier tous les donnateurs sur son site web. Conclusion Les objectifs du projet FreeBSD sont de créer et proposer gratuitement le code source d'un système d'exploitation de grande qualité. En travaillant avec le projet FreeBSD vous pouvez réduire vos coûts de développement et améliorer vos délais de mise sur le marché dans un certain nombre de scénarios de développement de produits. Nous avons passé en revue les caractéristiques du projet FreeBSD qui en font un excellent choix pour faire partie d'une stratégie produit d'une entreprise. Nous avons ensuite présenté la culture du projet et examiné les différents moyens à disposition pour interagir avec ses développeurs. Cet article conclut avec une liste des bonnes pratiques qui peuvent être mises en place par les organisations pour collaborer avec le projet. Carp1996 The Architectural Principles of the Internet B. Carpenter The Internet Architecture Board 1996 Com2004 How is Open-Source Affecting Software Development? Diomidis Spinellis Clemens Szyperski IEEE Computer Jan/Feb 2004 IEEE Computer Society ComGuide Committer's Guide The FreeBSD Project 2005 Cov2005 Coverity study on kernel security holes in Linux and FreeBSD Coverity Inc. 2005 GoldGab2005 Innovation Happens Elsewhere: Open Source as Business Strategy Ron Goldman Richard Gabriel 2005 ISBN 1558608893 Morgan-Kaufmann Hub1994 Contributing to the FreeBSD Project Jordan Hubbard 1994—2005 The FreeBSD Project McKu1999 Soft Updates: A Technique for Eliminating Most Synchronous Writes in the Fast Filesystem Kirk McKusick Gregory Ganger USENIX Annual Technical Conference 1999 McKu1999-1 Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable Marshall Kirk McKusick <ulink url="http://www.oreilly.com/catalog/opensources/book/toc.html">Open Sources: Voices from the Open Source Revolution</ulink> ISBN 1-56592-582-3 O'Reilly Inc. 1993 Mon2005 Why you should use a BSD style license for your Open Source Project Bruce Montague The FreeBSD Project 2005 Nik2005 A project model for the FreeBSD Project Niklas Saers 2005 The FreeBSD Project Nor1993 Tutorial on Good Lisp Programming Style Peter Norvig Kent Pitman 1993 Nor2001 Teach Yourself Programming in Ten Years Peter Norvig 2001 Ray2004 How to ask questions the smart way Eric Steven Raymond 2004 RelEngDoc FreeBSD Release Engineering Murray Stokely 2001 The FreeBSD Project
--- article.sgml ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 15:20:13 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DDE4106566B for ; Wed, 19 Oct 2011 15:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 31E1E8FC1B for ; Wed, 19 Oct 2011 15:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JFKDfO014385 for ; Wed, 19 Oct 2011 15:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9JFKDiQ014384; Wed, 19 Oct 2011 15:20:13 GMT (envelope-from gnats) Resent-Date: Wed, 19 Oct 2011 15:20:13 GMT Resent-Message-Id: <201110191520.p9JFKDiQ014384@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, Jim Carroll Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68DA6106564A for ; Wed, 19 Oct 2011 15:17:18 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 588148FC12 for ; Wed, 19 Oct 2011 15:17:18 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JFHH9f050301 for ; Wed, 19 Oct 2011 15:17:17 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p9JFHGuf050300; Wed, 19 Oct 2011 15:17:16 GMT (envelope-from nobody) Message-Id: <201110191517.p9JFHGuf050300@red.freebsd.org> Date: Wed, 19 Oct 2011 15:17:16 GMT From: Jim Carroll To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/161808: Missing documentation critical to correct usage of uuid_to_string(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: Wed, 19 Oct 2011 15:20:13 -0000 >Number: 161808 >Category: docs >Synopsis: Missing documentation critical to correct usage of uuid_to_string(3) >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Oct 19 15:20:12 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Jim Carroll >Release: 7.4 >Organization: Carroll-Net, Inc. >Environment: FreeBSD xxx.carroll.com 7.4-STABLE FreeBSD 7.4-STABLE #0: Fri Sep 9 12:00:03 EDT 2011 jim@xxx.carroll.com:/usr/obj/usr/src/sys/FSYNC i386 >Description: There is a key bit of information missing from the man page for uuid_to_string(3). Specifically that after calling this method, it is up to the caller to free the memory allocated. Arguable, it probably should be obvious to most developers, but it was not 100% obvious to us whether or not the call was allocating memory or returning a reference to a static buffer. A careful check of the libc source code showed us the error of our ways. But I thought it might be worthwhile to request a small addendum to the man page "caller needs to free buffer" A quick example, might go a long way as well. May I offer the following: char* str; uint32_t status; uuid_to_string(&u, &str, &status); if (status == uuid_s_ok) { printf("%s\n", str); free(str); } >How-To-Repeat: >Fix: Small addendum to man page: "It is up to the caller to free the string returned by uuid_to_string()." >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 16:30:11 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6BAA1065670 for ; Wed, 19 Oct 2011 16:30:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 42D0B8FC14 for ; Wed, 19 Oct 2011 16:30:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JGUBl6076943 for ; Wed, 19 Oct 2011 16:30:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9JGUBQ5076942; Wed, 19 Oct 2011 16:30:11 GMT (envelope-from gnats) Resent-Date: Wed, 19 Oct 2011 16:30:11 GMT Resent-Message-Id: <201110191630.p9JGUBQ5076942@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, Liton Das Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D72241065708 for ; Wed, 19 Oct 2011 16:21:45 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id C712E8FC19 for ; Wed, 19 Oct 2011 16:21:45 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JGLjCr062143 for ; Wed, 19 Oct 2011 16:21:45 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p9JGLj1Z062142; Wed, 19 Oct 2011 16:21:45 GMT (envelope-from nobody) Message-Id: <201110191621.p9JGLj1Z062142@red.freebsd.org> Date: Wed, 19 Oct 2011 16:21:45 GMT From: Liton Das To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/161810: Printing mistake in FreeBSD 8.2 Handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2011 16:30:11 -0000 >Number: 161810 >Category: docs >Synopsis: Printing mistake in FreeBSD 8.2 Handbook >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Oct 19 16:30:10 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Liton Das >Release: 8.2 >Organization: Advanced Data Networks System Ltd. >Environment: >Description: I have found a printing mistake in the FreeBSD 8.2 handbook,(32.2.5.1 Manual Configuration),where the last two lines seems missing octates in IP address. Please upgrade the document if possible. % netstat -nr Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 10.0.0.1 UGS 0 49378 xl0 127.0.0.1 127.0.0.1 UH 0 6 lo0 10.0.0/24 link#1 UC 0 0 xl0 192.168.1/24 link#2 UC 0 0 xl1 >How-To-Repeat: >Fix: 10.0.0.0/24 link#1 UC 0 0 xl0 192.168.1.0/24 link#2 UC 0 0 xl1 >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 18:06:39 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31362106566C; Wed, 19 Oct 2011 18:06:39 +0000 (UTC) (envelope-from manolis@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 091128FC13; Wed, 19 Oct 2011 18:06:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JI6cgC069887; Wed, 19 Oct 2011 18:06:38 GMT (envelope-from manolis@freefall.freebsd.org) Received: (from manolis@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9JI6cmW069883; Wed, 19 Oct 2011 18:06:38 GMT (envelope-from manolis) Date: Wed, 19 Oct 2011 18:06:38 GMT Message-Id: <201110191806.p9JI6cmW069883@freefall.freebsd.org> To: litondas@gmail.com, manolis@FreeBSD.org, freebsd-doc@FreeBSD.org, manolis@FreeBSD.org From: manolis@FreeBSD.org Cc: Subject: Re: docs/161810: Printing mistake in FreeBSD 8.2 Handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2011 18:06:39 -0000 Synopsis: Printing mistake in FreeBSD 8.2 Handbook State-Changed-From-To: open->closed State-Changed-By: manolis State-Changed-When: Wed Oct 19 18:05:25 UTC 2011 State-Changed-Why: Fixed, thanks! Responsible-Changed-From-To: freebsd-doc->manolis Responsible-Changed-By: manolis Responsible-Changed-When: Wed Oct 19 18:05:25 UTC 2011 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=161810 From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 18:50:11 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9A5F106564A for ; Wed, 19 Oct 2011 18:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D8EBF8FC16 for ; Wed, 19 Oct 2011 18:50:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JIoBMJ007932 for ; Wed, 19 Oct 2011 18:50:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9JIoBob007931; Wed, 19 Oct 2011 18:50:11 GMT (envelope-from gnats) Date: Wed, 19 Oct 2011 18:50:11 GMT Message-Id: <201110191850.p9JIoBob007931@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Niclas Zeising Cc: Subject: Re: docs/161808: Missing documentation critical to correct usage of uuid_to_string(3) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Niclas Zeising List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2011 18:50:12 -0000 The following reply was made to PR docs/161808; it has been noted by GNATS. From: Niclas Zeising To: Jim Carroll Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/161808: Missing documentation critical to correct usage of uuid_to_string(3) Date: Wed, 19 Oct 2011 20:42:59 +0200 This is a multi-part message in MIME format. --------------020509080204060605060408 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Here is a patch that adds the mentioned notice. Regards! -- Niclas Zeising --------------020509080204060605060408 Content-Type: text/plain; name="uuid.3.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="uuid.3.diff" Index: lib/libc/uuid/uuid.3 =================================================================== --- lib/libc/uuid/uuid.3 (revision 226521) +++ lib/libc/uuid/uuid.3 (working copy) @@ -80,6 +80,9 @@ or .Fn uuid_from_string respectively. +Please note that it is up to the caller of +.Fn uuid_to_string +to release the memory allocated to hold the returned string. A 16-bit hash value can be obtained by calling .Fn uuid_hash . .Pp --------------020509080204060605060408-- From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 18:59:01 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7902106566B; Wed, 19 Oct 2011 18:59:01 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7E3078FC12; Wed, 19 Oct 2011 18:59:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JIx1GH016198; Wed, 19 Oct 2011 18:59:01 GMT (envelope-from bcr@freefall.freebsd.org) Received: (from bcr@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9JIx18W016194; Wed, 19 Oct 2011 18:59:01 GMT (envelope-from bcr) Date: Wed, 19 Oct 2011 18:59:01 GMT Message-Id: <201110191859.p9JIx18W016194@freefall.freebsd.org> To: jim@carroll.com, bcr@FreeBSD.org, freebsd-doc@FreeBSD.org From: bcr@FreeBSD.org Cc: Subject: Re: docs/161808: Missing documentation critical to correct usage of uuid_to_string(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: Wed, 19 Oct 2011 18:59:01 -0000 Synopsis: Missing documentation critical to correct usage of uuid_to_string(3) State-Changed-From-To: open->feedback State-Changed-By: bcr State-Changed-When: Wed Oct 19 18:57:37 UTC 2011 State-Changed-Why: Set to feedback-state to see whether the patch submitted by Niclas is the intended change the submitter suggested. http://www.freebsd.org/cgi/query-pr.cgi?pr=161808 From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 20:24:19 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32985106564A; Wed, 19 Oct 2011 20:24:19 +0000 (UTC) (envelope-from jim@carroll.com) Received: from carroll.com (mail3.hck.carroll.com [216.44.20.5]) by mx1.freebsd.org (Postfix) with ESMTP id DCC688FC14; Wed, 19 Oct 2011 20:24:18 +0000 (UTC) Received: from [10.64.0.64] (HELO AS10) by carroll.com (CommuniGate Pro SMTP 4.1.3) with ESMTP id 16844997; Wed, 19 Oct 2011 15:24:18 -0400 From: "Jim Carroll" To: , References: <201110191859.p9JIx18W016194@freefall.freebsd.org> In-Reply-To: <201110191859.p9JIx18W016194@freefall.freebsd.org> Date: Wed, 19 Oct 2011 15:24:17 -0400 Organization: Carroll-Net, Inc. Message-ID: <002f01cc8e94$b207c760$16175620$@carroll.com> X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHycryKWGXoWvpDqsovNrN3vqOOd5U4Q9dw Content-Language: en-us Cc: Subject: RE: docs/161808: Missing documentation critical to correct usage of uuid_to_string(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: Wed, 19 Oct 2011 20:24:19 -0000 This is perfect! Thanks so much > -----Original Message----- > From: bcr@FreeBSD.org [mailto:bcr@FreeBSD.org] > Sent: Wednesday, October 19, 2011 2:59 PM > To: jim@carroll.com; bcr@FreeBSD.org; freebsd-doc@FreeBSD.org > Subject: Re: docs/161808: Missing documentation critical to correct > usage of uuid_to_string(3) > > Synopsis: Missing documentation critical to correct usage of > uuid_to_string(3) > > State-Changed-From-To: open->feedback > State-Changed-By: bcr > State-Changed-When: Wed Oct 19 18:57:37 UTC 2011 > State-Changed-Why: > Set to feedback-state to see whether the patch submitted by Niclas > is the intended change the submitter suggested. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=161808 From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 20:26:49 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 977B81065672; Wed, 19 Oct 2011 20:26:49 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6E7BB8FC14; Wed, 19 Oct 2011 20:26:49 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9JKQnHo099010; Wed, 19 Oct 2011 20:26:49 GMT (envelope-from bcr@freefall.freebsd.org) Received: (from bcr@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9JKQnpi099006; Wed, 19 Oct 2011 20:26:49 GMT (envelope-from bcr) Date: Wed, 19 Oct 2011 20:26:49 GMT Message-Id: <201110192026.p9JKQnpi099006@freefall.freebsd.org> To: jim@carroll.com, bcr@FreeBSD.org, freebsd-doc@FreeBSD.org, bcr@FreeBSD.org From: bcr@FreeBSD.org Cc: Subject: Re: docs/161808: Missing documentation critical to correct usage of uuid_to_string(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: Wed, 19 Oct 2011 20:26:49 -0000 Synopsis: Missing documentation critical to correct usage of uuid_to_string(3) State-Changed-From-To: feedback->analyzed State-Changed-By: bcr State-Changed-When: Wed Oct 19 20:25:59 UTC 2011 State-Changed-Why: Set to analyzed and assign to me. Responsible-Changed-From-To: freebsd-doc->bcr Responsible-Changed-By: bcr Responsible-Changed-When: Wed Oct 19 20:25:59 UTC 2011 Responsible-Changed-Why: Set to analyzed and assign to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=161808 From owner-freebsd-doc@FreeBSD.ORG Wed Oct 19 21:52:27 2011 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD478106566B for ; Wed, 19 Oct 2011 21:52:27 +0000 (UTC) (envelope-from markprz@gsinet.net) Received: from trueband.net (director.trueband.net [216.163.120.8]) by mx1.freebsd.org (Postfix) with SMTP id 589968FC12 for ; Wed, 19 Oct 2011 21:52:26 +0000 (UTC) Received: (qmail 21739 invoked by uid 1006); 19 Oct 2011 21:25:46 -0000 Received: from markprz@gsinet.net by rs0 by uid 1003 with qmail-scanner-1.16 (spamassassin: 3.2.5. Clear:SA:0(4.5/100.0):. Processed in 0.455637 secs); 19 Oct 2011 21:25:46 -0000 X-Spam-Status: No, hits=4.5 required=100.0 X-Spam-Level: **** Received: from unknown (HELO trueband.net) (172.16.0.3) by director.trueband.net with SMTP; 19 Oct 2011 21:25:45 -0000 Received: (qmail 9754 invoked from network); 19 Oct 2011 21:18:09 -0000 Received: from unknown (HELO gsinet.net) (markprz@190.240.139.24) by -v with SMTP; 19 Oct 2011 21:18:09 -0000 From: "Muliaman Purba" To: doc@freebsd.org Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Date: Thu, 20 Oct 2011 00:17:57 +0300 X-Qmail-Scanner-1.16: added fake MIME-Version header MIME-Version: 1.0 X-Qmail-Scanner-Message-ID: <1319059545210621734@rs0> Message-Id: <20111019215227.BD478106566B@hub.freebsd.org> Cc: Subject: =?utf-8?b?xIxhdSE=?= Lexa X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Muliaman Purba List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2011 21:52:27 -0000 ÄŒau, Äau! Lexa Es ļoti ceru, ka esi apdomÄjis manu priekÅ¡likumu. MÄ“s te pasÄ“dÄ“jÄm un izlÄ“mÄm, ka nav jÄ“gas doties uz Īriju. Tri Hasta ir atradis internetÄ variantu kÄ Ätri un droÅ¡i var labi nopelnÄ«t. http://vef.bplaced.net/lokos.php Es pamÄ“Ä£inÄju un es Å¡obrÄ«d domÄju, ko labÄk pirkt, nevis, kur labÄk doties strÄdÄt. Muliaman Purba From owner-freebsd-doc@FreeBSD.ORG Thu Oct 20 20:59:11 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99D0C106566B for ; Thu, 20 Oct 2011 20:59:11 +0000 (UTC) (envelope-from www@s113.loopia.se) Received: from s87.loopia.se (s87.loopia.se [194.9.95.112]) by mx1.freebsd.org (Postfix) with ESMTP id 281058FC0A for ; Thu, 20 Oct 2011 20:59:11 +0000 (UTC) Received: from s101.loopia.se (s101.loopia.se [194.9.95.47]) by s87.loopia.se (Postfix) with SMTP id 3E371465367 for ; Thu, 20 Oct 2011 22:40:33 +0200 (CEST) Received: (qmail 37651 invoked from network); 20 Oct 2011 20:40:22 -0000 Received: from s113.loopia.se (HELO s113.loopia.se) (194.9.94.207) by s101.loopia.se (qpsmtpd/0.31.1) with ESMTP; Thu, 20 Oct 2011 22:40:22 +0200 Received: from s113.loopia.se (localhost [127.0.0.1]) by s113.loopia.se (8.14.4/8.14.4) with ESMTP id p9KKeOg5007958 for ; Thu, 20 Oct 2011 22:40:24 +0200 (CEST) (envelope-from www@s113.loopia.se) Received: (from www@localhost) by s113.loopia.se (8.14.4/8.14.4/Submit) id p9KKeO75007957; Thu, 20 Oct 2011 22:40:24 +0200 (CEST) (envelope-from www) Date: Thu, 20 Oct 2011 22:40:24 +0200 (CEST) Message-Id: <201110202040.p9KKeO75007957@s113.loopia.se> To: freebsd-doc@freebsd.org From: Security Center Paypal MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Security Center Paypal 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, 20 Oct 2011 20:59:11 -0000 [1]PayPal [pixel.gif] Information Regarding Your account: Dear PayPal Member: Attention! Your PayPal account has been limited! As part of our security measures, we regularly screen activity in the PayPal system.We recently contacted you after noticing an issue on your account.We requested information from you for the following reason: Our system detected unusual charges to a credit card linked to your PayPal account. Reference Number: PP-259-187-991 This is the Last reminder to log in to PayPal as soon as possible. Once you log in, you will be provided with steps to restore your account access. Once you log in, you will be provided with steps to restore your account access. We appreciate your understanding as we work to ensure account safety. [2]Click here to activate your account We thank you for your prompt attention to this matter. Please understand that this is a security measure intended to help protect you and your account. We apologise for any inconvenience.. Sincerely, PayPal Account Review Department _________________________________________________________________ Copyright © 1999-2011 PayPal. All rights reserved. PayPal Ltd. PayPal FSA Register Number: 226056. [pixel.gif] PayPal Email ID PP059 Protect Your Account Info Make sure you never provide your password to fraudulent websites. To safely and securely access the PayPal website or your account, open a new web browser (e.g. Internet Explorer or Netscape) and type in the PayPal login page (http://paypal.com/) to be sure you are on the real PayPal site. For more information on protecting yourself from fraud, please review our Security Tips at https://www.paypal.com/us/securitytips Protect Your Password You should never give your PayPal password to anyone. References 1. https://www.paypal.com/us 2. http://paypalupdate.com.security.online.unlimited.conceptec.net/paypal.com/ From owner-freebsd-doc@FreeBSD.ORG Fri Oct 21 14:20:12 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E3F4106566C for ; Fri, 21 Oct 2011 14:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 599BD8FC15 for ; Fri, 21 Oct 2011 14:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9LEKC8Q014214 for ; Fri, 21 Oct 2011 14:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9LEKCYl014211; Fri, 21 Oct 2011 14:20:12 GMT (envelope-from gnats) Resent-Date: Fri, 21 Oct 2011 14:20:12 GMT Resent-Message-Id: <201110211420.p9LEKCYl014211@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, David Wolfskill Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB5D6106566B for ; Fri, 21 Oct 2011 14:13:54 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 8FC788FC0C for ; Fri, 21 Oct 2011 14:13:54 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.5/8.14.5) with ESMTP id p9LEDs4r086270 for ; Fri, 21 Oct 2011 07:13:54 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.5/8.14.5/Submit) id p9LEDs6O086269; Fri, 21 Oct 2011 07:13:54 -0700 (PDT) (envelope-from david) Message-Id: <201110211413.p9LEDs6O086269@albert.catwhisker.org> Date: Fri, 21 Oct 2011 07:13:54 -0700 (PDT) From: David Wolfskill To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: docs/161880: Handbook update: new mailing list X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Wolfskill List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2011 14:20:12 -0000 >Number: 161880 >Category: docs >Synopsis: Handbook update: new mailing list >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Fri Oct 21 14:20:11 UTC 2011 >Closed-Date: >Last-Modified: >Originator: David Wolfskill >Release: FreeBSD 8.2-STABLE i386 >Organization: Wolfskill & Dowling Residence >Environment: System: FreeBSD albert.catwhisker.org 8.2-STABLE FreeBSD 8.2-STABLE #376 r225739: Fri Sep 23 04:30:11 PDT 2011 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/sys/ALBERT i386 >Description: Kris Moore requested a new mailing list, freebsd-desktop. Attached patch is intended to update the Handbook to mention and describe it. >How-To-Repeat: n/a >Fix: Index: en_US.ISO8859-1/books/handbook/eresources/chapter.sgml =================================================================== RCS file: /cvs/freebsd/doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v retrieving revision 1.213 diff -u -r1.213 chapter.sgml --- en_US.ISO8859-1/books/handbook/eresources/chapter.sgml 4 Oct 2011 14:40:37 -0000 1.213 +++ en_US.ISO8859-1/books/handbook/eresources/chapter.sgml 21 Oct 2011 14:08:12 -0000 @@ -248,6 +248,11 @@ + &a.desktop.name; + Using and improving FreeBSD on the desktop + + + &a.doc.name; Creating FreeBSD related documents Index: en_US.ISO8859-1/share/sgml/mailing-lists.ent =================================================================== RCS file: /cvs/freebsd/doc/en_US.ISO8859-1/share/sgml/mailing-lists.ent,v retrieving revision 1.85 diff -u -r1.85 mailing-lists.ent --- en_US.ISO8859-1/share/sgml/mailing-lists.ent 4 Oct 2011 14:40:37 -0000 1.85 +++ en_US.ISO8859-1/share/sgml/mailing-lists.ent 21 Oct 2011 14:09:25 -0000 @@ -158,6 +158,10 @@ FreeBSD based Databases mailing list"> freebsd-database"> + +Using and improving FreeBSD on the desktop"> +freebsd-desktop"> + >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Fri Oct 21 15:43:36 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E94BF106564A; Fri, 21 Oct 2011 15:43:36 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C1A3C8FC14; Fri, 21 Oct 2011 15:43:36 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9LFhaZG096431; Fri, 21 Oct 2011 15:43:36 GMT (envelope-from gjb@freefall.freebsd.org) Received: (from gjb@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9LFhauT096427; Fri, 21 Oct 2011 15:43:36 GMT (envelope-from gjb) Date: Fri, 21 Oct 2011 15:43:36 GMT Message-Id: <201110211543.p9LFhauT096427@freefall.freebsd.org> To: gjb@FreeBSD.org, freebsd-doc@FreeBSD.org, gjb@FreeBSD.org From: gjb@FreeBSD.org Cc: Subject: Re: docs/161880: Handbook update: new mailing list 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, 21 Oct 2011 15:43:37 -0000 Synopsis: Handbook update: new mailing list Responsible-Changed-From-To: freebsd-doc->gjb Responsible-Changed-By: gjb Responsible-Changed-When: Fri Oct 21 15:43:27 UTC 2011 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=161880 From owner-freebsd-doc@FreeBSD.ORG Sat Oct 22 04:00:12 2011 Return-Path: Delivered-To: doc@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id EDEB31065676; Sat, 22 Oct 2011 04:00:10 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 5AFD3161743; Sat, 22 Oct 2011 04:00:10 +0000 (UTC) Message-ID: <4EA23FCA.10309@FreeBSD.org> Date: Fri, 21 Oct 2011 21:00:10 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111001 Thunderbird/7.0.1 MIME-Version: 1.0 To: John Baldwin References: <20111007141312.GJ26743@acme.spoerlein.net> <20111008120446.GU26743@acme.spoerlein.net> <4084CDBA-C96D-4D3E-9F99-9F64C68B187D@nitro.dk> <201110101301.37276.jhb@freebsd.org> In-Reply-To: <201110101301.37276.jhb@freebsd.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: doc@freebsd.org, doceng@freebsd.org, freebsd-doc@freebsd.org, =?ISO-8859-1?Q?Sp=F6rlein?= , "Simon L. B. Nielsen" , Ulrich@FreeBSD.ORG Subject: Re: Conversion to SVN 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, 22 Oct 2011 04:00:12 -0000 On 10/10/2011 10:01, John Baldwin wrote: > On Saturday, October 08, 2011 12:16:59 pm Simon L. B. Nielsen wrote: >>>> I'm not really sure where you would fit doc into the current repo... >>>> head/ etc. is on the top level. >>> >>> /doc and /www would be the obvious choices. Ed even jokingly (??) said >> >> Well, that seems like a bit of a mess as you mainly have branches at that level... >> >>> we should just rename /head to /src ... not sure I concur. >> >> Considering we have stable etc. on the same level that seems like a bad thing to do... > > I agree with both of these. The layout in svn currently is src-centric and > only setup to handle src. Right now under base/ we have: cvs2svn head projects release releng stable svnadmin user vendor vendor-crypto vendory-sys ROADMAP.TXT Those categories are primarily source-related, but not exclusively. > You would need to move the entire repo down into a > new "src" directory for it to really work, but we aren't going to do that now. > I think a separate SVN for doc+www is fine (and not near as much overhead to > manage as Ulrich fears). My primary motivating factor is not the administrative overhead, it's the fact that elements from the doc repo are used as part of 'make release.' > Also, I think the discontinuous history idea is a compelling reason to not put > the doc/www history into source svn. Right now svn changes move forward > continuously with time (so change N + 1 is "newer" than change N), but > importing doc+www history as changes that are subsequent to the current top of > tree would break that. OTOH, renumbering the current tree to put the doc+www > history in the "right" place is simply not workable now. I don't understand any of what you wrote above, but I'd like to. What I'm thinking is that the cvs->svn converter would simply start with the next available revision number and that would be the first revision for the oldest doc commit. When the import was done, the revision numbers would continue to increase monotonically regardless of whether it was a doc or src commit. Are you saying that this is not how it would work? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-doc@FreeBSD.ORG Sat Oct 22 04:00:12 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id EDEB31065676; Sat, 22 Oct 2011 04:00:10 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 5AFD3161743; Sat, 22 Oct 2011 04:00:10 +0000 (UTC) Message-ID: <4EA23FCA.10309@FreeBSD.org> Date: Fri, 21 Oct 2011 21:00:10 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111001 Thunderbird/7.0.1 MIME-Version: 1.0 To: John Baldwin References: <20111007141312.GJ26743@acme.spoerlein.net> <20111008120446.GU26743@acme.spoerlein.net> <4084CDBA-C96D-4D3E-9F99-9F64C68B187D@nitro.dk> <201110101301.37276.jhb@freebsd.org> In-Reply-To: <201110101301.37276.jhb@freebsd.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: doc@freebsd.org, doceng@freebsd.org, freebsd-doc@freebsd.org, =?ISO-8859-1?Q?Sp=F6rlein?= , "Simon L. B. Nielsen" , Ulrich@FreeBSD.ORG Subject: Re: Conversion to SVN 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, 22 Oct 2011 04:00:12 -0000 On 10/10/2011 10:01, John Baldwin wrote: > On Saturday, October 08, 2011 12:16:59 pm Simon L. B. Nielsen wrote: >>>> I'm not really sure where you would fit doc into the current repo... >>>> head/ etc. is on the top level. >>> >>> /doc and /www would be the obvious choices. Ed even jokingly (??) said >> >> Well, that seems like a bit of a mess as you mainly have branches at that level... >> >>> we should just rename /head to /src ... not sure I concur. >> >> Considering we have stable etc. on the same level that seems like a bad thing to do... > > I agree with both of these. The layout in svn currently is src-centric and > only setup to handle src. Right now under base/ we have: cvs2svn head projects release releng stable svnadmin user vendor vendor-crypto vendory-sys ROADMAP.TXT Those categories are primarily source-related, but not exclusively. > You would need to move the entire repo down into a > new "src" directory for it to really work, but we aren't going to do that now. > I think a separate SVN for doc+www is fine (and not near as much overhead to > manage as Ulrich fears). My primary motivating factor is not the administrative overhead, it's the fact that elements from the doc repo are used as part of 'make release.' > Also, I think the discontinuous history idea is a compelling reason to not put > the doc/www history into source svn. Right now svn changes move forward > continuously with time (so change N + 1 is "newer" than change N), but > importing doc+www history as changes that are subsequent to the current top of > tree would break that. OTOH, renumbering the current tree to put the doc+www > history in the "right" place is simply not workable now. I don't understand any of what you wrote above, but I'd like to. What I'm thinking is that the cvs->svn converter would simply start with the next available revision number and that would be the first revision for the oldest doc commit. When the import was done, the revision numbers would continue to increase monotonically regardless of whether it was a doc or src commit. Are you saying that this is not how it would work? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-doc@FreeBSD.ORG Sat Oct 22 14:20:11 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23993106566C for ; Sat, 22 Oct 2011 14:20:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 130F48FC0A for ; Sat, 22 Oct 2011 14:20:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9MEKART096053 for ; Sat, 22 Oct 2011 14:20:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9MEKAZe096052; Sat, 22 Oct 2011 14:20:10 GMT (envelope-from gnats) Date: Sat, 22 Oct 2011 14:20:10 GMT Message-Id: <201110221420.p9MEKAZe096052@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Benedict Reuschling Cc: Subject: Re: docs/159854: [patch] grammar updates for carp.4 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Benedict Reuschling List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Oct 2011 14:20:11 -0000 The following reply was made to PR docs/159854; it has been noted by GNATS. From: Benedict Reuschling To: bug-followup@FreeBSD.org, kaduk@mit.edu Cc: Subject: Re: docs/159854: [patch] grammar updates for carp.4 Date: Sat, 22 Oct 2011 16:02:21 +0200 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The "problem" with contributed man pages (from other projects, in this case OpenBSD's CARP) is that we don't fix them in our tree, as this would result in merge conflict when importing the next version their tree into ours. Hence, it is better to contact the vendor and see whether the corrections can be done in their tree first and when that is done, contact our maintainer for that piece of software to import these fixes. However, as we are currently a few versions behind the vendor version, the man page has changed significantly as far as your patch is concerned. You might want to check their current version and see whether your fixes still apply: http://www.openbsd.org/cgi-bin/cvsweb/src/share/man/man4/carp.4 Cheers Benedict Reuschling FreeBSD Documentation Committer The FreeBSD Documentation Project FreeBSD German Documentation Project - https://doc.bsdgroup.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6izO0ACgkQTSZQLkqBk0jDhACdEHauNwccMC3ZrWd8WQ0RTLyH N0kAnAwRwoVLhuyNzmw4t4gyzxpOLvgm =tm30 -----END PGP SIGNATURE-----