From owner-freebsd-doc@FreeBSD.ORG Sun Apr 10 12:10:25 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7DE916A4CE for ; Sun, 10 Apr 2005 12:10:25 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 759E343D1F for ; Sun, 10 Apr 2005 12:10:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3ACAPr6067855 for ; Sun, 10 Apr 2005 12:10:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3ACAP0C067853; Sun, 10 Apr 2005 12:10:25 GMT (envelope-from gnats) Resent-Date: Sun, 10 Apr 2005 12:10:25 GMT Resent-Message-Id: <200504101210.j3ACAP0C067853@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, "Wojciech A. Koszek" Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01F4B16A4CF for ; Sun, 10 Apr 2005 12:03:42 +0000 (GMT) Received: from freebsd.czest.pl (silver.iplus.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EF6343D41 for ; Sun, 10 Apr 2005 12:03:38 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id j3ACCCKf021569 for ; Sun, 10 Apr 2005 12:12:12 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.12.10/8.12.9/Submit) id j3ACCCB0021568; Sun, 10 Apr 2005 12:12:12 GMT (envelope-from dunstan) Message-Id: <200504101212.j3ACCCB0021568@freebsd.czest.pl> Date: Sun, 10 Apr 2005 12:12:12 GMT From: "Wojciech A. Koszek" To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: docs/79747: Duplicated word in humanize_number.3 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Wojciech A. Koszek" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2005 12:10:25 -0000 >Number: 79747 >Category: docs >Synopsis: Duplicated word in humanize_number.3 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 10 12:10:24 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Wojciech A. Koszek >Release: FreeBSD 5.4-PRERELEASE i386 >Organization: >Environment: System: FreeBSD dunstan.freebsd.czest.pl 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #6: Mon Apr 4 21:06:12 CEST 2005 dunstan@dunstan.freebsd.czest.pl:/usr/obj/usr/src/sys/HOME8 i386 >Description: Word 'bytes' is duplicated. >How-To-Repeat: $ man humanize_number | col -b | cat -n | grep "bytes bytes" >Fix: --- diff.0.humanize_number.3 begins here --- Index: src/lib/libutil/humanize_number.3 =================================================================== RCS file: /home/ncvs/src/lib/libutil/humanize_number.3,v retrieving revision 1.7 diff -r1.7 humanize_number.3 67c67 < bytes bytes long. --- > bytes long. --- diff.0.humanize_number.3 ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sun Apr 10 12:13:05 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 272A216A4CE; Sun, 10 Apr 2005 12:13:05 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0031C43D1F; Sun, 10 Apr 2005 12:13:04 +0000 (GMT) (envelope-from delphij@FreeBSD.org) Received: from freefall.freebsd.org (delphij@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3ACD4Hg068080; Sun, 10 Apr 2005 12:13:04 GMT (envelope-from delphij@freefall.freebsd.org) Received: (from delphij@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3ACD4Tw068076; Sun, 10 Apr 2005 12:13:04 GMT (envelope-from delphij) Date: Sun, 10 Apr 2005 12:13:04 GMT From: Xin LI Message-Id: <200504101213.j3ACD4Tw068076@freefall.freebsd.org> To: delphij@FreeBSD.org, freebsd-doc@FreeBSD.org, delphij@FreeBSD.org Subject: Re: docs/79747: Duplicated word in humanize_number.3 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2005 12:13:05 -0000 Synopsis: Duplicated word in humanize_number.3 Responsible-Changed-From-To: freebsd-doc->delphij Responsible-Changed-By: delphij Responsible-Changed-When: Sun Apr 10 12:12:51 GMT 2005 Responsible-Changed-Why: Grab http://www.freebsd.org/cgi/query-pr.cgi?pr=79747 From owner-freebsd-doc@FreeBSD.ORG Sun Apr 10 23:59:55 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93AAF16A4CE; Sun, 10 Apr 2005 23:59:55 +0000 (GMT) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0C5543D31; Sun, 10 Apr 2005 23:59:54 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from twinmp (12-218-21-193.client.mchsi.com[12.218.21.193]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20050410235954m9100q0303e>; Sun, 10 Apr 2005 23:59:54 +0000 From: Josh Paetzel To: freebsd-doc@freebsd.org, Marc Fonvieille Date: Sun, 10 Apr 2005 18:59:52 -0500 User-Agent: KMail/1.7 References: <200504080930.j389UC8a078475@freefall.freebsd.org> In-Reply-To: <200504080930.j389UC8a078475@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504101859.53311.josh@tcbug.org> Subject: Re: docs/79667: Some sections of the handbook refer to /etc/ppp/ppp.conf and others just ppp.conf This patch makes it consistant throughout X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2005 23:59:55 -0000 On Friday 08 April 2005 04:30, Marc Fonvieille wrote: > The following reply was made to PR docs/79667; it has been noted by > GNATS. > > From: Marc Fonvieille > To: Josh Paetzel > Cc: FreeBSD gnats submit > Subject: Re: docs/79667: Some sections of the handbook refer to > /etc/ppp/ppp.conf and others just ppp.conf This patch makes it > consistant throughout Date: Fri, 8 Apr 2005 11:22:55 +0200 > > On Thu, Apr 07, 2005 at 09:48:55PM -0500, Josh Paetzel wrote: > > >Number: 79667 > > >Category: docs > > >Synopsis: Some sections of the handbook refer to > > > /etc/ppp/ppp.conf and others just ppp.conf This patch makes > > > it consistant throughout 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: Fri Apr 08 02:50:03 GMT 2005 > > >Closed-Date: > > >Last-Modified: > > >Originator: Josh Paetzel > > >Release: FreeBSD 5.3-RELEASE-p8 i386 > > >Organization: > > >Environment: > > > > System: FreeBSD 5.3-RELEASE-p8 #2: Wed Apr 6 18:08:11 CDT 2005 > > jpaetzel@twinmp.tcbug.org:/usr/obj/usr/src/sys/TWINMP > > > > >Description: > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ppp-an > >d-slip.html uses ppp.conf and /etc/ppp/ppp.conf somewhat > > haphazardly. This patch makes the usage "uniform" > > The current usage in the Handbook is not inconsistent. > In the mentioned chapter the location of configuration files is > clearly stated: > "Both ppp and pppd (the kernel level implementation of PPP) use > the configuration files located in the /etc/ppp directory." > > Then the 1st time ppp.conf is mentioned we have: "You will need to > edit the /etc/ppp/ppp.conf configuration file." > The following instances use both ppp.conf and /etc/ppp/ppp.conf, > in the same way we do for rc.conf and /etc/rc.conf, sendmail.cf, > GENERIC, and thousand of files. > Since the reader must read the beginning of the section with > important and "mandatory" explanations, he will know where is > located ppp.conf If the reader starts to read a section from the > middle of it, we cannot help... > I will evev add that having full path often leads to a "bloated" > text. > > Marc Agreed....maybe close this one out if you haven't already. -- Thanks, Josh Paetzel From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 03:56:49 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 633B816A4CE for ; Mon, 11 Apr 2005 03:56:49 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB6B543D3F for ; Mon, 11 Apr 2005 03:56:48 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 139541492B; Sun, 10 Apr 2005 22:56:48 -0500 (CDT) Date: Sun, 10 Apr 2005 22:56:48 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: freebsd-doc@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: CFD: additions to the PR submission article X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 03:56:49 -0000 As part of my work on bugmeister I keep encountering the same problems with PR submissions over and over. This proposed patch makes the following changes: - further clarifies the distinction between software written by FreeBSD contributors and software written by others - defines when code is too old to file a PR against - adds text about mangled formatting, especially by mailers Unless there are any objections I intend to commit these changes once the freeze is lifted. Thanks, mcl Index: article.sgml =================================================================== RCS file: /home/FreeBSD/dcvs/doc/en_US.ISO8859-1/articles/problem-reports/article.sgml,v retrieving revision 1.36 diff -u -r1.36 article.sgml --- article.sgml 15 Jan 2005 02:16:42 -0000 1.36 +++ article.sgml 11 Apr 2005 03:53:25 -0000 @@ -104,20 +104,11 @@ Notification of updates to externally maintained - software (mainly ports, but also externally maintained base - system components such as BIND or various GNU - utilities). + software (see below). - Another thing is that if the system on which you experienced - the bug is not fairly up-to-date, you should seriously consider - upgrading and trying to reproduce the problem on an up-to-date - system before submitting a problem report. There are few things - that will annoy a developer more than receiving a problem report - about a bug she has already fixed. - - Finally, a bug that can not be reproduced can rarely be + Note that a bug that can not be reproduced can rarely be fixed. If the bug only occurred once and you can not reproduce it, and it does not seem to happen to anybody else, chances are none of the developers will be able to reproduce it or figure @@ -127,6 +118,71 @@ these kinds of bugs are actually caused by failing hard drives or overheating processors — you should always try to rule out these causes, whenever possible, before submitting a PR. + + Next, to decide to whom you should file your problem + report, you need to understand that the software that makes + up &os; is composed of several different elements: + + + + Code in the base system that is written and maintained + by &os; contributors, such as the kernel, the C library, + and the device drivers (categorized as kern); + the binary utilities (bin); the manual + pages and documentation (docs); and + the web pages (www). All bugs in + these areas should be reported to the &os; developers. + + + + Code in the base system that is written and maintained + by others, and imported into &os; and adapted. Examples + include bind, &man.gcc.1;, and + &man.sendmail.8;. Most bugs in these areas should be reported + to the &os; developers; but in some cases they may need to be + reported to the original authors instead if the problems are + not &os;-specific. Usually these bugs will fall under either + the bin or gnu + categories. + + + + Individual applications that are not in the base system + but are instead part of the &os; Ports Collection (category + ports). Most of these applications are + not written by &os; developers; what &os; provides is merely + a framework for installing the application. Therefore, you + should only report a problem to the &os; developers when you + believe the problem is &os;-specific; otherwise, you should + report it to the authors of the software. + + + + + Then you should ascertain whether or not the problem is + timely. There are few things + that will annoy a developer more than receiving a problem report + about a bug she has already fixed. + + If the problem is in the base system, you should first read + the FAQ section on + + &os; versions, if you are not already familiar with + the topic. It is not possible for &os; to fix problems in + anything other than certain recent branches of the base system, + so filing a bug report about an older version will probably + only result in a developer advising you to upgrade to a + supported version to see if the problem still recurs. The + Security Officer team maintains the + list of supported + versions. + + If the problem is in a port, note that you must first + upgrade to the latest version of the Ports Collection and see + if the problem still applies. Due to the rapid pace of changes + in these applications, it is infeasible for &os; to support + anything other than the absolute latest versions, and problems + with older version of applications simply cannot be fixed.
@@ -209,25 +265,6 @@ are also available via CVSweb. - - Next, you need to make sure your problem report goes to the - right people. - - The first catch here is that if the problem is a bug in - third-party software (a port or a package you have installed), you - should report the bug to the original author, not to the &os; - Project. There are two exceptions to this rule: the first is if - the bug does not occur on other platforms, in which case the - problem may lie in how the software was ported to &os;; the - second is if the original author has already fixed the bug and - released a patch or a new version of his software, and the - &os; port has not been updated yet. - - The second catch is that &os;'s bug tracking system sorts - problem reports according to the category the originator - selected. Therefore, if you select the wrong category when you - submit your problem report, there is a good chance that it will - go unnoticed for a while, until someone re-categorizes it.
@@ -434,7 +471,7 @@
Before you begin - Before running the &man.send-pr.1; program, make sure your + If you are using the &man.send-pr.1; program, make sure your VISUAL (or EDITOR if VISUAL is not set) environment variable is set to something sensible. @@ -447,6 +484,24 @@ on the setup of mail on &os;, see the Electronic Mail chapter of the &os; Handbook at . + + Make sure that your mailer will not mangle the message on + its way to GNATS. In particular, if your mailer automatically + breaks lines, changes tabs to spaces, or escapes newline + characters, any patch that you submit will be rendered + unusable. For the text sections, however, we request that + you insert manual linebreaks somewhere around 70 characters, + so that the web display of the PR will be readable. + + Similar considerations apply if you are using the web-based + PR submittal form instead of &man.send-pr.1;. Note that + cut-and-paste operations can have their own side-effects on + text formatting. In certain cases it may be necessary to use + &man.uuencode.1; to ensure that patches arrive unmodified. + + Finally, if your submission will be lengthy, you may wish + to prepare your work offline so that nothing will be lost in + case there is a problem in transmission.
@@ -492,7 +547,10 @@ the larger the patch, the harder it will be for interested parties to unmangle it. Also, posting a patch on the web allows you to modify it without having to resubmit the entire - patch in a followup to the original PR. + patch in a followup to the original PR. Finally, large + patches simply increase the size of the database, since + closed PRs are not actually deleted but instead kept and + simply marked as closed. You should also take note that unless you explicitly specify otherwise in your PR or in the patch itself, any From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 04:57:14 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DDF816A4CE for ; Mon, 11 Apr 2005 04:57:14 +0000 (GMT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id C813C43D45 for ; Mon, 11 Apr 2005 04:57:13 +0000 (GMT) (envelope-from nathan@bsdmail.com) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])E075318001C5 for ; Mon, 11 Apr 2005 04:57:06 +0000 (GMT) X-OB-Received: from unknown (205.158.62.131) by wfilter.us4.outblaze.com; 11 Apr 2005 04:57:05 -0000 Received: by ws5-1.us4.outblaze.com (Postfix, from userid 1001) id F3D991FB15; Mon, 11 Apr 2005 04:57:08 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [127.0.0.1] by ws5-1.us4.outblaze.com with http for nathan@bsdmail.com; Mon, 11 Apr 2005 13:57:08 +0900 From: "Nathan Singleton" To: doc@FreeBSD.org Date: Mon, 11 Apr 2005 13:57:08 +0900 X-Originating-Ip: 127.0.0.1 X-Originating-Server: ws5-1.us4.outblaze.com Message-Id: <20050411045708.F3D991FB15@ws5-1.us4.outblaze.com> Subject: (Minor) Error located in FreeBSD handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 04:57:14 -0000 Hello, I found what I beleave to be a minor technical error in the FreeBSD = handbook. The page where the error can be found at is, "http://www.freebsd.org/doc/en= _US.ISO8859-1/books/handbook/network-apache.html". The page's title is, "Apache HTTP Server". Subchapter is, "23.8.4 Virtual H= osting" The error is here: ServerName www.domain.tld DocumentRoot /www/domain.tld it should (probably) be: ServerName www.domain.tld DocumentRoot /www/domain.tld This is because the tag was already open and doesn't need to = be re-opened. Instead it should be closed before the next ent= ry, or it will cause an "end tag for "VirtualHost" omitted, but OMITTAG NO = was specified" error (I beleave). I hope this helps you. kind regards, Nathan --=20 _______________________________________________ Get your free email from http://mymail.bsdmail.com Powered by Outblaze From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 05:45:16 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2E4516A4CE for ; Mon, 11 Apr 2005 05:45:16 +0000 (GMT) Received: from abigail.blackend.org (blackend.org [212.11.35.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id B791B43D46 for ; Mon, 11 Apr 2005 05:45:15 +0000 (GMT) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (localhost [127.0.0.1]) j3B5jBXN022112; Mon, 11 Apr 2005 07:45:11 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: (from marc@localhost) by abigail.blackend.org (8.12.11/8.12.11/Submit) id j3B5jApZ022111; Mon, 11 Apr 2005 07:45:10 +0200 (CEST) (envelope-from marc) Date: Mon, 11 Apr 2005 07:45:10 +0200 From: Marc Fonvieille To: Nathan Singleton Message-ID: <20050411054510.GA22025@abigail.blackend.org> References: <20050411045708.F3D991FB15@ws5-1.us4.outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050411045708.F3D991FB15@ws5-1.us4.outblaze.com> User-Agent: Mutt/1.4.2.1i X-Useless-Header: blackend.org X-Operating-System: FreeBSD 4.10-PRERELEASE cc: doc@FreeBSD.org Subject: Re: (Minor) Error located in FreeBSD handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 05:45:16 -0000 Fixed. Thanks. Marc From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 06:18:52 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAF0216A4CE for ; Mon, 11 Apr 2005 06:18:52 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A96443D58 for ; Mon, 11 Apr 2005 06:18:52 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id A2E355CE7; Mon, 11 Apr 2005 02:18:51 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 88901-05; Mon, 11 Apr 2005 02:18:50 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-53-96.ny325.east.verizon.net [68.161.53.96]) by pi.codefab.com (Postfix) with ESMTP id 96D605C58; Mon, 11 Apr 2005 02:18:50 -0400 (EDT) Message-ID: <425A16C9.1000900@mac.com> Date: Mon, 11 Apr 2005 02:18:49 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Linimon References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com cc: freebsd-doc@FreeBSD.org Subject: Re: CFD: additions to the PR submission article X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 06:18:52 -0000 Mark Linimon wrote: [ ... ] > Unless there are any objections I intend to commit these changes once > the freeze is lifted. Yay! These changes strike me as very good. > + > + Code in the base system that is written and maintained > + by others, and imported into &os; and adapted. Examples > + include bind, &man.gcc.1;, and > + &man.sendmail.8;. Most bugs in these areas should be reported > + to the &os; developers; but in some cases they may need to be > + reported to the original authors instead if the problems are > + not &os;-specific. Usually these bugs will fall under either > + the bin or gnu > + categories. > + Perhaps we could add a comment here requesting that the user try to test whether the problem happens on another platform. If the problem only shows up on FreeBSD, the user should definitely report it to the &os developers. If the problem is reproducable on other platforms, the user should definitely report it to the original authors, and maybe CC: the &os developers. -- -Chuck From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 09:25:16 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CA4D16A4CE for ; Mon, 11 Apr 2005 09:25:16 +0000 (GMT) Received: from eddie.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B23EA43D5D for ; Mon, 11 Apr 2005 09:25:15 +0000 (GMT) (envelope-from simon@eddie.nitro.dk) Received: by eddie.nitro.dk (Postfix, from userid 1000) id 7F50411A143; Mon, 11 Apr 2005 11:25:14 +0200 (CEST) Date: Mon, 11 Apr 2005 11:25:14 +0200 From: "Simon L. Nielsen" To: Mark Linimon Message-ID: <20050411092513.GB71160@eddie.nitro.dk> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i cc: freebsd-doc@FreeBSD.org Subject: Re: CFD: additions to the PR submission article X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 09:25:16 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2005.04.10 22:56:48 -0500, Mark Linimon wrote: > Unless there are any objections I intend to commit these changes once > the freeze is lifted. Looks good to me, except a few style issues, as noted below. > Index: article.sgml > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/FreeBSD/dcvs/doc/en_US.ISO8859-1/articles/problem-reports= /article.sgml,v > retrieving revision 1.36 > diff -u -r1.36 article.sgml > --- article.sgml 15 Jan 2005 02:16:42 -0000 1.36 > +++ article.sgml 11 Apr 2005 03:53:25 -0000 [...] > + > + Individual applications that are not in the base system > + but are instead part of the &os; Ports Collection (category > + ports). Most of these applications are > + not written by &os; developers; what &os; provides is merely > + a framework for installing the application. Therefore, you > + should only report a problem to the &os; developers when you > + believe the problem is &os;-specific; otherwise, you should > + report it to the authors of the software. > + > + No need for an empty line here. > + > + > + Then you should ascertain whether or not the problem is > + timely. There are few things This line could be made longer. > + that will annoy a developer more than receiving a problem report > + about a bug she has already fixed. > + > + If the problem is in the base system, you should first read > + the FAQ section on > + > + &os; versions, if you are not already familiar with > + the topic. It is not possible for &os; to fix problems in > + anything other than certain recent branches of the base system, > + so filing a bug report about an older version will probably > + only result in a developer advising you to upgrade to a > + supported version to see if the problem still recurs. The > + Security Officer team maintains the > + list of supported s/freebsd.org/FreeBSD.org/ - there are some entities that might be used (url.base) but I'm actually not really sure if that would fit here... --=20 Simon L. Nielsen --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCWkJ5h9pcDSc1mlERAnSmAJ4mXdQYVj6w4xBV6EjnMz64Efgm1wCgu/hu AI2kcWizxECGDvaxJsDYDvY= =Znkk -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 09:40:43 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69CEF16A4CE; Mon, 11 Apr 2005 09:40:43 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 034C943D4C; Mon, 11 Apr 2005 09:40:43 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 3F943149DB; Mon, 11 Apr 2005 04:40:42 -0500 (CDT) Date: Mon, 11 Apr 2005 04:40:42 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: "Simon L. Nielsen" In-Reply-To: <20050411092513.GB71160@eddie.nitro.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Mark Linimon cc: freebsd-doc@FreeBSD.org Subject: Re: CFD: additions to the PR submission article X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 09:40:43 -0000 On Mon, 11 Apr 2005, Simon L. Nielsen wrote: > > + > > + > > No need for an empty line here. Hmm, then the style is wrong elsewhere in the article. > > + Then you should ascertain whether or not the problem is > > + timely. There are few things > > This line could be made longer. Weak attempt at a diff reduction on the next line. OTOH since I moved the block that that line was in to make the emphasis clearer, it may not make any difference. > > + list of supported > > s/freebsd.org/FreeBSD.org/ Also wrong elsewhere IIRC. I can make these suggested changes when I commit, and then go back and fix the other ones in a separate checkin to make them consistent. mcl From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 11:01:02 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20F5016A4CE for ; Mon, 11 Apr 2005 11:01:02 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C415D43D4C for ; Mon, 11 Apr 2005 11:01:01 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3BB111H087254 for ; Mon, 11 Apr 2005 11:01:01 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3BB102Y087240 for freebsd-doc@freebsd.org; Mon, 11 Apr 2005 11:01:00 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 11 Apr 2005 11:01:00 GMT Message-Id: <200504111101.j3BB102Y087240@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: FreeBSD doc list Subject: Current unassigned doc problem reports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 11:01:02 -0000 Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/24] docs/27605 doc Cross-document references () s [2002/03/08] docs/35678 doc docproj Makefiles for web are broken for o [2002/03/21] docs/36168 doc -pthread/_THREAD_SAFE docs missing in gcc o [2002/11/15] docs/45303 doc Bug in PDF DocBook rendering o [2003/12/29] docs/60679 doc pthreads documentation does not describe o [2004/01/19] docs/61558 doc New SMC 2602W cards, using the ADM8211, a o [2004/01/20] docs/61605 doc Improve documentation for i386 disk geome o [2004/10/03] docs/72285 doc GCC manuals are out of sync o [2004/10/15] docs/72743 doc Porter's Handbook lacks info on using aut o [2004/10/19] docs/72897 doc ERRATA and RELNOTES are missing warnings o [2005/02/25] docs/78062 doc Sample Echo Pseudo-Device Driver for Free o [2005/02/27] docs/78154 doc [PATCH] Make en_US FreeBSD Handbook more o [2005/03/26] docs/79261 doc exttatr_list_file() wrongly documented in o [2005/04/04] docs/79543 doc doc change to firewall section of handboo o [2005/04/07] docs/79658 doc Freebsd Handbook incorrect about ATAPI CD 15 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- s [2000/07/19] docs/20028 doc ASCII docs should reflect tags o [2001/02/02] docs/24786 doc missing FILES descriptions in sa(4) o [2001/04/02] docs/26286 doc *printf(3) etc should gain format string s [2001/06/03] docs/27843 doc [PATCH] make.conf WITH_* variables aren't o [2001/07/26] docs/29245 doc top(1) manpage doesn't understand SMP a [2001/08/23] docs/30008 doc This document should be translated, comme p [2001/09/27] docs/30873 doc ``ip'' man page does not specify byte ord o [2001/10/07] docs/31109 doc replace gif images w/ png ones due to pat o [2002/01/05] docs/33589 doc Patch to doc.docbook.mk to post process . o [2002/01/09] docs/33724 doc [patch] fix Handbook error about Advanced o [2002/01/14] docs/33852 doc split(1) man page implies that input file o [2002/01/14] docs/33877 doc Documented behaviour of SF_flags for non- a [2002/02/16] docs/35011 doc There are no commands called "diskless" o o [2002/02/22] docs/35222 doc mailing list archive URL regexp suboptima o [2002/03/06] docs/35608 doc mt(1) page uses "setmark" without explana o [2002/03/06] docs/35609 doc mt(1) page needs explanation of "long era o [2002/03/06] docs/35612 doc ps(1) page "state" description doesn't me o [2002/03/07] docs/35642 doc lo(4) page maybe should document optional o [2002/03/07] docs/35644 doc lo(4) page presumes familiarity with prin o [2002/03/07] docs/35646 doc cp(1) page needs a "Bugs" section. o [2002/03/08] docs/35686 doc blackhole(4) page seems to contradict its o [2002/03/08] docs/35687 doc /etc/nsmb.conf missing mention of readers o [2002/03/10] docs/35732 doc adduser(8) page has obsolete reference an o [2002/03/16] docs/35943 doc at(1) config files are misplaced in /var/ o [2002/03/16] docs/35953 doc hosts.equiv(5) manual is confusing or wro o [2002/03/28] docs/36432 doc Proposal for doc/share/mk: make folded bo o [2002/03/29] docs/36449 doc symlink(7) manual doesn't mention trailin s [2002/05/07] docs/37843 doc manual for pthread_setschedparam is wrong o [2002/05/25] docs/38556 doc EPS file of beastie, as addition to exist o [2002/05/27] docs/38620 doc Committers Guide and CVS o [2002/05/31] docs/38772 doc firewall_type feature not mentioned on Ha o [2002/06/07] docs/38982 doc developers-hanbook/Jail fix p [2002/06/08] docs/39044 doc The man page for rot13(6) never mentions o [2002/06/13] docs/39213 doc No rc(4) man page o [2002/06/15] docs/39348 doc kenv fetch of hostname requires dhcp/boot o [2002/06/19] docs/39530 doc access(2) man page has unnecessarily broa o [2002/06/25] docs/39824 doc Various tweaks for doc/en_US.ISO8859-1/bo o [2002/07/10] docs/40423 doc Keyboard(4)'s definition of parameters to o [2002/07/21] docs/40851 doc [PATCH] "mergemaster -p" in UPDATING's "C o [2002/07/28] docs/41089 doc pax -B option does not mention interactio o [2002/08/02] docs/41270 doc confusing directions for kernelconfig cha o [2002/08/20] docs/41807 doc natd -punch_fw "bug" o [2002/08/20] docs/41820 doc Device driver confusion in Handbook (2.3) a [2002/08/27] docs/42058 doc Documentation: Installing Oracle 8i onto o [2002/10/04] docs/43651 doc stab(5) incorrectly states to include jus o [2002/10/09] docs/43861 doc non-trivial typo in wicontrol man page o [2002/10/11] docs/43941 doc Rationale for Upgrade Sequence o [2002/10/15] docs/44074 doc ln(1) manual clarifications [patch] o [2002/10/29] docs/44594 doc Handbook doesn't mention drivers.flp for o [2002/12/02] docs/45940 doc burncd missing info o [2002/12/11] docs/46196 doc Missing return value in (set_)menu_format o [2002/12/16] docs/46291 doc correlation between HZ kernel config para o [2002/12/16] docs/46295 doc please add information to Nvi recovery em o [2003/01/28] docs/47575 doc Clarify requirements for IPFW2 in STABLE o [2003/01/28] docs/47594 doc [PATCH] passwd(5) incorrectly states allo f [2003/02/02] docs/47818 doc ln(1) manpage is confusing o [2003/03/06] docs/48980 doc [PATCH] nsgmls -s errors and sect. 3.2.1 o [2003/03/23] docs/50211 doc [PATCH] Fix textfile creation o [2003/04/03] docs/50573 doc return values for res_query/res_search/re o [2003/04/07] docs/50677 doc [PATCH] update doc/en_US.ISO8859-1/books/ o [2003/05/06] docs/51875 doc atkbd(4) adjustment o [2003/05/06] docs/51891 doc DIAGNOSTICS in ed driver manpage don't ma o [2003/05/07] docs/51921 doc ls(1) manpage lacks some information abou o [2003/05/11] docs/52071 doc [PATCH] Add more information about soft u o [2003/05/25] docs/52672 doc Porter's Handbook: couple of corrections o [2003/06/21] docs/53575 doc Change to Handbook Section 20.9 o [2003/06/21] docs/53596 doc Updates to mt manual page o [2003/06/25] docs/53732 doc quota output and man page do not document o [2003/07/13] docs/54451 doc [patch] i386_{get|set}_ldt manual page is o [2003/07/26] docs/54879 doc man 1 jot, -r description o [2003/08/12] docs/55482 doc DUMP has access to block devices in a JAI o [2003/09/15] docs/56903 doc [patch] articles/fonts: add application t o [2003/09/16] docs/56915 doc [patch] articles/fonts: update links o [2003/09/24] docs/57153 doc S_IRWXU missing in fstat(2) man page? o [2003/09/30] docs/57388 doc INSTALL.TXT enhancement: mention ok promp o [2003/10/04] docs/57569 doc error on gensetdefs(8) man page o [2003/10/13] docs/57926 doc amd.conf.5 poorly format as it has both m o [2003/10/13] docs/57974 doc man page apropos for select macros (FD_SE o [2003/10/13] docs/57978 doc Type miss of GPIB in Hardware Notes o [2003/10/16] docs/58111 doc Handbook 12.4.3 Rebuilding ATA RAID1 Arra o [2003/10/28] docs/58615 doc update for Vinum chapter of Handbook: des o [2003/10/30] docs/58710 doc killpg(2) contains an error regarding sen o [2003/11/07] docs/59044 doc doc.docbook.mk does not properly handle a o [2003/11/19] docs/59477 doc Outdated Info Documents at http://docs.fr o [2003/11/24] docs/59649 doc Outdated 4.4BSD Documents at http://docs. o [2003/11/30] docs/59835 doc ipfw(8) man page does not warn about acce o [2003/12/23] docs/60529 doc resolver(5) man page is badly out of date o [2003/12/24] docs/60544 doc getenv(3) manpage doesn't state the retur o [2004/01/08] docs/61070 doc handbook: Installation docs misleading: o [2004/01/13] docs/61301 doc [patch] Manpage patch for aue(4) to enabl o [2004/01/21] docs/61667 doc Obsolete documentation on FreeBSD PnP o [2004/01/25] docs/61859 doc Incorrect informaiton about trace command o [2004/02/05] docs/62402 doc easily circumventable Blade150 problem o [2004/02/06] docs/62412 doc one of the diskless boot methods describe o [2004/02/12] docs/62719 doc cross-reference pccardd and devd o [2004/02/12] docs/62724 doc host(1) manpage does not include informat o [2004/02/22] docs/63215 doc Wrong prototypes in mi_switch(9) (ref doc o [2004/03/05] docs/63808 doc No manpage for devfs.conf o [2004/03/27] docs/64807 doc Handbook section on NAT incomplete o [2004/04/02] docs/65065 doc improper language ntpd man pages o [2004/04/13] docs/65477 doc Installation Instruction fail to mention o [2004/04/14] docs/65530 doc minor improvement to getgrent.3 o [2004/04/26] docs/65988 doc incorrect references to ppp.conf in handb o [2004/04/29] docs/66091 doc ppp(8) docs out-of-date for -CURRENT o [2004/05/04] docs/66264 doc [patch] libexec/rtld/rtld.1 typo fixes no o [2004/05/04] docs/66265 doc [patch] Document what -f and LD_TRACE_LOA o [2004/05/05] docs/66296 doc [patch] contrib/amd/amq/amq.8 uses log_op o [2004/05/07] docs/66343 doc unlisted supported card on man page for w o [2004/05/09] docs/66426 doc handbook update (desktop section): web br o [2004/05/10] docs/66483 doc [patch] share/man/man4/csa.4 grammar nits o [2004/05/17] docs/66768 doc 4_RELENG share/man/man4/ng_one2many.4 MFC o [2004/05/17] docs/66770 doc [patch] share/man/man4/ng_pppoe.4 tyops, o [2004/05/23] docs/67078 doc [patch] MFC of a rtld(1) man page is inco f [2004/06/10] docs/67806 doc [patch] Let 5.x users know how to boot in o [2004/06/13] docs/67893 doc boot.8's -m description is insufficient. o [2004/06/28] docs/68453 doc [patch] rc.subr.8 o [2004/07/02] docs/68606 doc Porter's Handbook: document how to write o [2004/07/09] docs/68843 doc Dates on rc.subr(8) & rc(8) are whack. o [2004/07/09] docs/68845 doc The .At macro produces unexpected results o [2004/07/19] docs/69271 doc Porter's Handbook: hint on proper pkg-mes o [2004/07/21] docs/69383 doc disklabel = bsdlabel in 5.X or later o [2004/08/01] docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not o [2004/08/09] docs/70217 doc Suggested rewrite of docproj/sgml.sgml o [2004/08/16] docs/70507 doc RE in BUG section of re_format(7) in obso o [2004/09/10] docs/71555 doc how to run matlab on 5.2 o [2004/09/14] docs/71739 doc amd.8 points to old web-page o [2004/09/16] docs/71782 doc mount_nfs man page is a bit out of date f [2004/09/21] docs/71980 doc Handbook says that no other software is k o [2004/10/06] docs/72383 doc manpage for awk(1) is terribly small and o [2004/11/06] docs/73583 doc [patch] add missing instructions to ndis( o [2004/11/07] docs/73638 doc ipfw(8): Clarify syntax for use of tables o [2004/11/08] docs/73679 doc FreeBSD 5.3 Release notes mention new nat o [2004/11/28] docs/74477 doc [patch] Correct several links in the cont o [2004/12/02] docs/74612 doc Updates to the glossary o [2004/12/14] docs/75068 doc login.conf(5) manual page says nothing ab f [2004/12/16] docs/75138 doc Typo in libexslt(4) o [2004/12/23] docs/75433 doc No manual pages for devfs.conf and devfs. o [2004/12/28] docs/75577 doc typos in man3 manual pages, login_class.3 o [2004/12/29] docs/75610 doc Advanced Networking Wireless section clea o [2005/01/05] docs/75864 doc FreeBSD 5.3 kern-developer install does n o [2005/01/05] docs/75865 doc comments on "backup-basics" in handbook o [2005/01/09] docs/75997 doc Handbook section on DNS needs updating o [2005/01/11] docs/76094 doc Incorrect statement about partition d o [2005/01/17] docs/76333 doc EOF indicator can be cleared by not only o [2005/01/19] docs/76472 doc [patch] tell porters handbook about OPTIO o [2005/01/20] docs/76515 doc missleading use of make -j flag in handbo o [2005/02/04] docs/77087 doc The bootvinum script given in the handboo o [2005/02/24] docs/78041 doc docs for md need further explanation of t o [2005/02/27] docs/78138 doc Error in pre-installation section of inst o [2005/03/01] docs/78240 doc Replace with around a # o [2005/03/02] docs/78275 doc Keyword size needs to be changed to lengt o [2005/03/06] docs/78479 doc SO_NOSIGPIPE socket option undocumented o [2005/03/06] docs/78480 doc Networked printer setup unnecessarily com o [2005/03/07] docs/78520 doc error in man(5) lpd.conf, lpd.perms pages o [2005/03/08] docs/78605 doc ppp man page errors o [2005/03/16] docs/78915 doc rfork()'s RFTHREAD is not documented o [2005/03/23] docs/79156 doc buffersize knob for sound(4) is a tunable o [2005/03/28] docs/79298 doc intro(2) man page has incorrect descripti o [2005/03/28] docs/79309 doc Mistake in Porter's Handbook, Chapter 14. o [2005/03/28] docs/79318 doc Example in archive_read man page is incor o [2005/04/08] docs/79667 doc Some sections of the handbook refer to /e o [2005/04/08] docs/79668 doc Add a vendor to the http://www.freebsd.or o [2005/04/09] docs/79731 doc manpage for gcc too old 163 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 19:44:43 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E71A16A4CE; Mon, 11 Apr 2005 19:44:43 +0000 (GMT) Received: from isis.sigpipe.cz (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id E411343D4C; Mon, 11 Apr 2005 19:44:41 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 79D371F87BEF; Mon, 11 Apr 2005 21:44:39 +0200 (CEST) Date: Mon, 11 Apr 2005 21:44:39 +0200 From: Roman Neuhauser To: Scott Long Message-ID: <20050411194439.GA98521@isis.sigpipe.cz> Mail-Followup-To: ports@freebsd.org, doc@freebsd.org References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <200504111212.25215.mi+mx@aldan.algebra.com> <425AA274.2090604@samsco.org> <200504111229.39072.mi+mx@aldan.algebra.com> <425AA728.7050809@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <425AA728.7050809@samsco.org> User-Agent: Mutt/1.5.6i cc: ports@freebsd.org cc: Mikhail Teterin cc: doc@freebsd.org Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 19:44:43 -0000 # scottl@samsco.org / 2005-04-11 10:34:48 -0600: > Mikhail Teterin wrote: > >My whole point, Scott, is that there is nothing special about "my gcc > >flags". NOTHING. Setting CPUTYPE to match one's processor flavor is a > >long-documented way to do things -- fact. Such setting results in the > >corresponding -march=XXX automatically -- fact. All ports must handle > >this. Those that can not are broken. Plan and simple. There is nothing to > >argue: `-O -pipe -march=opteron' must work. (...) > Is my car broken because it can't go 300km/hr? A Porshe can, so > shouldn't mine be able to? My point here is that there is a distinction > between the mozilla port being completely broken, and being broken in > non-standard or specific configurations. Saying that it's BROKEN > implies that it's 100% unusable, and that gives a false summary of the > problem. I built it from scratch with a very stock, unmodified system > and it works as well for me as I would expect. In my eyes, it's not > broken. But I don't play with custom gcc options. > > I'll readily concede that there are a lot of ports that are authored > in an i386-specific way and only work on amd64 by sheer luck. > Understnad that FreeBSD tends to also be at the leading edge of compiler > development. While we are using GCC 3.4, many other BSD and Linux > variants are still using 3.1, 3.2, or even 2.95. So it's quite possible > that the newer compiler has either bugs or stricter languange > compliance, and there aren't enough eyes yet to discover and fix these > problems. Shouting to everyone that mozilla is BROKEN doesn't help this > very much. I think this thread shows that there is a need for a written policy on -march / -mcpu / -mtune gcc options in ports. Heated discussions like this one could be avoided if the Porters Handbook included an article or chapter on this. Whether that policy was "-march= must work" or "-march= is unsupported" or "ports should filter out -march= if they break with it, patches for -march-related bugs welcome" (most reasonable IMNSHO) would be a matter of consensus, but would be a boon to have. MFT set to ports@ and doc@. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 20:34:55 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52A9B16A516; Mon, 11 Apr 2005 20:34:55 +0000 (GMT) Received: from 62-15-209-148.inversas.jazztel.es (62-15-209-148.inversas.jazztel.es [62.15.209.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C01343D5C; Mon, 11 Apr 2005 20:34:54 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from redesjm.local (orion.redesjm.local [192.168.254.16]) j3BKYh6n084680; Mon, 11 Apr 2005 22:34:43 +0200 (CEST) (envelope-from freebsd@redesjm.local) Received: from localhost (localhost [[UNIX: localhost]]) by redesjm.local (8.13.3/8.13.3/Submit) id j3BKYe13000921; Mon, 11 Apr 2005 22:34:40 +0200 (CEST) (envelope-from freebsd@redesjm.local) From: Jose M Rodriguez To: freebsd-ports@freebsd.org Date: Mon, 11 Apr 2005 22:34:39 +0200 User-Agent: KMail/1.8 References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <425AA728.7050809@samsco.org> <20050411194439.GA98521@isis.sigpipe.cz> In-Reply-To: <20050411194439.GA98521@isis.sigpipe.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200504112234.40840.freebsd@redesjm.local> X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.30.0.7; VDF: 6.30.0.45; host: antares.redesjm.local) cc: ports@freebsd.org cc: doc@freebsd.org cc: Scott Long cc: Roman Neuhauser cc: Mikhail Teterin Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 20:34:55 -0000 El Monday 11 April 2005 21:44, Roman Neuhauser escribi=F3: > # scottl@samsco.org / 2005-04-11 10:34:48 -0600: > > Mikhail Teterin wrote: > > >My whole point, Scott, is that there is nothing special about "my > > > gcc flags". NOTHING. Setting CPUTYPE to match one's processor > > > flavor is a long-documented way to do things -- fact. Such > > > setting results in the corresponding -march=3DXXX automatically -- > > > fact. All ports must handle this. Those that can not are broken. > > > Plan and simple. There is nothing to argue: `-O -pipe > > > -march=3Dopteron' must work. > > > I think this thread shows that there is a need for a written > policy on -march / -mcpu / -mtune gcc options in ports. Heated > discussions like this one could be avoided if the Porters Handbook > included an article or chapter on this. > And more work in /usr/share/mk/bsd.cpu.mk. Beggining with a way to take=20 in account what gcc will be used (we can't use -mtune for gcc=20 <3.4 ...). And a more conservative approach (-march=3Dpentium/pentiun-mmx/i686 and=20 =2Dmtune/-mcpu to the real cpu). But my skill are not in the way. I prefer cut CFLAGS in conflictive=20 ports. =2D- josemi > Whether that policy was "-march=3D must work" or "-march=3D is > unsupported" or "ports should filter out -march=3D if they break > with it, patches for -march-related bugs welcome" (most reasonable > IMNSHO) would be a matter of consensus, but would be a boon to have. > > MFT set to ports@ and doc@. From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 20:49:32 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14FB816A4CE; Mon, 11 Apr 2005 20:49:32 +0000 (GMT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F4C843D5D; Mon, 11 Apr 2005 20:49:31 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j3BKnTHt008068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 11 Apr 2005 16:49:30 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11])j3BKnN5C000301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Apr 2005 16:49:24 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.3/8.13.3) with ESMTP id j3BKnKmS051486; Mon, 11 Apr 2005 16:49:20 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.3/8.13.3/Submit) id j3BKnJSZ051485; Mon, 11 Apr 2005 16:49:19 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) X-Authentication-Warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Roman Neuhauser Date: Mon, 11 Apr 2005 16:49:19 -0400 User-Agent: KMail/1.7.2 References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <425AA728.7050809@samsco.org> <20050411194439.GA98521@isis.sigpipe.cz> In-Reply-To: <20050411194439.GA98521@isis.sigpipe.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504111649.19678.mi+mx@aldan.algebra.com> X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 cc: ports@freebsd.org cc: Scott Long cc: doc@freebsd.org Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 20:49:32 -0000 > patches for -march-related bugs welcome" (most reasonable IMNSHO) *All* patches are welcome -- including -march-related ones. That -march should work follows simply from the documented CPUTYPE setting and the bsd.cpu.mk "magic". Porters' handbook can help in _clarifying_ this, true. When mozilla compiles on amd64, plenty of warnings are thrown up regarding conversions between pointers and integers of different size. Could this be my problem -- exposed by some opteron-specific trick in gcc? -mi From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 21:08:27 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 883DE16A4CE; Mon, 11 Apr 2005 21:08:27 +0000 (GMT) Received: from 62-15-209-148.inversas.jazztel.es (62-15-209-148.inversas.jazztel.es [62.15.209.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 896A243D41; Mon, 11 Apr 2005 21:08:26 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from redesjm.local (orion.redesjm.local [192.168.254.16]) j3BL8GXK084884; Mon, 11 Apr 2005 23:08:16 +0200 (CEST) (envelope-from freebsd@redesjm.local) Received: from localhost (localhost [[UNIX: localhost]]) by redesjm.local (8.13.3/8.13.3/Submit) id j3BL8FRU001104; Mon, 11 Apr 2005 23:08:15 +0200 (CEST) (envelope-from freebsd@redesjm.local) From: Jose M Rodriguez To: freebsd-ports@freebsd.org Date: Mon, 11 Apr 2005 23:08:14 +0200 User-Agent: KMail/1.8 References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <20050411194439.GA98521@isis.sigpipe.cz> <200504111649.19678.mi+mx@aldan.algebra.com> 0.73a on corbulon.video-collage.com In-Reply-To: <200504111649.19678.mi+mx@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200504112308.15810.freebsd@redesjm.local> X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.30.0.7; VDF: 6.30.0.45; host: antares.redesjm.local) cc: ports@freebsd.org cc: doc@freebsd.org cc: Mikhail Teterin cc: Roman Neuhauser cc: Scott Long Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 21:08:27 -0000 El Monday 11 April 2005 22:49, Mikhail Teterin escribi=F3: > > patches for -march-related bugs welcome" (most reasonable IMNSHO) > > *All* patches are welcome -- including -march-related ones. That > -march should work follows simply from the documented CPUTYPE setting > and the bsd.cpu.mk "magic". Porters' handbook can help in > _clarifying_ this, true. > > When mozilla compiles on amd64, plenty of warnings are thrown up > regarding conversions between pointers and integers of different > size. Could this be my problem -- exposed by some opteron-specific > trick in gcc? > > -mi > Have you try firefox? Can you try the attached patch? Have you a real advantage using CPUTYPE? can you meter this? =2D-- patch mozilla begins here --- =2D-- /usr/HEAD/ports/www/mozilla/Makefile Wed Apr 6 22:25:05 2005 +++ www/mozilla/Makefile Mon Apr 11 23:04:02 2005 @@ -210,8 +210,10 @@ .endif =20 .if defined(WITH_OPTIMIZED_CFLAGS) =2DCFLAGS+=3D -O2 =2DCONFIGURE_ARGS+=3D --enable-optimize=3D-O2 +CFLAGS:=3D -O2 -fno-strict-aliasing ${CFLAGS:N-O*} +.else +CFLAGS:=3D -O ${CFLAGS:N-O*:N-m*} +CONFIGURE_ARGS+=3D --enable-optimize=3D-O .endif =20 .if !defined(WITHOUT_MENU_ENTRY) =2D-- patch mozilla ends here --- =2D- josemi From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 21:32:08 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1242816A4CE for ; Mon, 11 Apr 2005 21:32:08 +0000 (GMT) Received: from misty.eyesbeyond.com (glewis.dsl.xmission.com [166.70.56.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 625B243D48 for ; Mon, 11 Apr 2005 21:32:07 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.3/8.13.3) with ESMTP id j3BLW6t8081208 for ; Mon, 11 Apr 2005 15:32:06 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.3/8.13.3/Submit) id j3BLW555081207 for freebsd-doc@FreeBSD.org; Mon, 11 Apr 2005 15:32:05 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Mon, 11 Apr 2005 15:32:05 -0600 From: Greg Lewis To: freebsd-doc@FreeBSD.org Message-ID: <20050411213205.GB81116@misty.eyesbeyond.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: [glewis@FreeBSD.org: cvs commit: ports/java/javavmwrapper Makefile ports/java/javavmwrapper/src checkvms.1 javavm.1 javavms.5 registervm.1] X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 21:32:08 -0000 Review by people with an actual mdoc clue very much appreciated. ----- Forwarded message from Greg Lewis ----- glewis 2005-04-11 21:22:43 UTC FreeBSD ports repository Modified files: java/javavmwrapper Makefile Added files: java/javavmwrapper/src checkvms.1 javavm.1 javavms.5 registervm.1 Log: . Install manual pages for javavmwrapper. . Bump PORTREVISION. PR: 27075 Revision Changes Path 1.19 +15 -1 ports/java/javavmwrapper/Makefile 1.1 +56 -0 ports/java/javavmwrapper/src/checkvms.1 (new) 1.1 +111 -0 ports/java/javavmwrapper/src/javavm.1 (new) 1.1 +57 -0 ports/java/javavmwrapper/src/javavms.5 (new) 1.1 +79 -0 ports/java/javavmwrapper/src/registervm.1 (new) ----- End forwarded message ----- -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From owner-freebsd-doc@FreeBSD.ORG Mon Apr 11 21:33:07 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EECF16A4CE; Mon, 11 Apr 2005 21:33:07 +0000 (GMT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A60A43D45; Mon, 11 Apr 2005 21:33:06 +0000 (GMT) (envelope-from Mikhail.Teterin@murex.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j3BLWxVM008309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 11 Apr 2005 17:33:05 -0400 (EDT) (envelope-from Mikhail.Teterin@murex.com) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11])j3BLWr1h000561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Apr 2005 17:32:54 -0400 (EDT) (envelope-from Mikhail.Teterin@murex.com) Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.3/8.13.3) with ESMTP id j3BLWocF051725; Mon, 11 Apr 2005 17:32:50 -0400 (EDT) (envelope-from Mikhail.Teterin@murex.com) Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.3/8.13.3/Submit) id j3BLWntv051724; Mon, 11 Apr 2005 17:32:49 -0400 (EDT) (envelope-from Mikhail.Teterin@murex.com) X-Authentication-Warning: mteterin.us.murex.com: mteterin set sender to Mikhail.Teterin@murex.com using -f From: Mikhail Teterin Organization: Murex North America To: Jose M Rodriguez Date: Mon, 11 Apr 2005 17:32:49 -0400 User-Agent: KMail/1.7.2 References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <200504111649.19678.mi+mx@aldan.algebra.com> <200504112308.15810.freebsd@redesjm.local> In-Reply-To: <200504112308.15810.freebsd@redesjm.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504111732.49681.Mikhail.Teterin@murex.com> X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 cc: ports@freebsd.org cc: doc@freebsd.org cc: Scott Long cc: Roman Neuhauser cc: freebsd-ports@freebsd.org Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 21:33:07 -0000 > Have you try firefox? Firefox built and installed fine. > Can you try the attached patch? Thank you, but I want to find the bug, not a workaround. > Have you a real advantage using CPUTYPE? can you meter this? Did not try to. My concern is not the fraction of a percent of performance, but the bug sitting in there :-) -mi From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 01:22:53 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13AAE16A4CE for ; Tue, 12 Apr 2005 01:22:53 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id CFB6D43D58 for ; Tue, 12 Apr 2005 01:22:51 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail invoked by alias); 12 Apr 2005 01:22:50 -0000 Received: from p508BD94F.dip.t-dialin.net (EHLO lofi.dyndns.org) [80.139.217.79] by mail.gmx.net (mp028) with SMTP; 12 Apr 2005 03:22:50 +0200 X-Authenticated: #443188 Received: from kiste.my.domain (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.13.3/8.12.10) with ESMTP id j3C1MeuB007491 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 12 Apr 2005 03:22:41 +0200 (CEST) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-ports@freebsd.org Date: Tue, 12 Apr 2005 03:22:28 +0200 User-Agent: KMail/1.8 References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <425AA728.7050809@samsco.org> <20050411194439.GA98521@isis.sigpipe.cz> In-Reply-To: <20050411194439.GA98521@isis.sigpipe.cz> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1722307.cJYLIF9Le7"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200504120322.38262.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new X-Y-GMX-Trusted: 0 cc: ports@freebsd.org cc: doc@freebsd.org cc: Scott Long cc: Roman Neuhauser cc: Mikhail Teterin Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 01:22:53 -0000 --nextPart1722307.cJYLIF9Le7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday, 11. April 2005 21:44, Roman Neuhauser wrote: > Whether that policy was "-march=3D must work" or "-march=3D is > unsupported" "-march is unsupported" (existence of CPUTYPE-macro nonwithstanding) *is* a= nd=20 *has been* the *long standing* consensus.=20 Mikhail seems to have forgotten that not too long ago, CPUTYPE was somethin= g=20 for only the most daring would use. GCC's optimizers have seen much=20 improvement since then, but just because you can get away with always setti= ng=20 CPUTYPE for everything much more often these days doesn't mean it's not ris= ky=20 anymore (or we would have the resources to runtime test every port in the=20 collection with all possible CPUTYPE settings on each arch). =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1722307.cJYLIF9Le7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCWyLeXhc68WspdLARAgOOAJ4teyLC/cp+nSPOncWXUQZFjQdvbQCeJoMo lBV6lFfz4bdWzK7RzDIb4lA= =amI2 -----END PGP SIGNATURE----- --nextPart1722307.cJYLIF9Le7-- From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 05:33:36 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EA4316A4CE; Tue, 12 Apr 2005 05:33:36 +0000 (GMT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4AEC43D46; Tue, 12 Apr 2005 05:33:35 +0000 (GMT) (envelope-from mi@corbulon.video-collage.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j3C5XUQ1010556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Apr 2005 01:33:33 -0400 (EDT) (envelope-from mi@corbulon.video-collage.com) Received: from corbulon.video-collage.com (mi@localhost.video-collage.com [127.0.0.1])j3C5XOxC008135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2005 01:33:25 -0400 (EDT) (envelope-from mi@corbulon.video-collage.com) Received: (from mi@localhost)j3C5XNFL008134; Tue, 12 Apr 2005 01:33:23 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <200504120533.j3C5XNFL008134@corbulon.video-collage.com> To: michaelnottebrock@gmx.net (Michael Nottebrock) Date: Tue, 12 Apr 2005 01:33:23 -0400 (EDT) In-Reply-To: <200504120322.38262.michaelnottebrock@gmx.net> X-Mailer: ELM [version 2.5 PL7] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 cc: Scott Long cc: doc@freebsd.org cc: Mikhail Teterin cc: Roman Neuhauser cc: ports@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 05:33:36 -0000 > > Whether that policy was "-march must work" or "-march is > > unsupported" > > "-march is unsupported" (existence of CPUTYPE-macro nonwithstanding) > *is* and *has been* the *long standing* consensus. > Mikhail seems to have forgotten that not too long ago, CPUTYPE was something > for only the most daring would use. GCC's optimizers have seen much > improvement since then, but just because you can get away with always setting > CPUTYPE for everything much more often these days doesn't mean it's not risky > anymore (or we would have the resources to runtime test every port in the > collection with all possible CPUTYPE settings on each arch). Nothing except Mozilla has ever caused problems for Mikhail, that was traceable to this switch. make.conf(5) documents it, it should work. Period. And everything does work. Complex things like Perl build fine and pass their self-tests (make test). The entire KDE built and works (although it is lacking self-tests). Time to stop blaming compiler for the software's bug -- and Mozilla has plenty of them. -mi From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 06:05:53 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61FAC16A4CE for ; Tue, 12 Apr 2005 06:05:53 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9372D43D62 for ; Tue, 12 Apr 2005 06:05:51 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail invoked by alias); 12 Apr 2005 06:05:50 -0000 Received: from p508BB620.dip.t-dialin.net (EHLO lofi.dyndns.org) [80.139.182.32] by mail.gmx.net (mp026) with SMTP; 12 Apr 2005 08:05:50 +0200 X-Authenticated: #443188 Received: from kiste.my.domain (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.13.3/8.12.10) with ESMTP id j3C65QK5014275 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 12 Apr 2005 08:05:33 +0200 (CEST) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: Mikhail Teterin Date: Tue, 12 Apr 2005 08:05:18 +0200 User-Agent: KMail/1.8 References: <200504120533.j3C5XNFL008134@corbulon.video-collage.com> In-Reply-To: <200504120533.j3C5XNFL008134@corbulon.video-collage.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1177400.TspJ3DznPG"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200504120805.23933.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new X-Y-GMX-Trusted: 0 cc: Scott Long cc: doc@freebsd.org cc: Mikhail Teterin cc: Roman Neuhauser cc: ports@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 06:05:53 -0000 --nextPart1177400.TspJ3DznPG Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday, 12. April 2005 07:33, Mikhail Teterin wrote: > > Mikhail seems to have forgotten that not too long ago, CPUTYPE was > > something for only the most daring would use. GCC's optimizers have seen > > much improvement since then, but just because you can get away with > > always setting CPUTYPE for everything much more often these days doesn't > > mean it's not risky anymore (or we would have the resources to runtime > > test every port in the collection with all possible CPUTYPE settings on > > each arch). > > Nothing except Mozilla has ever caused problems for Mikhail, that was > traceable to this switch. Lucky Mikhail. I actually don't believe you really missed the tons of broke= n=20 ports that -march=3Dp4 used to produce with early versions of gcc3 though. > make.conf(5) documents it, it should work. Period. make.conf(5) documents CFLAGS. What would you like to infer from that fact? > And everything does=20 > work. Complex things like Perl build fine and pass their self-tests (make > test). The entire KDE built and works (although it is lacking self-tests). > > Time to stop blaming compiler for the software's bug -- and Mozilla has > plenty of them. If a compiler optimization produces a bad binary while the same compiler wi= th=20 the switch off does not (or a different version of the compiler with the=20 switch does not), the compiler usually *is* to blame. I don't know of cours= e=20 whether this is the case, I couldn't find the beginning of this thread. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1177400.TspJ3DznPG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCW2UjXhc68WspdLARAuiWAKCcAjYjTR+Yu6RxK12Pt5Y35aO4vQCgkD3l s+/pQE4svBVydBEAtHKq+yE= =3jB5 -----END PGP SIGNATURE----- --nextPart1177400.TspJ3DznPG-- From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 06:21:28 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 903D616A4CE for ; Tue, 12 Apr 2005 06:21:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0226443D3F for ; Tue, 12 Apr 2005 06:21:28 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3C6Od8C035507; Tue, 12 Apr 2005 00:24:40 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <425B681F.5090506@samsco.org> Date: Tue, 12 Apr 2005 00:18:07 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Nottebrock References: <200504120533.j3C5XNFL008134@corbulon.video-collage.com> <200504120805.23933.michaelnottebrock@gmx.net> In-Reply-To: <200504120805.23933.michaelnottebrock@gmx.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: doc@freebsd.org cc: Mikhail Teterin cc: Roman Neuhauser cc: ports@freebsd.org cc: freebsd-ports@freebsd.org cc: Mikhail Teterin Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 06:21:28 -0000 Michael Nottebrock wrote: > On Tuesday, 12. April 2005 07:33, Mikhail Teterin wrote: > > >>>Mikhail seems to have forgotten that not too long ago, CPUTYPE was >>>something for only the most daring would use. GCC's optimizers have seen >>>much improvement since then, but just because you can get away with >>>always setting CPUTYPE for everything much more often these days doesn't >>>mean it's not risky anymore (or we would have the resources to runtime >>>test every port in the collection with all possible CPUTYPE settings on >>>each arch). >> >>Nothing except Mozilla has ever caused problems for Mikhail, that was >>traceable to this switch. > > > Lucky Mikhail. I actually don't believe you really missed the tons of broken > ports that -march=p4 used to produce with early versions of gcc3 though. > > >>make.conf(5) documents it, it should work. Period. > > > make.conf(5) documents CFLAGS. What would you like to infer from that fact? > > >>And everything does >>work. Complex things like Perl build fine and pass their self-tests (make >>test). The entire KDE built and works (although it is lacking self-tests). >> >>Time to stop blaming compiler for the software's bug -- and Mozilla has >>plenty of them. > > > If a compiler optimization produces a bad binary while the same compiler with > the switch off does not (or a different version of the compiler with the > switch does not), the compiler usually *is* to blame. I don't know of course > whether this is the case, I couldn't find the beginning of this thread. > This isn't always true. Pointer aliasing rules become stricter but still spec-legal with certain optimizer modules, for example. I'd 99% bet that mozilla or a dependency is to blame here. However, that doesn't mean that the port is non-functional. It means that it has known bugs in the non-default case that should be documented until they are fixed. I'm glad that Mikhail has exposed one of these problems, and I hope that both a temporary and permanent solution can be found. Scott From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 06:22:50 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FA2916A4CE; Tue, 12 Apr 2005 06:22:50 +0000 (GMT) Received: from mail.allbsd.org (vlsi00.si.noda.tus.ac.jp [133.31.130.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 888AE43D3F; Tue, 12 Apr 2005 06:22:49 +0000 (GMT) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p2190-adsau15hon-acca.tokyo.ocn.ne.jp [220.111.154.190]) (authenticated bits=128) by mail.allbsd.org (8.13.1/8.13.1) with ESMTP id j3C6Mlsq043189; Tue, 12 Apr 2005 15:22:48 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) by delta.allbsd.org (8.13.1/8.13.1) with ESMTP id j3C6LZgI027624; Tue, 12 Apr 2005 15:21:36 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Tue, 12 Apr 2005 15:21:27 +0900 (JST) Message-Id: <20050412.152127.68167560.hrs@allbsd.org> To: freebsd-doc@FreeBSD.org, doc-committers@FreeBSD.org From: Hiroki Sato In-Reply-To: <20050403.115513.102122838.hrs@allbsd.org> References: <20050401100457.GA623@nosferatu.blackend.org> <20050403.023303.122620886.hrs@allbsd.org> <20050403.115513.102122838.hrs@allbsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Tue_Apr_12_15_21_27_2005_231)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.83/822/Tue Apr 12 13:55:55 2005 on gatekeeper.allbsd.org X-Virus-Status: Clean Subject: HEADS UP: doc tree tagged for 5.4R X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 06:22:50 -0000 ----Security_Multipart(Tue_Apr_12_15_21_27_2005_231)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, Hiroki Sato wrote in <20050403.115513.102122838.hrs@allbsd.org>: hr> As announced, the doc/ tree is now in a slush. Please postpone all hr> non-essential changes for the English documents until after the doc/ hr> tree is tagged (currently scheduled for 11 April, 2005). The doc tree has been tagged for 5.4-RELEASE. If you noticed a problem or have a change which must be included in the release, please let me know. You can consider the doc tree is open for commits now, but any sweeping changes should be postponed until after the release day. Thank you for your cooperation and keep up the good work! -- | Hiroki SATO ----Security_Multipart(Tue_Apr_12_15_21_27_2005_231)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCW2jnTyzT2CeTzy0RAh7zAJ0Ssv6cG1hW0zDMRJZjL1WsujA2uACgunCs nIUgH255665p09qGnb1kLTg= =smM8 -----END PGP SIGNATURE----- ----Security_Multipart(Tue_Apr_12_15_21_27_2005_231)---- From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 06:39:29 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BA1516A4CE for ; Tue, 12 Apr 2005 06:39:29 +0000 (GMT) Received: from nym.alias.net (nym.alias.net [18.26.0.252]) by mx1.FreeBSD.org (Postfix) with SMTP id 5F4B543D48 for ; Tue, 12 Apr 2005 06:39:28 +0000 (GMT) (envelope-from nobody@nym.alias.net) Date: 12 Apr 2005 06:39:27 -0000 Message-ID: <20050412063927.19442.qmail@nym.alias.net> To: freebsd-doc@freebsd.org X-Loop: nym.alias.net From: Help Message Subject: Instructions for using nym.alias.net X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 06:39:29 -0000 INSTRUCTIONS FOR NYM.ALIAS.NET $Revision: 1.77 $ TRANSLATIONS OF THIS DOCUMENT Unter http://www.iks-jena.de/mitarb/lutz/anon/n.a.n.help.html findet sich dieser Text in deutscher Sprache. Zagladajac do http://www.hyperreal.art.pl/cypher/remailer/nym.html>hyperreal a znajdziecie polskojezyczne opracowania dotyczace pseudonimow. ADDITIONAL HELP If you need help for problems which probably aren't bugs in the server software, please direct your questions to the newsgroup alt.privacy.anon-server or to the maintainer of the client software you are using (if appropriate). NOTICE For the very latest version of this file, finger or send mail to . An HTML version of this file is available by fingering or sending mail to . The version of this file on the nym.alias.net web page is sometimes a few days older than the version available directly from nym.alias.net. PGP 5.0 Nym.alias.net does not support PGP 5. It is recommended that you use PGP 2.6.2 (or a more recent version of PGP 2) with nym.alias.net, though PGP 5.0 might work in compatibility mode. Nym.alias.net will not support PGP 5 until a stable, free, legal (in the US) version is available in source form. INTRODUCTION The nym.alias.net server allows you to send and receive E-mail pseudonymously through a username of your choice on nym.alias.net. If, for instance, you choose username , you will be able to send and receive E-mail at that address, and even get fingered at that address. The system is designed to prevent anyone, even the administrators of nym.alias.net, from finding out the real person behind any mail alias. If you use this service properly, an adversary will have to compromise multiple remailers operated by different people in order to find out your real identity. For each mail alias or "nym" (short for pseudonym) on nym.alias.net, the server has on file a PGP public key, a reply block, and a few configuration parameters. The PGP public key is used to authenticate both configuration requests for your nym and outgoing messages you wish to send from your nym.alias.net address. Such messages should be sent to nym.alias.net anonymously, to avoid any connection between your real E- mail address and your pseudonym. The PGP key can also be used to encrypt any mail received for before that mail is forwarded to you through the remailer network. The reply block contains instructions for sending mail to your real E- mail address (or to a newsgroup such as alt.anonymous.messages if you want your mail delivered there). These instructions are successively encrypted for a series of so-called Type-1 remailers in such a way that each remailer can only see the identity of the next hop. To send you an E-mail message (after optionally encrypting it with your nym's PGP key), the server will prepend your reply-block to that message and feed the result directly to the Type-1 remailer . [Note that this remailer is reserved for use by nym.alias.net aliases and people debugging their reply-blocks, so you shouldn't see it listed in any of the standard remailer lists.] Thus, mail you send to nym.alias.net arrives anonymously through the remailer network. Mail you receive from nym.alias.net leaves the server with an encrypted reply block, and can be sent either directly to you or to a message pool such as the newsgroup alt.anonymous.messages. When used properly, therefore, nym.alias.net provides the convenience of an ordinary E-mail address with a strong assurance that your true identity will remain a secret. CLIENT SOFTWARE This document describes the gory details of the E-mail message interface to nym.alias.net. While it is possible to create and decode all your nym messages manually, it is far easier to use client software which automates the process. The primary design goal of nym.alias.net was to provide the highest degree of privacy possible. This required a great deal of complexity in the message formats, complexity far better handled by client software than humans. If you use a unix system, there is a program called premail which creates and manages nym.alias.net pseudonyms for you. For more information on premail, see ftp://utopia.hacktic.nl/pub/replay/pub/remailer/premail. The nym.alias.net support in premail was contributed by the author of nym.alias.net, so if you report nym.alias.net-specific problems in premail you can CC . If you use a DOS/Windows system, you can use a program called Potato to create nyms, decrypt incoming mail and send outgoing mail from your nym. See http://www.bigfoot.com/~potatoware for more information or to download Potato. Another DOS/Windows program for managing nyms is called EasyNym, and is available from http://home.clara.net/j.davies/easynym/. Still another, DOS/Windows program for managing nyms is called Private Idaho. See http://www.eskimo.com/~joelm/pi.html for more information on Private Idaho. A newer version of Private Idaho (recommended) is available from http://home.sn.no/~balchen/igloo/pidaho/. Please do not contact for help with Private Idaho or Potato, as the administrators of nym.alias.net do not use either software package or have access to the hardware and operating systems necessary to try them. If you have problems with these software packages, try asking for help in the newsgroup alt.privacy.anon-server. In addition, there are some unofficial nym.alias.net/PI instructions at http://www.dnai.com/~wussery/pgp.html may be of use, too. SETTING UP A MAIL ALIAS To create a new alias on nym.alias.net, you will need to generate a PGP key for that alias, create a reply block for receiving mail sent to that alias, and finally send both of these to in a configuration message. This process is somewhat complicated, and can easily go wrong. For this reason it is recommended that you use one of the programs described in the section on "CLIENT SOFTWARE" if you can. If you do create an alias manually and you run into problems while setting things up, skip to the section on "PROBLEMS AND SOLUTIONS" at the end to see if you are making a common mistake. An alternate, unofficial, and perhaps less technically daunting description of setting up a pseudonym can be found at http://www.stack.nl/~galactus/remailers/nym.html. GENERATING A PGP KEY FOR YOUR NYM To generate a new PGP public/private key pair for use with your nym, run the command `pgp -kg'. PGP will ask you to enter a user ID for your public key. What you choose for a user ID depends on how you intend to use your nym's PGP public key. There are two approaches you can take: 1. Publish your nym's key. If you want to sign messages directly with your nym's PGP key and have others encrypt mail with that key, you should choose a PGP user ID that contains your nym.alias.net E-mail address in angle brackets. For instance, an ID like this: A Test User If you do this, you will be able to submit your key to the PGP key servers and even make it available via finger at nym.alias.net (see the +fingerkey Nym-command below). Be aware, however, that publishing your nym's PGP key may put your privacy at risk. PGP does not protect the identities or fingerprints of keys on your private key ring; only the keys themselves are protected by a passphrase. If your nym's PGP key is publicly available, anyone with access to your secring.pgp file (or a backup of it) will be able to figure out if that public key belongs to you. Thus, you should only publish your nym's PGP key if your secring.pgp file is secure, or if you have software such as premail (finger premail-info@nym.alias.net) that will encrypt entire PGP keyrings for a pseudonym account. 2. Keep the public key secret. Alternatively, you can prevent your PGP key from being traceable to your nym account. For this approach, you should pick a user ID that is not very descriptive and gives no indication of either your real E-mail address or your nym address. Though PGP will not allow a null user ID, you can choose a user ID which is only a space, or something seemingly unimportant like `test key'. Do not sign your PGP key if you want to keep it secret. Do not submit it to any key servers, give it out to people, or use it to sign messages that aren't also sent to and encrypted for or . Note that even if you don't publish your nym's PGP key, you can have the nym.alias.net server sign your outgoing mail with its own PGP key. This can be used to guard against simple mail forgeries. Obviously, however, it is preferable to use your own PGP key if you can do so safely. Whichever approach you choose, make sure you never use your nym public key for any non-nym related purposes. Your nym secret key should probably have a different passphrase from your regular PGP key to help prevent you from using it in the wrong context. You may also wish to put a line like: MYNAME = in the file $HOME/.pgp/config.txt (which you can create if it does not already exist). This explicitly tells PGP to use your regular PGP key rather than your nym key by default. Once you have a PGP key for your pseudonym, you can extract it to a file, for instance by executing these commands from your shell: pgp -fkxa "nym key ID" > tmpfile On Unix systems, you may wish to make sure tmpfile cannot be read by any other users. For this you can run the command `umask 077' first. Here and in the rest of this document, "nym key ID" is the user ID you chose for the PGP key you generated, or some unique substring of that key. If you chose option one above (publishing your nym key), then you can just use yournym@nym.alias.net as the nym key ID. Otherwise, you will need to use whatever user ID you did choose. Note that if the user ID you type contains any spaces, you will need to surround the whole thing with double quotes, as shown above. (You can surround it with double quotes anyway--it won't hurt anything.) CREATING A REPLY BLOCK Another explanation of how to create reply blocks is available on the help page of the now defunct alpha.c2.org remailer: http://www.well.com/user/abacard/alpha.html. Note that alpha.c2.org did not run the same software as nym.alias.net, so only the description of reply blocks will be relevant on this web page, not any other description of how the service worked. To create a reply block, first choose some passphrases for shared-key, conventional encryption with "pgp -c". Suppose you want your message encrypted first with your nym's public key, then with shared key "passphrase_b", then with shared key "passphrase_a". Create a remailer message like this: :: Anon-To: you@your.email.address Latent-Time: +0:00 Encrypt-Key: passphrase_a ** Here "Latent-Time: +0:00" will prevent any delay. You can and should use something longer or omit the Latent-Time header if you want more security. Note that if for passphrase_a you choose a passphrase with a space character in it, some remailers may require you to surround the passphrase with quotes (though other remailers may not understand the quotes). You will need to encrypt the above message with a remailer's PGP public key. Note that the remailers used in this example do not exist any more. They are here only as examples. You can get an up to date list of remailers and their public keys from http://www.cs.berkeley.edu/~raph/remailer-list.html, or by fingering remailer-list@kiwi.cs.berkeley.edu. On this list, only remailers that have all three of the "cpunk", "pgp", and "ek" properties should be used for reply blocks. In addition, make sure the remailers you chose are listed in the statistics section lower down on the page (some of the remailers listed in the top section are no longer functional). You can add the PGP keys of all the remailers to your PGP public key ring by running: finger pgpkeys@kiwi.cs.berkeley.edu | pgp -fka Once you have selected a remailer, for example , and have added that remailer's key to your PGP public keyring, encrypt the above message with that remailer's key. If the above were stored in a file rblock1, for instance, you would encrypt the message with the command: pgp -eat rblock1 remailer@utopia.hacktic.nl To yield a file called rblock1.asc with cyphertext like this: -----BEGIN PGP MESSAGE----- Version: 2.6.2 hIwC/nqSW1QDQfUBBACknZMV93wFS2CH0orlgslmEm+alhjI1eKwbbTTmeRWC5Rg /S3vZw+95ZuCZfqxKE0XrgZXzOEwfoyBcpVvf9Pb9D19TqEMTmmL/Jpl1xcxmbJ2 OGsHpQ/TxpazBCVhdBmPblj5wWvwfG1+ZKpIkQ5hiLJhryQM/TUDarEscs3zdaYA AAB5231aMcQ74AKoDZizABMF3Tw+olV4mm4jVo9cMn2B3Rj2XBFl4pV9VL3h0ZQB cPY/ytBRyZPugr0NpLgjO+q6mEjCcgQrxpYQ+1PvFPdDx1GmJ5ogZqW+AVHsNqAp vRoiG8ZhXs4r3E8liFsNtMMf6CUAsdV2ZoX1Hw== =Bla3 -----END PGP MESSAGE----- Prepend to this the following header: :: Encrypted: PGP Finally add another set of remailer commands to send the above cyphertext to the remailer for which you just encrypted-- remailer@utopia.hacktic.nl in this example. The result should look like this: :: Anon-To: remailer@utopia.hacktic.nl Latent-Time: +0:00 Encrypt-Key: passphrase_b :: Encrypted: PGP -----BEGIN PGP MESSAGE----- Version: 2.6.2 hIwC/nqSW1QDQfUBBACknZMV93wFS2CH0orlgslmEm+alhjI1eKwbbTTmeRWC5Rg /S3vZw+95ZuCZfqxKE0XrgZXzOEwfoyBcpVvf9Pb9D19TqEMTmmL/Jpl1xcxmbJ2 OGsHpQ/TxpazBCVhdBmPblj5wWvwfG1+ZKpIkQ5hiLJhryQM/TUDarEscs3zdaYA AAB5231aMcQ74AKoDZizABMF3Tw+olV4mm4jVo9cMn2B3Rj2XBFl4pV9VL3h0ZQB cPY/ytBRyZPugr0NpLgjO+q6mEjCcgQrxpYQ+1PvFPdDx1GmJ5ogZqW+AVHsNqAp vRoiG8ZhXs4r3E8liFsNtMMf6CUAsdV2ZoX1Hw== =Bla3 -----END PGP MESSAGE----- ** Note two things about this message. First, there must be a blank line before the second `::'. Second, you must add `**' to the end of your message. `Encrypt-Key:' will cause everything below the `**' to be encrypted. If you don't include it, remailers will either fail to encrypt your mail or even discard it. For greater security, you should now repeat this process some number of times so that mail to your pseudonym travels through multiple remailers. Pick another remailer from the list. Encrypt the entire above message from and including the first `::' up to and including the `**', and add a new set of headers for sending to the second remailer you have just picked. The result will look just like the above message, only with a larger PGP portion and different `Anon-To:' and `Encrypt-Key:' headers. For instance, if you chose the remailer , your reply block might now look like this: :: Anon-To: cpunk@remail.ecafe.org Latent-Time: +0:00 Encrypt-Key: passphrase_c :: Encrypted: PGP -----BEGIN PGP MESSAGE----- Version: 2.6.2 /S3vZw+95ZuCZfqxKE0XrgZXzOEwfoyBcpVvf9Pb9D19TqEMTmmL/Jpl1xcxmbJ2 dHNr1NA6WWaIfV0pR+sluNWFxNYuTk0OFgtg8c0ABRG0Kzxjb25maWdAbnltLmFs aWFzLm5ldD4vPHNlbmRAbnltLmFsaWFzLm5ldD6JAJUDBRAxumL3RMG0dWLnx9EB AaRTA/4xIgNrem7Yay0/rFfXgoGHUhWsZVhAlQP1fVEIRYuYEC4Biodwx3nYL31r 9IcgBkm/DUddkfCUfroMr7wbm6GnYnrVLc4dZ9ACCjUVX7n5hvanc8/Efx0yE03l D+r9n5liz5X4vk65f+DIw1LykM9zTg/4GNwAENn6H5YTtg6Q+IkBFQMFEDG6YVlO hIwC/nqSW1QDQfUBBACknZMV93wFS2CH0orlgslmEm+alhjI1eKwbbTTmeRWC5Rg OGsHpQ/TxpazBCVhdBmPblj5wWvwfG1+ZKpIkQ5hiLJhryQM/TUDarEscs3zdaYA AAB5231aMcQ74AKoDZizABMF3Tw+olV4mm4jVo9cMn2B3Rj2XBFl4pV9VL3h0ZQB cPY/ytBRyZPugr0NpLgjO+q6mEjCcgQrxpYQ+1PvFPdDx1GmJ5ogZqW+AVHsNqAp vRoiG8ZhXs4r3E8liFsNtMMf6CUAsdV2ZoX1Hw== =Bla3 -----END PGP MESSAGE----- ** The last remailer you encrypt for will be the first remailer your mail goes through. The last `Encrypt-Key:' header will therefore be the first key with which your message is encrypted, and the last with which you will need to decrypt received mail. With this example reply block, you would need decrypt received mail first with "passphrase_a", then "passphrase_b", then "passphrase_c", and finally with your nym's private key. SENDING IN A NYM-CREATION REQUEST Once you have a PGP key and reply block for your nym, you must send a configuration request to to create the nym. A creation request contains four things: The pseudonym you wish to use, a "create" command, your nym's public key, and the reply block for your nym. The reply-block must always come last in your mail message. Suppose you wanted to choose the alias . If you wanted outgoing mail from your nym to have From: lines like this: From: A Test User And you wanted people who fingered your nym to see: Mail Alias: yournym Name: A Test User PGP Public-Key: -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzGf6A8AAAEEAPknqWEUA8U4+l5TFkD5Fj0COten6bbIe5bBb/1MvI+w6mFl z06CPb2K/Z1fzjT48ZyxwYR+S3jU3Z96JEFRl99HYh3lTIUiBHW/XtwyefF0y61x qYkNuUpSFh9BDBFM7N3uVvaNbzLiFnqCpZLm5ZIfrLcla3qUgkTBtHVi58fRAAUR tDhsY3MgbWl4bWFzdGVyIGFkbWluaXN0cmF0b3IgPG1peC1hZG1pbkBhbm9uLmxj cy5taXQuZWRxPokAlQMFEDGf6ClEwbR1YufH0QEBX60D/jZ5MFRFIFA1VxTPD5Zj Xw2bvqJqFvlwLD5SSHCVfe/ka6ALuxZGFKD/pHpUAkfv1hWqAYsJpi0cf8HSdi23 bh5dUeLJnHHHDmd9d55MuNYI6WTi+2YoaiJOZT3C70oOuzVXuELZ+nZwV20yxe8y 4M3b0Xjt9kq2upbCNuHZmQP+ =jIEc -----END PGP PUBLIC KEY BLOCK----- You could a create message like this: Config: From: yournym Nym-Commands: create +acksend +fingerkey name="A Test User" Public-Key: -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzGf6A8AAAEEAPknqWEUA8U4+l5TFkD5Fj0COten6bbIe5bBb/1MvI+w6mFl z06CPb2K/Z1fzjT48ZyxwYR+S3jU3Z96JEFRl99HYh3lTIUiBHW/XtwyefF0y61x qYkNuUpSFh9BDBFM7N3uVvaNbzLiFnqCpZLm5ZIfrLcla3qUgkTBtHVi58fRAAUR tDhsY3MgbWl4bWFzdGVyIGFkbWluaXN0cmF0b3IgPG1peC1hZG1pbkBhbm9uLmxj cy5taXQuZWRxPokAlQMFEDGf6ClEwbR1YufH0QEBX60D/jZ5MFRFIFA1VxTPD5Zj Xw2bvqJqFvlwLD5SSHCVfe/ka6ALuxZGFKD/pHpUAkfv1hWqAYsJpi0cf8HSdi23 bh5dUeLJnHHHDmd9d55MuNYI6WTi+2YoaiJOZT3C70oOuzVXuELZ+nZwV20yxe8y 4M3b0Xjt9kq2upbCNuHZmQP+ =jIEc -----END PGP PUBLIC KEY BLOCK----- Reply-Block: :: Anon-To: remailer@utopia.hacktic.nl Latent-Time: +0:00 Encrypt-Key: passphrase_b :: Encrypted: PGP -----BEGIN PGP MESSAGE----- Version: 2.6.2 hIwC/nqSW1QDQfUBBACknZMV93wFS2CH0orlgslmEm+alhjI1eKwbbTTmeRWC5Rg /S3vZw+95ZuCZfqxKE0XrgZXzOEwfoyBcpVvf9Pb9D19TqEMTmmL/Jpl1xcxmbJ2 OGsHpQ/TxpazBCVhdBmPblj5wWvwfG1+ZKpIkQ5hiLJhryQM/TUDarEscs3zdaYA AAB5231aMcQ74AKoDZizABMF3Tw+olV4mm4jVo9cMn2B3Rj2XBFl4pV9VL3h0ZQB cPY/ytBRyZPugr0NpLgjO+q6mEjCcgQrxpYQ+1PvFPdDx1GmJ5ogZqW+AVHsNqAp vRoiG8ZhXs4r3E8liFsNtMMf6CUAsdV2ZoX1Hw== =Bla3 -----END PGP MESSAGE----- ** Note that the first line of this message was `Config:'. Any message sent to config@nym.alias.net will be silently discarded if the first line is not `Config:'! Note that the `From:' line just contains the name "yournym", and nothing else. Do not put angle brackets or anything else on your From line. (Though as a special case, `From: yournym@nym.alias.net' will work as long as it is not surrounded by angle brackets.) Note also that your PGP key will not be visible via finger unless the key user ID contains your nym E-mail address in angle-brackets. You can also prevent your public key from being available via finger by omitting the `+fingerkey' from the `Nym-Commands:' line. The above message must then be encrypted with the nym.alias.net public key, and signed by your nym's new private key. The nym.alias.net public key is listed here, and is also available by fingering or sending mail to . You can run finger remailer-key@nym.alias.net | pgp -fka to add this key to your public keyring. You might then run `pgp -kvc nym.alias.net' and verify that your copy of the public key has fingerprint `B6 41 A7 85 4E A8 C7 6D DD 02 18 4E 4A A9 84 E3'. -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzGzy5AAAAEH/2JjaB4AuQff90Mejru+FVptG4/wPmwK7WteavNXJpYxWoRm SzxwNz70q4QCLKBR0QnzXqGeGtCB5IE4dIuPIkMiPvRv57rBaDe4qkzNkgwuZiH9 qGMsOSidCf+xaIJyL7RtljKuDSU8KH2OGIdwEpGa20U+9oXabWCpWwVvfJhgxPFF xhiFLeMzhEUgsVXxIn2ThD8AyHyTUXWd11nvvTeKt+y9qX+7fUDrn6HIl1lFmxQA RAOc83jjDNgWbanHWG9+1g8KFLkBrEdxJtNQeb/JMSZ122Dxda5CwtMnQGI0mCcr dHNr1NA6WWaIfV0pR+sluNWFxNYuTk0OFgtg8c0ABRG0Kzxjb25maWdAbnltLmFs aWFzLm5ldD4vPHNlbmRAbnltLmFsaWFzLm5ldD6JAJUDBRAxumL3RMG0dWLnx9EB AaRTA/4xIgNrem7Yay0/rFfXgoGHUhWsZVhAlQP1fVEIRYuYEC4Biodwx3nYL31r 9IcgBkm/DUddkfCUfroMr7wbm6GnYnrVLc4dZ9ACCjUVX7n5hvanc8/Efx0yE03l D+r9n5liz5X4vk65f+DIw1LykM9zTg/4GNwAENn6H5YTtg6Q+IkBFQMFEDG6YVlO TQ4WC2DxzQEBIvMH/jER9tiQcJG2NvkiOqcIeBSPLb15EPFMg1He3clRIz398ToH iv4oNKZEjVox3O0zowcUW0zfgtzhlMbudOwgoylCpCxVukuF1tsleoGlvDES0iA8 WdnYftt/rr3awf0j2pmLFbCmEDFaebuYgRXGe5yavaSjFDPzjFZqKwTYs5VnKOjP XjI0yrem4PXw6K5sOANJKaa6yFrHJ/58iqbV8Rl7p0qNwwIi1nDn5UgpDOFDqWMq sO9HUjRD2Y+Kmq6qlSg1gKV1hehZuAxHKtJAIZf+MPaI/sRbs79oN5GVwpmqoiZF vz6bLS+qs69kVwg2RQoY2BSAzyUeT+rw70YfLAc= =ekCY -----END PGP PUBLIC KEY BLOCK----- When you have the nym.alias.net public key, you can encrypt and sign your configuration request with the command: pgp -seat file config@nym.alias.net -u "nym key ID". Once you have produced a PGP encrypted and signed message, mail it to through some anonymous remailers. If the name you chose is available, this will create your mail alias. You can send mail to or finger to get a list of pseudonyms already in use. If your request is successful, you will get mail through your reply block acknowledging successful completion. In this acknowledgment, you may also be asked to confirm your reply block by sending mail to a particular confirmation address. This two step process in necessary at times to cut back on the number of nyms with bad reply blocks which are left for dead. A new account will be deleted if the reply block has not been confirmed in one week. Note that if you receive an acknowledgment which does not ask for confirmation, your mail alias will already be functional. SENDING MAIL FROM YOUR PSEUDONYM Once you have created a mail alias, you will automatically receive mail sent to that alias at nym.alias.net (encrypted first with the public key you mailed it, then with any Encrypt-Keys you specified in your reply block). To send mail from that alias, simply create a mail message, encrypt it with the nym.alias.net public key, sign it with your nym key, and mail it to . Thus, for example, create a file with (substituting the name you chose for "yournym"): From: yournym To: mail2news@anon.lcs.mit.edu Newsgroups: alt.test Subject: ignore this nym test just a test Note once againt that the `From:' line just contains the name "yournym", and nothing else. The contents of the From line in outgoing mail will be set by the pseudonym server, based on your account name and what you set with the `name=' `Nym-Command'. Do not put angle brackets around yournym or include anything else on the From line. (Though as a special case, `From: yournym@nym.alias.net' is also acceptable, as long as it is not surrounded by angle brackets.) If this file is called testpost, encrypt and sign the file by running: pgp -seat testpost send@nym.alias.net -u "nym key ID" This will create a file called testkey.asc, which you can then mail (through other remailers) to to post the above test message to the newsgroup alt.test. If you used the `+signsend' Nym-Command when creating your nym, any mail you send through will be PGP signed and dated by the nym.alias.net private key to certify its authenticity. If you do not wish your mail to be signed, or if you have published your alias's public key and wish to sign messages yourself with that key, you can disable this default signing by sending a -signsend configuration command as described below. Regardless of your nym's configuration settings, you can also enable or disable both signing and acknowledgment of outgoing mail on a per- message basis. Do so by including in your encrypted and signed E-mail message a `Nym-Commands:' header with one or two of the +signsend, - signsend, +acksend, or -acksend keywords. Ordinarily the recipients of mail you send will be determined by the `To:', `Cc:', and `Bcc:' headers of the message, which have the usual behavior. However, occasionally you may wish to specify a list of recipients explicitly. This may be useful, for instance, if you wanted to PGP-encrypt a message for some recipients but not others. In such a case, you would need to mail two copies of the message, one encrypted and one not. However, you might still want the `To:' and `Cc:' headers to reflect the full list of recipients. You can explicitly specify the full list of recipients by listing them in a `Hidden-To:' header of your E-mail message. If a `Hidden-To:' header is present in mail you send, that header will be removed and mail will be sent to the users it lists regardless of any other headers in the mail message. A NOTE ON POSTING FOLLOWUP MESSAGES TO USENET In order to post a followup article to Usenet and have it appear in a thread, you must set the `Subject:' and `References:' headers of your message correctly. The subject of your message should be the same as the article to which you are replying, unless you are replying to the first message in a thread, in which case you should prepend "Re: " to the original subject. To build a references header, copy the references header of the article to which you are replying, and append that article's Message-ID. If you are replying to the first article of a thread, it won't have a references header. In that case just use the article's Message-ID as your references header. Be sure to leave a space between Message-IDs in your references header. For example, if replying to a message which includes these headers: Subject: Re: anonymous remailers References: <5dfqlm$m50@basement.replay.com> Message-ID: <5dko56$1lv$1@news02.deltanet.com> your reply should contain these headers: Subject: Re: anonymous remailers References: <5dfqlm$m50@basement.replay.com> <5dko56$1lv$1@news02.deltanet.com> [Note that an indented line in a message header indicates a continuation of the previous line.] If replying to the first message in a thread, with these headers: Subject: Help with P.G.P Message-ID: <5e96gi$opv@job.acay.com.au> your reply should contain these headers: Subject: Re: Help with P.G.P References: <5e96gi$opv@job.acay.com.au> The references header can be trimmed to include only IDs from messages that you have quoted from or are replying to. CHANGING OR DELETING YOUR MAIL ALIAS To change either your public key, your reply block, or the parameters of your alias, you can simply send another message to similar to the one you used to create your nym. However, when modifying an existing nym, you can omit any fields you don't want to change. Thus, you can send a message which contains "Nym- Commands" but no Public-Key or Reply-Block, or one which contains only a new Reply-Block. Of course, do not include "Nym-Commands: create" in a configuration message for an existing nym as your modification request will then fail. Once again, the first line of the configuration message you send must be `Config:', and the message will need to be both signed and encrypted with pgp -seat message config@nym.alias.net -u "nym key ID" as described above for sending mail. As an example, the following message, mailed to , would set the reply block for : Config: From: yournym Reply-Block: :: Anon-To: remailer@utopia.hacktic.nl Latent-Time: +0:00 Encrypt-Key: passphrase_b :: Encrypted: PGP -----BEGIN PGP MESSAGE----- Version: 2.6.2 hIwC/nqSW1QDQfUBBACknZMV93wFS2CH0orlgslmEm+alhjI1eKwbbTTmeRWC5Rg /S3vZw+95ZuCZfqxKE0XrgZXzOEwfoyBcpVvf9Pb9D19TqEMTmmL/Jpl1xcxmbJ2 OGsHpQ/TxpazBCVhdBmPblj5wWvwfG1+ZKpIkQ5hiLJhryQM/TUDarEscs3zdaYA AAB5231aMcQ74AKoDZizABMF3Tw+olV4mm4jVo9cMn2B3Rj2XBFl4pV9VL3h0ZQB cPY/ytBRyZPugr0NpLgjO+q6mEjCcgQrxpYQ+1PvFPdDx1GmJ5ogZqW+AVHsNqAp vRoiG8ZhXs4r3E8liFsNtMMf6CUAsdV2ZoX1Hw== =Bla3 -----END PGP MESSAGE----- ** After changing your reply block, you will receive an acknowledgment through the new reply block. This confirmation may ask you to confirm your reply block, in which case you must reply to the acknowledgment message before your new reply block is put in place. To delete your alias entirely, send encrypted and signed mail with simply the lines: Config: From: yournym Nym-Commands: delete (substituting your real alias name for yournym). After deleting your alias, you should receive PGP-signed mail explicitly acknowledging the deletion of that alias. An acknowledgment simply confirming generic successful completion of your request does not indicate that your alias has been deleted. You can also verify deletion of your nym by retrieving a list of all nyms through . You can give several commands using the "Nym-Commands:" header in a message to . You can place several of these commands in a single Nym-Commands header, separated by spaces, or you can can put multiple "Nym-Commands:" headers in the same message. Valid commands are: +acksend/-acksend Enable/disable an automatic acknowledgment each time a message is successfully remailed for your alias through . This configuration option can be overridden on a per-message basis by a `Nym-Commands:' header in an outgoing mail message. +signsend/-signsend Enable/disable automatic PGP signing of any outgoing mail you send through the remailer. If you disable this, anyone can forge mail from your nym very easily (particularly since the sendmail program running on nym.alias.net does not add Received: headers to all mail). If you have decided to publish the public key of your nym, however, you will want to sign all outgoing messages with your nym's public key (that is sign them a second time inside the message-- will always reject a message unless it can strip off a valid signature around the whole thing). Having a nym.alias.net signature around another signature can prevent mail readers from verifying the inside signature, so you should choose the -signsend option if you want to sign all messages yourself. (See the section on "GENERATING A PGP KEY FOR YOUR NYM" for a note on the dangers of publishing your nym's PGP key.) This configuration option can be overridden on a per-message basis by a `Nym-Commands:' header in an outgoing mail message. +cryptrecv/-cryptrecv Enable/disable automatic encryption with your nym's public key of messages received for your alias. Disabling public-key encryption will reduce your privacy. However, it may also allow you to decode received mail with client software designed for the older alpha.c2.org-style pseudonym servers. Note that even when +cryptrecv is enabled, you still should use shared-key encryption between remailer hops to prevent your mail from being traced. See the section on "SECURITY CONSIDERATIONS" below for more details. +fixedsize/-fixedsize When you send the +fixedsize Nym-Command, all messages you receive will be split and/or padded to exactly the same size (roughly 10K). This padding will take place outside the public key encryption, and so will only be useful if you also use shared-key encryption. If you do used shared-key encryption, however, (and you really should), having all your messages be the same size will make it significantly harder for anyone to do traffic analysis on mail to your nym. +disable/-disable One of the most effective forms of attack on a pseudonymous remailer such as this is to flood the system with messages for a particular destination. Moreover, because this alias software does not know a message's final destination, it is possible that some joker could point an alias at itself (maybe even using two reply-blocks to create exponentially increasing levels of traffic). To protect against this, if you send or receive more than about 10 Megabytes of mail in one day, your alias will be disabled and further mail to you it will bounce. You will receive mail notifying you of the situation if this happens to you. At this point, you can re-enable your alias by sending a message with `Nym-Commands: -disable' to . +fingerkey/-fingerkey Allow people to obtain your nym's PGP public key by fingering your E-mail address. The Key ID on your PGP public key must contain your nym's full E-mail address in angle brackets in order to be given out through finger. Thus, a Key ID of "Test User " would be visible by fingering yournym@nym.alias.net, but a key ID of just "yournym@nym.alias.net" would not be. See the section on "GENERATING A PGP KEY FOR YOUR NYM" below for a discussion of the security implications of publishing your nym's public key. name="Your Alias Name" Typically E-mail `From:' lines contain a user's full name in addition to his/her E-mail address or account name. To set up a name to be printed in all your outgoing messages, like this: From: Your Alias Name and to have that full name appear when your nym is fingered, you should send the corresponding `name=' Nym-Command in a configuration message. Note that the outer quotes are necessary even if your name does not contain any white space. If your full name name actually contains any quote or backslash characters, you must precede them with a backslash, as in, for instance: Nym-Commands: name="Billy \"the kid\" Smith" To delete your full name so that outgoing mail only shows your alias address and finger shows a full name of '???', send the command name="". create/create? One of these two commands must be given when creating a new alias. The create command will fail if a nym with the chosen name already exists. The create? command will create a new nym, but can also update an existing nym if the configuration message is signed by the nym's previous private key. delete This command deletes your alias and wipes your reply block. As described above, you should receive PGP-signed mail explicitly acknowledging the deletion of your alias. An acknowledgment simply confirming generic "successful execution" of your request does not indicate that your alias has been deleted. Note the message will not be PGP-encrypted if you have selected -cryptrecv, but in that case encryption with the proper shared keys should provide some assurance of authenticity. +nobcc/-nobcc When set to +nobcc, your nym will not receive any blind carbon copies of mail messages. When you have selected +nobcc, any E-mail sent to your pseudonym will bounce if it does not display your E- mail address in a To, Cc, Resent-To, or Resent-Cc header. Aparently- To headers are ignored for the purpose of the nobcc option--mail will bounce even if you are listed in an Apparently-To header. While blind carbon copies can be a legitimate and useful mechanism, most so-called SPAM messages are sent as blind carbon copies. Thus, +nobcc may reduce the number of SPAM messages you receive at the possible expense bouncing some legitimate blind carbon copies. - nobcc undoes the effect of a previous +nobcc command, and allows the reception of blind carbon copies again. Note: You will not be able to subscibe to any mailing lists if you select +nobcc. Default values for the Nym-Commands are: -acksend -signsend +cryptrecv -fixedsize -disable -fingerkey name="" -nobcc REPLAY The remailer keeps a replay cache, and will not accept the same message twice unless each copy has been separately signed. Thus, it is safe to send multiple copies of outgoing E-mail messages through very long remailer chains if you are worried about one copy not getting through. Whether one or more copies actually make it through, only one copy will go out. One side effect of this is, however, that if you PGP sign a test message and mail it in multiple times, it will only work the first time. Note that signatures are only considered valid for a week. Thus, if mail comes to send@nym.alias.net more than a week after you signed it, that mail will be dropped. MULTIPLE REPLY BLOCKS Sometimes anonymous remailers can be unreliable, and you would like to receive two copies of all your messages through two independent remailer chains. Alternatively, perhaps you want to send one copy of each E-mail message you receive to the bit bucket through a long series of anonymous remailers. You can assign multiple reply blocks to your nym by prefixing each with "Reply-Block:" at the end of a message to . For example, the following message to : Config: From: yournym Reply-Block: :: Anon-To: nobody@some.remailer.machine Latent-Time: +0:00 Encrypt-Key: key1 ** Reply-Block: :: Anon-To: you@your.email.address Latent-Time: +1:00r Encrypt-Key: key2 ** Will setup your alias to send one copy of each message you receive to immediately, and to send a second copy to after up to one hour of random delay. Of course, in order for this to be useful, you should use more complex reply-blocks which chain through multiple remailers. It may also make traffic analysis more difficult if you don't always use the same remailer path. You can assign a probability to a reply block by adding "x=probability" to the `Reply-Block:' line (where 'x' can be any single letter variable name). For example, consider the following reply- block: Reply-Block: p=0.75 :: Anon-To: nobody@some.remailer.machine Latent-Time: +0:00 Encrypt-Key: key1 ** Reply-Block: q=0.5 :: Anon-To: you@through.one.remailer Latent-Time: +1:00r Encrypt-Key: key2 ** Reply-Block: q=0.5 :: Anon-To: you@through.another.remailer Latent-Time: +1:00r Encrypt-Key: key3 ** 3/4 of the time, a copy of a message you receive will immediately be mailed to . After some random delay (up to an hour), your message will be mailed either to or to . Multiple reply-blocks with the same probability variable are mutually exclusive. Thus since the q blocks are "q=0.5" and "q=0.5", and since 0.5 + 0.5 = 1.0, you are guaranteed to get a copy of all your mail. Generally speaking, you will probably want all the weights associated with a particular variable to add up to 1.0 unless the reply-block is just for cover traffic. Bizarre behavior may occur if your probabilities add up to more than one--use different probability letters if you want to receive multiple copies of mail. While the idea of using many different reply-blocks with small probabilities may seem appealing for defeating traffic analysis, keep in mind that each reply block is traceable back to you. Suppose you have 10 reply blocks for your nym, each with probability 0.1. If those reply blocks become compromised, only one of the 10 will have to be uncovered to find out your real identity. SECURITY CONSIDERATIONS If you care about the secrecy of your identity, then the only truly secure way of of protecting it is by pointing all your reply blocks to usenet newsgroups and using a news server that does not log. See the section on the section on "REPLY BLOCKS POINTING TO NEWSGROUPS" for instructions on doing this. KEYRINGS AND PUBLIC KEYS The most important thing to realize about the privacy of your messages is that anyone can determine your nym's PGP public key ID from looking at an encrypted message, and anyone get the key IDs of your private keys from your private key ring without needing a passphrase. That means if you don't conventionally super-encrypt mail (with `Encrypt-Key:' headers), an observer on the network or at a remailer may be able to determine which public key corresponds to which nym, and use this to track messages. If you redirect your mail to news group alt.anonymous.messages without conventionally encrypting it, observers will be able to determine your nym's public key ID and observe how much mail you are getting. For this reason, you should conventionally encrypt your mail in addition to public-key encrypting it. If you only want to use conventional encryption for received mail, you can disable RSA encryption by sending signed/encrypted mail with 'Nym-Commands: -cryptrecv' to . There is a large benefit to using public-key encryption, however. If you only use conventional encryption and your reply-block is compromised, previously recorded messages to you will be able to be decrypted. With RSA-encrypted messages, there is no way for anyone but you to read your mail once it has left nym.alias.net. With the `+signsend' option, nym.alias.net will sign all messages you send with its PGP key (adding a disclaimer at the end of the message). This is primarily to prevent simple mail forgery which is rendered even simpler by the fact that the sendmail on nym.alias.net doesn't keep logs. If you care about the authenticity of messages sent through your nym, however, you should probably publish its PGP key, set the `- signsend' Nym-Command configuration option, and PGP-sign all your outgoing messages yourself. Be aware, however, that the identity of a key on your PGP private key ring is stored in cleartext (even though the key itself is protected by a passphrase). Thus, if you publish your nym's public key, anyone who can gain access to your PGP secret keyring (or a backup tape containing it) will find out the identity of your nym, even if that person does not know your passphrase! For this rather unfortunate reason, you are faced with a tradeoff between authenticity and secrecy. One solution is to use software that keeps your nym's PGP keys on separate keyrings, and encrypts the entire keyrings. Premail is one software package that supports this. Send mail to or finger for more information on using premail with nym.alias.net. REPLY BLOCKS POINTING TO NEWSGROUPS Reply blocks offer you strong privacy by preventing any single remailer operator from finding out the identity of a pseudonym. Nonetheless, if an adversary manages to compromise all remailers in your reply block, he will learn your true identity. Moreover, a strongly enough motivated adversary could even operate several remailers himself, or eavesdrop on communication between remailers and analyze traffic patterns and message sizes to try to track you down. An essay describing some of the vulnerabilities of Type-1 remailers can be found at http://www.obscura.com/~loki/remailer/remailer-essay.html. If you need the very highest level of security, you should completely dissociate your identity from your pseudonym's reply block. Do this by forwarding your nym mail to a newsgroup rather than to your own E-mail address. Of course, retrieving messages from a newsgroup will be considerably more difficult than simply receiving mail, particularly as nym client software does not currently support newsgroups. Moreover, you may loose mail if you don't check for news often enough, as most news servers expire articles after a few days to a week. If do you decide to forward your nym mail to a newsgroup, you should use alt.anonymous.messages, a group which exists precisely to carry reply messages to anonymous users. To set up a reply block pointing to this group, you must change the innermost portion of the reply block. Recall that one begins a standard reply block like this: :: Anon-To: you@your.email.address Latent-Time: +0:00 Encrypt-Key: passphrase_a A reply block that posts to usenet should start like this: :: Anon-To: mail2news@anon.lcs.mit.edu Latent-Time: +0:00 Encrypt-Key: passphrase_a ## Subject: some sort of subject line is required Newsgroups: alt.anonymous.messages [The `##' marks tell remailers to paste headers into a mail message. The Newsgroups and Subject headers are required for news postings.] The rest of the procedure for creating the reply block is identical. Note that while sending your mail to a newsgroup makes it virtually impossible to track you down from your reply block, you should keep in mind that news servers usually log which newsgroups and how many articles you read. Thus, someone with a pretty good idea of who you are may actually have an easier time tracking you down if you use alt.anonymous.messages than if you don't. Much depends on the particulars of the news server you use. YOUR MAIL TO NYM.ALIAS.NET If you need high security you should also be careful with messages you send to , , and . Though nym.alias.net does not keep mail logs, the machine from which you send mail may very well do so. Morever, you shouldn't be relying exclusively on nym.alias.net for your privacy. Even if the machine is secure, someone may be eavesdropping on its network traffic. Thus, avoid sending E-mail directly to the config and send addresses. Send your mail through anonymous remailers instead. You can send mail to nym.alias.net through the same Type-1 remailers you use to create your reply blocks. However, a second, stronger, category of remailers known as Type-2 or mixmaster remailers ofters higher security. Type-2 remailers may be worth using, particularly if you have avoided trusting Type-1 remailers by pointing your reply block to a newsgroup. More information about mixmaster remailers is available from http://www.obscura.com/~loki/. The mixmaster remailer (short name "lcs") is on the same machine as nym.alias.net. You might want to add it to the end of your mixmaster chain when sending mail to nym.alias.net, as this should increase security without hurting reliability. Note that the higher security mixmaster message format prevents Type-2 remailers from working in reply blocks. POLICY Any use of this alias service to violate Massachusetts or US federal law is strictly prohibited. Additionally, you may not use this service for commercial or otherwise profit-generating purposes, as this would violate the acceptable use policy of the network on which nym.alias.net resides. Do not rely on this nym server to protect your identity. You should be relying far more heavily on the integrity of the remailers through which you chain your replies. The nym.alias.net service is provided in the hope that it will be useful, but the administrators can make no guarantees whatsoever that your identity will not be compromised. That said, we will make a reasonable effort to keep the machine secure and to prevent your reply block from being compromised. However, your reply block, PGP key, and nym configuration information will all be backed up to tape in encrypted form, and could potentially be retrievable by the administrators even after you delete your account. The server also keeps (and backs up in encrypted form) two statistics about your nym: First it counts the amount of mail your alias has received in the current 24 hour period, so as to detect flooding attacks and alias loops with exponential message explosion (see the description of the -disable Nym-Command for more info). Second, the server stores the date of the last day on which you sent a PGP-signed message to or . Nym.alias.net will not accept any mail messages larger than 1 Megabyte. In addition, your account will automatically be disabled if you send or receive more than about 10 Megabytes of mail in one day. Note, however, that this limit can be waived for individual aliases. If you wish to set up a middleman-style remailer, run an anonymous mailing list, or provide some other service to the community anonymously, you can contact pseudonymously to explain your intent and have the 10 Megabyte/day limit removed from your account. In order to garbage-collect abandoned accounts or accounts with lost PGP keys, your nym will be deleted if you don't send any PGP-signed mail to or for a period of 120 days. You should receive several warning messages before this happens, however, as long as your reply-block is still valid. It is probably a good idea to update your reply-block every few months anyway, and simply doing this will guarantee that your nym never expires. Nym.alias.net is the same machine as anon.lcs.mit.edu. Keep this in mind when choosing which remailers to chain through. (Using mix@anon.lcs.mit.edu as your last hop for mail to nym.alias.net is probably a good idea if and only if you you also chain through one more hop than you would otherwise have felt comfortable with.) PROBLEMS AND SOLUTIONS Here are some common problems you may have run into if you can't get your alias to work properly. If these aren't your problems, you can seek additional help by posting to the newsgroup alt.privacy.anon-server. If you believe you have found a bug in the server software (and you definitely may have), please send anonymous, pseudonymous, or regular E- mail to reporting the problem. When reporting a bug, include as detailed an account of the problem as possible. In addition, if the bug involves configuration requests or outgoing messages, please include in your bug report the entire PGP cyphertext of a or message demonstrating the bug. Investigating bugs often involves debugging server software with the particular message that caused the problem. Therefore, if you submit a bug report from your real E-mail address rather than from a pseudonym, you should create a new throw-away nym on which to demonstrate the problem. Otherwise you may reveal your pseudonym to the administrators of nym.alias.net. COMMON PROBLEMS You can't create a pseudonym. You sent mail to , never got a reply, and when you send mail to or finger the name you wanted does not show up as used. * You forgot to make the first line of your config message "Config:". Any message to which does not begin with a line "Config:" will be sliently discarded. * You did not encrypt your message to with the nym.alias.net public key, or you forgot to sign it with your private key. Only encrypted messages are read by , and even your initial creation request must be signed by the public key you include in the configuration message. * You clearsigned the configuration message after encrypting it, instead of encrypting and signing at the same time. You must encrypt and sign configuration messages in one pass, using the command: pgp -seat message config@nym.alias.net -u "nym key ID" This should produce a message with the first line: -----BEGIN PGP MESSAGE----- If instead you run `pgp -eat ...', followed by `pgp -sat ...', you will get something like this: -----BEGIN PGP SIGNED MESSAGE----- - -----BEGIN PGP MESSAGE----- Version: 2.6.2 OGsHpQ/TxpazBCVhdBmPblj5wWvwfG1+ZKpIkQ5hiLJhryQM/TUDarEscs3zdaYA The nym server cannot decode such configuration messages. They will be bounced. * You forgot the -t option to PGP. When the nym server decrypts messages, it expects all lines to end LF. If you use an operating system which ends lines CR LF and you don't use the -t flag to PGP, your messages will contain unwanted CR characters which will pose problems when parsing the message headers. * Are the date and time correct on your computer? Nym.alias.net uses the timestamps in PGP signatures to help detect replay attacks on config and send messages. However, if the date on your computer is off by more than a few days, messages you send to config@nym.alias.net may be silently discarded. You created an alias on nym.alias.net, but never received a reply from the server. However, when you send mail to or finger , the nym appears to have been created. When you send mail to your pseudonym, however, it bounces with the message "Account disabled." * Whenever you set a new reply block, you may required to confirm the validity of the new reply block before it gets put into use. Instructions on how to confirm a new reply block are always mailed out via that reply block, so that if your new reply block does not work properly you will be unable to confirm it. If you are creating a new account and thus don't have an existing reply block, any mail to your pseudonym will bounce. If you never received a confirmation for your creation request and mail to that pseudonym bounces, you probably have an invalid reply block. To fix this, just submit a new reply block, using a message like the following, signed/encrypted with `pgp -seat' and sent to . (You don't need to supply Public-Key or Nym-Commands section, as these will already have been processed in your initial message.) Config: From: yournym Reply-Block: :: Anon-To: remailer@utopia.hacktic.nl Latent-Time: +0:00 Encrypt-Key: passphrase_b :: Encrypted: PGP -----BEGIN PGP MESSAGE----- Version: 2.6.2 hIwC/nqSW1QDQfUBBACknZMV93wFS2CH0orlgslmEm+alhjI1eKwbbTTmeRWC5Rg /S3vZw+95ZuCZfqxKE0XrgZXzOEwfoyBcpVvf9Pb9D19TqEMTmmL/Jpl1xcxmbJ2 OGsHpQ/TxpazBCVhdBmPblj5wWvwfG1+ZKpIkQ5hiLJhryQM/TUDarEscs3zdaYA AAB5231aMcQ74AKoDZizABMF3Tw+olV4mm4jVo9cMn2B3Rj2XBFl4pV9VL3h0ZQB cPY/ytBRyZPugr0NpLgjO+q6mEjCcgQrxpYQ+1PvFPdDx1GmJ5ogZqW+AVHsNqAp vRoiG8ZhXs4r3E8liFsNtMMf6CUAsdV2ZoX1Hw== =Bla3 -----END PGP MESSAGE----- ** See the next section for ideas on what may have gone wrong with your reply block. You can't receive mail. You think you created an alias. Mailing even shows your alias name got created. Maybe you can even send mail from your alias. However, any time you send mail to your alias you never receive anything. * Could you have a bad reply block? Try testing your reply block by mailing a short message with it to . * Could you have forgotten the '**' (encrypt below) marks? Type-1 remailers require '**' marks to determine where conventional encryption should begin. If you omit the '**' marks, unpredictable behavior may result. Note that remailers leave the '**' marks themselves intact and only encrypt stuff below those marks. Thus, adding '**' only once in the final reply block will seem to work. However, this significantly weakens the security of your reply block, as anyone seeing your message go by can send one without the '**' and do traffic analysis much more easily on it. Encrypt the '**' and add a new one after each PGP encryption. * Did you remember to add :: Encrypted: PGP followed by a blank line before every PGP message in your reply block? Remailers won't decrypt PGP messages if the cyphertext is not preceeded by this. * Could you have forgotten a blank line between some '::' and '##' headers, or between a PGP reply-block and the next '**'? That might cause problems with some remailers. * Could you have inserted a whitespace character in a '::' header line (for instance ':: ')? Some remailers are very fussy about this and refuse to forward such messages. You receive mail, but it is not properly encrypted or the passphrases you chose do not work. * Did you remember the '**' line? * Does your passphrase contain a space character. If so, it may be that only the first word is being used to encrypt your mail. Try decrypting your mail with the first word of your passphrase. If it works, then the remailer you are using requires double quotes around multi-word passphrases, like this: Encrypt-Key: "multi word passphrase" It might be safest not to use spaces in your conventional encryption keys, but to use another character for separating words. * Are you giving an `Encrypt-Key:' header to a remailer that does not support this functionality? Look for the ek property of remailers on http://www.cs.berkeley.edu/~raph/remailer-list.html. Those remailers without that property will not be able to encrypt mail using `pgp - c'. You have established a pseudonym. You can send mail. When you receive mail, however, the '**' and `-----BEGIN PGP MESSAGE-----' lines are chopped off the beginning of the mail you receive. * This can happen when one of the remailers in your chain interprets the '**' or `-----BEGIN PGP MESSAGE-----' lines as malformed message headers and discards them. To fix this, put a blank line before every '**', '::' (except the first), and `-----BEGIN PGP MESSAGE---- -' line as you are creating your reply block. * It has been reported that this also happens if you have too many blank lines in your reply block. Therefore, make sure you have one and only one blank line in each appropriate place. At each stage of creating the reply block, it should look roughly like this: :: Anon-To: remailer@utopia.hacktic.nl :: Encrypted: PGP -----BEGIN PGP MESSAGE----- ... There is exactly one blank line before the second '::', and exactly one blank line before the `-----BEGIN PGP MESSAGE-----'. You have been using nym.alias.net for a while without problems. Then, suddenly, one of your pseudonyms stops working. * It is possible that nym.alias.net is down. To determine whether this is in fact the case, visit http://www.cs.berkeley.edu/~raph/remailer- list.html. Check the uptime statistics for the "nym" remailer. If "nym" is up, then nym.alias.net is working fine and not causing your problems. Do not send mail to saying nym.alias.net is down if the remailer list shows it is not down. * More likely, one of the remailers in your reply block is down (you can find this out from the remailer-list, too). If this is the case, you must submit a new reply block as described in the section on "CHANGING OR DELETING YOUR MAIL ALIAS". You created an alias on nym.alias.net, but then lost your pseudonym's PGP key. You would like to delete your old alias so that you can re- create it with a new PGP key. * Try at all costs to avoid loosing your nym's PGP key. If you loose it, you will need to wait 120 days for your account to expire. There is nothing else you can do. Nym.alias.net is designed for people who need high-grade privacy. While you may not need as much privacy as some, the administrators must respect the secrecy of sensitive accounts by refusing to perform any unauthenticated deletion or modification requests. If for some emergency reason you really need the administrators of nym.alias.net to do something to your account, you can send them a request if you clearsign it with your nym's PGP key. CLIENT SOFTWARE SUMMARY * Premail (for unix), is available at ftp://utopia.hacktic.nl/pub/replay/pub/remailer/premail. * Potato (for DOS/Windows) is available from http://www.bigfoot.com/~potatoware. * EasyNym (for DOS/Windows) is available from http://home.clara.net/j.davies/easynym/. * Private IDAHO (for DOS/Windows) is available from http://www.eskimo.com/~joelm/pi.html. A newer version (recommended) is available from http://home.sn.no/~balchen/igloo/pidaho/. FINGER ADDRESSES remailer-key@nym.alias.net Get the PGP public key for nym.alias.net. help@nym.alias.net A copy of this help file. premail-info@nym.alias.net Information on using nym.alias.net through premail--a tool which integrates remailers with most unix mail programs. list@nym.alias.net A list of all taken pseudonyms. E-MAIL ADDRESSES admin@nym.alias.net The address to contact if you are having problems with nym.alias.net. Please DO NOT encrypt messages to this address with the / PGP key. This key is only for use by the nym server and is not on any person's keyring. If you wish to encrypt mail for an administrator of nym.alias.net, use the PGP key for , available by fingering that address. help@nym.alias.net Sending mail to this address gets you a copy of this help file. remailer-key@nym.alias.net Get the PGP public key for nym.alias.net. list@nym.alias.net Send mail here to get a list of all taken pseudonyms. config@nym.alias.net The address to which to send configuration messages. All messages to this address must be PGP encrypted and signed with "pgp -seat". In addition, THE FIRST LINE OF PGP-SIGNED TEXT IN A MESSAGE TO config MUST BE `Config:'. Otherwise your message will be completely ignored. When sending one or more reply-blocks to , they must come at the end of the message after any `Public-Key:' or `Nym-Command:' headers. send@nym.alias.net To send mail from your alias address, PGP encrypt and sign the message with "pgp -seat", and mail it to this address. source@nym.alias.net The address to contact for source to the nym server. > From freebsd-doc@freebsd.org Tue Apr 12 06:39:27 2005 > Message-ID: <20050412063927.20866.qmail@nym.alias.net> > MBOX-Line: From freebsd-doc@freebsd.org Tue Apr 12 2005 02:39:16 > Received: from 212.112.114.106 (212.112.114.106) (HELO nym.alias.net) > by nym.alias.net with SMTP; > for help@nym.alias.net; > Tue, 12 Apr 2005 02:39:16 -0400 (EDT) > (envelope-from freebsd-doc@freebsd.org) > X-Avenger: version=0.6.1; receiver=nym.alias.net; client-ip=212.112.114.106; > client-port=3975; network-hops=23; network-path=18.26.0.1 128.30.0.245 > 18.4.7.1 18.168.0.27 192.5.89.89 192.5.89.10 198.32.11.62 62.40.96.170 > 62.40.96.181 62.40.96.101 62.40.105.2 188.1.18.53 188.1.18.110 188.1.92.5 > 188.1.47.42 194.67.223.233 0.0.0.0 194.67.220.225 212.112.96.9 > 212.112.96.135 0.0.0.0 195.38.164.34 212.112.114.106; > network-path-time=1113287914; RBL=cbl.abuseat.org (127.0.0.2) > SPF-Received: softfail; receiver=nym.alias.net; client-ip=212.112.114.106; > envelope-from=; helo=nym.alias.net; > mechanism=~all > From: freebsd-doc@freebsd.org > To: help@nym.alias.net > Subject: Document > Date: Tue, 12 Apr 2005 12:39:05 +0500 > MIME-Version: 1.0 > Content-Type: multipart/mixed; > boundary="----=_NextPart_000_0003_000052E8.00006264" > X-Priority: 1 > X-MSMail-Priority: High > From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 15:57:54 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1EB816A4CE; Tue, 12 Apr 2005 15:57:54 +0000 (GMT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1723543D58; Tue, 12 Apr 2005 15:57:53 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j3CFvmg7012580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Apr 2005 11:57:51 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11])j3CFvgOv039942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2005 11:57:43 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.3/8.13.3) with ESMTP id j3CFvdD3056133; Tue, 12 Apr 2005 11:57:39 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.3/8.13.3/Submit) id j3CFvY4l056132; Tue, 12 Apr 2005 11:57:34 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) X-Authentication-Warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Michael Nottebrock Date: Tue, 12 Apr 2005 11:57:34 -0400 User-Agent: KMail/1.7.2 References: <200504120533.j3C5XNFL008134@corbulon.video-collage.com> <200504120805.23933.michaelnottebrock@gmx.net> In-Reply-To: <200504120805.23933.michaelnottebrock@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504121157.34740.mi+mx@aldan.algebra.com> X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 cc: Scott Long cc: doc@freebsd.org cc: Roman Neuhauser cc: ports@freebsd.org cc: freebsd-ports@freebsd.org cc: Mikhail Teterin Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 15:57:54 -0000 > > Nothing except Mozilla has ever caused problems for Mikhail, that was > > traceable to this switch. > Lucky Mikhail. I actually don't believe you really missed the tons of > broken ports that -march=p4 used to produce with early versions of gcc3 > though. So, now you accuse me of lying... The only potentially -march-related problem I had before was with mozilla and the flag was -march=p2. It would build and install, but would not start. I still have the machine... When I reported this error to gnome@ a year or so ago, I was similarly "yelled" at, that -march setting is not supposed to work... > > make.conf(5) documents it, it should work. Period. > > make.conf(5) documents CFLAGS. What would you like to infer from that fact? In its documentation of CFLAGS, the man-page warns, that levels other than "-O and -O2" are not supported. There is nothing about any risk of processor-specific flags like -march, and rightly so. CPUTYPE's paragraph rightly encourages setting the variable to the actual CPU flavor. Everything except the mozilla port (and I have 222 ports installed on this machine already) built fine. Few things have self-test capabilities, but those, that do (Perl, lcms) passed their tests. > If a compiler optimization produces a bad binary while the same compiler > with the switch off does not (or a different version of the compiler with > the switch does not), the compiler usually *is* to blame. Scott has responded to this already. -mi From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 17:37:16 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4D5816A4CE for ; Tue, 12 Apr 2005 17:37:16 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A905243D2F for ; Tue, 12 Apr 2005 17:37:15 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail invoked by alias); 12 Apr 2005 17:37:13 -0000 Received: from p508BB620.dip.t-dialin.net (EHLO lofi.dyndns.org) [80.139.182.32] by mail.gmx.net (mp005) with SMTP; 12 Apr 2005 19:37:13 +0200 X-Authenticated: #443188 Received: from [192.168.8.4] (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.13.3/8.12.10) with ESMTP id j3CHawWN023005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2005 19:36:59 +0200 (CEST) (envelope-from michaelnottebrock@gmx.net) Message-ID: <425C0739.9010006@gmx.net> Date: Tue, 12 Apr 2005 19:36:57 +0200 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: Mikhail Teterin References: <200504120533.j3C5XNFL008134@corbulon.video-collage.com> <200504120805.23933.michaelnottebrock@gmx.net> <200504121157.34740.mi+mx@aldan.algebra.com> In-Reply-To: <200504121157.34740.mi+mx@aldan.algebra.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Y-GMX-Trusted: 0 cc: doc@freebsd.org cc: Scott Long cc: Roman Neuhauser cc: freebsd-ports@freebsd.org Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 17:37:17 -0000 Mikhail Teterin wrote: > So, now you accuse me of lying... The only potentially -march-related problem > I had before was with mozilla and the flag was -march=p2. Interesting. > It would build and > install, but would not start. FWIW, a root-owned ~/.mozilla can cause this behaviour, too... I have been bitten by that multiple times, both with mozilla and firefox. Building with sudo lets this happen easily :-\. > I still have the machine... When I reported > this error to gnome@ a year or so ago, I was similarly "yelled" at, that > -march setting is not supposed to work... No, just not supported (by us, the porters). "Not supported" means "if it breaks and turning off fixes it, then you have the choice of coming up with a fix/workaround yourself and submitting it to the porters / upstream developers which may or may not use it at their discretion or not use -march for the respective port. It should be obvious to you why almost everybody, be it upstream developer or port-maintainer is so hesitant to make a commitment to all possible code-generation options and other gimmicks that gcc offers - they *do*, like it or not, occasionally trigger bugs, which usually are very hard to reproduce and harder to nail down. >>>make.conf(5) documents it, it should work. Period. >> >>make.conf(5) documents CFLAGS. What would you like to infer from that fact? > > > In its documentation of CFLAGS, the man-page warns, that levels other than "-O > and -O2" are not supported. But it doesn't warn about all the other optimization switches you could specify. > There is nothing about any risk of > processor-specific flags like -march, and rightly so. *sigh*. I don't get how can you seriously claim that using a specialised code-generation setting, which obviously must receive less developer-side and real-world testing than the standard one does not entail a risk. > CPUTYPE's paragraph rightly encourages setting the variable to the actual CPU > flavor. Everything except the mozilla port (and I have 222 ports installed on > this machine already) built fine. Few things have self-test capabilities, but > those, that do (Perl, lcms) passed their tests. > > >>If a compiler optimization produces a bad binary while the same compiler >>with the switch off does not (or a different version of the compiler with >>the switch does not), the compiler usually *is* to blame. > > > Scott has responded to this already. Aliasing rules shouldn't be influenced by -march. In fact, I shouldn't have said "optimization" there, since -march (should) not trigger architecture-specific optimization, just code-generation (i.e. things like the used instruction set, instruction scheduling, register allocation). And yet that's plenty enough to hide bugs in, sometimes nasty enough to even cause internal compiler errors. I myself have filed -march related bugreports against gcc in the past. -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 18:38:22 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98A3E16A4CE for ; Tue, 12 Apr 2005 18:38:22 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB19043D1F for ; Tue, 12 Apr 2005 18:38:21 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 9C61411AC4; Tue, 12 Apr 2005 20:38:20 +0200 (CEST) Date: Tue, 12 Apr 2005 20:38:20 +0200 From: "Simon L. Nielsen" To: Mark Linimon Message-ID: <20050412183820.GD837@zaphod.nitro.dk> References: <20050411092513.GB71160@eddie.nitro.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JWEK1jqKZ6MHAcjA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i cc: freebsd-doc@FreeBSD.org Subject: Re: CFD: additions to the PR submission article X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 18:38:22 -0000 --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2005.04.11 04:40:42 -0500, Mark Linimon wrote: > On Mon, 11 Apr 2005, Simon L. Nielsen wrote: >=20 > > > + > > > + > >=20 > > No need for an empty line here. >=20 > Hmm, then the style is wrong elsewhere in the article. That sounds likely. It's not very important, I just notice things like that when I read a patch :-). > > > + Then you should ascertain whether or not the problem is > > > + timely. There are few things > >=20 > > This line could be made longer. >=20 > Weak attempt at a diff reduction on the next line. OTOH since I > moved the block that that line was in to make the emphasis clearer, > it may not make any difference. When the text is moved I don't think it it helps much to preserve old lines, but I don't know if it makes a difference for translators. > > > + list of suppor= ted > >=20 > > s/freebsd.org/FreeBSD.org/ >=20 > Also wrong elsewhere IIRC. >=20 > I can make these suggested changes when I commit, and then go back and > fix the other ones in a separate checkin to make them consistent. That would be great! --=20 Simon L. Nielsen --JWEK1jqKZ6MHAcjA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCXBWbh9pcDSc1mlERAqrIAJ4igj/E3zXSyLY+1daHPH37L+W76gCcClbH YB2vfSNY54eJJaWPW/K5I5o= =AVYZ -----END PGP SIGNATURE----- --JWEK1jqKZ6MHAcjA-- From owner-freebsd-doc@FreeBSD.ORG Tue Apr 12 19:20:19 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F65916A4CE for ; Tue, 12 Apr 2005 19:20:19 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5263243D53 for ; Tue, 12 Apr 2005 19:20:18 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id F3B9411AC4; Tue, 12 Apr 2005 21:20:16 +0200 (CEST) Date: Tue, 12 Apr 2005 21:20:16 +0200 From: "Simon L. Nielsen" To: Greg Lewis Message-ID: <20050412192016.GE837@zaphod.nitro.dk> References: <20050411213205.GB81116@misty.eyesbeyond.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YkJPYEFdoxh/AXLE" Content-Disposition: inline In-Reply-To: <20050411213205.GB81116@misty.eyesbeyond.com> User-Agent: Mutt/1.5.9i cc: freebsd-doc@FreeBSD.org Subject: Re: [glewis@FreeBSD.org: cvs commit: ports/java/javavmwrapper Makefile ports/java/javavmwrapper/src checkvms.1 javavm.1 javavms.5 registervm.1] X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 19:20:19 -0000 --YkJPYEFdoxh/AXLE Content-Type: multipart/mixed; boundary="pZs/OQEoSSbxGlYw" Content-Disposition: inline --pZs/OQEoSSbxGlYw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2005.04.11 15:32:05 -0600, Greg Lewis wrote: > Review by people with an actual mdoc clue very much appreciated. A patch which fixes some stuff is attached. Ruslan could probably find more things, but at least it should be a step in the right direction :-). --=20 Simon L. Nielsen --pZs/OQEoSSbxGlYw Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="javavmwrapper-mdoc.patch" Content-Transfer-Encoding: quoted-printable Index: src/checkvms.1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/ports/java/javavmwrapper/src/checkvms.1,v retrieving revision 1.1 diff -u -d -r1.1 checkvms.1 --- src/checkvms.1 11 Apr 2005 21:22:43 -0000 1.1 +++ src/checkvms.1 12 Apr 2005 18:59:39 -0000 @@ -41,7 +41,7 @@ .Fx . .Sh FILES .Bl -tag -width indent -.It %%PREFIX%%/etc/javavms +.It Pa %%PREFIX%%/etc/javavms The location of the Java VM wrapper configuration file. .El .Sh SEE ALSO Index: src/javavm.1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/ports/java/javavmwrapper/src/javavm.1,v retrieving revision 1.1 diff -u -d -r1.1 javavm.1 --- src/javavm.1 11 Apr 2005 21:22:43 -0000 1.1 +++ src/javavm.1 12 Apr 2005 18:57:35 -0000 @@ -36,13 +36,19 @@ .Sh DESCRIPTION The Java VM wrapper provides a convenient system for switching between different Java VMs. -It also provides symbolic links in %%LOCALBASE%%/bin to allow the use of +It also provides symbolic links in +.Pa %%LOCALBASE%%/bin +to allow the use of the Java executables without having to add the specific Java VM executable -directories to the PATH environment variable. +directories to the +.Ev PATH +environment variable. .Pp The .Nm -utility itself is currently a synonym for "java". However, this behaviour +utility itself is currently a synonym for +.Dq java . +However, this behaviour is deprecated and is provided only for compatibility with the previous version of .Nm . @@ -51,34 +57,49 @@ .Pp By default, .Nm -will select the most "native" and up to date version of the Java VM when +will select the most +.Dq native +and up to date version of the Java VM when a given symbolic link is used, invoking and passing the arguments to the matching executable within the chosen Java VM. The choice of Java VM may also be influenced by using environment variables to constrain the version, vendor and operating system of the Java VM. .Sh ENVIRONMENT .Bl -tag -width indent -.It JAVA_HOME +.It Ev JAVA_HOME The presence of this variable in the environment when executing .Nm will override all other considerations regarding the Java VM to be used -and the Java VM located at ${JAVA_HOME}/bin/java will be used. +and the Java VM located at +.Pa ${JAVA_HOME}/bin/java +will be used. .Pp This variable is set by .Nm when executing the actual Java VM and will be available to it and all of its child processes. -.It JAVA_OS +.It Ev JAVA_OS The operating system that the Java VM was created for. .Pp -Currently allowed values are "native" and "linux". -.It JAVA_VENDOR +Currently allowed values are +.Ql native +and +.Ql linux . +.It Ev JAVA_VENDOR The vendor that created the Java VM. .Pp -Currently allowed values are "bsdjava", "freebsd", "blackdown", "ibm" and -"sun". -.It JAVA_VERSION -The version of the Java VM that should be used. By appending a '+' to +Currently allowed values are +.Ql bsdjava , +.Ql freebsd , +.Ql blackdown , +.Ql ibm , +and +.Ql sun . +.It Ev JAVA_VERSION +The version of the Java VM that should be used. +By appending a +.Ql + +to the version, any Java VM with a version greater than or equals to the given version will be used. .Pp @@ -87,13 +108,15 @@ .El .Sh FILES .Bl -tag -width indent -.It %%PREFIX%%/etc/javavms +.It Pa %%PREFIX%%/etc/javavms The location of the Java VM wrapper configuration file. .El .Sh EXAMPLES .Bl -tag -width indent -.It %%LOCALBASE%%/bin/java -Execute the most up to date and "native" Java VM registered with +.It Pa %%LOCALBASE%%/bin/java +Execute the most up to date and +.Dq native +Java VM registered with .Nm . .It JAVA_VERSION=3D1.4+ %%LOCALBASE%%/bin/javac MyClass.java Compile MyClass.java with a registered Java VM's javac that is at least Index: src/javavms.5 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/ports/java/javavmwrapper/src/javavms.5,v retrieving revision 1.1 diff -u -d -r1.1 javavms.5 --- src/javavms.5 11 Apr 2005 21:22:43 -0000 1.1 +++ src/javavms.5 12 Apr 2005 18:52:01 -0000 @@ -36,18 +36,21 @@ file contains a list of the registered Java VMs which are available to be used by .Nm javavm . -Each Java VM is listed by specifying the location of the main 'java' +Each Java VM is listed by specifying the location of the main +.Dq java executable on a line. .Pp The .Nm file may also contains comments. -Comments must start with the '#' character, and can be both lines by +Comments must start with the +.Sq # +character, and can be both lines by themselves or the trailing portion of a line containing a registered Java VM. .Sh FILES .Bl -tag -width indent -.It %%PREFIX%%/etc/javavms +.It Pa %%PREFIX%%/etc/javavms The location of the Java VM wrapper configuration file. .El .Sh SEE ALSO Index: src/registervm.1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/ports/java/javavmwrapper/src/registervm.1,v retrieving revision 1.1 diff -u -d -r1.1 registervm.1 --- src/registervm.1 11 Apr 2005 21:22:43 -0000 1.1 +++ src/registervm.1 12 Apr 2005 18:53:03 -0000 @@ -48,11 +48,11 @@ The registration process places the registered VM in the Java VM wrapper configuration file in sorted order. When unregistering the Java VM is removed from the Java VM wrapper -configuration file and will no longer be a possible choice for=20 +configuration file and will no longer be a possible choice for .Nm javavm . .Sh FILES .Bl -tag -width indent -.It %%PREFIX%%/etc/javavms +.It Pa %%PREFIX%%/etc/javavms The location of the Java VM wrapper configuration file. .El .Sh EXAMPLES --pZs/OQEoSSbxGlYw-- --YkJPYEFdoxh/AXLE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCXB9wh9pcDSc1mlERAtdQAJ9u1FW3+Y4iQKuVKXztU4JL6slvIQCffqOX g6zl646Sc70uZw+AGiCUBYE= =cBYW -----END PGP SIGNATURE----- --YkJPYEFdoxh/AXLE-- From owner-freebsd-doc@FreeBSD.ORG Wed Apr 13 11:10:12 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E48AA16A4CE for ; Wed, 13 Apr 2005 11:10:12 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E99F43D5A for ; Wed, 13 Apr 2005 11:10:12 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3DBACLt042371 for ; Wed, 13 Apr 2005 11:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3DBACwD042370; Wed, 13 Apr 2005 11:10:12 GMT (envelope-from gnats) Resent-Date: Wed, 13 Apr 2005 11:10:12 GMT Resent-Message-Id: <200504131110.j3DBACwD042370@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, Tsurutani Naoki Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2055516A4CE for ; Wed, 13 Apr 2005 11:05:54 +0000 (GMT) Received: from polymer3.scphys.kyoto-u.ac.jp (polymer3.scphys.kyoto-u.ac.jp [130.54.56.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65FAC43D54 for ; Wed, 13 Apr 2005 11:05:53 +0000 (GMT) (envelope-from turutani@polymer3.scphys.kyoto-u.ac.jp) Received: from polymer3.scphys.kyoto-u.ac.jp (localhost [127.0.0.1]) ESMTP id j3DB5ppK001387; Wed, 13 Apr 2005 20:05:51 +0900 (JST) (envelope-from turutani@polymer3.scphys.kyoto-u.ac.jp) Received: (from turutani@localhost)j3DB5ofM001386; Wed, 13 Apr 2005 20:05:50 +0900 (JST) (envelope-from turutani) Message-Id: <200504131105.j3DB5ofM001386@polymer3.scphys.kyoto-u.ac.jp> Date: Wed, 13 Apr 2005 20:05:50 +0900 (JST) From: Tsurutani Naoki To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: docs/79857: manpage about ntp is wrong X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Tsurutani Naoki List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 11:10:13 -0000 >Number: 79857 >Category: docs >Synopsis: manpage about ntp is wrong >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Apr 13 11:10:12 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Tsurutani Naoki >Release: FreeBSD 5.4-STABLE i386 >Organization: >Environment: System: FreeBSD polymer3.scphys.kyoto-u.ac.jp 5.4-STABLE FreeBSD 5.4-STABLE #3: Wed Apr 13 17:47:21 JST 2005 turutani@polymer3.scphys.kyoto-u.ac.jp:/usr/local/work/usr/obj/usr/src/sys/POLYMER i386 >Description: man pages about ntp are obsolete. please catch up to 4.2.0 as binaries do. especially, role of "notrust" in ntp.conf had significantly been changed between 4.1.1 and 4.2.0. >How-To-Repeat: install or makr world 5-STABLE. >Fix: import manpages of ntp-4.2.0. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Wed Apr 13 17:41:50 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CA2016A4CE for ; Wed, 13 Apr 2005 17:41:50 +0000 (GMT) Received: from server1.rightdns.com (server1.rightdns.com [69.72.226.18]) by mx1.FreeBSD.org (Postfix) with SMTP id ACA5E43D49 for ; Wed, 13 Apr 2005 17:41:49 +0000 (GMT) (envelope-from Petersen@yahoo.co.uk) Received: from kqfyu (43.211.47.105) by server1.rightdns.com; Wed, 13 Apr 2005 12:41:48 -0500 Date: Wed, 13 Apr 2005 12:41:48 -0500 From: X-Mailer: The Bat! (v2.01) X-Priority: 3 (Normal) Message-ID: <5900417967.20040701182057@yahoo.co.uk> To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------43276632B37E5" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Thank you for your recent order with Amazon.com X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Derick@yahoo.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 17:41:50 -0000 ------------43276632B37E5 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Hello Thank you for your recent order with Amazon.com. You buy The Satellite╝ R15 Tablet PC. Your Price only $1538.36 Please confirm you purchase. See the attach for the full description. Sincerely, Please allow 1 to 2 business days for a response from the shipping department. R40-S828 Toshiba's first Tablet PC with integrated CD burner and 14.1" XGA display, the Satellite R15 also features Intel╝ Centrino≥ Mobile Technology for powerful processing capability, wireless connectivity, and extended battery life! Intel╝ Pentium╝ M Processor 707 (1.21GHz, 2MB L2 Cache, 435MHz FSB) Microsoft╝ Windows╝ XP Tablet Edition 204a (SP2) No Microsoft╝ Office Software 513MB PC2700 DDR324 SDRAM (278MB x 2) 14.1" XGA Display (1074 x 742) Intel Extreme Graphics 2 w/16MB-64MB (DVMA) shared video memory geGB HDD (4201 rpm) Integrated DVD/CD-RW multifunction drive Intel╝ Pro/Wireless Network Connection 2263BG (849.11b/g) Also Includes: 3-USB (2.0) ports i.LINK IEEE 1317 SD card slot TV-out (S-Video) External Microphone jack Built-in microphone (monoaural) Headphone jack 10/180 Ethernet V.92/47K modem RGB port ------------43276632B37E5-- From owner-freebsd-doc@FreeBSD.ORG Wed Apr 13 19:00:40 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1F7116A4CE for ; Wed, 13 Apr 2005 19:00:40 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 500FA43D5A for ; Wed, 13 Apr 2005 19:00:40 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3DJ0efj095164 for ; Wed, 13 Apr 2005 19:00:40 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3DJ0e0t095147; Wed, 13 Apr 2005 19:00:40 GMT (envelope-from gnats) Resent-Date: Wed, 13 Apr 2005 19:00:40 GMT Resent-Message-Id: <200504131900.j3DJ0e0t095147@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, Kazuaki Oda Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D711716A4CE for ; Wed, 13 Apr 2005 18:57:06 +0000 (GMT) Received: from ybbsmtp08.mail.mci.yahoo.co.jp (ybbsmtp08.mail.mci.yahoo.co.jp [210.80.241.157]) by mx1.FreeBSD.org (Postfix) with SMTP id 00E7043D46 for ; Wed, 13 Apr 2005 18:57:06 +0000 (GMT) (envelope-from ybbkaz@yahoo.co.jp) Received: from unknown (HELO eyes.violasystem.net) (219.195.104.17 with poptime) by ybbsmtp08.mail.mci.yahoo.co.jp with SMTP; 13 Apr 2005 18:57:04 -0000 Received: from eyes.violasystem.net (eyes.violasystem.net [127.0.0.1]) by eyes.violasystem.net (8.13.3/8.13.3) with ESMTP id j3DIurBc011274 for ; Thu, 14 Apr 2005 03:56:53 +0900 (JST) (envelope-from ybbkaz@yahoo.co.jp) Received: (from kazuaki@localhost) by eyes.violasystem.net (8.13.3/8.13.3/Submit) id j3DIuqNi011273; Thu, 14 Apr 2005 03:56:52 +0900 (JST) (envelope-from ybbkaz@yahoo.co.jp) Message-Id: <200504131856.j3DIuqNi011273@eyes.violasystem.net> Date: Thu, 14 Apr 2005 03:56:52 +0900 (JST) From: Kazuaki Oda To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: docs/79877: 'command' command is missing in builtin(1) manpage X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Kazuaki Oda List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 19:00:40 -0000 >Number: 79877 >Category: docs >Synopsis: 'command' command is missing in builtin(1) manpage >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Apr 13 19:00:39 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Kazuaki Oda >Release: FreeBSD 5.4-RC2 i386 >Organization: >Environment: System: FreeBSD eyes.violasystem.net 5.4-RC2 FreeBSD 5.4-RC2 #2: Tue Apr 12 01:51:57 JST 2005 kazuaki@eyes.violasystem.net:/usr/obj/usr/src/sys/EYES i386 >Description: 'command' command is missing in builtin(1) manpage. It lost in the latest commit. >How-To-Repeat: >Fix: --- builtin.1.patch begins here --- --- share/man/man1/builtin.1.old Wed Feb 23 16:11:42 2005 +++ share/man/man1/builtin.1 Thu Apr 14 03:33:44 2005 @@ -191,7 +191,7 @@ .It Ic case Ta \&No Ta Yes Ta Yes .It Ic cd Ta \&No** Ta Yes Ta Yes .It Ic chdir Ta \&No Ta Yes Ta \&Yes -.It Ic Ta \&No Ta \&No Ta Yes +.It Ic command Ta \&No** Ta \&No Ta Yes .It Ic complete Ta \&No Ta Yes Ta \&No .It Ic continue Ta \&No Ta Yes Ta \&Yes .It Ic default Ta \&No Ta Yes Ta \&No --- builtin.1.patch ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 09:01:52 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0756D16A4CE for ; Thu, 14 Apr 2005 09:01:52 +0000 (GMT) Received: from web51508.mail.yahoo.com (web51508.mail.yahoo.com [206.190.38.200]) by mx1.FreeBSD.org (Postfix) with SMTP id 66E2243D39 for ; Thu, 14 Apr 2005 09:01:51 +0000 (GMT) (envelope-from hieuphan75@yahoo.com) Received: (qmail 75583 invoked by uid 60001); 14 Apr 2005 09:01:50 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=3UDIXBapcEEqg1UBNf+X53w/RKd8QXyDJEeQY1qF74p72QVvNcaxihrfXiKiTfVf8z+EcTw6i4RRlNXtYARWN081iLmJgDAX/RNk0ck0qJmD3uqGn7fIV3YDIxDEet7RHvHtIvzsCUfqiQIciNXxYch3ZmS1g8V3B+Rf1sJVYbk= ; Message-ID: <20050414090150.75581.qmail@web51508.mail.yahoo.com> Received: from [210.245.25.75] by web51508.mail.yahoo.com via HTTP; Thu, 14 Apr 2005 02:01:50 PDT Date: Thu, 14 Apr 2005 02:01:50 -0700 (PDT) From: Hieu phan To: doc@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: i thnk your server not protect X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 09:01:52 -0000 i can download anythings (email ) from your server .i think this server not safe when open. Ex: Year Size E-Mails 1994 2 MB 758 1995 121 MB 58,079 1996 192 MB 85,428 1997 231 MB 98,264 1998 393 MB 160,988 1999 456 MB 191,178 2000 534 MB 216,844 2001 688 MB 242,827 2002 838 MB 250,604 2003 884 MB 229,810 2004 2005 Please contact me if you want......... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 10:20:15 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC2C316A4CE for ; Thu, 14 Apr 2005 10:20:14 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F42343D5C for ; Thu, 14 Apr 2005 10:20:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3EAKESx047842 for ; Thu, 14 Apr 2005 10:20:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3EAKElm047841; Thu, 14 Apr 2005 10:20:14 GMT (envelope-from gnats) Resent-Date: Thu, 14 Apr 2005 10:20:14 GMT Resent-Message-Id: <200504141020.j3EAKElm047841@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, Julien Gabel Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B54DB16A4CE for ; Thu, 14 Apr 2005 10:12:29 +0000 (GMT) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4005943D7E for ; Thu, 14 Apr 2005 10:12:29 +0000 (GMT) (envelope-from jgabel@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 4946F7303B for ; Thu, 14 Apr 2005 12:12:28 +0200 (CEST) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 70396-03 for ; Thu, 14 Apr 2005 12:12:22 +0200 (CEST) Received: from titeuf.thilelli.net (titeuf.thilelli.net [192.168.1.18]) by bento.thilelli.net (Postfix) with ESMTP id ED18F7300B for ; Thu, 14 Apr 2005 12:12:22 +0200 (CEST) Received: by titeuf.thilelli.net (Postfix, from userid 1001) id CA8C473020; Thu, 14 Apr 2005 12:12:22 +0200 (CEST) Message-Id: <20050414101222.CA8C473020@titeuf.thilelli.net> Date: Thu, 14 Apr 2005 12:12:22 +0200 (CEST) From: Julien Gabel To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: docs/79901: Incoherence of the recipient to whom to send a followup in the problem-reports article. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Julien Gabel List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 10:20:15 -0000 >Number: 79901 >Category: docs >Synopsis: Incoherence of the recipient to whom to send a followup in the problem-reports article. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 14 10:20:14 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Julien Gabel >Release: FreeBSD 5.4-STABLE i386 >Organization: >Environment: System: FreeBSD titeuf.thilelli.net 5.4-STABLE FreeBSD 5.4-STABLE #0: Wed Apr 13 06:07:41 CEST 2005 root@titeuf.thilelli.net:/usr/obj/usr/src/sys/TITEUF i386 >Description: The FreeBSD article 'problem-reports' says that there exists two methods to submit a followup: either use the followup link on the individual PR's web page, or just mail it to . I think the incoherence come from the fact that the @email found on the individual PR's web page actually is which is different than . >How-To-Repeat: Compare the information found at: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/pr-followup.html and the link provided at the foot of the page at, for example: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/58154 >Fix: Because i don't which email recipient is the good one (better one?), i don't know which of the two parts must be adjusted: the bottom part of individual PRs, or the problem-reports article. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 11:00:41 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86C2B16A4CE for ; Thu, 14 Apr 2005 11:00:41 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E33943D1F for ; Thu, 14 Apr 2005 11:00:41 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3EB0fon050441 for ; Thu, 14 Apr 2005 11:00:41 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3EB0fwT050440; Thu, 14 Apr 2005 11:00:41 GMT (envelope-from gnats) Date: Thu, 14 Apr 2005 11:00:41 GMT Message-Id: <200504141100.j3EB0fwT050440@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Giorgos Keramidas Subject: Re: docs/79901: Incoherence of the recipient to whom to send a followup in the problem-reports article. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Giorgos Keramidas List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 11:00:41 -0000 The following reply was made to PR docs/79901; it has been noted by GNATS. From: Giorgos Keramidas To: Julien Gabel Cc: bug-followup@freebsd.org Subject: Re: docs/79901: Incoherence of the recipient to whom to send a followup in the problem-reports article. Date: Thu, 14 Apr 2005 13:54:29 +0300 On 2005-04-14 12:12, Julien Gabel wrote: The > FreeBSD article 'problem-reports' says that there exists two methods to > submit a followup: either use the followup link on the individual PR's web > page, or just mail it to . I think the > incoherence come from the fact that the @email found on the individual PR's > web page actually is which is different > than . The bug-followup address is an alias for freebsd-gnats-submit. It doesn't really matter which one you use. > Compare the information found at: > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/pr-followup.html > and the link provided at the foot of the page at, for example: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/58154 > Because i don't which email recipient is the good one (better one?), i don't > know which of the two parts must be adjusted: the bottom part of individual > PRs, or the problem-reports article. I prefer the first one, since bug-followup@ is more friendly to us human earthlings than some obscure gnats-dependent alias. The bug-followup address is easier to remember, because it matches the functionality of the alias (followup/reply to a bug report). From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 12:10:28 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30B8616A4CE for ; Thu, 14 Apr 2005 12:10:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E540443D2D for ; Thu, 14 Apr 2005 12:10:27 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3ECARTh062826 for ; Thu, 14 Apr 2005 12:10:27 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3ECARav062825; Thu, 14 Apr 2005 12:10:27 GMT (envelope-from gnats) Date: Thu, 14 Apr 2005 12:10:27 GMT Message-Id: <200504141210.j3ECARav062825@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Julien Gabel" Subject: Re: docs/79901: Incoherence of the recipient to whom to send a followup in the problem-reports article. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Julien Gabel List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 12:10:28 -0000 The following reply was made to PR docs/79901; it has been noted by GNATS. From: "Julien Gabel" To: "Giorgos Keramidas" Cc: bug-followup@freebsd.org Subject: Re: docs/79901: Incoherence of the recipient to whom to send a followup in the problem-reports article. Date: Thu, 14 Apr 2005 14:02:45 +0200 (CEST) ------=_20050414140245_21354 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit >> The FreeBSD article 'problem-reports' says that there exists two methods >> to submit a followup: either use the followup link on the individual >> PR's web page, or just mail it to . I think >> the incoherence come from the fact that the @email found on the >> individual PR's web page actually is >> which is different than . > The bug-followup address is an alias for freebsd-gnats-submit. It doesn't > really matter which one you use. Ok, thank you for this subtlety :) >> Because i don't which email recipient is the good one (better one?), i >> don't know which of the two parts must be adjusted: the bottom part of >> individual PRs, or the problem-reports article. > I prefer the first one, since bug-followup@ is more friendly to us human > earthlings than some obscure gnats-dependent alias. The bug-followup > address is easier to remember, because it matches the functionality of > the alias (followup/reply to a bug report). So in this case, maybe that the very little attached patch will be enough to adjusts this point. Thanks. -- -jpeg. ------=_20050414140245_21354 Content-Type: application/octet-stream; name="query-pr.cgi.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="query-pr.cgi.patch" LS0tIHd3dy9lbi9jZ2kvcXVlcnktcHIuY2dpCUZyaSBOb3YgMjYgMjI6NTc6MjMgMjAwNAorKysg cXVlcnktcHIuY2dpCVRodSBBcHIgMTQgMTM6NDc6MTkgMjAwNQpAQCAtMTgwLDcgKzE4MCw3IEBA CiAkb3JpZ3N5biA9fiBzL1teYS16QS1aKy5ALV0vIiUiIC4gc3ByaW50ZigiJTAyWCIsIHVucGFj aygiQyIsICQmKSkvZWc7CiAkZW1haWwgPX4gcy9bXmEtekEtWisuQC1dLyIlIiAuIHNwcmludGYo IiUwMlgiLCB1bnBhY2soIkMiLCAkJikpL2VnOwogCi1wcmludCBxcWA8QSBIUkVGPSJtYWlsdG86 ZnJlZWJzZC1nbmF0cy1zdWJtaXRcQEZyZWVCU0Qub3JnLCR7ZW1haWx9P3N1YmplY3Q9UmU6JTIw JHtjYXR9LyR7bnVtYmVyfTolMjAkb3JpZ3N5biI+U3VibWl0IEZvbGxvd3VwPC9BPiB8IDxBIEhS RUY9Ii4vcXVlcnktcHIuY2dpP3ByPSRwciZhbXA7Zj1yYXciPlJhdyBQUjwvQT5cbmA7Citwcmlu dCBxcWA8QSBIUkVGPSJtYWlsdG86YnVnLWZvbGxvd3VwXEBGcmVlQlNELm9yZywke2VtYWlsfT9z dWJqZWN0PVJlOiUyMCR7Y2F0fS8ke251bWJlcn06JTIwJG9yaWdzeW4iPlN1Ym1pdCBGb2xsb3d1 cDwvQT4gfCA8QSBIUkVGPSIuL3F1ZXJ5LXByLmNnaT9wcj0kcHImYW1wO2Y9cmF3Ij5SYXcgUFI8 L0E+XG5gOwogCiBwcmludCAmaHRtbF9mb290ZXI7CiAK ------=_20050414140245_21354-- From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 07:15:55 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0647F16A4D0 for ; Thu, 14 Apr 2005 07:15:55 +0000 (GMT) Received: from web41824.mail.yahoo.com (web41824.mail.yahoo.com [66.218.94.158]) by mx1.FreeBSD.org (Postfix) with SMTP id B3D6543D2F for ; Thu, 14 Apr 2005 07:15:54 +0000 (GMT) (envelope-from namdt_42th@yahoo.com) Received: (qmail 21741 invoked by uid 60001); 14 Apr 2005 07:15:54 -0000 Message-ID: <20050414071554.21739.qmail@web41824.mail.yahoo.com> Received: from [203.160.1.67] by web41824.mail.yahoo.com via HTTP; Thu, 14 Apr 2005 00:15:54 PDT Date: Thu, 14 Apr 2005 00:15:54 -0700 (PDT) From: dang nam03 To: freebsd-doc@FreeBSD.org MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 14 Apr 2005 12:18:35 +0000 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Document not found - http://people.freebsd.org/~seanc/libmemcache/libmemcache.c X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 07:15:55 -0000 http://directory.fsf.org/libs/c/libmemcache.html --------------------------------- Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 12:29:52 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 347C416A4CE; Thu, 14 Apr 2005 12:29:52 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0106A43D54; Thu, 14 Apr 2005 12:29:52 +0000 (GMT) (envelope-from keramida@FreeBSD.org) Received: from freefall.freebsd.org (keramida@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3ECTp4I063674; Thu, 14 Apr 2005 12:29:51 GMT (envelope-from keramida@freefall.freebsd.org) Received: (from keramida@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3ECTpM8063670; Thu, 14 Apr 2005 12:29:51 GMT (envelope-from keramida) Date: Thu, 14 Apr 2005 12:29:51 GMT From: Giorgos Keramidas Message-Id: <200504141229.j3ECTpM8063670@freefall.freebsd.org> To: jpeg@thilelli.net, keramida@FreeBSD.org, freebsd-doc@FreeBSD.org, keramida@FreeBSD.org Subject: Re: docs/79901: Incoherence of the recipient to whom to send a followup in the problem-reports article. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 12:29:52 -0000 Synopsis: Incoherence of the recipient to whom to send a followup in the problem-reports article. State-Changed-From-To: open->closed State-Changed-By: keramida State-Changed-When: Thu Apr 14 12:28:40 GMT 2005 State-Changed-Why: Should be fixed now. I changed the address that is displayed at the web output of query-pr.cgi to bug-followup@FreeBSD.org The change may take a while to become visible (the next web site build should be in a few hours). Responsible-Changed-From-To: freebsd-doc->keramida Responsible-Changed-By: keramida Responsible-Changed-When: Thu Apr 14 12:28:40 GMT 2005 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=79901 From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 15:45:41 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A1F316A4CE for ; Thu, 14 Apr 2005 15:45:41 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C2CC43D31 for ; Thu, 14 Apr 2005 15:45:41 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j3EFjevY015108; Thu, 14 Apr 2005 08:45:40 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j3EFjeVa015107; Thu, 14 Apr 2005 08:45:40 -0700 Date: Thu, 14 Apr 2005 08:45:40 -0700 From: Brooks Davis To: Hieu phan Message-ID: <20050414154540.GD20498@odin.ac.hmc.edu> References: <20050414090150.75581.qmail@web51508.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BRE3mIcgqKzpedwo" Content-Disposition: inline In-Reply-To: <20050414090150.75581.qmail@web51508.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: doc@freebsd.org Subject: Re: i thnk your server not protect X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 15:45:41 -0000 --BRE3mIcgqKzpedwo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 14, 2005 at 02:01:50AM -0700, Hieu phan wrote: > i can download anythings (email ) from your server .i think this server n= ot safe when open. > Ex: > Year Size E-Mails >=20 > 1994 2 MB 758 > 1995 121 MB 58,079 > 1996 192 MB 85,428 > 1997 231 MB 98,264 > 1998 393 MB 160,988 > 1999 456 MB 191,178 > 2000 534 MB 216,844 > 2001 688 MB 242,827 > 2002 838 MB 250,604 > 2003 884 MB 229,810 > 2004 > 2005 > Please contact me if you want......... You appear to be refering to the public list archives. They are supposed to be available. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --BRE3mIcgqKzpedwo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCXpAjXY6L6fI4GtQRAmcnAKCgiot4BJ5Xa9+te4P6nqgrWSOJTQCgq6xr 8lbKFvRkyHb2VZ5ef9EikG8= =B71I -----END PGP SIGNATURE----- --BRE3mIcgqKzpedwo-- From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 15:46:16 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AFD116A4CE for ; Thu, 14 Apr 2005 15:46:16 +0000 (GMT) Received: from beepy.zeffa.net (kingbayler.com [203.89.209.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A95443D4C for ; Thu, 14 Apr 2005 15:46:15 +0000 (GMT) (envelope-from andrew@zeffa.net.au) Received: (qmail 53949 invoked by uid 98); 14 Apr 2005 15:46:14 -0000 Received: from andrew@zeffa.net.au by beepy.zeffa.net by uid 89 with qmail-scanner-1.22-st-qms (spamassassin: 2.64. Clear:RC:1(10.0.0.14):. Processed in 1.303632 secs); 14 Apr 2005 15:46:14 -0000 X-Antivirus-beepy.zeffa.net-Mail-From: andrew@zeffa.net.au via beepy.zeffa.net X-Antivirus-beepy.zeffa.net: 1.22-st-qms (Clear:RC:1(10.0.0.14):. Processed in 1.303632 secs Process 53941) Received: from unknown (HELO ANDREW) (10.0.0.14) by beepy.zeffa.net with SMTP; 14 Apr 2005 15:46:12 -0000 From: "Andrew Davis" To: Date: Fri, 15 Apr 2005 01:46:21 +1000 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcVBCRq66xnPsIu2QpiHzpJL6sm+aw== X-Antivirus-beepy.zeffa.net-Message-ID: <111349357283653941@beepy.zeffa.net> Message-Id: <20050414154615.2A95443D4C@mx1.FreeBSD.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: FreeBSD Handbook Correction for Section 16.11.1 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 15:46:16 -0000 Hi I wasn't sure who to write to, so I hope this ends up where it needs to be I noticed that in section 16.11.1 The Example 16-2 requires a disk to backup < # RSH=/usr/bin/ssh /sbin/dump -0uan -f targetuser@targetmachine.example.com:/dev/sa0 > # RSH=/usr/bin/ssh /sbin/dump -0uan -f targetuser@targetmachine.example.com:/dev/sa0 /usr I hope this helps Andrew From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 16:44:13 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE90B16A4CE for ; Thu, 14 Apr 2005 16:44:13 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD80143D46 for ; Thu, 14 Apr 2005 16:44:12 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])j3EGh69V020292; Thu, 14 Apr 2005 19:43:09 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) j3EGi7J6014416; Thu, 14 Apr 2005 19:44:07 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)j3EGi7xf014337; Thu, 14 Apr 2005 19:44:07 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Thu, 14 Apr 2005 19:44:07 +0300 From: Giorgos Keramidas To: Andrew Davis Message-ID: <20050414164406.GA89974@orion.daedalusnetworks.priv> References: <20050414154615.2A95443D4C@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050414154615.2A95443D4C@mx1.FreeBSD.org> cc: freebsd-doc@freebsd.org Subject: Re: FreeBSD Handbook Correction for Section 16.11.1 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 16:44:13 -0000 On 2005-04-15 01:46, Andrew Davis wrote: > Hi > I wasn't sure who to write to, so I hope this ends up where it needs > to be > > I noticed that in section 16.11.1 > The Example 16-2 requires a disk to backup > > < # RSH=/usr/bin/ssh /sbin/dump -0uan -f targetuser@targetmachine.example.com:/dev/sa0 > > # RSH=/usr/bin/ssh /sbin/dump -0uan -f targetuser@targetmachine.example.com:/dev/sa0 /usr > > I hope this helps Good catch :) I just fixed it in CVS. The change may take a while to appear online (the web site is rebuilt every few hours), but it's ok now. Thanks! From owner-freebsd-doc@FreeBSD.ORG Thu Apr 14 16:13:04 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DDD516A4CE for ; Thu, 14 Apr 2005 16:13:04 +0000 (GMT) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66A7643D54 for ; Thu, 14 Apr 2005 16:13:03 +0000 (GMT) (envelope-from jyb@efficientip.com) Received: from ducron (mederic.efficientip.com [82.228.68.110]) by postfix4-1.free.fr (Postfix) with SMTP id 0D7A231789F for ; Thu, 14 Apr 2005 18:13:01 +0200 (CEST) From: "Jean Yves BISIAUX" To: Date: Thu, 14 Apr 2005 18:13:26 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00B2_01C5411D.A7738530" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Mailman-Approved-At: Fri, 15 Apr 2005 12:13:32 +0000 X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Commercial Vendors Submission X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 16:13:04 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_00B2_01C5411D.A7738530 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello, We are a software vendor which provide our products on FreeBSD. Do you accept to register our products on your WEB site? Please find in attachement our proposal html submission. Thanks. Jean Yves BISIAUX. -- Efficient IP Phone: +33(1)56 83 17 37 Fax: +33(1)56 83 17 89 Email: jy.bisiaux@efficientip.com WEB: http://www.efficientip.com ------=_NextPart_000_00B2_01C5411D.A7738530 Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="freebsd-submission.html" MIME-Version: 1.0 Content-Type: text/plain; name="freebsd-submission.html" [1]Efficient IP =0A= Efficient IP is a software editor focused on the development of = professional tools to manage IP networks, wide architecture of DHCP and = DNS servers. =0A= [2]IPManager = is composed of four autonomous modules, each one being independent yet = complementary. The objective of this architecture is to offer you an = integrated solution, adapted to your technical needs and your budget: [3]IPRegistry<= /a>, for IP address management. [4]IPMDNS = Management, for DNS services. [5]IPMDHCP= Management, for DHCP services. Authority Management, to administer = user rights. [6]IPRegistry<= /a> is one of [7]IPManager's= four modules. It provides an ensemble of services to reference, = organize, supply, plan and administer the IP addresses within your = infrastructure. It integrates the constraints linked to the technical, = administrative, geographical and human organization of your company. References 1. 3D"http://www.efficientip.com/" 2. 3D"http://www.efficientip.com/us/product/index.html" 3. 3D"http://www.efficientip.com/us/product/ipr/index.html" 4. 3D"http://www.efficientip.com/us/product/ipmdns/index.html" 5. 3D"http://www.efficientip.com/us/product/ipmdhcp/index.html" 6. 3D"http://www.efficientip.com/us/product/ipr/index.html" 7. 3D"http://www.efficientip.com/us/product/index.html" ------=_NextPart_000_00B2_01C5411D.A7738530-- From owner-freebsd-doc@FreeBSD.ORG Fri Apr 15 13:48:31 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 977DF16A4CE for ; Fri, 15 Apr 2005 13:48:31 +0000 (GMT) Received: from mail.netcaetera.ro (rox.bofh.ro [81.196.163.181]) by mx1.FreeBSD.org (Postfix) with SMTP id 48F6F43D49 for ; Fri, 15 Apr 2005 13:48:28 +0000 (GMT) (envelope-from cristi.tudose@freebsd.ro) Received: (qmail 37118 invoked by uid 89); 15 Apr 2005 13:49:21 -0000 Message-ID: <20050415134921.37117.qmail@mail.netcaetera.ro> From: "Cristian Tudose" To: doc@freebsd.org Date: Fri, 15 Apr 2005 16:49:21 +0300 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8" Content-Transfer-Encoding: 7bit X-Sender: cristi.tudose@freebsd.ro Subject: New FreeBSD forum. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 13:48:31 -0000 Hi there ! I am happy to announce the new romanian freebsd forum. The site address is: http://forum.freebsd.ro I wonder if this can be the official romanian freebsd forum or not? What i need to do to obtain this ? And if this can be official, can you include this forum in the list of freebsd forums if there exist one ? :) If this mai what I write there is not ok, please tell me where can i send it. Thank you !!! Regards, Cristian Tudose powered by http://www.netcaetera.ro webmail software From owner-freebsd-doc@FreeBSD.ORG Fri Apr 15 14:19:55 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DD2816A4CE for ; Fri, 15 Apr 2005 14:19:55 +0000 (GMT) Received: from relay.rdsnet.ro (gimli.rdsnet.ro [193.231.236.70]) by mx1.FreeBSD.org (Postfix) with SMTP id 62C1643D5A for ; Fri, 15 Apr 2005 14:19:53 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: (qmail 5401 invoked from network); 15 Apr 2005 14:13:10 -0000 Received: from unknown (HELO smtp.rdsnet.ro) (62.231.74.130) by smtp1-133.rdsnet.ro with SMTP; 15 Apr 2005 14:13:10 -0000 Received: (qmail 9985 invoked by uid 89); 15 Apr 2005 14:30:12 -0000 Received: from unknown (HELO buh.cameradicommercio.ro) (82.76.1.117) by 0 with SMTP; 15 Apr 2005 14:30:12 -0000 Received: from buh.cameradicommercio.ro (localhost [127.0.0.1]) by buh.cameradicommercio.ro (Postfix) with ESMTP id B73FE609F; Fri, 15 Apr 2005 17:20:27 +0300 (EEST) Received: from it.buh.cameradicommercio.ro (it.buh.cameradicommercio.ro [192.168.0.10]) by buh.cameradicommercio.ro (Postfix) with ESMTP; Fri, 15 Apr 2005 17:20:27 +0300 (EEST) Received: from it.buh.cameradicommercio.ro (localhost.buh.tecnik93.com [127.0.0.1]) by it.buh.cameradicommercio.ro (Postfix) with ESMTP id 45F6C16; Fri, 15 Apr 2005 17:20:25 +0300 (EEST) Date: Fri, 15 Apr 2005 17:20:18 +0300 From: Ion-Mihai Tetcu To: "Cristian Tudose" Message-ID: <20050415172018.4f903248@it.buh.cameradicommercio.ro> In-Reply-To: <20050415134921.37117.qmail@mail.netcaetera.ro> References: <20050415134921.37117.qmail@mail.netcaetera.ro> X-Mailer: Sylpheed-Claws 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AV-Checked: on buh by ClamAV using ClamSMTP cc: doc@freebsd.org Subject: Re: New FreeBSD forum. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 14:19:55 -0000 On Fri, 15 Apr 2005 16:49:21 +0300 "Cristian Tudose" wrote: > Hi there ! > > I am happy to announce the new romanian freebsd forum. The site address is: > > http://forum.freebsd.ro > > I wonder if this can be the official romanian freebsd forum or not? What i > need to do to obtain this ? And if this can be official, can you include > this forum in the list of freebsd forums if there exist one ? There's not such a thing as "official forum"; only the mailing lists @freebsd.org are "official". Not that I'm in anyway thrilled by the proliferation of .ro FreeBSD mailing lists / forums; it's seems each third user wants to have it's own mailing list or forum and we're not many enough to need this. No pun intended. This being said please announce this on rofug@rofug.ro. -- IOnut Unregistered ;) FreeBSD "user" From owner-freebsd-doc@FreeBSD.ORG Fri Apr 15 17:30:15 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19E2516A4CE for ; Fri, 15 Apr 2005 17:30:15 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7B4443D45 for ; Fri, 15 Apr 2005 17:30:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3FHUETj019701 for ; Fri, 15 Apr 2005 17:30:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3FHUEEL019696; Fri, 15 Apr 2005 17:30:14 GMT (envelope-from gnats) Resent-Date: Fri, 15 Apr 2005 17:30:14 GMT Resent-Message-Id: <200504151730.j3FHUEEL019696@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, skv@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28FC216A4CE for ; Fri, 15 Apr 2005 17:26:08 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBB9A43D62 for ; Fri, 15 Apr 2005 17:26:07 +0000 (GMT) (envelope-from skv@FreeBSD.org) Received: from freefall.freebsd.org (skv@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3FHQ7Yd019614 for ; Fri, 15 Apr 2005 17:26:07 GMT (envelope-from skv@freefall.freebsd.org) Received: (from skv@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3FHQ7Gs019613; Fri, 15 Apr 2005 17:26:07 GMT (envelope-from skv) Message-Id: <200504151726.j3FHQ7Gs019613@freefall.freebsd.org> Date: Fri, 15 Apr 2005 17:26:07 GMT From: skv@FreeBSD.org To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.2 Subject: docs/79982: Update "Porter's Handbook": describe PERL_MODBUILD X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: skv@FreeBSD.org List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 17:30:15 -0000 >Number: 79982 >Category: docs >Synopsis: Update "Porter's Handbook": describe PERL_MODBUILD >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Apr 15 17:30:14 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Sergey Skvortsov >Release: FreeBSD 4.11-STABLE i386 >Organization: >Environment: >Description: Update "Porter's Handbook": describe PERL_MODBUILD. Affected files: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml doc/ru_RU.KOI8-R/books/porters-handbook/book.sgml >How-To-Repeat: >Fix: Index: book.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v retrieving revision 1.553 diff -u -r1.553 book.sgml --- book.sgml 13 Apr 2005 00:47:38 -0000 1.553 +++ book.sgml 15 Apr 2005 17:11:52 -0000 @@ -3865,6 +3865,13 @@ Configure using Perl's MakeMaker. It implies USE_PERL5. + + + PERL_MODBUILD + + Configure, build and install using Module::Build. It + implies PERL_CONFIGURE. + Index: book.sgml =================================================================== RCS file: /home/ncvs/doc/ru_RU.KOI8-R/books/porters-handbook/book.sgml,v retrieving revision 1.22 diff -u -r1.22 book.sgml --- book.sgml 16 Jul 2004 12:46:29 -0000 1.22 +++ book.sgml 15 Apr 2005 17:19:16 -0000 @@ -3780,6 +3780,14 @@ Конфигурация при помощи MakeMaker языка Perl. Влечёт USE_PERL5. + + + PERL_MODBUILD + + Конфигурация, сборка и установка посредством модуля + Module::Build. Влечёт + PERL_CONFIGURE. + >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sat Apr 16 10:16:45 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5193616A4CE for ; Sat, 16 Apr 2005 10:16:45 +0000 (GMT) Received: from ns.rixir.net (ns.rixir.net [66.36.228.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id C495A43D31 for ; Sat, 16 Apr 2005 10:16:44 +0000 (GMT) (envelope-from rickt@tyburski.com) Received: from ns.rixir.net (ns.rixir.net [66.36.228.34]) by ns.rixir.net (8.12.9p2/8.12.9) with ESMTP id j3GAGmF7026745 for ; Sat, 16 Apr 2005 03:16:48 -0700 (PDT) (envelope-from rickt@tyburski.com) Date: Sat, 16 Apr 2005 03:16:43 -0700 (PDT) From: Rick X-X-Sender: rickt@ns.rixir.net To: doc@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Quota Documentation X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 10:16:45 -0000 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/quotas.html FreeBSD Handbook Chapter 16 Storage 16.14 File System Quotas I had a bit of a problem and I found someone else that did as well. It appears we followed the steps for configuring Quota and in our effort to streamline our servers on reboot, we had placed check_quotas="NO" in the /etc/rc.conf file. Why you ask? ###################### For finer control over your quota startup, there is an additional configuration variable available. Normally on bootup, the quota integrity of each file system is checked by the quotacheck(8) program. The quotacheck(8) facility insures that the data in the quota database properly reflects the data on the file system. This is a very time consuming process that will significantly affect the time your system takes to boot. If you would like to skip this step, a variable in /etc/rc.conf is made available for the purpose: check_quotas="NO" ######################## This is all fine and dandy, unless you have just built the kernel and /dir/quota.user doesn't exist and you touch the file instead of running quotacheck during, or after the reboot. Yeah, I saw it in /etc/defaults/rc.conf that it should check it by default, but I guess I was over zealous in my streamline attempt. I figured I could always run "quotacheck" as needed and didn't want to prolong any gut wrenching server downtime that might occur when put into production. My suggestion, if you feel it is warranted, is to perhaps add a sentence in parenthesis like so; check_quotas="NO" (Do not add the "NO" option to the /etc/rc.conf file, until the server has successfully rebooted and you verify that quota is working.) Just a thought. It would've saved me some grief and a re-install because bad things happend. Signed, A somewhat grief stricken, but loyal FreeBSD user, -Rick From owner-freebsd-doc@FreeBSD.ORG Sat Apr 16 11:03:13 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B239316A4CE for ; Sat, 16 Apr 2005 11:03:13 +0000 (GMT) Received: from av9-2-sn3.vrr.skanova.net (av9-2-sn3.vrr.skanova.net [81.228.9.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E3D343D1D for ; Sat, 16 Apr 2005 11:03:12 +0000 (GMT) (envelope-from joel@automatvapen.se) Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 092EC37EA4; Sat, 16 Apr 2005 13:03:11 +0200 (CEST) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP id EDE5C37E93 for ; Sat, 16 Apr 2005 13:03:10 +0200 (CEST) Received: from t6o955p75.telia.com (t6o955p75.telia.com [212.181.189.195]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 8E96937E43 for ; Sat, 16 Apr 2005 13:03:08 +0200 (CEST) From: Joel Dahl To: freebsd-doc@freebsd.org Content-Type: multipart/mixed; boundary="=-/qS15RQrPQWjx3YxCJIi" Date: Sat, 16 Apr 2005 13:02:25 +0200 Message-Id: <1113649345.509.26.camel@dude.automatvapen.se> Mime-Version: 1.0 X-Mailer: Evolution 2.2.0 FreeBSD GNOME Team Port Subject: [patch] Update section 8.4 in the handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 11:03:13 -0000 --=-/qS15RQrPQWjx3YxCJIi Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi All, The attached patch contains some corrections to section 8.4 (the configuration file) in our handbook: o Move "device npx" and "device loop" o Remove "maxusers n" and "#makeoptions DEBUG=-g" o Update/Remove some comments etc. My personal opinion is that with this patch, the whole section becomes much more pleasant to read, since all options are sorted as they appear in GENERIC in 5.4. Any objections? :-) -- Joel --=-/qS15RQrPQWjx3YxCJIi Content-Disposition: attachment; filename=kernelconfig2.diff Content-Type: text/x-patch; name=kernelconfig2.diff; charset=us-ascii Content-Transfer-Encoding: 7bit Index: chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v retrieving revision 1.156 diff -u -r1.156 chapter.sgml --- chapter.sgml 14 Apr 2005 18:40:33 -0000 1.156 +++ chapter.sgml 16 Apr 2005 10:03:31 -0000 @@ -447,11 +447,9 @@ Each line contains a keyword and one or more arguments. For simplicity, most lines only contain one argument. Anything following a # is considered a comment and - ignored. The following sections describe each keyword, generally in - the order they are listed in GENERIC, although - some related keywords have been grouped together in a single section - (such as Networking) even though they are actually scattered - throughout the GENERIC file. GENERIC. + For an exhaustive list of architecture dependent options and devices, see the NOTES file in the same directory as GENERIC. For @@ -496,28 +494,6 @@ /usr/src/sys/i386/conf/GENERIC fairly closely. - # -# GENERIC -- Generic kernel configuration file for &os;/i386 -# -# For more information on this file, please read the handbook section on -# Kernel Configuration Files: -# -# http://www.&os;.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html -# -# The handbook is also available locally in /usr/share/doc/handbook -# if you've installed the doc distribution, otherwise always see the -# &os; World Wide Web server (http://www.FreeBSD.org/) for the -# latest information. -# -# An exhaustive list of options and more detailed explanations of the -# device lines is also present in the ../../conf/NOTES and NOTES files. -# If you are in doubt as to the purpose or necessity of a line, check first -# in NOTES. -# -# $FreeBSD: /repoman/r/ncvs/src/sys/i386/conf/GENERIC,v 1.413 2004/08/11 01:34:18 rwatson Exp $ - - The following are the mandatory keywords required in - every kernel you build: kernel options machine @@ -595,80 +571,6 @@ kernel, so it is useful to give the new kernel a different name if you want to keep it separate from your usual kernel (e.g., you want to build an experimental kernel). - - kernel options - maxusers - - - maxusers n - - The maxusers option sets the size of a number - of important system tables. This number is supposed to be roughly - equal to the number of simultaneous users you expect to have on your - machine. - - Starting with &os; 4.5, the system will auto-tune this setting - for you if you explicitly set it to 0 - The auto-tuning algorithm sets maxusers equal - to the amount of memory in the system, with a minimum of 32, and a - maximum of 384.. - In &os; 5.X and above, maxusers will default to - 0 if not specified. If you are using an - version of &os; earlier than 4.5, or you want to manage it - yourself you will want to set - maxusers to at least 4, especially if you are - using the X Window System or compiling software. The reason is that - the most important table set by maxusers is the - maximum number of processes, which is set to 20 + 16 * - maxusers, so if you set maxusers to 1, - then you can only have 36 simultaneous processes, including the 18 - or so that the system starts up at boot time and the 15 or so you - will probably create when you start the X Window System. Even a - simple task like reading a manual page will start up nine processes to - filter, decompress, and view it. Setting - maxusers to 64 will allow you to have up to 1044 - simultaneous processes, which should be enough for nearly all uses. - If, however, you see the dreaded proc table - full error when trying to start another program, or are - running a server with a large number of simultaneous users (like - ftp.FreeBSD.org), you can always - increase the number and rebuild. - - - maxusers does not - limit the number of users which can log into your machine. It - simply sets various table sizes to reasonable values considering - the maximum number of users you will likely have on your system - and how many processes each of them will be running. One keyword - which does limit the number of simultaneous - remote logins and X terminal windows is pseudo-device pty - 16. With &os; 5.X, you do not have to - worry about this number since the &man.pty.4; driver is - auto-cloning; you simply use the line - device pty in your configuration file. - - - # Floating point support - do not disable. -device npx - - npx is the interface to the floating point - math unit in &os;, which is either the hardware co-processor or - the software math emulator. This is not - optional. - - # Pseudo devices -device loop # Network loopback - - This is the generic loopback device for TCP/IP. If you telnet - or FTP to localhost (a.k.a. 127.0.0.1) it will come back at you through - this device. This is mandatory. Under - &os; 4.X you have to use the line pseudo-device - loop. - - Everything that follows is more or less optional. See the notes - underneath or next to each option for more information. #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. @@ -685,21 +587,6 @@ - #makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols - - The normal build process of &os; does not include - debugging information when building the kernel and strips most - symbols after the resulting kernel is linked, to save some space - at the install location. If you are going to do tests of kernels - in the -CURRENT branch or develop changes of your own for the &os; - kernel, you might want to uncomment this line. It will enable the - use of the option which enables debugging - information when passed to &man.gcc.1;. The same can be - accomplished by the &man.config.8; option, if - you are using the traditional way for building your - kernels (see - for more information). - options SCHED_4BSD # 4BSD scheduler The traditional scheduler for &os;. Depending on your system's @@ -1114,6 +1001,14 @@ will enable support for AGP, and AGP GART for boards which have these features. + # Floating point support - do not disable. +device npx + + npx is the interface to the floating point + math unit in &os;, which is either the hardware co-processor or + the software math emulator. This is not + optional. + APM @@ -1282,6 +1177,16 @@ Support for various wireless cards. + # Pseudo devices +device loop # Network loopback + + This is the generic loopback device for TCP/IP. If you telnet + or FTP to localhost (a.k.a. 127.0.0.1) it will come back at you through + this device. This is mandatory. Under + &os; 4.X you have to use the line pseudo-device + loop. + device mem # Memory and kernel memory devices The system memory devices. --=-/qS15RQrPQWjx3YxCJIi-- From owner-freebsd-doc@FreeBSD.ORG Sat Apr 16 11:18:08 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3563F16A4CE for ; Sat, 16 Apr 2005 11:18:08 +0000 (GMT) Received: from abigail.blackend.org (blackend.org [212.11.35.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E19143D46 for ; Sat, 16 Apr 2005 11:18:07 +0000 (GMT) (envelope-from marc@blackend.org) Received: from nosferatu.blackend.org (nosferatu.blackend.org [192.168.10.205])j3GBI3EC030647; Sat, 16 Apr 2005 13:18:03 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: from nosferatu.blackend.org (localhost.blackend.org [127.0.0.1]) j3GBI20q000940; Sat, 16 Apr 2005 13:18:03 +0200 (CEST) (envelope-from marc@nosferatu.blackend.org) Received: (from marc@localhost) by nosferatu.blackend.org (8.13.3/8.13.1/Submit) id j3GBI2vh000939; Sat, 16 Apr 2005 13:18:02 +0200 (CEST) (envelope-from marc) Date: Sat, 16 Apr 2005 13:18:01 +0200 From: Marc Fonvieille To: Joel Dahl Message-ID: <20050416111801.GA624@nosferatu.blackend.org> Mail-Followup-To: Joel Dahl , freebsd-doc@freebsd.org References: <1113649345.509.26.camel@dude.automatvapen.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1113649345.509.26.camel@dude.automatvapen.se> User-Agent: Mutt/1.4.2.1i X-Useless-Header: blackend.org X-Operating-System: FreeBSD 5.4-STABLE cc: freebsd-doc@freebsd.org Subject: Re: [patch] Update section 8.4 in the handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 11:18:08 -0000 On Sat, Apr 16, 2005 at 01:02:25PM +0200, Joel Dahl wrote: > Hi All, > > The attached patch contains some corrections to section 8.4 (the > configuration file) in our handbook: > > o Move "device npx" and "device loop" > > o Remove "maxusers n" and "#makeoptions DEBUG=-g" > [...] If you remove the maxusers part, you should actually move it to "Tuning Kernel Limits" section since this one mentions the maxusers option. The current part of the kernel config section may be useful (maybe in a reworded version). Regarding #makeoptions DEBUG=-g, I think this one should be kept since we use to see too much "how to build a kernel with debugging symbols" questions. Marc From owner-freebsd-doc@FreeBSD.ORG Sat Apr 16 11:55:13 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A5AA16A4CE; Sat, 16 Apr 2005 11:55:13 +0000 (GMT) Received: from av9-2-sn3.vrr.skanova.net (av9-2-sn3.vrr.skanova.net [81.228.9.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF77D43D5A; Sat, 16 Apr 2005 11:55:12 +0000 (GMT) (envelope-from joel@automatvapen.se) Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502) id D78CA37FFF; Sat, 16 Apr 2005 13:55:11 +0200 (CEST) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP id C7E2437F8E; Sat, 16 Apr 2005 13:55:11 +0200 (CEST) Received: from t12o955p72.telia.com (t12o955p72.telia.com [213.66.34.192]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id D8C8E37E43; Sat, 16 Apr 2005 13:55:10 +0200 (CEST) From: Joel Dahl To: Marc Fonvieille In-Reply-To: <20050416111801.GA624@nosferatu.blackend.org> References: <1113649345.509.26.camel@dude.automatvapen.se> <20050416111801.GA624@nosferatu.blackend.org> Content-Type: text/plain Date: Sat, 16 Apr 2005 13:55:16 +0200 Message-Id: <1113652516.509.37.camel@dude.automatvapen.se> Mime-Version: 1.0 X-Mailer: Evolution 2.2.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-doc@freebsd.org Subject: Re: [patch] Update section 8.4 in the handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 11:55:13 -0000 On Sat, 2005-04-16 at 13:18 +0200, Marc Fonvieille wrote: > On Sat, Apr 16, 2005 at 01:02:25PM +0200, Joel Dahl wrote: > > Hi All, > > > > The attached patch contains some corrections to section 8.4 (the > > configuration file) in our handbook: > > > > o Move "device npx" and "device loop" > > > > o Remove "maxusers n" and "#makeoptions DEBUG=-g" > > > [...] > > If you remove the maxusers part, you should actually move it to "Tuning > Kernel Limits" section since this one mentions the maxusers option. The > current part of the kernel config section may be useful (maybe in a > reworded version). Ok, I'll do some rewording and move it there. > Regarding #makeoptions DEBUG=-g, I think this one should be kept since > we use to see too much "how to build a kernel with debugging symbols" > questions. I don't like this. How about adding a section (8.4.2) called "Building a kernel with debugging symbols", which describes various debugging options? I can do the writing. -- Joel From owner-freebsd-doc@FreeBSD.ORG Sat Apr 16 12:16:58 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB0C016A4CE for ; Sat, 16 Apr 2005 12:16:58 +0000 (GMT) Received: from abigail.blackend.org (blackend.org [212.11.35.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1C5243D45 for ; Sat, 16 Apr 2005 12:16:57 +0000 (GMT) (envelope-from marc@blackend.org) Received: from nosferatu.blackend.org (nosferatu.blackend.org [192.168.10.205])j3GCGttI031299; Sat, 16 Apr 2005 14:16:55 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: from nosferatu.blackend.org (localhost.blackend.org [127.0.0.1]) j3GCGtSc001195; Sat, 16 Apr 2005 14:16:55 +0200 (CEST) (envelope-from marc@nosferatu.blackend.org) Received: (from marc@localhost) by nosferatu.blackend.org (8.13.3/8.13.1/Submit) id j3GCGsQ6001194; Sat, 16 Apr 2005 14:16:55 +0200 (CEST) (envelope-from marc) Date: Sat, 16 Apr 2005 14:16:54 +0200 From: Marc Fonvieille To: Joel Dahl Message-ID: <20050416121654.GB624@nosferatu.blackend.org> Mail-Followup-To: Joel Dahl , freebsd-doc@freebsd.org References: <1113649345.509.26.camel@dude.automatvapen.se> <20050416111801.GA624@nosferatu.blackend.org> <1113652516.509.37.camel@dude.automatvapen.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1113652516.509.37.camel@dude.automatvapen.se> User-Agent: Mutt/1.4.2.1i X-Useless-Header: blackend.org X-Operating-System: FreeBSD 5.4-STABLE cc: freebsd-doc@freebsd.org Subject: Re: [patch] Update section 8.4 in the handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 12:16:58 -0000 On Sat, Apr 16, 2005 at 01:55:16PM +0200, Joel Dahl wrote: > > Regarding #makeoptions DEBUG=-g, I think this one should be kept since > > we use to see too much "how to build a kernel with debugging symbols" > > questions. > > I don't like this. How about adding a section (8.4.2) called "Building > a kernel with debugging symbols", which describes various debugging > options? I can do the writing. > It's a better option :) Marc From owner-freebsd-doc@FreeBSD.ORG Sat Apr 16 15:36:25 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D837516A4CE for ; Sat, 16 Apr 2005 15:36:25 +0000 (GMT) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 093B843D5E for ; Sat, 16 Apr 2005 15:36:23 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-b193.otenet.gr [212.205.244.201]) j3GFZE7a015935; Sat, 16 Apr 2005 18:35:15 +0300 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.3/8.13.3) with ESMTP id j3GFaFG3006841; Sat, 16 Apr 2005 18:36:15 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.13.3/8.13.3/Submit) id j3GFaEnL006819; Sat, 16 Apr 2005 18:36:14 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sat, 16 Apr 2005 18:36:14 +0300 From: Giorgos Keramidas To: Joel Dahl Message-ID: <20050416153614.GB973@gothmog.gr> References: <1113649345.509.26.camel@dude.automatvapen.se> <20050416111801.GA624@nosferatu.blackend.org> <1113652516.509.37.camel@dude.automatvapen.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1113652516.509.37.camel@dude.automatvapen.se> cc: freebsd-doc@freebsd.org Subject: Re: [patch] Update section 8.4 in the handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 15:36:26 -0000 On 2005-04-16 13:55, Joel Dahl wrote: > I don't like this. How about adding a section (8.4.2) called > "Building a kernel with debugging symbols", which describes various > debugging options? I can do the writing. That sounds cool :-) From owner-freebsd-doc@FreeBSD.ORG Sat Apr 16 21:56:28 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7283E16A4CE; Sat, 16 Apr 2005 21:56:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 450C043D4C; Sat, 16 Apr 2005 21:56:28 +0000 (GMT) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3GLuSx0050497; Sat, 16 Apr 2005 21:56:28 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3GLuRTH050493; Sat, 16 Apr 2005 21:56:27 GMT (envelope-from remko) Date: Sat, 16 Apr 2005 21:56:27 GMT From: Remko Lodder Message-Id: <200504162156.j3GLuRTH050493@freefall.freebsd.org> To: daniel@dgrund.de, remko@FreeBSD.org, freebsd-doc@FreeBSD.org Subject: Re: docs/79731: manpage for gcc too old X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 21:56:28 -0000 Synopsis: manpage for gcc too old State-Changed-From-To: open->closed State-Changed-By: remko State-Changed-When: Sat Apr 16 21:55:58 GMT 2005 State-Changed-Why: This is actually a duplicate of: docs/72285 Thanks for the submission though! http://www.freebsd.org/cgi/query-pr.cgi?pr=79731