From owner-freebsd-doc Sun Feb 24 1:41:10 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mx1.datanet.hu (mx1.datanet.hu [194.149.13.160]) by hub.freebsd.org (Postfix) with ESMTP id 16EC437B400 for ; Sun, 24 Feb 2002 01:41:07 -0800 (PST) Received: from fonix.adamsfamily.xx (nilus-244.adsl.datanet.hu [195.56.92.243]) by mx1.datanet.hu (DataNet) with ESMTP id 0F13AF961; Sun, 24 Feb 2002 10:41:05 +0100 (CET) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.11.6/8.11.6) id g1O9fUv08816; Sun, 24 Feb 2002 10:41:30 +0100 (CET) (envelope-from sziszi@bsd.hu) Date: Sun, 24 Feb 2002 10:41:27 +0100 From: Szilveszter Adam To: Hiroki Sato Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Entities in translations Message-ID: <20020224094126.GA967@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , Hiroki Sato , freebsd-doc@FreeBSD.ORG References: <20020223115416.GA1152@fonix.adamsfamily.xx> <20020224.090926.85420473.hrs@eos.ocn.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020224.090926.85420473.hrs@eos.ocn.ne.jp> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Feb 24, 2002 at 09:09:26AM +0900, Hiroki Sato wrote: > As you pointed out, this do not become a problem for translated > documents. I think you can use non-ascii characters as is to > write your language, but I also think if we can use entities we should > use them because entities do not mislead us to understand the meaning > in non-English documents. The Japanese team uses entities for Latin > characters, although our Japanese character set has a own set of > Latin characters. Thanks for your suggestion. I think a solution like this will be best.:-) -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 5: 0:11 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CA05F37B405 for ; Sun, 24 Feb 2002 05:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1OD02t76834; Sun, 24 Feb 2002 05:00:02 -0800 (PST) (envelope-from gnats) Received: from community2.interfree.it (community2.interfree.it [213.158.72.4]) by hub.freebsd.org (Postfix) with SMTP id BD07137B400 for ; Sun, 24 Feb 2002 04:49:55 -0800 (PST) Received: (qmail 25437 invoked from network); 24 Feb 2002 12:49:52 -0000 Received: from unknown (HELO numeria) (151.35.185.252) by mail.interfree.it with SMTP; 24 Feb 2002 12:49:52 -0000 Received: (qmail 1242 invoked by uid 1008); 19 Feb 2002 10:50:13 -0000 Message-Id: <20020219105013.1241.qmail@numeria> Date: 19 Feb 2002 10:50:13 -0000 From: nivit@libero.it (Nicola Vitale) Reply-To: Nicola Vitale To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35273: Misprint in _secure_path(3) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35273 >Category: docs >Synopsis: Misprint in _secure_path(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 Feb 24 05:00:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: Nicola Vitale >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD numeria.domo.sua 4.5-STABLE FreeBSD 4.5-STABLE #2: Tue Feb 19 10:18:35 CET 2002 stan@numeria.domo.sua:/usr/obj/usr/src/sys/NUMERIA.SYSCONS i386 >Description: In _secure_path(3) you read "4. Is not group wriable...", instead of "4. Is not group writable...". >How-To-Repeat: man 3 _secure_path >Fix: --- src/lib/libutil/_secure_path.3 Sat Jan 5 22:03:25 2002 +++ src/lib/libutil/_secure_path.3.new Tue Feb 19 11:41:01 2002 @@ -54 +54 @@ -Is not group wriable or it has group ownership by the given +Is not group writable or it has group ownership by the given >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 5: 0:13 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0D7E037B417 for ; Sun, 24 Feb 2002 05:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1OD02B76843; Sun, 24 Feb 2002 05:00:02 -0800 (PST) (envelope-from gnats) Received: from community2.interfree.it (community2.interfree.it [213.158.72.4]) by hub.freebsd.org (Postfix) with SMTP id BD40C37B402 for ; Sun, 24 Feb 2002 04:49:55 -0800 (PST) Received: (qmail 25424 invoked from network); 24 Feb 2002 12:49:50 -0000 Received: from unknown (HELO numeria) (151.35.185.252) by mail.interfree.it with SMTP; 24 Feb 2002 12:49:50 -0000 Received: (qmail 1337 invoked by uid 1008); 21 Feb 2002 17:17:02 -0000 Message-Id: <20020221171702.1336.qmail@numeria> Date: 21 Feb 2002 17:17:02 -0000 From: nivit@libero.it (Nicola Vitale) Reply-To: Nicola Vitale To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35274: Misprint in calendar.birthday Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35274 >Category: docs >Synopsis: Misprint in calendar.birthday >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 Feb 24 05:00:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: Nicola Vitale >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD numeria.domo.sua 4.5-STABLE FreeBSD 4.5-STABLE #2: Tue Feb 19 10:18:35 CET 2002 stan@numeria.domo.sua:/usr/obj/usr/src/sys/NUMERIA.SYSCONS i386 >Description: A 'lapsus calami' in the calendar(1) file: calendar.birthday. 'Buanarroti' instead of 'Buonarroti' >How-To-Repeat: calendar -f /usr/share/calendar/calendar.birthday -t 28.09 >Fix: --- src/usr.bin/calendar/calendars/calendar.birthday Fri Oct 8 23:34:15 1999 +++ src/usr.bin/calendar/calendars/calendar.birthday.new Thu Feb 21 18:00:51 2002 @@ -216 +216 @@ -09/28 Michelangelo Buanarroti born in Caprese, Italy, 1573 +09/28 Michelangelo Buonarroti born in Caprese, Italy, 1573 >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 8:40:30 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id DDE4D37B405 for ; Sun, 24 Feb 2002 08:40:28 -0800 (PST) Received: from hal2500 ([208.191.168.11]) by mta4.rcsntx.swbell.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with SMTP id <0GS100E7TQBG6X@mta4.rcsntx.swbell.net> for FreeBSD-doc@FreeBSD.ORG; Sun, 24 Feb 2002 10:40:28 -0600 (CST) Date: Sun, 24 Feb 2002 10:41:42 -0600 From: Albert Levi Ball Subject: To: FreeBSD-doc@FreeBSD.ORG Reply-To: alball@mindspring.com Message-id: <000501c1bd52$240379a0$6501a8c0@hal2500> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 9: 0: 9 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9A8E037B405 for ; Sun, 24 Feb 2002 09:00:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1OH04D43745; Sun, 24 Feb 2002 09:00:04 -0800 (PST) (envelope-from gnats) Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id 3A99837B41A for ; Sun, 24 Feb 2002 08:50:46 -0800 (PST) Received: from pc4-card4-0-cust162.cdf.cable.ntl.com ([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16f1rI-0004Vm-00 for FreeBSD-gnats-submit@freebsd.org; Sun, 24 Feb 2002 16:50:44 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.35 #1) id 16f1r5-000Ioy-00 for FreeBSD-gnats-submit@freebsd.org; Sun, 24 Feb 2002 16:50:31 +0000 Message-Id: Date: Sun, 24 Feb 2002 16:50:31 +0000 From: Ceri Reply-To: Ceri To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35278: Add a note to my chroot'ing named section Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35278 >Category: docs >Synopsis: Add a note to my chroot'ing named section >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 24 09:00:04 PST 2002 >Closed-Date: >Last-Modified: >Originator: Ceri >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD rhadamanth.private.submonkey.net 4.5-STABLE FreeBSD 4.5-STABLE #0: Tue Feb 12 17:56:57 GMT 2002 setantae@rhadamanth.private.submonkey.net:/usr/obj/usr/src/sys/RHADAMANTH i386 >Description: I've received two reports of the directions for building a statically linked copy of named-xfer failing. This patch adds information on how to fix the issue should it arise. Ceri >How-To-Repeat: >Fix: --- doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml.old Sun Feb 24 16:35:42 2002 +++ doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml Sun Feb 24 16:43:21 2002 @@ -4316,7 +4316,19 @@ &prompt.root; cd /usr/src/lib/libisc && make clean all &prompt.root; cd /usr/src/lib/libbind && make clean all &prompt.root; cd /usr/src/libexec/named-xfer && make NOSHARED=yes all -&prompt.root; cp named-xfer /etc/namedb/bin && chmod 555 /etc/namedb/bin/named-xfer +&prompt.root; cp named-xfer /etc/namedb/bin && chmod 555 /etc/namedb/bin/named-xfer + + + This step has been reported to fail occasionally. If this + happens to you, then issue the command: + + &prompt.root; cd /usr/src && make cleandir && make cleandir + + This will clean out any cruft from your + source tree, and retrying the steps above should then work. + + + >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 9:40:10 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2FCB037B402 for ; Sun, 24 Feb 2002 09:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1OHe1052185; Sun, 24 Feb 2002 09:40:01 -0800 (PST) (envelope-from gnats) Received: from Kain.sumuk.de (Kain.sumuk.de [213.221.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 0BC5237B41C for ; Sun, 24 Feb 2002 09:38:53 -0800 (PST) Received: from Moses.earth.sol (Moses.earth.sol [192.168.1.1]) by Kain.sumuk.de (8.11.6/8.11.5) with ESMTP id g1OHcpp20553 for ; Sun, 24 Feb 2002 18:38:51 +0100 (CET) (envelope-from martin@sumuk.de) Received: (from vincent@localhost) by Moses.earth.sol (8.11.6/8.11.6) id g1OHcpt53446; Sun, 24 Feb 2002 18:38:51 +0100 (CET) (envelope-from vincent) Message-Id: <200202241738.g1OHcpt53446@sumuk.de> Date: Sun, 24 Feb 2002 18:38:51 +0100 (CET) From: Martin Heinen Reply-To: Martin Heinen To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35280: [PATCH] null-modem cable pinout in 'Serial Communications' Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35280 >Category: docs >Synopsis: [PATCH] null-modem cable pinout in 'Serial Communications' >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 Feb 24 09:40:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Martin Heinen >Release: FreeBSD 4.4-STABLE i386 >Organization: >Environment: System: FreeBSD Moses.earth.sol 4.4-STABLE FreeBSD 4.4-STABLE #0: Sat Dec 22 07:35:30 CET 2001 toor@Moses.earth.sol:/usr/obj/usr/src/sys/MOSES i386 >Description: With the null-modem cable pinout depicted in the handbook it is impossible to use hardware flow control. Replaced the layout with a more common one. >How-To-Repeat: Read the chapter 'Serial Communications' and compare for example with http://www.indiacam.net/pinout/#7C >Fix: Index: chapter.sgml =================================================================== RCS file: /u/cvs/doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v retrieving revision 1.52 diff -u -r1.52 chapter.sgml --- chapter.sgml 14 Feb 2002 22:31:00 -0000 1.52 +++ chapter.sgml 24 Feb 2002 17:11:29 -0000 @@ -141,6 +141,14 @@ + SG + 7 + connects to + 7 + SG + + + TxD 2 connects to @@ -157,60 +165,53 @@ - DTR - 20 + RTS + 4 connects to - 6 - DSR + 5 + CTS - DSR - 6 + CTS + 5 connects to - 20 - DTR + 4 + RTS - SG - 7 + DTR + 20 connects to - 7 - SG + 6 + DSR DCD 8 - connects to - 4 - RTS - - - - RTS - 4 - 5 - CTS + 6 + DSR - CTS - 5 + DSR + 6 connects to - 8 - DCD + 20 + DTR - For DCD to RTS, connect pins 4 to 5 internally in the - connector hood, and then to pin 8 in the remote - hood. + Connect Data Set Ready (DSR) and + Data Carrier Detect (DCD) internally in the + connector hood, and then to Data Terminal + Ready (DTR) in the remote hood. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 9:46:41 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 1D6CE37B402 for ; Sun, 24 Feb 2002 09:46:35 -0800 (PST) Received: from hal2500 ([208.191.168.11]) by mta4.rcsntx.swbell.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with SMTP id <0GS100EVDTDM5B@mta4.rcsntx.swbell.net> for FreeBSD-doc@FreeBSD.ORG; Sun, 24 Feb 2002 11:46:34 -0600 (CST) Date: Sun, 24 Feb 2002 11:47:47 -0600 From: Albert Levi Ball Subject: Subscribe To: FreeBSD-doc@FreeBSD.ORG Reply-To: alball@mindspring.com Message-id: <000801c1bd5b$5fdd3250$6501a8c0@hal2500> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 11: 0: 6 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 22C1A37B416 for ; Sun, 24 Feb 2002 11:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1OJ02k65089; Sun, 24 Feb 2002 11:00:02 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0E15C37B405 for ; Sun, 24 Feb 2002 10:52:39 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1OIqcs63912; Sun, 24 Feb 2002 10:52:38 -0800 (PST) (envelope-from nobody) Message-Id: <200202241852.g1OIqcs63912@freefall.freebsd.org> Date: Sun, 24 Feb 2002 10:52:38 -0800 (PST) From: "Daniel B. Hemmerich" To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: docs/35282: typo Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35282 >Category: docs >Synopsis: typo >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 Feb 24 11:00:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: Daniel B. Hemmerich >Release: >Organization: >Environment: >Description: http://www.kr.freebsd.org/handbook/handbook342.shtml In the 2nd paragraph, the 3rd sentance is: It is better to leave maxusers at some reasonable number of add other options, such as NMBCLUSTERS, to increase specific resources. The word 'of' should be changed to 'and' >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 12:39:56 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail.freebsd.se (as3-3-1.n.n.bonet.se [217.215.25.174]) by hub.freebsd.org (Postfix) with ESMTP id BF13037B402 for ; Sun, 24 Feb 2002 12:39:53 -0800 (PST) Received: from trubbel.freebsd.se (t1o975p54.telia.com [195.198.190.54]) by mail.freebsd.se (Postfix) with ESMTP id D68A42BF for ; Sun, 24 Feb 2002 21:45:26 +0100 (CET) Subject: translation of FreeBSD docs to swedish From: Markus =?ISO-8859-1?Q?Hallstr=F6m?= To: freebsd-doc@FreeBSD.ORG Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution/1.0.2 Date: 24 Feb 2002 21:52:28 +0100 Message-Id: <1014583951.3703.6.camel@trubbel.freebsd.se> Mime-Version: 1.0 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi,=20 I want to announce that me and a couple of friends just started a translation of the FreeBSD docs to swedish, We have set up a mailing list and interested are welcome to write to freebsd-doc@lists.freebsd.se and of course, if there is anyone out there who already started this we would be happy to join you in this project cheers /Markus o----------------------------o |Markus Hallstr=F6m tubbs@FreeBSD.se=20 |mobil:073-755 29 86=20 |hem:0121-301 99 |http://tubbs.FreeBSD.se |E a t y o u r d a s e i n o----------------------------o To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 14:44:31 2002 Delivered-To: freebsd-doc@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 1191F37B404; Sun, 24 Feb 2002 14:44:24 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1OMiED95247; Sun, 24 Feb 2002 17:44:15 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 24 Feb 2002 17:44:14 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dag-Erling Smorgrav Cc: freebsd-fs@freebsd.org, doc@freebsd.org Subject: Re: maximum filesystem size In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've taken David out of the CC list. This FAQ entry probably needs updating: it talks about 2.2.7-STABLE and 3.0-CURRENT. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On 22 Feb 2002, Dag-Erling Smorgrav wrote: > David Dougall writes: > > What is the largest filesystem that the freebsd kernel can support? > > I am not on the list. Please reply directly. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#FFS-LIMITS > > Do a minimum amount of research yourself next time. > > DES > -- > Dag-Erling Smorgrav - des@ofug.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 16: 2:27 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B480537B400; Sun, 24 Feb 2002 16:02:25 -0800 (PST) Received: (from grog@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1P01IH39060; Sun, 24 Feb 2002 16:01:18 -0800 (PST) (envelope-from grog) Date: Sun, 24 Feb 2002 16:01:18 -0800 (PST) From: Message-Id: <200202250001.g1P01IH39060@freefall.freebsd.org> To: nivit@libero.it, grog@FreeBSD.org, freebsd-doc@freebsd.org, grog@FreeBSD.org Subject: Re: docs/35274: Misprint in calendar.birthday Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Misprint in calendar.birthday State-Changed-From-To: open->closed State-Changed-By: grog State-Changed-When: Sun Feb 24 16:00:20 PST 2002 State-Changed-Why: Correction applied. Responsible-Changed-From-To: freebsd-doc->grog Responsible-Changed-By: grog Responsible-Changed-When: Sun Feb 24 16:00:20 PST 2002 Responsible-Changed-Why: grog closed this PR. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35274 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 16:49:56 2002 Delivered-To: freebsd-doc@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 3BFEF37B416 for ; Sun, 24 Feb 2002 16:49:53 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id A6E9978319; Mon, 25 Feb 2002 11:19:50 +1030 (CST) Date: Mon, 25 Feb 2002 11:19:50 +1030 From: Greg Lehey To: Rich Morin Cc: freebsd-doc@freebsd.org Subject: Re: Any troff wizards out there? Message-ID: <20020225111950.E41780@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sunday, 17 February 2002 at 13:33:37 -0800, Rich Morin wrote: > I am using the troff MS macros to generate the front matter for the DOSSIER > volumes. I use the XA macro to create table of contents entries, as: > > .XA 10 > \fCcpp(1:RedHat/cpp)\fR > check out RCS revisions > .XA 11 > \fCctm(1:FreeBSD)\fR > source code mirror system > > Each entry contains two lines. The first line consists of a name (e.g., > cpp) > and a parenthesized designation. The second line contains an (indented) > description. So far so good; everything prints as desired: > > cpp(1:RedHat/cpp) > check out RCS revisions . . . . . . . 10 > > Except that the two lines do not always stay together at the end of a page. > > It's been suggested to me that I use the .ne troff command. Our resident > troff "expert" says this is beyond her. She thinks we need to modify the > .XA macro to "do the right thing". Keeps (as in "keep this line with > next") are created from scratch under troff -ms (there is no keep > command, per se) using diversions. > > Help?? Try this in /usr/share/tmac/tmac.s: --- tmac.s Fri Jan 5 10:50:49 2001 +++ /usr/share/tmac/tmac.s Mon Feb 25 11:19:11 2002 @@ -1456,6 +1456,7 @@ .. .de XA .ie '\\n(.z'toc*div' \{\ +. ne 2v . if d toc*num .toc*end-entry . ie \\n[.$] \{\ . ie '\\$1'no' .ds toc*num Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 17:28:49 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 2B54937B400; Sun, 24 Feb 2002 17:28:44 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g1P1Shb47346; Sun, 24 Feb 2002 20:28:43 -0500 (EST) (envelope-from mwlucas) Date: Sun, 24 Feb 2002 20:28:43 -0500 From: Michael Lucas To: Robert Watson Cc: Dag-Erling Smorgrav , freebsd-fs@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: maximum filesystem size Message-ID: <20020224202843.A47334@blackhelicopters.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Sun, Feb 24, 2002 at 05:44:14PM -0500 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org That would be good... is the info correct, except the version number? On Sun, Feb 24, 2002 at 05:44:14PM -0500, Robert Watson wrote: > > I've taken David out of the CC list. This FAQ entry probably needs > updating: it talks about 2.2.7-STABLE and 3.0-CURRENT. > > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > On 22 Feb 2002, Dag-Erling Smorgrav wrote: > > > David Dougall writes: > > > What is the largest filesystem that the freebsd kernel can support? > > > I am not on the list. Please reply directly. > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#FFS-LIMITS > > > > Do a minimum amount of research yourself next time. > > > > DES > > -- > > Dag-Erling Smorgrav - des@ofug.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-fs" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 17:30: 7 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7FE7637B404 for ; Sun, 24 Feb 2002 17:30:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1P1U1r56727; Sun, 24 Feb 2002 17:30:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CD56337B402 for ; Sun, 24 Feb 2002 17:21:58 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1P1LwE55341; Sun, 24 Feb 2002 17:21:58 -0800 (PST) (envelope-from nobody) Message-Id: <200202250121.g1P1LwE55341@freefall.freebsd.org> Date: Sun, 24 Feb 2002 17:21:58 -0800 (PST) From: John Nielsen To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: docs/35291: of/or typo in nge(4) manpage Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35291 >Category: docs >Synopsis: of/or typo in nge(4) 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: Sun Feb 24 17:30:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: John Nielsen >Release: 4.5-RELEASE >Organization: n/a >Environment: FreeBSD humbaba 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Wed Feb 13 01:41:09 GMT 2002 root@humbaba:/usr/src/sys/compile/HUMBABA i386 >Description: The second paragraph of the DESCRIPTION portion of the nge(4) manpage says "...copper of 1000baseX fiber..." and it should say "...copper or 1000baseX fiber...". >How-To-Repeat: man 4 nge >Fix: Change "of" to "or" on line 70 of src/share/man/nge.4. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 17:46:51 2002 Delivered-To: freebsd-doc@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 99B3B37B404 for ; Sun, 24 Feb 2002 17:46:48 -0800 (PST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by white.imgsrc.co.jp (Postfix) with ESMTP id F417724D8E for ; Mon, 25 Feb 2002 10:46:47 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [2001:218:422:2::160]) by black.imgsrc.co.jp (Postfix) with ESMTP id D0B771E4651 for ; Mon, 25 Feb 2002 10:46:46 +0900 (JST) Date: Mon, 25 Feb 2002 10:46:25 +0900 Message-ID: <7mofiebafi.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Documentation Team Subject: www/en/gnome/gnotices.rdf References: <200202250132.g1P1WW375953@castle.jp.FreeBSD.org> User-Agent: Wanderlust/2.9.6 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I don't know fetch'ing gnotices.rdf on the fly when building our www/ tree... /pub/tmp/kuriyama/ncvs/www/en/gnome/gnotices.rdf:17: error: Input is not pr= oper UTF-8, indicate encoding ! GARNOME Preview Two: "Hundmat g=F6r dig stark och smart!"</t= itle> ^ /pub/tmp/kuriyama/ncvs/www/en/gnome/gnotices.rdf:17: error: Bytes: 0xF6 0x7= 2 0x20 0x64 <title>GARNOME Preview Two: "Hundmat g=F6r dig stark och smart!"</t= itle> ^ output conversion failed due to conv error Bytes: 0xF6 0x72 0x20 0x64 xmlOutputBufferWrite: encoder error --=20 Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc. <kuriyama@FreeBSD.org> // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 21:59:10 2002 Delivered-To: freebsd-doc@freebsd.org Received: from promiscuous.dyndns.org (12-248-252-154.client.attbi.com [12.248.252.154]) by hub.freebsd.org (Postfix) with ESMTP id 5C74137B400 for <doc@freebsd.org>; Sun, 24 Feb 2002 21:59:03 -0800 (PST) Received: from sensor (win2k [192.168.1.107]) by promiscuous.dyndns.org (Postfix) with SMTP id 3741053453 for <doc@freebsd.org>; Sun, 24 Feb 2002 23:50:16 -0600 (CST) Message-ID: <005c01c1bdc1$8b39e6d0$6b01a8c0@remingtonltd.com> From: "Onie Camara" <neil@restricted.dyndns.org> To: <doc@freebsd.org> Subject: Help in IPSEC Date: Sun, 24 Feb 2002 23:59:10 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org Hi I've been having a hard time configuring ipsec for a third site. I've read the article about IPSec on the link below. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html I have noticed that it did not mention anything about gif interface. Can I establish ipsec on vpn-gateways without using gif interface? I was actually successful on 2 sites. But not when I connected another site. Thanks in advance. Neil neil camara (neil@restricted.dyndns.org) - cc{na|sa}, mcse - pgp 0x777777B2 network/security engineer - dl := +1(847)2.21.0.224 cn := +1(847)9.80.17.53 echo "I love windows" | sed -e 's/wi/u/g' | cut -f1 -dd | \ awk '/u/ {printf("%s %s %six\n",$1,$2,$3)}' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sun Feb 24 22:11:50 2002 Delivered-To: freebsd-doc@freebsd.org Received: from cyber2.cybrtyme.com (cyber2.cybrtyme.com [209.149.100.11]) by hub.freebsd.org (Postfix) with ESMTP id 40DAD37B41A for <doc@FreeBSD.org>; Sun, 24 Feb 2002 22:11:39 -0800 (PST) Received: from [216.76.88.110] by cyber2.powernet.org (NTMail 7.00.0018/NT3646.00.c574fefa) with ESMTP id ryizmhaa for doc@FreeBSD.org; Mon, 25 Feb 2002 00:14:24 -0600 Message-ID: <000801d28f3e$cb1ebfa0$6e584cd8@system> From: "string" <string@powernet.org> To: <doc@FreeBSD.org> Subject: help Date: Sat, 25 Feb 2017 00:11:39 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01D28EFB.BC2A7400" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0005_01D28EFB.BC2A7400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable will this version of linux install on a 386 PC with 8Mb of RAM and 504 = MB hard drive? string@powernet.org ------=_NextPart_000_0005_01D28EFB.BC2A7400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>will this version of linux install on a = 386 PC with=20 8Mb of RAM and 504 MB hard drive?</FONT></DIV> <DIV><FONT face=3DArial size=3D2><A=20 href=3D"mailto:string@powernet.org">string@powernet.org</A></FONT></DIV> <DIV> </DIV></BODY></HTML> ------=_NextPart_000_0005_01D28EFB.BC2A7400-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Mon Feb 25 1:48: 3 2002 Delivered-To: freebsd-doc@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 522B537B402 for <doc@FreeBSD.org>; Mon, 25 Feb 2002 01:48:01 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id C69D578315; Mon, 25 Feb 2002 20:17:58 +1030 (CST) Date: Mon, 25 Feb 2002 20:17:58 +1030 From: Greg Lehey <grog@FreeBSD.org> To: string <string@powernet.org> Cc: doc@FreeBSD.org Subject: Re: help Message-ID: <20020225201758.M41780@wantadilla.lemis.com> References: <000801d28f3e$cb1ebfa0$6e584cd8@system> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000801d28f3e$cb1ebfa0$6e584cd8@system> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org On Saturday, 25 February 2017 at 0:11:39 -0800, string wrote: > will this version of linux install on a 386 PC with 8Mb of RAM and > 504 MB hard drive? In 15 years' time we'll know. Right now, I'm not sure what you're talking about, especially since we don't have much to do with Linux. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Mon Feb 25 11: 1:51 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4AA4737B42A for <freebsd-doc@freebsd.org>; Mon, 25 Feb 2002 11:00:47 -0800 (PST) Received: (from peter@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1PJ0kn17213 for freebsd-doc@freebsd.org; Mon, 25 Feb 2002 11:00:46 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 25 Feb 2002 11:00:46 -0800 (PST) Message-Id: <200202251900.g1PJ0kn17213@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster <bugmaster@freebsd.org> To: FreeBSD doc list <freebsd-doc@freebsd.org> Subject: Current unassigned doc problem reports Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org 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 report has been examined by a team member and evaluated. f - feedback The problem has been solved, and the originator has been given a patch or a fix has been committed. The PR remains in this state pending a response from the originator. s - suspended The problem is not being worked on. 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. Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- s [2000/07/18] docs/20028 doc ASCII docs should reflect <emphasis> tags o [2001/05/23] docs/27605 doc Cross-document references (<olink>) o [2001/10/14] docs/31265 doc crontab(1) doesn't decribe format of allo o [2002/01/15] ports/33929 doc Section 15.15 of the FreeBSD Porter's Han o [2002/02/14] docs/34947 doc Updated/Translated Article on Filtering B 5 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/08/10] docs/20528 doc sysconf(3) manpage doesn't mention posix. s [2000/11/01] docs/22470 doc man 3 msgrcv's BUGS section needs updatin o [2001/02/01] docs/24786 doc missing FILES descriptions in sa(4) o [2001/04/02] docs/26286 doc *printf(3) etc should gain format string o [2001/04/29] docs/26943 doc [patch] description of :C modifier is mis o [2001/05/25] docs/27653 doc Updates to send-pr.html to support MIME o [2001/05/26] docs/27654 doc Update to PR 27653 o [2001/06/06] docs/27915 doc man 5 passwd does not properly explain th o [2001/06/30] docs/28555 doc [PATCH] style(9) isn't explicit about boo o [2001/07/04] docs/28699 doc strptime(3) %d format specifier not compl o [2001/07/22] docs/29143 doc List of man pages that need to be written o [2001/07/26] docs/29245 doc top(1) manpage doesn't understand SMP f [2001/08/09] docs/29571 doc [PATCH] No man page for pgrp kernel funct a [2001/08/23] docs/30008 doc This document should be translated, comme o [2001/09/08] docs/30442 doc remove broken referemce to gettime(9) fro o [2001/09/13] docs/30556 doc vnconfig man page incorrect; functionalit o [2001/09/24] docs/30809 doc fdisk(8) cleanup o [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 [2001/10/09] docs/31164 doc man page for strftime is incorrect a [2001/10/14] docs/31271 doc rl(4) discourages vender openness by disp o [2001/10/30] docs/31640 doc Avoiding uppercase program names in manpa o [2001/10/30] docs/31653 doc Chapter 14 of the Handbook lacks content o [2001/11/15] docs/32020 doc loader.8 manpage missing tunables o [2001/11/16] docs/32041 doc Add point about net.inet.tcp.portange.{fi o [2001/11/16] docs/32054 doc inconsistency between index.3 and rindex. a [2001/11/26] docs/32323 doc man page `named(8)' do not have link for o [2001/12/01] docs/32425 doc Document cvs update `P file' output o [2001/12/03] docs/32468 doc broken link in handbook: sysutils/mkisofs s [2001/12/07] docs/32578 doc A _really_ petty change to the front page o [2001/12/10] docs/32674 doc no man page for the ntp_adjtime system ca o [2001/12/13] docs/32825 doc undocumented options in LINT o [2001/12/30] docs/33354 doc no rsync section in mirror chapter of the o [2002/01/05] docs/33585 doc Possible Errata in ntp.conf.5 manpage o [2002/01/05] docs/33586 doc An errata in ntp.keys.5 manpage o [2002/01/05] docs/33589 doc Patch to doc.docbook.mk to post process . o [2002/01/13] docs/33852 doc split(1) man page implies that input file o [2002/01/14] docs/33877 doc Documentet behaviour of SF_flags for non- o [2002/01/15] misc/33926 doc Search function on website can not access o [2002/01/18] docs/34038 doc [NEW ARTICLE] Upgrading a.out to Elf o [2002/01/20] docs/34088 doc a.out(5) fails to explain what bss is o [2002/01/22] docs/34184 doc Document "sysctl variable=/dev/foo" synta o [2002/01/24] docs/34234 doc restore(8) man page doesn't explain rrest o [2002/01/24] docs/34239 doc tunefs(8) man page doesn't describe argum o [2002/01/24] docs/34248 doc dump(8) man page block/record/other clari o [2002/02/01] docs/34529 doc [patch] Grammar nits in usbd.conf(5) and o [2002/02/03] docs/34577 doc Some man pages still advise using "confli o [2002/02/03] docs/34583 doc DECLARE_MODULE(9) man page is broken. o [2002/02/04] docs/34626 doc Copyright on "Index of /mail/current" pag o [2002/02/05] docs/34654 doc Update UIDs for porters handbook o [2002/02/08] docs/34743 doc nfsd(8) lacking signal explanation o [2002/02/09] docs/34782 doc pw(8) contains conflicting explanations f o [2002/02/10] docs/34794 doc [patch] Documentation Primer uses depreca o [2002/02/13] docs/34909 doc Porters Handbook or portlint problem o [2002/02/13] docs/34921 doc Developer's Handbook fixes continued: Ker o [2002/02/15] docs/34982 doc rc.conf man page does not list the kerber o [2002/02/16] docs/35011 doc There are no commands called "diskless" o o [2002/02/18] docs/35098 doc NFS chapter simultaneously sucks and blow o [2002/02/18] docs/35105 doc [PATCH] handbook User-ppp chapter o [2002/02/19] docs/35108 doc Developers' Handbook::VM chapter o [2002/02/19] docs/35115 doc src/release/doc/en_US.ISO8859-1/installat o [2002/02/19] docs/35133 doc [patch] work for -junior doc hacker threa o [2002/02/20] docs/35140 doc How to enable DPMS support in XFree86-4 i o [2002/02/20] docs/35155 doc [PATCH] Misc corrections to the Handbook, o [2002/02/22] docs/35206 doc Give information how to mount a photo-cd o [2002/02/22] docs/35222 doc mailing list archive URL regexp suboptima o [2002/02/24] docs/35273 doc Misprint in _secure_path(3) o [2002/02/24] docs/35278 doc Add a note to my chroot'ing named section o [2002/02/24] docs/35280 doc [PATCH] null-modem cable pinout in 'Seria o [2002/02/24] docs/35282 doc typo o [2002/02/24] docs/35291 doc of/or typo in nge(4) manpage 71 problems total. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Mon Feb 25 11:11:40 2002 Delivered-To: freebsd-doc@freebsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [212.22.195.2]) by hub.freebsd.org (Postfix) with ESMTP id CC54E37B41A for <freebsd-doc@freebsd.org>; Mon, 25 Feb 2002 11:11:28 -0800 (PST) Received: from fanf by chiark.greenend.org.uk with local (Exim 3.12 #2) id 16fQWw-00042C-00 (Debian); Mon, 25 Feb 2002 19:11:22 +0000 Date: Mon, 25 Feb 2002 19:11:22 +0000 From: Tony Finch <dot@dotat.at> To: freebsd-doc@freebsd.org Subject: yacc documentation Message-ID: <20020225191122.A15283@chiark.greenend.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org The yacc manual page is remarkably sparse for such a complicated program. Now that ancient Unix has been freed, why not commit the old AT&T PSD documentation for it? Tony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Mon Feb 25 14:10:28 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B08AE37B417 for <freebsd-doc@freebsd.org>; Mon, 25 Feb 2002 14:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1PMA2m64302; Mon, 25 Feb 2002 14:10:02 -0800 (PST) (envelope-from gnats) Date: Mon, 25 Feb 2002 14:10:02 -0800 (PST) Message-Id: <200202252210.g1PMA2m64302@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Tom Rhodes <darklogik@pittgoth.com> Subject: Re: docs/35291 [PATCH] of/or typo in nge(4) man page Reply-To: Tom Rhodes <darklogik@pittgoth.com> Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org The following reply was made to PR docs/35291; it has been noted by GNATS. From: Tom Rhodes <darklogik@pittgoth.com> To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: docs/35291 [PATCH] of/or typo in nge(4) man page Date: Mon, 25 Feb 2002 17:02:26 -0500 (EST) --- nge.4.old Mon Feb 25 16:57:14 2002 +++ nge.4 Mon Feb 25 16:58:21 2002 @@ -67,7 +67,7 @@ All of these NICs are capable of 10, 100 and 1000mbps speeds over CAT5 copper cable. The DP83820 supports TBI (ten bit interface) and GMII -transceivers, which means it can be used with either copper of 1000baseX +transceivers, which means it can be used with either copper or 1000baseX fiber applications. The DP83820 supports TCP/IP checksum offload and VLAN tagging/insertion as well as a 2048-bit multicast hash filter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Mon Feb 25 14:38:35 2002 Delivered-To: freebsd-doc@freebsd.org Received: from zayda.com (celery.zayda.com [208.186.180.200]) by hub.freebsd.org (Postfix) with ESMTP id DED4637B400 for <doc@FreeBSD.org>; Mon, 25 Feb 2002 14:38:33 -0800 (PST) Received: (from apache@localhost) by zayda.com (8.11.6/8.11.6) id g1PMclq13856; Mon, 25 Feb 2002 22:38:47 GMT Date: Mon, 25 Feb 2002 22:38:47 GMT Message-Id: <200202252238.g1PMclq13856@zayda.com> To: doc@FreeBSD.org Subject: Jordan Hubbard Interview Revised From: Ben Hacker Jr <strbenjr@yahoo.com> X-Sender: X-Mailer: PHP Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org OSNews Automatic Email-A-Friend System From: Ben Hacker Jr Email: strbenjr@yahoo.com Hello, this is a message requested to be sent to you on behalf of your friend Ben Hacker Jr. He found this interesting article on OSNews, called: Jordan Hubbard Interview Revised and he would like you to read it too. Please click here to read the article: http://www.osnews.com/story.php?news_id=676 ----------- http://www.OSNews.com The premier web site which reports on a variety of operating systems and technology news! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Mon Feb 25 18:20:10 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2E21937B41C for <freebsd-doc@freebsd.org>; Mon, 25 Feb 2002 18:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1Q2K1m21975; Mon, 25 Feb 2002 18:20:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D529837B41A for <freebsd-gnats-submit@FreeBSD.org>; Mon, 25 Feb 2002 18:10:12 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1Q2ACk20093; Mon, 25 Feb 2002 18:10:12 -0800 (PST) (envelope-from nobody) Message-Id: <200202260210.g1Q2ACk20093@freefall.freebsd.org> Date: Mon, 25 Feb 2002 18:10:12 -0800 (PST) From: Steve Davidson <sdn@sprintlabs.com> To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: docs/35327: XFree86 Intel i810 documentation in handbook is inaccurate Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org >Number: 35327 >Category: docs >Synopsis: XFree86 Intel i810 documentation in handbook is inaccurate >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 25 18:20:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Steve Davidson >Release: FreeBSD 4.5-RELEASE >Organization: >Environment: FreeBSD 4.5-RELEASE PORTNAME= XFree86 PORTVERSION= 4.1.0 PORTREVISION= 12 PORTEPOCH= 1 CATEGORIES= x11 % kldstat Id Refs Address Size Name 1 4 0xc0100000 394090 kernel 2 1 0xc0495000 a2f8 agp.ko 3 1 0xc16e7000 2000 blank_saver.ko 4 1 0xc16eb000 14000 linux.ko % ls -l /dev/agpgart crw------- 1 root wheel 148, 0 Feb 25 05:36 /dev/agpgart >Description: I find the following inaccuracies at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html The docs say: # XFree86 -configure I get: % XFree86 -configure XFree86 Version 4.1.0 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: FreeBSD 4.5-RELEASE i386 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Mon Feb 25 16:32:31 2002 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 Fatal server error: xf86EnableIO: Failed to open /dev/io for extended I/O When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.0.log". Please report problems to xfree86@xfree86.org. It doesn't seem to work. Most i810 advice that I find on the internet is also in some way inaccurate. Is there any accurate information that can advise me on how to get the i810 video chipset working with X? >How-To-Repeat: Just run the command on an i810 system >Fix: Somewhere, somehow, there must be some accurate information on the i810 video chip and X. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 1:52:31 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1ACF137B402; Tue, 26 Feb 2002 01:52:29 -0800 (PST) Received: (from chern@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1Q9jCR21793; Tue, 26 Feb 2002 01:45:12 -0800 (PST) (envelope-from chern) Date: Tue, 26 Feb 2002 01:45:12 -0800 (PST) From: <chern@FreeBSD.org> Message-Id: <200202260945.g1Q9jCR21793@freefall.freebsd.org> To: setantae@submonkey.net, chern@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35278: Add a note to my chroot'ing named section Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org Synopsis: Add a note to my chroot'ing named section State-Changed-From-To: open->closed State-Changed-By: chern State-Changed-When: Tue Feb 26 01:44:57 PST 2002 State-Changed-Why: Committed, Thanks! http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35278 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 1:52:32 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9876437B405; Tue, 26 Feb 2002 01:52:29 -0800 (PST) Received: (from chern@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1Q9nR322466; Tue, 26 Feb 2002 01:49:27 -0800 (PST) (envelope-from chern) Date: Tue, 26 Feb 2002 01:49:27 -0800 (PST) From: <chern@FreeBSD.org> Message-Id: <200202260949.g1Q9nR322466@freefall.freebsd.org> To: sdn@sprintlabs.com, chern@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35327: XFree86 Intel i810 documentation in handbook is inaccurate Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org Synopsis: XFree86 Intel i810 documentation in handbook is inaccurate State-Changed-From-To: open->closed State-Changed-By: chern State-Changed-When: Tue Feb 26 01:47:46 PST 2002 State-Changed-Why: The documentation is accurate. I've helped several people set up their XFree86 servers on various systems using the i810. Notice the instructions say to run (as super user), # XFree86 -configure Run this as root, and follow the rest of the instructions. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35327 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 2:13:18 2002 Delivered-To: freebsd-doc@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 729) id E58A837B405; Tue, 26 Feb 2002 02:13:16 -0800 (PST) To: freebsd-docs@freebsd.org Cc: Subject: Question on managing translations Message-Id: <20020226101316.E58A837B405@hub.freebsd.org> Date: Tue, 26 Feb 2002 02:13:16 -0800 (PST) From: jkoshy@FreeBSD.ORG (Joseph Koshy) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org Question to the translation teams: How are we keeping our translation efforts sync'ed up with the main pages? Do we have a tool that does a 'tree diff' of the original english SGML documentation and highlights changes? I can see that doing a 'diff' can be painful if there are a number of changes to content and structural changes. Regards, Koshy <jkoshy@freebsd.org> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 2:27:20 2002 Delivered-To: freebsd-doc@freebsd.org Received: from catv00.kitanet.ne.jp (catv00.kitanet.ne.jp [210.146.3.11]) by hub.freebsd.org (Postfix) with SMTP id 19CB237B400 for <freebsd-docs@FreeBSD.ORG>; Tue, 26 Feb 2002 02:27:18 -0800 (PST) Received: (qmail 19132 invoked by uid 0); 26 Feb 2002 10:27:10 -0000 Received: from fw132125.kitanet.ne.jp (HELO localhost) (210.237.132.125) by catv00.kitanet.ne.jp with SMTP; 26 Feb 2002 10:27:10 -0000 Date: Tue, 26 Feb 2002 19:27:25 +0900 (JST) Message-Id: <20020226.192725.730589983.sugimura@jp.FreeBSD.org> To: freebsd-docs@FreeBSD.ORG Subject: Re: Question on managing translations From: SUGIMURA Takashi =?iso-2022-jp?B?GyRCP3lCPBsoQiAbJEI1LjtOGyhC?= <sugimura@jp.FreeBSD.org> In-Reply-To: <20020226101316.E58A837B405@hub.freebsd.org> References: <20020226101316.E58A837B405@hub.freebsd.org> X-Mailer: Mew version 2.1 on XEmacs 21.1.14 (Cuyahoga Valley) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org >Question to the translation teams: How are we keeping our translation >efforts sync'ed up with the main pages? > Japanese documents team made the 'syncstat' page; http://www.jp.freebsd.org/doc-jp/syncstat/ How do you feel? --- SUGIMURA Takashi <sugimura@jp.FreeBSD.org> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 2:53:55 2002 Delivered-To: freebsd-doc@freebsd.org Received: from gioria.dyndns.org (AFontenayssB-104-1-5-167.abo.wanadoo.fr [80.13.76.167]) by hub.freebsd.org (Postfix) with ESMTP id 6FEDE37B400 for <freebsd-docs@FreeBSD.ORG>; Tue, 26 Feb 2002 02:53:48 -0800 (PST) Received: by gioria.dyndns.org (Postfix, from userid 42) id 9BEAA374B8; Tue, 26 Feb 2002 11:54:45 +0000 (GMT) Date: Tue, 26 Feb 2002 11:54:45 +0000 From: Sebastien Gioria <gioria@FreeBSD.ORG> To: "SUGIMURA Takashi ?$B?yB<?(B ?$B5.;N?(B" <sugimura@jp.FreeBSD.org> Cc: freebsd-docs@FreeBSD.ORG Subject: Re: Question on managing translations Message-ID: <20020226115445.H79500@thorm.gioria.dyndns.org> Reply-To: Sebastien Gioria <gioria@FreeBSD.ORG> Mail-Followup-To: "SUGIMURA Takashi ?$B?yB<?(B ?$B5.;N?(B" <sugimura@jp.FreeBSD.org>, freebsd-docs@FreeBSD.ORG References: <20020226101316.E58A837B405@hub.freebsd.org> <20020226.192725.730589983.sugimura@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020226.192725.730589983.sugimura@jp.FreeBSD.org>; from sugimura@jp.FreeBSD.org on Tue, Feb 26, 2002 at 07:27:25PM +0900 X-Hostname: thorm.gioria.dyndns.org X-Uptime: 11:53AM up 18:27, 11 users, load averages: 1.27, 1.13, 1.09 X-FreeBSD-Release: FreeBSD-4.5-STABLE Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org On Tue, Feb 26, 2002 at 07:27:25PM +0900, SUGIMURA Takashi ?$B?yB<?(B ?$B5.;N?(B wrote: > >Question to the translation teams: How are we keeping our translation > >efforts sync'ed up with the main pages? > > > > Japanese documents team made the 'syncstat' page; > http://www.jp.freebsd.org/doc-jp/syncstat/ > > How do you feel? Sounds good. > > --- > SUGIMURA Takashi <sugimura@jp.FreeBSD.org> > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-doc" in the body of the message -- Sebastien Gioria gioria@{FreeBSD,FreeBSD-FR}.ORG French FreeBSD User Group http://www.FreeBSD-FR.ORG ...and on the eighth day God created FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 4:26:45 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail.ruhr.de (in-ruhr4.ruhr.de [212.23.134.2]) by hub.freebsd.org (Postfix) with SMTP id 3A23837B400 for <freebsd-docs@freebsd.org>; Tue, 26 Feb 2002 04:26:42 -0800 (PST) Received: (qmail 11916 invoked by uid 10); 26 Feb 2002 12:26:40 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.11.6/8.11.2) id g1QCP9W49099 for freebsd-docs@freebsd.org; Tue, 26 Feb 2002 13:25:09 +0100 (CET) (envelope-from ue) Date: Tue, 26 Feb 2002 13:25:09 +0100 From: Udo Erdelhoff <ue@nathan.ruhr.de> To: freebsd-docs@freebsd.org Subject: Re: Question on managing translations Message-ID: <20020226132509.B191@nathan.ruhr.de> References: <20020226101316.E58A837B405@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020226101316.E58A837B405@hub.freebsd.org> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org On Tue, Feb 26, 2002 at 02:13:16AM -0800, Joseph Koshy wrote: > Question to the translation teams: How are we keeping our translation > efforts sync'ed up with the main pages? cvs diff -u, mostly. > I can see that doing a 'diff' can be painful if there are a number of > changes to content and structural changes. That is the reason why we have the 'do not mix changes to content, structure, markup and whitespace'-rule for the english documents. I just battered my way through the last 4 months (or so) of FAQ changes during the last 72 hours and finding out what was happening was rather easy because of this rule. And yes, the very few people who violated this rule have been slapped for it, both in private and in public. /s/Udo PS: Yes, I am still very much alive and kicking -- Der Einsatz von M$-Mailsystemen ist sehr erfolgreich, aber leider vor allem bei der Verbreitung von Viren wie Melissa, Papa oder explore.zip. Dies ist durchaus auch in der Architektur dieser Software begruendet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 5:20: 8 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A26F037B404 for <freebsd-doc@freebsd.org>; Tue, 26 Feb 2002 05:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1QDK1880268; Tue, 26 Feb 2002 05:20:01 -0800 (PST) (envelope-from gnats) Received: from hand.dotat.at (host217-35-46-127.in-addr.btopenworld.com [217.35.46.127]) by hub.freebsd.org (Postfix) with ESMTP id 868D037B400 for <FreeBSD-gnats-submit@freebsd.org>; Tue, 26 Feb 2002 05:17:54 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.35 #1) id 16fhU1-000O79-00; Tue, 26 Feb 2002 13:17:29 +0000 Message-Id: <E16fhU1-000O79-00@hand.dotat.at> Date: Tue, 26 Feb 2002 13:17:29 +0000 From: Tony Finch <dot@dotat.at> Reply-To: Tony Finch <dot@dotat.at> To: FreeBSD-gnats-submit@freebsd.org Cc: Tony Finch <dot@dotat.at> X-Send-Pr-Version: 3.113 Subject: docs/35343: Old broken Unix docco Makefiles Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org >Number: 35343 >Category: docs >Synopsis: Old broken Unix docco Makefiles >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 26 05:20:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Tony Finch >Release: FreeBSD 4.5-STABLE-20020220 i386 >Organization: dotat labs >Environment: System: FreeBSD hand.dotat.at 4.5-STABLE-20020220 FreeBSD 4.5-STABLE-20020220 #1 5: Wed Feb 20 07:46:52 GMT 2002 fanf@hand.dotat.at:/FreeBSD/obj/FreeBSD/releng4/ sys/SHARP i386 >Description: The following Makefiles are broken (they don't install the documentation in the right place) and aren't used because the documentation is built by Makefiles under /usr/src/share/doc/{usd,psd,smm}/. /usr/src/usr.sbin/config/SMM.doc/Makefile /usr/src/usr.bin/make/PSD.doc/Makefile /usr/src/usr.bin/mail/USD.doc/Makefile /usr/src/usr.bin/gprof/PSD.doc/Makefile /usr/src/sbin/fsck/SMM.doc/Makefile /usr/src/games/trek/USD.doc/Makefile /usr/src/games/rogue/USD.doc/Makefile /usr/src/bin/csh/USD.doc/Makefile >How-To-Repeat: >Fix: Remove the bogus Makefiles listed above. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 5:23:37 2002 Delivered-To: freebsd-doc@freebsd.org Received: from router.uvt.ro (routeruvt.utt.ro [193.226.8.113]) by hub.freebsd.org (Postfix) with ESMTP id 12F3137B404; Tue, 26 Feb 2002 05:23:29 -0800 (PST) Received: from quasar.physics.uvt.ro (quasar.physics.uvt.ro [193.226.13.67]) by router.uvt.ro (8.11.6/8.11.6) with ESMTP id g1QDNTL65992; Tue, 26 Feb 2002 15:23:29 +0200 (EET) Received: from ns.ro.freebsd.org (ns.ro.freebsd.org [193.226.13.15]) by quasar.physics.uvt.ro (8.11.6/8.11.6) with ESMTP id g1QDNEc73530; Tue, 26 Feb 2002 15:23:15 +0200 (EET) Received: from localhost (admin@localhost) by ns.ro.freebsd.org (8.11.6/8.11.6) with ESMTP id g1QDQlY07627; Tue, 26 Feb 2002 15:27:08 +0200 (EET) (envelope-from admin@ns.ro.freebsd.org) Date: Tue, 26 Feb 2002 15:26:46 +0200 (EET) From: Gheorghe Ardelean <admin@ro.freebsd.org> To: freebsd-hubs@freebsd.org Cc: freebsd-www@freebsd.org, <freebsd-doc@freebsd.org> Subject: New cvsup and www server in Romania! Message-ID: <20020223181934.C4027-100000@ns.ro.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org Hi all, A new (the first cvsup.ro.freebsd.org) cvs server was established in Romania. There is also a second WWW server here (www2.ro.freebsd.org) Please update the home page and handbook to reflect this ( http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html ) Regards, G. Ardelean (aka hostmaster@ro.freebsd.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 6:11:40 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2F32B37B402 for <freebsd-doc@freebsd.org>; Tue, 26 Feb 2002 06:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1QEA1Y00284; Tue, 26 Feb 2002 06:10:01 -0800 (PST) (envelope-from gnats) Received: from hand.dotat.at (host217-35-46-127.in-addr.btopenworld.com [217.35.46.127]) by hub.freebsd.org (Postfix) with ESMTP id 71DF737B402 for <FreeBSD-gnats-submit@freebsd.org>; Tue, 26 Feb 2002 06:07:16 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.35 #1) id 16fiFp-000OEy-00; Tue, 26 Feb 2002 14:06:53 +0000 Message-Id: <E16fiFp-000OEy-00@hand.dotat.at> Date: Tue, 26 Feb 2002 14:06:53 +0000 From: Tony Finch <dot@dotat.at> Reply-To: Tony Finch <dot@dotat.at> To: FreeBSD-gnats-submit@freebsd.org Cc: Tony Finch <dot@dotat.at> X-Send-Pr-Version: 3.113 Subject: docs/35345: Restore old yacc documentation Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org >Number: 35345 >Category: docs >Synopsis: Restore old yacc documentation >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Tue Feb 26 06:10:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Tony Finch >Release: FreeBSD 4.5-STABLE-20020220 i386 >Organization: dotat labs >Environment: System: FreeBSD hand.dotat.at 4.5-STABLE-20020220 FreeBSD 4.5-STABLE-20020220 #15: Wed Feb 20 07:46:52 GMT 2002 fanf@hand.dotat.at:/FreeBSD/obj/FreeBSD/releng4/sys/SHARP i386 >Description: The patch below adds the yacc documentation obtained from 4.3BSD-Reno via TUHS's archives. There are some incompatibilities between the -msU macros that this documentation was written in and the -ms macros, but I am not a troff person so I haven't attempted to fix it. There are of course lots of other sections of the documentation that are missing because they have in the past been encumbered. I can prepare patches for adding them as well, if you want. >How-To-Repeat: >Fix: --- /usr/src/share/doc/psd/Makefile Fri Nov 26 09:27:36 1999 +++ /usr/src/share/doc/psd.new/Makefile Tue Feb 26 13:50:20 2002 @@ -4,15 +4,15 @@ # The following modules do not build/install: # 10.gdb -# The following modules are encumbered: +# The following modules are missing because they were encumbered: # 01.cacm 02.implement 03.iosys 04.uprog 06.Clang 11.adb 14.sccs -# 15.yacc 16.lex 17.m4 +# 16.lex 17.m4 # The following modules do not apply to FreeBSD: # 07.pascal 08.f77 09.f77io SUBDIR= title contents -SUBDIR+= 05.sysman 12.make 13.rcs 18.gprof 20.ipctut 21.ipc +SUBDIR+= 05.sysman 12.make 13.rcs 15.yacc 18.gprof 20.ipctut 21.ipc # The following modules are new in FreeBSD: SUBDIR+= 22.rpcgen 23.rpc 24.xdr 25.xdrrfc 26.rpcrfc 27.nfsrpc --- /usr/src/share/doc/psd/15.yacc/Makefile Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/Makefile Tue Feb 26 13:53:48 2002 @@ -0,0 +1,10 @@ +# From: @(#)Makefile 8.1 (Berkeley) 6/8/93 +# $FreeBSD$ + +VOLUME= psd/15.yacc +SRCS= ss.. ss0 ss1 ss2 ss3 ss4 ss5 ss6 ss7 ss8 ss9 ssA ssB ssa ssb ssc ssd +MACROS= -ms + +USE_REFER= yes + +.include <bsd.doc.mk> --- /usr/src/share/doc/psd/15.yacc/ss.. Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss.. Tue Feb 26 13:49:21 2002 @@ -0,0 +1,56 @@ +.\" @(#)ss.. 6.1 (Berkeley) 5/8/86 +.\" +.EH 'PSD:15-%''Yacc: Yet Another Compiler-Compiler' +.OH 'Yacc: Yet Another Compiler-Compiler''PSD:15-%' +.\".RP +.ND "July 31, 1978" +.TL +Yacc: +Yet Another Compiler-Compiler +.AU "MH 2C-559" 3968 +Stephen C. Johnson +.AI +.MH +.AB +.PP +Computer program input generally has some structure; +in fact, every computer program that does input can be thought of as defining +an ``input language'' which it accepts. +An input language may be as complex as a programming language, or as simple as +a sequence of numbers. +Unfortunately, usual input facilities +are limited, difficult to use, +and often are lax about checking their inputs for validity. +.PP +Yacc provides a general tool for describing +the input to a computer program. +The Yacc user specifies the structures +of his input, together with code to be invoked as +each such structure is recognized. +Yacc turns such a specification into a subroutine that +handles the input process; +frequently, it is convenient and appropriate to have most +of the flow of control in the user's application +handled by this subroutine. +.PP +The input subroutine produced by Yacc calls a user-supplied routine to +return the next basic input item. +Thus, the user can specify his input in terms of individual input characters, or +in terms of higher level constructs such as names and numbers. +The user-supplied routine may also handle idiomatic features such as +comment and continuation conventions, which typically defy easy grammatical specification. +.PP +Yacc is written in portable C. +The class of specifications accepted is a very general one: LALR(1) +grammars with disambiguating rules. +.PP +In addition to compilers for C, APL, Pascal, RATFOR, etc., Yacc +has also been used for less conventional languages, +including a phototypesetter language, several desk calculator languages, a document retrieval system, +and a Fortran debugging system. +.AE +.OK +.\"Computer Languages +.\"Compilers +.\"Formal Language Theory +.CS 23 11 34 0 0 8 --- /usr/src/share/doc/psd/15.yacc/ss0 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss0 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,201 @@ +.\" @(#)ss0 6.1 (Berkeley) 5/8/86 +.\" +.SH +0: Introduction +.PP +Yacc provides a general tool for imposing structure on the input to a computer program. +The Yacc user prepares a +specification of the input process; this includes rules +describing the input structure, code to be invoked when these +rules are recognized, and a low-level routine to do the +basic input. +Yacc then generates a function to control the input process. +This function, called a +.I parser , +calls the user-supplied low-level input routine +(the +.I "lexical analyzer" ) +to pick up the basic items +(called +.I tokens ) +from the input stream. +These tokens are organized according to the input structure rules, +called +.I "grammar rules" \|; +when one of these rules has been recognized, +then user code supplied for this rule, an +.I action , +is invoked; actions have the ability to return values and +make use of the values of other actions. +.PP +Yacc is written in a portable dialect of C +.[ +Ritchie Kernighan Language Prentice +.] +and the actions, and output subroutine, are in C as well. +Moreover, many of the syntactic conventions of Yacc follow C. +.PP +The heart of the input specification is a collection of grammar rules. +Each rule describes an allowable structure and gives it a name. +For example, one grammar rule might be +.DS +date : month\_name day \',\' year ; +.DE +Here, +.I date , +.I month\_name , +.I day , +and +.I year +represent structures of interest in the input process; +presumably, +.I month\_name , +.I day , +and +.I year +are defined elsewhere. +The comma ``,'' is enclosed in single quotes; this implies that the +comma is to appear literally in the input. +The colon and semicolon merely serve as punctuation in the rule, and have +no significance in controlling the input. +Thus, with proper definitions, the input +.DS +July 4, 1776 +.DE +might be matched by the above rule. +.PP +An important part of the input process is carried out by the +lexical analyzer. +This user routine reads the input stream, recognizing the lower level structures, +and communicates these tokens +to the parser. +For historical reasons, a structure recognized by the lexical analyzer is called a +.I "terminal symbol" , +while the structure recognized by the parser is called a +.I "nonterminal symbol" . +To avoid confusion, terminal symbols will usually be referred to as +.I tokens . +.PP +There is considerable leeway in deciding whether to recognize structures using the lexical +analyzer or grammar rules. +For example, the rules +.DS +month\_name : \'J\' \'a\' \'n\' ; +month\_name : \'F\' \'e\' \'b\' ; + + . . . + +month\_name : \'D\' \'e\' \'c\' ; +.DE +might be used in the above example. +The lexical analyzer would only need to recognize individual letters, and +.I month\_name +would be a nonterminal symbol. +Such low-level rules tend to waste time and space, and may +complicate the specification beyond Yacc's ability to deal with it. +Usually, the lexical analyzer would +recognize the month names, +and return an indication that a +.I month\_name +was seen; in this case, +.I month\_name +would be a token. +.PP +Literal characters such as ``,'' must also be passed through the lexical +analyzer, and are also considered tokens. +.PP +Specification files are very flexible. +It is realively easy to add to the above example the rule +.DS +date : month \'/\' day \'/\' year ; +.DE +allowing +.DS +7 / 4 / 1776 +.DE +as a synonym for +.DS +July 4, 1776 +.DE +In most cases, this new rule could be ``slipped in'' to a working system with minimal effort, +and little danger of disrupting existing input. +.PP +The input being read may not conform to the +specifications. +These input errors are detected as early as is theoretically possible with a +left-to-right scan; +thus, not only is the chance of reading and computing with bad +input data substantially reduced, but the bad data can usually be quickly found. +Error handling, +provided as part of the input specifications, +permits the reentry of bad data, +or the continuation of the input process after skipping over the bad data. +.PP +In some cases, Yacc fails to produce a parser when given a set of +specifications. +For example, the specifications may be self contradictory, or they may +require a more powerful recognition mechanism than that available to Yacc. +The former cases represent design errors; +the latter cases +can often be corrected +by making +the lexical analyzer +more powerful, or by rewriting some of the grammar rules. +While Yacc cannot handle all possible specifications, its power +compares favorably with similar systems; +moreover, the +constructions which are difficult for Yacc to handle are +also frequently difficult for human beings to handle. +Some users have reported that the discipline of formulating valid +Yacc specifications for their input revealed errors of +conception or design early in the program development. +.PP +The theory underlying Yacc has been described elsewhere. +.[ +Aho Johnson Surveys LR Parsing +.] +.[ +Aho Johnson Ullman Ambiguous Grammars +.] +.[ +Aho Ullman Principles Compiler Design +.] +Yacc has been extensively used in numerous practical applications, +including +.I lint , +.[ +Johnson Lint +.] +the Portable C Compiler, +.[ +Johnson Portable Compiler Theory +.] +and a system for typesetting mathematics. +.[ +Kernighan Cherry typesetting system CACM +.] +.PP +The next several sections describe the +basic process of preparing a Yacc specification; +Section 1 describes the preparation of grammar rules, +Section 2 the preparation of the user supplied actions associated with these rules, +and Section 3 the preparation of lexical analyzers. +Section 4 describes the operation of the parser. +Section 5 discusses various reasons why Yacc may be unable to produce a +parser from a specification, and what to do about it. +Section 6 describes a simple mechanism for +handling operator precedences in arithmetic expressions. +Section 7 discusses error detection and recovery. +Section 8 discusses the operating environment and special features +of the parsers Yacc produces. +Section 9 gives some suggestions which should improve the +style and efficiency of the specifications. +Section 10 discusses some advanced topics, and Section 11 gives +acknowledgements. +Appendix A has a brief example, and Appendix B gives a +summary of the Yacc input syntax. +Appendix C gives an example using some of the more advanced +features of Yacc, and, finally, +Appendix D describes mechanisms and syntax +no longer actively supported, but +provided for historical continuity with older versions of Yacc. --- /usr/src/share/doc/psd/15.yacc/ss1 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss1 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,138 @@ +.\" @(#)ss1 6.1 (Berkeley) 5/8/86 +.\" +.tr *\(** +.tr |\(or +.SH +1: Basic Specifications +.PP +Names refer to either tokens or nonterminal symbols. +Yacc requires +token names to be declared as such. +In addition, for reasons discussed in Section 3, it is often desirable +to include the lexical analyzer as part of the specification file; +it may be useful to include other programs as well. +Thus, every specification file consists of three sections: +the +.I declarations , +.I "(grammar) rules" , +and +.I programs . +The sections are separated by double percent ``%%'' marks. +(The percent ``%'' is generally used in Yacc specifications as an escape character.) +.PP +In other words, a full specification file looks like +.DS +declarations +%% +rules +%% +programs +.DE +.PP +The declaration section may be empty. +Moreover, if the programs section is omitted, the second %% mark may be omitted also; +thus, the smallest legal Yacc specification is +.DS +%% +rules +.DE +.PP +Blanks, tabs, and newlines are ignored except +that they may not appear in names or multi-character reserved symbols. +Comments may appear wherever a name is legal; they are enclosed +in /* . . . */, as in C and PL/I. +.PP +The rules section is made up of one or more grammar rules. +A grammar rule has the form: +.DS +A : BODY ; +.DE +A represents a nonterminal name, and BODY represents a sequence of zero or more names and literals. +The colon and the semicolon are Yacc punctuation. +.PP +Names may be of arbitrary length, and may be made up of letters, dot ``.'', underscore ``\_'', and +non-initial digits. +Upper and lower case letters are distinct. +The names used in the body of a grammar rule may represent tokens or nonterminal symbols. +.PP +A literal consists of a character enclosed in single quotes ``\'''. +As in C, the backslash ``\e'' is an escape character within literals, and all the C escapes +are recognized. +Thus +.DS +\'\en\' newline +\'\er\' return +\'\e\'\' single quote ``\''' +\'\e\e\' backslash ``\e'' +\'\et\' tab +\'\eb\' backspace +\'\ef\' form feed +\'\exxx\' ``xxx'' in octal +.DE +For a number of technical reasons, the +\s-2NUL\s0 +character (\'\e0\' or 0) should never +be used in grammar rules. +.PP +If there are several grammar rules with the same left hand side, the vertical bar ``|'' +can be used to avoid rewriting the left hand side. +In addition, +the semicolon at the end of a rule can be dropped before a vertical bar. +Thus the grammar rules +.DS +A : B C D ; +A : E F ; +A : G ; +.DE +can be given to Yacc as +.DS +A : B C D + | E F + | G + ; +.DE +It is not necessary that all grammar rules with the same left side appear together in the grammar rules section, +although it makes the input much more readable, and easier to change. +.PP +If a nonterminal symbol matches the empty string, this can be indicated in the obvious way: +.DS +empty : ; +.DE +.PP +Names representing tokens must be declared; this is most simply done by writing +.DS +%token name1 name2 . . . +.DE +in the declarations section. +(See Sections 3 , 5, and 6 for much more discussion). +Every name not defined in the declarations section is assumed to represent a nonterminal symbol. +Every nonterminal symbol must appear on the left side of at least one rule. +.PP +Of all the nonterminal symbols, one, called the +.I "start symbol" , +has particular importance. +The parser is designed to recognize the start symbol; thus, +this symbol represents the largest, +most general structure described by the grammar rules. +By default, +the start symbol is taken to be the left hand side of the first +grammar rule in the rules section. +It is possible, and in fact desirable, to declare the start +symbol explicitly in the declarations section using the %start keyword: +.DS +%start symbol +.DE +.PP +The end of the input to the parser is signaled by a special token, called the +.I endmarker . +If the tokens up to, but not including, the endmarker form a structure +which matches the start symbol, the parser function returns to its caller +after the endmarker is seen; it +.I accepts +the input. +If the endmarker is seen in any other context, it is an error. +.PP +It is the job of the user-supplied lexical analyzer +to return the endmarker when appropriate; see section 3, below. +Usually the endmarker represents some reasonably obvious +I/O status, such as ``end-of-file'' or ``end-of-record''. --- /usr/src/share/doc/psd/15.yacc/ss2 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss2 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,151 @@ +.\" @(#)ss2 6.1 (Berkeley) 5/8/86 +.\" +.SH +2: Actions +.PP +With each grammar rule, the user may associate actions to be performed each time +the rule is recognized in the input process. +These actions may return values, and may obtain the values returned by previous +actions. +Moreover, the lexical analyzer can return values +for tokens, if desired. +.PP +An action is an arbitrary C statement, and as such can do +input and output, call subprograms, and alter +external vectors and variables. +An action is specified by +one or more statements, enclosed in curly braces ``{'' and ``}''. +For example, +.DS +A : \'(\' B \')\' + { hello( 1, "abc" ); } +.DE +and +.DS +XXX : YYY ZZZ + { printf("a message\en"); + flag = 25; } +.DE +are grammar rules with actions. +.PP +To facilitate easy communication between the actions and the parser, the action statements are altered +slightly. +The symbol ``dollar sign'' ``$'' is used as a signal to Yacc in this context. +.PP +To return a value, the action normally sets the +pseudo-variable ``$$'' to some value. +For example, an action that does nothing but return the value 1 is +.DS + { $$ = 1; } +.DE +.PP +To obtain the values returned by previous actions and the lexical analyzer, the +action may use the pseudo-variables $1, $2, . . ., +which refer to the values returned by the +components of the right side of a rule, reading from left to right. +Thus, if the rule is +.DS +A : B C D ; +.DE +for example, then $2 has the value returned by C, and $3 the value returned by D. +.PP +As a more concrete example, consider the rule +.DS +expr : \'(\' expr \')\' ; +.DE +The value returned by this rule is usually the value of the +.I expr +in parentheses. +This can be indicated by +.DS +expr : \'(\' expr \')\' { $$ = $2 ; } +.DE +.PP +By default, the value of a rule is the value of the first element in it ($1). +Thus, grammar rules of the form +.DS +A : B ; +.DE +frequently need not have an explicit action. +.PP +In the examples above, all the actions came at the end of their rules. +Sometimes, it is desirable to get control before a rule is fully parsed. +Yacc permits an action to be written in the middle of a rule as well +as at the end. +This rule is assumed to return a value, accessible +through the usual \$ mechanism by the actions to +the right of it. +In turn, it may access the values +returned by the symbols to its left. +Thus, in the rule +.DS +A : B + { $$ = 1; } + C + { x = $2; y = $3; } + ; +.DE +the effect is to set +.I x +to 1, and +.I y +to the value returned by C. +.PP +Actions that do not terminate a rule are actually +handled by Yacc by manufacturing a new nonterminal +symbol name, and a new rule matching this +name to the empty string. +The interior action is the action triggered off by recognizing +this added rule. +Yacc actually treats the above example as if +it had been written: +.DS +$ACT : /* empty */ + { $$ = 1; } + ; + +A : B $ACT C + { x = $2; y = $3; } + ; +.DE +.PP +In many applications, output is not done directly by the actions; +rather, a data structure, such as a parse tree, is constructed in memory, +and transformations are applied to it before output is generated. +Parse trees are particularly easy to +construct, given routines to build and maintain the tree +structure desired. +For example, suppose there is a C function +.I node , +written so that the call +.DS +node( L, n1, n2 ) +.DE +creates a node with label L, and descendants n1 and n2, and returns the index of +the newly created node. +Then parse tree can be built by supplying actions such as: +.DS +expr : expr \'+\' expr + { $$ = node( \'+\', $1, $3 ); } +.DE +in the specification. +.PP +The user may define other variables to be used by the actions. +Declarations and definitions can appear in +the declarations section, +enclosed in the marks ``%{'' and ``%}''. +These declarations and definitions have global scope, +so they are known to the action statements and the lexical analyzer. +For example, +.DS +%{ int variable = 0; %} +.DE +could be placed in the declarations section, +making +.I variable +accessible to all of the actions. +The Yacc parser uses only names beginning in ``yy''; +the user should avoid such names. +.PP +In these examples, all the values are integers: a discussion of +values of other types will be found in Section 10. --- /usr/src/share/doc/psd/15.yacc/ss3 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss3 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,104 @@ +.\" @(#)ss3 6.1 (Berkeley) 5/8/86 +.\" +.SH +3: Lexical Analysis +.PP +The user must supply a lexical analyzer to read the input stream and communicate tokens +(with values, if desired) to the parser. +The lexical analyzer is an integer-valued function called +.I yylex . +The function returns an integer, the +.I "token number" , +representing the kind of token read. +If there is a value associated with that token, it should be assigned +to the external variable +.I yylval . +.PP +The parser and the lexical analyzer must agree on these token numbers in order for +communication between them to take place. +The numbers may be chosen by Yacc, or chosen by the user. +In either case, the ``# define'' mechanism of C is used to allow the lexical analyzer +to return these numbers symbolically. +For example, suppose that the token name DIGIT has been defined in the declarations section of the +Yacc specification file. +The relevant portion of the lexical analyzer might look like: +.DS +yylex(){ + extern int yylval; + int c; + . . . + c = getchar(); + . . . + switch( c ) { + . . . + case \'0\': + case \'1\': + . . . + case \'9\': + yylval = c\-\'0\'; + return( DIGIT ); + . . . + } + . . . +.DE +.PP +The intent is to return a token number of DIGIT, and a value equal to the numerical value of the +digit. +Provided that the lexical analyzer code is placed in the programs section of the specification file, +the identifier DIGIT will be defined as the token number associated +with the token DIGIT. +.PP +This mechanism leads to clear, +easily modified lexical analyzers; the only pitfall is the need +to avoid using any token names in the grammar that are reserved +or significant in C or the parser; for example, the use of +token names +.I if +or +.I while +will almost certainly cause severe +difficulties when the lexical analyzer is compiled. +The token name +.I error +is reserved for error handling, and should not be used naively +(see Section 7). +.PP +As mentioned above, the token numbers may be chosen by Yacc or by the user. +In the default situation, the numbers are chosen by Yacc. +The default token number for a literal +character is the numerical value of the character in the local character set. +Other names are assigned token numbers +starting at 257. +.PP +To assign a token number to a token (including literals), +the first appearance of the token name or literal +.I +in the declarations section +.R +can be immediately followed by +a nonnegative integer. +This integer is taken to be the token number of the name or literal. +Names and literals not defined by this mechanism retain their default definition. +It is important that all token numbers be distinct. +.PP +For historical reasons, the endmarker must have token +number 0 or negative. +This token number cannot be redefined by the user; thus, all +lexical analyzers should be prepared to return 0 or negative as a token number +upon reaching the end of their input. +.PP +A very useful tool for constructing lexical analyzers is +the +.I Lex +program developed by Mike Lesk. +.[ +Lesk Lex +.] +These lexical analyzers are designed to work in close +harmony with Yacc parsers. +The specifications for these lexical analyzers +use regular expressions instead of grammar rules. +Lex can be easily used to produce quite complicated lexical analyzers, +but there remain some languages (such as FORTRAN) which do not +fit any theoretical framework, and whose lexical analyzers +must be crafted by hand. --- /usr/src/share/doc/psd/15.yacc/ss4 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss4 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,330 @@ +.\" @(#)ss4 6.1 (Berkeley) 5/8/86 +.\" +.SH +4: How the Parser Works +.PP +Yacc turns the specification file into a C program, which +parses the input according to the specification given. +The algorithm used to go from the +specification to the parser is complex, and will not be discussed +here (see +the references for more information). +The parser itself, however, is relatively simple, +and understanding how it works, while +not strictly necessary, will nevertheless make +treatment of error recovery and ambiguities much more +comprehensible. +.PP +The parser produced by Yacc consists +of a finite state machine with a stack. +The parser is also capable of reading and remembering the next +input token (called the +.I lookahead +token). +The +.I "current state" +is always the one on the top of the stack. +The states of the finite state machine are given +small integer labels; initially, the machine is in state 0, +the stack contains only state 0, and no lookahead token has been read. +.PP +The machine has only four actions available to it, called +.I shift , +.I reduce , +.I accept , +and +.I error . +A move of the parser is done as follows: +.IP 1. +Based on its current state, the parser decides +whether it needs a lookahead token to decide +what action should be done; if it needs one, and does +not have one, it calls +.I yylex +to obtain the next token. +.IP 2. +Using the current state, and the lookahead token +if needed, the parser decides on its next action, and +carries it out. +This may result in states being pushed onto the stack, or popped off of +the stack, and in the lookahead token being processed +or left alone. +.PP +The +.I shift +action is the most common action the parser takes. +Whenever a shift action is taken, there is always +a lookahead token. +For example, in state 56 there may be +an action: +.DS + IF shift 34 +.DE +which says, in state 56, if the lookahead token is IF, +the current state (56) is pushed down on the stack, +and state 34 becomes the current state (on the +top of the stack). +The lookahead token is cleared. +.PP +The +.I reduce +action keeps the stack from growing without +bounds. +Reduce actions are appropriate when the parser has seen +the right hand side of a grammar rule, +and is prepared to announce that it has seen +an instance of the rule, replacing the right hand side +by the left hand side. +It may be necessary to consult the lookahead token +to decide whether to reduce, but +usually it is not; in fact, the default +action (represented by a ``.'') is often a reduce action. +.PP +Reduce actions are associated with individual grammar rules. +Grammar rules are also given small integer +numbers, leading to some confusion. +The action +.DS + \fB.\fR reduce 18 +.DE +refers to +.I "grammar rule" +18, while the action +.DS + IF shift 34 +.DE +refers to +.I state +34. +.PP +Suppose the rule being reduced is +.DS +A \fB:\fR x y z ; +.DE +The reduce action depends on the +left hand symbol (A in this case), and the number of +symbols on the right hand side (three in this case). +To reduce, first pop off the top three states +from the stack +(In general, the number of states popped equals the number of symbols on the +right side of the rule). +In effect, these states were the ones +put on the stack while recognizing +.I x , +.I y , +and +.I z , +and no longer serve any useful purpose. +After popping these states, a state is uncovered +which was the state the parser was in before beginning to +process the rule. +Using this uncovered state, and the symbol +on the left side of the rule, perform what is in +effect a shift of A. +A new state is obtained, pushed onto the stack, and parsing continues. +There are significant differences between the processing of +the left hand symbol and an ordinary shift of a token, +however, so this action is called a +.I goto +action. +In particular, the lookahead token is cleared by a shift, and +is not affected by a goto. +In any case, the uncovered state contains an entry such as: +.DS + A goto 20 +.DE +causing state 20 to be pushed +onto the stack, and become the current state. +.PP +In effect, the reduce action ``turns back the clock'' in the parse, +popping the states off the stack to go back to the +state where the right hand side of the rule was first seen. +The parser then behaves as if it had seen the left side at that time. +If the right hand side of the rule is empty, +no states are popped off of the stack: the uncovered state +is in fact the current state. +.PP +The reduce action is also important in the treatment of user-supplied +actions and values. +When a rule is reduced, the code supplied with the rule is executed +before the stack is adjusted. +In addition to the stack holding the states, another stack, +running in parallel with it, holds the values returned +from the lexical analyzer and the actions. +When a shift takes place, the external variable +.I yylval +is copied onto the value stack. +After the return from the user code, the reduction is carried out. +When the +.I goto +action is done, the external variable +.I yyval +is copied onto the value stack. +The pseudo-variables $1, $2, etc., refer to the value stack. +.PP +The other two parser actions are conceptually much simpler. +The +.I accept +action indicates that the entire input has been seen and +that it matches the specification. +This action appears only when the lookahead token is +the endmarker, and indicates that the parser has successfully +done its job. +The +.I error +action, on the other hand, represents a place where the parser +can no longer continue parsing according to the specification. +The input tokens it has seen, together with the lookahead token, +cannot be followed by anything that would result +in a legal input. +The parser reports an error, and attempts to recover the situation and +resume parsing: the error recovery (as opposed to the detection of error) +will be covered in Section 7. +.PP +It is time for an example! +Consider the specification +.DS +%token DING DONG DELL +%% +rhyme : sound place + ; +sound : DING DONG + ; +place : DELL + ; +.DE +.PP +When Yacc is invoked with the +.B \-v +option, a file called +.I y.output +is produced, with a human-readable description of the parser. +The +.I y.output +file corresponding to the above grammar (with some statistics +stripped off the end) is: +.DS +state 0 + $accept : \_rhyme $end + + DING shift 3 + . error + + rhyme goto 1 + sound goto 2 + +state 1 + $accept : rhyme\_$end + + $end accept + . error + +state 2 + rhyme : sound\_place + + DELL shift 5 + . error + + place goto 4 + +state 3 + sound : DING\_DONG + + DONG shift 6 + . error + +state 4 + rhyme : sound place\_ (1) + + . reduce 1 + +state 5 + place : DELL\_ (3) + + . reduce 3 + +state 6 + sound : DING DONG\_ (2) + + . reduce 2 +.DE +Notice that, in addition to the actions for each state, there is a +description of the parsing rules being processed in each +state. The \_ character is used to indicate +what has been seen, and what is yet to come, in each rule. +Suppose the input is +.DS +DING DONG DELL +.DE +It is instructive to follow the steps of the parser while +processing this input. +.PP +Initially, the current state is state 0. +The parser needs to refer to the input in order to decide +between the actions available in state 0, so +the first token, +.I DING , +is read, becoming the lookahead token. +The action in state 0 on +.I DING +is +is ``shift 3'', so state 3 is pushed onto the stack, +and the lookahead token is cleared. +State 3 becomes the current state. +The next token, +.I DONG , +is read, becoming the lookahead token. +The action in state 3 on the token +.I DONG +is ``shift 6'', +so state 6 is pushed onto the stack, and the lookahead is cleared. +The stack now contains 0, 3, and 6. +In state 6, without even consulting the lookahead, +the parser reduces by rule 2. +.DS + sound : DING DONG +.DE +This rule has two symbols on the right hand side, so +two states, 6 and 3, are popped off of the stack, uncovering state 0. +Consulting the description of state 0, looking for a goto on +.I sound , +.DS + sound goto 2 +.DE +is obtained; thus state 2 is pushed onto the stack, +becoming the current state. +.PP +In state 2, the next token, +.I DELL , +must be read. +The action is ``shift 5'', so state 5 is pushed onto the stack, which now has +0, 2, and 5 on it, and the lookahead token is cleared. +In state 5, the only action is to reduce by rule 3. +This has one symbol on the right hand side, so one state, 5, +is popped off, and state 2 is uncovered. +The goto in state 2 on +.I place , +the left side of rule 3, +is state 4. +Now, the stack contains 0, 2, and 4. +In state 4, the only action is to reduce by rule 1. +There are two symbols on the right, so the top two states are popped off, +uncovering state 0 again. +In state 0, there is a goto on +.I rhyme +causing the parser to enter state 1. +In state 1, the input is read; the endmarker is obtained, +indicated by ``$end'' in the +.I y.output +file. +The action in state 1 when the endmarker is seen is to accept, +successfully ending the parse. +.PP +The reader is urged to consider how the parser works +when confronted with such incorrect strings as +.I "DING DONG DONG" , +.I "DING DONG" , +.I "DING DONG DELL DELL" , +etc. +A few minutes spend with this and other simple examples will +probably be repaid when problems arise in more complicated contexts. --- /usr/src/share/doc/psd/15.yacc/ss5 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss5 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,302 @@ +.\" @(#)ss5 6.1 (Berkeley) 5/8/86 +.\" +.SH +5: Ambiguity and Conflicts +.PP +A set of grammar rules is +.I ambiguous +if there is some input string that can be structured in two or more different ways. +For example, the grammar rule +.DS +expr : expr \'\-\' expr +.DE +is a natural way of expressing the fact that one way of forming an arithmetic expression +is to put two other expressions together with a minus sign between them. +Unfortunately, this grammar rule does not +completely specify the way that all complex inputs +should be structured. +For example, if the input is +.DS +expr \- expr \- expr +.DE +the rule allows this input to be structured as either +.DS +( expr \- expr ) \- expr +.DE +or as +.DS +expr \- ( expr \- expr ) +.DE +(The first is called +.I "left association" , +the second +.I "right association" ). +.PP +Yacc detects such ambiguities when it is attempting to build the parser. +It is instructive to consider the problem that confronts the parser when it is +given an input such as +.DS +expr \- expr \- expr +.DE +When the parser has read the second expr, the input that it has seen: +.DS +expr \- expr +.DE +matches the right side of the grammar rule above. +The parser could +.I reduce +the input by applying this rule; +after applying the rule; +the input is reduced to +.I expr (the +left side of the rule). +The parser would then read the final part of the input: +.DS +\- expr +.DE +and again reduce. +The effect of this is to take the left associative interpretation. +.PP +Alternatively, when the parser has seen +.DS +expr \- expr +.DE +it could defer the immediate application of the rule, and continue reading +the input until it had seen +.DS +expr \- expr \- expr +.DE +It could then apply the rule to the rightmost three symbols, reducing them to +.I expr +and leaving +.DS +expr \- expr +.DE +Now the rule can be reduced once more; the effect is to +take the right associative interpretation. +Thus, having read +.DS +expr \- expr +.DE +the parser can do two legal things, a shift or a reduction, and has no way of +deciding between them. +This is called a +.I "shift / reduce conflict" . +It may also happen that the parser has a choice of two legal reductions; +this is called a +.I "reduce / reduce conflict" . +Note that there are never any ``Shift/shift'' conflicts. +.PP +When there are shift/reduce or reduce/reduce conflicts, Yacc still produces a parser. +It does this by selecting one of the valid steps wherever it has a choice. +A rule describing which choice to make in a given situation is called +a +.I "disambiguating rule" . +.PP +Yacc invokes two disambiguating rules by default: +.IP 1. +In a shift/reduce conflict, the default is to do the shift. +.IP 2. +In a reduce/reduce conflict, the default is to reduce by the +.I earlier +grammar rule (in the input sequence). +.PP +Rule 1 implies that reductions are deferred whenever there is a choice, +in favor of shifts. +Rule 2 gives the user rather crude control over the behavior of the parser +in this situation, but reduce/reduce conflicts should be avoided whenever possible. +.PP +Conflicts may arise because of mistakes in input or logic, or because the grammar rules, while consistent, +require a more complex parser than Yacc can construct. +The use of actions within rules can also cause conflicts, if the action must +be done before the parser can be sure which rule is being recognized. +In these cases, the application of disambiguating rules is inappropriate, +and leads to an incorrect parser. +For this reason, Yacc +always reports the number of shift/reduce and reduce/reduce conflicts resolved by Rule 1 and Rule 2. +.PP +In general, whenever it is possible to apply disambiguating rules to produce a correct parser, it is also +possible to rewrite the grammar rules so that the same inputs are read but there are no +conflicts. +For this reason, most previous parser generators +have considered conflicts to be fatal errors. +Our experience has suggested that this rewriting is somewhat unnatural, +and produces slower parsers; thus, Yacc will produce parsers even in the presence of conflicts. +.PP +As an example of the power of disambiguating rules, consider a fragment from a programming +language involving an ``if-then-else'' construction: +.DS +stat : IF \'(\' cond \')\' stat + | IF \'(\' cond \')\' stat ELSE stat + ; +.DE +In these rules, +.I IF +and +.I ELSE +are tokens, +.I cond +is a nonterminal symbol describing +conditional (logical) expressions, and +.I stat +is a nonterminal symbol describing statements. +The first rule will be called the +.ul +simple-if +rule, and the +second the +.ul +if-else +rule. +.PP +These two rules form an ambiguous construction, since input of the form +.DS +IF ( C1 ) IF ( C2 ) S1 ELSE S2 +.DE +can be structured according to these rules in two ways: +.DS +IF ( C1 ) { + IF ( C2 ) S1 + } +ELSE S2 +.DE +or +.DS +IF ( C1 ) { + IF ( C2 ) S1 + ELSE S2 + } +.DE +The second interpretation is the one given in most programming languages +having this construct. +Each +.I ELSE +is associated with the last preceding +``un-\fIELSE'\fRd'' +.I IF . +In this example, consider the situation where the parser has seen +.DS +IF ( C1 ) IF ( C2 ) S1 +.DE +and is looking at the +.I ELSE . +It can immediately +reduce +by the simple-if rule to get +.DS +IF ( C1 ) stat +.DE +and then read the remaining input, +.DS +ELSE S2 +.DE +and reduce +.DS +IF ( C1 ) stat ELSE S2 +.DE +by the if-else rule. +This leads to the first of the above groupings of the input. +.PP +On the other hand, the +.I ELSE +may be shifted, +.I S2 +read, and then the right hand portion of +.DS +IF ( C1 ) IF ( C2 ) S1 ELSE S2 +.DE +can be reduced by the if-else rule to get +.DS +IF ( C1 ) stat +.DE +which can be reduced by the simple-if rule. +This leads to the second of the above groupings of the input, which +is usually desired. +.PP +Once again the parser can do two valid things \- there is a shift/reduce conflict. +The application of disambiguating rule 1 tells the parser to shift in this case, +which leads to the desired grouping. +.PP +This shift/reduce conflict arises only when there is a particular current input symbol, +.I ELSE , +and particular inputs already seen, such as +.DS +IF ( C1 ) IF ( C2 ) S1 +.DE +In general, there may be many conflicts, and each one +will be associated with an input symbol and +a set of previously read inputs. +The previously read inputs are characterized by the +state +of the parser. +.PP +The conflict messages of Yacc are best understood +by examining the verbose (\fB\-v\fR) option output file. +For example, the output corresponding to the above +conflict state might be: +.DS L +23: shift/reduce conflict (shift 45, reduce 18) on ELSE + +state 23 + + stat : IF ( cond ) stat\_ (18) + stat : IF ( cond ) stat\_ELSE stat + + ELSE shift 45 + . reduce 18 + +.DE +The first line describes the conflict, giving the state and the input symbol. +The ordinary state description follows, giving +the grammar rules active in the state, and the parser actions. +Recall that the underline marks the +portion of the grammar rules which has been seen. +Thus in the example, in state 23 the parser has seen input corresponding +to +.DS +IF ( cond ) stat +.DE +and the two grammar rules shown are active at this time. +The parser can do two possible things. +If the input symbol is +.I ELSE , +it is possible to shift into state +45. +State 45 will have, as part of its description, the line +.DS +stat : IF ( cond ) stat ELSE\_stat +.DE +since the +.I ELSE +will have been shifted in this state. +Back in state 23, the alternative action, described by ``\fB.\fR'', +is to be done if the input symbol is not mentioned explicitly in the above actions; thus, +in this case, if the input symbol is not +.I ELSE , +the parser reduces by grammar rule 18: +.DS +stat : IF \'(\' cond \')\' stat +.DE +Once again, notice that the numbers following ``shift'' commands refer to other states, +while the numbers following ``reduce'' commands refer to grammar +rule numbers. +In the +.I y.output +file, the rule numbers are printed after those rules which can be reduced. +In most one states, there will be at most reduce action possible in the +state, and this will be the default command. +The user who encounters unexpected shift/reduce conflicts will probably want to +look at the verbose output to decide whether the default actions are appropriate. +In really tough cases, the user might need to know more about +the behavior and construction of the parser than can be covered here. +In this case, one of the theoretical references +.[ +Aho Johnson Surveys Parsing +.] +.[ +Aho Johnson Ullman Deterministic Ambiguous +.] +.[ +Aho Ullman Principles Design +.] +might be consulted; the services of a local guru might also be appropriate. --- /usr/src/share/doc/psd/15.yacc/ss6 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss6 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,146 @@ +.\" @(#)ss6 6.1 (Berkeley) 5/8/86 +.\" +.SH +6: Precedence +.PP +There is one common situation +where the rules given above for resolving conflicts are not sufficient; +this is in the parsing of arithmetic expressions. +Most of the commonly used constructions for arithmetic expressions can be naturally +described by the notion of +.I precedence +levels for operators, together with information about left +or right associativity. +It turns out that ambiguous grammars with appropriate disambiguating rules +can be used to create parsers that are faster and easier to +write than parsers constructed from unambiguous grammars. +The basic notion is to write grammar rules +of the form +.DS +expr : expr OP expr +.DE +and +.DS +expr : UNARY expr +.DE +for all binary and unary operators desired. +This creates a very ambiguous grammar, with many parsing conflicts. +As disambiguating rules, the user specifies the precedence, or binding +strength, of all the operators, and the associativity +of the binary operators. +This information is sufficient to allow Yacc to resolve the parsing conflicts +in accordance with these rules, and construct a parser that realizes the desired +precedences and associativities. +.PP +The precedences and associativities are attached to tokens in the declarations section. +This is done by a series of lines beginning with a Yacc keyword: %left, %right, +or %nonassoc, followed by a list of tokens. +All of the tokens on the same line are assumed to have the same precedence level +and associativity; the lines are listed in +order of increasing precedence or binding strength. +Thus, +.DS +%left \'+\' \'\-\' +%left \'*\' \'/\' +.DE +describes the precedence and associativity of the four arithmetic operators. +Plus and minus are left associative, and have lower precedence than +star and slash, which are also left associative. +The keyword %right is used to describe right associative operators, +and the keyword %nonassoc is used to describe operators, like +the operator .LT. in Fortran, that may not associate with themselves; thus, +.DS +A .LT. B .LT. C +.DE +is illegal in Fortran, and such an operator would be described with the keyword +%nonassoc in Yacc. +As an example of the behavior of these declarations, the description +.DS +%right \'=\' +%left \'+\' \'\-\' +%left \'*\' \'/\' + +%% + +expr : expr \'=\' expr + | expr \'+\' expr + | expr \'\-\' expr + | expr \'*\' expr + | expr \'/\' expr + | NAME + ; +.DE +might be used to structure the input +.DS +a = b = c*d \- e \- f*g +.DE +as follows: +.DS +a = ( b = ( ((c*d)\-e) \- (f*g) ) ) +.DE +When this mechanism is used, +unary operators must, in general, be given a precedence. +Sometimes a unary operator and a binary operator +have the same symbolic representation, but different precedences. +An example is unary and binary \'\-\'; unary minus may be given the same +strength as multiplication, or even higher, while binary minus has a lower strength than +multiplication. +The keyword, %prec, changes the precedence level associated with a particular grammar rule. +%prec appears immediately after the body of the grammar rule, before the action or closing semicolon, +and is followed by a token name or literal. +It +causes the precedence of the grammar rule to become that of the following token name or literal. +For example, to make unary minus have the same precedence as multiplication the rules might resemble: +.DS +%left \'+\' \'\-\' +%left \'*\' \'/\' + +%% + +expr : expr \'+\' expr + | expr \'\-\' expr + | expr \'*\' expr + | expr \'/\' expr + | \'\-\' expr %prec \'*\' + | NAME + ; +.DE +.PP +A token declared +by %left, %right, and %nonassoc need not be, but may be, declared by %token as well. +.PP +The precedences and associativities are used by Yacc to +resolve parsing conflicts; they give rise to disambiguating rules. +Formally, the rules work as follows: +.IP 1. +The precedences and associativities are recorded for those tokens and literals +that have them. +.IP 2. +A precedence and associativity is associated with each grammar rule; it is the precedence +and associativity of the last token or literal in the body of the rule. +If the %prec construction is used, it overrides this default. +Some grammar rules may have no precedence and associativity associated with them. +.IP 3. +When there is a reduce/reduce conflict, or there is a shift/reduce conflict +and either the input symbol or the grammar rule has no precedence and associativity, +then the two disambiguating rules given at the beginning of the section are used, +and the conflicts are reported. +.IP 4. +If there is a shift/reduce conflict, and both the grammar rule and the input character +have precedence and associativity associated with them, then the conflict is resolved +in favor of the action (shift or reduce) associated with the higher precedence. +If the precedences are the same, then the associativity is used; left +associative implies reduce, right associative implies shift, and nonassociating +implies error. +.PP +Conflicts resolved by precedence are not counted in the number of shift/reduce and reduce/reduce +conflicts reported by Yacc. +This means that mistakes in the specification of precedences may +disguise errors in the input grammar; it is a good idea to be sparing +with precedences, and use them in an essentially ``cookbook'' fashion, +until some experience has been gained. +The +.I y.output +file +is very useful in deciding whether the parser is actually doing +what was intended. --- /usr/src/share/doc/psd/15.yacc/ss7 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss7 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,124 @@ +.\" @(#)ss7 6.1 (Berkeley) 5/8/86 +.\" +.SH +7: Error Handling +.PP +Error handling is an extremely difficult area, and many of the problems are semantic ones. +When an error is found, for example, it may be necessary to reclaim parse tree storage, +delete or alter symbol table entries, and, typically, set switches to avoid generating any further output. +.PP +It is seldom acceptable to stop all processing when an error is found; it is more useful to continue +scanning the input to find further syntax errors. +This leads to the problem of getting the parser ``restarted'' after an error. +A general class of algorithms to do this involves discarding a number of tokens +from the input string, and attempting to adjust the parser so that input can continue. +.PP +To allow the user some control over this process, +Yacc provides a simple, but reasonably general, feature. +The token name ``error'' is reserved for error handling. +This name can be used in grammar rules; +in effect, it suggests places where errors are expected, and recovery might take place. +The parser pops its stack until it enters a state where the token ``error'' is legal. +It then behaves as if the token ``error'' were the current lookahead token, +and performs the action encountered. +The lookahead token is then reset to the token that caused the error. +If no special error rules have been specified, the processing halts when an error is detected. +.PP +In order to prevent a cascade of error messages, the parser, after +detecting an error, remains in error state until three tokens have been successfully +read and shifted. +If an error is detected when the parser is already in error state, +no message is given, and the input token is quietly deleted. +.PP +As an example, a rule of the form +.DS +stat : error +.DE +would, in effect, mean that on a syntax error the parser would attempt to skip over the statement +in which the error was seen. +More precisely, the parser will +scan ahead, looking for three tokens that might legally follow +a statement, and start processing at the first of these; if +the beginnings of statements are not sufficiently distinctive, it may make a +false start in the middle of a statement, and end up reporting a +second error where there is in fact no error. +.PP +Actions may be used with these special error rules. +These actions might attempt to reinitialize tables, reclaim symbol table space, etc. +.PP +Error rules such as the above are very general, but difficult to control. +Somewhat easier are rules such as +.DS +stat : error \';\' +.DE +Here, when there is an error, the parser attempts to skip over the statement, but +will do so by skipping to the next \';\'. +All tokens after the error and before the next \';\' cannot be shifted, and are discarded. +When the \';\' is seen, this rule will be reduced, and any ``cleanup'' +action associated with it performed. +.PP +Another form of error rule arises in interactive applications, where +it may be desirable to permit a line to be reentered after an error. +A possible error rule might be +.DS +input : error \'\en\' { printf( "Reenter last line: " ); } input + { $$ = $4; } +.DE +There is one potential difficulty with this approach; +the parser must correctly process three input tokens before it +admits that it has correctly resynchronized after the error. +If the reentered line contains an error +in the first two tokens, the parser deletes the offending tokens, +and gives no message; this is clearly unacceptable. +For this reason, there is a mechanism that +can be used to force the parser +to believe that an error has been fully recovered from. +The statement +.DS +yyerrok ; +.DE +in an action +resets the parser to its normal mode. +The last example is better written +.DS +input : error \'\en\' + { yyerrok; + printf( "Reenter last line: " ); } + input + { $$ = $4; } + ; +.DE +.PP +As mentioned above, the token seen immediately +after the ``error'' symbol is the input token at which the +error was discovered. +Sometimes, this is inappropriate; for example, an +error recovery action might +take upon itself the job of finding the correct place to resume input. +In this case, +the previous lookahead token must be cleared. +The statement +.DS +yyclearin ; +.DE +in an action will have this effect. +For example, suppose the action after error +were to call some sophisticated resynchronization routine, +supplied by the user, that attempted to advance the input to the +beginning of the next valid statement. +After this routine was called, the next token returned by yylex would presumably +be the first token in a legal statement; +the old, illegal token must be discarded, and the error state reset. +This could be done by a rule like +.DS +stat : error + { resynch(); + yyerrok ; + yyclearin ; } + ; +.DE +.PP +These mechanisms are admittedly crude, but do allow for a simple, fairly effective recovery of the parser +from many errors; +moreover, the user can get control to deal with +the error actions required by other portions of the program. --- /usr/src/share/doc/psd/15.yacc/ss8 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss8 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,93 @@ +.\" @(#)ss8 6.1 (Berkeley) 5/8/86 +.\" +.SH +8: The Yacc Environment +.PP +When the user inputs a specification +to Yacc, the output is a file of C programs, called +.I y.tab.c +on most +systems +(due to local file system conventions, the names may differ from +installation to installation). +The function produced by Yacc is called +.I yyparse \|; +it is an integer valued function. +When it is called, it in turn repeatedly calls +.I yylex , +the lexical analyzer +supplied by the user (see Section 3) +to obtain input tokens. +Eventually, either an error is detected, in which case +(if no error recovery is possible) +.I yyparse +returns the value 1, +or the lexical analyzer returns the endmarker token +and the parser accepts. +In this case, +.I yyparse +returns the value 0. +.PP +The user must provide a certain amount of environment for this +parser in order to obtain a working program. +For example, as with every C program, a program called +.I main +must be defined, that eventually calls +.I yyparse . +In addition, a routine called +.I yyerror +prints a message +when a syntax error is detected. +.PP +These two routines must be supplied in one form or another by the +user. +To ease the initial effort of using Yacc, a library has been +provided with default versions of +.I main +and +.I yyerror . +The name of this library is system dependent; +on many systems the library is accessed by a +.B \-ly +argument to the loader. +To show the triviality of these default programs, the source is +given below: +.DS +main(){ + return( yyparse() ); + } +.DE +and +.DS +# include <stdio.h> + +yyerror(s) char *s; { + fprintf( stderr, "%s\en", s ); + } +.DE +The argument to +.I yyerror +is a string containing an error message, usually +the string ``syntax error''. +The average application will want to do better than this. +Ordinarily, the program should keep track of the input line number, and print it +along with the message when a syntax error is detected. +The external integer variable +.I yychar +contains the lookahead token number at the time the error was detected; +this may be of some interest in giving better diagnostics. +Since the +.I main +program is probably supplied by the user (to read arguments, etc.) +the Yacc library is useful only in small +projects, or in the earliest stages of larger ones. +.PP +The external integer variable +.I yydebug +is normally set to 0. +If it is set to a nonzero value, the parser will output a +verbose description of its actions, including +a discussion of which input symbols have been read, and +what the parser actions are. +Depending on the operating environment, +it may be possible to set this variable by using a debugging system. --- /usr/src/share/doc/psd/15.yacc/ss9 Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ss9 Tue Feb 26 13:49:21 2002 @@ -0,0 +1,169 @@ +.\" @(#)ss9 6.1 (Berkeley) 5/8/86 +.\" +.SH +9: Hints for Preparing Specifications +.PP +This section contains miscellaneous hints on preparing efficient, easy to change, +and clear specifications. +The individual subsections are more or less +independent. +.SH +Input Style +.PP +It is difficult to +provide rules with substantial actions +and still have a readable specification file. +The following style hints owe much to Brian Kernighan. +.IP a. +Use all capital letters for token names, all lower case letters for +nonterminal names. +This rule comes under the heading of ``knowing who to blame when +things go wrong.'' +.IP b. +Put grammar rules and actions on separate lines. +This allows either to be changed without +an automatic need to change the other. +.IP c. +Put all rules with the same left hand side together. +Put the left hand side in only once, and let all +following rules begin with a vertical bar. +.IP d. +Put a semicolon only after the last rule with a given left hand side, +and put the semicolon on a separate line. +This allows new rules to be easily added. +.IP e. +Indent rule bodies by two tab stops, and action bodies by three +tab stops. +.PP +The example in Appendix A is written following this style, as are +the examples in the text of this paper (where space permits). +The user must make up his own mind about these stylistic questions; +the central problem, however, is to make the rules visible through +the morass of action code. +.SH +Left Recursion +.PP +The algorithm used by the Yacc parser encourages so called ``left recursive'' +grammar rules: rules of the form +.DS +name : name rest_of_rule ; +.DE +These rules frequently arise when +writing specifications of sequences and lists: +.DS +list : item + | list \',\' item + ; +.DE +and +.DS +seq : item + | seq item + ; +.DE +In each of these cases, the first rule +will be reduced for the first item only, and the second rule +will be reduced for the second and all succeeding items. +.PP +With right recursive rules, such as +.DS +seq : item + | item seq + ; +.DE +the parser would be a bit bigger, and the items would be seen, and reduced, +from right to left. +More seriously, an internal stack in the parser +would be in danger of overflowing if a very long sequence were read. +Thus, the user should use left recursion wherever reasonable. +.PP +It is worth considering whether a sequence with zero +elements has any meaning, and if so, consider writing +the sequence specification with an empty rule: +.DS +seq : /* empty */ + | seq item + ; +.DE +Once again, the first rule would always be reduced exactly once, before the +first item was read, +and then the second rule would be reduced once for each item read. +Permitting empty sequences +often leads to increased generality. +However, conflicts might arise if Yacc is asked to decide +which empty sequence it has seen, when it hasn't seen enough to +know! +.SH +Lexical Tie-ins +.PP +Some lexical decisions depend on context. +For example, the lexical analyzer might want to +delete blanks normally, but not within quoted strings. +Or names might be entered into a symbol table in declarations, +but not in expressions. +.PP +One way of handling this situation is +to create a global flag that is +examined by the lexical analyzer, and set by actions. +For example, suppose a program +consists of 0 or more declarations, followed by 0 or more statements. +Consider: +.DS +%{ + int dflag; +%} + ... other declarations ... + +%% + +prog : decls stats + ; + +decls : /* empty */ + { dflag = 1; } + | decls declaration + ; + +stats : /* empty */ + { dflag = 0; } + | stats statement + ; + + ... other rules ... +.DE +The flag +.I dflag +is now 0 when reading statements, and 1 when reading declarations, +.ul +except for the first token in the first statement. +This token must be seen by the parser before it can tell that +the declaration section has ended and the statements have +begun. +In many cases, this single token exception does not +affect the lexical scan. +.PP +This kind of ``backdoor'' approach can be elaborated +to a noxious degree. +Nevertheless, it represents a way of doing some things +that are difficult, if not impossible, to +do otherwise. +.SH +Reserved Words +.PP +Some programming languages +permit the user to +use words like ``if'', which are normally reserved, +as label or variable names, provided that such use does not +conflict with the legal use of these names in the programming language. +This is extremely hard to do in the framework of Yacc; +it is difficult to pass information to the lexical analyzer +telling it ``this instance of `if' is a keyword, and that instance is a variable''. +The user can make a stab at it, using the +mechanism described in the last subsection, +but it is difficult. +.PP +A number of ways of making this easier are under advisement. +Until then, it is better that the keywords be +.I reserved \|; +that is, be forbidden for use as variable names. +There are powerful stylistic reasons for preferring this, anyway. --- /usr/src/share/doc/psd/15.yacc/ssA Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ssA Tue Feb 26 13:49:21 2002 @@ -0,0 +1,184 @@ +.\" @(#)ssA 6.1 (Berkeley) 5/8/86 +.\" +.SH +10: Advanced Topics +.PP +This section discusses a number of advanced features +of Yacc. +.SH +Simulating Error and Accept in Actions +.PP +The parsing actions of error and accept can be simulated +in an action by use of macros YYACCEPT and YYERROR. +YYACCEPT causes +.I yyparse +to return the value 0; +YYERROR causes +the parser to behave as if the current input symbol +had been a syntax error; +.I yyerror +is called, and error recovery takes place. +These mechanisms can be used to simulate parsers +with multiple endmarkers or context-sensitive syntax checking. +.SH +Accessing Values in Enclosing Rules. +.PP +An action may refer to values +returned by actions to the left of the current rule. +The mechanism is simply the same as with ordinary actions, +a dollar sign followed by a digit, but in this case the +digit may be 0 or negative. +Consider +.DS +sent : adj noun verb adj noun + { \fIlook at the sentence\fR . . . } + ; + +adj : THE { $$ = THE; } + | YOUNG { $$ = YOUNG; } + . . . + ; + +noun : DOG + { $$ = DOG; } + | CRONE + { if( $0 == YOUNG ){ + printf( "what?\en" ); + } + $$ = CRONE; + } + ; + . . . +.DE +In the action following the word CRONE, a check is made that the +preceding token shifted was not YOUNG. +Obviously, this is only possible when a great deal is known about +what might precede the symbol +.I noun +in the input. +There is also a distinctly unstructured flavor about this. +Nevertheless, at times this mechanism will save a great +deal of trouble, especially when a few combinations are to +be excluded from an otherwise regular structure. +.SH +Support for Arbitrary Value Types +.PP +By default, the values returned by actions and the lexical analyzer are integers. +Yacc can also support +values of other types, including structures. +In addition, Yacc keeps track of the types, and inserts +appropriate union member names so that the resulting parser will +be strictly type checked. +The Yacc value stack (see Section 4) +is declared to be a +.I union +of the various types of values desired. +The user declares the union, and associates union member names +to each token and nonterminal symbol having a value. +When the value is referenced through a $$ or $n construction, +Yacc will automatically insert the appropriate union name, so that +no unwanted conversions will take place. +In addition, type checking commands such as +.I Lint\| +.[ +Johnson Lint Checker 1273 +.] +will be far more silent. +.PP +There are three mechanisms used to provide for this typing. +First, there is a way of defining the union; this must be +done by the user since other programs, notably the lexical analyzer, +must know about the union member names. +Second, there is a way of associating a union member name with tokens +and nonterminals. +Finally, there is a mechanism for describing the type of those +few values where Yacc can not easily determine the type. +.PP +To declare the union, the user includes in the declaration section: +.DS +%union { + body of union ... + } +.DE +This declares the Yacc value stack, +and the external variables +.I yylval +and +.I yyval , +to have type equal to this union. +If Yacc was invoked with the +.B \-d +option, the union declaration +is copied onto the +.I y.tab.h +file. +Alternatively, +the union may be declared in a header file, and a typedef +used to define the variable YYSTYPE to represent +this union. +Thus, the header file might also have said: +.DS +typedef union { + body of union ... + } YYSTYPE; +.DE +The header file must be included in the declarations +section, by use of %{ and %}. +.PP +Once YYSTYPE is defined, +the union member names must be associated +with the various terminal and nonterminal names. +The construction +.DS +< name > +.DE +is used to indicate a union member name. +If this follows +one of the +keywords %token, +%left, %right, and %nonassoc, +the union member name is associated with the tokens listed. +Thus, saying +.DS +%left <optype> \'+\' \'\-\' +.DE +will cause any reference to values returned by these two tokens to be +tagged with +the union member name +.I optype . +Another keyword, %type, is +used similarly to associate +union member names with nonterminals. +Thus, one might say +.DS +%type <nodetype> expr stat +.DE +.PP +There remain a couple of cases where these mechanisms are insufficient. +If there is an action within a rule, the value returned +by this action has no +.I "a priori" +type. +Similarly, reference to left context values (such as $0 \- see the +previous subsection ) leaves Yacc with no easy way of knowing the type. +In this case, a type can be imposed on the reference by inserting +a union member name, between < and >, immediately after +the first $. +An example of this usage is +.DS +rule : aaa { $<intval>$ = 3; } bbb + { fun( $<intval>2, $<other>0 ); } + ; +.DE +This syntax has little to recommend it, but the situation arises rarely. +.PP +A sample specification is given in Appendix C. +The facilities in this subsection are not triggered until they are used: +in particular, the use of %type will turn on these mechanisms. +When they are used, there is a fairly strict level of checking. +For example, use of $n or $$ to refer to something with no defined type +is diagnosed. +If these facilities are not triggered, the Yacc value stack is used to +hold +.I int' s, +as was true historically. --- /usr/src/share/doc/psd/15.yacc/ssB Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ssB Tue Feb 26 13:49:21 2002 @@ -0,0 +1,26 @@ +.\" @(#)ssB 6.1 (Berkeley) 5/8/86 +.\" +.SH +11: Acknowledgements +.PP +Yacc owes much to a +most stimulating collection of users, who have goaded +me beyond my inclination, and frequently beyond my +ability, in their endless search for ``one more feature''. +Their irritating unwillingness to learn how to +do things my way has usually led to my doing things their way; +most of the time, they have been right. +B. W. Kernighan, P. J. Plauger, S. I. Feldman, C. Imagna, +M. E. Lesk, +and A. Snyder will recognize some of their ideas in the current version +of Yacc. +C. B. Haley contributed to the error recovery algorithm. +D. M. Ritchie, B. W. Kernighan, and M. O. Harris helped translate this document into English. +Al Aho also deserves special credit for bringing +the mountain to Mohammed, and other favors. +.SG "MH-1273-SCJ-unix" +.bp +.[ +$LIST$ +.] +.bp --- /usr/src/share/doc/psd/15.yacc/ssa Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ssa Tue Feb 26 13:49:21 2002 @@ -0,0 +1,113 @@ +.\" @(#)ssa 6.1 (Berkeley) 5/8/86 +.\" +.SH +Appendix A: A Simple Example +.PP +This example gives the complete Yacc specification for a small desk calculator; +the desk calculator has 26 registers, labeled ``a'' through ``z'', and accepts +arithmetic expressions made up of the operators +, \-, *, /, +% (mod operator), & (bitwise and), | (bitwise or), and assignment. +If an expression at the top level is an assignment, the value is not +printed; otherwise it is. +As in C, an integer that begins with 0 (zero) is assumed to be octal; +otherwise, it is assumed to be decimal. +.PP +As an example of a Yacc specification, the desk calculator +does a reasonable job of showing how precedences and ambiguities +are used, and demonstrating simple error recovery. +The major oversimplifications are that the +lexical analysis phase is much simpler than for most applications, and the +output is produced immediately, line by line. +Note the way that decimal and octal integers are read in by the grammar rules; +This job is probably better done by the lexical analyzer. +.sp +.nf +.ta .5i 1i 1.5i 2i 2.5i + +%{ +# include <stdio.h> +# include <ctype.h> + +int regs[26]; +int base; + +%} + +%start list + +%token DIGIT LETTER + +%left \'|\' +%left \'&\' +%left \'+\' \'\-\' +%left \'*\' \'/\' \'%\' +%left UMINUS /* supplies precedence for unary minus */ + +%% /* beginning of rules section */ + +list : /* empty */ + | list stat \'\en\' + | list error \'\en\' + { yyerrok; } + ; + +stat : expr + { printf( "%d\en", $1 ); } + | LETTER \'=\' expr + { regs[$1] = $3; } + ; + +expr : \'(\' expr \')\' + { $$ = $2; } + | expr \'+\' expr + { $$ = $1 + $3; } + | expr \'\-\' expr + { $$ = $1 \- $3; } + | expr \'*\' expr + { $$ = $1 * $3; } + | expr \'/\' expr + { $$ = $1 / $3; } + | expr \'%\' expr + { $$ = $1 % $3; } + | expr \'&\' expr + { $$ = $1 & $3; } + | expr \'|\' expr + { $$ = $1 | $3; } + | \'\-\' expr %prec UMINUS + { $$ = \- $2; } + | LETTER + { $$ = regs[$1]; } + | number + ; + +number : DIGIT + { $$ = $1; base = ($1==0) ? 8 : 10; } + | number DIGIT + { $$ = base * $1 + $2; } + ; + +%% /* start of programs */ + +yylex() { /* lexical analysis routine */ + /* returns LETTER for a lower case letter, yylval = 0 through 25 */ + /* return DIGIT for a digit, yylval = 0 through 9 */ + /* all other characters are returned immediately */ + + int c; + + while( (c=getchar()) == \' \' ) { /* skip blanks */ } + + /* c is now nonblank */ + + if( islower( c ) ) { + yylval = c \- \'a\'; + return ( LETTER ); + } + if( isdigit( c ) ) { + yylval = c \- \'0\'; + return( DIGIT ); + } + return( c ); + } +.fi +.bp --- /usr/src/share/doc/psd/15.yacc/ssb Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ssb Tue Feb 26 13:49:21 2002 @@ -0,0 +1,110 @@ +.\" @(#)ssb 6.1 (Berkeley) 5/8/86 +.\" +.SH +Appendix B: Yacc Input Syntax +.PP +This Appendix has a description of the Yacc input syntax, as a Yacc specification. +Context dependencies, etc., are not considered. +Ironically, the Yacc input specification language +is most naturally specified as an LR(2) grammar; the sticky +part comes when an identifier is seen in a rule, immediately +following an action. +If this identifier is followed by a colon, it is the start of the +next rule; otherwise +it is a continuation of the current rule, which just happens to have +an action embedded in it. +As implemented, the lexical analyzer looks +ahead after seeing an identifier, and +decide whether the next token (skipping blanks, newlines, comments, etc.) +is a colon. +If so, it returns the token C_IDENTIFIER. +Otherwise, it returns IDENTIFIER. +Literals (quoted strings) are also returned as IDENTIFIERS, +but never as part of C_IDENTIFIERs. +.sp +.nf +.ta .6i 1.2i 1.8i 2.4i 3i 3.6i + + /* grammar for the input to Yacc */ + + /* basic entities */ +%token IDENTIFIER /* includes identifiers and literals */ +%token C_IDENTIFIER /* identifier (but not literal) followed by colon */ +%token NUMBER /* [0-9]+ */ + + /* reserved words: %type => TYPE, %left => LEFT, etc. */ + +%token LEFT RIGHT NONASSOC TOKEN PREC TYPE START UNION + +%token MARK /* the %% mark */ +%token LCURL /* the %{ mark */ +%token RCURL /* the %} mark */ + + /* ascii character literals stand for themselves */ + +%start spec + +%% + +spec : defs MARK rules tail + ; + +tail : MARK { \fIIn this action, eat up the rest of the file\fR } + | /* empty: the second MARK is optional */ + ; + +defs : /* empty */ + | defs def + ; + +def : START IDENTIFIER + | UNION { \fICopy union definition to output\fR } + | LCURL { \fICopy C code to output file\fR } RCURL + | ndefs rword tag nlist + ; + +rword : TOKEN + | LEFT + | RIGHT + | NONASSOC + | TYPE + ; + +tag : /* empty: union tag is optional */ + | \'<\' IDENTIFIER \'>\' + ; + +nlist : nmno + | nlist nmno + | nlist \',\' nmno + ; + +nmno : IDENTIFIER /* NOTE: literal illegal with %type */ + | IDENTIFIER NUMBER /* NOTE: illegal with %type */ + ; + + /* rules section */ + +rules : C_IDENTIFIER rbody prec + | rules rule + ; + +rule : C_IDENTIFIER rbody prec + | '|' rbody prec + ; + +rbody : /* empty */ + | rbody IDENTIFIER + | rbody act + ; + +act : \'{\' { \fICopy action, translate $$, etc.\fR } \'}\' + ; + +prec : /* empty */ + | PREC IDENTIFIER + | PREC IDENTIFIER act + | prec \';\' + ; +.fi +.bp --- /usr/src/share/doc/psd/15.yacc/ssc Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ssc Tue Feb 26 13:49:21 2002 @@ -0,0 +1,311 @@ +.\" @(#)ssc 6.1 (Berkeley) 5/8/86 +.\" +.SH +Appendix C: An Advanced Example +.PP +This Appendix gives an example of a grammar using some +of the advanced features discussed in Section 10. +The desk calculator example in Appendix A is +modified to provide a desk calculator that +does floating point interval arithmetic. +The calculator understands floating point +constants, the arithmetic operations +, \-, *, /, +unary \-, and = (assignment), and has 26 floating +point variables, ``a'' through ``z''. +Moreover, it also understands +.I intervals , +written +.DS + ( x , y ) +.DE +where +.I x +is less than or equal to +.I y . +There are 26 interval valued variables ``A'' through ``Z'' +that may also be used. +The usage is similar to that in Appendix A; assignments +return no value, and print nothing, while expressions print +the (floating or interval) value. +.PP +This example explores a number of interesting features +of Yacc and C. +Intervals are represented by a structure, consisting of the +left and right endpoint values, stored as +.I double 's. +This structure is given a type name, INTERVAL, by using +.I typedef . +The Yacc value stack can also contain floating point scalars, and +integers (used to index into the arrays holding the variable values). +Notice that this entire strategy depends strongly on being able to +assign structures and unions in C. +In fact, many of the actions call functions that return structures +as well. +.PP +It is also worth noting the use of YYERROR to handle error conditions: +division by an interval containing 0, and an interval presented in +the wrong order. +In effect, the error recovery mechanism of Yacc is used to throw away the +rest of the offending line. +.PP +In addition to the mixing of types on the value stack, +this grammar also demonstrates an interesting use of syntax to +keep track of the type (e.g. scalar or interval) of intermediate +expressions. +Note that a scalar can be automatically promoted to an interval if +the context demands an interval value. +This causes a large number of conflicts when the grammar is run through +Yacc: 18 Shift/Reduce and 26 Reduce/Reduce. +The problem can be seen by looking at the two input lines: +.DS + 2.5 + ( 3.5 \- 4. ) +.DE +and +.DS + 2.5 + ( 3.5 , 4. ) +.DE +Notice that the 2.5 is to be used in an interval valued expression +in the second example, but this fact is not known until +the ``,'' is read; by this time, 2.5 is finished, and the parser cannot go back +and change its mind. +More generally, it might be necessary to look ahead an arbitrary number of +tokens to decide whether to convert a scalar to an interval. +This problem is evaded by having two rules for each binary interval +valued operator: one when the left operand is a scalar, and one when +the left operand is an interval. +In the second case, the right operand must be an interval, +so the conversion will be applied automatically. +Despite this evasion, there are still many cases where the +conversion may be applied or not, leading to the above +conflicts. +They are resolved by listing the rules that yield scalars first +in the specification file; in this way, the conflicts will +be resolved in the direction of keeping scalar +valued expressions scalar valued until they are forced to become +intervals. +.PP +This way of handling multiple types is very instructive, but not very general. +If there were many kinds of expression types, instead of just two, +the number of rules needed would increase dramatically, and the conflicts +even more dramatically. +Thus, while this example is instructive, it is better practice in a +more normal programming language environment to +keep the type information as part of the value, and not as part +of the grammar. +.PP +Finally, a word about the lexical analysis. +The only unusual feature is the treatment of floating point constants. +The C library routine +.I atof +is used to do the actual conversion from a character string +to a double precision value. +If the lexical analyzer detects an error, +it responds by returning a token that +is illegal in the grammar, provoking a syntax error +in the parser, and thence error recovery. +.DS L + +%{ + +# include <stdio.h> +# include <ctype.h> + +typedef struct interval { + double lo, hi; + } INTERVAL; + +INTERVAL vmul(), vdiv(); + +double atof(); + +double dreg[ 26 ]; +INTERVAL vreg[ 26 ]; + +%} + +%start lines + +%union { + int ival; + double dval; + INTERVAL vval; + } + +%token <ival> DREG VREG /* indices into dreg, vreg arrays */ + +%token <dval> CONST /* floating point constant */ + +%type <dval> dexp /* expression */ + +%type <vval> vexp /* interval expression */ + + /* precedence information about the operators */ + +%left \'+\' \'\-\' +%left \'*\' \'/\' +%left UMINUS /* precedence for unary minus */ + +%% + +lines : /* empty */ + | lines line + ; + +line : dexp \'\en\' + { printf( "%15.8f\en", $1 ); } + | vexp \'\en\' + { printf( "(%15.8f , %15.8f )\en", $1.lo, $1.hi ); } + | DREG \'=\' dexp \'\en\' + { dreg[$1] = $3; } + | VREG \'=\' vexp \'\en\' + { vreg[$1] = $3; } + | error \'\en\' + { yyerrok; } + ; + +dexp : CONST + | DREG + { $$ = dreg[$1]; } + | dexp \'+\' dexp + { $$ = $1 + $3; } + | dexp \'\-\' dexp + { $$ = $1 \- $3; } + | dexp \'*\' dexp + { $$ = $1 * $3; } + | dexp \'/\' dexp + { $$ = $1 / $3; } + | \'\-\' dexp %prec UMINUS + { $$ = \- $2; } + | \'(\' dexp \')\' + { $$ = $2; } + ; + +vexp : dexp + { $$.hi = $$.lo = $1; } + | \'(\' dexp \',\' dexp \')\' + { + $$.lo = $2; + $$.hi = $4; + if( $$.lo > $$.hi ){ + printf( "interval out of order\en" ); + YYERROR; + } + } + | VREG + { $$ = vreg[$1]; } + | vexp \'+\' vexp + { $$.hi = $1.hi + $3.hi; + $$.lo = $1.lo + $3.lo; } + | dexp \'+\' vexp + { $$.hi = $1 + $3.hi; + $$.lo = $1 + $3.lo; } + | vexp \'\-\' vexp + { $$.hi = $1.hi \- $3.lo; + $$.lo = $1.lo \- $3.hi; } + | dexp \'\-\' vexp + { $$.hi = $1 \- $3.lo; + $$.lo = $1 \- $3.hi; } + | vexp \'*\' vexp + { $$ = vmul( $1.lo, $1.hi, $3 ); } + | dexp \'*\' vexp + { $$ = vmul( $1, $1, $3 ); } + | vexp \'/\' vexp + { if( dcheck( $3 ) ) YYERROR; + $$ = vdiv( $1.lo, $1.hi, $3 ); } + | dexp \'/\' vexp + { if( dcheck( $3 ) ) YYERROR; + $$ = vdiv( $1, $1, $3 ); } + | \'\-\' vexp %prec UMINUS + { $$.hi = \-$2.lo; $$.lo = \-$2.hi; } + | \'(\' vexp \')\' + { $$ = $2; } + ; + +%% + +# define BSZ 50 /* buffer size for floating point numbers */ + + /* lexical analysis */ + +yylex(){ + register c; + + while( (c=getchar()) == \' \' ){ /* skip over blanks */ } + + if( isupper( c ) ){ + yylval.ival = c \- \'A\'; + return( VREG ); + } + if( islower( c ) ){ + yylval.ival = c \- \'a\'; + return( DREG ); + } + + if( isdigit( c ) || c==\'.\' ){ + /* gobble up digits, points, exponents */ + + char buf[BSZ+1], *cp = buf; + int dot = 0, exp = 0; + + for( ; (cp\-buf)<BSZ ; ++cp,c=getchar() ){ + + *cp = c; + if( isdigit( c ) ) continue; + if( c == \'.\' ){ + if( dot++ || exp ) return( \'.\' ); /* will cause syntax error */ + continue; + } + + if( c == \'e\' ){ + if( exp++ ) return( \'e\' ); /* will cause syntax error */ + continue; + } + + /* end of number */ + break; + } + *cp = \'\e0\'; + if( (cp\-buf) >= BSZ ) printf( "constant too long: truncated\en" ); + else ungetc( c, stdin ); /* push back last char read */ + yylval.dval = atof( buf ); + return( CONST ); + } + return( c ); + } + +INTERVAL hilo( a, b, c, d ) double a, b, c, d; { + /* returns the smallest interval containing a, b, c, and d */ + /* used by *, / routines */ + INTERVAL v; + + if( a>b ) { v.hi = a; v.lo = b; } + else { v.hi = b; v.lo = a; } + + if( c>d ) { + if( c>v.hi ) v.hi = c; + if( d<v.lo ) v.lo = d; + } + else { + if( d>v.hi ) v.hi = d; + if( c<v.lo ) v.lo = c; + } + return( v ); + } + +INTERVAL vmul( a, b, v ) double a, b; INTERVAL v; { + return( hilo( a*v.hi, a*v.lo, b*v.hi, b*v.lo ) ); + } + +dcheck( v ) INTERVAL v; { + if( v.hi >= 0. && v.lo <= 0. ){ + printf( "divisor interval contains 0.\en" ); + return( 1 ); + } + return( 0 ); + } + +INTERVAL vdiv( a, b, v ) double a, b; INTERVAL v; { + return( hilo( a/v.hi, a/v.lo, b/v.hi, b/v.lo ) ); + } +.DE +.bp --- /usr/src/share/doc/psd/15.yacc/ssd Thu Jan 1 00:00:00 1970 +++ /usr/src/share/doc/psd.new/15.yacc/ssd Tue Feb 26 13:49:21 2002 @@ -0,0 +1,40 @@ +.\" @(#)ssd 6.1 (Berkeley) 5/8/86 +.\" +.SH +Appendix D: Old Features Supported but not Encouraged +.PP +This Appendix mentions synonyms and features which are supported for historical +continuity, but, for various reasons, are not encouraged. +.IP 1. +Literals may also be delimited by double quotes ``"''. +.IP 2. +Literals may be more than one character long. +If all the characters are alphabetic, numeric, or \_, the type number of the literal is defined, +just as if the literal did not have the quotes around it. +Otherwise, it is difficult to find the value for such literals. +.IP +The use of multi-character literals is likely to mislead those unfamiliar with +Yacc, since it suggests that Yacc is doing a job which must be actually done by the lexical analyzer. +.IP 3. +Most places where % is legal, backslash ``\e'' may be used. +In particular, \e\e is the same as %%, \eleft the same as %left, etc. +.IP 4. +There are a number of other synonyms: +.DS +%< is the same as %left +%> is the same as %right +%binary and %2 are the same as %nonassoc +%0 and %term are the same as %token +%= is the same as %prec +.DE +.IP 5. +Actions may also have the form +.DS +={ . . . } +.DE +and the curly braces can be dropped if the action is a +single C statement. +.IP 6. +C code between %{ and %} used to be permitted at the +head of the rules section, as well as in the +declaration section. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 6:35:35 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 5529737B405 for <freebsd-doc@FreeBSD.ORG>; Tue, 26 Feb 2002 06:35:25 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g1QEZJO55269; Tue, 26 Feb 2002 09:35:19 -0500 (EST) (envelope-from mwlucas) Date: Tue, 26 Feb 2002 09:35:19 -0500 From: Michael Lucas <mwlucas@blackhelicopters.org> To: Tom Rhodes <darklogik@pittgoth.com> Cc: freebsd-doc@FreeBSD.ORG Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Message-ID: <20020226093519.A55250@blackhelicopters.org> References: <200202231550.g1NFo1t30805@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202231550.g1NFo1t30805@freefall.freebsd.org>; from darklogik@pittgoth.com on Sat, Feb 23, 2002 at 07:50:01AM -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org Closer still... On Sat, Feb 23, 2002 at 07:50:01AM -0800, Tom Rhodes wrote: > + <para>On FreeBSD, the setup of <acronym>NFS</acronym> is a relatively straightforward suggest ", NFS setup is relatively"; shorter. > > <programlisting>portmap_enable="YES" > nfs_server_enable="YES" > -nfs_server_flags="-u -t -n 4" > mountd_flags="-r"</programlisting> So, we're no longer giving the default flags, which is good, but you describe the options below? This will leave trailing references, where people will ask "what '-n 4' flag?" > - <para><command>mountd</command> is automatically run whenever the > - NFS server is enabled. The <option>-u</option> and > - <option>-t</option> flags to <command>nfsd</command> tell it to > + <para><command>mountd</command> runs automatically whenever the > + <acronym>NFS</acronym> server is enabled. The <option>-u</option> and > + <option>-t</option> flags tell <command>nfsd</command> to > serve UDP and TCP clients. The <option>-n 4</option> flag tells > <command>nfsd</command> to start 4 copies of itself.</para> > > - <programlisting>nfs_client_enable="YES" > -nfs_client_flags="-n 4"</programlisting> > + <programlisting>nfs_client_enable="YES"</programlisting> Gratuitous whitespace; please be kind to translators. Should look more like (generated off the top of my head, not a real patch, will not apply, blah blah blah) > <programlisting>nfs_client_enable="YES" > -nfs_client_flags="-n 4"</programlisting> > + </programlisting> Diff size reduced by 33%, translators will appreciate it. Whoever commits this patch will re-wrap it for you. > > - <para>Like <command>nfsd</command>, the <option>-n 4</option> tells > + <para>As with <command>nfsd</command>, the <option>-n 4</option> tells > <command>nfsiod</command> to start 4 copies of itself.</para> Ditto here on "dangling references to example that no longer exists." > + <para>The <acronym>NFS</acronym> configuration requires that an > + <filename>exports</filename> file be created in the I still really dislike "be created". "be created" by what? "be", like "is", indicates passive voice. If the admin creates the file, say so. If a program creates the file, say so. We generally assume an "explicit administrator creation" throughout the docs, so this sentence could be eliminated. > + <filename>/etc</filename> directory. The <filename>/etc/exports</filename> > + file will specify which filesystems <acronym>NFS</acronym> should export (sometimes will specify -> specifies > <indexterm> > - <primary>NFS</primary> > - <secondary>exporting filesystems</secondary> > + <primary>Examples of exporting filesystems</primary> > </indexterm> So, you think this should show up in the index as "Examples of exporting filesystems" and not be referenced under NFS? That's not a very typical index entry... > - <option>-alldirs</option> flag allows all the directories below > - the specified file system to be exported as well.</para> > + Optionally the <filename>/etc/hosts</filename> file could be configured > + for internal hostnames, please view the &man.hosts.5; man page for more > + information. This sentence is ugly. Perhaps a semicolon instead of a comma? Also, we don't usually say "the X man page"; we just say "see X," and let the DocBook system do its magic. The <option>-alldirs</option> flag allows for the directories > + below the specified filesystem to also be exported.</para> "for" is unnecessary. > - <para>Now that you have made all these changes you can just reboot > - and let FreeBSD start everything for you at boot time, or you can > - run the following commands as root:</para> > + <para>Alternatively, a reboot will make FreeBSD set everything > + up properly. Although, a reboot is not necessary. Never start a sentence with "although" or "however"; bad grammar. > + Executing the following commands, as <username>root</username> of course, "of course" is like "it goes without saying"; if it's that obvious, don't write it. And if it goes without saying, then don't say it. > system. This can be done one of two ways. In these examples the The whole "This can be done one of two ways" sentence can go entirely; it's not true. You can do temporary mounts, or automatic mounts, but they can only be done in one way. > - <para>There are many very cool uses for NFS. Some of the more common > - ones are listed below.</para> > + <para><acronym>NFS</acronym> has many practical. Some of the > + more common ones are listed below:</para> Practical what? Fragment. Fragments bad. also, gratuitous whitespace. The first line in this will probably be very long, but whoever commits will word-wrap it in a second commit. > - <para>&man.amd.8;, which is also known as the automatic mounter > - daemon, is a useful utility used for automatically mounting a > + <para>&man.amd.8; (the automatic mounter daemon) > + is a useful utility that automatically mounts a It better be 'useful', or why are we discussing it? :-) I'd cut that bit out. "amd (the automatic mounter daemon) automatically mounts a..." ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 6:42:29 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id C000237B400 for <freebsd-doc@FreeBSD.ORG>; Tue, 26 Feb 2002 06:42:26 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g1QEgQ655303 for freebsd-doc@FreeBSD.ORG; Tue, 26 Feb 2002 09:42:26 -0500 (EST) (envelope-from mwlucas) Date: Tue, 26 Feb 2002 09:42:26 -0500 From: Michael Lucas <mwlucas@blackhelicopters.org> To: freebsd-doc@FreeBSD.ORG Subject: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) Message-ID: <20020226094226.B55250@blackhelicopters.org> References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202221535.g1MFZx236793@bmah.dyndns.org>; from bmah@FreeBSD.ORG on Fri, Feb 22, 2002 at 07:35:59AM -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org On Fri, Feb 22, 2002 at 07:35:59AM -0800, Bruce A. Mah wrote: > I think your call for a "doc freeze" during the release cycle is a good > idea, and I'd like to see us start doing this. Guys, This is simple enough to do, and discussion seems to have faded. If we want this as policy, it should be in the Release Engineering schedule and the FDP. I propose an official one-week doc/en_US.ISO8859-1 freeze for everything except the release notes, to give translators a little bit of catch-up time. The release notes are difficult, as the -src committers MFC until just a couple days before. I suggest that we have a "best effort" relnotes freeze. Basically, the relnotes maintainer will try to keep things up-to-date so that updates during the last couple days are minimal. Bruce already does this, but it would be important for his successor to be as reliable. ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 8:16:55 2002 Delivered-To: freebsd-doc@freebsd.org Received: from svr-ganmtc-appserv-mgmt.ncf.coxexpress.com (svr-ganmtc-appserv-mgmt.ncf.coxexpress.com [24.136.46.5]) by hub.freebsd.org (Postfix) with ESMTP id E1BCD37B422; Tue, 26 Feb 2002 08:16:28 -0800 (PST) Received: from darkstar.doublethink.cx (cpe-oca-24-136-59-202-cmcpe.ncf.coxexpress.com [24.136.59.202]) by svr-ganmtc-appserv-mgmt.ncf.coxexpress.com (8.11.4/8.11.4) with ESMTP id g1QGGRl06042; Tue, 26 Feb 2002 11:16:28 -0500 Received: by darkstar.doublethink.cx (Postfix, from userid 1000) id 6608329A3; Tue, 26 Feb 2002 11:16:27 -0500 (EST) Date: Tue, 26 Feb 2002 11:16:27 -0500 From: Chris Faulhaber <jedgar@fxp.org> To: Chris Costello <chris@FreeBSD.org> Cc: doc@FreeBSD.org Subject: Re: cvs commit: www/en/news/status Makefile report-dec-2001-jan-2002.xml status.sgml Message-ID: <20020226161627.GA73431@darkstar.doublethink.cx> References: <200202252233.g1PMXNC68607@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <200202252233.g1PMXNC68607@freefall.freebsd.org> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2002 at 02:33:23PM -0800, Chris Costello wrote: > chris 2002/02/25 14:33:23 PST >=20 > Modified files: > en/news/status Makefile status.sgml=20 > Added files: > en/news/status report-dec-2001-jan-2002.xml=20 > Log: > Add in the new Dec. 2001/Jan 2002 bi-monthly status report. > =20 Will this be added to the Project News on the main page? emailed like previous reports? On a related note, the link to the status report page from the 2001 News Flash page is broken: The file http://www.freebsd.org/news/2001/status/status.html does not exist at this server. You are coming from http://www.freebsd.org/news/2001/index.html.=20 --=20 Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: FreeBSD: The Power To Serve iEYEARECAAYFAjx7tNsACgkQObaG4P6BelDHXwCZAdM64kCk/V6gU7Lltg7IrO25 egoAn2a1A3ZSXjU7YujbhrMQ1LrGP8c8 =9wne -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 9:47:56 2002 Delivered-To: freebsd-doc@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 44A1537B417 for <freebsd-doc@FreeBSD.ORG>; Tue, 26 Feb 2002 09:47:55 -0800 (PST) Received: from cfcl.com (cpe-24-221-169-54.ca.sprintbbd.net [24.221.169.54]) by idiom.com (8.9.3/8.9.3) with ESMTP id JAA58088 for <freebsd-doc@FreeBSD.ORG>; Tue, 26 Feb 2002 09:47:54 -0800 (PST) Received: from [192.168.254.205] (cerberus [192.168.254.205]) by cfcl.com (8.11.1/8.11.1) with ESMTP id g1QHoYG48965 for <freebsd-doc@FreeBSD.ORG>; Tue, 26 Feb 2002 09:50:34 -0800 (PST) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: <p051003dfb8a170c0a167@[192.168.254.205]> In-Reply-To: <20020225191122.A15283@chiark.greenend.org.uk> References: <20020225191122.A15283@chiark.greenend.org.uk> Date: Tue, 26 Feb 2002 09:44:24 -0800 To: freebsd-doc@FreeBSD.ORG From: Rich Morin <rdm@cfcl.com> Subject: Re: yacc documentation Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org At 7:11 PM +0000 2/25/02, Tony Finch wrote: >The yacc manual page is remarkably sparse for such a complicated >program. Now that ancient Unix has been freed, why not commit the old >AT&T PSD documentation for it? More generally, I'd like to see all of the missing papers added, as well as tools like diction, spell, and style. -r -- email: rdm@cfcl.com; phone: +1 650-873-7841 http://www.cfcl.com/rdm - my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 10:28: 1 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by hub.freebsd.org (Postfix) with ESMTP id 39A9637B402 for <freebsd-doc@FreeBSD.ORG>; Tue, 26 Feb 2002 10:27:58 -0800 (PST) Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mail3.panix.com (Postfix) with ESMTP id 52E5C98285; Tue, 26 Feb 2002 13:27:57 -0500 (EST) Received: (from ziggy@localhost) by panix2.panix.com (8.11.3nb1/8.8.8/PanixN1.0) id g1QIRv607316; Tue, 26 Feb 2002 13:27:57 -0500 (EST) Date: Tue, 26 Feb 2002 13:27:57 -0500 From: Adam Turoff <ziggy@panix.com> To: Rich Morin <rdm@cfcl.com> Cc: freebsd-doc@FreeBSD.ORG Subject: Re: yacc documentation Message-ID: <20020226182757.GC23959@panix.com> References: <20020225191122.A15283@chiark.greenend.org.uk> <p051003dfb8a170c0a167@[192.168.254.205]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <p051003dfb8a170c0a167@[192.168.254.205]> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org On Tue, Feb 26, 2002 at 09:44:24AM -0800, Rich Morin wrote: > At 7:11 PM +0000 2/25/02, Tony Finch wrote: > >The yacc manual page is remarkably sparse for such a complicated > >program. Now that ancient Unix has been freed, why not commit the old > >AT&T PSD documentation for it? > > More generally, I'd like to see all of the missing papers added, as well > as tools like diction, spell, and style. Do you mean the ones that were in the jointly published USENIX/O'Reilly 5-Volume 4.4BSD docset? What's the copyright status on those papers? I was overjoyed when I found all five volumes in one fell swoop a couple of years ago. Would it be possible to reprint them in their entirety today? Would it be possible to work with USENIX to produce an new version of something similar and up-to-date? Z. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 10:45:43 2002 Delivered-To: freebsd-doc@freebsd.org Received: from iomworld.com (66-81-161-192-modem.o1.com [66.81.161.192]) by hub.freebsd.org (Postfix) with ESMTP id 41EDA37B402 for <doc@FreeBSD.org>; Tue, 26 Feb 2002 10:45:28 -0800 (PST) From: Deepak Sharma <deepak@iomworld.com> To: doc@FreeBSD.org Subject: Offshore software development Reply-To: deepak@iomworld.com Date: 26 Feb 2002 10:44:01 -0800 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: <20020226184528.41EDA37B402@hub.freebsd.org> Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org My name is Deepak Sharma, Vice President for iOM North America. We offer OFFSHORE SOFTWARE DEVELOPMENT services thereby helping companies reduce their IT Software Development & Maintenance costs by as much as 30% and in some cases 50%. This email is to request your permission to send to you the advantages of offshore software development. If you are in need of software development services today or in future you can contact us for a no-obligation fixed price quote once you know more about us. We definitely respect your email privacy. If you prefer not to receive any further emails from us please let me know and we will cease sending you any further emails. Thank you for your time. Deepak Sharma, Vice President iOM.compositiongroup, Inc. 28005 North Smyth Drive, Suite 108 Valencia, CA 91355 Tel: (661)295-4630 Fax: (661)295-4635 www.iomworld.com England | India | Malaysia | Philippines | Singapore | Sri Lanka |Thailand | USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 10:49: 2 2002 Delivered-To: freebsd-doc@freebsd.org Received: from web12503.mail.yahoo.com (web12503.mail.yahoo.com [216.136.173.195]) by hub.freebsd.org (Postfix) with SMTP id 1710437B41A for <freebsd-doc@FreeBSD.org>; Tue, 26 Feb 2002 10:48:32 -0800 (PST) Message-ID: <20020226184832.4794.qmail@web12503.mail.yahoo.com> Received: from [157.182.44.249] by web12503.mail.yahoo.com via HTTP; Tue, 26 Feb 2002 10:48:32 PST Date: Tue, 26 Feb 2002 10:48:32 -0800 (PST) From: praveen polishetty <poli_praveen@yahoo.com> Subject: Regarding freeBSD To: freebsd-doc@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org Sir, I am working on FreeBSD for my research.I installed version 4.3 on my system.I made some changes to the folder sys to build my own kernel and I want to delete it and download the new sys folder to my system.Please tell me the best way in doing that or else do i need to install freeBSD4.3 again.I would appreciate if you can mail me regarding this. Thanks, praveen ===== Praveen kumar Polishetty, 445,oakland street, Apt#401, Morgantown,wv-26505 Ph:304-598-7418(R) 304-293-7226 Ext:4203(O) __________________________________________________ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 11:58:38 2002 Delivered-To: freebsd-doc@freebsd.org Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by hub.freebsd.org (Postfix) with ESMTP id D312737B400 for <freebsd-doc@FreeBSD.ORG>; Tue, 26 Feb 2002 11:58:33 -0800 (PST) Received: from pittgoth.com (lcl234.zbzoom.net [208.236.36.234]) by pittgoth.com (8.11.6/8.11.6) with ESMTP id g1QK0N913916; Tue, 26 Feb 2002 15:00:23 -0500 (EST) (envelope-from darklogik@pittgoth.com) Message-ID: <3C7BEB80.2010101@pittgoth.com> Date: Tue, 26 Feb 2002 15:09:36 -0500 From: Tom Rhodes <darklogik@pittgoth.com> Reply-To: darklogik@pittgoth.com User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: praveen polishetty <poli_praveen@yahoo.com> Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Regarding freeBSD References: <20020226184832.4794.qmail@web12503.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org praveen polishetty wrote: > Sir, > I am working on FreeBSD for my research.I installed > version 4.3 on my system.I made some changes to the > folder sys to build my own kernel and I want to delete > it and download the new sys folder to my system.Please > tell me the best way in doing that or else do i need > to install freeBSD4.3 again.I would appreciate if you > can mail me regarding this. > Thanks, > praveen > > ===== > Praveen kumar Polishetty, > 445,oakland street, > Apt#401, > Morgantown,wv-26505 > Ph:304-598-7418(R) > 304-293-7226 Ext:4203(O) > This list is for the documentation project, please send your questions to questions@FreeBSD.org. But real quick: The information you requested sent through email would take a good while to type up, and has even been done already in the FreeBSD handbook. You would most likly wish to review the "Kernel Configuration" chapter and maybe glance over the "Cutting Edge" chapter, it will give you some upgrading information. Enjoy -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 12: 2: 2 2002 Delivered-To: freebsd-doc@freebsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [212.22.195.2]) by hub.freebsd.org (Postfix) with ESMTP id 0E3BA37B405; Tue, 26 Feb 2002 12:01:57 -0800 (PST) Received: from fanf by chiark.greenend.org.uk with local (Exim 3.12 #1) id 16fnnK-0003Vb-00 (Debian); Tue, 26 Feb 2002 20:01:50 +0000 Date: Tue, 26 Feb 2002 20:01:50 +0000 From: Tony Finch <dot@dotat.at> To: Murray Stokely <murray@freebsd.org> Cc: Tony Finch <dot@dotat.at>, freebsd-doc@freebsd.org Subject: Re: yacc documentation Message-ID: <20020226200150.A12793@chiark.greenend.org.uk> References: <20020225191122.A15283@chiark.greenend.org.uk> <20020226083857.GC5866@freebsdmall.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020226083857.GC5866@freebsdmall.com> Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org I have submitted the following PRs. The first is just a Makefile cleanup and only tangentially related to tha yacc docs. The second is the actual documentation as a patch. It sort-of works, barring some formatting problems caused by troff macro bit rot. There are loads of other usd/psd/smm docs that could be added but I think they will all need some attention -- e.g. the lex doc has some nasty formatting bugs. http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/35343 http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/35345 Tony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 12: 5:24 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mx02.admiral.ne.jp (mx02.admiral.ne.jp [211.10.216.33]) by hub.freebsd.org (Postfix) with SMTP id EE79D37B405 for <freebsd-doc@FreeBSD.ORG>; Tue, 26 Feb 2002 12:05:17 -0800 (PST) Received: (qmail 55172 invoked from network); 27 Feb 2002 05:05:16 +0900 Message-ID: <20020226200516.55172.qmail@mx02.admiral.ne.jp> Received: from 61.206.112.54.user.am.il24.net (HELO mash2) (61.206.112.54) by mx02.admiral.ne.jp with SMTP; 27 Feb 2002 05:05:16 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Date: Wed, 27 Feb 2002 05:03:10 +0900 Subject: =?ISO-2022-JP?B?GyRCQWo4XyVqJXMlLyROJCo0aiQkGyhC?= From: =?ISO-2022-JP?B?GyRCIUozdCFLJV4lQyU3JWUbKEI=?= <info@e-7.co.jp> To: =?ISO-2022-JP?B?GyRCJSYlJyVWQzRFdjxUTU0bKEI=?= <freebsd-doc@FreeBSD.ORG> Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org $B$O$8$a$^$7$F!"$3$NEY!"$*BpMM$N%[!<%`%Z!<%8$rGR8+$5$;$F$$(B $B$?$@$$$F!"@'Hs$H$b!"Aj8_%j%s%/$r$*4j$$$G$-$J$$$+$H;W$$$^(B $B$7$F$4O"Mm$7$?<!Bh$G$9!#(B $BJ@<R$N%5%$%H$O@-IB$K4X$7$F>\$7$/>R2p$7$?%5%$%H$K$J$C(B $B$F$$$^$9!#IB>u$N2r@b$O$b$A$m$s!":_Bp$G4JC1$K$G$-$k(B $B@-IB8!::$r<B;\$7$F$$$^$9$N$G!"%Q!<%H%J!<$rBg@Z$K;W$&J}$d(B $BIwB/E9$GM7$V$3$H$NB?$$J}!&ITFCDjB??t$NAj<j$H4X78$r;}$D$3$H(B $B$,$"$kJ}$K$OM-0U5A$J%5%$%H$G$9!#Kt!"Hs46@w$N>ZL@=q$H$7$F$b(B $B$*;H$$$$$?$@$1$^$9!#(B $B8!::$O8|@8>JG'Dj$N$N0eNE8!::2q<R$,9T$$$^$9$N$G!"@:EY$K4X$7(B $B$F$bIB1!$G$N8!::$HJQ$o$j$"$j$^$;$s!#(B $B$b$7!"Aj8_%j%s%/$KF10U$rD:$1$k$h$&$G$"$l$P!"%j%s%/@h$N(B $B%"%I%l%9$d>R2pJ8$r$4O"MmD:$1$l$PAa5^$KJ@<R$N%[!<%`(B $B%Z!<%8$KH?1G$$$?$7$^$9!#$^$?!"$4<+J,$GEPO?$7$FD:$/$3$H(B $B$b$G$-$^$9!#$=$N>l9g$O2<5-$h$j%"%/%;%9$7$F>R2pJ8Ey$r$4(B $B<+J,$GEPO?$7$F$/$@$5$$!#(B $BJ@<R$N%P%J!<$rE=$C$F$$$?$@$1$k>l9g$O2<5-$h$j%@%&%s%m!<%I(B $B$7$F$*;H$$$/$@$5$$!#(B $B@'Hs$H$b$*NO$rB_$7$FD:$-$?$/!"$h$m$7$/$*4j$$$$$?$7$^$9!#(B $B:G8e$^$G!"$*IU$-9g$$D:$-$"$j$,$H$&$4$6$$$^$7$?!#(B $B%5%$%HL>!!:_Bp@-IB8!::!!7r9/(B110$BHV(B $B>R2pJ8(B $B%(%$%:$dNTIB$H$$$C$?@-IB$K4X$7$F!">\:Y$rL5NA$G2r@b$7$?%5%$%H$G$9!#(B $B:_Bp@-IB8!::$b<B;\$7$F$$$k$N$GIT0B$r46$8$F$$$kJ}$d%Q!<%H%J!<$,(B $BIQHK$KJQ$o$kJ}$O8!::$r?=9~$s$G$_$k$N$b$$$$$+$b!#(B $B7HBS$+$i$N%"%/%;%9$b#O#K!*(B $B%P%J!<2hA|!J2<5-$h$jE,Ev$J$b$N$r;H$C$F$/$@$5$$!K(B http://www.h-110.com/pch110/linkbanner.htm $B%j%s%/@h%"%I%l%9(B http://www.h-110.com/ $B$4<+J,$GEPO?$5$l$k>l9g$O2<5-$h$j(B http://www.h-110.com/cruiser/cruiser.cgi $B%5%$%H$N@5<0L>!'(B $B%j%s%/@h!'(B $B>R2pJ8!'(B $B$rJV?.$7$F$$$?$@$$$F$bJ@<R$GH?1G$$$?$7$^$9!#(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 12: 6:10 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mx02.admiral.ne.jp (mx02.admiral.ne.jp [211.10.216.33]) by hub.freebsd.org (Postfix) with SMTP id 5146E37B405 for <freebsd-doc@FreeBSD.org>; Tue, 26 Feb 2002 12:06:04 -0800 (PST) Received: (qmail 55375 invoked from network); 27 Feb 2002 05:06:03 +0900 Message-ID: <20020226200603.55375.qmail@mx02.admiral.ne.jp> Received: from 61.206.112.54.user.am.il24.net (HELO mash2) (61.206.112.54) by mx02.admiral.ne.jp with SMTP; 27 Feb 2002 05:06:03 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Date: Wed, 27 Feb 2002 05:03:58 +0900 Subject: =?ISO-2022-JP?B?GyRCQWo4XyVqJXMlLyROJCo0aiQkGyhC?= From: =?ISO-2022-JP?B?GyRCIUozdCFLJV4lQyU3JWUbKEI=?= <info@e-7.co.jp> To: =?ISO-2022-JP?B?GyRCJSYlJyVWQzRFdjxUTU0bKEI=?= <freebsd-doc@FreeBSD.org> Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org $B$O$8$a$^$7$F!"$3$NEY!"$*BpMM$N%[!<%`%Z!<%8$rGR8+$5$;$F$$(B $B$?$@$$$F!"@'Hs$H$b!"Aj8_%j%s%/$r$*4j$$$G$-$J$$$+$H;W$$$^(B $B$7$F$4O"Mm$7$?<!Bh$G$9!#(B $BJ@<R$N%5%$%H$O@-IB$K4X$7$F>\$7$/>R2p$7$?%5%$%H$K$J$C(B $B$F$$$^$9!#IB>u$N2r@b$O$b$A$m$s!":_Bp$G4JC1$K$G$-$k(B $B@-IB8!::$r<B;\$7$F$$$^$9$N$G!"%Q!<%H%J!<$rBg@Z$K;W$&J}$d(B $BIwB/E9$GM7$V$3$H$NB?$$J}!&ITFCDjB??t$NAj<j$H4X78$r;}$D$3$H(B $B$,$"$kJ}$K$OM-0U5A$J%5%$%H$G$9!#Kt!"Hs46@w$N>ZL@=q$H$7$F$b(B $B$*;H$$$$$?$@$1$^$9!#(B $B8!::$O8|@8>JG'Dj$N$N0eNE8!::2q<R$,9T$$$^$9$N$G!"@:EY$K4X$7(B $B$F$bIB1!$G$N8!::$HJQ$o$j$"$j$^$;$s!#(B $B$b$7!"Aj8_%j%s%/$KF10U$rD:$1$k$h$&$G$"$l$P!"%j%s%/@h$N(B $B%"%I%l%9$d>R2pJ8$r$4O"MmD:$1$l$PAa5^$KJ@<R$N%[!<%`(B $B%Z!<%8$KH?1G$$$?$7$^$9!#$^$?!"$4<+J,$GEPO?$7$FD:$/$3$H(B $B$b$G$-$^$9!#$=$N>l9g$O2<5-$h$j%"%/%;%9$7$F>R2pJ8Ey$r$4(B $B<+J,$GEPO?$7$F$/$@$5$$!#(B $BJ@<R$N%P%J!<$rE=$C$F$$$?$@$1$k>l9g$O2<5-$h$j%@%&%s%m!<%I(B $B$7$F$*;H$$$/$@$5$$!#(B $B@'Hs$H$b$*NO$rB_$7$FD:$-$?$/!"$h$m$7$/$*4j$$$$$?$7$^$9!#(B $B:G8e$^$G!"$*IU$-9g$$D:$-$"$j$,$H$&$4$6$$$^$7$?!#(B $B%5%$%HL>!!:_Bp@-IB8!::!!7r9/(B110$BHV(B $B>R2pJ8(B $B%(%$%:$dNTIB$H$$$C$?@-IB$K4X$7$F!">\:Y$rL5NA$G2r@b$7$?%5%$%H$G$9!#(B $B:_Bp@-IB8!::$b<B;\$7$F$$$k$N$GIT0B$r46$8$F$$$kJ}$d%Q!<%H%J!<$,(B $BIQHK$KJQ$o$kJ}$O8!::$r?=9~$s$G$_$k$N$b$$$$$+$b!#(B $B7HBS$+$i$N%"%/%;%9$b#O#K!*(B $B%P%J!<2hA|!J2<5-$h$jE,Ev$J$b$N$r;H$C$F$/$@$5$$!K(B http://www.h-110.com/pch110/linkbanner.htm $B%j%s%/@h%"%I%l%9(B http://www.h-110.com/ $B$4<+J,$GEPO?$5$l$k>l9g$O2<5-$h$j(B http://www.h-110.com/cruiser/cruiser.cgi $B%5%$%H$N@5<0L>!'(B $B%j%s%/@h!'(B $B>R2pJ8!'(B $B$rJV?.$7$F$$$?$@$$$F$bJ@<R$GH?1G$$$?$7$^$9!#(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 12:46:26 2002 Delivered-To: freebsd-doc@freebsd.org Received: from lists.blarg.net (lists.blarg.net [206.124.128.17]) by hub.freebsd.org (Postfix) with ESMTP id 4FE4837B41D for <freebsd-doc@freebsd.org>; Tue, 26 Feb 2002 12:46:21 -0800 (PST) Received: from thig.blarg.net (thig.blarg.net [206.124.128.18]) by lists.blarg.net (Postfix) with ESMTP id BB006BD48 for <freebsd-doc@freebsd.org>; Tue, 26 Feb 2002 12:46:20 -0800 (PST) Received: from localhost.localdomain ([206.124.139.115]) by thig.blarg.net (8.9.3/8.9.3) with ESMTP id MAA11839 for <freebsd-doc@freebsd.org>; Tue, 26 Feb 2002 12:46:20 -0800 Received: (from jojo@localhost) by localhost.localdomain (8.11.6/8.11.3) id g1QKmUO07633; Tue, 26 Feb 2002 12:48:30 -0800 (PST) (envelope-from swear@blarg.net) To: freebsd-doc@freebsd.org Subject: Suggestions for handbook/eresources.html#ERESOURCES-MAIL From: swear@blarg.net (Gary W. Swearingen) Date: 26 Feb 2002 12:48:30 -0800 Message-ID: <1wzo1wufz5.o1w@localhost.localdomain> Lines: 32 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org 1) I've seen a couple of questions about how to get a new mailing list created. (And another suggestion that I get one started for the discussion of proposed PRs, which I think would get read too little.) I suggest that a "C.1.4 List Creation" section be added to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html but I don't know what to put in there. Maybe "Contact postmaster"? 2) The above web page should have the list charter for freebsd-www; the description under "Limited lists" ("Maintainers of www.FreeBSD.org") is rather unhelpful. I thought that's what -doc was for. 3) Three occurances of (non-) "FreeBSD related" should have the space replaced with an hyphen. (There is already one "FreeBSD-related".) 4) Since mailing addresses like "doc@freebsd.org" are permitted, it would be helpful to have that stated on the page. I'm not sure if it's true for only a few lists or for all which start with "freebsd-". P.S. I found the discussion of "Limited lists" a bit nebulous, like maybe it was trying to not be open about some things. Is subscription screened? Is it really about "audiences" and "interest" (many of the technical lists should then qualify) or really about limiting discussion to important contributors (quite reasonably, eg, to keep "noise" down)? Are they segregated just because they refuse to publish guidelines? Why is -install not under "Technical lists"? It might be better to just have Technical and Non-Technical lists and let the lists describe themselves and their desires/requirements for subscribers in their charters. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 13:10:39 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E6ADB37B431 for <freebsd-doc@freebsd.org>; Tue, 26 Feb 2002 13:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1QLA2f07435; Tue, 26 Feb 2002 13:10:02 -0800 (PST) (envelope-from gnats) Date: Tue, 26 Feb 2002 13:10:02 -0800 (PST) Message-Id: <200202262110.g1QLA2f07435@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Tom Rhodes <darklogik@pittgoth.com> Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Reply-To: Tom Rhodes <darklogik@pittgoth.com> Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-doc.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc> X-Loop: FreeBSD.org The following reply was made to PR docs/35098; it has been noted by GNATS. From: Tom Rhodes <darklogik@pittgoth.com> To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Date: Tue, 26 Feb 2002 16:10:17 -0500 (EST) Try this one now ;) Clean up of whitespace, and other little "picks" -- Tom Rhodes diff -ru handbook.old/advanced-networking/chapter.sgml handbook/advanced-networking/chapter.sgml --- handbook.old/advanced-networking/chapter.sgml Fri Feb 22 16:16:17 2002 +++ handbook/advanced-networking/chapter.sgml Tue Feb 26 15:45:36 2002 @@ -648,6 +648,13 @@ <sect1info> <authorgroup> <author> + <firstname>Tom</firstname> + <surname>Rhodes</surname> + <contrib>Reorganized and enhanced by </contrib> + </author> + </authorgroup> + <authorgroup> + <author> <firstname>Bill</firstname> <surname>Swingle</surname> <contrib>Written by </contrib> @@ -658,44 +665,41 @@ <indexterm><primary>NFS</primary></indexterm> <para>Among the many different file systems that FreeBSD supports is - the Network File System or NFS. NFS allows you - to share directories and files on one machine with others - via the network they are attached to. Using NFS, users and - programs can access files on remote systems as if they were local + the Network File System, also known as <acronym>NFS</acronym>. + <acronym>NFS</acronym> allows a system to share directories and files + with others over a network. By using <acronym>NFS</acronym>, users and + programs can access files on remote systems almost as if they were local files.</para> - <para>NFS has several benefits:</para> + <para>Some of the most notable benefits that <acronym>NFS</acronym> can provide are:</para> <itemizedlist> <listitem> - <para>Local workstations do not need as much disk space because + <para>Local workstations use less disk space because commonly used data can be stored on a single machine and still - remain accessible to everyone on the network.</para> + remain accessible to others over the network.</para> </listitem> <listitem> <para>There is no need for users to have unique home directories - on every machine on your network. Once they have an established - directory that is available via NFS it can be accessed from - anywhere.</para> + on every network machine. Home directories could be setup on the + <acronym>NFS</acronym> server and made available throughout the network.</para> </listitem> <listitem> - <para>Storage devices such as floppies and CDROM drives can be - used by other machines on the network eliminating the need for - extra hardware.</para> + <para>Storage devices such as floppy disks, CDROM drives, and ZIP drives + can be used by other machines on the network. This may reduce the number + of removable media drives.</para> </listitem> </itemizedlist> <sect2> - <title>How It Works + How <acronym>NFS</acronym> Works - NFS is composed of two sides – a client side and a - server side. Think of it as a want/have relationship. The client - wants the data that the server side - has. The server shares its data with the - client. In order for this system to function properly a few - processes have to be configured and running. + NFS consists of at least two main parts: a server + and at least one client. The client remotely accesses the data that is stored + on the server machine. In order for this to function properly a few + processes have to be configured and running: The server has to be running the following daemons: @@ -723,141 +727,129 @@ nfsd - The NFS Daemon which services requests from NFS - clients. + The NFS daemon which services requests from + the NFS clients. mountd - The NFS Mount Daemon which actually carries out - requests that &man.nfsd.8; passes on to it. + The NFS mount daemon which carries out + the requests that &man.nfsd.8; passes on to it. portmap - The portmapper daemon which - allows NFS clients to find out which port the NFS server - is using. + The portmapper daemon + allows NFS clients to discover which port the NFS server + is using. - The client side only needs to run a single daemon: - - NFS - client - - - nfsiod - - - - - - - nfsiod - The NFS async I/O Daemon which services requests - from its NFS server. - - - - + The client can also run a daemon, known as + nfsiod. The nfsiod + daemon services the requests from the NFS server. This + is optional, and improves performance, but is not required for normal + and correct operation. See the &man.nfsiod.8; man page for more information. + - Configuring NFS + Configuring <acronym>NFS</acronym> NFS configuration - Luckily for us, on a FreeBSD system this setup is a snap. The - processes that need to be running can all be run at boot time with + NFS configuration is relatively straightforward + process. The processes that need to be running can all start at boot time with a few modifications to your /etc/rc.conf - file. + file. - On the NFS server make sure you have: + On the NFS server, make sure that the following options + are configured in the /etc/rc.conf file: portmap_enable="YES" nfs_server_enable="YES" -nfs_server_flags="-u -t -n 4" mountd_flags="-r" - mountd is automatically run whenever the - NFS server is enabled. The and - flags to nfsd tell it to - serve UDP and TCP clients. The flag tells - nfsd to start 4 copies of itself. + mountd runs automatically whenever the + NFS server is enabled. - On the client, make sure you have: + On the client, make sure this option is present in + /etc/rc.conf: nfs_client_enable="YES" -nfs_client_flags="-n 4" - - Like nfsd, the tells - nfsiod to start 4 copies of itself. + - The last configuration step requires that you create a file - called /etc/exports. The exports file - specifies which file systems on your server will be shared - (a.k.a., exported) and with what clients they will - be shared. Each line in the file specifies a file system to be - shared. There are a handful of options that can be used in this - file but only a few will be mentioned here. You can find out - about the rest in the &man.exports.5; manual page. + + The /etc/exports + file specifies which filesystems NFS should export (sometimes + referred to as share). + Each line in /etc/exports specifies a filesystem to be exported and + which machines have access to that filesystem. Along with what machines have access + to that filesystem, access options may also be specified. There are many such options + that can be used in this file but only a few will be mentioned here. You can easily discover + other options by reading over the &man.exports.5; manual page. + Here are a few example /etc/exports entries: NFS - exporting filesystems + Examples of exporting filesystems - The following line exports /cdrom to - three silly machines that have the same domain name as the server + + The following examples give an idea of how to export filesystems, + although the settings may be different depending on + your environment and network configuration. + The following line exports /cdrom to + three example machines that have the same domain name as the server (hence the lack of a domain name for each) or have entries in your /etc/hosts file. The - flag makes the shared file system read-only. With this flag, the - remote system will not be able to make any changes to the - shared file system. + flag makes the exported file system read-only. With this flag, the + remote system will not be able to write any changes to the + exported file system. - /cdrom -ro moe larry curly + /cdrom -ro host1 host2 host3 The following line exports /home to three hosts by IP address. This is a useful setup if you have a - private network but do not have DNS running. The - flag allows all the directories below - the specified file system to be exported as well. + private network without a DNS server configured. + Optionally the /etc/hosts file could be configured + for internal hostnames; please review &man.hosts.5; for more + information. The flag allows the directories + below the specified filesystem to also be exported. /home -alldirs 10.0.0.2 10.0.0.3 10.0.0.4 - The following line exports /a to two - machines that have different domain names than the server. The - flag allows - the root user on the remote system to write to the shared - file system as root. Without the -maproot=0 flag even if - someone has root access on the remote system they will not - be able to modify files on the shared file system. + The following line exports /a so that two + clients from different domains may access the filesystem. The + flag allows the root + user on the remote system to write data on the exported filesystem as + root. If the -maproot=0 flag is not specified, then even if + a user has root access on the remote system, they will not + be able to modify files on the exported filesystem. - /a -maproot=0 host.domain.com box.example.com + /a -maproot=0 host.example.com box.example.org - In order for a client to access- an exported file system it must - have permission to do so. Make sure your client is listed in your + In order for a client to access an exported filesystem, the client must + have permission to do so. Make sure the client is listed in your /etc/exports file. In /etc/exports, each line represents the export information for one filesystem to one host. A - remote host can only be specified once for each local - filesystem, and you can only have one default entry per local - filesystem. For example, let's assume that - /usr is a single filesystem. The - following /etc/exports is invalid: + remote host can only be specified once per filesystem, and may only + have one default entry. For example, assume that /usr + is a single filesystem. The following /etc/exports + would be valid: /usr/src client /usr/ports client One filesystem, /usr, has two lines - specifying its exports to the same host, - client. The correct format is: + specifying exports to the same host, client. + The correct format for this situation is: /usr/src /usr/ports client @@ -874,40 +866,41 @@ # client01 has root privileges on it /usr/src /usr/ports -maproot=0 client01 /usr/src /usr/ports client02 -# The "client" machines have root and can mount anywhere -# up /exports. Anyone inhe world can mount /exports/obj read-only +# The client machines have root and can mount anywhere +# on /exports. Anyone in the world can mount /exports/obj read-only /exports -alldirs -maproot=0 client01 client02 /exports/obj -ro You must restart mountd whenever you modify - /etc/exports to make changes take - effect. This can be accomplished by sending the hangup signal + /etc/exports so the changes can take effect. + This can be accomplished by sending the hangup signal to the mountd process: &prompt.root; kill -HUP `cat /var/run/mountd.pid` - Now that you have made all these changes you can just reboot - and let FreeBSD start everything for you at boot time, or you can - run the following commands as root: + Alternatively, a reboot will make FreeBSD set everything + up properly. A reboot is not necessary though. + Executing the following commands as root, + should start everything up. - On the NFS server: + On the NFS server: &prompt.root; portmap &prompt.root; nfsd -u -t -n 4 &prompt.root; mountd -r - On the NFS client: + On the NFS client: &prompt.root; nfsiod -n 4 - Now you should be ready to actually mount a remote file - system. This can be done one of two ways. In these examples the + Now everything should be ready to actually mount a remote file + system. In these examples the server's name will be server and the client's - name will be client. If you just want to - temporarily mount a remote file system or just want to test out - your configuration you can run a command like this as root on the - client: + name will be client. If you only want to + temporarily mount a remote file system or would rather test the + configuration, just execute a command like this as root on the + client: NFS mounting filesystems @@ -916,56 +909,59 @@ This will mount the /home directory on the server at /mnt on the client. If - everything is setup correctly you should be able to go into - /mnt on the client and see all the files that are on the - server. - - If you want to automatically mount a remote file system - each time the computer boots, add the filesystem to - /etc/fstab. Here is an example: + everything is set up correctly you should be able to enter + /mnt on the client and see all the files + that are on the server. + + If you want to automatically mount a remote filesystem + each time the computer boots, add the filesystem to the + /etc/fstab file. Here is an example: server:/home /mnt nfs rw 0 0 - Read the &man.fstab.5; manual page for more options. + The &man.fstab.5; manual page lists all the available options. Practical Uses - There are many very cool uses for NFS. Some of the more common - ones are listed below. + NFS has many practical uses. Some of the more common + ones are listed below: + + The following NFS examples require + NFS to be correctly configured before actual use, + as previously discussed. + + NFS uses - Have several machines on a network and share a CDROM or - floppy drive among them. This is cheaper and often more - convenient. + Set several machines to share a CDROM or + other media among them. This is cheaper and often + more convenient. - With so many machines on a network, it gets old having your - personal files strewn all over the place. You can have a - central NFS server that houses all user home directories and - shares them with the rest of the machines on the LAN, so no - matter where you log in you will have the same home - directory. + On large networks, it might be more convenient to configure a + central NFS server in which to store all the user + home directories. These home directories can then be exported to + the network so that users would always have the same home directory, + regardless of which workstation they log in to. - When you get to reinstalling FreeBSD on one of your - machines, NFS is the way to go! Just pop your distribution - CDROM into your file server and away you go! + You can use an exported CDROM to install + software on multiple machines. - Have a common /usr/ports/distfiles - directory that all your machines share. That way, when you go - to install a port that you have already installed on a different - machine, you do not have to download the source all over - again! + Several machines could have a common /usr/ports/distfiles + directory. + That way, when you need to install a port on several machines, you can + quickly access the source without downloading it on each machine. @@ -992,14 +988,15 @@ amd automatic mounter daemon - &man.amd.8;, which is also known as the automatic mounter - daemon, is a useful utility used for automatically mounting a + &man.amd.8; (the automatic mounter daemon) + is a useful that automatically mounts a remote filesystem whenever a file or directory within that filesystem is accessed. Filesystems that are inactive for a period of time will also be automatically unmounted by amd. Using - amd provides a simplistic alternative - to static mounts. + amd provides a simple alternative + to permanent mounts, as permanent mounts should be listed in the + /etc/fstab. amd operates by attaching itself as an NFS server to the /host and To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 13:50:21 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CFE4A37B42C for ; Tue, 26 Feb 2002 13:50:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1QLo4s14851; Tue, 26 Feb 2002 13:50:04 -0800 (PST) (envelope-from gnats) Date: Tue, 26 Feb 2002 13:50:04 -0800 (PST) Message-Id: <200202262150.g1QLo4s14851@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Tom Rhodes Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Reply-To: Tom Rhodes Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35155; it has been noted by GNATS. From: Tom Rhodes To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Date: Tue, 26 Feb 2002 16:53:46 -0500 New patch on its way... Sorry for being slightly impatient. -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 13:50:27 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D1E8B37B426 for ; Tue, 26 Feb 2002 13:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1QLo1S14773; Tue, 26 Feb 2002 13:50:01 -0800 (PST) (envelope-from gnats) Date: Tue, 26 Feb 2002 13:50:01 -0800 (PST) Message-Id: <200202262150.g1QLo1S14773@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Tom Rhodes Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Reply-To: Tom Rhodes Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35155; it has been noted by GNATS. From: Tom Rhodes To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Date: Tue, 26 Feb 2002 16:43:10 -0500 (EST) diff -ru handbook.old/install/chapter.sgml handbook/install/chapter.sgml --- handbook.old/install/chapter.sgml Tue Feb 26 16:27:25 2002 +++ handbook/install/chapter.sgml Tue Feb 26 16:39:16 2002 @@ -994,7 +994,7 @@ If there are no conflicts listed then you can skip this step. Otherwise, the remaining conflicts need to be examined. If they - do not have the indication of an "allowed conflict" in the message + do not have the indication of an allowed conflict in the message area, then either the IRQ/address for device probe will need to be changed, or the IRQ/address on the hardware will need to be changed. @@ -2705,7 +2705,7 @@ the real server. For example, assuming you want to install from ftp.FreeBSD.org, using the proxy FTP server foo.example.com, listening on port - 1024. + 1034. In this case, you go to the options menu, set the FTP username to ftp@ftp.FreeBSD.org, and the password to your @@ -2958,7 +2958,7 @@ Choosing [ Yes ] and pressing Enter will bring - the machine up on the network and be ready for use after leaving + the machine up on the network and be ready for use after leaving the installation. @@ -4217,7 +4217,7 @@ use a shell that does not exist or you will not be able to login. - The user was also added to the group "wheel" to be able to + The user was also added to the group wheel to be able to become a superuser with root privileges. When you are satisfied, press &gui.ok; and @@ -4514,7 +4514,7 @@ Please press any key to reboot. It is safe to turn off the power after the shutdown command - has been issued and the message "Please press any key to reboot" + has been issued and the message Please press any key to reboot appears. If any key is pressed instead of turning off the power switch, the system will reboot. @@ -4821,7 +4821,7 @@ headless (serial console) serial console - This type of installation is called a "headless install", + This type of installation is called a headless install, because the machine that you are trying to install FreeBSD on either does not have a monitor attached to it, or does not even have a VGA output. How is this possible you ask? Using a @@ -4928,8 +4928,8 @@ Here is where you must set the floppy to boot into a serial console. You have to make a file called - boot.config containing "/boot/loader - -h". All this does is pass a flag to the bootloader to + boot.config containing /boot/loader + -h. All this does is pass a flag to the bootloader to boot into a serial console. &prompt.root; echo "/boot/loader -h" > boot.config @@ -5002,7 +5002,7 @@ FreeBSD installation media and/or source. This might be physical media, such as a tape, or a source that Sysinstall can use to retrieve the files, such as a local FTP site, or an MS-DOS - partition. For example; + partition. For example: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 14: 0:21 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 88AA237B402 for ; Tue, 26 Feb 2002 14:00:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1QM07w17418; Tue, 26 Feb 2002 14:00:07 -0800 (PST) (envelope-from gnats) Date: Tue, 26 Feb 2002 14:00:07 -0800 (PST) Message-Id: <200202262200.g1QM07w17418@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Priit Piipuu Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Reply-To: Priit Piipuu Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35155; it has been noted by GNATS. From: Priit Piipuu To: Michael Lucas Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Date: Wed, 27 Feb 2002 00:16:53 +0200 New, hopefully better patch. --- chapter.sgml.old Wed Feb 20 20:59:44 2002 +++ chapter.sgml Fri Feb 22 01:36:49 2002 @@ -994,7 +994,7 @@ If there are no conflicts listed then you can skip this step. Otherwise, the remaining conflicts need to be examined. If they - do not have the indication of an "allowed conflict" in the message + do not have the indication of an allowed conflict in the message area, then either the IRQ/address for device probe will need to be changed, or the IRQ/address on the hardware will need to be changed. @@ -4217,7 +4217,7 @@ use a shell that does not exist or you will not be able to login. - The user was also added to the group "wheel" to be able to + The user was also added to the group wheel to be able to become a superuser with root privileges. When you are satisfied, press &gui.ok; and @@ -4514,7 +4514,7 @@ Please press any key to reboot. It is safe to turn off the power after the shutdown command - has been issued and the message "Please press any key to reboot" + has been issued and the message Please press any key to reboot appears. If any key is pressed instead of turning off the power switch, the system will reboot. @@ -4821,7 +4821,7 @@ headless (serial console) serial console - This type of installation is called a "headless install", + This type of installation is called a headless install, because the machine that you are trying to install FreeBSD on either does not have a monitor attached to it, or does not even have a VGA output. How is this possible you ask? Using a @@ -4928,8 +4928,8 @@ Here is where you must set the floppy to boot into a serial console. You have to make a file called - boot.config containing "/boot/loader - -h". All this does is pass a flag to the bootloader to + boot.config containing + /boot/loader -h. All this does is pass a flag to the bootloader to boot into a serial console. &prompt.root; echo "/boot/loader -h" > boot.config @@ -5002,7 +5002,7 @@ FreeBSD installation media and/or source. This might be physical media, such as a tape, or a source that Sysinstall can use to retrieve the files, such as a local FTP site, or an MS-DOS - partition. For example; + partition. For example: -- For 20 dollars, I'll give you a good fortune next time ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 14:19:16 2002 Delivered-To: freebsd-doc@freebsd.org Received: from zen.estpak.ee (zen.estpak.ee [194.126.101.100]) by hub.freebsd.org (Postfix) with ESMTP id 4AE2337B400 for ; Tue, 26 Feb 2002 14:19:13 -0800 (PST) Received: from ppp2648.estpak.ee (ppp2458.estpak.ee [80.235.6.174]) by zen.estpak.ee (Postfix) with ESMTP id 10A7D6E968; Wed, 27 Feb 2002 00:19:11 +0200 (EET) Received: (from priitp@localhost) by ppp2648.estpak.ee (8.11.6/8.11.6) id g1QMhbn04493; Wed, 27 Feb 2002 00:43:37 +0200 (EET) (envelope-from priitp) Date: Wed, 27 Feb 2002 00:43:36 +0200 From: Priit Piipuu To: Tom Rhodes Cc: freebsd-doc@freebsd.org Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Message-ID: <20020227004336.E752@minerva.meskaliin.ee> References: <200202262150.g1QLo4s14851@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202262150.g1QLo4s14851@freefall.freebsd.org>; from darklogik@pittgoth.com on Tue, Feb 26, 2002 at 01:50:04PM -0800 X-Operating-System: FreeBSD minerva.meskaliin.ee 4.5-STABLE FreeBSD 4.5-STABLE Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Tue, Feb 26, 2002 at 01:50:04PM -0800 kirjutas Tom Rhodes: > > New patch on its way... > > Sorry for being slightly impatient. Oh my, I've got your post just after I send mine... :)) -- Goto, n.: A programming tool that exists to allow structured programmers to complain about unstructured programmers. -- Ray Simard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 14:25: 7 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mx1.datanet.hu (mx1.datanet.hu [194.149.13.160]) by hub.freebsd.org (Postfix) with ESMTP id 9981237B400 for ; Tue, 26 Feb 2002 14:24:56 -0800 (PST) Received: from fonix.adamsfamily.xx (nilus-961.adsl.datanet.hu [195.56.95.192]) by mx1.datanet.hu (DataNet) with ESMTP id 98807FA27 for ; Tue, 26 Feb 2002 23:24:53 +0100 (CET) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.2/8.12.2) with ESMTP id g1QMPNlZ025977 for ; Tue, 26 Feb 2002 23:25:23 +0100 (CET) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.2/8.12.2/Submit) id g1QMPM3L025976 for freebsd-doc@FreeBSD.ORG; Tue, 26 Feb 2002 23:25:22 +0100 (CET) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Tue, 26 Feb 2002 23:25:22 +0100 From: Szilveszter Adam To: freebsd-doc@FreeBSD.ORG Subject: Re: Suggestions for handbook/eresources.html#ERESOURCES-MAIL Message-ID: <20020226222521.GA1145@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , freebsd-doc@FreeBSD.ORG References: <1wzo1wufz5.o1w@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1wzo1wufz5.o1w@localhost.localdomain> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello Gary, I very much appreciate you brought up this topic just now. It is because the whereabouts about FreeBSD as in "FreeBSD the Project" not "FreeBSD the code" are not entirely clear and it all shows just way to well to anyone who has been hanging around the lists lately. Way to much stuff is unwritten, exists only in peoples' conflicting memories or is just plain rotting away. The mailing list issue is one such topic. (The web site maintenance is another) On Tue, Feb 26, 2002 at 12:48:30PM -0800, Gary W. Swearingen wrote: > > 1) I've seen a couple of questions about how to get a new mailing list > created. (And another suggestion that I get one started for the > discussion of proposed PRs, which I think would get read too little.) I think so... ideally, the "front line of support" lists should be -questions, and perhaps -current (when it is specific to -CURRENT) and perhaps -stable. A PR should only be filed if it has been determined that we have a real problem at hand. (For which reason it would be fitting to rename send-pr just like OpenBSD has done: they call it sendbug, because it is just that: We are not expecting *Problem* Reports but rather Bug Reports via it) A specific maillist is not such a good idea since people should be able to report legit bugs (even if in a not yet totally analyzed state) without being subscribed to any mailing list. Any communication later can happen via the PR system. (Now even the bug-followup@freebsd.org alias exists for such communication, although I assume it is just a shorthand for gnats-submit@ since it is not obvious to many) If you are not sure it is a bug, it is better to bring it up on a frequented mailing list so that people can comment on it. > I suggest that a "C.1.4 List Creation" section be added to > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html > but I don't know what to put in there. Maybe "Contact postmaster"? Yeah. And he will decide in his sole discretion if he will grant the request. We have seen example where a maillist that was not allowed on FreeBSD.org mailservers became successful but the opposite has also happened, more than once. Eg the freebsd-printing list is still at @bostonradio.org last I checked. But it can also be said that FreeBSD already has to many mailing lists which is also sort-of true. Just look at mailing-lists.ent recently:-) > 2) The above web page should have the list charter for freebsd-www; the > description under "Limited lists" ("Maintainers of www.FreeBSD.org") is > rather unhelpful. I thought that's what -doc was for. Yes. But the "Webmasters" hang out there. If you click the email link on the bottom of most of the www pages, the email goes to that list. > 4) Since mailing addresses like "doc@freebsd.org" are permitted, it > would be helpful to have that stated on the page. I'm not sure if it's > true for only a few lists or for all which start with "freebsd-". This is tricky. Up till very recently I was convinced that the dual addressing scheme whereby all mailing list names were valid with or without freebsd- was due to history and that it was just a "transit" measure albeit one that lasted quite long. The basis for this statement is that I saw some really old announcements from JKH, those were sent to freebsd-announce before the freebsd.org domain even existed. So at that time the freebsd- prefix was even necessary to show that this list had to do with freebsd. (As I recall the addresses were then in the .cdrom.com domain but I may be wrong.) At least -announce and -questions existed even way back then, and I think maybe even -current. Later as the freebsd.org domain came along, the prefixes are pretty much unnecessary but were retained so that (I guess) old configs and subscriptions would continue to work, and even added for new lists. Up till (I think) this summer it appeared to be the same if you subscribed to doc@ or freebsd-doc@ and posting still works to both addresses. But subscribing doesn't. If you attempt to subscribe to the address without the freebsd-, for the "Limited lists" you get an answer to try the variant with the prefix. (Eg -announce. Subscribe to announce@freebsd.org. Try it. See the error message.) This is almost OK in that you get instructions to try again. But with non-limited lists, your request (at least in my recent experience) is simply *ignored* and you get *nothing* back. This is definitely wrong. Now I am just wildly speculating from here on, since mailing list management is not in the least "open" on FreeBSD.org, you can only learn about the configuration by tripping up some traps and learning as you go. So. I assume that for some lists (most notably announce and security-announce) a duplicate subscription policy was instituted so as to allow subscribing in "read-only" mode but at the same time keep a separate list of people who may also post. This *may* have happened in response to a series of pranks that were committed AFAIR last spring or even before that (and also happened to announce@openbsd.org) and which involved sending out fake Security Advisories (without PGP signature, of course) by forging the From: to some allowed address (and maybe then some, details are fuzzy). These "SAs"did not have flattering content about FreeBSD's security. This configuration change may have been an attempt to stop that from happening and now probably even authorized people can only post to these lists from within a trusted domain and may be using the address without the freebsd-. Now, why this change involved changing every list's config is beyond me, but I never had to manage majordomo, soooo... So the short story is: while posting apparently still works to both address variants, now the freebsd- versions should be preferred for subscription etc. (Except the only list which never had this prefix: cvs-all) > P.S. I found the discussion of "Limited lists" a bit nebulous, like > maybe it was trying to not be open about some things. Is subscription > screened? Is it really about "audiences" and "interest" (many of the > technical lists should then qualify) or really about limiting discussion > to important contributors (quite reasonably, eg, to keep "noise" down)? > Are they segregated just because they refuse to publish guidelines? Why > is -install not under "Technical lists"? While I do not know the answer to this question above, I would like to point out that -install is one of the lists, that are actually dead. Look over the archives, you will see that eg -install has not had a single message sent to it for more than two years now. (May be more, was just too lazy to look) These lists are easy to spot, the weekly archives will have a constant and small size like "3k" all the time. And while we are on topic, it would also be nice to add that there are actually rather strict requirements for *posting* (as opposed to subscribing) to FreeBSD.org mailing lists. Again, you may never find out, but who knows. Nowadays, when it is not the usual thing to have your very own leased line and IP space to play your own ISP, you are entirely at the mercy of your provider. So. FreeBSD.org lets you subscribe from just about anywhere, so far so good. But if you want to post, it appears that: The mail server that will try to connect to hub.freebsd.org (which will probably be your ISP's) must meet the following requirements: 1) It must have a reverse-resolvable IP. It is unclear if it is required that the forward and reverse resolve match, too, but maybe. 2) It must use HELO with its fully qualified domain name. Only using its hostname is guaranteed to fail, only using its IP is possible to fail. 3) I am not sure if the string in the HELO is actually checked against the result of the reverse-resolve, it may be. But for sure it must be reverse-resolvable. Otherwise your message will be kept in limbo until the sending MTA eventually gives up. (The error returned by hub is a Transient Failure, although it already knows that it is not going to accept your message, ever.) Although quite some people have been bitten by this (including me, I had to find about the "using only the hostname in the HELO" thing the hard way) the Postmaster and some hard-core users (in particular Ted Mittelstaedt, who, surprise, is an ISP himself) have always refused to do something about this or even discuss it. They will only tell you to fix things on your end, as if that was possible with a large ISP of which you are just a customer. Up till now these "requirements" are fully undocumented, although even OpenBSD does set a better example in this regard. (Oh, and of course the alleged spam-killer effect is far from 100% with this setup, in fact I get the most spam from FreeBSD.org lists. Just ironic.) I hope that you will be able to get some discussion going about Project interna, because quite unlike some "old hands" I do feel that, once this is a public effort where everyone's effort is solicited, it is only fair to treat everybody as equals, not as first-rate (core and some alumni) second-rate (committers) and the rest ("just" users, testers, bug fixers etc) and this involves making the "house rules" public knowledge, even if that means that a debate might start about them. It is just the right thing to do. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 15: 6:46 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail.ruhr.de (in-ruhr4.ruhr.de [212.23.134.2]) by hub.freebsd.org (Postfix) with SMTP id 4F2F637B41A for ; Tue, 26 Feb 2002 15:06:41 -0800 (PST) Received: (qmail 9848 invoked by uid 10); 26 Feb 2002 23:06:39 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.11.6/8.11.2) id g1QN0Pt52998 for freebsd-doc@FreeBSD.ORG; Wed, 27 Feb 2002 00:00:25 +0100 (CET) (envelope-from ue) Date: Wed, 27 Feb 2002 00:00:24 +0100 From: Udo Erdelhoff To: freebsd-doc@FreeBSD.ORG Subject: Re: Suggestions for handbook/eresources.html#ERESOURCES-MAIL Message-ID: <20020227000024.F191@nathan.ruhr.de> Mail-Followup-To: freebsd-doc@FreeBSD.ORG References: <1wzo1wufz5.o1w@localhost.localdomain> <20020226222521.GA1145@fonix.adamsfamily.xx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020226222521.GA1145@fonix.adamsfamily.xx> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Feb 26, 2002 at 11:25:22PM +0100, Szilveszter Adam wrote: > The mail server that will try to connect to hub.freebsd.org (which will > probably be your ISP's) must meet the following requirements: > > [list snipped] > > Up till now these "requirements" are fully undocumented Hmm, check the FAQ, the requirements are documented there. Yes, this was long overdue, but from what I see in the FAQ and the commit message for this change, I would not say that the postmasters blocked Michael when he started to collect the requirements. I have the distinct impression that the biggest problem was that for a long time, nobody cared to sit down, collect the information, and write a FAQ entry about it. To abuse an old saying: 'Do not assume malice if simly laziness is a sufficient explanation.' > in fact I get the most spam from FreeBSD.org lists. Just ironic.) Same here - I am really tempted to put a 'if it's for ue@freebsd.org and not in [list of mailing lists], just trash it'-rule into my .procmailrc /s/Udo -- Could you please explain why you need to smash a finger in a door in order to get a back trace?? What other grievous bodily harm does one need to inflict on one's self when kernel debugging? -- Andy Farkas on freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 15: 7: 8 2002 Delivered-To: freebsd-doc@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 8BFB137B400 for ; Tue, 26 Feb 2002 15:07:00 -0800 (PST) Received: from cfcl.com (cpe-24-221-169-54.ca.sprintbbd.net [24.221.169.54]) by idiom.com (8.9.3/8.9.3) with ESMTP id PAA72910 for ; Tue, 26 Feb 2002 15:07:00 -0800 (PST) Received: from [192.168.254.205] (cerberus [192.168.254.205]) by cfcl.com (8.11.1/8.11.1) with ESMTP id g1QN9dG56740 for ; Tue, 26 Feb 2002 15:09:39 -0800 (PST) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: In-Reply-To: <20020226182757.GC23959@panix.com> References: <20020225191122.A15283@chiark.greenend.org.uk> <20020226182757.GC23959@panix.com> Date: Tue, 26 Feb 2002 15:06:56 -0800 To: freebsd-doc@FreeBSD.ORG From: Rich Morin Subject: FreeBSD manual sets (was: yacc documentation) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 1:27 PM -0500 2/26/02, Adam Turoff wrote: >Do you mean the ones that were in the jointly published USENIX/O'Reilly >5-Volume 4.4BSD docset? Bingo. >What's the copyright status on those papers? These papers are in the 4.4BSD distribution, but missing from the FreeBSD distribution, largely because of copyright issues. AFAIK, these issues are now resolved, so the papers should be OK for anyone to include. >I was overjoyed when I found all five volumes in one fell swoop a couple >of years ago. Would it be possible to reprint them in their entirety >today? Would it be possible to work with USENIX to produce a new version >of something similar and up-to-date? I also own a set, which I guard zealously. OTOH, the sales of these sets sagged with each version, eventually getting to the point where publishing more was deemed impractical (i.e., not enough projected sales to merit an offset print run). In the meanwhile, however, I have been working on setting up DOSSIER, a demand-publishing service for Free and Open Source software. DOSSIER is already publishing selected documents from the FreeBSD distribution and could, in theory, print up a complete FreeBSD manual set. In fact, I considered doing a FreeBSD manual set, but decided that it would be so large that it would be inconvenient to use. Here are some numbers, tallied from /usr/share/man/cat?/*.gz in FreeBSD 4.5: section docs lines pages ======= ==== ====== ===== 1 590 203929 3375 1aout 8 743 15 2 212 19770 400 3 2019 355702 6371 4 239 29909 568 5 118 25387 443 6 43 4412 89 7 36 16484 269 8 335 47434 890 9 274 27174 540 Total 12960 The "pages" value is derived by counting lines and rounding up to whole pages. The values are somewhat inflated (section 3 contains multiple copies of some man pages and troff output is a bit more compact than nroff output), so let's figure 10 K pages of manuals for FreeBSD itself. That's 20 volumes at 500 pages each, and we haven't added in the papers, let alone the docs for anything in the Ports Collection. Pulling down several volumes to solve a given problem doesn't seem real convenient... Consequently, DOSSIER provides topical volumes (e.g., "File Systems: FreeBSD"); each volume contains a "working set" of documents on a given topic. I'm open to suggestions, however; if folks want a particular collection and I can print it, I'll be quite happy to do so! -r -- email: rdm@cfcl.com; phone: +1 650-873-7841 http://www.cfcl.com/rdm - my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 15:25:54 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 6B90D37B41C; Tue, 26 Feb 2002 15:25:43 -0800 (PST) Received: from hades.hell.gr (patr530-a221.otenet.gr [212.205.215.221]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g1QNPbI8013833; Wed, 27 Feb 2002 01:25:40 +0200 (EET) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id g1QNOQZ12981; Wed, 27 Feb 2002 01:24:26 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Wed, 27 Feb 2002 01:24:26 +0200 From: Giorgos Keramidas To: Joseph Koshy Cc: freebsd-docs@freebsd.org Subject: Re: Question on managing translations Message-ID: <20020226232425.GE11922@hades.hell.gr> References: <20020226101316.E58A837B405@hub.freebsd.org> Mime-Version: 1.0 Content-Type: application/pgp; x-action=sign; format=text Content-Disposition: inline; filename="msg.pgp" In-Reply-To: <20020226101316.E58A837B405@hub.freebsd.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2002-02-26 02:13, Joseph Koshy wrote: > > Question to the translation teams: How are we keeping our translation > efforts sync'ed up with the main pages? I check to ensure that every translated file has a line containing: Original revision: 1.2.3.x with the last version of the English sources it was synched with. Then one can use scripts to check: a) If a $FreeBSD$ line exists in a file. b) If an 'Original revision: ' line exists. c) What the proper path of an english translation in the repository would be. Here's where the CVS/Repository and CVS/Root files can help a lot. d) The latest english revision can be checked out with `cvs co -p' and it's RCS id extracted in a script. e) A simple comparison of the 'Original revision' and the RCS id from step d) is enough to know if there have been changes. Then manually using `cvs diff' for the revisions Original -> Latest of the english file, one can patch the translated text. This is where the requirement that whitespace changes and content changes are separated in different commits really shines... It makes things SO much easier :-) Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) iD8DBQE8fBkp1g+UGjGGA7YRArJnAJ9gcOS8Qms4clwtj+2jbgq3Jh5F8wCgwwIF SHcPtXI38edA2G2VrvQx3N8= =wmmV -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 15:41:12 2002 Delivered-To: freebsd-doc@freebsd.org Received: from hotmail.com (f214.law11.hotmail.com [64.4.17.214]) by hub.freebsd.org (Postfix) with ESMTP id CAE1237B423 for ; Tue, 26 Feb 2002 15:40:25 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 26 Feb 2002 15:40:25 -0800 Received: from 68.6.86.185 by lw11fd.law11.hotmail.msn.com with HTTP; Tue, 26 Feb 2002 23:40:25 GMT X-Originating-IP: [68.6.86.185] From: "Charles Burns" To: doc@freebsd.org Subject: Advocacy post Date: Tue, 26 Feb 2002 16:40:25 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 26 Feb 2002 23:40:25.0730 (UTC) FILETIME=[F704DE20:01C1BF1E] Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On February 25th, I replied to a post on the freebsd-questions mailing list which was asking for help with "Presentation of UNIX to an ignorant crowd" I recieved the following suggestion from swear@blarg.net (Gary W. Swearingen): >You wrote the best advocacy-related post I've read in a long time. > >Please consider asking doc@freebsd.org if they'd agree to putting it >up on freebsd.org if you'd agree to the necessary rework (by you or >maybe someone there). (Quote your message there for those who didn't >see it.) Unfortunately, I don't see a good "advocacy" place for it. > >Thanks. I didn't think it was so good as to be suggested for material on FreeBSD.org, but if so I would gladly rework it to make it appropriate. (And reworking it would indeed require!) The full thread can be read here: http://www.geocrawler.com/lists/3/FreeBSD/151/150/7939157/ Here is the post in question: ------------------------------ I have been in that situation myself and, let me tell you, it isn't as easy as it should be. As far as the server part: We all know Microsoft pushes "TCO" as a benefit of Windows. In many small companies, they have Windows setup well by some contractor and they really can hire a monkey to administer it, that is, they can hire a cheap MCSE that reboots the system when it starts to get flaky and the company is very often perfectly happy with this. The c*'s (CEO, CTO, etc.) are probably going to expect that you will say that BSd or Linux is free and Windows costs thousands of dollars (for a server), because that is what they have likely heard in the news and through the grapevine. They have also likely heard about how much cheaper MCSEs are (which they really are, most of the time) and how Windows, according to Microsoft, ends up being cheaper in the long run--this appeals to c*'s who concentrate on the bottom line. This is much easier to combat in a big company, because big companies will need enough servers that hiring a competant admin will be worthwhile. Anyway, what I usually do is talk about how much more reliable Unix is, I point to the Netcraft uptime survey and point to several case studies in which (NT, Exchange, IIS) either crapped out, was too difficult to maintain/configure for the MCSE, or couldn't handle the load that the Unix equivalent could. Zeus Webserver, for example, which is only available on Unix is far faster, more scaleable, easier to maintain, and can handle heavier loads than either Apache or IIS. (Apache 2.0 may be more competitive and would not be a bad thing to demo). Postfix and Qmail are both FAR faster than Exchange server (particularly Postfix) and are far more secure (particularly Qmail. Exchange does have some functionality that these do not have. Anyway, Unix software generally doesn't get flaky after an arbitrary period of time and is generally updated much faster than NT software. Point this out. Additionally, show some numbers from reliable sources of the percentage of NT webservers vs Unix webservers on the internet, and how that number relates to how many NT servers are defaced/hacked vs. Unix. (Big difference, but I am not that aforementioned reliable source) Point out that FreeBSD has been chosen above all else by bigwigs such as Yahoo, UUnet, etc. and demo the articles about how MS had difficulty transferring Hotmail to NT because it couldn't hack it. After blowing them away with fact after fact (all backed up and documented. !.), nonchalantly point out that all of this software (except Zeus if you use that) is free, that they need not employ someone to track the licensing, and that due to the license it MUST be free. Many c*s fear that they are getting what they pay for, so it is important that you stress the functionality, stability, and most importantly--the popularity of the software. How could Apache be twice as popular as IIS if it was crap? See--big company A,B,C,D, and E all use Apache. Do they know something we don't? Look, Ebay uses Zeus and says that their CPU usage went from 80% to 30%. Etc, etc. In the desktop arena, show OpenOffice (StarOffice won't be free other than for Solaris) and show how it can open office documents (be sure to pre-test the office documents, and make them big nasty complex documents and point this out) and show it saving the documents. One thing that impressed me about certain Linux distros, probably Mandrake as well, is that after upgrading a video card from a G200 to a G400, the system used the card without so much as a dialogue box, whereas Windows made me download the driver, install it, and reboot again. Point out how reliable Unix is, and ask rhetorical questions like, "How much productivity has been lost over the history of the company by Windows crashing, losing data, and the employees needing to wait for it to restart if, indeed, it ever did restart successfully?" Point out that OpenOffice can be modified for company use if needed (you have the source code, after all) and point out that Linux upgrades are also free and that there is never any pressure to upgrade whereas MS always finds a way to make you spend more on software. Very important: Show examples of companies and governments switching from Windows to Unix and being successful--I have seen several such stories on the internet. Many more will follow after StarOffice 6, which will be much cheaper than Office, is released I am sure. Show Evolution, Mozilla, and other popular apps accessing Microsoft services like Hotmail to show that MS's best efforts to make them incompatible have failed (though don't word it like that, of course) and, before the presentation, ask employees what some common programs that they use are and find a Unix equivalent--then find ways that it is better, which is usually easy. It takes quite a bit of work, but all but the most dedicated MS shop that does not have many custom MS-only apps will usually see the light. If the company has many custom Windows apps, well, it wouldn't be a good idea for them to switch. Don't bother mentioning WINE, believe me. (Though, during a presentation, you might have WINE preinstalled and setup and nonchalantly show Linux/BSD running some Windows apps) Good luck. Sorry for the lack of references, but I am not at home where such info is kept. ---------------------------------------- _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 15:50:16 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 56ACD37B417 for ; Tue, 26 Feb 2002 15:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1QNo1Q47285; Tue, 26 Feb 2002 15:50:01 -0800 (PST) (envelope-from gnats) Received: from fafoe.dyndns.org (chello212186121237.14.vie.surfer.at [212.186.121.237]) by hub.freebsd.org (Postfix) with ESMTP id 00AD637B400 for ; Tue, 26 Feb 2002 15:47:09 -0800 (PST) Received: by stefan.fafoe (Postfix, from userid 1001) id 13A24EA1B; Wed, 27 Feb 2002 00:46:10 +0100 (CET) Message-Id: <20020226234610.13A24EA1B@stefan.fafoe> Date: Wed, 27 Feb 2002 00:46:10 +0100 (CET) From: Stefan Farfeleder Reply-To: Stefan Farfeleder To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35361: [PATCH] more pedantry for ktrace(1) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35361 >Category: docs >Synopsis: [PATCH] more pedantry for ktrace(1) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Feb 26 15:50:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Stefan Farfeleder >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD stefan.fafoe 4.5-STABLE FreeBSD 4.5-STABLE #8: Tue Feb 26 21:34:20 CET 2002 root@stefan.fafoe:/usr/obj/usr/src/sys/MORDOR i386 >Description: In the synopsis of ktrace(1) the name of the argument to -f is `trfile' but later on it is referred to as only `file'. I think it would be nicer if those occurences would also read `trfile'. >How-To-Repeat: man ktrace >Fix: Index: ktrace.1 =================================================================== RCS file: /home/ncvs/src/usr.bin/ktrace/ktrace.1,v retrieving revision 1.14 diff -u -r1.14 ktrace.1 --- ktrace.1 11 Feb 2002 09:03:34 -0000 1.14 +++ ktrace.1 26 Feb 2002 23:10:42 -0000 @@ -85,9 +85,9 @@ .It Fl d Descendants; perform the operation for all current children of the designated processes. -.It Fl f Ar file +.It Fl f Ar trfile Log trace records to -.Ar file +.Ar trfile instead of .Pa ktrace.out . .It Fl g Ar pgid @@ -166,7 +166,7 @@ .Xr kdump 1 .Sh BUGS Only works if -.Ar file +.Ar trfile is a regular file. .Sh HISTORY The >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 15:59: 5 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by hub.freebsd.org (Postfix) with ESMTP id 0AC1E37B402 for ; Tue, 26 Feb 2002 15:59:02 -0800 (PST) Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mail1.panix.com (Postfix) with ESMTP id 21D074877A; Tue, 26 Feb 2002 18:59:01 -0500 (EST) Received: (from ziggy@localhost) by panix2.panix.com (8.11.3nb1/8.8.8/PanixN1.0) id g1QNx1627790; Tue, 26 Feb 2002 18:59:01 -0500 (EST) Date: Tue, 26 Feb 2002 18:59:01 -0500 From: Adam Turoff To: Rich Morin Cc: freebsd-doc@FreeBSD.ORG Subject: Re: FreeBSD manual sets (was: yacc documentation) Message-ID: <20020226235901.GA23559@panix.com> References: <20020225191122.A15283@chiark.greenend.org.uk> <20020226182757.GC23959@panix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Feb 26, 2002 at 03:06:56PM -0800, Rich Morin wrote: > At 1:27 PM -0500 2/26/02, Adam Turoff wrote: > >What's the copyright status on those papers? > > These papers are in the 4.4BSD distribution, but missing from the FreeBSD > distribution, largely because of copyright issues. AFAIK, these issues > are now resolved, so the papers should be OK for anyone to include. You mean like in /usr/share/doc/{smm|usd|psd}? :-) > >I was overjoyed when I found all five volumes in one fell swoop a couple > >of years ago. Would it be possible to reprint them in their entirety > >today? Would it be possible to work with USENIX to produce a new version > >of something similar and up-to-date? > > I also own a set, which I guard zealously. OTOH, the sales of these sets > sagged with each version, eventually getting to the point where publishing > more was deemed impractical (i.e., not enough projected sales to merit an > offset print run). > > In the meanwhile, however, I have been working on setting up DOSSIER, a > demand-publishing service for Free and Open Source software. DOSSIER is > already publishing selected documents from the FreeBSD distribution and > could, in theory, print up a complete FreeBSD manual set. [math that comes to 20 volumes of 500 pages of printed manpages] Ya know, I think the days of the Big (Grey|Orange|Beige) Wall are thankfully a thing of the past. The manuals have grown to the point where what's really needed is a fully integrated, cross referenced and hyperlinked online manuals. Much like KDE provides with man:troff type urls in Konqueror. But... > Consequently, DOSSIER provides topical volumes (e.g., "File Systems: > FreeBSD"); each volume contains a "working set" of documents on a given > topic. I'm open to suggestions, however; if folks want a particular > collection and I can print it, I'll be quite happy to do so! ...this approach seems like the happy medium. I don't know what the value of a printed version of section 4 would be, or how complete section 3 would be if it omits what manpages for what many programmers use today: perl, python, java, ruby, etc. 30 years ago, a printed version of man(3) was *very* useful because everyone was using C or C APIs. What would be truly nice if {smm|usd|psd|*} were to be resurrected to be current and modern. Many of the documents in /usr/src/doc/en would be applicable, but there are many gaps to be filled. Of course, with an all-vounteer project, this would be more than a simple matter of content aggregation to fill in the missing pieces... Z. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 16:47:30 2002 Delivered-To: freebsd-doc@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 2CDC437B400 for ; Tue, 26 Feb 2002 16:47:26 -0800 (PST) Received: from cfcl.com (cpe-24-221-169-54.ca.sprintbbd.net [24.221.169.54]) by idiom.com (8.9.3/8.9.3) with ESMTP id QAA44000 for ; Tue, 26 Feb 2002 16:47:12 -0800 (PST) Received: from [192.168.254.205] (cerberus [192.168.254.205]) by cfcl.com (8.11.1/8.11.1) with ESMTP id g1R0npG59372 for ; Tue, 26 Feb 2002 16:49:51 -0800 (PST) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: In-Reply-To: <20020226235901.GA23559@panix.com> References: <20020225191122.A15283@chiark.greenend.org.uk> <20020226182757.GC23959@panix.com> <20020226235901.GA23559@panix.com> Date: Tue, 26 Feb 2002 16:47:08 -0800 To: freebsd-doc@FreeBSD.ORG From: Rich Morin Subject: Re: FreeBSD manual sets (was: yacc documentation) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 6:59 PM -0500 2/26/02, Adam Turoff wrote: >> ... the papers should be OK for anyone to include. > >You mean like in /usr/share/doc/{smm|usd|psd}? :-) Yep. >Ya know, I think the days of the Big (Grey|Orange|Beige) Wall are >thankfully a thing of the past. The manuals have grown to the point >where what's really needed is a fully integrated, cross referenced >and hyperlinked online manuals. Much like KDE provides with >man:troff type urls in Konqueror. Online docs have significant merits, but so do printed docs. I don't see a conflict, however; use either or both, depending on your needs! >But... > >> Consequently, DOSSIER provides topical volumes ... > >...this approach seems like the happy medium. I don't know what the >value of a printed version of section 4 would be, or how complete >section 3 would be if it omits what manpages for what many programmers >use today: perl, python, java, ruby, etc. 30 years ago, a printed >version of man(3) was *very* useful because everyone was using C >or C APIs. Well, FreeBSD's section 9 takes up a lot of "Kernel: FreeBSD". I add in some other pages having to do with tools for working on the kernel, etc. Sections 2, 4, and 5 would each fill a DOSSIER volume quite nicely. The other sections, however, are a bit more problematic. One of the peculiarities of the current manual organization is that name spaces are spread across sections. Sections 2 & 3 both contain C calls; does anyone really care about the distinction between library functions and system calls? Sections 1 & 8 both contain commands, but RedHat differs with FreeBSD on the placement of some commands. As a result, a user can't predict which section a given page is in! Adding Perl calls into section 3 does NOT help the confusion. Grumble... >What would be truly nice if {smm|usd|psd|*} were to be resurrected >to be current and modern. Many of the documents in /usr/src/doc/en >would be applicable, but there are many gaps to be filled. Of course, >with an all-vounteer project, this would be more than a simple matter >of content aggregation to fill in the missing pieces... There is actually quite a bit of content lying around. Start with the BSD papers, add in materials from assorted conferences and journals, and you end up with a quite respectable bibliography. DOSSIER has shown that it can handle the mechanics of formatting and printing, but someone still has to pick the papers and obtain the appropriate permissions. I'm actively looking for "area experts" who would like to pick papers for topical volumes. If you want to see a volume happen and can spare a few hours to put together a TOC, please get in touch! Obtaining permissions can be anything from trivial to impossible, but I'm always willing to ask. -r -- email: rdm@cfcl.com; phone: +1 650-873-7841 http://www.cfcl.com/rdm - my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 18:33:33 2002 Delivered-To: freebsd-doc@freebsd.org Received: from eyepublish.no (gaia.eyepublish.no [193.71.199.34]) by hub.freebsd.org (Postfix) with SMTP id 54E7C37B41B for ; Tue, 26 Feb 2002 18:33:29 -0800 (PST) Received: (qmail 18146 invoked by uid 48); 27 Feb 2002 02:18:17 -0000 To: freebsd-doc@FreeBSD.org Subject: Translations/Other work Message-ID: <1014776297.3c7c41e91f96b@webmail.gaia.eyepublish.no> Date: Wed, 27 Feb 2002 03:18:17 +0100 (CET) From: inter@o12a.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.6 X-Originating-IP: 193.216.40.78 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Sirs, I have currently been injected with some "helping-out" vitamins, and in that case I am wondering if there's anyone working on the Norwegian translation of FreeBSD documentation such as installation instructions and so forth. My previous translation experiences consists of translating the "Virtual-Host HOW- TO" to Norwegian for the Norwegian Linux Documentation Project (NLDP) and began on the "X-Windows HOW-TO" which I have not completed due to lack of time. As I have long since moved on from Linux and joined the BSD community (I am a semi- regular on #freebsdhelp on EFNet as of late), I am interested in helping you guys out with some things. A bit about me: * I have years and years with Linux experience * About a year FreeBSD experience * Former AIX System Administrator at Bull (Now Integris) * Former Oracle System Administrator (large-scale Oracle/AIX oriented projects) * Some teaching Linux experience (Part-time instructor in NSA Linux certification) If you can use me for translations or any other work, please notify me of any proposals you might have. I will give them duly consideration. Thank you for your time and keep up the great work! Regards, Aasmund Eikli To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Tue Feb 26 20:23:14 2002 Delivered-To: freebsd-doc@freebsd.org Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by hub.freebsd.org (Postfix) with ESMTP id 45BCA37B405 for ; Tue, 26 Feb 2002 20:23:11 -0800 (PST) Received: from pittgoth.com (c2.depaul-inst.pittsburgh.pa.us [192.168.1.2]) by pittgoth.com (8.11.6/8.11.6) with ESMTP id g1R4P3914791; Tue, 26 Feb 2002 23:25:03 -0500 (EST) (envelope-from darklogik@pittgoth.com) Message-ID: <3C7C60AC.7020300@pittgoth.com> Date: Tue, 26 Feb 2002 23:29:32 -0500 From: Tom Rhodes User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2) Gecko/20010628 X-Accept-Language: en-us MIME-Version: 1.0 To: inter@o12a.com Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Translations/Other work References: <1014776297.3c7c41e91f96b@webmail.gaia.eyepublish.no> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org inter@o12a.com wrote: Yes yes, please help. You might the following link very helpful on how the FreeBSD documentation project works, it includes information on SGML, transaltional effort, and other bits of usefull information. http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/ Thanks alot, enjoy, -- Tom Rhodes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 0:27:58 2002 Delivered-To: freebsd-doc@freebsd.org Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id BA8F037B402 for ; Wed, 27 Feb 2002 00:27:55 -0800 (PST) Received: from pc4-card4-0-cust162.cdf.cable.ntl.com ([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16fzRK-0000fN-00 for freebsd-doc@freebsd.org; Wed, 27 Feb 2002 08:27:54 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.35 #1) id 16fzQZ-0000b3-00; Wed, 27 Feb 2002 08:27:07 +0000 Date: Wed, 27 Feb 2002 08:27:07 +0000 From: Ceri To: Szilveszter Adam Cc: freebsd-doc@FreeBSD.ORG Subject: [OT] Mail delivery [was: Re: Suggestions for handbook/eresources.html#ERESOURCES-MAIL] Message-ID: <20020227082707.GA2105@rhadamanth> Mail-Followup-To: Ceri , Szilveszter Adam , freebsd-doc@FreeBSD.ORG References: <1wzo1wufz5.o1w@localhost.localdomain> <20020226222521.GA1145@fonix.adamsfamily.xx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020226222521.GA1145@fonix.adamsfamily.xx> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Feb 26, 2002 at 11:25:22PM +0100, Szilveszter Adam wrote: > > The mail server that will try to connect to hub.freebsd.org (which will > probably be your ISP's) must meet the following requirements: > Otherwise your message will be kept in limbo until the sending MTA > eventually gives up. (The error returned by hub is a Transient Failure, > although it already knows that it is not going to accept your message, > ever.) It has to be a transient failure, as network or server issues may cause hostname resolution to fail, and an MTA shouldn't return a permanent error when that happens. I'll shut up now. Ceri -- keep a mild groove on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 2:31:56 2002 Delivered-To: freebsd-doc@freebsd.org Received: from lists.blarg.net (lists.blarg.net [206.124.128.17]) by hub.freebsd.org (Postfix) with ESMTP id 1484137B400 for ; Wed, 27 Feb 2002 02:31:52 -0800 (PST) Received: from thig.blarg.net (thig.blarg.net [206.124.128.18]) by lists.blarg.net (Postfix) with ESMTP id AEC66BD24; Wed, 27 Feb 2002 02:31:51 -0800 (PST) Received: from localhost.localdomain ([206.124.139.115]) by thig.blarg.net (8.9.3/8.9.3) with ESMTP id CAA30455; Wed, 27 Feb 2002 02:31:51 -0800 Received: (from jojo@localhost) by localhost.localdomain (8.11.6/8.11.3) id g1RAXuV08141; Wed, 27 Feb 2002 02:33:56 -0800 (PST) (envelope-from swear@blarg.net) To: Szilveszter Adam Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Suggestions for handbook/eresources.html#ERESOURCES-MAIL References: <1wzo1wufz5.o1w@localhost.localdomain> <20020226222521.GA1145@fonix.adamsfamily.xx> From: swear@blarg.net (Gary W. Swearingen) Date: 27 Feb 2002 02:33:56 -0800 In-Reply-To: <20020226222521.GA1145@fonix.adamsfamily.xx> Message-ID: <9f8z9fusbv.z9f@localhost.localdomain> Lines: 59 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Szilveszter Adam writes: > I very much appreciate you brought up this topic just now. I almost wish I hadn't. I wasn't trying to stir things up or chaff sore spots; just to note some fairly minor problems I noticed on one page. > If you are not sure it is a bug, it is better to bring it up on a > frequented mailing list so that people can comment on it. That's best, but some may not have the patience to see it through, since many questions are ignored or inadequately answered. The person I mentioned didn't like to see man page issues discussed outside -doc, but I think we agree he was wrong as the -doc audience is to limited. > happened, more than once. Eg the freebsd-printing list is still at > @bostonradio.org last I checked. But it can also be said that FreeBSD > already has to many mailing lists which is also sort-of true. Just look > at mailing-lists.ent recently:-) Is there a policy against listing non-freebsd.org MLs? I don't remember seeing any such MLs. > Yes. But the "Webmasters" hang out there. If you click the email link > on the bottom of most of the www pages, the email goes to that list. So are the many web-page comments seen on -doc mis-addressed? > So the short story is: while posting apparently still works to both > address variants, now the freebsd- versions should be preferred for > subscription etc. (Except the only list which never had this prefix: > cvs-all) It should be preferred to let the newbies know what the veterans know. > Although quite some people have been bitten by this (including me, I had Mine stopped working after I had been using the lists for a few weeks last summer without any known change at my end. Took me several days to fix. It's interesting to read that it might have been my ISP who changed something. (They went belly up a couple of weeks later.) I was silently cussing FreeBSD for not warning of upcoming rule change. > I hope that you will be able to get some discussion going about Project > interna, because quite unlike some "old hands" I do feel that, once this > is a public effort where everyone's effort is solicited, it is only fair > to treat everybody as equals, not as first-rate (core and some alumni) > second-rate (committers) and the rest ("just" users, testers, bug fixers > etc) and this involves making the "house rules" public knowledge, even > if that means that a debate might start about them. It is just the right > thing to do. I disagree that it's fair to treat everybody as equals. It's fair to treat the greatest contributors (past and present) specially, especially if it helps them contribute even more (eg, keeping low-contributors (ie, noise) off some lists). I do agree that openness is a very helpful thing, except in rare instances. Thanks for your interest. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 2:44: 1 2002 Delivered-To: freebsd-doc@freebsd.org Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id B9ABD37B400 for ; Wed, 27 Feb 2002 02:43:57 -0800 (PST) Received: from pc4-card4-0-cust162.cdf.cable.ntl.com ([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16g1Yy-0003KM-00 for doc@freebsd.org; Wed, 27 Feb 2002 10:43:56 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.35 #1) id 16g1Yn-00010k-00 for doc@freebsd.org; Wed, 27 Feb 2002 10:43:45 +0000 Date: Wed, 27 Feb 2002 10:43:45 +0000 From: Ceri To: doc@freebsd.org Subject: Re: Suggestions for handbook/eresources.html#ERESOURCES-MAIL Message-ID: <20020227104345.GB3715@rhadamanth> References: <1wzo1wufz5.o1w@localhost.localdomain> <20020226222521.GA1145@fonix.adamsfamily.xx> <9f8z9fusbv.z9f@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9f8z9fusbv.z9f@localhost.localdomain> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Feb 27, 2002 at 02:33:56AM -0800, Gary W. Swearingen wrote: > > That's best, but some may not have the patience to see it through, since > many questions are ignored or inadequately answered. The person I > mentioned didn't like to see man page issues discussed outside -doc, but > I think we agree he was wrong as the -doc audience is to limited. Out of interest: Are -doc committers allowed to commit to manpages, or do they come under the remit of source committers (since they are in src/) ? Ceri -- keep a mild groove on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 3:30:40 2002 Delivered-To: freebsd-doc@freebsd.org Received: from void.xpert.com (xpert.com [199.203.132.1]) by hub.freebsd.org (Postfix) with ESMTP id 9968837B405 for ; Wed, 27 Feb 2002 03:30:37 -0800 (PST) Received: from mailserv.xpert.com ([199.203.132.135]) by void.xpert.com with esmtp (Exim 3.22 #1) id 16g2Ee-0002Yj-00 for freebsd-doc@freebsd.org; Wed, 27 Feb 2002 13:27:00 +0200 Received: by mailserv.xpert.com with Internet Mail Service (5.5.2650.21) id ; Wed, 27 Feb 2002 13:30:36 +0200 Message-ID: From: Yonatan Bokovza To: "'freebsd-doc@freebsd.org'" Subject: &man question Date: Wed, 27 Feb 2002 13:30:27 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="windows-1255" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org &man.something.1 works. Why doesn't &man.some_thing.1 works? Best Regards, Yonatan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 4:30:58 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id C74D837B402 for ; Wed, 27 Feb 2002 04:30:55 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g1RCUqn62114; Wed, 27 Feb 2002 07:30:52 -0500 (EST) (envelope-from mwlucas) Date: Wed, 27 Feb 2002 07:30:52 -0500 From: Michael Lucas To: Ceri Cc: doc@FreeBSD.ORG Subject: Re: Suggestions for handbook/eresources.html#ERESOURCES-MAIL Message-ID: <20020227073052.A62061@blackhelicopters.org> References: <1wzo1wufz5.o1w@localhost.localdomain> <20020226222521.GA1145@fonix.adamsfamily.xx> <9f8z9fusbv.z9f@localhost.localdomain> <20020227104345.GB3715@rhadamanth> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020227104345.GB3715@rhadamanth>; from setantae@submonkey.net on Wed, Feb 27, 2002 at 10:43:45AM +0000 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Feb 27, 2002 at 10:43:45AM +0000, Ceri wrote: > On Wed, Feb 27, 2002 at 02:33:56AM -0800, Gary W. Swearingen wrote: > > > > That's best, but some may not have the patience to see it through, since > > many questions are ignored or inadequately answered. The person I > > mentioned didn't like to see man page issues discussed outside -doc, but > > I think we agree he was wrong as the -doc audience is to limited. > > Out of interest: > > Are -doc committers allowed to commit to manpages, or do they come under > the remit of source committers (since they are in src/) ? We can commit to man pages, but it's a good idea to run things by ru first. We have *extremely* particular mdoc rules... don't pretend to understand mdoc myself, I just know that ru is the master. :-) ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 4:49: 4 2002 Delivered-To: freebsd-doc@freebsd.org Received: from straylight.ringlet.net (discworld.nanolink.com [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id 536DC37B420 for ; Wed, 27 Feb 2002 04:48:32 -0800 (PST) Received: (qmail 791 invoked by uid 1000); 27 Feb 2002 12:48:08 -0000 Date: Wed, 27 Feb 2002 14:48:08 +0200 From: Peter Pentchev To: Yonatan Bokovza Cc: "'freebsd-doc@freebsd.org'" Subject: Re: &man question Message-ID: <20020227144808.A359@straylight.oblivion.bg> Mail-Followup-To: Yonatan Bokovza , "'freebsd-doc@freebsd.org'" References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from Yonatan@xpert.com on Wed, Feb 27, 2002 at 01:30:27PM +0200 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 27, 2002 at 01:30:27PM +0200, Yonatan Bokovza wrote: > &man.something.1 works. Why doesn't > &man.some_thing.1 works?=20 Uhm.. because &man.some_thing.1 is not defined as an entity? See doc/share/sgml/man-refs.ent for the defined entities. Hm; taking a second look at man-refs.ent, I see that there are indeed entities referring to manual pages which contain underscores; the entities themselves replace the underscore with a dot, e.g. &man.pkg.create.1; for pkg_create(1). If this was your question, it may be something related to the SGML and/or DocBook standard regarding entity naming; it just might be that an underscore is an illegal character for entity names. I doubt that, however; I think that this was more of a decision to reflect another level of naming hierarchy (e.g. all pkg_* pages refer to packaging utilities, and their entities all *seem* to be grouped under a &man.pkg. "tree"). I might be wrong though; maybe some doc old-timers could shed some light on that. It seems that the &man.pkg.create.1; entities date back right to rev. 1.1 of man-refs.ent, committed by Nik Clayton back in 1999. Nik, any ideas on why pkg.create instead of pkg_create? G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This would easier understand fewer had omitted. --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjx81YgACgkQ7Ri2jRYZRVO3kwCfaY7JaUGae6lwo3jrHtYsPVI/ gjEAn16Ybp4wuUcjn36Tgb4w+HcCpPJM =wiBo -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 5:26:42 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail.ruhr.de (in-ruhr4.ruhr.de [212.23.134.2]) by hub.freebsd.org (Postfix) with SMTP id CA12A37B405 for ; Wed, 27 Feb 2002 05:26:38 -0800 (PST) Received: (qmail 9490 invoked by uid 10); 27 Feb 2002 13:26:37 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.11.6/8.11.2) id g1RDLqW56483 for freebsd-doc@freebsd.org; Wed, 27 Feb 2002 14:21:52 +0100 (CET) (envelope-from ue) Date: Wed, 27 Feb 2002 14:21:52 +0100 From: Udo Erdelhoff To: "'freebsd-doc@freebsd.org'" Subject: Re: &man question Message-ID: <20020227142152.B56195@nathan.ruhr.de> Mail-Followup-To: "'freebsd-doc@freebsd.org'" References: <20020227144808.A359@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20020227144808.A359@straylight.oblivion.bg> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hoi, On Wed, Feb 27, 2002 at 02:48:08PM +0200, Peter Pentchev wrote: > On Wed, Feb 27, 2002 at 01:30:27PM +0200, Yonatan Bokovza wrote: > > &man.something.1 works. Why doesn't > > &man.some_thing.1 works? > > Uhm.. because &man.some_thing.1 is not defined as an entity? > See doc/share/sgml/man-refs.ent for the defined entities. which reminds me that I need to re-run makemanent (ports/fdp-tools) one of these days and fill in all the entities that are missing. > it just might be that an underscore is an illegal character > for entity names. That's exactly the reason why we have &man.pkg.create.1; and not the more logical &man.pkg_create.1;. Underscores are not allowed in an entity names. The characters + and [ are also illegal, given us entities like &man.c...1; for c++. > I doubt that, however; Just try it - open man-refs.ent, define &man.pkg_create.1;, use it in an .sgml file, and watch the system hurl. /s/Udo -- "Ich kann rennen wie ein Hirsch!" "Zustoßen wie ein Stier!" "Kämpfen wie ein Löwe!" "Wer sagte 'Saufen wie ein Kamel?'" - Hägar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 6:59:43 2002 Delivered-To: freebsd-doc@freebsd.org Received: from alpha.url.com.tw (alpha.url.com.tw [210.59.228.107]) by hub.freebsd.org (Postfix) with SMTP id C236237B400 for ; Wed, 27 Feb 2002 06:59:37 -0800 (PST) Received: (qmail 24180 invoked from network); 27 Feb 2002 15:58:24 -0000 Received: from acclife.url.com.tw (HELO ms72.url.com.tw) ([210.59.228.123]) (envelope-sender ) by alpha.url.com.tw (qmail-ldap-1.03) with SMTP for ; 27 Feb 2002 15:58:24 -0000 Received: from 210 ([210.58.191.64]) by AccSMTP/NT 2.5 [210.59.228.123]; Wed, 27 Feb 2002 22:56:10 +0800 Message-ID: <000801c1bf9e$fd8563c0$0300a8c0@58.94.72.ethome.net.tw> From: "=?big5?B?q8KvUw==?=" To: Subject: =?big5?B?vdCx0EZyZWVCU0QgUmVsZWFzZSA0LjMgpnCm86RVuPw=?= Date: Wed, 27 Feb 2002 22:56:49 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C1BFE2.0A0505E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C1BFE2.0A0505E0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable =A4=A3=A6n=B7N=AB=E4=A5=B4=C2Z=A7A=A4F=A1A=A5=D1=B0Q=BD=D7=B0=CF=AC=DD=A8= =EC=A4F=A7A=AA=BA=A4=E5=B3=B9=A1A=A4]=A8=CC =B5=DB=A5h=A7=E4=A4U=B8=FC=AA=BA=A6a=A4=E8=A1A=A5i=ACO=B4N=ACO=A8S=AAk=A4= U=B8=FC=A1A=A9=D2=A5H=B7Q=BD=D0=B0=DD=A4@=A4U=C1=D9=A6=B3=A8=BA=B8=CC=A5i= =A5H=A4U=B8=FC??? =C1=C2=C1=C2 ------=_NextPart_000_0005_01C1BFE2.0A0505E0 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable
=A4=A3=A6n=B7N=AB=E4=A5=B4=C2Z=A7A=A4F=A1A=A5=D1=B0Q=BD=D7=B0=CF= =AC=DD=A8=EC=A4F=A7A=AA=BA=A4=E5=B3=B9=A1A=A4]=A8=CC
=B5=DB=A5h=A7=E4=A4U=B8=FC=AA=BA=A6a=A4=E8=A1A=A5i=ACO=B4N=ACO=A8= S=AAk=A4U=B8=FC=A1A=A9=D2=A5H=B7Q=BD=D0=B0=DD=A4@=A4U=C1=D9=A6=B3=A8=BA=B8= =CC=A5i=A5H=A4U=B8=FC???
=C1=C2=C1=C2
------=_NextPart_000_0005_01C1BFE2.0A0505E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 7:10: 7 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B35BF37B405 for ; Wed, 27 Feb 2002 07:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1RFA1n74430; Wed, 27 Feb 2002 07:10:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 522F837B400 for ; Wed, 27 Feb 2002 07:02:04 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1RF24723852; Wed, 27 Feb 2002 07:02:04 -0800 (PST) (envelope-from nobody) Message-Id: <200202271502.g1RF24723852@freefall.freebsd.org> Date: Wed, 27 Feb 2002 07:02:04 -0800 (PST) From: Bob Johnson To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: docs/35378: Handbook has inaccurate description of freebsd-security list Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35378 >Category: docs >Synopsis: Handbook has inaccurate description of freebsd-security list >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: wish >Submitter-Id: current-users >Arrival-Date: Wed Feb 27 07:10:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Bob Johnson >Release: N/A >Organization: >Environment: FreeBSD Handbook page at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html and web page at http://www.freebsd.org/search/search.html#mailinglists >Description: Handbook description of freebsd-security mailing list is "Security issues". Mailing list is flooded with questions about how to use ssh, how to log in, how to configure IPFW, etc. Problem is multiplied by three responses telling them they should have posted their question on freebsd-questions. >How-To-Repeat: Subscribe to freebsd-security mailing list and expect technical discussion of security issues. >Fix: On http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html change description of freebsd-security mailing list to read freebsd-security Security aspects of proposed changes to FreeBSD or freebsd-security Discussion of security aspects of proposed changes or similar wording. Similar change required for http://www.freebsd.org/search/search.html#mailinglists I believe the proposed phrasing accurately summarizes the security list charter, which limits it to strictly technical discussion. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 7:11:42 2002 Delivered-To: freebsd-doc@freebsd.org Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by hub.freebsd.org (Postfix) with ESMTP id 4ACBC37B41C for ; Wed, 27 Feb 2002 07:11:20 -0800 (PST) Received: from pittgoth.com (lcl234.zbzoom.net [208.236.36.234]) by pittgoth.com (8.11.6/8.11.6) with ESMTP id g1RFDB915822 for ; Wed, 27 Feb 2002 10:13:11 -0500 (EST) (envelope-from darklogik@pittgoth.com) Message-ID: <3C7CF9B5.3090003@pittgoth.com> Date: Wed, 27 Feb 2002 10:22:29 -0500 From: Tom Rhodes Reply-To: darklogik@pittgoth.com User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 Cc: "'freebsd-doc@freebsd.org'" Subject: Re: &man question References: <20020227144808.A359@straylight.oblivion.bg> <20020227142152.B56195@nathan.ruhr.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Udo Erdelhoff wrote: > > That's exactly the reason why we have &man.pkg.create.1; and not the > more logical &man.pkg_create.1;. Underscores are not allowed in an > entity names. The characters + and [ are also illegal, given us > entities like &man.c...1; for c++. > > Just try it - open man-refs.ent, define &man.pkg_create.1;, use it in > an .sgml file, and watch the system hurl. > > /s/Udo > So this is why my system spit errors at me when I tried to use &man.pkg_add.1; hehehe. Add that to the primer some day please, it will most likly help alot of people ;) -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 9:21:49 2002 Delivered-To: freebsd-doc@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 3224A37B400 for ; Wed, 27 Feb 2002 09:21:45 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id g1RCXUx21205; Wed, 27 Feb 2002 12:33:30 GMT (envelope-from nik) Date: Wed, 27 Feb 2002 12:33:30 +0000 From: Nik Clayton To: Yonatan Bokovza Cc: "'freebsd-doc@freebsd.org'" Subject: Re: &man question Message-ID: <20020227123329.E1369@canyon.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5xSkJheCpeK0RUEJ" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from Yonatan@xpert.com on Wed, Feb 27, 2002 at 01:30:27PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --5xSkJheCpeK0RUEJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 27, 2002 at 01:30:27PM +0200, Yonatan Bokovza wrote: > &man.something.1 works. Why doesn't > &man.some_thing.1 works?=20 The SGML declaration we're using doesn't allow underscores in entity names. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --5xSkJheCpeK0RUEJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjx80hkACgkQk6gHZCw343XvIQCdGY3vT/FXUKLwiwobCFZ9uT0S DSoAnjrCs+gz28FeGhsEzm04hXlAbUDZ =lXvK -----END PGP SIGNATURE----- --5xSkJheCpeK0RUEJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 9:43:18 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 2FBD337B402 for ; Wed, 27 Feb 2002 09:43:10 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g1RHh9w64303 for doc@freebsd.org; Wed, 27 Feb 2002 12:43:09 -0500 (EST) (envelope-from mwlucas) Date: Wed, 27 Feb 2002 12:43:09 -0500 From: Michael Lucas To: doc@freebsd.org Subject: http://www.freebsd.org/internal/ Message-ID: <20020227124309.A64269@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org From redpixel, via IRC: There's a staff link on the subject URL. It goes to a nonexistent page in the Handbook. Someone obviously broke this link, for some purpose, so I don't want to put it back. Also, I don't have time to fix it this week, not until Black February staggers and lurches to its horrid conclusion. So, anyone want to find out: a) where the staff page went. b) create a patch to fix internal/index.html Would suggest browsing the CVS archive for hints as to its disappearance. We really need to scan all the docs when eliminating a URL, so as to catch these things. Anyone have a recommendation for an automated way of doing this? ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 9:47:20 2002 Delivered-To: freebsd-doc@freebsd.org Received: from columbus.cris.net (columbus.cris.net [212.110.128.65]) by hub.freebsd.org (Postfix) with ESMTP id 086C637B400 for ; Wed, 27 Feb 2002 09:47:13 -0800 (PST) Received: from ark.cris.net (ns2.cris.net [212.110.128.68]) by columbus.cris.net (8.9.3/8.9.3) with ESMTP id TAA57944; Wed, 27 Feb 2002 19:47:06 +0200 (EET) Received: (from phantom@localhost) by ark.cris.net (8.11.1/8.11.1) id g1RHkaj35972; Wed, 27 Feb 2002 19:46:36 +0200 (EET) Date: Wed, 27 Feb 2002 19:46:36 +0200 From: Alexey Zelkin To: Michael Lucas Cc: doc@FreeBSD.ORG Subject: Re: http://www.freebsd.org/internal/ Message-ID: <20020227194636.A34773@ark.cris.net> References: <20020227124309.A64269@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20020227124309.A64269@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Wed, Feb 27, 2002 at 12:43:09PM -0500 X-Operating-System: FreeBSD 3.5-STABLE i386 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Feb 27, 2002 at 12:43:09PM -0500, Michael Lucas wrote: > > >From redpixel, via IRC: > > There's a staff link on the subject URL. It goes to a nonexistent > page in the Handbook. > > Someone obviously broke this link, for some purpose, so I don't want > to put it back. Also, I don't have time to fix it this week, not > until Black February staggers and lurches to its horrid conclusion. > So, anyone want to find out: > > a) where the staff page went. Appropriate handbook's information was moved to articles/contributors. New location of this information is: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html > b) create a patch to fix internal/index.html > > Would suggest browsing the CVS archive for hints as to its > disappearance. > > We really need to scan all the docs when eliminating a URL, so as to > catch these things. Anyone have a recommendation for an automated way > of doing this? /usr/ports/www/checkbot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 9:49:52 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 7745A37B405; Wed, 27 Feb 2002 09:49:44 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g1RHnim64421; Wed, 27 Feb 2002 12:49:44 -0500 (EST) (envelope-from mwlucas) Date: Wed, 27 Feb 2002 12:49:44 -0500 From: Michael Lucas To: Alexey Zelkin Cc: doc@FreeBSD.ORG Subject: Re: http://www.freebsd.org/internal/ Message-ID: <20020227124944.B64269@blackhelicopters.org> References: <20020227124309.A64269@blackhelicopters.org> <20020227194636.A34773@ark.cris.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020227194636.A34773@ark.cris.net>; from phantom@FreeBSD.ORG on Wed, Feb 27, 2002 at 07:46:36PM +0200 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Feb 27, 2002 at 07:46:36PM +0200, Alexey Zelkin wrote: > Appropriate handbook's information was moved to articles/contributors. > > New location of this information is: > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html Ah, okay. Easy PR for one of you new guys... it's simple, but life still hates me right now. :-( > /usr/ports/www/checkbot Thanks, will investigate. -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 10: 4:27 2002 Delivered-To: freebsd-doc@freebsd.org Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by hub.freebsd.org (Postfix) with ESMTP id 6A56D37B41C; Wed, 27 Feb 2002 10:04:22 -0800 (PST) Received: from pittgoth.com (lcl234.zbzoom.net [208.236.36.234]) by pittgoth.com (8.11.6/8.11.6) with ESMTP id g1RI6F935676; Wed, 27 Feb 2002 13:06:15 -0500 (EST) (envelope-from darklogik@pittgoth.com) Message-ID: <3C7D2246.7000305@pittgoth.com> Date: Wed, 27 Feb 2002 13:15:34 -0500 From: Tom Rhodes Reply-To: darklogik@pittgoth.com User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: Michael Lucas Cc: Alexey Zelkin , doc@FreeBSD.ORG Subject: Re: http://www.freebsd.org/internal/ References: <20020227124309.A64269@blackhelicopters.org> <20020227194636.A34773@ark.cris.net> <20020227124944.B64269@blackhelicopters.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Michael Lucas wrote: > On Wed, Feb 27, 2002 at 07:46:36PM +0200, Alexey Zelkin wrote: > >>Appropriate handbook's information was moved to articles/contributors. >> >>New location of this information is: >> >>http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html >> > > Ah, okay. > > Easy PR for one of you new guys... it's simple, but life still hates > me right now. :-( > > >>/usr/ports/www/checkbot >> > > Thanks, will investigate. > > While the "new guys" should not only fix this, they should also put this in alphabetical order, the names list. Just like the contributers list, it would be easier to understand. This information is also in the committers guide, listing that new committers should move their name from the "contributers list" over to the "developers list" as a beginning commit job. I have nothing to do this afternoon... maybe i'll put some time into this.. ;) -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 12:10:15 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5A22337B405 for ; Wed, 27 Feb 2002 12:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1RKA1j79777; Wed, 27 Feb 2002 12:10:01 -0800 (PST) (envelope-from gnats) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by hub.freebsd.org (Postfix) with ESMTP id 7297737B400 for ; Wed, 27 Feb 2002 12:06:26 -0800 (PST) Received: (from darklogik@localhost) by pittgoth.com (8.11.6/8.11.6) id g1RK8LU35882; Wed, 27 Feb 2002 15:08:21 -0500 (EST) (envelope-from darklogik) Message-Id: <200202272008.g1RK8LU35882@pittgoth.com> Date: Wed, 27 Feb 2002 15:08:21 -0500 (EST) From: Tom Rhodes Reply-To: Tom Rhodes To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35384: [PATCH] added to handbook boot chapter Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35384 >Category: docs >Synopsis: [PATCH] added to handbook boot chapter >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 27 12:10:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Tom Rhodes >Release: FreeBSD 4.5-RELEASE i386 >Organization: >Environment: System: FreeBSD pittgoth.com 4.5-RELEASE FreeBSD 4.5-RELEASE #2: Thu Feb 21 23:00:49 EST 2002 darklogik@pittgoth.com:/usr/src/sys/compile/PITTGOTH i386 >Description: reading the source (bored, yes I was) I seen the use of " and replaced it with tags >How-To-Repeat: Read the source >Fix: Apply this patch ;) --- boot.diff begins here --- diff -ru handbook.old/boot/chapter.sgml handbook/boot/chapter.sgml --- handbook.old/boot/chapter.sgml Wed Feb 27 14:49:36 2002 +++ handbook/boot/chapter.sgml Wed Feb 27 14:54:59 2002 @@ -615,7 +615,7 @@ # name getty type status comments # # This entry needed for asking password when init goes to single-user mode -# If you want to be asked for password, change "secure" to "insecure" here +# If you want to be asked for password, change secure to insecure here console none unknown off insecure --- boot.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 12:28:37 2002 Delivered-To: freebsd-doc@freebsd.org Received: from lists.blarg.net (lists.blarg.net [206.124.128.17]) by hub.freebsd.org (Postfix) with ESMTP id EE88237B422 for ; Wed, 27 Feb 2002 12:28:00 -0800 (PST) Received: from thig.blarg.net (thig.blarg.net [206.124.128.18]) by lists.blarg.net (Postfix) with ESMTP id 9E307BC95; Wed, 27 Feb 2002 12:28:00 -0800 (PST) Received: from localhost.localdomain ([206.124.139.115]) by thig.blarg.net (8.9.3/8.9.3) with ESMTP id MAA09685; Wed, 27 Feb 2002 12:27:59 -0800 Received: (from jojo@localhost) by localhost.localdomain (8.11.6/8.11.3) id g1RKU2d08485; Wed, 27 Feb 2002 12:30:02 -0800 (PST) (envelope-from swear@blarg.net) To: Bob Johnson Cc: freebsd-doc@FreeBSD.ORG Subject: Re: docs/35378: Handbook has inaccurate description of freebsd-security list References: <200202271502.g1RF24723852@freefall.freebsd.org> From: swear@blarg.net (Gary W. Swearingen) Date: 27 Feb 2002 12:30:02 -0800 In-Reply-To: <200202271502.g1RF24723852@freefall.freebsd.org> Message-ID: Lines: 43 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bob Johnson writes: > I believe the proposed phrasing accurately summarizes the > security list charter, which limits it to strictly > technical discussion. The list charter itself is way too ambiguous and can easily be misunderstood by those who need don't already understand. FreeBSD computer security issues (DES, Kerberos, known security holes and fixes, etc). This is a technical mailing list for which strictly technical content is expected. People asking questions or attempting any discussion of firewalls, X authentication, shh, etc, even config problems, are going to rightfully consider it "strictly technical" until they learn to translate the FDP meaning. More words are needed in the charters and in the intro paragraphs. Also -- (This probably should be a PR, but I've too many better ones to write.) In handbook/eresources.html, at least, -security is listed under General lists: The following are general lists which anyone is free (and encouraged) to join: Sounds like it doesn't belong there and should be under Technical lists: The following lists are for technical discussion. You should read the charter for each list carefully before joining or sending mail to one as there are firm guidelines for their use and content. and that needs expansion of the first sentence. If they're intended developers only (I hope not), say that. If they're not to be used to discuss individual configuration problems, say that. I expect it may be hard to generalize, in which case, remove the catgories and just call for improvement of the charters. If any list is too lazy to help improve their charter, they will have only themselves to blame for high noise level. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 12:50:27 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7AD1C37B41D for ; Wed, 27 Feb 2002 12:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1RKo2c87143; Wed, 27 Feb 2002 12:50:02 -0800 (PST) (envelope-from gnats) Date: Wed, 27 Feb 2002 12:50:02 -0800 (PST) Message-Id: <200202272050.g1RKo2c87143@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Tom Rhodes Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Reply-To: Tom Rhodes Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35384; it has been noted by GNATS. From: Tom Rhodes To: FreeBSD-gnats-submit@FreeBSD.ORG Cc: Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Date: Wed, 27 Feb 2002 15:55:19 -0500 Tom Rhodes wrote: > Apply this patch ;) > > --- boot.diff begins here --- > diff -ru handbook.old/boot/chapter.sgml handbook/boot/chapter.sgml > --- handbook.old/boot/chapter.sgml Wed Feb 27 14:49:36 2002 > +++ handbook/boot/chapter.sgml Wed Feb 27 14:54:59 2002 > @@ -615,7 +615,7 @@ > # name getty type status comments > # > # This entry needed for asking password when init goes to single-user mode > -# If you want to be asked for password, change "secure" to "insecure" here > +# If you want to be asked for password, change secure to insecure here > console none unknown off insecure > > The more I think about this, the more I wonder if this change is apropriate... Any elder-doc-hackers want to comment? -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 15: 0:18 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A8F2037B405 for ; Wed, 27 Feb 2002 15:00:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1RN06311981; Wed, 27 Feb 2002 15:00:06 -0800 (PST) (envelope-from gnats) Received: from smtp.whitebarn.com (Spin.whitebarn.com [216.0.13.113]) by hub.freebsd.org (Postfix) with ESMTP id 854ED37B417 for ; Wed, 27 Feb 2002 14:56:09 -0800 (PST) Received: (from bob@localhost) by smtp.whitebarn.com (8.9.3/8.9.3) id QAA58312; Wed, 27 Feb 2002 16:56:08 -0600 (CST) (envelope-from bob) Message-Id: <200202272256.QAA58312@smtp.whitebarn.com> Date: Wed, 27 Feb 2002 16:56:08 -0600 (CST) From: Bob Van Valzah Reply-To: Bob@Talarian.Com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/35387: Minor patches to Vinum article Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35387 >Category: docs >Synopsis: Just fixing two minor typos >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 27 15:00:06 PST 2002 >Closed-Date: >Last-Modified: >Originator: Bob Van Valzah >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: >Description: Typos: I meant to type "stripe" and "strip" came out. I meant to type "mount_msdos" and just "mount" came out. >How-To-Repeat: >Fix: cd /usr/doc/en_US.ISO8859-1/articles/vinum *** article.sgml.orig Wed Feb 27 16:31:32 2002 --- article.sgml Wed Feb 27 16:32:10 2002 *************** *** 173,179 **** Both organizations are useful for spreading I/O requests across spindles since plexes reside on distinct spindles. A striped plex will switch spindles each time a multiple of the ! strip size is reached. A concatenated plex will switch spindles only when the end of a subdisk is reached. --- 173,179 ---- Both organizations are useful for spreading I/O requests across spindles since plexes reside on distinct spindles. A striped plex will switch spindles each time a multiple of the ! stripe size is reached. A concatenated plex will switch spindles only when the end of a subdisk is reached. *************** *** 1023,1029 **** &prompt.root; fdformat -f 1440 /dev/fd0 &prompt.root; newfs_msdos -f 1440 /dev/fd0 ! &prompt.root; mount /dev/fd0 /mnt &prompt.root; cp /usr/share/examples/vinum/bootvinum /mnt XXX Someday, I would like this script to live in --- 1023,1029 ---- &prompt.root; fdformat -f 1440 /dev/fd0 &prompt.root; newfs_msdos -f 1440 /dev/fd0 ! &prompt.root; mount_msdos /dev/fd0 /mnt &prompt.root; cp /usr/share/examples/vinum/bootvinum /mnt XXX Someday, I would like this script to live in >Release-Note: >Audit-Trail: >Unformatted: Bob Van Valzah To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 15:23:12 2002 Delivered-To: freebsd-doc@freebsd.org Received: from trex.fandom.net (CPE-203-45-124-249.nsw.bigpond.net.au [203.45.124.249]) by hub.freebsd.org (Postfix) with ESMTP id 542AB37B41A; Wed, 27 Feb 2002 15:22:56 -0800 (PST) Received: from localhost.fandom.net ([127.0.0.1] helo=fandom.net) by trex.fandom.net with smtp (Exim 3.34 #1) id 16gDPS-000IEV-00; Thu, 28 Feb 2002 10:22:54 +1100 Received: from 192.168.167.6 (SquirrelMail authenticated user andrew@fandom.net) by 192.168.167.1 with HTTP; Thu, 28 Feb 2002 10:22:54 +1100 (EST) Message-ID: <2477.192.168.167.6.1014852174.squirrel@192.168.167.1> Date: Thu, 28 Feb 2002 10:22:54 +1100 (EST) Subject: Parallel Port From: To: freebsd-doc@FreeBSD.org Cc: doc@FreeBSD.org X-Mailer: SquirrelMail (version 1.0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, It appears that much (most) of the BSD community is unable to get a local printer working quickly. Though the statement sounds odd please remember that most of us use network printers, not local printers -- so it hasn't been a huge thing. The gottch-yer being that the /dev/plip in GEBERIC takes the port away from /dev/lpt. There is reasoning for /dev/plip to be in the GENERIC as it `could' be used as one of the installation media (though one might question how often they'd have two computers ready for such an opperation). However, I feel the Handbook should at least cover this issue. Second issue is /dev/ppi which I feel definatly shouldn't be in GENERIC and should be in LINT only. Could you please pass my request to the appropiate people? P.S. the parallel issue surfaced as I wanted to provide people with a 'standardised' KDE environment including CUPS -- which couldn't poll the parallel port untill the /dev/plip was removed. Thanx very much for all your time & efforts. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 15:23:18 2002 Delivered-To: freebsd-doc@freebsd.org Received: from trex.fandom.net (CPE-203-45-124-249.nsw.bigpond.net.au [203.45.124.249]) by hub.freebsd.org (Postfix) with ESMTP id 542AB37B41A; Wed, 27 Feb 2002 15:22:56 -0800 (PST) Received: from localhost.fandom.net ([127.0.0.1] helo=fandom.net) by trex.fandom.net with smtp (Exim 3.34 #1) id 16gDPS-000IEV-00; Thu, 28 Feb 2002 10:22:54 +1100 Received: from 192.168.167.6 (SquirrelMail authenticated user andrew@fandom.net) by 192.168.167.1 with HTTP; Thu, 28 Feb 2002 10:22:54 +1100 (EST) Message-ID: <2477.192.168.167.6.1014852174.squirrel@192.168.167.1> Date: Thu, 28 Feb 2002 10:22:54 +1100 (EST) Subject: Parallel Port From: To: freebsd-doc@FreeBSD.org Cc: doc@FreeBSD.org X-Mailer: SquirrelMail (version 1.0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, It appears that much (most) of the BSD community is unable to get a local printer working quickly. Though the statement sounds odd please remember that most of us use network printers, not local printers -- so it hasn't been a huge thing. The gottch-yer being that the /dev/plip in GEBERIC takes the port away from /dev/lpt. There is reasoning for /dev/plip to be in the GENERIC as it `could' be used as one of the installation media (though one might question how often they'd have two computers ready for such an opperation). However, I feel the Handbook should at least cover this issue. Second issue is /dev/ppi which I feel definatly shouldn't be in GENERIC and should be in LINT only. Could you please pass my request to the appropiate people? P.S. the parallel issue surfaced as I wanted to provide people with a 'standardised' KDE environment including CUPS -- which couldn't poll the parallel port untill the /dev/plip was removed. Thanx very much for all your time & efforts. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 18:40: 5 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6DD8837B400 for ; Wed, 27 Feb 2002 18:40:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1S2e3r63505; Wed, 27 Feb 2002 18:40:03 -0800 (PST) (envelope-from gnats) Date: Wed, 27 Feb 2002 18:40:03 -0800 (PST) Message-Id: <200202280240.g1S2e3r63505@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Giorgos Keramidas Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Reply-To: Giorgos Keramidas Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35384; it has been noted by GNATS. From: Giorgos Keramidas To: Tom Rhodes Cc: bug-followup@freebsd.org Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Date: Thu, 28 Feb 2002 04:39:24 +0200 On 2002-02-27 15:08, Tom Rhodes wrote: > > @@ -615,7 +615,7 @@ > # name getty type status comments > # > # This entry needed for asking password when init goes to single-user mode > -# If you want to be asked for password, change "secure" to "insecure" here > +# If you want to be asked for password, change secure to insecure here I think this should probably be left as it is. Looking at your followup, I assume it's ok to close this? - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 18:42:34 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D699537B400; Wed, 27 Feb 2002 18:42:32 -0800 (PST) Received: (from keramida@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1S2g5n63826; Wed, 27 Feb 2002 18:42:05 -0800 (PST) (envelope-from keramida) Date: Wed, 27 Feb 2002 18:42:05 -0800 (PST) From: Message-Id: <200202280242.g1S2g5n63826@freefall.freebsd.org> To: darklogik@pittgoth.com, keramida@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [PATCH] added to handbook boot chapter State-Changed-From-To: open->closed State-Changed-By: keramida State-Changed-When: Wed Feb 27 18:41:05 PST 2002 State-Changed-Why: Submitter says it's not that important. I agree that using in is not a very good idea anyways. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35384 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 18:52:35 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D8C9237B402; Wed, 27 Feb 2002 18:52:32 -0800 (PST) Received: (from keramida@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1S2pdP65050; Wed, 27 Feb 2002 18:51:39 -0800 (PST) (envelope-from keramida) Date: Wed, 27 Feb 2002 18:51:39 -0800 (PST) From: Message-Id: <200202280251.g1S2pdP65050@freefall.freebsd.org> To: code@psu.edu, keramida@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35282: typo Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: typo State-Changed-From-To: open->closed State-Changed-By: keramida State-Changed-When: Wed Feb 27 18:50:01 PST 2002 State-Changed-Why: I can't spot this in the current docs. Perhaps the Korean mirror mentioned in the PR has an old version of the documentation online? Can you please check with the maintainer of that mirror? Thanks for spotting this though :) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35282 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 19: 2:45 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 16D1937B421; Wed, 27 Feb 2002 19:02:33 -0800 (PST) Received: (from keramida@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1S2tYZ65899; Wed, 27 Feb 2002 18:55:34 -0800 (PST) (envelope-from keramida) Date: Wed, 27 Feb 2002 18:55:34 -0800 (PST) From: Message-Id: <200202280255.g1S2tYZ65899@freefall.freebsd.org> To: Bob@Talarian.Com, keramida@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35387: Just fixing two minor typos Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Just fixing two minor typos State-Changed-From-To: open->closed State-Changed-By: keramida State-Changed-When: Wed Feb 27 18:55:09 PST 2002 State-Changed-Why: Committed, thanks. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35387 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 19:14:11 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 40A8537B417 for ; Wed, 27 Feb 2002 19:13:56 -0800 (PST) Received: from hades.hell.gr (patr530-a024.otenet.gr [212.205.215.24]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g1S3DiN2002521; Thu, 28 Feb 2002 05:13:45 +0200 (EET) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id g1S3Dca47819; Thu, 28 Feb 2002 05:13:38 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 28 Feb 2002 05:13:37 +0200 From: Giorgos Keramidas To: Priit Piipuu Cc: freebsd-doc@freebsd.org Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Message-ID: <20020228031337.GA47751@hades.hell.gr> References: <200202262200.g1QM07w17418@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: application/pgp; x-action=sign; format=text Content-Disposition: inline; filename="msg.pgp" In-Reply-To: <200202262200.g1QM07w17418@freefall.freebsd.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2002-02-26 14:00, Priit Piipuu wrote: > > New, hopefully better patch. Looks ok to me. But I'll make this two separate changes. One to substitute "stuff" with stuff and one for the typo. Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) iD8DBQE8faBh1g+UGjGGA7YRAjqIAJ0ZSdLFRSygFE2bIRf6gcx8O8+UQQCgp99C XgrHLpbdCGI9NzG4q8WCaRE= =b3i7 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Wed Feb 27 19:58:30 2002 Delivered-To: freebsd-doc@freebsd.org Received: from spielberg.vip.uk.com (spielberg.vip.uk.com [194.176.218.9]) by hub.freebsd.org (Postfix) with ESMTP id 8EB2E37B417 for ; Wed, 27 Feb 2002 19:58:25 -0800 (PST) Received: from [62.60.68.16] (helo=yahoo.com) by spielberg.vip.uk.com with smtp (Exim 3.22 #1) id 16gHhr-0003l6-00; Thu, 28 Feb 2002 03:58:14 +0000 From: "For Sale" To: Subject: 1 Million Emails inc. 200,000 UK - £5 Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 28 Feb 2002 04:02:07 -0000 Reply-To: "For Sale" Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 1 Million world wide email addresses including 200,000 UK for just £5 inc P&P! The list comes on a CD in 2 files, one containing 200,000 UK email addresses and another containing 1 million world-wide emails (inc UK) , both in csv format. The emails have been collected from the internet, and have been physically validated in the last 3 weeks, removing aprox 25% bad emails from the previous amount, so there should be a very low failure rate. To purchase the CD please send a £5 cheque/PO payable to "Teletech" (no cash please) to: Teletech Office 434 405 Kings Rd London SW10 0BB United Kingdom The CD will be sent by first class post as soon as your money has been received. If you live outside the UK and would like to purchase the CD, please send a cheque for $10 US, or a cheque in your local currency [for the value of at least $10 US - Please do not send cash} NOTE: This CD does not contain any personal info of email owners (eg name/age etc) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 0:38:16 2002 Delivered-To: freebsd-doc@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 5710037B417 for ; Thu, 28 Feb 2002 00:37:29 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id g1S8GSQ10794 for doc@freebsd.org; Thu, 28 Feb 2002 08:16:28 GMT (envelope-from nik) Date: Thu, 28 Feb 2002 08:16:27 +0000 From: Nik Clayton To: doc@freebsd.org Subject: Warm fuzzies (was [senmonk6@yahoo.com: Re: FreeBSD] ) Message-ID: <20020228081627.H4562@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="TBNym+cBXeFsS4Vs" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Organization: FreeBSD Project Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --TBNym+cBXeFsS4Vs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Pats on the back all round folks. . . N ----- Forwarded message from Shaun ----- Date: Wed, 27 Feb 2002 22:03:22 -0500 To: Johnson David From: Shaun Subject: Re: FreeBSD Cc: freebsd-newbies@freebsd.org That was very well put. I completely agree. I also sympathize with the=20 frustrations of the "core." I am what you might call an intermediate user,= =20 who switched from Linux. The main reason that I choose FreeBSD over the=20 other flavors was the extensive documentation and mailing list archive. I= =20 have not yet had one thing that I needed to post to a list that I didn't=20 find somewhere else. Much gratitude goes towards the few who run everything. Shaun Newcomer Senior Server Administrator/Webmaster Mentor High School monk@mentorhigh.com At 06:37 PM 2/27/2002 -0800, you wrote: >On Wednesday 27 February 2002 06:16 pm, Gerardo Paredes wrote: > > > Mr Arrogant, you are right, newbies got to learn the Fine Handbook befo= re > > they ask lame questions. > >For any newbies that haven't figured it out yet, there are three fundament= als >reasons for checking the documentation before you post a question. First, = if >you post a question with an answer readily available in the Handbook, you >broadcast your lameness to the world. Yes, there will be times where you >overlook something and ask a lame question, but one lame question out of t= en >is much better then ten lame questions out of ten. > >Second, the people on the ircs and mailing lists are volunteers. They don't >get paid for taking the time to look up answers that you could have looked= up >anyway. FreeBSD Mall offers paid support plans if you wish to access tech >support people that actually ARE paid to answer your questions. > >And finally, learning about your system is a wonderful thing. But you will >never learn it if you keep insisting on being spoon fed. > >David (aka Mr. Arrogant) > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-newbies" in the body of the message _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message ----- End forwarded message ----- --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --TBNym+cBXeFsS4Vs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjx951oACgkQk6gHZCw343XSFwCgi/8RLv6bo+rH2kTcMbaR91DE LrUAn2tUa6WejQg6MFKKC7WA8HYVJDpA =fhw3 -----END PGP SIGNATURE----- --TBNym+cBXeFsS4Vs-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 0:38:31 2002 Delivered-To: freebsd-doc@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 7F2C937B402 for ; Thu, 28 Feb 2002 00:37:57 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id g1S8fph10944; Thu, 28 Feb 2002 08:41:51 GMT (envelope-from nik) Date: Thu, 28 Feb 2002 08:41:50 +0000 From: Nik Clayton To: Peter Pentchev Cc: freebsd-doc@FreeBSD.org Subject: Re: FreeBSD web build failed on freefall.freebsd.org Message-ID: <20020228084150.K4562@canyon.nothing-going-on.org> References: <200202181359.g1IDxip44049@freefall.freebsd.org> <20020218180524.A1671@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="IJAclU0AInkryoed" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --IJAclU0AInkryoed Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 18, 2002 at 06:05:24PM +0200, Peter Pentchev wrote: > It seems that we stumbled upon a DSSSL/DocBook bug: a > does not like whitespace, even if the whitespace lies between > a and the next . Maybe an entry was never meant to > contain more than one paragraph? It's an SGML 'bug'. From DocBook: The Definitive Guide[1], and the=20 section dealing with the element: =3D=3D Pernicious Mixed Content The content model of the Entry element exhibits a nasty peculiarity that we call "pernicious mixed content". Every other element in DocBook contains either block elements or inline elements (including #PCDATA) unambiguously. In these cases, the meaning of line breaks and spaces are well understood; they are insignificant between block elements and significant (to the SGML parser, anyway) where inline markup can occur. Table entries are different; they can contain either block or inline elements, but not both at the same time. In other words, one Entry in a tab= le might contain a paragraph or a list while another contains simply #PCDATA or another inline markup, but no single Entry can contain both. Because the content model of an Entry allows both kinds of markup, each time the SGML parser encounters an Entry, it has to decide what variety of markup it contains. SGML parsers are forbidden to use more than a single token of lookahead to reach this decision. In practical terms, what this means is th= at a line feed or space after an Entry start tag causes the parser to decide that the cell contains inline markup. Subsequent discovery of a paragraph or another block element causes a parsing error. All of these are legal: 3.1415927 General #PCDATA A paragraph of text However, each of these is an error: Error, cannot have a line break before a block eleme= nt A paragraph of text. A paragraph of text. Error, cannot have a line break between block elements A paragraph of text. A paragraph of text. Error, cannot have a line break after a block element When designing a DTD, it is wise to avoid pernicious mixed content. Unfortunately, the only way to correct the pernicious mixed content problem that already exists in DocBook is to require some sort of wrapper (a block element, or an inline like Phrase) around #PCDATA within table Entrys. This is annoying and inconvenient in a great many tables in which #PCDATA cells predominate and, in addition, differ from CALS. =3D=3D N [1] www.docbook.org -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --IJAclU0AInkryoed Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjx97U4ACgkQk6gHZCw343W7VgCfUR/uMcr0+3f35XQG0k0I9H2e 7UIAnRTuBWx4t4izC69TD6DB4ADt/IhX =LfLw -----END PGP SIGNATURE----- --IJAclU0AInkryoed-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 0:50: 7 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3353E37B402 for ; Thu, 28 Feb 2002 00:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1S8o2H43857; Thu, 28 Feb 2002 00:50:02 -0800 (PST) (envelope-from gnats) Date: Thu, 28 Feb 2002 00:50:02 -0800 (PST) Message-Id: <200202280850.g1S8o2H43857@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Ceri Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Reply-To: Ceri Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35384; it has been noted by GNATS. From: Ceri To: keramida@FreeBSD.org Cc: freebsd-gnats-submit@freebsd.org Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Date: Thu, 28 Feb 2002 08:43:15 +0000 On Wed, Feb 27, 2002 at 06:42:05PM -0800, keramida@FreeBSD.org wrote: > State-Changed-Why: > Submitter says it's not that important. I agree that using > in is not a very good idea anyways. > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35384 While it's not the same problem at all, I didn't think that /etc/ttys contained grammar quite that bad, and on checking it was changed two and a half years ago, so can we apply this patch to bring it up to date ? Ceri --- doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml.old Thu Feb 28 08:37:57 2002 +++ doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml Thu Feb 28 08:38:13 2002 @@ -614,8 +614,8 @@ # name getty type status comments # -# This entry needed for asking password when init goes to single-user mode -# If you want to be asked for password, change "secure" to "insecure" here +# If console is marked "insecure", then init will ask for the root password +# when going to single-user mode. console none unknown off insecure To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 1:34: 1 2002 Delivered-To: freebsd-doc@freebsd.org Received: from korovev.stm.it (korovev.stm.it [195.62.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D8FF37B402 for ; Thu, 28 Feb 2002 01:33:58 -0800 (PST) Received: (from wftuser@localhost) by korovev.stm.it (8.9.2/8.9.2) id KAA24578; Thu, 28 Feb 2002 10:31:44 +0100 (ITA) Date: Thu, 28 Feb 2002 10:31:44 +0100 (ITA) Message-Id: <200202280931.KAA24578@korovev.stm.it> To: doc@freebsd.org, stutz@dsl.org, kmia@smd.mega.net.id, loktony@hotmail.com, geser@tagem.gov.tr, curienlam@hkonly.com, teca@ilovechocolate.com, etabeta@esanet.it, mabramov@npp.cit.bg, krazy_b@iamwasted.com From: jenniepoo@aol.com () Subject: FREE Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Below is the result of your feedback form. It was submitted by (jenniepoo@aol.com) on Thursday, February 28, 19102 at 10:31:42 --------------------------------------------------------------------------- :: Come Chat for FREE at the TOP Adult Web Community TODAY! Don't Miss your chance to see and chat with GREAT people on the internet! Click here --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 1:44:49 2002 Delivered-To: freebsd-doc@freebsd.org Received: from iceberg.mrican.web.id (yogya.indosat.net.id [202.155.16.68]) by hub.freebsd.org (Postfix) with SMTP id B80E637B402 for ; Thu, 28 Feb 2002 01:44:40 -0800 (PST) Received: (qmail 3172 invoked from network); 28 Feb 2002 09:41:56 -0000 Received: from unknown (HELO nurseto) (202.155.16.17) by yogya.indosat.net.id with SMTP; 28 Feb 2002 09:41:56 -0000 From: "Seto ygy" To: Subject: pdf file Date: Thu, 28 Feb 2002 16:47:35 +0700 Message-ID: <000201c1c03c$f33397e0$090a0a0a@nurseto> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Sir, We interesting with freeBSD Operating Sytem, could you send us the installation guide (pdf file) ? Best Regards, FX nurseto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 2:21:33 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 9454337B400 for ; Thu, 28 Feb 2002 02:21:31 -0800 (PST) Received: from hades.hell.gr (patr530-a109.otenet.gr [212.205.215.109]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g1SALHN2029809; Thu, 28 Feb 2002 12:21:18 +0200 (EET) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id g1SALD467300; Thu, 28 Feb 2002 12:21:13 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 28 Feb 2002 12:21:13 +0200 From: Giorgos Keramidas To: Seto ygy Cc: doc@freebsd.org Subject: Re: pdf file Message-ID: <20020228102112.GA58460@hades.hell.gr> References: <000201c1c03c$f33397e0$090a0a0a@nurseto> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000201c1c03c$f33397e0$090a0a0a@nurseto> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2002-02-28 16:47, Seto ygy wrote: > Dear Sir, > > We interesting with freeBSD Operating Sytem, could you send us the > installation guide (pdf file) ? You can find the FreeBSD documentation online at: ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/ For instance, here's a copy of the Handbook in PDF format ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.bz2 (other formats are available on the FreeBSD ftp server and mirrors too). Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 4:53:21 2002 Delivered-To: freebsd-doc@freebsd.org Received: from spam.ru (ts18-a491.dial.sovam.com [195.239.6.237]) by hub.freebsd.org (Postfix) with ESMTP id 3574A37B417 for ; Thu, 28 Feb 2002 04:53:14 -0800 (PST) Received: (from ser@localhost) by spam.ru (8.11.4/8.11.3) id g1SCmha32062; Thu, 28 Feb 2002 15:48:43 +0300 Date: Thu, 28 Feb 2002 15:48:43 +0300 Message-Id: <200202281248.g1SCmha32062@spam.ru> From: uucp@ncal.verio.com To: doc@freebsd.org Subject: MIME-Version: 1.0 Content-type: text/plain; charset=koi8-r Content-transfer-encoding: 8bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 7:13:40 2002 Delivered-To: freebsd-doc@freebsd.org Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by hub.freebsd.org (Postfix) with ESMTP id C73BC37B4A8; Thu, 28 Feb 2002 07:12:31 -0800 (PST) Received: from pittgoth.com (lcl234.zbzoom.net [208.236.36.234]) by pittgoth.com (8.11.6/8.11.6) with ESMTP id g1SFEQ937602; Thu, 28 Feb 2002 10:14:28 -0500 (EST) (envelope-from darklogik@pittgoth.com) Message-ID: <3C7E4B77.5030702@pittgoth.com> Date: Thu, 28 Feb 2002 10:23:35 -0500 From: Tom Rhodes Reply-To: darklogik@pittgoth.com User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: Nik Clayton Cc: freebsd-doc@FreeBSD.ORG Subject: Re: FreeBSD web build failed on freefall.freebsd.org References: <200202181359.g1IDxip44049@freefall.freebsd.org> <20020218180524.A1671@straylight.oblivion.bg> <20020228084150.K4562@canyon.nothing-going-on.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Nik Clayton wrote: > On Mon, Feb 18, 2002 at 06:05:24PM +0200, Peter Pentchev wrote: Now we are all a little bit smarter ;) Sorry I cut your cute little daemon and name ;) -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 7:15:22 2002 Delivered-To: freebsd-doc@freebsd.org Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by hub.freebsd.org (Postfix) with ESMTP id 2F87E37B50E for ; Thu, 28 Feb 2002 07:15:11 -0800 (PST) Received: from pittgoth.com (lcl234.zbzoom.net [208.236.36.234]) by pittgoth.com (8.11.6/8.11.6) with ESMTP id g1SFH4937614; Thu, 28 Feb 2002 10:17:05 -0500 (EST) (envelope-from darklogik@pittgoth.com) Message-ID: <3C7E4C18.4050405@pittgoth.com> Date: Thu, 28 Feb 2002 10:26:16 -0500 From: Tom Rhodes Reply-To: darklogik@pittgoth.com User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: Ceri Cc: freebsd-doc@FreeBSD.ORG Subject: Re: docs/35384: [PATCH] added to handbook boot chapter References: <200202280850.g1S8o2H43857@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ceri wrote: Nice catch ;) I didn't even notice it when I was looking... Thanks for the point out. Now i'll agree to apply this patch ;) -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 8:30: 4 2002 Delivered-To: freebsd-doc@freebsd.org Received: from melchior.cuivre.fr.eu.org (melchior.enst.fr [137.194.161.6]) by hub.freebsd.org (Postfix) with ESMTP id 3A59B37B41C for ; Thu, 28 Feb 2002 08:30:01 -0800 (PST) Received: from melusine.cuivre.fr.eu.org (melusine.enst.fr [137.194.160.34]) by melchior.cuivre.fr.eu.org (Postfix) with ESMTP id DFBF983FE for ; Thu, 28 Feb 2002 17:29:58 +0100 (CET) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id ED7042C3D1; Thu, 28 Feb 2002 17:29:57 +0100 (CET) Date: Thu, 28 Feb 2002 17:29:57 +0100 From: Thomas Quinot To: freebsd-doc@FreeBSD.org Subject: sysctl.8 update Message-ID: <20020228172957.A29295@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Could someone please take a look at PR docs/34184? It contains a patch that updates sysctl.8 to reflect the newly-introduced possibility of specifying dev_t values as device special names. Thanks, Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 9: 0:17 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2058537B41C for ; Thu, 28 Feb 2002 09:00:08 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1SH08u69085; Thu, 28 Feb 2002 09:00:08 -0800 (PST) (envelope-from gnats) Date: Thu, 28 Feb 2002 09:00:08 -0800 (PST) Message-Id: <200202281700.g1SH08u69085@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Ceri Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Reply-To: Ceri Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35384; it has been noted by GNATS. From: Ceri To: freebsd-gnats-submit@FreeBSD.org Cc: darklogik@pittgoth.com Subject: Re: docs/35384: [PATCH] added to handbook boot chapter Date: Thu, 28 Feb 2002 16:50:45 +0000 For the audit trail : Giorgos has taken care of this. Ceri -- keep a mild groove on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 9:50:23 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D41C337B41B for ; Thu, 28 Feb 2002 09:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1SHo1a80590; Thu, 28 Feb 2002 09:50:01 -0800 (PST) (envelope-from gnats) Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id 5009F37B400 for ; Thu, 28 Feb 2002 09:48:06 -0800 (PST) Received: from pc4-card4-0-cust162.cdf.cable.ntl.com ([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16gUey-0003zj-00 for FreeBSD-gnats-submit@freebsd.org; Thu, 28 Feb 2002 17:48:04 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.35 #1) id 16gUej-000CcE-00 for FreeBSD-gnats-submit@freebsd.org; Thu, 28 Feb 2002 17:47:49 +0000 Message-Id: Date: Thu, 28 Feb 2002 17:47:49 +0000 From: Ceri Reply-To: Ceri To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35420: Fix some errors in my chroot'ing named section of the Handbook Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35420 >Category: docs >Synopsis: Fix some errors in my chroot'ing named section of the Handbook >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 28 09:50:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Ceri >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD rhadamanth.private.submonkey.net 4.5-STABLE FreeBSD 4.5-STABLE #0: Mon Feb 25 09:12:59 GMT 2002 setantae@rhadamanth.private.submonkey.net:/usr/obj/usr/src/sys/RHADAMANTH i386 >Description: - Update the doc now that the loopback ip6.int file is created as well - Fix a bad typo that results in this just not working - Change a "/" for a "." as it should have been anyway - Slap myself round head for getting these wrong in the first place Ceri >How-To-Repeat: >Fix: --- doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml.old Thu Feb 28 17:21:38 2002 +++ doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml Thu Feb 28 17:42:33 2002 @@ -4287,7 +4287,7 @@ &prompt.root; mv named.conf etc && ln -sf etc/named.conf &prompt.root; mv named.root master -&prompt.root; sh make-localhost && mv localhost.rev master +&prompt.root; sh make-localhost && mv localhost.rev localhost-v6.rev master &prompt.root; cat > master/named.localhost $ORIGIN localhost. $TTL 6h @@ -4379,7 +4379,7 @@ /etc/named.conf is denoted by a full pathname relative to the sandbox, i.e. in the line above, the file referred to is actually - /etc/namedb/etc/named.conf/ + /etc/namedb/etc/named.conf. @@ -4411,9 +4411,15 @@ }; zone "0.0.127.in-addr.arpa" IN { type master; - file "master/named.loopback"; + file "master/localhost.rev"; allow-transfer { localhost; }; notify no; +}; +zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.int" { + type master; + file "master/localhost-v6.rev"; + allow-transfer { localhost; }; + notify no; }; zone "." IN { type hint; >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 11:40:39 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9E3C037B41F for ; Thu, 28 Feb 2002 11:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1SJe1706247; Thu, 28 Feb 2002 11:40:01 -0800 (PST) (envelope-from gnats) Received: from core.radioactivedata.org (146-115-123-124.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com [146.115.123.124]) by hub.freebsd.org (Postfix) with ESMTP id 6042837B405 for ; Thu, 28 Feb 2002 11:38:15 -0800 (PST) Received: (from mbertsch@localhost) by core.radioactivedata.org (8.11.6/8.9.3) id g1S1wGa24290; Wed, 27 Feb 2002 20:58:16 -0500 (EST) (envelope-from mbertsch) Message-Id: <200202280158.g1S1wGa24290@core.radioactivedata.org> Date: Wed, 27 Feb 2002 20:58:16 -0500 (EST) From: Mike DeGraw-Bertsch Reply-To: Mike DeGraw-Bertsch To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35422: [PATCH] Nit typo in security.7 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35422 >Category: docs >Synopsis: [PATCH] Nit typo in security.7 >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 Feb 28 11:40:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Mike DeGraw-Bertsch >Release: FreeBSD 4.5-PRERELEASE i386 >Organization: >Environment: System: FreeBSD core.radioactivedata.org 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #0: Sun Feb 10 15:18:22 EST 2002 root@core.radioactivedata.org:/usr/src/sys/compile/GENERIC i386 >Description: security.7 reads "...by putting the min the wheel group..." instead of "...them in..." >How-To-Repeat: man security.7 >Fix: *** security.7 Wed Feb 27 20:46:39 2002 --- security.7.fix Tue Feb 26 14:23:15 2002 *************** *** 159,165 **** in the wheel group are allowed to .Sq su to root. You should never give staff ! members native wheel access by putting the min the wheel group in their password entry. Staff accounts should be placed in a .Sq staff group, and then added to the wheel group via the --- 159,165 ---- in the wheel group are allowed to .Sq su to root. You should never give staff ! members native wheel access by putting them in the wheel group in their password entry. Staff accounts should be placed in a .Sq staff group, and then added to the wheel group via the >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 13:17:21 2002 Delivered-To: freebsd-doc@freebsd.org Received: from ns.debtreliefnow.org (ns.debtreliefnow.org [63.197.117.207]) by hub.freebsd.org (Postfix) with SMTP id A236237B417 for ; Thu, 28 Feb 2002 13:17:17 -0800 (PST) Received: (qmail 15576 invoked by uid 0); 27 Feb 2002 23:42:03 -0000 Date: 27 Feb 2002 23:42:03 -0000 Message-ID: <20020227234203.15575.qmail@ns.debtreliefnow.org> Subject: Seven Things Creditors Don't Want You To Know From: help@debtreliefnow.org To: freebsd-doc@freebsd.org Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Seven Things Creditors Don't Want You To Know 1. The credit card companies are saturating Americans with debts they have trouble repaying. Of the approximately 1.8 billion credit cards held by Americans, a staggering percentage of those are at their limit or past due! 2. You have rights under the Fair Debt Collection Practices Act that protect you from intimidation and harassment. (And those harassing calls can be stopped immediately!) 3. Many of the tactics used by bill collectors are illegal!! 4. You can control the terms of repayment. 5. There are ways to get out of debt WITHOUT filing bankruptcy 6. You can be debt-free in as little as 15 to 30 months, at the same time reducing your monthly payment! 7. Your debt can be repaid with pennies on the dollar Don't let the financial stress control you and your family. Take charge! Get your FREE telephone consultation! Find out how to stop the worry TODAY! http://www.debtreliefnow.org/DebtForm.pl?email=freebsd-doc@freebsd.org_MSG7 --------- Removal Options: This is not SPAM. This email was sent to you because your email was entered in on one of our affiliate websites requesting to be opted into mailings such as this. If you would like to be removed from our list, please click the link below. Your privacy is very important to us, and we will honor all requests to have names removed from our list. Remove requests are honored automatically. http://www.debtreliefnow.org/remove.pl?email=freebsd-doc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 13:50:25 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9F85937B427 for ; Thu, 28 Feb 2002 13:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1SLo1U34173; Thu, 28 Feb 2002 13:50:01 -0800 (PST) (envelope-from gnats) Received: from vaio.alexdupre.com (212-41-211-209.adsl.galactica.it [212.41.211.209]) by hub.freebsd.org (Postfix) with ESMTP id 97F6F37B400 for ; Thu, 28 Feb 2002 13:47:08 -0800 (PST) Received: (from alex@localhost) by vaio.alexdupre.com (8.11.6/8.11.6) id g1SM28T00472; Thu, 28 Feb 2002 23:02:08 +0100 (CET) (envelope-from alex) Message-Id: <200202282202.g1SM28T00472@vaio.alexdupre.com> Date: Thu, 28 Feb 2002 23:02:08 +0100 (CET) From: Alex Dupre Reply-To: Alex Dupre To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35430: [Maintainer Update] Filtering-Bridges Articles Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35430 >Category: docs >Synopsis: [Maintainer Update] Filtering-Bridges Articles >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: maintainer-update >Submitter-Id: current-users >Arrival-Date: Thu Feb 28 13:50:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Alex Dupre >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD vaio.alexdupre.com 4.5-STABLE FreeBSD 4.5-STABLE #0: Sun Feb 3 15:53:42 CET 2002 alex@vaio.alexdupre.com:/usr/obj/usr/src/sys/VAIO2002 i386 >Description: Italian version: - completely reformatted - fixed two typos English version: - re-indented one paragraph >How-To-Repeat: >Fix: --- doc.uue begins here --- begin 755 doc.tar.gz M'XL("-!@@#P``$,Z7&1O8RYT87(`[7W[DQO'D:9_YE_1R]O5S$2`&)(2*8FF M>$>1U.W$4=*LAK+#X=AP%+H+0)F-+K@?&`[_^LLO,^O1#6!(R9)/%R&N8T5B M&M7UR,>77V;E5+X\M\W??KR:7UQ]_\47C[Z\]^#M?;IG.^.3]_]=W= MXJ]WGO[;J^_>7+SY2_$?Q<8T!X?B!RY>7<7QOC7-8.KBTJQL\:KI7>](SC#> MLSO_08/\\=J3:N^5^&WEEAU'GI-T_/ MY:=/S\/C:>#S`R/3A]EJPK^R]AX^"ANUZ/K6E'T< M>&M:\^S[)9UVX?K"=<70V>50%[TO*K=SE2U\8XOM^J9S)9UE8_MKW[XM3FOW MUA8D"*_ZM6WIT[.X`-?0=^FIHK,8O+?TE]7&-GU77#N:]M`7:[/#6=)S96OY MB6%!8W0S&K'"#`H3AZ,UTM'CV=HU;PMZW8;^L;)X[[QXL[9%97>NM/03TQ>E M;QI;TJOHQSP)G7"738]^1NN\-C=8+BVJ)GDWA=C!>?&\T,TKZ.AZ>ADFG0^5 M+]2V2U/:#@/9Q@^K-8;W;243IGTN3)?&CH?)FWYG=`3/]:&"9ULL;HJN-$W# MVT1+43&A5_DEG6+9^N9F\^S;YR](%O0?<5ZUW=FZ.`TGD[Y[AB_W<<>ZL%NT M?IJM->4:#[@^;58X[FRI."$:HRF6OKTV;15F2&)%^I9>,#DO5;U,@YZ> MCPP6/NEH/Q\4KOKJ[IZ+O7>]OKD[,FM_7M^(M!?Q816#_SDQ<#R#;WTK>[7! M7Y:M_<=`&U'?S"#[#6TM%(^VL?;7,E;I.]F41>M-52SHN[JF"QPHA$-%@':\ M*T[?O;QZ?<9O,'7GZ2A+@^FIU+2V&OA)?&!V9+_,HK9AP,O=9TG29G(J9.FV MIG&0&IKP2-HP8)S$P\\*L@LM9$.'HT\P#3Z5)1WH:>GM$$TNOG-#3>T(79=:X?C"Q2K)QGBT?RYEHL`C,BHR0GT=IK,@IB M3^1CB^F;%@HP>3=>4;VV?SCI, MSM<#;^N"72_]16W>ADP45KN@>6VW-1E@FNJLL`XR7%0#3UM,9Y^&OXZ:0O]MUSK$,NA83DQ-;O\=!IDTVQC6N?%/JML[4L_35B'6KO5FG325#M' M>S._LV<_Q];SGFQA/$,RH=@]6N_2K886AI[.QS6=;2&'F:W2]T$#PJ[AT1L2 MRV@SBO6P.,_L!5P9Q)Q$KQDV"UF!;/]XIO@;&X8/VXBUOQ[;B/_TUSCFBZ;K M:46'S,+SJLJV;K+Y;/:F+LV)%L&VNG*H^V#IKDC,;?'9_!'I>FV-'#0]O/5= MYU1-:E@2'/;>F\C5;7PU4'@1))'F;.EI.N/D\5N[&%PM]OXMMK6>P423""YO M@B_9MKXD8P-K5ZR`$'3`RIHZ2!/YGYH,';Y"*M`%&W9!)T,';]]M:T.^>.'[ M-<^#]D[\"OG][H`PC!P?QJ_:=V4]5("R:32LR[-V$^J:%U=T"H0A\.F"7&-1KCWY[6PT M4Y9>7;`766VLK<1)FX53_VXDR>OK9+^!C954;E*-GFP6H&NZ:604]TX[IR\`,+"4ZOE4UK;6FWXO%A.EO3=/0D0@_( M11.72Z/<%)NA$W.HPMA9^DZ<@=A7@9FLF.H09BSM?Z?OIK%<"Y,X+^!3_MGZE0)7O]Z0OR+)^67[Y[1RMNV:2^\5%K1!O4Y.DP MP>*)S),6PY:TX0%D8Z>@4:I$+'PCS]73TY`%/AP[+BP\55>MHWPA4 MYI"WNW*=0*2C+VG@"`SO/*X?N[HN38@R$-.`.K_ M\(A%%2-S-TJ]&-#_PY\6+_)]&AO7H`Y7K%FR7Y4M*23B^<)YL;K66#H<_+7% MX=*9VVID/F_7]T)_[RX_.;BAU=_?O[Z]8&/_O:G5S]\ M_?W5*QIT/-AXC]Z(!)*X4Y#&9XO8CM"?JV67U#FI21"-HD/SP%%-YN^+D3#' MP(`BMC8\J1!WM<(6!1_4!9`:OGIKL/4=66SQ;"1_I'NFO<&$Q3$I0NB-JFI# M\%,V?U[\A84":UOONXW)+I?ZS^+!."+@`CXX^(%&3>R$2+53\_Y MI<\*]8IA;\*[#@*VM?K!"D[Z&J=[4*7HD9P3JBTS/#B._AS@ MQK9SG`+X(?W9DP/[-5G56#EDI_Z&T;ZZ^Y=75W?WU>?0KB1F8D;HO@UH2$$; M[4';#]M9AE;S!2C'\-9G$U<\)I!H81F[L?42^D2IC6RX(.<7?<"("#)=*R8/ MVVEB/(VMA!<_/!VW75X?G(QZ=>C?>%IQ$#.0*--A@YHA'[YD^H?VP;ZSY9#+ M,VW+-BI:!@=%ZF^5\I^`R$G'34TN>GMW0DDVX#;IXR@%&%>DBZ.#C)? MR4AZ;&$*V<^XZ\$3JVJ=CO">X"J[!CUL:"BJ*%J(W,@.^)]C*9W]M3^B)CJ#=L`5Y<^*WMCF)@\U&VTE@!&`HT5<^G,PH6./X#/&- M4>`QCM=@WZL<6E'6%*JT=N,)U)'N M)CPMENI._+2_V=)GV/'L0Q)+VT^?5&=\S-1E^I!P`JR'1&J-@/E<2$Z%^Z&_ M11T1%;CS$6;&+8-O]WW`(%6P$J)F9[D1S6`(1Q0L;!@ARAL'+*<4WFI4R<,= M/82PBFQ.\KX,Q?0<1R*:N&8U"2);B^^,N&=)R(]Y2?Z*;E7`/@JFCI,B"R^B M,Y%%5F.TW'0ZXX2*H2Y;#_%):M$*>!\:!_L]O%W"8C3M!`1@KW-C]F2S`:,TP97@0&]%1RP05<-[((?F:0N9(GT M+)TL/'CEV0A1%*I,Y).8)2D3"32"RB(*D0U5@1`O#=*37&-:VJE@M`D#G-C1 M:\(B4;4#X?CRNZO$/B+L)?N.*5+\U9T%$)&=?]">LX_%=KDZ8T5&DWQ73^?(=G!>/.<#$]NBI\4*E]8ZTEZF=]E& M,4S8P*,1N.CH]4-3L_3D0H@=#6X\[.HLD-82#RES(K(GEK:5+)17FFZ2FHEY MGF/V[0W$AF%^(YQ9I+-2+/"6(H%Y\6?DJ]I!TFFT>!`^^I;P4K9](!Q;%B$Q M32-^BQ;6^]+7C#C)/CX)\>C%9>Y.="I=DN3G/V0\^OS(Y[+A:1@Z>K`KF7BD M!(>0YFO8:4ZV$N0IIMF^/39_E"LDDWECVS/F4E.ZDIE,\1>;S=#HT066*W#E MM"=KSBLEBZ4TE6CB;-]>J%(=\`2:1#RV*1$37D$`PPD$YTXF``QJ%6UWV"=> M719HV'>.$V'P5QSSJ`S$71/@JBQYR&($-!)R0$S8=FYGV>N-WA4<=BMX']\B MWW5OBFVSXQBO,ZSD+)HQW1A;1?"ZL"G'(U.RU2QZSRG(SORE@@U"PQO'&)BU MXZA:"3ER0L)(SD89>XI>L$U']&#CPB,%&:38LV/A#7[8:9V7@;2:SPK=S#(YP(`8)Q^W,Q3*W#4@V MMY[@P:83]Z^&K2=!9])"*>\-$H1,1,C^Y.;15GL'\!,"4H:!],$X'GVEG_)V M2)7,P611KW$+$N:S#%7F"IRCFA3M9#%V-%*;#:V9Y#KD=R`C:SJ*JE$K3_%Q M;=13PR-%HFZ_HB+#?K?[76SS;4XO&AC2=.9._74#8]V=32.BKB25;YY]@O3$ MMI^W).=_+)X.(-F;[="C>J?LN>IE#D9M+E4G2N^4R]57F-R3^S.:P1.:0_KB MG9\W),*9KQ[\\P.-QR#)DG4>#\6ZK2W=$EF\"4^?ISR2VHG!#YY!I6;"Z1Z- M[M1V9NK/%$O,%(Q#I>DP.2@^%/3D\IWK9Y8UDORO!#L:&V3>+<(/*9T07Q>, M,.))3F4)DKH9N\J4"VDR<_%[Z'=YI4I4#:,W;5B4H]0TH!<("OK4!]`)#Q\Q>:4H;;(@JP.1W5")N($X?[).X):)SG0;>R.*WKZC9Y ML^)"ODGOWSES$LPO@AI-+78W36_>,2J*IZK5CD*-<%R&(+IA>]>BY,(AY-.P MJ'8T&94SG>R8V:1XH6]=B,NY*@>K/=E2E"_+J5J_/4GN'J1!.(FX0W2*9N01 M"+7[[1HL8"E<*V!G5W#EZ$F%Y'%_,BM.5&+D14(,G_#>T_0#4`MBK8%`R%.B MO$?8'$EM5X(=]>1C81:HJC8G9@Z00Q1#V7I)@3RSA[RQB)//CL-D`K5T:*&R MYK/Y_5E(3I:0NFT/I2!CUW/&/=HQ&`/'4AAWRZT0NK84D2#@Y=V-<<*/+_,X M05Y%[$A/.K.#8(`$DVIV=9H3L M.]2P=F3DF1BE!>5E=J+BP+M2_D0XD//@&"-5=L;:G53;V4(9^+AHQ!*5?Y9B MT6]P2*J]71#P'>1`MO&MM5M:TBP=HIJNFBE+>@Q4)1*`ENR(K@0%H)@AK*>* M@R@-C50G"I@+3N;%UV'ZTSI`2-K=ELX'Z[S+RJGE?U/>:GQ@FER@;9B%9)GX M?A0UDD4CGXBJ9XZ\TP'*8(5"H3 MSEVQEI*RRK.9N$"LEU=X5>+Z^=199W,\'6?RYL7!0)V%F]?3A1P'AUSL]*(H M-#135@]9`,&"G@80@1*CU9BNO\&BZ&/1:@2;J$J-0A_+5-[:3APWBTG1,\Y; M`=;^8Z#O0SW(3KCWQU'C:XM-J'%I`8ZJ21MF`56*[WP?T+*X,D&/O=_2*GY* M)B"/)&M8ZAM,NJG`@8@S(2G)J6WOMPO:FHQKS".?VH\C'W9*UU8Q+\HSH4%A M/*[UL4$.$<;?``7,0_6`3"#AY>W`61"3*OF7B7D\!7M\?,US]N9Y#H0/5S/0 M@(%,)00%#/0U62,*V+-20)PB2MX_R(WF)/(U)R$Y48,Q)FG#CTV+20+L\,+N M'B^(.5I&^)N2]ES)41T6X/U+EK7 MO3V67LS&RW(;/[5($,8:*A<4Q6W,RC4V1_VW1_'3H'^4'+C66D(+,\M0^C2D M"\X"YW.`HM]CO_.1%),G"N[U\^^R^N:P`6_VL0'0@+)]3Q$.DC5K/1*F;@M? M>/?9@_G#^:?SSYZ>RT^?$8P(T$6IRF1?%7YE+GY49\V>9D7@2#!:4=8$PHKG M`0@I`A@8!*CFPXX?7@_IS_[_P+N:G!1IL\6@').?3\YP_G#Q[S-QX\_,BO?/EP_O@+ M^=4^=>()9$3X#PD^5(88:5WL_CZ MC*<'@%WTY5:G)U(4)L:NIP#HT3V-WQBJP]\X]*P[^.AXI:H9PG1,U\FA$%9Z M8,9XZ7@;20,_9N*'OWC;_`]^@\7LQ65(I,5%75W]Y^VS??@P/_?]&<>!OGUS MJ=5EF27!U3W-2!Y_#2I,Z$6//NY%[SFF0_'STK::J="PN*L9!`L&YRSH7ZNF M>SAO7#EW_7\?$J0O/YT_O/]H_O"S1W/6)@J5'GWZH8E<\G97B$!`<*/(6+#A MPO92@F50/>]Z#?/#53RF4,A,W[[C#QY\W`2PXKO_&,A:-?0B>[=H49MT^]B? M??G@T<-[CQ\]^O0#NTTO(0"])RXOO[O:/^1LPX\+\/[&_O05'5**8RL:K^7B MQ;?Y8OAM)PB13C+]*3<'-(@^!+KIBB\.3-BV+9UN3-@(":.L[PGNOEFNT_[X MEWSZT4\^>(!UO:(]5^MCZTXN\0U`3'TRZK5?)<.>QOI`]9&7&T=PK==K12I: M\9,B3_5W>OL*X0D3=D)?A*`#5Q00S%\TM#!<`AQJT^9)Y`;SZ=T]BN7\DDM/ M`V_(1!-CU)B)2A!PD']L<`.,QDA_>X.Z7@ MM,9EA,X(I;B-I-QCNEB>DCLID085YH,O\ZEW43;JFH,.,$RLB8A!?99&%&(5 M80-]%;8RUB>$O)O=&?&PXX(^#BE4A%,HV]@EKJ$-W7B5'``JM@H$8%BJ.$E) M%&L",(^+>]F[F.L6:B*=:[@SDQ\N5S>!NO#Y%;2PIPD9QTVJ))-[S24.%+VO MFI!XU:L3PF`,'94XLB%!.D\,=2&W%:C M(>597`S:6;OIY&`UR"9%J`;AP6VZG9SJ1V?YA2(639E.;5,F6QV#'@#7U4DV M2PN(A?N2K>FS*''">C]A#5)#8ZM(%Z4JY=7JEBN(;Z+F([,98WF>W(C"`:88 M'4$UI9#&I4^)Q3R(0&(*'`XK\EDM7VER69V]I*"^7X1R87R%;&!MP]'T6>2_ M),SAV_S$MTI9%SUN.LV$67.*5$S<\1B"G/*H2Q#M?;K>4=FN;-W"!-.FNX$4X6MF27_ M#0,.Q1ZVG51F92GGI)]B]*=W\>)U5,U`5AE[FTBB2`%MS%LIS&PSI<7.:O2H MF<_2MRW*G_.*JSEA$2Z(=BV592PXO2R'2VK0;')\X)I-D",_!CV_S';8K9!,D!=K%$E*N M<5$V/Q#-<(Y361@A.J&VI90/Y"[D6!.45*9+E*"Y>M&.4R]#"(WT<)-CQS5Y"Q_RC6+ MJ\H(FER4N6IT/\\JWQFZO*!4TJ,P+QUH>34[A@'(45R M56534YRWLX(G.BK;Q7!'.!;1T3Y-\L+BX$89U)"3Y2T(M68!#*9K,)J5%5/& M1:YLT<-E9+R;-ZJ^R2(@M4.S_+2#K28T'ZX MO.?0^[;;JWV(/SG8.83+UBA.T3(/Z(0VA6+]67"VGS:!C,RPK6)IG:G,=L(; M2UZZZ)'$DEH^GAX23VXE2M^<._?^YB% MX[N%R+>.+D6H72A]E=0KYGBY5$F_SG4C:^&&*UIW&:X3;2!(G39@T;J-39"1 M<.V(,[3[18=[R]`EK!#L\`4F3H#YX@T%)3^L:9(=Q[&`-ZA1X!*#F^+O?I$P M"9-*>AN,@YF+WM2.]EJJ\EO:&=BVVC2K`8VZ)O)QQA8H%$LW*XH;UT<%./;# M>?;_NOG9[W_^4/GRW/5_NWB3^O\]^J4;`-[>_^_1I_?OQ_Y_GS_ZG/O_/?[T M\]_[__TK_OQ_T/\O&Y1DE(S4@S@P_;OXXHO/OWSRX,LO'F=C/Z^0Z'P-,J=X M$`;3+__>4/"WTE#P:DM3\,4G=M42O/AC,?0`G])0$!%D@Y(CKB=`6\'BE#$3 M/CW43I#Q@=X&%!5[/<0N:+#B>X)`EAY#F,K!:NBF%0?%1@;NK"/M($F7?/WJP8G3N\"_3380QN`#WT-"(-BI3H$4QY_ M*6H[VC\^H,YC.RR>W5#(R!O&_PI!-VA?.@H:P.\,*LN&*%IQI!C$.)0P]GRZ M-0V^'2"`-+<=':6!:&F7P71.Z(V`%D)#DW9..X:E1DET\#Q/B!6"V)8# M]"`,6RMGS30$%]PY-&I$]1/!SY;T3!L08@,17HEPD*D@*87,@AJ.-X&&C6W1 M;R@36^Y!R'+7.!3BS_C<8!5(=?I/3#PD&E'//S(C(J!HM#EJ2XA$$(D(_8WG MC3W3-]O.K09?G)IBQR]I[(86'0:$9&]]+Q;*H3_A9*8\$6P!V98P M&T'64T>*AU;QW=<65PQ0Z&W#"896=]PV8N6AR'S7"ULL;UVUV7@PC*4C\84= MR56*3L&BB4*77\W=&%X*+@;+"=#IDA+%M`S.,UB4VJ4]IO?N]56`-&B'I^WP MB=G M/748>-OFX@'C1U%>XS`@/3&Z-.UOZ8]XZRO3,O7:OBD0AQW:O'GQR:OP_49# M11`ICL^X/H$S12@;>8=#F@QGB^`6E"!K(\LOR2R`@+\U[/PQDRH^;K:2.FQV MJ;F`9WN-:T=]FAP=2I@`C';:$6ZUR+9Y1R:"-"KKKAAM)?OX<`)U20M5 M06"U(DMC5XU1VS!1L"-+;'QOQV#EM<',@HEQ$A[S^'?C39,D,G:5ON^0Z(-PG;/G) M7\SPI:$A@>#VJK2';3P+0 MZM-T`XC"@0ZB7+30S8(.-Q/.@ZXJ;.K/;W/YK>T][4YU$MK7\&F,FDCES$@& M?XX:H'#!C"W8AO1W3:N.\"LI9&8-&&7AFL%+PXY'NV"B(V9\2K(Q,,(E@0FN MJ(7(A)KK`W/1LZX&P$WZ<68@!+W2,-RGA"_6!`\7FV-:;O-';P((HG715YNB MIN7#;<;[]H;EIV;FGB:8NITGB!:ED0GF\-WL%DT MXL>$TDI+AHT08Y+UDY0+,6PX-WB$L9^I4&\.N&+%]ECVYF1JZ"]QA-*0!_N0 MX$]V(<^:M4Z,%%A;1X%PF^'$<#?>22<-I$);\=;BV$V=80D.?V@%5<+%"4NN M8U,]0LJ0!Y*SD?"%SIO19SM`?XB<%8-7KN4V5VM"XTVR+Z0*M$>(!'8X`C7U M]!B-RE(8V=&=XY0?U`OYP#',18L7MEC1-/L9FQK&OZYF^Q1V]H*A/KT<_CX" MG,7`%T;HZXPI9Y";L!M^U]K%0M`83S#.JW=;CQ:=X^:<\^(U]R`&7MO`%9(I M%!DS#1E>#BFX,V?>'$+[[H/.D3?$88MT) MS$KTF!'4)H>[[U\E=I;]2**0G/_&M&6>>7$43G-S90B$-NG,?GJ66_W0KC,5 M12!R;=5?X_2RL,P9%IZ`E:%`P9>'9]5J]HD\9QT\9D-^>MO.%_M;%WH>CMH- MQG<$=7SANT^<;BS]OUYZ>79L4!50B?7-XYR=A=/PA3`!9B"[D;PIVTN_;R_Y M^+>L_13[4(!#;R&04IB1SX(DC8).+)@F'X*-D(RLT^]WD!OC#`RC$J!F"(#FO!W/K1$C/.]KS_)_UO^NMY?D)+T#ABWAOT8WJ",J3\=3N!OF!F7WE;(; M'<.(?Q!(5-JD@QF+ENGB#-$2+N>+)I*4+4=N.%=)$U32LCS'`8-&_M9:A>:\ M(Q,ONYWS2IA$L+M#C!!A*!]+9L$"FVGJ5''`:*`6M.H_T%X4M5F)"#VD7`0/ M+*[WI7UFZA?V0BV"O"CGU&_I[,>`HI%>C_OKREG9V$/4LZ\&1=JZ;7_@'ID6 M8>7O@1=GAYL9*?A]#V;%,*W"VZQ(.RK[K]QQ%+U&F?K>.>F8X0ZQ=1%WM@XB MP>`,>"3$*A/#5F!1&IO0$VMG$UUW:J)UAKU598.$B+(RDL*VHPTI(7;$ZF>S MZ/`L08Z^'](]T(8T;G4W^!@2 MBD&4K,4^EP$Q8%K?IUF&<\`YE:;#/6@'DM**J:+7LA7(@D#8.&Y$BCXCC,C0 M,78EV+G8A1%!!0%]M'F\#%P.X6F@I[@$T-A`W!BFC9B\(,1<19AWEK`[TSZ1 MPD2K4G"B'WO`O[U6I0?1324"HH>;^I4*8YTT;&35;K5I\6@;+CHBR%^L7,X< M`)S@IHD=\P)G,W%9HIZ&>]_A%FWMCTNKYMFD"+>/CN"64SK2CQLE/,;!.Y/J$0NG?!RI M-(?]2$*P&^XRLB2=5=>EK%FVF+7A>CV0K4A;!8!P0@;2;;R(6.J.&O%W1`JA M0;]))D%CXFPW&M,AG6.2)X[V,[1-Y>`EVHDI!?>R MU.@J*I.ZIX*:V,"V8.$B>'E,&C@130S#!-;IM[D%Z>0-4I+U-S5D"3&?G";N_ZQEZPX51!*B[U2#;O M;.!*2'U8F6@OQF%8[+E:J;$[VK1AXIAFW,55`H2/Z#D'&O]Y/#\V"3GA.:'Q M8//7AM,`#`S0'H1MR MRC<65<0^F+?EA5Z+5 M;@C&*TV`.4KV-/O!0"/O/.7N?C;FWPXO_HQ-H6D:'XI3N"H)J%ZMD$!YE"@% M1YYV?#]0R?.G6\D4RX&8-AY),Y`QNU4YOZ?=2KQ&VXIY9BBJ&"R/"'/?)Y52 MT;&%\O44TCU!2IYD1]8,0@\09`H^,J0$8NM64>XAPV7.>!2 M1M!ZQGO*U3\!:!Z+Q#`@62);95%-@$ORF% MZ5`/U.MW&[]QBF6K:058!K0^@`P^T`(=%B74>?S>`?9HA!ONS++[`"!V^7GL M3-+0)`_)8\9(5,*YD:DC[*A&:O,'.\(9TS71#+\)YQR4%PPJ)V MO0`USG$65S8W^3$9-4NN0>E$SU;_<+PY2B%QWX'@JOZ%'6-I(LKRC'-6']4K M-C%F"8CP;G.66=.KQ^*THR:2;=D_U34VLY1[C6-_AJO54AHYU2UP%V\13%&= MVFXR'Z(DQ^B7&H7\+/+>.&TI$2@TJHYIU>*%`.=)>:4TEHW9*$EZB-;,)@5J M<)K`0S9-ZV`U34ZQ"E1/99:DWSF8BJ`H.L(4CL<4?YG'$ND6_GNQ/OEPI?Q^ MB2:N4F)NK4<(^*O*H0)GU1:A%$#>(R1DC!ZH8IS%E!L M-$B!%]>D?VA"N]VB@$8:T>8T71[&;XP+2F=25UK!T!1PI3N5(]2>Z*V.!)'S M(1E'A,JXTC#8*_E^'%@,CFV9,JJX2(6^4MM5^MTV/X9X4GK5BBYFU?30@)AV MELA$MKX?:&?+.:%Q0]LQU$53VUZLVX&NMCH1X7IR6>%RM2K6VR@C/%GK M-.`:M3F=Z5V,AF]0H+1'B64;(O&0N#(I2I`BYYEF[D!5+]!U5LLDF:A0LHYY M<[',1G>5_D6XP.1E3JFPM+!2`LZX02IY3S?@CQYQ&&\ MA#.I%W'C0FX6+:T3;L2W@%YI7'0P?+QA."[>3!9UHW4I*\PAFG[=@*X$^<,_ MKZ`)X>I-9!FD!*Q@'#,OOC6A[GTTP:Q,Z2ZJ%]L*!6QWY4""H5:U\\?:US*M MP[7H-G(PXU-I;#@![I4+5R,\\XX"L;`\%\FN(^^94*VA>F!>O#X)Y&W,_:.5 M,/-:M"OPFYQYC%+1F>E@"6\NF=[68&.?0!FUJ@BD:%IV%#4*7'KQUT)):10063+4,^NL&`G-VFJ45CO+4MS3:#97).9).Y$DL M):XU\JL^.DLKZ00;_1CDPTBK76CQ@>I333S2.+]FU]UCQ$+8<<'*Y`8>VO8;^X;K#*R_LTL7XTE_[!`N-) MQM.%;$C4/K?A)KRLE+&4>"3Y!Z1]GT[)"SSK$\DV^;P!KTWYPUN)%\4N,H'& M'V^]2S;V2#Z2X&.",/7)1W?@#;@H(9A-5K>_SJ^='&F-M@OIW8R'/=MJQG-B:3 M["*ZEG;\=U0U<^81/2Y/NS$EE"64I&`IQAG_`;Z]J;%X](N$U=Z M33*C!HYN@@<*;_QOM)GOE:9K"2SE*_T%^OFFL=#2E^,M,4^,K7_!?K[Q18ZO M5"QM\!IT(N]]H[$>XL^\I:_2IP@6?IWNOJ\YHY3E^+B9$*=9N5G7DZ0'>E&& MD1IYSC[BMIVI.->(B"&?!AH"CT7D%^D&_'-7^?,[!(?UH5,PVATK.3\IJO\G>P9'@:]%O+B&$3FS MF"!$>0^:"DMG`3&E_E_32_C-T`LYVXZ)B`@"LC)C1$B:(:<-*K4JB6+.K,NPQ^4$(1-#%*1QANAS$?/HH>]P MNLMU]&YJ`!B27NC]OZ[C\/<[6KY>":/X.12!,2J.R'-,R!HPQ1O#M!OPC\MJ MQNH]@OR_I#YV1#9S&,^<(BA8#8MWCA`:XRBSSS,S_2ZOYS-!'0JFC-_9A!X& M5K$":T#>?%B'$GH9,K\$:3MEM^UFP1RSK$86KYB9"Q]"F?#TOBI'\8GVR>Y) M\O7!_(A)%H$4LGO[!TO*(O?D19>4BV/RO3QZGN^48LA8T8M=Q\:$ M!L0^XBBM,P\5YC/P=5#61*,OI\49V=8%[C5&G4'&M"N#SWY]/:K%LXO"Q[(B M3SA),VZ!$BW8`6(?%;.W43[( MO"D8VB+6./&]@GGQ?:1'0_3(_32E;HYGRT5_B4D?D2QYHDCN0Z/!0[SB.PO1 M&DXKY?&X@HQS*$TZNM@T0R.Y4U=K3^-)47/R*[AA+3_N-=37E7!!8@QSI;WQ MJ.GQV2&R;`:#-RH-"RV/+3<\3K=ZN1Z)MHI4H1=BMTV]%V;"]F25J3967^Q2 M$7*TI@YI")<*`^8'Z/_\6FEB*N3"JG*M=,1*DB!6$HP*_R25]9EHVVE7YE-U'+*B# M(JWZ)(@?K&K666/2ZD7Z*[LZ7X'927F6)H*&3A!(M&:Q MSW*6RYIDQP+)P;U[3R6S`?!^F,(F:;T*/9:#C.EME`.M%;B)#*X+F;R_2^#+ M0G61VO=:?;2FC.QT,*V.JU/)XA(%5NS^->^BY/,W(\W9KWIG&Y^^$`IRX130 M<3DT,F8!]W%]TF)C[ZBU*W.H0>24/7(,AT6S]229;99WSZ,"D?IX!#.N)Y#[ M/K%076X.<3,I37^`?IIFTB;-F6&Q-%D6%J=7_/>BNK/;'"E?JLQ*@'&9R9_D M(%721+X''`/(#?!VDC^98)A,8ME\:QUD5MQZ@/`).QBKDO'56\B1>?&#I*QZ MJYAN9+4"G/2[@2O<&15J4;STJG52-!0=Y!9U&EP28%LT<''9??N@GWV/P=4C MZMV[P%5)]NE]R,S@6%J_AR8SFG1$]4`)[*B0,GM34*U4Q3ZQ5%(+@1;*:0@V M>.@!;;4#--E$]::9E'+FLG0!\F5U51FD"$DZ+GTPHYV99UD2K33X&'[Z)'HK M]GAY/3M>,!_5<\24GR3;)Z\[F6S6Y#>'<&U9+WG`)&*V#)TSIM4%X=>,R)ZJ M34R75F%^$X[+M M&3=-\@C\HP_BOBIR"Z!GUA00/D@@%Q'WM$5-J,>I?#EP!^9X64:+#R+='EH6 M\2]KQ3O)W.CUA]1AFM3H)_2&_A$5"2C**+!M2%-J20(J'$>=HC5O&/M$\RQ' MI5:W-1[27Y43RBEBG5=/#EJ#?#)0Z:)8)2$(I[Z;BDMG<3M.K\PZQ#H;+J0P 5L=[Z]S[,O_\Y_N?_`L5>DY4`J@`` ` end --- doc.uue ends here --- >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 14:52:40 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C00B037B400; Thu, 28 Feb 2002 14:52:34 -0800 (PST) Received: (from keramida@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1SMlTg47732; Thu, 28 Feb 2002 14:47:29 -0800 (PST) (envelope-from keramida) Date: Thu, 28 Feb 2002 14:47:29 -0800 (PST) From: Message-Id: <200202282247.g1SMlTg47732@freefall.freebsd.org> To: mbertsch@radioactivedata.org, keramida@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35422: [PATCH] Nit typo in security.7 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [PATCH] Nit typo in security.7 State-Changed-From-To: open->closed State-Changed-By: keramida State-Changed-When: Thu Feb 28 14:46:58 PST 2002 State-Changed-Why: Change committed to both -CURRENT and -STABLE. Thank you :-) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35422 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 17: 0:46 2002 Delivered-To: freebsd-doc@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 8F38037B41B for ; Thu, 28 Feb 2002 17:00:40 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020301010040.KWYE2626.rwcrmhc51.attbi.com@bmah.dyndns.org>; Fri, 1 Mar 2002 01:00:40 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id g2110e001512; Thu, 28 Feb 2002 17:00:40 -0800 (PST) (envelope-from bmah) Message-Id: <200203010100.g2110e001512@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Michael Lucas Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) In-reply-to: <20020226094226.B55250@blackhelicopters.org> References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> Comments: In-reply-to Michael Lucas message dated "Tue, 26 Feb 2002 09:42:26 -0500." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Feb 2002 17:00:40 -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org If memory serves me right, Michael Lucas wrote: > I propose an official one-week doc/en_US.ISO8859-1 freeze for > everything except the release notes, to give translators a little bit > of catch-up time. OK, nobody has commented on this so far, so I'll write something. It probably comes as no surprise (since I've already written as such) that I think this is a good idea. I have no strong opinion about the length of the doc freeze, but hopefully some of the translators will give some input here. > The release notes are difficult, as the -src committers MFC until just > a couple days before. I suggest that we have a "best effort" relnotes > freeze. Basically, the relnotes maintainer will try to keep things > up-to-date so that updates during the last couple days are minimal. > Bruce already does this, but it would be important for his successor > to be as reliable. Thanks, Michael. I'm looking at the commits to RELENG_4 and RELENG_4_5 during the last release cycle. During the week before the final i386 builds (28 January), there were ten commits to the release notes (two of which had to be double-committed to the release branch), which were reflected in revisions 1.22.2.183 to 1.22.2.192 of new.sgml. In retrospect, many of these could easily have landed in the errata file, post-release. We might even be able to do a short, hard RELNOTESng freeze, but I want to know if this would be useful or not. Cheers, Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 18: 0:10 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A005737B417 for ; Thu, 28 Feb 2002 18:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g21203e92834; Thu, 28 Feb 2002 18:00:03 -0800 (PST) (envelope-from gnats) Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by hub.freebsd.org (Postfix) with ESMTP id 7DCAE37B405 for ; Thu, 28 Feb 2002 17:53:54 -0800 (PST) Received: from mortis.sighup.org (mortis.over-yonder.net [64.89.206.226]) by draco.over-yonder.net (Postfix) with ESMTP id 5C895FC2 for ; Thu, 28 Feb 2002 19:53:53 -0600 (CST) Received: by mortis.sighup.org (Postfix, from userid 100) id C36451F06; Thu, 28 Feb 2002 19:53:51 -0600 (CST) Message-Id: <20020301015351.C36451F06@mortis.sighup.org> Date: Thu, 28 Feb 2002 19:53:51 -0600 (CST) From: "Matthew D.Fuller" Reply-To: "Matthew D.Fuller" To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35436: PAO isn't very latest-and-greatest these days Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35436 >Category: docs >Synopsis: PAO isn't very latest-and-greatest these days >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 28 18:00:03 PST 2002 >Closed-Date: >Last-Modified: >Originator: Matthew D. Fuller >Release: FreeBSD 5.0-CURRENT i386 >Organization: >Environment: System: FreeBSD mortis.sighup.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Oct 31 00:17:52 CST 2001 fullermd@mortis.sighup.org:/usr/src/sys/i386/compile/MORTIS i386 >Description: PAO isn't exactly the latest-and-greatest in laptop support for the last major version or so... >How-To-Repeat: http://www.freebsd.org/support.html In the "Hardware" section right near the end. >Fix: (watch for whitespace) Index: support.sgml =================================================================== RCS file: /usr/cvs/www/en/support.sgml,v retrieving revision 1.252 diff -u -r1.252 support.sgml --- support.sgml 2002/02/23 06:02:26 1.252 +++ support.sgml 2002/03/01 01:50:21 @@ -898,11 +898,6 @@ href="ftp://rtfm.mit.edu/pub/usenet-by-hierarchy/comp/answers/pc-hardware-faq">pc-hardware-faq is a great reference for people building their own machines. -
  • Laptop users looking for PCCARD (aka PCMCIA) support not already - provided in the FreeBSD base distribution should see the PAO distribution page for - the latest and greatest experimental laptop support.
    • -
  • Intel Secrets -- What Intel Doesn't Want You To Know - lots of information about Intel chips.
    • >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 19:22: 6 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 7B98C37B417; Thu, 28 Feb 2002 19:21:56 -0800 (PST) Received: from hades.hell.gr (patr530-a135.otenet.gr [212.205.215.135]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g213Li78013059; Fri, 1 Mar 2002 05:21:44 +0200 (EET) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id g213LhP46180; Fri, 1 Mar 2002 05:21:43 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Fri, 1 Mar 2002 05:21:43 +0200 From: Giorgos Keramidas To: "Bruce A. Mah" Cc: Michael Lucas , freebsd-doc@freebsd.org Subject: Re: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) Message-ID: <20020301032142.GA46101@hades.hell.gr> References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200203010100.g2110e001512@bmah.dyndns.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2002-02-28 17:00, Bruce A. Mah wrote: > If memory serves me right, Michael Lucas wrote: > > > I propose an official one-week doc/en_US.ISO8859-1 freeze for > > everything except the release notes, to give translators a little bit > > of catch-up time. > > OK, nobody has commented on this so far, so I'll write something. It > probably comes as no surprise (since I've already written as such) that > I think this is a good idea. > > I have no strong opinion about the length of the doc freeze, but > hopefully some of the translators will give some input here. I haven't finished many parts of the doc/el_GR.ISO8859-7 tree and I'm only recently beginning to see people who are interested to actually contribute stuff. It is rather early to ask for a freeze in the English documentation, to let Greek translators catch up, since we are trying to come up with a somewhat up to date translation of the documents. This is not a bad idea, though. I've seen kuriyama-san's speedy updates to the Japanese tree, and eventually I want to bring the Greek translation to a similar state. Perhaps, other translators think of this as a good thing too? Having about a week of time to update the release notes before a release is cut seems a good idea, IMO. Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 19:40:49 2002 Delivered-To: freebsd-doc@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 92AEB37B400; Thu, 28 Feb 2002 19:40:46 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020301034046.TUWR1147.rwcrmhc52.attbi.com@bmah.dyndns.org>; Fri, 1 Mar 2002 03:40:46 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id g213eka03676; Thu, 28 Feb 2002 19:40:46 -0800 (PST) (envelope-from bmah) Message-Id: <200203010340.g213eka03676@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Giorgos Keramidas Cc: "Bruce A. Mah" , Michael Lucas , freebsd-doc@freebsd.org Subject: Re: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) In-reply-to: <20020301032142.GA46101@hades.hell.gr> References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> Comments: In-reply-to Giorgos Keramidas message dated "Fri, 01 Mar 2002 05:21:43 +0200." From: bmah@freebsd.org (Bruce A. Mah) Reply-To: bmah@freebsd.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Feb 2002 19:40:46 -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org If memory serves me right, Giorgos Keramidas wrote: > On 2002-02-28 17:00, Bruce A. Mah wrote: > > If memory serves me right, Michael Lucas wrote: > > > > > I propose an official one-week doc/en_US.ISO8859-1 freeze for > > > everything except the release notes, to give translators a little bit > > > of catch-up time. > > > > OK, nobody has commented on this so far, so I'll write something. It > > probably comes as no surprise (since I've already written as such) that > > I think this is a good idea. > > > > I have no strong opinion about the length of the doc freeze, but > > hopefully some of the translators will give some input here. > > I haven't finished many parts of the doc/el_GR.ISO8859-7 tree and I'm only > recently beginning to see people who are interested to actually contribute > stuff. It is rather early to ask for a freeze in the English documentation, > to let Greek translators catch up, since we are trying to come up with a > somewhat up to date translation of the documents. So...I was assuming that Michael's proposal was for a freeze before *each release*, not right this instant. Although I can see how one might have interpreted it either way. :-) Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 19:42:16 2002 Delivered-To: freebsd-doc@freebsd.org Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by hub.freebsd.org (Postfix) with ESMTP id 9B35C37B400; Thu, 28 Feb 2002 19:42:13 -0800 (PST) Received: from pittgoth.com (c2.depaul-inst.pittsburgh.pa.us [192.168.1.2]) by pittgoth.com (8.11.6/8.11.6) with ESMTP id g213iB938870; Thu, 28 Feb 2002 22:44:11 -0500 (EST) (envelope-from darklogik@pittgoth.com) Message-ID: <3C7EF912.30001@pittgoth.com> Date: Thu, 28 Feb 2002 22:44:18 -0500 From: Tom Rhodes User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2) Gecko/20010628 X-Accept-Language: en-us MIME-Version: 1.0 To: Giorgos Keramidas Cc: "Bruce A. Mah" , Michael Lucas , freebsd-doc@FreeBSD.ORG Subject: Re: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Giorgos Keramidas wrote: >On 2002-02-28 17:00, Bruce A. Mah wrote: > >>If memory serves me right, Michael Lucas wrote: >> Not sure if I ever made a comment on this thread or not. Here we go: I honestly feel the doc freeze will do no harm to anyone, but in fact be helpful to the translation teams, or even doc hackers working on a specific part of the documentation. Currently i'm working on a few parts of the doc project and I do not see how it would hurt my work in any way ;) You have my vote ;) -- Tom Rhodes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Thu Feb 28 23:49:56 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id D7F7D37B444; Thu, 28 Feb 2002 23:49:50 -0800 (PST) Received: from hades.hell.gr (patr530-a235.otenet.gr [212.205.215.235]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g217nf7A021079; Fri, 1 Mar 2002 09:49:44 +0200 (EET) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id g217hnQ47501; Fri, 1 Mar 2002 09:43:50 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Fri, 1 Mar 2002 09:43:49 +0200 From: Giorgos Keramidas To: "Bruce A. Mah" Cc: Michael Lucas , freebsd-doc@freebsd.org Subject: Re: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) Message-ID: <20020301074349.GB46101@hades.hell.gr> References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> <200203010340.g213eka03676@bmah.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200203010340.g213eka03676@bmah.dyndns.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2002-02-28 19:40, Bruce A. Mah wrote: > If memory serves me right, Giorgos Keramidas wrote: > > > > I haven't finished many parts of the doc/el_GR.ISO8859-7 tree and I'm only > > recently beginning to see people who are interested to actually contribute > > stuff. It is rather early to ask for a freeze in the English documentation, > > to let Greek translators catch up, since we are trying to come up with a > > somewhat up to date translation of the documents. > > So...I was assuming that Michael's proposal was for a freeze before > *each release*, not right this instant. Although I can see how one > might have interpreted it either way. :-) Err, actually, no. I probably didn't put my thoughts to words in the best manner possible. I meant to say that I like the idea of a 'doc freeze before the release', since it will give translators some time to catch up with the English versions of important documents. I would like to have at least the release notes and a first cut at the Handbook, translated by the time 4.6 hits the shelves, but when I say it's too early to ask for a freeze I meant that the Greek translation I'm pushing through it's first stages, doesn't have enough of the documentation translated to justify a freeze request. - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 0:23:11 2002 Delivered-To: freebsd-doc@freebsd.org Received: from zaphod.euronet.nl (zaphod.euronet.nl [194.134.128.241]) by hub.freebsd.org (Postfix) with ESMTP id 059C437B402 for ; Fri, 1 Mar 2002 00:23:09 -0800 (PST) Received: (from ernst@localhost) by zaphod.euronet.nl (8.11.6/8.11.6) id g218N8W35064 for doc@FreeBSD.org; Fri, 1 Mar 2002 09:23:08 +0100 (CET) (envelope-from ernst) Message-Id: <200203010823.g218N8W35064@zaphod.euronet.nl> Content-Type: text/plain; charset="iso-8859-1" From: Ernst de Haan To: doc@FreeBSD.org Subject: doc/en_US.ISO8859-1/books/porters-handbook/porting-pkgname.html Date: Fri, 1 Mar 2002 09:23:08 +0100 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-pkgname.html says: "The package name should look like [language[_region]]-name[[-]compiled.specifics]-version.numbers." This is wrong. It would mean that a package name starts with a minus sign if language is not specified. I think it should rather be: "The package name should look like [language[_region]-]name[[-]compiled.specifics]-version.numbers." And should the second minus sign be optional? Should not it be mandatory, as below? "The package name should look like [language[_region]-]name[-compiled.specifics]-version.numbers." Sincerely, Ernst -- Ernst de Haan EuroNet Internet B.V. "Come to me all who are weary and burdened and I will give you rest" -- Jesus Christ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 1:10:12 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 65A6B37B41A for ; Fri, 1 Mar 2002 01:09:56 -0800 (PST) Received: from hukins.hn.org ([62.253.80.147]) by mta01-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020301090953.DCEW9422.mta01-svc.ntlworld.com@hukins.hn.org> for ; Fri, 1 Mar 2002 09:09:53 +0000 Received: (qmail 87964 invoked by uid 1001); 1 Mar 2002 09:09:53 -0000 Date: Fri, 1 Mar 2002 09:09:53 +0000 From: Tom Hukins To: Tom Rhodes Cc: Giorgos Keramidas , "Bruce A. Mah" , Michael Lucas , freebsd-doc@FreeBSD.ORG Subject: Re: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) Message-ID: <20020301090953.A87015@eborcom.com> Mail-Followup-To: Tom Hukins , Tom Rhodes , Giorgos Keramidas , "Bruce A. Mah" , Michael Lucas , freebsd-doc@FreeBSD.ORG References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> <3C7EF912.30001@pittgoth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3C7EF912.30001@pittgoth.com>; from darklogik@pittgoth.com on Thu, Feb 28, 2002 at 10:44:18PM -0500 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Feb 28, 2002 at 10:44:18PM -0500, Tom Rhodes wrote: > > I honestly feel the doc freeze will do no harm to anyone, but in fact be > helpful to the translation teams, or even doc hackers working on a > specific part of the documentation. This is a good point: a doc freeze is also beneficial to people who aren't translators. When we freeze src, release candidates are distributed for testing to reduce the number of bugs in the final release. As the docs and Web site are built nightly, a brief freeze will allow people to look for technical and linguistic errors. Just as important changes are committed with src when it's frozen, we could do the same with doc, perhaps with a small group of people who can approve these changes performing the same role as the release engineers do for src. This will reduce the likelihood of serious problems creeping into doc before a release is created. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 2:12:30 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mailhost2.dircon.co.uk (mailhost2.dircon.co.uk [194.112.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 36E5137B417 for ; Fri, 1 Mar 2002 02:12:28 -0800 (PST) Received: from mail.blackmans.org (unknown [195.157.223.19]) by mailhost2.dircon.co.uk (Postfix) with ESMTP id C897362FEA for ; Fri, 1 Mar 2002 10:12:26 +0000 (GMT) Received: from blackmans.org (localhost [127.0.0.1]) by mail.blackmans.org (Postfix) with ESMTP id 37A4A17C6 for ; Fri, 1 Mar 2002 10:12:26 +0000 (GMT) From: "Mark Blackman" To: freebsd-doc@FreeBSD.ORG Subject: PR docs/32041 Date: Fri, 01 Mar 2002 10:12:26 +0000 Message-Id: <20020301101226.37A4A17C6@mail.blackmans.org> Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Just a quick reminder. Could someone quickly review PR docs/32041 and either commit it or reject it, please? Should be an easy one. Submitted back in Nov. 2001. Its just an extra paragraph for tuning(7). Cheers, Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 4:24: 7 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 0AEAF37B41C; Fri, 1 Mar 2002 04:24:03 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g21CO2d75211; Fri, 1 Mar 2002 07:24:02 -0500 (EST) (envelope-from mwlucas) Date: Fri, 1 Mar 2002 07:24:02 -0500 From: Michael Lucas To: "Bruce A. Mah" Cc: Giorgos Keramidas , freebsd-doc@freebsd.org Subject: Re: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) Message-ID: <20020301072402.A75158@blackhelicopters.org> References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> <200203010340.g213eka03676@bmah.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200203010340.g213eka03676@bmah.dyndns.org>; from bmah@freebsd.org on Thu, Feb 28, 2002 at 07:40:46PM -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Feb 28, 2002 at 07:40:46PM -0800, Bruce A. Mah wrote: > So...I was assuming that Michael's proposal was for a freeze before > *each release*, not right this instant. Although I can see how one > might have interpreted it either way. :-) See the dangers of writing so you can be misunderstood? :-) To summarize: We have consensus on the desirability of a -doc freeze. Excellent. We need to determine an appropriate length of time for the freeze. While a week sounds good to some, we could really use buy-in from the Japanese translation team. I'll write directly to Hiroki and ask him what he thinks. Personally, I don't really like the idea of a hard relnotes freeze. But I don't maintain the relnotes, have never maintained the relnotes, and probably never will maintain the relnotes, so I'll just utter my wish for relnotes flexibility and let it die in silence, unmourned and unloved by those it cares for. ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 4:30:16 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 3DDE537B400; Fri, 1 Mar 2002 04:30:13 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g21CUCx75241; Fri, 1 Mar 2002 07:30:12 -0500 (EST) (envelope-from mwlucas) Date: Fri, 1 Mar 2002 07:30:12 -0500 From: Michael Lucas To: hrs@FreeBSD.org Cc: doc@FreeBSD.org Subject: request input from Japanese translators, Message-ID: <20020301073012.B75158@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, We are discussing a pre-release -doc freeze to aid the translation teams, and would appreciate your opinions. This is still in the initial stages, and we are still working out the details. Our current idea is that the main -doc tree would be frozen for a week before a release. The release notes would enter a "soft freeze" during that time. Only vital updates would be entered. Because the main source tree can be updated during this time, we have difficulty freezing the release notes. Whenever possible, however, updates would go into the post-release errata rather than the main release notes. Would this be helpful to you? Is a week long enough? Thank you for any advice, Michael -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 4:40: 8 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7FC2C37B41A for ; Fri, 1 Mar 2002 04:40:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g21Ce3k33797; Fri, 1 Mar 2002 04:40:03 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Mar 2002 04:40:03 -0800 (PST) Message-Id: <200203011240.g21Ce3k33797@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Michael Lucas Subject: Re: docs/35436: PAO isn't very latest-and-greatest these days Reply-To: Michael Lucas Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35436; it has been noted by GNATS. From: Michael Lucas To: "Matthew D.Fuller" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: docs/35436: PAO isn't very latest-and-greatest these days Date: Fri, 1 Mar 2002 07:33:15 -0500 Hello, (This is aimed more at -doc than the submitter.) The FAQ covers older versions of FreeBSD... should the website? If so, we should add version-specific info here. If not, this looks good to me. (to the submitter) Good catch, thanks! -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 6:39:39 2002 Delivered-To: freebsd-doc@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id A649937B41C for ; Fri, 1 Mar 2002 06:39:36 -0800 (PST) Received: from max ([12.254.136.195]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020301143936.CPB2626.rwcrmhc51.attbi.com@max> for ; Fri, 1 Mar 2002 14:39:36 +0000 Message-ID: <018501c1c12f$2e65ed20$0900a8c0@max> From: "John Nielsen" To: Subject: Fw: docs/35291: of/or typo in nge(4) manpage Date: Fri, 1 Mar 2002 07:41:32 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I don't know how often PR's get looked at if no one hollers about them, so here's a holler. Spend 30 seconds fixing the typo and have a great sense of accomplishment the rest of the day! :) JN ----- Original Message ----- From: To: "John Nielsen" Sent: Sunday, February 24, 2002 6:30 PM Subject: Re: docs/35291: of/or typo in nge(4) manpage > Thank you very much for your problem report. > It has the internal identification `docs/35291'. > The individual assigned to look at your > report is: freebsd-doc. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=35291 > > >Category: docs > >Responsible: freebsd-doc > >Synopsis: of/or typo in nge(4) manpage > >Arrival-Date: Sun Feb 24 17:30:01 PST 2002 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 8:10:11 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 098A137B402 for ; Fri, 1 Mar 2002 08:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g21GA3c93435; Fri, 1 Mar 2002 08:10:03 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Mar 2002 08:10:03 -0800 (PST) Message-Id: <200203011610.g21GA3c93435@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Tom Rhodes Subject: Re: docs/35378: Handbook has inaccurate description of freebsd-security list Reply-To: Tom Rhodes Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35378; it has been noted by GNATS. From: Tom Rhodes To: Bob Johnson Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: docs/35378: Handbook has inaccurate description of freebsd-security list Date: Fri, 01 Mar 2002 11:15:53 -0500 Bob Johnson wrote: >> > Handbook description of freebsd-security mailing list is "Security issues". > Mailing list is flooded with questions about how to use ssh, how > to log in, how to configure IPFW, etc. Problem is multiplied by > three responses telling them they should have posted their question > on freebsd-questions. Indeed the Handbook does not cover the use and configuration of ipfw(8) as it should. I have already started writing a section for the use and configuration of ipfw(8). As for ssh(1), we have a nice section that has been written by Chern Lee in the security section of the handbook, so it need not be touched unless a large update is needed. -- Tom (Darklogik) Rhodes www.Pittgoth.com Gothic Liberation Front www.FreeBSD.org The Power To Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 8:11:11 2002 Delivered-To: freebsd-doc@freebsd.org Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id D99CC37B402 for ; Fri, 1 Mar 2002 08:10:59 -0800 (PST) Received: from pc4-card4-0-cust162.cdf.cable.ntl.com ([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16gpcY-0001y6-00 for doc@freebsd.org; Fri, 01 Mar 2002 16:10:58 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.35 #1) id 16gpcL-000BSb-00 for doc@FreeBSD.org; Fri, 01 Mar 2002 16:10:45 +0000 Date: Fri, 1 Mar 2002 16:10:45 +0000 From: Ceri To: doc@FreeBSD.org Subject: The FAQ and IndexTerm Message-ID: <20020301161045.GA43649@submonkey.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org All, As promised, today is the day when I start work on adding IndexTerm elements to the FAQ (although a close friend has suffered a bereavement, so I probably cannot actually add any today; but I can at least kick off this discussion). According to http://www.docbook.org/tdg/en/html/indexterm.html, the indexterm element is not valid within tags, which as I understand (and I could be very wrong) leaves me with the only way of doing this to be adding IndexTerm ranges as described on the same page. Which there are two ways of doing: 1) Use the StartOfRange class attribute, and produce stuff which looks like this : __start first_way.diff --- book.sgml.old Fri Mar 1 15:29:03 2002 +++ book.sgml Fri Mar 1 15:44:32 2002 @@ -577,6 +577,9 @@ + + further information + What other sources of information are there? @@ -590,6 +593,8 @@ site. + + __end first_way.diff Now this is a bit horrible. It's hard to do, it's hard to maintain, and I think it's ugly. Which brings us to the second way : 2) Use the Zone attribute, which produces stuff like this : __start second_way.diff --- book.sgml.old Fri Mar 1 15:29:03 2002 +++ book.sgml Fri Mar 1 15:31:09 2002 @@ -12334,4 +12334,8 @@ &bibliography; + + + further information + __end second_way.diff I hope you'll agree this is much nicer, and easier to maintain. The URL above mentions that when done in this way, the IndexTerm elements can quite happily live in another file, which make it even nicer, as if this could be done then I could happily knock that file together and not have to worry about anyone making major changes to the FAQ and upsetting my patchset. Also, it would make it more easily maintainable. Presumably there needs to be some magic somewhere to make this work though, and I don't know how to do that - is it as simple as adding SRCS+= index.sgml to the Makefile and doing something similar to the Handbook's book.sgml ? (At this point I am querying my usage of the word "simple" there...) So I would like some input on which way people would prefer to see this done, and also on how I make the second one happen (I'm very confident it will turn out to be the preferred solution). Thank you for your attention, Ceri -- keep a mild groove on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 9:32:38 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 928E837B41B; Fri, 1 Mar 2002 09:32:36 -0800 (PST) Received: (from bmah@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g21HVT410452; Fri, 1 Mar 2002 09:31:29 -0800 (PST) (envelope-from bmah) Date: Fri, 1 Mar 2002 09:31:29 -0800 (PST) From: Message-Id: <200203011731.g21HVT410452@freefall.freebsd.org> To: zoobie@bsdconspiracy.net, bmah@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35291: of/or typo in nge(4) manpage Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: of/or typo in nge(4) manpage State-Changed-From-To: open->closed State-Changed-By: bmah State-Changed-When: Fri Mar 1 09:31:16 PST 2002 State-Changed-Why: Committed to HEAD and RELENG_4, thanks! http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35291 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 9:33:56 2002 Delivered-To: freebsd-doc@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id A51D137B402 for ; Fri, 1 Mar 2002 09:33:53 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020301173353.IONE1147.rwcrmhc52.attbi.com@bmah.dyndns.org>; Fri, 1 Mar 2002 17:33:53 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id g21HXrG11716; Fri, 1 Mar 2002 09:33:53 -0800 (PST) (envelope-from bmah) Message-Id: <200203011733.g21HXrG11716@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "John Nielsen" Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Fw: docs/35291: of/or typo in nge(4) manpage In-reply-to: <018501c1c12f$2e65ed20$0900a8c0@max> References: <018501c1c12f$2e65ed20$0900a8c0@max> Comments: In-reply-to "John Nielsen" message dated "Fri, 01 Mar 2002 07:41:32 -0700." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Mar 2002 09:33:53 -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org If memory serves me right, "John Nielsen" wrote: > I don't know how often PR's get looked at if no one hollers about them, so > here's a holler. Spend 30 seconds fixing the typo and have a great sense > of accomplishment the rest of the day! :) Committed, thanks! I feel like I've accomplished something, but I'd rather have the great sense of accomplishment that would come from configuring this Cisco box I'm working on. :-) Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 15:52:38 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2A0CF37B41A; Fri, 1 Mar 2002 15:52:37 -0800 (PST) Received: (from bmah@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g21No3i23365; Fri, 1 Mar 2002 15:50:03 -0800 (PST) (envelope-from bmah) Date: Fri, 1 Mar 2002 15:50:03 -0800 (PST) From: Message-Id: <200203012350.g21No3i23365@freefall.freebsd.org> To: gioria@freebsd.org, bmah@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35115: src/release/doc/en_US.ISO8859-1/installation/common/install.sgml be consistent with the differents docs files Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: src/release/doc/en_US.ISO8859-1/installation/common/install.sgml be consistent with the differents docs files State-Changed-From-To: open->closed State-Changed-By: bmah State-Changed-When: Fri Mar 1 15:49:29 PST 2002 State-Changed-Why: Committed the applicable parts of this patch to -CURRENT and 4-STABLE. Thanks! http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35115 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 21: 3:35 2002 Delivered-To: freebsd-doc@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id A643637B405 for ; Fri, 1 Mar 2002 21:03:31 -0800 (PST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by white.imgsrc.co.jp (Postfix) with ESMTP id 90E3224D3B for ; Sat, 2 Mar 2002 14:03:30 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [2001:218:422:2::160]) by black.imgsrc.co.jp (Postfix) with ESMTP id 14D2E1E4651 for ; Sat, 2 Mar 2002 14:03:29 +0900 (JST) Date: Sat, 02 Mar 2002 14:03:30 +0900 Message-ID: <7mofi7h87x.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: doc@FreeBSD.org Subject: Re: request input from Japanese translators, In-Reply-To: <20020301073012.B75158@blackhelicopters.org> References: <20020301073012.B75158@blackhelicopters.org> User-Agent: Wanderlust/2.9.6 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Yes, hrs is gathering feedbacks in Japanese mailing list about this issue. At Fri, 1 Mar 2002 12:30:16 +0000 (UTC), Michael Lucas wrote: > Our current idea is that the main -doc tree would be frozen for a week > before a release. > > The release notes would enter a "soft freeze" during that time. Only > vital updates would be entered. Because the main source tree can be > updated during this time, we have difficulty freezing the release > notes. Whenever possible, however, updates would go into the > post-release errata rather than the main release notes. > > Would this be helpful to you? Is a week long enough? IMHO, that's enough for me. Honestly, I cannot say that's really enough because my spare time for FreeBSD is heavily depends on my real job. If I have much free time in freeze days (less real job), only one day freeze is enough for me. But I don't know future. :-) -- Jun Kuriyama // IMG SRC, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Fri Mar 1 22:52:39 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DB17337B402; Fri, 1 Mar 2002 22:52:37 -0800 (PST) Received: (from bmah@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g226pch04906; Fri, 1 Mar 2002 22:51:38 -0800 (PST) (envelope-from bmah) Date: Fri, 1 Mar 2002 22:51:38 -0800 (PST) From: Message-Id: <200203020651.g226pch04906@freefall.freebsd.org> To: priit@bsd.ee, bmah@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [PATCH] Misc corrections to the Handbook, chapter 2 State-Changed-From-To: open->closed State-Changed-By: bmah State-Changed-When: Fri Mar 1 22:50:37 PST 2002 State-Changed-Why: Committed with a couple of modifications (I substituted more appropriate tags in two places where you used )...see chapter.sgml 1.141->1.142 for the details. Thanks! http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35155 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 0:38:34 2002 Delivered-To: freebsd-doc@freebsd.org Received: from eos.ocn.ne.jp (eos.ocn.ne.jp [210.190.142.171]) by hub.freebsd.org (Postfix) with ESMTP id 5DD3737B400; Sat, 2 Mar 2002 00:38:30 -0800 (PST) Received: from mail.hrslab.yi.org (p0775-ip01funabasi.chiba.ocn.ne.jp [61.119.148.13]) by eos.ocn.ne.jp (OCN) with ESMTP id RAA15483; Sat, 2 Mar 2002 17:38:27 +0900 (JST) Received: from localhost (alph.hrslab.yi.org [192.168.0.10]) by mail.hrslab.yi.org (8.9.3/3.7W/DomainMaster) with ESMTP id RAA32950; Sat, 2 Mar 2002 17:37:35 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sat, 02 Mar 2002 16:44:31 +0900 (JST) Message-Id: <20020302.164431.112548966.hrs@eos.ocn.ne.jp> To: mwlucas@FreeBSD.ORG Cc: doc@FreeBSD.ORG Subject: Re: request input from Japanese translators, From: Hiroki Sato In-Reply-To: <20020301073012.B75158@blackhelicopters.org> References: <20020301073012.B75158@blackhelicopters.org> X-Mailer: Mew version 2.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Michael Lucas wrote in <20020301073012.B75158@blackhelicopters.org>: mwlucas> Our current idea is that the main -doc tree would be frozen for a week mwlucas> before a release. I also think one week before a release is reasonable. Personally, three days are enough for me and more than one week is too long, but as Kuriyama-san said, it depends on how long time we can spend on the work around the release point. Perhaps for translation teams, the fact that English documents would be frozen at a certain point of time is important. However, although Japanese team is not using our own CVS tree for the work now, some other teams using their own CVS tree may need additional time to synchronize each other. I think one week long can be common ground in either case, and at least there is no objection to this idea in Japanese mailing-list. mwlucas> The release notes would enter a "soft freeze" during that time. Only mwlucas> vital updates would be entered. Because the main source tree can be mwlucas> updated during this time, we have difficulty freezing the release mwlucas> notes. Whenever possible, however, updates would go into the mwlucas> post-release errata rather than the main release notes. Yes, I agree with your idea if the exceptional changes are informed the translation teams well. -- | Hiroki Sato | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 2:26:39 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail.ruhr.de (in-ruhr4.ruhr.de [212.23.134.2]) by hub.freebsd.org (Postfix) with SMTP id E7D2637B405 for ; Sat, 2 Mar 2002 02:26:35 -0800 (PST) Received: (qmail 12525 invoked by uid 10); 2 Mar 2002 10:26:34 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.11.6/8.11.2) id g22AQtx77726 for freebsd-doc@FreeBSD.ORG; Sat, 2 Mar 2002 11:26:55 +0100 (CET) (envelope-from ue) Date: Sat, 2 Mar 2002 11:26:55 +0100 From: Udo Erdelhoff To: freebsd-doc@FreeBSD.ORG Subject: Using seperate CVS trees for translations (Re: request input from Japanese translators,) Message-ID: <20020302112655.R56195@nathan.ruhr.de> Mail-Followup-To: freebsd-doc@FreeBSD.ORG References: <20020301073012.B75158@blackhelicopters.org> <20020302.164431.112548966.hrs@eos.ocn.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020302.164431.112548966.hrs@eos.ocn.ne.jp> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, On Sat, Mar 02, 2002 at 04:44:31PM +0900, Hiroki Sato wrote: > However, although Japanese team is not using our own CVS tree > for the work now, some other teams using their own CVS tree > may need additional time to synchronize each other. we are using our own CVS tree to organize the German translation and I do not think that this will slow us down. Basically, everybody commits his changes to the local repo, one guy checks it out on his own systems, does a test build, and commits everything to freefall. There is an extra step in there, but the fact that the translators do not have to worry about testing the complete build process saves them a lot of time, which shortens the overall process. /s/Udo -- Windows is not the answer, Windows is the question. No is the answer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 2:26:40 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail.ruhr.de (in-ruhr4.ruhr.de [212.23.134.2]) by hub.freebsd.org (Postfix) with SMTP id D00D437B402 for ; Sat, 2 Mar 2002 02:26:35 -0800 (PST) Received: (qmail 12519 invoked by uid 10); 2 Mar 2002 10:26:34 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.11.6/8.11.2) id g22AK6077692 for freebsd-doc@FreeBSD.ORG; Sat, 2 Mar 2002 11:20:06 +0100 (CET) (envelope-from ue) Date: Sat, 2 Mar 2002 11:20:06 +0100 From: Udo Erdelhoff To: freebsd-doc@FreeBSD.ORG Subject: Re: Official -doc freeze proposal Message-ID: <20020302112006.Q56195@nathan.ruhr.de> Mail-Followup-To: freebsd-doc@FreeBSD.ORG References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> <3C7EF912.30001@pittgoth.com> <20020301090953.A87015@eborcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020301090953.A87015@eborcom.com> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [trimmed cc: list and subject] Tom, On Fri, Mar 01, 2002 at 09:09:53AM +0000, Tom Hukins wrote: > This will reduce the likelihood of serious problems creeping into doc > before a release is created. I have had mixed feelings about the freeze before but this a very important point. I do remember some rather frustrated mails from Jordan when problems with the documentation broke the release building process again and again. So, basically, here's another vote for a 'hard' freeze of the documentation. I just want to add a vote of caution: Even in the hard freeze, it should still be possible to fix typos and similar stuff in the english documentation... /s/Udo -- > FreeBSD recently made 'flex' its default implementation of 'lex'. For geological values of ``recently''. Archie Cobbs and Garett Wollmann on cvs-all@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 4:17:41 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 9F52637B416 for ; Sat, 2 Mar 2002 04:17:37 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g22CHY382154; Sat, 2 Mar 2002 07:17:34 -0500 (EST) (envelope-from mwlucas) Date: Sat, 2 Mar 2002 07:17:34 -0500 From: Michael Lucas To: Udo Erdelhoff Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Official -doc freeze proposal Message-ID: <20020302071734.A82120@blackhelicopters.org> References: <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> <3C7EF912.30001@pittgoth.com> <20020301090953.A87015@eborcom.com> <20020302112006.Q56195@nathan.ruhr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020302112006.Q56195@nathan.ruhr.de>; from ue@nathan.ruhr.de on Sat, Mar 02, 2002 at 11:20:06AM +0100 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Mar 02, 2002 at 11:20:06AM +0100, Udo Erdelhoff wrote: > [trimmed cc: list and subject] > > I have had mixed feelings about the freeze before but this a very > important point. I do remember some rather frustrated mails from > Jordan when problems with the documentation broke the release > building process again and again. > Well, it does help that we have a -doc member who is part of the releng team. If we break it, Bruce will fix it. Lucky Bruce. :-) > So, basically, here's another vote for a 'hard' freeze of the > documentation. I just want to add a vote of caution: Even in > the hard freeze, it should still be possible to fix typos and > similar stuff in the english documentation... Good point. The release engineers allow certain changes during code freeze. Do we want to allow changes during -doc freeze? Here's my opinion: My gut reaction is that a freeze is a freeze, and that we should freeze for anything not blatantly, obviously wrong. We're not really debugging, we're giving translators time to catch up. While I intend to follow this rule, I suspect other -doc people will have other ideas. So, howe about: Changes that do not directly affect the translation teams should be allowed. This basically means typos. We should directly notify the translation teams of these changes. Breaking the -doc build should be a definite no-no during this time, and anything that causes a break or breaks "make release" should be immediately backed out or fixed. How does that sound? (Sorry to be pedantic here: we're seeing what a lack of ground rules is doing to other parts of the Project at the moment. I don't want -doc to have those sorts of issues. Nik is a nice relaxed team lead, and if we can agree on these things ourselves he won't start to hate us all come release time. :-) ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 4:29: 7 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blueyonder.co.uk (pcow057o.blueyonder.co.uk [195.188.53.94]) by hub.freebsd.org (Postfix) with ESMTP id 949BF37B400 for ; Sat, 2 Mar 2002 04:29:05 -0800 (PST) Received: from pcow057o.blueyonder.co.uk ([127.0.0.1]) by blueyonder.co.uk with Microsoft SMTPSVC(5.5.1877.757.75); Sat, 2 Mar 2002 12:29:04 +0000 Received: from fluoxetine.lan (unverified [62.31.193.116]) by pcow057o.blueyonder.co.uk (Content Technologies SMTPRS 4.2.9) with ESMTP id ; Sat, 2 Mar 2002 12:29:04 +0000 Date: Sat, 2 Mar 2002 12:29:17 +0000 (GMT) From: Andrew McKay X-X-Sender: andy@fluoxetine.lan To: FreeBSD Doc List Cc: Michael Lucas Subject: Re: Official -doc freeze proposal In-Reply-To: <20020302071734.A82120@blackhelicopters.org> Message-ID: <20020302122715.T37068-100000@fluoxetine.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 2 Mar 2002, Michael Lucas wrote: ML> Breaking the -doc build should be a definite no-no during this time, ML> and anything that causes a break or breaks "make release" should be ML> immediately backed out or fixed. Pardon my naivety but shouldn't breaking the -doc build be a definite no-no at all times? :) Andy -- Andrew McKay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 4:56:38 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail.ruhr.de (in-ruhr4.ruhr.de [212.23.134.2]) by hub.freebsd.org (Postfix) with SMTP id E4CAE37B405 for ; Sat, 2 Mar 2002 04:56:35 -0800 (PST) Received: (qmail 18569 invoked by uid 10); 2 Mar 2002 12:56:33 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.11.6/8.11.2) id g22CvXo78150 for freebsd-doc@freebsd.org; Sat, 2 Mar 2002 13:57:33 +0100 (CET) (envelope-from ue) Date: Sat, 2 Mar 2002 13:57:32 +0100 From: Udo Erdelhoff To: FreeBSD Doc List Subject: Re: Official -doc freeze proposal Message-ID: <20020302135732.S56195@nathan.ruhr.de> Mail-Followup-To: FreeBSD Doc List References: <20020302071734.A82120@blackhelicopters.org> <20020302122715.T37068-100000@fluoxetine.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020302122715.T37068-100000@fluoxetine.lan> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Mar 02, 2002 at 12:29:17PM +0000, Andrew McKay wrote: > Pardon my naivety but shouldn't breaking the -doc build be a definite > no-no at all times? :) Reckless actions are frowned upon all the time, bold actions are frowned upon only during the freeze. If this doesn't make sense to you, you should read some more Clausewitz. /s/Udo -- > FreeBSD recently made 'flex' its default implementation of 'lex'. For geological values of ``recently''. Archie Cobbs and Garett Wollmann on cvs-all@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 5:41:16 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 5CB0A37B400 for ; Sat, 2 Mar 2002 05:41:13 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g22DfA082337; Sat, 2 Mar 2002 08:41:10 -0500 (EST) (envelope-from mwlucas) Date: Sat, 2 Mar 2002 08:41:10 -0500 From: Michael Lucas To: Andrew McKay Cc: FreeBSD Doc List Subject: Re: Official -doc freeze proposal Message-ID: <20020302084110.A82314@blackhelicopters.org> References: <20020302071734.A82120@blackhelicopters.org> <20020302122715.T37068-100000@fluoxetine.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020302122715.T37068-100000@fluoxetine.lan>; from andy@openirc.co.uk on Sat, Mar 02, 2002 at 12:29:17PM +0000 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Mar 02, 2002 at 12:29:17PM +0000, Andrew McKay wrote: > On Sat, 2 Mar 2002, Michael Lucas wrote: > > ML> Breaking the -doc build should be a definite no-no during this time, > ML> and anything that causes a break or breaks "make release" should be > ML> immediately backed out or fixed. > > Pardon my naivety but shouldn't breaking the -doc build be a definite > no-no at all times? :) Well, it's less bad than over on -stable. :-) Having -doc broken for a day or two, so that the breaker can fix the damage, isn't that big a deal. A -src committer recently broke the tree by importing new PGP key handling scripts, for example. We waited for that developer to clean up after himself rather than fixing it ourselves. At times we've lived with -doc breakage for considerable time. For example, we had a time where one article simply refused to build on freefall. It built everywhere else, just not on the main FreeBSD web server where everybody goes to look for docs. We lived with this for some time while things were being debugged. It was no big hairy deal. This is one of the nice things about the doc proj; we're much mellower than the -src people. During freeze, however, I think we need to enforce a little more discipline than we traditionally do. ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 6:18:49 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 27F7037B419 for ; Sat, 2 Mar 2002 06:18:45 -0800 (PST) Received: from hukins.hn.org ([62.253.89.204]) by mta02-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020302141843.KHMZ8848.mta02-svc.ntlworld.com@hukins.hn.org> for ; Sat, 2 Mar 2002 14:18:43 +0000 Received: (qmail 98282 invoked by uid 1001); 2 Mar 2002 14:18:14 -0000 Date: Sat, 2 Mar 2002 14:18:14 +0000 From: Tom Hukins To: Michael Lucas Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Official -doc freeze proposal Message-ID: <20020302141814.A98115@eborcom.com> Mail-Followup-To: Tom Hukins , Michael Lucas , freebsd-doc@FreeBSD.ORG References: <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> <3C7EF912.30001@pittgoth.com> <20020301090953.A87015@eborcom.com> <20020302112006.Q56195@nathan.ruhr.de> <20020302071734.A82120@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020302071734.A82120@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Sat, Mar 02, 2002 at 07:17:34AM -0500 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Mar 02, 2002 at 07:17:34AM -0500, Michael Lucas wrote: > > My gut reaction is that a freeze is a freeze, and that we should > freeze for anything not blatantly, obviously wrong. Yes, this is the point I tried to make yesterday, but your description is more succinct. > Changes that do not directly affect the translation teams should be > allowed. This basically means typos. We should directly notify the > translation teams of these changes. I also think this is a good idea, but it should be clear how to "directly notify translation teams". This should be done in a way that both -doc committers and translation teams are happy with. > (Sorry to be pedantic here: we're seeing what a lack of ground rules > is doing to other parts of the Project at the moment. I don't want > -doc to have those sorts of issues. Nik is a nice relaxed team lead, > and if we can agree on these things ourselves he won't start to hate > us all come release time. :-) I'm sure there will be some teething problems with the first -doc freeze, but we'll learn from them. Your "directly notify translation teams" comment is one example of a procedure that different people will interpret differently. Hopefully nobody will get too upset as we figure out the best way implement a freeze. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 8:51: 4 2002 Delivered-To: freebsd-doc@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 5D6BD37B419 for ; Sat, 2 Mar 2002 08:50:58 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020302165053.KJNX1147.rwcrmhc52.attbi.com@bmah.dyndns.org>; Sat, 2 Mar 2002 16:50:53 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id g22Goq946750; Sat, 2 Mar 2002 08:50:52 -0800 (PST) (envelope-from bmah) Message-Id: <200203021650.g22Goq946750@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Michael Lucas Cc: Udo Erdelhoff , freebsd-doc@FreeBSD.ORG Subject: Re: Official -doc freeze proposal In-reply-to: <20020302071734.A82120@blackhelicopters.org> References: <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> <3C7EF912.30001@pittgoth.com> <20020301090953.A87015@eborcom.com> <20020302112006.Q56195@nathan.ruhr.de> <20020302071734.A82120@blackhelicopters.org> Comments: In-reply-to Michael Lucas message dated "Sat, 02 Mar 2002 07:17:34 -0500." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Mar 2002 08:50:52 -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org If memory serves me right, Michael Lucas wrote: > On Sat, Mar 02, 2002 at 11:20:06AM +0100, Udo Erdelhoff wrote: > > [trimmed cc: list and subject] > > > > I have had mixed feelings about the freeze before but this a very > > important point. I do remember some rather frustrated mails from > > Jordan when problems with the documentation broke the release > > building process again and again. > > > > Well, it does help that we have a -doc member who is part of the > releng team. If we break it, Bruce will fix it. Lucky Bruce. :-) Heh. murray still wears a -doc hat too, and rumor has it that jhb was a -doc person before he got seduced by the src/ side. :-) > Changes that do not directly affect the translation teams should be > allowed. This basically means typos. We should directly notify the > translation teams of these changes. Fixing residual build breakage should also be allowed. Three other points: 1. For src/, the re team approves commits during a freeze. But for doc/ we allow much less change, and we're a small enough group that we can basically trust each other to Do The Right Thing (TM). 2. Note that the doc/ freeze ends when the doc/ tree is tagged, and the release notes "soft freeze" (== slush) ends when src/ is tagged. The doc/ tagging usually doesn't slip, and happens a few days before the src/ tagging, which may have slippage of days to a week. So we can determine the doc/ freeze date from the release schedule, and the release documentation person can call the release notes slush based on the general state of the world. 3. Unbeknownst to some of you we've got a developer preview of 5.0 coming up. Its working name is "5.0-DP1", and it is tentatively scheduled to be cut around in late March or early April. I intend to implement the release notes slush for 5.0-DP1. This might also be a chance to try a "test run" of the doc/ freeze concept in a low pressure environment (i.e. not a "real" release, so mistakes won't hurt too much). Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 12:25:39 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 5376B37B402 for ; Sat, 2 Mar 2002 12:25:14 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g22KP8r83194; Sat, 2 Mar 2002 15:25:08 -0500 (EST) (envelope-from mwlucas) Date: Sat, 2 Mar 2002 15:25:07 -0500 From: Michael Lucas To: Tom Rhodes Cc: freebsd-doc@FreeBSD.ORG Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Message-ID: <20020302152507.A83170@blackhelicopters.org> References: <200202262110.g1QLA2f07435@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202262110.g1QLA2f07435@freefall.freebsd.org>; from darklogik@pittgoth.com on Tue, Feb 26, 2002 at 01:10:02PM -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Okay, I think I'm done ripping on this poor guys work. Anything left for me to say is purely stylistic. Anyone else care to comment? On Tue, Feb 26, 2002 at 01:10:02PM -0800, Tom Rhodes wrote: > The following reply was made to PR docs/35098; it has been noted by GNATS. > > From: Tom Rhodes > To: FreeBSD-gnats-submit@FreeBSD.org > Cc: > Subject: Re: docs/35098: [PATCH] Handbook NFS stuff > Date: Tue, 26 Feb 2002 16:10:17 -0500 (EST) > > Try this one now ;) Clean up of whitespace, and other little "picks" > > -- > Tom Rhodes > > diff -ru handbook.old/advanced-networking/chapter.sgml handbook/advanced-networking/chapter.sgml > --- handbook.old/advanced-networking/chapter.sgml Fri Feb 22 16:16:17 2002 > +++ handbook/advanced-networking/chapter.sgml Tue Feb 26 15:45:36 2002 > @@ -648,6 +648,13 @@ > > > > + Tom > + Rhodes > + Reorganized and enhanced by > + > + > + > + > Bill > Swingle > Written by > @@ -658,44 +665,41 @@ > > NFS > Among the many different file systems that FreeBSD supports is > - the Network File System or NFS. NFS allows you > - to share directories and files on one machine with others > - via the network they are attached to. Using NFS, users and > - programs can access files on remote systems as if they were local > + the Network File System, also known as NFS. > + NFS allows a system to share directories and files > + with others over a network. By using NFS, users and > + programs can access files on remote systems almost as if they were local > files. > > - NFS has several benefits: > + Some of the most notable benefits that NFS can provide are: > > > > - Local workstations do not need as much disk space because > + Local workstations use less disk space because > commonly used data can be stored on a single machine and still > - remain accessible to everyone on the network. > + remain accessible to others over the network. > > > > There is no need for users to have unique home directories > - on every machine on your network. Once they have an established > - directory that is available via NFS it can be accessed from > - anywhere. > + on every network machine. Home directories could be setup on the > + NFS server and made available throughout the network. > > > > - Storage devices such as floppies and CDROM drives can be > - used by other machines on the network eliminating the need for > - extra hardware. > + Storage devices such as floppy disks, CDROM drives, and ZIP drives > + can be used by other machines on the network. This may reduce the number > + of removable media drives. > > > > > - How It Works > + How <acronym>NFS</acronym> Works > > - NFS is composed of two sides – a client side and a > - server side. Think of it as a want/have relationship. The client > - wants the data that the server side > - has. The server shares its data with the > - client. In order for this system to function properly a few > - processes have to be configured and running. > + NFS consists of at least two main parts: a server > + and at least one client. The client remotely accesses the data that is stored > + on the server machine. In order for this to function properly a few > + processes have to be configured and running: > > The server has to be running the following daemons: > > @@ -723,141 +727,129 @@ > > > nfsd > - The NFS Daemon which services requests from NFS > - clients. > + The NFS daemon which services requests from > + the NFS clients. > > > mountd > - The NFS Mount Daemon which actually carries out > - requests that &man.nfsd.8; passes on to it. > + The NFS mount daemon which carries out > + the requests that &man.nfsd.8; passes on to it. > > > portmap > - The portmapper daemon which > - allows NFS clients to find out which port the NFS server > - is using. > + The portmapper daemon > + allows NFS clients to discover which port the NFS server > + is using. > > > > > > - The client side only needs to run a single daemon: > - > - NFS > - client > - > - > - nfsiod > - > - > - > - > - > - > - nfsiod > - The NFS async I/O Daemon which services requests > - from its NFS server. > - > - > - > - > + The client can also run a daemon, known as > + nfsiod. The nfsiod > + daemon services the requests from the NFS server. This > + is optional, and improves performance, but is not required for normal > + and correct operation. See the &man.nfsiod.8; man page for more information. > + > > > > - Configuring NFS > + Configuring <acronym>NFS</acronym> > > NFS > configuration > > > - Luckily for us, on a FreeBSD system this setup is a snap. The > - processes that need to be running can all be run at boot time with > + NFS configuration is relatively straightforward > + process. The processes that need to be running can all start at boot time with > a few modifications to your /etc/rc.conf > - file. > + file. > > - On the NFS server make sure you have: > + On the NFS server, make sure that the following options > + are configured in the /etc/rc.conf file: > > portmap_enable="YES" > nfs_server_enable="YES" > -nfs_server_flags="-u -t -n 4" > mountd_flags="-r" > > - mountd is automatically run whenever the > - NFS server is enabled. The and > - flags to nfsd tell it to > - serve UDP and TCP clients. The flag tells > - nfsd to start 4 copies of itself. > + mountd runs automatically whenever the > + NFS server is enabled. > > - On the client, make sure you have: > + On the client, make sure this option is present in > + /etc/rc.conf: > > nfs_client_enable="YES" > -nfs_client_flags="-n 4" > - > - Like nfsd, the tells > - nfsiod to start 4 copies of itself. > + > > - The last configuration step requires that you create a file > - called /etc/exports. The exports file > - specifies which file systems on your server will be shared > - (a.k.a., exported) and with what clients they will > - be shared. Each line in the file specifies a file system to be > - shared. There are a handful of options that can be used in this > - file but only a few will be mentioned here. You can find out > - about the rest in the &man.exports.5; manual page. > + > + The /etc/exports > + file specifies which filesystems NFS should export (sometimes > + referred to as share). > + Each line in /etc/exports specifies a filesystem to be exported and > + which machines have access to that filesystem. Along with what machines have access > + to that filesystem, access options may also be specified. There are many such options > + that can be used in this file but only a few will be mentioned here. You can easily discover > + other options by reading over the &man.exports.5; manual page. > + > > Here are a few example /etc/exports > entries: > > > NFS > - exporting filesystems > + Examples of exporting filesystems > > - The following line exports /cdrom to > - three silly machines that have the same domain name as the server > + > + The following examples give an idea of how to export filesystems, > + although the settings may be different depending on > + your environment and network configuration. > + The following line exports /cdrom to > + three example machines that have the same domain name as the server > (hence the lack of a domain name for each) or have entries in your > /etc/hosts file. The > - flag makes the shared file system read-only. With this flag, the > - remote system will not be able to make any changes to the > - shared file system. > + flag makes the exported file system read-only. With this flag, the > + remote system will not be able to write any changes to the > + exported file system. > > - /cdrom -ro moe larry curly > + /cdrom -ro host1 host2 host3 > > The following line exports /home to three > hosts by IP address. This is a useful setup if you have a > - private network but do not have DNS running. The > - flag allows all the directories below > - the specified file system to be exported as well. > + private network without a DNS server configured. > + Optionally the /etc/hosts file could be configured > + for internal hostnames; please review &man.hosts.5; for more > + information. The flag allows the directories > + below the specified filesystem to also be exported. > > /home -alldirs 10.0.0.2 10.0.0.3 10.0.0.4 > > - The following line exports /a to two > - machines that have different domain names than the server. The > - flag allows > - the root user on the remote system to write to the shared > - file system as root. Without the -maproot=0 flag even if > - someone has root access on the remote system they will not > - be able to modify files on the shared file system. > + The following line exports /a so that two > + clients from different domains may access the filesystem. The > + flag allows the root > + user on the remote system to write data on the exported filesystem as > + root. If the -maproot=0 flag is not specified, then even if > + a user has root access on the remote system, they will not > + be able to modify files on the exported filesystem. > > - /a -maproot=0 host.domain.com box.example.com > + /a -maproot=0 host.example.com box.example.org > > - In order for a client to access- an exported file system it must > - have permission to do so. Make sure your client is listed in your > + In order for a client to access an exported filesystem, the client must > + have permission to do so. Make sure the client is listed in your > /etc/exports file. > > In /etc/exports, each line represents > the export information for one filesystem to one host. A > - remote host can only be specified once for each local > - filesystem, and you can only have one default entry per local > - filesystem. For example, let's assume that > - /usr is a single filesystem. The > - following /etc/exports is invalid: > + remote host can only be specified once per filesystem, and may only > + have one default entry. For example, assume that /usr > + is a single filesystem. The following /etc/exports > + would be valid: > > /usr/src client > /usr/ports client > > One filesystem, /usr, has two lines > - specifying its exports to the same host, > - client. The correct format is: > + specifying exports to the same host, client. > + The correct format for this situation is: > > /usr/src /usr/ports client > > @@ -874,40 +866,41 @@ > # client01 has root privileges on it > /usr/src /usr/ports -maproot=0 client01 > /usr/src /usr/ports client02 > -# The "client" machines have root and can mount anywhere > -# up /exports. Anyone inhe world can mount /exports/obj read-only > +# The client machines have root and can mount anywhere > +# on /exports. Anyone in the world can mount /exports/obj read-only > /exports -alldirs -maproot=0 client01 client02 > /exports/obj -ro > > You must restart > mountd whenever you modify > - /etc/exports to make changes take > - effect. This can be accomplished by sending the hangup signal > + /etc/exports so the changes can take effect. > + This can be accomplished by sending the hangup signal > to the mountd process: > > &prompt.root; kill -HUP `cat /var/run/mountd.pid` > > - Now that you have made all these changes you can just reboot > - and let FreeBSD start everything for you at boot time, or you can > - run the following commands as root: > + Alternatively, a reboot will make FreeBSD set everything > + up properly. A reboot is not necessary though. > + Executing the following commands as root, > + should start everything up. > > - On the NFS server: > + On the NFS server: > > &prompt.root; portmap > &prompt.root; nfsd -u -t -n 4 > &prompt.root; mountd -r > > - On the NFS client: > + On the NFS client: > > &prompt.root; nfsiod -n 4 > > - Now you should be ready to actually mount a remote file > - system. This can be done one of two ways. In these examples the > + Now everything should be ready to actually mount a remote file > + system. In these examples the > server's name will be server and the client's > - name will be client. If you just want to > - temporarily mount a remote file system or just want to test out > - your configuration you can run a command like this as root on the > - client: > + name will be client. If you only want to > + temporarily mount a remote file system or would rather test the > + configuration, just execute a command like this as root on the > + client: > > NFS > mounting filesystems > @@ -916,56 +909,59 @@ > > This will mount the /home directory > on the server at /mnt on the client. If > - everything is setup correctly you should be able to go into > - /mnt on the client and see all the files that are on the > - server. > - > - If you want to automatically mount a remote file system > - each time the computer boots, add the filesystem to > - /etc/fstab. Here is an example: > + everything is set up correctly you should be able to enter > + /mnt on the client and see all the files > + that are on the server. > + > + If you want to automatically mount a remote filesystem > + each time the computer boots, add the filesystem to the > + /etc/fstab file. Here is an example: > > server:/home /mnt nfs rw 0 0 > > - Read the &man.fstab.5; manual page for more options. > + The &man.fstab.5; manual page lists all the available options. > > > > Practical Uses > > - There are many very cool uses for NFS. Some of the more common > - ones are listed below. > + NFS has many practical uses. Some of the more common > + ones are listed below: > + > + The following NFS examples require > + NFS to be correctly configured before actual use, > + as previously discussed. > + > + > > NFS > uses > > > > - Have several machines on a network and share a CDROM or > - floppy drive among them. This is cheaper and often more > - convenient. > + Set several machines to share a CDROM or > + other media among them. This is cheaper and often > + more convenient. > > > > - With so many machines on a network, it gets old having your > - personal files strewn all over the place. You can have a > - central NFS server that houses all user home directories and > - shares them with the rest of the machines on the LAN, so no > - matter where you log in you will have the same home > - directory. > + On large networks, it might be more convenient to configure a > + central NFS server in which to store all the user > + home directories. These home directories can then be exported to > + the network so that users would always have the same home directory, > + regardless of which workstation they log in to. > > > > - When you get to reinstalling FreeBSD on one of your > - machines, NFS is the way to go! Just pop your distribution > - CDROM into your file server and away you go! > + You can use an exported CDROM to install > + software on multiple machines. > > > > - Have a common /usr/ports/distfiles > - directory that all your machines share. That way, when you go > - to install a port that you have already installed on a different > - machine, you do not have to download the source all over > - again! > + Several machines could have a common /usr/ports/distfiles > + directory. > + That way, when you need to install a port on several machines, you can > + quickly access the source without downloading it on each machine. > > > > @@ -992,14 +988,15 @@ > amd > automatic mounter daemon > > - &man.amd.8;, which is also known as the automatic mounter > - daemon, is a useful utility used for automatically mounting a > + &man.amd.8; (the automatic mounter daemon) > + is a useful that automatically mounts a > remote filesystem whenever a file or directory within that > filesystem is accessed. Filesystems that are inactive for a > period of time will also be automatically unmounted by > amd. Using > - amd provides a simplistic alternative > - to static mounts. > + amd provides a simple alternative > + to permanent mounts, as permanent mounts should be listed in the > + /etc/fstab. > > amd operates by attaching > itself as an NFS server to the /host and > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-doc" in the body of the message -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 15: 1:52 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 1646637B416 for ; Sat, 2 Mar 2002 15:01:46 -0800 (PST) Received: from hades.hell.gr (patr530-b140.otenet.gr [212.205.244.148]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g22N1Zou011809; Sun, 3 Mar 2002 01:01:36 +0200 (EET) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id g22N1XW23521; Sun, 3 Mar 2002 01:01:33 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Sun, 3 Mar 2002 01:01:32 +0200 From: Giorgos Keramidas To: Michael Lucas Cc: Tom Rhodes , freebsd-doc@freebsd.org Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Message-ID: <20020302230131.GA99866@hades.hell.gr> References: <200202262110.g1QLA2f07435@freefall.freebsd.org> <20020302152507.A83170@blackhelicopters.org> Mime-Version: 1.0 Content-Type: application/pgp; x-action=sign; format=text Content-Disposition: inline; filename="msg.pgp" In-Reply-To: <20020302152507.A83170@blackhelicopters.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2002-03-02 15:25, Michael Lucas wrote: > Okay, I think I'm done ripping on this poor guys work. Anything left > for me to say is purely stylistic. Tom has been doing a lot of work, lately. Michael, you've also carefully checked what he posted, and usually have already commented already by the time I downloaded the thread. My compliments, guys :) You certainly make everyone envy you^W^W^H proud. > > There is no need for users to have unique home directories > - on every machine on your network. Once they have an established > - directory that is available via NFS it can be accessed from > - anywhere. > + on every network machine. Home directories could be setup on the > + NFS server and made available throughout the network. >     I'd probably go for "There is no need for users to have separate ..." here. 'Unique' is almost exclusively used when a reference to a set of objects is made, and emphasis on their being different is needed. > > - Storage devices such as floppies and CDROM drives can be > - used by other machines on the network eliminating the need for > - extra hardware. > + Storage devices such as floppy disks, CDROM drives, and ZIP drives > + can be used by other machines on the network. This may reduce the number > + of removable media drives. Number of 'required' or 'necessary' media drives? Whose number of media drives? > + NFS consists of at least two main parts: a server > + and at least one client. The client remotely accesses the data that is stored > + on the server machine. In order for this to function properly a few > + processes have to be configured and running: Whitespace nit. If you use tab for initial line indentation, please use it consistently, before commiting this; since this replaces the entire paragraph, it doesn't count as a 'whitespace only change'. > + The portmapper daemon > + allows NFS clients to discover which port the NFS server > + is using. Whitespace nit. Since this is an entirely new , could we have it properly indented and wrapped too? (For some definition of 'properly' that fits the style of the rest of this document.) > + The client can also run a daemon, known as > + nfsiod. The nfsiod > + daemon services the requests from the NFS server. This > + is optional, and improves performance, but is not required for normal > + and correct operation. See the &man.nfsiod.8; man page for more information. s/man page/manual page/ This is not some doc-policy style of thing, but I tend to prefer one of these two forms: * The &blah; manual page. * You can find out by checking out &man.blah; how this is done. I'm not really that sure about this though. It's really up to you two to decide if you like one of these two any better. > + mountd runs automatically whenever the > + NFS server is enabled. Indentation needs fix0ring, and there's a missing . > nfs_client_enable="YES" > -nfs_client_flags="-n 4" > - > - Like nfsd, the tells > - nfsiod to start 4 copies of itself. > + Should we close on the first and 'last' line of content? nfs_client_enable="YES" > + > + The /etc/exports > ... > + that can be used in this file but only a few will be mentioned here. You can easily discover > + other options by reading over the &man.exports.5; manual page. > + Please indent a bit, wrap the replacement paragraph to some reasonable length, and make ... cuddle to the text within, at the beginning and end of it, like the rest of the text does: ... ... > + The following examples give an idea of how to export filesystems, > + although the settings may be different depending on > + your environment and network configuration. > + The following line exports /cdrom to > + three example machines that have the same domain name as the server I'm a little uncomfortable with two sentences that both start with 'The following'. The second could probably be rewritten as: For instance, to export /cdrom ... > + The following line exports /a so that two > + clients from different domains may access the filesystem. The > + flag allows the root > + user on the remote system to write data on the exported filesystem as That same tab vs. space thing for initial indentation, again :-/ Since there are many places where tabs and spaces have been mixed in indentation, I'll probably shuttup now. > + The &man.fstab.5; manual page lists all the available options. Wheeeee :) "The &foo; manual page." :) Thanks, thanks! > + Set several machines to share a CDROM or > + other media among them. This is cheaper and often > + more convenient. Than what? > + Several machines could have a common /usr/ports/distfiles wrap? [-- Finally --] Excellent work! I haven't used NFS in a while, and I am probably not the best guy to comment on technical parts of this, but it looks great. Very easy to follow, IMHO. My apologies, if commenting now is a bit late, and has you thinking things like 'Ya, right, Mr. Anal Retentiveness, where were you when we were writing this stuff?'. I seem to have a complete lack of organization in my time schedule these last weeks, and I keep forgetting TODO stuff. Cheers, Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) iD8DBQE8gVnL1g+UGjGGA7YRAnn9AJ4g/baYxyLTAcvNbIrhY8oCfQM2vACfSOe8 PEySyVyLUJX6dhmufV3y7+c= =bzKC -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 16: 1:52 2002 Delivered-To: freebsd-doc@freebsd.org Received: from smtp1.san.rr.com (smtp1.san.rr.com [24.25.195.37]) by hub.freebsd.org (Postfix) with ESMTP id 4428637B416 for ; Sat, 2 Mar 2002 16:01:51 -0800 (PST) Received: from 66-75-1-142.san.rr.com (66-75-1-142.san.rr.com [66.75.1.142]) by smtp1.san.rr.com (8.11.4/8.11.4) with ESMTP id g2301oM00033; Sat, 2 Mar 2002 16:01:50 -0800 (PST) Date: Sat, 2 Mar 2002 16:02:13 -0800 (PST) From: Peter Leftwich X-X-Sender: root@66-75-1-142.san.rr.com To: freebsd-doc@FreeBSD.org Subject: freebsd-xfree86 (?) Message-ID: <20020302160055.T942-100000@66-75-1-142.san.rr.com> Organization: Video2Video Services - http://Www.Video2Video.Com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, do you have any plans for a majordomo list about getting xfree86 to work on FreeBSD (4.5-RELEASE)? Thanks for a reply =-) -- Peter Leftwich President & Founder Video2Video Services Box 13692, La Jolla, CA, 92039 USA +1-413-403-9555 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 16:31:43 2002 Delivered-To: freebsd-doc@freebsd.org Received: from hex.databits.net (hex.csh.rit.edu [129.21.60.203]) by hub.freebsd.org (Postfix) with SMTP id A069437B402 for ; Sat, 2 Mar 2002 16:31:41 -0800 (PST) Received: (qmail 85162 invoked by uid 1001); 3 Mar 2002 00:13:03 -0000 Date: Sat, 2 Mar 2002 19:13:03 -0500 From: Pete Fritchman To: Peter Leftwich Cc: freebsd-doc@FreeBSD.org Subject: Re: freebsd-xfree86 (?) Message-ID: <20020302191303.D34179@databits.net> References: <20020302160055.T942-100000@66-75-1-142.san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020302160055.T942-100000@66-75-1-142.san.rr.com>; from Hostmaster@Video2Video.Com on Sat, Mar 02, 2002 at 04:02:13PM -0800 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ++ 02/03/02 16:02 -0800 - Peter Leftwich: | Hello, do you have any plans for a majordomo list about getting xfree86 to | work on FreeBSD (4.5-RELEASE)? Thanks for a reply =-) http://lists.csociety.org/listinfo/freebsd-xfree86 --pete -- Pete Fritchman [petef@(databits.net|freebsd.org|csh.rit.edu)] finger petef@databits.net for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 17:22:43 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9533737B402; Sat, 2 Mar 2002 17:22:39 -0800 (PST) Received: (from dd@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g231ES522434; Sat, 2 Mar 2002 17:14:28 -0800 (PST) (envelope-from dd) Date: Sat, 2 Mar 2002 17:14:28 -0800 (PST) From: Message-Id: <200203030114.g231ES522434@freefall.freebsd.org> To: nivit@libero.it, dd@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35273: Misprint in _secure_path(3) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Misprint in _secure_path(3) State-Changed-From-To: open->closed State-Changed-By: dd State-Changed-When: Sat Mar 2 17:14:19 PST 2002 State-Changed-Why: Corrected, thanks! http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35273 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 17:22:44 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5935F37B416; Sat, 2 Mar 2002 17:22:40 -0800 (PST) Received: (from keramida@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g231FsV22669; Sat, 2 Mar 2002 17:15:54 -0800 (PST) (envelope-from keramida) Date: Sat, 2 Mar 2002 17:15:54 -0800 (PST) From: Message-Id: <200203030115.g231FsV22669@freefall.freebsd.org> To: e0026813@stud3.tuwien.ac.at, keramida@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/35361: [PATCH] more pedantry for ktrace(1) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [PATCH] more pedantry for ktrace(1) State-Changed-From-To: open->closed State-Changed-By: keramida State-Changed-When: Sat Mar 2 17:15:18 PST 2002 State-Changed-Why: Committed in revision 1.15 and MFC'ed. Thank you :) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35361 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 17:22:47 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1549037B405; Sat, 2 Mar 2002 17:22:42 -0800 (PST) Received: (from dd@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g231I4f22856; Sat, 2 Mar 2002 17:18:04 -0800 (PST) (envelope-from dd) Date: Sat, 2 Mar 2002 17:18:04 -0800 (PST) From: Message-Id: <200203030118.g231I4f22856@freefall.freebsd.org> To: darklogik@pittgoth.com, dd@FreeBSD.org, freebsd-doc@freebsd.org, roam@FreeBSD.org Subject: Re: docs/35133: [patch] work for -junior doc hacker thread Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [patch] work for -junior doc hacker thread State-Changed-From-To: open->closed State-Changed-By: dd State-Changed-When: Sat Mar 2 17:17:45 PST 2002 State-Changed-Why: Peter committed this but forgot to close it. Responsible-Changed-From-To: freebsd-doc->roam Responsible-Changed-By: dd Responsible-Changed-When: Sat Mar 2 17:17:45 PST 2002 Responsible-Changed-Why: JFYI http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35133 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 18:12:59 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EF3CA37B400; Sat, 2 Mar 2002 18:12:39 -0800 (PST) Received: (from dd@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2323MG31600; Sat, 2 Mar 2002 18:03:22 -0800 (PST) (envelope-from dd) Date: Sat, 2 Mar 2002 18:03:22 -0800 (PST) From: Message-Id: <200203030203.g2323MG31600@freefall.freebsd.org> To: m.oosterhof@xs4all.nl, dd@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/34982: rc.conf man page does not list the kerberos5 (heimdal) options. Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: rc.conf man page does not list the kerberos5 (heimdal) options. State-Changed-From-To: open->closed State-Changed-By: dd State-Changed-When: Sat Mar 2 18:02:56 PST 2002 State-Changed-Why: Applied, thanks! http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 18:40: 8 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BC49037B41B for ; Sat, 2 Mar 2002 18:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g232e1539406; Sat, 2 Mar 2002 18:40:01 -0800 (PST) (envelope-from gnats) Received: from jinx.unknown.nu (jinx.unknown.nu [216.80.99.202]) by hub.freebsd.org (Postfix) with ESMTP id 57A0337B402 for ; Sat, 2 Mar 2002 18:35:02 -0800 (PST) Received: by jinx.unknown.nu (Postfix, from userid 1002) id B848F31FE; Sat, 2 Mar 2002 20:35:01 -0600 (CST) Message-Id: <20020303023501.B848F31FE@jinx.unknown.nu> Date: Sat, 2 Mar 2002 20:35:01 -0600 (CST) From: Kim Scarborough To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/35491: sshd(8) has an incorrect path Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 35491 >Category: docs >Synopsis: sshd(8) has an incorrect path >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Mar 02 18:40:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Kim Scarborough >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD jinx.unknown.nu 4.5-STABLE FreeBSD 4.5-STABLE #2: Sat Feb 23 17:05:29 CST 2002 toor@jinx.unknown.nu:/usr/src/sys/compile/JINX i386 >Description: The man page for sshd(8) gives an incorrect location for the "primes" file. >How-To-Repeat: man 8 sshd >Fix: *** sshd.8 Sat Mar 2 20:26:40 2002 --- sshd.8.orig Mon Jan 28 07:13:17 2002 *************** *** 1054,1060 **** the user so their contents can be copied to known hosts files. These files are created using .Xr ssh-keygen 1 . ! .It Pa /etc/ssh/primes Contains Diffie-Hellman groups used for the "Diffie-Hellman Group Exchange". .It Pa /var/run/sshd.pid Contains the process ID of the --- 1054,1060 ---- the user so their contents can be copied to known hosts files. These files are created using .Xr ssh-keygen 1 . ! .It Pa /etc/primes Contains Diffie-Hellman groups used for the "Diffie-Hellman Group Exchange". .It Pa /var/run/sshd.pid Contains the process ID of the >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 19:32:41 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C342B37B41C; Sat, 2 Mar 2002 19:32:39 -0800 (PST) Received: (from dd@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g233NYB47356; Sat, 2 Mar 2002 19:23:34 -0800 (PST) (envelope-from dd) Date: Sat, 2 Mar 2002 19:23:34 -0800 (PST) From: Message-Id: <200203030323.g233NYB47356@freefall.freebsd.org> To: dd@FreeBSD.org, freebsd-doc@freebsd.org, green@FreeBSD.org Subject: Re: docs/35491: sshd(8) has an incorrect path Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: sshd(8) has an incorrect path Responsible-Changed-From-To: freebsd-doc->green Responsible-Changed-By: dd Responsible-Changed-When: Sat Mar 2 19:22:45 PST 2002 Responsible-Changed-Why: Over to OpenSSH maintainer. (Note: the patch is reversed.) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35491 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message From owner-freebsd-doc Sat Mar 2 23: 3:41 2002 Delivered-To: freebsd-doc@freebsd.org Received: from web11401.mail.yahoo.com (web11401.mail.yahoo.com [216.136.131.231]) by hub.freebsd.org (Postfix) with SMTP id AF1F637B405 for ; Sat, 2 Mar 2002 23:03:38 -0800 (PST) Message-ID: <20020303070338.99619.qmail@web11401.mail.yahoo.com> Received: from [61.11.78.1] by web11401.mail.yahoo.com via HTTP; Sat, 02 Mar 2002 23:03:38 PST Date: Sat, 2 Mar 2002 23:03:38 -0800 (PST) From: karthik nil Subject: Want to Help you To: freebsd-doc@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Sir, My name is K.KARTHIK from India. Pls send me all neccessary details regarding me. Regards Karthik __________________________________________________ Do You Yahoo!? Yahoo! Sports - sign up for Fantasy Baseball http://sports.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message