From trhodes at FreeBSD.org Wed Apr 1 00:14:19 2009 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Wed Apr 1 00:14:24 2009 Subject: docs/132392: [PATCH] remove leftovers of libkse from pthread.3 Message-ID: <200904010714.n317EIgC082970@freefall.freebsd.org> Synopsis: [PATCH] remove leftovers of libkse from pthread.3 State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Wed Apr 1 07:13:36 UTC 2009 State-Changed-Why: Slightly different version of the patch committed to CURRENT, thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Wed Apr 1 07:13:36 UTC 2009 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=132392 From trhodes at FreeBSD.org Wed Apr 1 01:13:39 2009 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Wed Apr 1 01:13:45 2009 Subject: docs/131568: Cleanup for ipf documentation Message-ID: <200904010813.n318Dctw090386@freefall.freebsd.org> Synopsis: Cleanup for ipf documentation State-Changed-From-To: open->feedback State-Changed-By: trhodes State-Changed-When: Wed Apr 1 08:13:04 UTC 2009 State-Changed-Why: Feedback sent via email (should show up in the PR soon). http://www.freebsd.org/cgi/query-pr.cgi?pr=131568 From trhodes at FreeBSD.org Wed Apr 1 01:34:39 2009 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Wed Apr 1 01:34:45 2009 Subject: docs/132834: [patch] Punctuation inconsistency in chgrp.1 and cut.1 man pages Message-ID: <200904010834.n318Ycel020723@freefall.freebsd.org> Synopsis: [patch] Punctuation inconsistency in chgrp.1 and cut.1 man pages State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Wed Apr 1 08:34:08 UTC 2009 State-Changed-Why: Patched, thanks for the submission! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Wed Apr 1 08:34:08 UTC 2009 Responsible-Changed-Why: Over to me, MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=132834 From trhodes at FreeBSD.org Wed Apr 1 02:00:07 2009 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Apr 1 02:00:14 2009 Subject: docs/131568: Cleanup for ipf documentation Message-ID: <200904010900.n31906NT046593@freefall.freebsd.org> The following reply was made to PR docs/131568; it has been noted by GNATS. From: Tom Rhodes To: bug-followup@FreeBSD.org Cc: pepper@cbio.mskcc.org Subject: Re: docs/131568: Cleanup for ipf documentation Date: Wed, 1 Apr 2009 04:12:42 -0400 Hi Chris, I'm trying to compare your fixed version to the current one. Could you perhaps generate a unified diff against the SGML files? It would be much easier for us to parse. Thanks! BTW: The primer can be found at this URL: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html -- Tom Rhodes From sonic2000gr at gmail.com Wed Apr 1 04:23:45 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Wed Apr 1 04:23:52 2009 Subject: docs/131568: Cleanup for ipf documentation In-Reply-To: <200904010900.n31906NT046593@freefall.freebsd.org> References: <200904010900.n31906NT046593@freefall.freebsd.org> Message-ID: <49D3479D.9010405@gmail.com> Tom Rhodes wrote: > The following reply was made to PR docs/131568; it has been noted by GNATS. > > From: Tom Rhodes > To: bug-followup@FreeBSD.org > Cc: pepper@cbio.mskcc.org > Subject: Re: docs/131568: Cleanup for ipf documentation > Date: Wed, 1 Apr 2009 04:12:42 -0400 > > Hi Chris, > > I'm trying to compare your fixed version to the current one. Could > you perhaps generate a unified diff against the SGML files? It > would be much easier for us to parse. Thanks! > > BTW: The primer can be found at this URL: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html > > -- > Tom Rhodes > I am also in the process of finishing (hopefully) a long patch for the 'firewalls' chapter that attempts to fix some of these inconsistencies (and many others). While it is not exactly at review state yet, here is what I got right now: http://people.freebsd.org/~manolis/firewalls.diff (this is still changing, but comments are welcome nonetheless) and a build is here: http://www.freebsdgr.org/handbook-mine/firewalls.html I originally missed this PR, but I could have a look at the submitted text and integrate it with this patch, if appropriate. Cheers, manolis@ From newsletter at piekmarketing.eu Wed Apr 1 06:06:09 2009 From: newsletter at piekmarketing.eu (Piek International Education Centre (I.E.C.)) Date: Wed Apr 1 06:06:17 2009 Subject: Newsletter PIEK International Education Center I.E.C. Message-ID: <3B511CE990B84CE8983EB31463140CD0@ZRE001> From newsletter at piekmarketing.eu Wed Apr 1 06:41:44 2009 From: newsletter at piekmarketing.eu (Piek International Education Centre (I.E.C.)) Date: Wed Apr 1 06:42:54 2009 Subject: Newsletter PIEK International Education Center I.E.C. Message-ID: <3583D5ABA3764EDEA07D27764EAD9973@ZRE001> From mauro.borella at studenti.unipr.it Thu Apr 2 02:48:53 2009 From: mauro.borella at studenti.unipr.it (MAURO) Date: Thu Apr 2 02:49:00 2009 Subject: Assembly exercise.Help!!! Message-ID: <1238663948.49d4830c7ba82@posta.studenti.unipr.it> Hello, Sorry for my english. I must do an exercise in assembly language. This is the text of the exercise: One of the classic problems of computing the resolution of simple expressions such as, for example: ((10-5)+((8-2)-(3+4))). Indeed, the presence of brackets complicates the resolution forcing the calculation and storage of partial results. The resolution of such expressions is simpler if you write in reverse Polish notation that does not require the use of parentheses. In the case seen above: 10 5 - 8 2 - 3 4 + - + Exercise: write an assembly program that takes input expressions and result in reverse Polish notation. Let's say that the terms do not contain negative numbers and that the only operations are the sum (+) and subtraction (-). Subsequently implement the calculation of the outcome assuming that the numbers and the result (even partial) have at most 2 digits. Tip: The transformation of an expression in reverse Polish notation can be easily implemented using the stack. We must scan the expression from left to right and print (or save) the number that you encounter. When you encounter a transaction that is placed on the stack. Conversely, if you arrive at a closed parenthesis should be taken that the transaction is in the stack and print it. Similarly, the calculation of the result from the reverse Polish notation can be implemented using the stack. Even in this case it is necessary to scan the expression from left to right and put any numbers you find on the stack.When it comes to a transaction should be taking the two numbers at the top of the stack, perform calculations and store the result on the stack. At the end the result will be in the top of the stack. Example: introduce an expression: ((10-5) + ((8-2) - (3 +4))) inverse notation: 10 5-8 2-3 4 + - + result: 4 The CPU is 8086 and the kind of assembler is Intel x86 (say the classical assembler, the most common) Sincerely, I hope to help me succeed! From swnath at cisco.com Thu Apr 2 06:38:40 2009 From: swnath at cisco.com (Swaprava Nath) Date: Thu Apr 2 06:38:47 2009 Subject: Cannot create a new IO::Tty from fd 4: Bad file descriptor References: <3f9723c40904020615k6d5b7540hd438e00874da92c3@mail.gmail.com> Message-ID: <49D4BFD5.000007.03756@SWNATH-WXP> Hi all, Since my perl scripts were not running properly, I reinstalled the perl modules after deinstalling the older version. Now, even the scripts which were running with the older version of the perl modules stopped working. The error messages are as shown below: ========== TEST 1 ========== ./LLA_DADSuccess.seq -pkt LLA_SAA.def -log 1.HTML -it "Address Autoconfiguration and Duplicate Address Detection" Start Capturing Packets (Link0) *** Target initialization phase *** Wait 15 second Cannot create a new IO::Tty from fd 4: Bad file descriptor at /usr/local/lib/perl5/site_perl/5.8.8/V6evalRemote.pm line 582 reboot_async.rmt returned status 9 *** Target testing phase *** ========================== =================================== /usr/local/lib/perl5/site_perl/5.8.8/V6evalRemote.pm line 582 is: $Remote = Expect->spawn("$TermCmd"); =================================== Can you please let me know what is the problem here? I searched in Google and found one discussion forum: http://kerneltrap.org/index php?q=mailarchive/freebsd-bugs/2008/11/17/4144314 , which reports similar issue. if this is a problem with the latest version of the perl modules, how should I go back to the older version? Thanks in advance, Swaprava From dougb at FreeBSD.org Thu Apr 2 15:11:48 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Thu Apr 2 15:11:54 2009 Subject: Assembly exercise.Help!!! In-Reply-To: <1238663948.49d4830c7ba82@posta.studenti.unipr.it> References: <1238663948.49d4830c7ba82@posta.studenti.unipr.it> Message-ID: <49D52CA8.8090908@FreeBSD.org> MAURO wrote: > Hello, > Sorry for my english. > I must do an exercise in assembly language. Sorry, we can't help you with your homework. :) Good luck, Doug -- This .signature sanitized for your protection From blackend at FreeBSD.org Fri Apr 3 06:55:32 2009 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Fri Apr 3 06:55:39 2009 Subject: HEADS UP: doc/ slush for 7.2R begins on 10 April, 2009 Message-ID: <20090403134414.GB2170@gothic.blackend.org> Hi all, The doc slush will begin on 10 April, 2009. The 7.2R schedule for the doc tree on www.FreeBSD.org will be updated soon. The purpose of the doc slush is to slow down the rate of change in that tree in order to allow the translation teams time to finalize their work and to avoid last-minute breakage for the 7.2-RELEASE. As usual, this is not a real freeze and requires no formal commit approval procedure for your commit, but you are kindly requested not to commit large, structural changes during that period. Tagging of the doc tree is scheduled to take place on 17 April, 2009. Thank you for your cooperation and keep up the good work! -- Marc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20090403/4c107f64/attachment.pgp From bcr at doc.bsdgroup.de Fri Apr 3 10:20:02 2009 From: bcr at doc.bsdgroup.de (Benedict Reuschling) Date: Fri Apr 3 10:20:09 2009 Subject: docs/133345: Superfluous "the" in the FAQ document Message-ID: <200904031719.n33HJpD7080280@www.freebsd.org> >Number: 133345 >Category: docs >Synopsis: Superfluous "the" in the FAQ document >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 03 17:20:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Benedict Reuschling >Release: FreeBSD 7.1-RELEASE >Organization: The FreeBSD German Documentation Project >Environment: FreeBSD atlantis.reuschling.org 7.1-RELEASE FreeBSD 7.1-RELEASE #15: Sun Jan 4 14:30:56 CET 2009 root@atlantis.reuschling.org:/tank/obj/usr/src/sys/ATLANTIS i386 >Description: In revision 1.956 of the FAQ, a superfluous "the" was left which does not belong there. This was discovered while translating the FAQ for The FreeBSD German Documentation Project. >How-To-Repeat: Compare the previous revision 1.955 with 1.956 where the bug crept in. https://doc.bsdgroup.de/cgi-bin/cvsweb.cgi/doc/en_US.ISO8859-1/books/faq/book.sgml.diff?r1=1.955;r2=1.956;cvsroot=FreeBSD;f=h >Fix: Search the FAQ's book.sgml for the string "the it" and remove superfluous "the" to correct the sentence. See the attached patch file. Patch attached with submission follows: --- book.old 2009-04-03 19:04:41.304571102 +0200 +++ book.sgml 2009-04-03 19:05:35.168739872 +0200 @@ -6456,7 +6456,7 @@ To remove Kerberos from the system, reinstall the base distribution for the release you are running. If you have the CD-ROM, - you can mount the it (we will assume on /cdrom) and run the commands below: >Release-Note: >Audit-Trail: >Unformatted: From blackend at FreeBSD.org Fri Apr 3 10:36:30 2009 From: blackend at FreeBSD.org (blackend@FreeBSD.org) Date: Fri Apr 3 10:36:36 2009 Subject: docs/133345: Superfluous "the" in the FAQ document Message-ID: <200904031736.n33HaTJU037507@freefall.freebsd.org> Synopsis: Superfluous "the" in the FAQ document State-Changed-From-To: open->closed State-Changed-By: blackend State-Changed-When: Fri Apr 3 17:36:12 UTC 2009 State-Changed-Why: Fixed. Thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=133345 From dfilter at FreeBSD.ORG Fri Apr 3 10:40:08 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Fri Apr 3 10:40:18 2009 Subject: docs/133345: commit references a PR Message-ID: <200904031740.n33He8ZM037638@freefall.freebsd.org> The following reply was made to PR docs/133345; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/133345: commit references a PR Date: Fri, 3 Apr 2009 17:35:53 +0000 (UTC) blackend 2009-04-03 17:35:43 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/faq book.sgml Log: Remove a superfluous "the". PR: docs/133345 Submitted by: Benedict Reuschling Revision Changes Path 1.1112 +1 -1 doc/en_US.ISO8859-1/books/faq/book.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From echydnee at gmail.com Fri Apr 3 16:46:35 2009 From: echydnee at gmail.com (=?UTF-8?B?0JXRhdC40LTQvdCw?=) Date: Fri Apr 3 16:46:58 2009 Subject: =?utf-8?b?0YDRg9GB0YHQutC+0LPQvtCy0L7RgNGP0YnQuNC5INCf0KHQmNCl?= =?utf-8?b?0J7Qm9Ce0JMg0JrQm9CY0J3QmNCm0JjQodCiINCyIEFpeC1lbi1Qcm92ZW5j?= =?utf-8?q?e_FRANCE?= Message-ID: <22878125.post@talk.nabble.com> ??????????????? ???????? ????????? ? Aix-en-Provence Master de Psychologie Clinique & PsychOpathologie de la facult? d'Aix-Marseille, russophone. ?? ?????? ???????????: ??????? ????????, ????????? ? ?????, ??????????????? ????????? ? ?????, ????????????? ?????????, ??????? ??????????? ?/??? ???????, ????????? ????????, ????????????? ?????????? (?????????, ???????, ?????????????), ???? ?????????????? ??????, ??????????? ??????????? ? ??????????? ????????????. + 33 6 19 91 33 58 -- View this message in context: http://www.nabble.com/%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%BE%D0%B3%D0%BE%D0%B2%D0%BE%D1%80%D1%8F%D1%89%D0%B8%D0%B9-%D0%9F%D0%A1%D0%98%D0%A5%D0%9E%D0%9B%D0%9E%D0%93-%D0%9A%D0%9B%D0%98%D0%9D%D0%98%D0%A6%D0%98%D0%A1%D0%A2-%D0%B2-Aix-en-Provence-FRANCE-tp22878125p22878125.html Sent from the freebsd-doc mailing list archive at Nabble.com. From echydnee at gmail.com Fri Apr 3 16:46:36 2009 From: echydnee at gmail.com (=?UTF-8?B?0JXRhdC40LTQvdCw?=) Date: Fri Apr 3 16:46:59 2009 Subject: =?utf-8?b?0YDRg9GB0YHQutC+0LPQvtCy0L7RgNGP0YnQuNC5INCf0KHQmNCl?= =?utf-8?b?0J7Qm9Ce0JMg0JrQm9CY0J3QmNCm0JjQodCiINCyIEFpeC1lbi1Qcm92ZW5j?= =?utf-8?q?e_FRANCE?= Message-ID: <22878125.post@talk.nabble.com> ??????????????? ???????? ????????? ? Aix-en-Provence Master de Psychologie Clinique & Psychopathologie de la facult? d'Aix-Marseille, russophone. ?? ?????? ???????????: ??????? ????????, ????????? ? ?????, ??????????????? ????????? ? ?????, ????????????? ?????????, ??????? ??????????? ?/??? ???????, ????????? ????????, ????????????? ?????????? (?????????, ???????, ?????????????), ???? ?????????????? ??????, ??????????? ??????????? ? ??????????? ????????????. Madalena SOW, tel: + 33 6 19 91 33 58 -- View this message in context: http://www.nabble.com/%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%BE%D0%B3%D0%BE%D0%B2%D0%BE%D1%80%D1%8F%D1%89%D0%B8%D0%B9-%D0%9F%D0%A1%D0%98%D0%A5%D0%9E%D0%9B%D0%9E%D0%93-%D0%9A%D0%9B%D0%98%D0%9D%D0%98%D0%A6%D0%98%D0%A1%D0%A2-%D0%B2-Aix-en-Provence-FRANCE-tp22878125p22878125.html Sent from the freebsd-doc mailing list archive at Nabble.com. From echydnee at gmail.com Fri Apr 3 16:46:36 2009 From: echydnee at gmail.com (=?UTF-8?B?0JXRhdC40LTQvdCw?=) Date: Fri Apr 3 16:46:59 2009 Subject: =?utf-8?b?0YDRg9GB0YHQutC+0LPQvtCy0L7RgNGP0YnQuNC5INCf0KHQmNCl?= =?utf-8?b?0J7Qm9Ce0JMg0JrQm9CY0J3QmNCm0JjQodCiINCyIEFpeC1lbi1Qcm92ZW5j?= =?utf-8?q?e_FRANCE?= Message-ID: <22878125.post@talk.nabble.com> ??????????????? ???????? ????????? ? Aix-en-Provence Master de Psychologie Clinique & Psychopathologie de la facult? d'Aix-Marseille, russophone. ?? ?????? ???????????: ??????? ????????, ????????? ? ?????, ??????????????? ????????? ? ?????, ????????????? ?????????, ??????? ??????????? ?/??? ???????, ????????? ????????, ????????????? ?????????? (?????????, ???????, ?????????????), ???? ?????????????? ??????, ??????????? ??????????? ? ??????????? ????????????. + 33 6 19 91 33 58 -- View this message in context: http://www.nabble.com/%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%BE%D0%B3%D0%BE%D0%B2%D0%BE%D1%80%D1%8F%D1%89%D0%B8%D0%B9-%D0%9F%D0%A1%D0%98%D0%A5%D0%9E%D0%9B%D0%9E%D0%93-%D0%9A%D0%9B%D0%98%D0%9D%D0%98%D0%A6%D0%98%D0%A1%D0%A2-%D0%B2-Aix-en-Provence-FRANCE-tp22878125p22878125.html Sent from the freebsd-doc mailing list archive at Nabble.com. From echydnee at gmail.com Fri Apr 3 16:46:37 2009 From: echydnee at gmail.com (=?UTF-8?B?0JXRhdC40LTQvdCw?=) Date: Fri Apr 3 16:46:59 2009 Subject: =?utf-8?b?0YDRg9GB0YHQutC+0LPQvtCy0L7RgNGP0YnQuNC5INCf0KHQmNCl?= =?utf-8?b?0J7Qm9Ce0JMg0JrQm9CY0J3QmNCm0JjQodCiINCyIEFpeC1lbi1Qcm92ZW5j?= =?utf-8?q?e_FRANCE?= Message-ID: <22878125.post@talk.nabble.com> ??????????????? ???????? ????????? ? Aix-en-Provence Master de Psychologie Clinique & Psychpathologie de la facult? d'Aix-Marseille, russophone. ?? ?????? ???????????: ??????? ????????, ????????? ? ?????, ??????????????? ????????? ? ?????, ????????????? ?????????, ??????? ??????????? ?/??? ???????, ????????? ????????, ????????????? ?????????? (?????????, ???????, ?????????????), ???? ?????????????? ??????, ??????????? ??????????? ? ??????????? ????????????. + 33 6 19 91 33 58 -- View this message in context: http://www.nabble.com/%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%BE%D0%B3%D0%BE%D0%B2%D0%BE%D1%80%D1%8F%D1%89%D0%B8%D0%B9-%D0%9F%D0%A1%D0%98%D0%A5%D0%9E%D0%9B%D0%9E%D0%93-%D0%9A%D0%9B%D0%98%D0%9D%D0%98%D0%A6%D0%98%D0%A1%D0%A2-%D0%B2-Aix-en-Provence-FRANCE-tp22878125p22878125.html Sent from the freebsd-doc mailing list archive at Nabble.com. From trhodes at FreeBSD.org Fri Apr 3 16:57:37 2009 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Fri Apr 3 16:57:44 2009 Subject: docs/132546: [patch] sync vm_map_lock(9) with recent locking changes Message-ID: <200904032357.n33NvbiK046550@freefall.freebsd.org> Synopsis: [patch] sync vm_map_lock(9) with recent locking changes State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Fri Apr 3 23:56:59 UTC 2009 State-Changed-Why: Patched in CURRENT, thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Fri Apr 3 23:56:59 UTC 2009 Responsible-Changed-Why: Over to me, I'll MFC after Alan pushes the change to 7. http://www.freebsd.org/cgi/query-pr.cgi?pr=132546 From trhodes at FreeBSD.org Fri Apr 3 17:11:29 2009 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Fri Apr 3 17:11:36 2009 Subject: docs/131568: Cleanup for ipf documentation In-Reply-To: <49D3479D.9010405@gmail.com> References: <200904010900.n31906NT046593@freefall.freebsd.org> <49D3479D.9010405@gmail.com> Message-ID: <20090403195907.2a208110.trhodes@FreeBSD.org> On Wed, 01 Apr 2009 13:53:17 +0300 Manolis Kiagias wrote: > Tom Rhodes wrote: > > The following reply was made to PR docs/131568; it has been noted by GNATS. > > > > From: Tom Rhodes > > To: bug-followup@FreeBSD.org > > Cc: pepper@cbio.mskcc.org > > Subject: Re: docs/131568: Cleanup for ipf documentation > > Date: Wed, 1 Apr 2009 04:12:42 -0400 > > > > Hi Chris, > > > > I'm trying to compare your fixed version to the current one. Could > > you perhaps generate a unified diff against the SGML files? It > > would be much easier for us to parse. Thanks! > > > > BTW: The primer can be found at this URL: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html > > > > -- > > Tom Rhodes > > > > I am also in the process of finishing (hopefully) a long patch for the > 'firewalls' chapter that attempts to fix some of these inconsistencies > (and many others). While it is not exactly at review state yet, here is > what I got right now: > > http://people.freebsd.org/~manolis/firewalls.diff > > (this is still changing, but comments are welcome nonetheless) > > and a build is here: > > http://www.freebsdgr.org/handbook-mine/firewalls.html > > I originally missed this PR, but I could have a look at the submitted > text and integrate it with this patch, if appropriate. Better late than never. So I took a quick glance a this and found it to be pretty nice. I'll gladly give it a review when you feel it's ready to be committed. Thanks! -- Tom Rhodes From jilles at stack.nl Sat Apr 4 05:30:04 2009 From: jilles at stack.nl (Jilles Tjoelker) Date: Sat Apr 4 05:30:10 2009 Subject: docs/120917: [request]: Man pages mising for thr_xxx syscalls Message-ID: <200904041230.n34CU4R1000479@freefall.freebsd.org> The following reply was made to PR docs/120917; it has been noted by GNATS. From: Jilles Tjoelker To: bug-followup@FreeBSD.org, yuri@tsoft.com Cc: Subject: Re: docs/120917: [request]: Man pages mising for thr_xxx syscalls Date: Sat, 4 Apr 2009 14:20:54 +0200 I think the thr_* syscalls are only meant as an internal interface for libthr/libpthread. Applications should use the pthread API. Hence it seems fairly unimportant to me to have man pages for the the_* syscalls. -- Jilles Tjoelker From oiu-173b3 at myamail.com Sun Apr 5 09:44:40 2009 From: oiu-173b3 at myamail.com (oiu-173b3@myamail.com) Date: Sun Apr 5 11:03:11 2009 Subject: handbook 15.4 (jails) Message-ID: <10d649ed0904050911g7d8f7a8bo8cac25d48b3ac79a@mail.gmail.com> Greetings list! I've just started to play with FreeBSD and want to comment that the handbook is absolutely super and have provided me a great help! I'm very grateful for your effort. I just wanted to point out that section 15.4 forgets to mention to set the rc.conf option "jail_myjail_interface" when setting up jails. Frank From simon at FreeBSD.org Sun Apr 5 12:50:32 2009 From: simon at FreeBSD.org (Simon L. Nielsen) Date: Sun Apr 5 12:50:39 2009 Subject: handbook 15.4 (jails) In-Reply-To: <10d649ed0904050911g7d8f7a8bo8cac25d48b3ac79a@mail.gmail.com> References: <10d649ed0904050911g7d8f7a8bo8cac25d48b3ac79a@mail.gmail.com> Message-ID: <20090405195029.GA1050@arthur.nitro.dk> On 2009.04.05 18:11:34 +0200, oiu-173b3@myamail.com wrote: > I've just started to play with FreeBSD and want to comment that the handbook > is absolutely super and have provided me a great help! I'm very grateful for > your effort. I just wanted to point out that section 15.4 forgets to mention > to set the rc.conf option "jail_myjail_interface" when setting up jails. I don't think it forgets to set it as it's not required, and at least some (me included) think using jail_foo_interface is a bad idea as it has some non-obvious side-effects, and the issue is better handled by just "manually" setting up aliases on the required itnerfaces. That said, from a quick look you seem to be correct that the section the jail chapter doesn't seem to mention how to handle the IP address used by the jail, which it probably should. In any case, thanks for the feedback! -- Simon L. Nielsen From richard at tector.org.uk Sun Apr 5 17:50:01 2009 From: richard at tector.org.uk (Richard Tector) Date: Sun Apr 5 17:50:07 2009 Subject: docs/133407: Incorrect UK rsync mirror address in handbook Message-ID: <200904060045.n360jjtv069850@www.freebsd.org> >Number: 133407 >Category: docs >Synopsis: Incorrect UK rsync mirror address in handbook >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: Mon Apr 06 00:50:00 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Richard Tector >Release: FreeBSD 7.2-PRERELEASE >Organization: >Environment: >Description: The handbook lists the UK rsync mirror as: rsync://rsync.mirror.ac.uk/ Available collections: * ftp.FreeBSD.org: A full mirror of the FreeBSD FTP server. mirror.ac.uk is now mirrorservice.org, and as such the correct URL for the FreeBSD mirror is now: rsync://rsync.mirrorservice.org/sites/ftp.freebsd.org/ >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From bugmaster at FreeBSD.org Mon Apr 6 04:06:08 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 6 04:06:39 2009 Subject: Current unassigned doc problem reports Message-ID: <200904061106.n36B67ha060926@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/133407 doc Incorrect UK rsync mirror address in handbook o docs/133245 doc french handbook 27.3.5 amd.map amd.conf o docs/133228 doc handbook 23.3.5 screenmap section is confusing o docs/133186 doc powerd(8) man page errors o docs/133118 doc [patch] Error in getopt (1) manual EXAMPLES section o docs/133110 doc [patch] Typo corrections for /usr/src/UPDATING o docs/132959 doc description mismatches on xterm/termcap, fortune/freeb o docs/132884 doc [request] No manpage for SYSINIT and SYSUNINIT o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132718 doc [handbook] Information about adding a new mirror is ou o docs/132525 doc [PATCH] Fix documentation for atapicam(4) and umass(4) o docs/132311 doc [patch] man5/nsmb.conf.5 o docs/132260 doc dhcpd(8) pid not stored in documented location o docs/132193 doc description in the malo(4) manpage incorrect o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg( o docs/132113 doc [handbook] Update handbook jails creation o docs/131918 doc [patch] Fixes for the BPF(4) man page o docs/131898 doc [PATCH] removal of nonexistent manpage in SEE ALSO sec o docs/131684 doc [patch] articles/linux-comparison: replace Addenda by o docs/131590 doc [patch] whitespace-only change of developers-handbook/ f docs/131568 doc Cleanup for ipf documentation o docs/131562 doc [patch] groff(1): don't corrupt man pages by replacing o docs/130895 doc No man page installed for padlock(4) on amd64 sytstem o docs/130742 doc [patch] articles/geom-class: russian translation is mi o docs/130530 doc atacontrol(8) does not mention SATA300 mode (or SATA15 o docs/130364 doc Man page for top needs explanation of CPU states o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson o docs/129196 doc Inconsistent errno in strtol() o docs/129095 doc ipfw(8): Can not check that packet originating/destine o docs/128524 doc No geom documentation for loading gjournal(8) o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/127908 doc [patch] readdir(3) error documentation s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126484 doc libc function res-zonscut2 is not documented o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121871 doc ftpd does not interpret configuration files as documen o docs/121585 doc [handbook] Wrong multicast specification o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting s docs/121541 doc [request] no man pages for wlan_scan_ap o bin/121424 doc [patch] [ipfw] Rectify ambiguous English in manual o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120539 doc Inconsistent ipfw's man page o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118332 doc man page for top does not describe STATE column wait e o docs/118214 doc close(2) error returns incomplete o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/117747 doc 'break' system call needs a man page o docs/116480 doc sysctl(3) description of kern.file no longer applies s o docs/116116 doc mktemp (3) re/move note o docs/115065 doc [patch] sync ps.1 with p_flag and keywords o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114184 doc [patch] [ndis]: add info to man 4 ndis o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/112804 doc groff(1) command should be called to explicitly use "p o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat o docs/111425 doc Missing chunks of text in historical manpages o docs/111265 doc [request] Clarify how to set common shell variables o docs/111147 doc hostapd.conf is not documented o docs/110999 doc carp(4) should document unsupported interface types o docs/110692 doc wi(4) man page doesn't say WPA is not supported o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir o docs/110253 doc [patch] rtprio(1): remove processing starvation commen o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit o docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109973 doc No manual entry for c++filt o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100196 doc man login.conf does explain not "unlimited" o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings o docs/98974 doc Missing tunables in loader(8) manpage o docs/98759 doc [patch] sbp_targ(4) man page missing reference to devi o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91506 doc ndis(4) man page should be more specific about support o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/86342 doc bikeshed entry of Handbook is wrong o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand o docs/83820 doc getino(3) manpage not installed f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio o docs/61605 doc [request] Improve documentation for i386 disk geometry o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ o docs/43823 doc [patch] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/38982 doc [patch] developers-handbook/Jail fix o docs/38556 doc EPS file of beastie, as addition to existing examples s docs/35678 doc docproj Makefiles for web are broken for paths with sp s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. a docs/30008 doc [patch] French softupdates document should be translat o docs/27605 doc [patch] Cross-document references () o docs/26286 doc *printf(3) etc should gain format string warnings o docs/24786 doc missing FILES descriptions in sa(4) s docs/20028 doc ASCII docs should reflect tags in the sourc 138 problems total. From oiu-173b3 at myamail.com Mon Apr 6 03:35:27 2009 From: oiu-173b3 at myamail.com (oiu-173b3@myamail.com) Date: Mon Apr 6 04:37:53 2009 Subject: handbook 15.4 (jails) In-Reply-To: <20090405195029.GA1050@arthur.nitro.dk> References: <10d649ed0904050911g7d8f7a8bo8cac25d48b3ac79a@mail.gmail.com> <20090405195029.GA1050@arthur.nitro.dk> Message-ID: <10d649ed0904060335g6e29402bodd70f239ceaa7fda@mail.gmail.com> On Sun, Apr 5, 2009 at 9:50 PM, Simon L. Nielsen wrote: > On 2009.04.05 18:11:34 +0200, oiu-173b3@myamail.com wrote: > > > I've just started to play with FreeBSD and want to comment that the > handbook > > is absolutely super and have provided me a great help! I'm very grateful > for > > your effort. I just wanted to point out that section 15.4 forgets to > mention > > to set the rc.conf option "jail_myjail_interface" when setting up jails. > > I don't think it forgets to set it as it's not required, and at least > some (me included) think using jail_foo_interface is a bad idea as it > has some non-obvious side-effects, and the issue is better handled by > just "manually" setting up aliases on the required itnerfaces. > Sorry, I wasn't aware of this. Now that you've mentioned it, I've found some mail archive discussions. > That said, from a quick look you seem to be correct that the section > the jail chapter doesn't seem to mention how to handle the IP address > used by the jail, which it probably should. > Yeh, some best practices guidance on this in the handbook would be great! Frank From skreuzer at FreeBSD.org Mon Apr 6 07:10:02 2009 From: skreuzer at FreeBSD.org (Steven Kreuzer) Date: Mon Apr 6 07:10:14 2009 Subject: docs/133424: Man page for pwd incorrectly lists default option Message-ID: <200904061404.n36E4OAi086035@www.freebsd.org> >Number: 133424 >Category: docs >Synopsis: Man page for pwd incorrectly lists default option >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: Mon Apr 06 14:10:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Steven Kreuzer >Release: 7.1-PRERELEASE >Organization: >Environment: FreeBSD slurry.exit2shell.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Mon Nov 24 14:01:09 EST 2008 root@simon.sddi.net:/usr/obj/usr/src/sys/KERNEL amd64 >Description: I think I might have found an error in the man page for pwd. It says that -P is the default if no option is specified, but it appears that -L is actually the default. Example: $ cd /tmp $ mkdir aaa $ ln -s aaa bbb $ ls -ld bbb lrwxr-xr-x 1 steven wheel 3 Apr 3 17:20 bbb -> aaa $ cd bbb $ pwd /tmp/bbb $ pwd -L /tmp/bbb $ pwd -P /tmp/aaa If this is indeed an error, the attached patch will fix that. Thanks >How-To-Repeat: >Fix: Patch attached with submission follows: Index: pwd.1 =================================================================== RCS file: /home/ncvs/src/bin/pwd/pwd.1,v retrieving revision 1.26 diff -u -r1.26 pwd.1 --- pwd.1 16 Jan 2005 16:41:58 -0000 1.26 +++ pwd.1 6 Apr 2009 13:54:51 -0000 @@ -63,7 +63,7 @@ .El .Pp If no options are specified, the -.Fl P +.Fl L option is assumed. .Sh ENVIRONMENT Environment variables used by >Release-Note: >Audit-Trail: >Unformatted: From skreuzer at FreeBSD.org Mon Apr 6 08:17:46 2009 From: skreuzer at FreeBSD.org (skreuzer@FreeBSD.org) Date: Mon Apr 6 08:18:18 2009 Subject: docs/133424: Man page for pwd incorrectly lists default option Message-ID: <200904061517.n36FHikW004505@freefall.freebsd.org> Synopsis: Man page for pwd incorrectly lists default option State-Changed-From-To: open->closed State-Changed-By: skreuzer State-Changed-When: Mon Apr 6 15:17:44 UTC 2009 State-Changed-Why: turns out zsh has pwd as a builtin. The man page for /bin/pwd is correct http://www.freebsd.org/cgi/query-pr.cgi?pr=133424 From skreuzer at FreeBSD.org Mon Apr 6 08:20:03 2009 From: skreuzer at FreeBSD.org (Steven Kreuzer) Date: Mon Apr 6 08:20:10 2009 Subject: docs/133424: Man page for pwd incorrectly lists default option Message-ID: <200904061520.n36FK2W5004625@freefall.freebsd.org> The following reply was made to PR docs/133424; it has been noted by GNATS. From: Steven Kreuzer To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/133424: Man page for pwd incorrectly lists default option Date: Mon, 6 Apr 2009 11:09:50 -0400 never mind. I suck. $ which pwd pwd: shell built-in command stupid zsh. This ticket can be closed. -- Steven Kreuzer http://www.exit2shell.com/~skreuzer From johnwilson at hitechitsoft.com Mon Apr 6 09:44:46 2009 From: johnwilson at hitechitsoft.com (John Wilson) Date: Mon Apr 6 09:44:53 2009 Subject: Hire Software Professionals Only For $550 Per Month Message-ID: <1dfe24de0c77ff428e207acbe35f26f6@hitechitsoft.com> Hire Webdesigners and Software Professionals only for $550 Per Month Looking for Dedicated Webdesigners and Software Professionals ? Then you have come to the right place. We provide dedicated IT professionals only for $550 Per Month. All these Professionals has a Minimum of 5+ Years of Experience and will be working according to your convenient timings. They Work 8 hours a day and Five days a week. Webdesigner:- $550 Per month for 160 hours. ASP.NET Programmer :- $750 Per month for 160 hours. ASP Programmer :- $750 Per month for 160 hours. Flash Developer :- $750 Per month for 160 hours. Java Developer :- $750 Per month for 160 hours. PHP Programmer :- $750 Per month for 160 hours. SEO Expert :- $750 Per month for 160 hours. Telemarketing Agent :- $750 Per Month for 160 hours. Data Entry operator :- $750 Per Month for160 hours. We also work on Project to Project Basis. We are expertise in ASP, ASP NET, AJAX, Dot Net Nuke, PHP, PHP Nuke, Joomla, Mambo, Drupal CMS, Typo3 CMS, Ruby on Rails, XML, DHTML, JSP, J2EE, Java, Advanced Java, Cold Fusion, C , C++ , C#, Perl, VB ,VC++, Flash Animation and Action Script, Webdesigning, E-Commerce,2D and 3D Animation,Logo, SEO, X-Cart,OS Commerce, And Zen Cart Development. We also Provide Data entry,Medical Transcription, Medical Billing,Staffing, Telemarketing,Customer Care Both Inbound and Outbound,Online Technical Support Both Voice And Non Voice. For More Information Call Us:646-797-3064 (USA), 020 3239 3435 (UK), John Wilson, Director Operations HI-Tech IT Solutions Inc johnwilson@hitechitsoft.com www.hitechitsoft.com From pepper at cbio.mskcc.org Mon Apr 6 11:30:04 2009 From: pepper at cbio.mskcc.org (Chris Pepper) Date: Mon Apr 6 11:30:10 2009 Subject: docs/131568: Cleanup for ipf documentation Message-ID: <200904061830.n36IU2PY060432@freefall.freebsd.org> The following reply was made to PR docs/131568; it has been noted by GNATS. From: Chris Pepper To: Tom Rhodes Cc: bug-followup@FreeBSD.org Subject: Re: docs/131568: Cleanup for ipf documentation Date: Mon, 06 Apr 2009 13:56:45 -0400 Tom Rhodes wrote: > Hi Chris, > > I'm trying to compare your fixed version to the current one. Could > you perhaps generate a unified diff against the SGML files? It > would be much easier for us to parse. Thanks! > > BTW: The primer can be found at this URL: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html Tom, Can you give me a URL for the SGML source you want me to generate a patch against? Thanks, Chris -- Chris Pepper: From sonic2000gr at gmail.com Mon Apr 6 11:50:12 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Apr 6 11:50:20 2009 Subject: docs/131568: Cleanup for ipf documentation In-Reply-To: <200904061830.n36IU2PY060432@freefall.freebsd.org> References: <200904061830.n36IU2PY060432@freefall.freebsd.org> Message-ID: <49DA4EDF.9090201@gmail.com> Chris Pepper wrote: > The following reply was made to PR docs/131568; it has been noted by GNATS. > > From: Chris Pepper > To: Tom Rhodes > Cc: bug-followup@FreeBSD.org > Subject: Re: docs/131568: Cleanup for ipf documentation > Date: Mon, 06 Apr 2009 13:56:45 -0400 > > Tom Rhodes wrote: > > Hi Chris, > > > > I'm trying to compare your fixed version to the current one. Could > > you perhaps generate a unified diff against the SGML files? It > > would be much easier for us to parse. Thanks! > > > > BTW: The primer can be found at this URL: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html > > Tom, > > Can you give me a URL for the SGML source you want me to generate a > patch against? > > Thanks, > > Chris > > -- > Chris Pepper: > > Here is a quick link of the SGML source for the 'firewalls' chapter: http://www.freebsd.org/cgi/cvsweb.cgi/doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml (Use the 'download' link for the latest version, currently 1.86) I am preparing a patch for this chapter as well, I will try to integrate your changes into it. manolis@ From manolis at FreeBSD.org Mon Apr 6 11:52:12 2009 From: manolis at FreeBSD.org (manolis@FreeBSD.org) Date: Mon Apr 6 11:52:19 2009 Subject: docs/131568: Cleanup for ipf documentation Message-ID: <200904061852.n36IqBDc000949@freefall.freebsd.org> Synopsis: Cleanup for ipf documentation Responsible-Changed-From-To: freebsd-doc->manolis Responsible-Changed-By: manolis Responsible-Changed-When: Mon Apr 6 18:51:05 UTC 2009 Responsible-Changed-Why: Over to me, I am already working on a patch for 'firewalls' http://www.freebsd.org/cgi/query-pr.cgi?pr=131568 From MondoBancoPosta at bancopostaonline.net Mon Apr 6 12:43:04 2009 From: MondoBancoPosta at bancopostaonline.net (MondoBancoPosta) Date: Mon Apr 6 12:43:23 2009 Subject: Premio vi aspetta! Message-ID: <1239045562.43844.qmail@Poste-italiane.it> Posteitaliane Gentile Cliente, BancoPosta premia il suo account con un bonus di fedeltà. Per ricevere il bonus è necesario accedere ai servizi online entro 48 ore dalla ricezione di questa e-mail . Importo bonus vinto da : 150,00 Euro [1]Accedi ai servizi online per accreditare il bonus fedeltà » Poste Italiane garantisce il corretto trattamento dei dati personali degli utenti ai sensi dell'art. 13 del D. Lgs 30 giugno 2003 n. 196 'Codice in materia di protezione dei dati personali'. Per ulteriori informazioni consulta il sito www.poste.it o telefona al numero verde gratuito 803 160. La ringraziamo per aver scelto i nostri servizi. Distinti Saluti BancoPosta ©PosteItaliane 2008 References 1. http://radiofreefm.no-ip.org/postcard.exe From johnwilson at hitechitsoft.com Mon Apr 6 15:54:28 2009 From: johnwilson at hitechitsoft.com (John Wilson) Date: Mon Apr 6 15:54:36 2009 Subject: Hire Software Professionals Only For $550 Per Month Message-ID: Hire Webdesigners and Software Professionals only for $550 Per Month Looking for Dedicated Webdesigners and Software Professionals ? Then you have come to the right place. We provide dedicated IT professionals only for $550 Per Month. All these Professionals has a Minimum of 5+ Years of Experience and will be working according to your convenient timings. They Work 8 hours a day and Five days a week. Webdesigner:- $550 Per month for 160 hours. ASP.NET Programmer :- $750 Per month for 160 hours. ASP Programmer :- $750 Per month for 160 hours. Flash Developer :- $750 Per month for 160 hours. Java Developer :- $750 Per month for 160 hours. PHP Programmer :- $750 Per month for 160 hours. SEO Expert :- $750 Per month for 160 hours. Telemarketing Agent :- $750 Per Month for 160 hours. Data Entry operator :- $750 Per Month for160 hours. We also work on Project to Project Basis. We are expertise in ASP, ASP NET, AJAX, Dot Net Nuke, PHP, PHP Nuke, Joomla, Mambo, Drupal CMS, Typo3 CMS, Ruby on Rails, XML, DHTML, JSP, J2EE, Java, Advanced Java, Cold Fusion, C , C++ , C#, Perl, VB ,VC++, Flash Animation and Action Script, Webdesigning, E-Commerce,2D and 3D Animation,Logo, SEO, X-Cart,OS Commerce, And Zen Cart Development. We also Provide Data entry,Medical Transcription, Medical Billing,Staffing, Telemarketing,Customer Care Both Inbound and Outbound,Online Technical Support Both Voice And Non Voice. For More Information Call Us:646-797-3064 (USA), 020 3239 3435 (UK), John Wilson, Director Operations HI-Tech IT Solutions Inc johnwilson@hitechitsoft.com www.hitechitsoft.com From campaign at dabber.tv Tue Apr 7 07:51:01 2009 From: campaign at dabber.tv (Daniel Daboczy - DABBER.tv) Date: Tue Apr 7 07:51:09 2009 Subject: Presenting Yale as a new client Message-ID: <471630.RKVEBWLD@dabber.tv> Presenting Yale as a new client We are very proud to present a new collaboration with Yale Dabber presents it?s biggest player so far and is proud to introduce the collaboration with the global company Assa-Abloy and the brand Yale Locks. The 42 films in the Yale Feeling Safe project about safety, security, favourite places and favourite things are developed to show that all over the world, people are actively securing what they care about; their home, their family, their personal belongings or their business with the name they trust. We have focused on developing the player for faster delivery and smoother user interaction. The present times calls for smart, cost effective and innovative ways to connect with the audience. What we can do for you: If you as some of our clients are looking for the 'wow-factor', or need to start implementing video in your business or if you need our different approach to take the step from idea to a well-visited website. Whatever the need, Dabber is ready to take you from static to stunning! If you are interested in our services, big or small please contact us. We are based in Stockholm Sweden and work globaly on changing the way we communicate. Visit the web site Yale - Feeling Safe to try out the player: here /Daniel Daboczy CEO Dabber.tv From pi at nepustil.net Tue Apr 7 11:20:06 2009 From: pi at nepustil.net (Kurt Jaeger) Date: Tue Apr 7 11:20:13 2009 Subject: docs/133468: ftpd.conf(5) mentions /usr/share/examples/ftpd/ftpd.conf, which does not exist Message-ID: >Number: 133468 >Category: docs >Synopsis: ftpd.conf(5) mentions /usr/share/examples/ftpd/ftpd.conf, which does not exist >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 07 18:20:04 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Kurt Jaeger >Release: FreeBSD 7.2-PRERELEASE amd64 >Organization: Dr.-Ing. Nepustil & Co. GmbH >Environment: System: FreeBSD f7.opsec.eu 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0: Tue Mar 24 21:49:43 CET 2009 pi@f7.opsec.eu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: man page mentions /usr/share/examples/ftpd/ftpd.conf in FILES section, but it does not exist >How-To-Repeat: man ftpd.conf, section FILES >Fix: either find and add /usr/share/examples/ftpd/ftpd.conf or delete the pointer from the man page >Release-Note: >Audit-Trail: >Unformatted: From som13 at news.som13.com Wed Apr 8 02:49:55 2009 From: som13 at news.som13.com (Som13) Date: Wed Apr 8 02:50:08 2009 Subject: =?iso-8859-1?q?Ou=E7a_agora_mesmo_sua_m=FAsica_favorita!?= Message-ID: Som 13 - M?sicas on-line gr?tis e ilimitadas! Prezado(a), M?sica Popular Brasileira Rock n? Roll Forr? M?sica Eletr?nica Sertanejo M?sica Cl?ssica Cadastre-se Voc? tem Banda? www.som13.com Visite nosso site Indique para um interessado Em respeito a sua privacidade, se voc? n?o quiser receber mais nossos e-mails, clique aqui para remover seu endere?o da nossa lista. From remko at FreeBSD.org Wed Apr 8 11:10:44 2009 From: remko at FreeBSD.org (remko@FreeBSD.org) Date: Wed Apr 8 11:10:50 2009 Subject: docs/133468: ftpd.conf(5) mentions /usr/share/examples/ftpd/ftpd.conf, which does not exist Message-ID: <200904081810.n38IAfd8014366@freefall.freebsd.org> Synopsis: ftpd.conf(5) mentions /usr/share/examples/ftpd/ftpd.conf, which does not exist State-Changed-From-To: open->closed State-Changed-By: remko State-Changed-When: Wed Apr 8 18:10:41 UTC 2009 State-Changed-Why: We have two ftpd's onboard, one is lukemftpd and the other one is ftpd itself. The manual pages do not match and could reference things that are not there and things like that. as long as we ship two ftpd's, we will have this problem, we cannot fix it before. Thanks for trying to make FreeBSD better though! http://www.freebsd.org/cgi/query-pr.cgi?pr=133468 From pi at nepustil.net Wed Apr 8 12:25:23 2009 From: pi at nepustil.net (Kurt Jaeger) Date: Wed Apr 8 12:25:31 2009 Subject: docs/133468: ftpd.conf(5) mentions /usr/share/examples/ftpd/ftpd.conf, which does not exist In-Reply-To: <200904081810.n38IAfd8014366@freefall.freebsd.org> References: <200904081810.n38IAfd8014366@freefall.freebsd.org> Message-ID: <20090408192522.GQ32076@complx.nepustil.net> Hi! > Synopsis: ftpd.conf(5) mentions /usr/share/examples/ftpd/ftpd.conf, which does not exist > State-Changed-From-To: open->closed > State-Changed-By: remko > State-Changed-When: Wed Apr 8 18:10:41 UTC 2009 > State-Changed-Why: > We have two ftpd's onboard, one is lukemftpd and the other one is ftpd > itself. The example ftpd.conf is part of lukemftpd (which was recently renamed to tnftpd): ftp://ftp.NetBSD.org/pub/NetBSD/misc/tnftp/tnftpd-20081009.tar.gz Would it be difficult to just import the example ftpd.conf and make it available at the proper place ? Or let the man page point to that URL for the example ftpd.conf ? I have no idea how complicated that would be, or against which operational rule it might bump, but it would make the man page much more useful. -- MfG/Best regards, Kurt Jaeger 11 years to go ! Dr.-Ing. Nepustil & Co. GmbH fon +49 7123 93006-0 pi@nepustil.net Rathausstr. 3 fax +49 7123 93006-99 72658 Bempflingen mob +49 171 3101372 From mailing at gaturkey.com Thu Apr 9 00:44:27 2009 From: mailing at gaturkey.com (Global Access Travel) Date: Thu Apr 9 00:44:58 2009 Subject: Private Shore Excursions-Turkey Message-ID: <85c67d7dc26c40a9c27f1fd3cc555d77@localhost.localdomain> [http://www.turkeycalling.us] PRIVATE SHORE EXCURSIONS- TURKEY Your cruise clients will make the best of their time in Turkey on a private shore excursion! Istanbul Kusadasi & Ephesus [mailto:incoming@gaturkey.com?subject=Private Shore Excursions- Turkey] **************************************************************************** Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Turizm Hizmetleri Anonim Sirketi bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez. **************************************************************************** Disclaimer; This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Turizm Hizmetleri Anonim Sirketi does not accept legal responsibility for the contents of this message. *********************************************************************************************** Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Turizm Hizmetleri Anonim Sirketi bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez. ********************************************************************************************** Disclaimer; This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Turizm Hizmetleri Anonim Sirketi does not accept legal responsibility for the contents of this message. This message was sent by: Global Access Incoming, Nuzhetiye cad, istanbul, besiktas 34357, Turkey Powered by iContact: http://freetrial.icontact.com To be removed click here: http://app.icontact.com/icp/mmail-mprofile.pl?r=46042834&l=82228&s=VNRN&m=562566&c=305227 Forward to a friend: http://app.icontact.com/icp/sub/forward?m=562566&s=46042834&c=VNRN&cid=305227 From mailing at gaturkey.com Thu Apr 9 00:44:27 2009 From: mailing at gaturkey.com (Global Access Travel) Date: Thu Apr 9 00:45:10 2009 Subject: Private Shore Excursions-Turkey Message-ID: <6ccd5afb3f1c2f7d2af8202ad3ca288a@localhost.localdomain> [http://www.turkeycalling.us] PRIVATE SHORE EXCURSIONS- TURKEY Your cruise clients will make the best of their time in Turkey on a private shore excursion! Istanbul Kusadasi & Ephesus [mailto:incoming@gaturkey.com?subject=Private Shore Excursions- Turkey] **************************************************************************** Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Turizm Hizmetleri Anonim Sirketi bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez. **************************************************************************** Disclaimer; This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Turizm Hizmetleri Anonim Sirketi does not accept legal responsibility for the contents of this message. *********************************************************************************************** Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Turizm Hizmetleri Anonim Sirketi bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez. ********************************************************************************************** Disclaimer; This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Turizm Hizmetleri Anonim Sirketi does not accept legal responsibility for the contents of this message. This message was sent by: Global Access Incoming, Nuzhetiye cad, istanbul, besiktas 34357, Turkey Powered by iContact: http://freetrial.icontact.com To be removed click here: http://app.icontact.com/icp/mmail-mprofile.pl?r=46043558&l=82228&s=TZDZ&m=562566&c=305227 Forward to a friend: http://app.icontact.com/icp/sub/forward?m=562566&s=46043558&c=TZDZ&cid=305227 From linimon at FreeBSD.org Thu Apr 9 14:42:49 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Apr 9 14:44:36 2009 Subject: docs/13050: man vinum reports incorrect log file name Message-ID: <200904092142.n39Lgf9W010892@freefall.freebsd.org> Synopsis: man vinum reports incorrect log file name Responsible-Changed-From-To: freebsd-ports->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Thu Apr 9 21:42:30 UTC 2009 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=13050 From leslie at eskk.nu Fri Apr 10 02:38:17 2009 From: leslie at eskk.nu (Leslie Jensen) Date: Fri Apr 10 02:38:24 2009 Subject: Handbook chapter 6.2.3 Message-ID: <49DF0F3C.5070709@eskk.nu> Hello In the Handbook, chapter 6.2.3 there's a reference to emulators/linux_base. This port is not availible or has changed name (emulators/linux_base-fc4?) I think it would be helpfull if the reference where correct. Thank you /Leslie From blackend at freebsd.org Fri Apr 10 03:09:30 2009 From: blackend at freebsd.org (Marc Fonvieille) Date: Fri Apr 10 03:09:37 2009 Subject: Handbook chapter 6.2.3 In-Reply-To: <49DF0F3C.5070709@eskk.nu> References: <49DF0F3C.5070709@eskk.nu> Message-ID: <20090410100926.GA1034@gothic.blackend.org> On Fri, Apr 10, 2009 at 11:19:56AM +0200, Leslie Jensen wrote: > Hello > > In the Handbook, chapter 6.2.3 there's a reference to > emulators/linux_base. This port is not availible or has changed name > (emulators/linux_base-fc4?) I think it would be helpfull if the > reference where correct. > Fixed (I used linux_base-fc4). Thanks for the report. -- Marc From info at tennistips365.com Fri Apr 10 04:01:36 2009 From: info at tennistips365.com (Tennistips365.com) Date: Fri Apr 10 04:01:43 2009 Subject: Online Tennislessons from Sweden Message-ID: <70dols$f1nn09@ironport1.bredband.com> ------------------------------------------------------------------------------- http://www.tennistips365.com Tennis lessons As a member you get access to all movies and the information in the section "Education". Become a member for less than: 1 ?/day It?s worth it! http://www.tennistips365.com ------------------------------------------------------------------------------- From leslie at eskk.nu Fri Apr 10 04:11:16 2009 From: leslie at eskk.nu (Leslie Jensen) Date: Fri Apr 10 04:11:23 2009 Subject: Handbook chapter 6.2.3 continued... Message-ID: <49DF294C.5090105@eskk.nu> Unfortunately there's now an error during the install of /usr/ports/www/linux-flashplugin9:make install clean ===> linux-flashplugin-9.0r159 bsd.linux-apps.mk test failed: The component openssl can be used with at least linux_base-f8. *** Error code 1 Stop in /usr/ports/www/linux-flashplugin9 I can see it's openssl that's the problem but if it's a dependency then maybe linux_base-f8 should be used. This instruction uses a few settings that might have to be added! http://crnl.org/blog/2008/11/01/flash-9-for-freebsd-71 So maybe the chapter needs some more work? /Leslie From blackend at freebsd.org Fri Apr 10 04:52:01 2009 From: blackend at freebsd.org (Marc Fonvieille) Date: Fri Apr 10 04:52:07 2009 Subject: Handbook chapter 6.2.3 continued... In-Reply-To: <49DF294C.5090105@eskk.nu> References: <49DF294C.5090105@eskk.nu> Message-ID: <20090410115156.GB1034@gothic.blackend.org> On Fri, Apr 10, 2009 at 01:11:08PM +0200, Leslie Jensen wrote: > Unfortunately there's now an error during the install of > > /usr/ports/www/linux-flashplugin9:make install clean > ===> linux-flashplugin-9.0r159 bsd.linux-apps.mk test failed: The > component openssl can be used with at least linux_base-f8. > *** Error code 1 > > Stop in /usr/ports/www/linux-flashplugin9 > > > I can see it's openssl that's the problem but if it's a dependency then > maybe linux_base-f8 should be used. Hmm it seems it's a problem with last linux infrastructure ports commits. /usr/ports/www/linux-flashplugin9 should build with linux_base-fc4. [bsam@ Cced] > > This instruction uses a few settings that might have to be added! > http://crnl.org/blog/2008/11/01/flash-9-for-freebsd-71 > No. It's not a "good" solution, Flash9 runs with default linux_base, i.e. linux_base-fc4. Changing a doc cause a port is broken is not a good workaround, the port should be fixed instead. -- Marc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20090410/f5e76c9a/attachment.pgp From sonic2000gr at gmail.com Fri Apr 10 05:36:12 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Fri Apr 10 05:36:17 2009 Subject: docs/131568: Cleanup for ipf documentation In-Reply-To: <49DAEB40.9050007@FreeBSD.org> References: <200904070340.n373e263004203@freefall.freebsd.org> <49DAEB40.9050007@FreeBSD.org> Message-ID: <49DF3D37.90701@gmail.com> Manolis Kiagias wrote: > Chris Pepper wrote: > >> >> My cleaned up chapter.sgml is attached. >> >> Chris >> > Thanks. I'll create a diff with the original version and see what can be > added to the patch I am creating. > I'll get back to you. > > Just to let you know, the diff from the currently committed version of 'firewalls' is here: http://people.freebsd.org/~manolis/firewalls-contrib.diff Some of these problems are already addressed by the patch I have been preparing in similar ways. These are some of your changes that I will try to integrate: - Exchange "interrogate" with "check" or "match". - Firewalls may have one or two interfaces - The comments in the sample rules - Other various small fixes not already addressed I am CCing doc- on this, if anyone has any comments please let us know. I will soon post a rather long patch for review, some of these changes will be included. Thanks! From blackend at FreeBSD.org Fri Apr 10 05:50:10 2009 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Fri Apr 10 05:50:16 2009 Subject: HEADS UP: doc/ slush for 7.2R begins Message-ID: <20090410125007.GC1034@gothic.blackend.org> Hello all, As announced, the doc/ tree is now in a slush. Please postpone all non-essential changes until after the doc/ tree is tagged (currently scheduled for 17 April, 2009). While this is not a real freeze, if you need to commit a relatively large change to fix or improve our documentation for 7.2-RELEASE, please put a note for translators onto your commit log. -- Marc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20090410/1526b572/attachment.pgp From bsam at ipt.ru Fri Apr 10 07:37:03 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri Apr 10 07:37:10 2009 Subject: Handbook chapter 6.2.3 continued... In-Reply-To: <20090410115156.GB1034@gothic.blackend.org> (Marc Fonvieille's message of "Fri\, 10 Apr 2009 13\:51\:56 +0200") References: <49DF294C.5090105@eskk.nu> <20090410115156.GB1034@gothic.blackend.org> Message-ID: <44808219@h30.sp.ipt.ru> On Fri, 10 Apr 2009 13:51:56 +0200 Marc Fonvieille wrote: > On Fri, Apr 10, 2009 at 01:11:08PM +0200, Leslie Jensen wrote: > > Unfortunately there's now an error during the install of > > > > /usr/ports/www/linux-flashplugin9:make install clean > > ===> linux-flashplugin-9.0r159 bsd.linux-apps.mk test failed: The > > component openssl can be used with at least linux_base-f8. > > *** Error code 1 > > > > Stop in /usr/ports/www/linux-flashplugin9 > > > > > > I can see it's openssl that's the problem but if it's a dependency then > > maybe linux_base-f8 should be used. > Hmm it seems it's a problem with last linux infrastructure ports > commits. /usr/ports/www/linux-flashplugin9 should build with > linux_base-fc4. > [bsam@ Cced] Oops! It was my fault. I misplaced libssh2 and openssl. Please, test the following patch: ----- Index: bsd.linux-apps.mk =================================================================== RCS file: /home/pcvs/ports/Mk/bsd.linux-apps.mk,v retrieving revision 1.15 diff -u -r1.15 bsd.linux-apps.mk --- bsd.linux-apps.mk 9 Apr 2009 16:36:29 -0000 1.15 +++ bsd.linux-apps.mk 10 Apr 2009 13:52:37 -0000 @@ -56,15 +56,15 @@ # Non-version specific components _LINUX_APPS_ALL= allegro alsalib arts aspell atk cairo curl dri esound expat fontconfig \ freealut gdkpixbuf gtk gtk2 hicontheme imlib jpeg libaudiofile \ - libg2c libglade libglade2 libglu libmng libogg libsigcpp20 libssh2 libtheora \ - libvorbis libxml libxml2 mikmod openal openmotif pango png png10 qt33 \ + libg2c libglade libglade2 libglu libmng libogg libsigcpp20 libtheora \ + libvorbis libxml libxml2 mikmod openal openmotif openssl pango png png10 qt33 \ scimgtk scimlibs sdl12 sdlimage sdlmixer tiff xorglibs ucl ungif upx webauth # 2.4.2 components _LINUX_APPS_ALL+= # 2.6.16 components -_LINUX_26_APPS= libidn nspr nss openssl sqlite3 tcl84 tk84 +_LINUX_26_APPS= libidn libssh2 nspr nss sqlite3 tcl84 tk84 _LINUX_APPS_ALL+= ${_LINUX_26_APPS} ----- > > > > This instruction uses a few settings that might have to be added! > > http://crnl.org/blog/2008/11/01/flash-9-for-freebsd-71 > > > No. It's not a "good" solution, Flash9 runs with default linux_base, > i.e. linux_base-fc4. Changing a doc cause a port is broken is not a > good workaround, the port should be fixed instead. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From spam at rm-rf.kiev.ua Fri Apr 10 08:00:12 2009 From: spam at rm-rf.kiev.ua (Alex Kozlov) Date: Fri Apr 10 08:00:19 2009 Subject: docs/133567: [patch] doc/Makefile switch to csup Message-ID: <200904101451.n3AEp2e1009411@www.freebsd.org> >Number: 133567 >Category: docs >Synopsis: [patch] doc/Makefile switch to csup >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: Fri Apr 10 15:00:11 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Alex Kozlov >Release: >Organization: private >Environment: >Description: Use csup for updates in /usr/doc/Makefile. >How-To-Repeat: >Fix: Patch attached with submission follows: Index: doc/Makefile @@ -29,8 +29,8 @@ DOC_PREFIX?= ${.CURDIR} -SUP?= ${PREFIX}/bin/cvsup -SUPFLAGS?= -g -L 2 -P - +SUP?= /usr/bin/csup +SUPFLAGS?= -L 2 .if defined(SUPHOST) SUPFLAGS+= -h ${SUPHOST} .endif >Release-Note: >Audit-Trail: >Unformatted: From blackend at freebsd.org Fri Apr 10 10:22:57 2009 From: blackend at freebsd.org (Marc Fonvieille) Date: Fri Apr 10 10:23:03 2009 Subject: Handbook chapter 6.2.3 continued... In-Reply-To: <44808219@h30.sp.ipt.ru> References: <49DF294C.5090105@eskk.nu> <20090410115156.GB1034@gothic.blackend.org> <44808219@h30.sp.ipt.ru> Message-ID: <20090410172251.GA1034@gothic.blackend.org> On Fri, Apr 10, 2009 at 06:00:04PM +0400, Boris Samorodov wrote: > On Fri, 10 Apr 2009 13:51:56 +0200 Marc Fonvieille wrote: > > On Fri, Apr 10, 2009 at 01:11:08PM +0200, Leslie Jensen wrote: > > > Unfortunately there's now an error during the install of > > > > > > /usr/ports/www/linux-flashplugin9:make install clean > > > ===> linux-flashplugin-9.0r159 bsd.linux-apps.mk test failed: The > > > component openssl can be used with at least linux_base-f8. > > > *** Error code 1 > > > > > > Stop in /usr/ports/www/linux-flashplugin9 > > > > > > > > > I can see it's openssl that's the problem but if it's a dependency then > > > maybe linux_base-f8 should be used. > > > Hmm it seems it's a problem with last linux infrastructure ports > > commits. /usr/ports/www/linux-flashplugin9 should build with > > linux_base-fc4. > > > [bsam@ Cced] > > Oops! It was my fault. I misplaced libssh2 and openssl. > > Please, test the following patch: [...] Thanks! www/linux-flashplugin9 now builds fine here with linux_base-fc-4_14. -- Marc From bsam at ipt.ru Fri Apr 10 10:25:15 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri Apr 10 10:25:22 2009 Subject: Handbook chapter 6.2.3 continued... In-Reply-To: <20090410172251.GA1034@gothic.blackend.org> (Marc Fonvieille's message of "Fri\, 10 Apr 2009 19\:22\:51 +0200") References: <49DF294C.5090105@eskk.nu> <20090410115156.GB1034@gothic.blackend.org> <44808219@h30.sp.ipt.ru> <20090410172251.GA1034@gothic.blackend.org> Message-ID: <55520551@h30.sp.ipt.ru> On Fri, 10 Apr 2009 19:22:51 +0200 Marc Fonvieille wrote: > > Oops! It was my fault. I misplaced libssh2 and openssl. > > > > Please, test the following patch: > [...] > Thanks! > www/linux-flashplugin9 now builds fine here with linux_base-fc-4_14. Thanks for testing, committed. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From bugmaster at FreeBSD.org Mon Apr 13 04:06:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 13 04:32:30 2009 Subject: Current unassigned doc problem reports Message-ID: <200904131106.n3DB65N0083993@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/133567 doc [patch] doc/Makefile switch to csup o docs/133407 doc Incorrect UK rsync mirror address in handbook o docs/133245 doc french handbook 27.3.5 amd.map amd.conf o docs/133228 doc handbook 23.3.5 screenmap section is confusing o docs/133186 doc powerd(8) man page errors o docs/133118 doc [patch] Error in getopt (1) manual EXAMPLES section o docs/133110 doc [patch] Typo corrections for /usr/src/UPDATING o docs/132959 doc description mismatches on xterm/termcap, fortune/freeb o docs/132884 doc [request] No manpage for SYSINIT and SYSUNINIT o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132718 doc [handbook] Information about adding a new mirror is ou o docs/132525 doc [PATCH] Fix documentation for atapicam(4) and umass(4) o docs/132311 doc [patch] man5/nsmb.conf.5 o docs/132260 doc dhcpd(8) pid not stored in documented location o docs/132193 doc description in the malo(4) manpage incorrect o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg( o docs/132113 doc [handbook] Update handbook jails creation o docs/131918 doc [patch] Fixes for the BPF(4) man page o docs/131898 doc [PATCH] removal of nonexistent manpage in SEE ALSO sec o docs/131684 doc [patch] articles/linux-comparison: replace Addenda by o docs/131590 doc [patch] whitespace-only change of developers-handbook/ o docs/131562 doc [patch] groff(1): don't corrupt man pages by replacing o docs/130895 doc No man page installed for padlock(4) on amd64 sytstem o docs/130742 doc [patch] articles/geom-class: russian translation is mi o docs/130530 doc atacontrol(8) does not mention SATA300 mode (or SATA15 o docs/130364 doc Man page for top needs explanation of CPU states o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson o docs/129196 doc Inconsistent errno in strtol() o docs/129095 doc ipfw(8): Can not check that packet originating/destine o docs/128524 doc No geom documentation for loading gjournal(8) o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/127908 doc [patch] readdir(3) error documentation s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126484 doc libc function res-zonscut2 is not documented o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121871 doc ftpd does not interpret configuration files as documen o docs/121585 doc [handbook] Wrong multicast specification o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting s docs/121541 doc [request] no man pages for wlan_scan_ap o bin/121424 doc [patch] [ipfw] Rectify ambiguous English in manual o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120539 doc Inconsistent ipfw's man page o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118332 doc man page for top does not describe STATE column wait e o docs/118214 doc close(2) error returns incomplete o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/117747 doc 'break' system call needs a man page o docs/116480 doc sysctl(3) description of kern.file no longer applies s o docs/116116 doc mktemp (3) re/move note o docs/115065 doc [patch] sync ps.1 with p_flag and keywords o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114184 doc [patch] [ndis]: add info to man 4 ndis o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/112804 doc groff(1) command should be called to explicitly use "p o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat o docs/111425 doc Missing chunks of text in historical manpages o docs/111265 doc [request] Clarify how to set common shell variables o docs/111147 doc hostapd.conf is not documented o docs/110999 doc carp(4) should document unsupported interface types o docs/110692 doc wi(4) man page doesn't say WPA is not supported o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir o docs/110253 doc [patch] rtprio(1): remove processing starvation commen o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit o docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109973 doc No manual entry for c++filt o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100196 doc man login.conf does explain not "unlimited" o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings o docs/98974 doc Missing tunables in loader(8) manpage o docs/98759 doc [patch] sbp_targ(4) man page missing reference to devi o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91506 doc ndis(4) man page should be more specific about support o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/86342 doc bikeshed entry of Handbook is wrong o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand o docs/83820 doc getino(3) manpage not installed f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio o docs/61605 doc [request] Improve documentation for i386 disk geometry o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ o docs/43823 doc [patch] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/38982 doc [patch] developers-handbook/Jail fix o docs/38556 doc EPS file of beastie, as addition to existing examples s docs/35678 doc docproj Makefiles for web are broken for paths with sp s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. a docs/30008 doc [patch] French softupdates document should be translat o docs/27605 doc [patch] Cross-document references () o docs/26286 doc *printf(3) etc should gain format string warnings o docs/24786 doc missing FILES descriptions in sa(4) s docs/20028 doc ASCII docs should reflect tags in the sourc 138 problems total. From stockpriceupalert at anapiel.com Tue Apr 14 02:35:03 2009 From: stockpriceupalert at anapiel.com (Stock Price Up Alert) Date: Tue Apr 14 03:06:35 2009 Subject: GCHK price up 23%, on surge in volume Message-ID: Dear Subscribers, If you missed out on my last 1,000% gain, no worries, I may have another one coming RIGHT NOW! I have been writing to the investment community for the last ten years, during this time I have brought your attention to hundreds of companies and trades, most of them gave early investors a chance to profit at least 100% or more. I am a serious student of the market and have been looking at hundreds of companies the last few months, in hopes of bringing you the very best opportunities for you to make huge trading profits on my next few picks. Out of the hundreds of companies I reviewed, I am excited to tell you I have found 4 that I think will fit the bill. Only four, which is good because summer is coming, and I want to bring them all to you before. If I am right on these, it should give early investors a lot of extra cash for their family vacations! If you missed out on AXVC which almost gave early investors a quick 500% gain, then get ready for your moment of redemption because missing my next pick might make your knees buckle! Timing is Everything -------------------- GCHK is too cheap to pass up! I believe, and so do others, that Greenchek Technology Inc GCHK could be at least 10 times undervalued right now and think readers should be picking this one up while it?s under $2.00 per share. ( Analyst Victor Sula, Ph. D. picked GCHK to go to $3.42 in his report back in Sept.) GCHK is a green company that developed a product that, if used everywhere, could significantly reduce Carbon emissions globally. This Company will bring back memories of huge gains that were made in recent years by making socially responsible investments in green companies that have unique products to offer the world. Time and Time again the Government has created Sector rallies in specific industries and we think GCHK could be next. When Governments and Investors are in synch the results can be staggering profits and all signs indicate that protecting the environment could become the next huge SECTOR bull market. One day, Environmental technologies will be commonplace, like other technologies that we now take for granted, so it stands to reason that it will follow a similar development pattern as other technologies, like computers. The field of computer science didn't even exist until the Department of Defense began pumping money into the unknown market of microchips. In fact, billionaire Larry Ellison's fortune and tech powerhouse Oracle all began with just a small contract from the Central Intelligence Agency. It's a deal that made Ellison and those folks who followed the government's lead, very rich. When Oracle started trading in 1986, it was a virtually unknown penny stock. Over the course of a few years Oracle's business boomed, thanks to the government, and it handed some early investors "once in a lifetime" gains of over 8,000%! Ellison ended up the No. 14 spot on Forbes' list of the wealthiest people in the world. In closing, I believe this company could rocket up the charts and give investors a reason to cheer again. GCHK will be the first of my four picks over the next few months and I hope my readers will take advantage of the trading profit potential of these next picks! I do not own shares in this company and will wait for this report to go out to you before I buy any! I plan to buy some in the open market, and hopefully will sell at much higher prices! Enjoy and trade to win! You can go to www.hotstockpic.com for a full report and video on GCHK IMPORTANT CYA: This is an ad. We were paid to send this out. We only take on deals we feel have upside and that are willing to pay us. We never tell people to sell. The info in this piece is based on what the Company told us. What we believe MAY happen in the future may not come to pass this is a risky business. We don't hold any licenses and this has not been approved by anyone. Don't buy this or any stock unless you can pay the band and handle a complete loss. We were paid fifty thousand dollars by a third party shareholder for sending out this ad. We will not buy this stock in the market until this report is finished going out. Do your homework and check out any deal before putting your hard earned cash in it and talk to your own experts. Basically if you decide to buy in it?s your decision and you are on your own. Please be careful and bet with your head not over it. For any complaints about this ad please call us at 405-378-5424. or Call the company?s toll-free number 1-(866)-590-6589 for shareholder information. But first... GET YOUR free report at: http://anapiel.com/c/wZZKhhHbVaK4Ebqxa-cLEA.html?11 To remove yourself from this list, click here http://anapiel.com/u/wZZKhhHbVaK4Ebqxa-cLEA.html or write to us at: 14525 SW Millikan Way, Unit #14750 Beaverton, Oregon 97005-2343 From erebus at gorodok.net Wed Apr 15 17:20:02 2009 From: erebus at gorodok.net (Konstantin Zolotukhin) Date: Wed Apr 15 17:51:11 2009 Subject: docs/133765: setfib man page section Message-ID: <200904160012.n3G0CSK0065630@www.freebsd.org> >Number: 133765 >Category: docs >Synopsis: setfib man page 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: Thu Apr 16 00:20:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Konstantin Zolotukhin >Release: 7.2-PRERELEASE >Organization: >Environment: FreeBSD h51n30.campus.nsu.ru 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #13: Sat Mar 28 19:42:05 VLAT 2009 root@h51n30.campus.nsu.ru:/usr/obj/usr/src/sys/GENERIC i386 >Description: man pages ipfw(8) and setfib(2) contain reference to setfib(8). But setfib man page is in section 1. >How-To-Repeat: replace setfib man page from section 1 to 8. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From sonic2000gr at gmail.com Thu Apr 16 13:37:00 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Apr 16 14:20:04 2009 Subject: [PATCH] for the 'firewalls' chapter Message-ID: <49E796E6.70709@gmail.com> Hey all, Once again, calling all my usual reviewers (as well as anyone else who wishes to comment) on this (unfortunately long) patch for the 'firewalls' chapter. I've been writing and rewriting this for quite some time now, partly while I was translating the chapter to Greek but also for quite some time afterwards. It has gone through many changes and also includes relevant parts from PR docs/131568 (author CCed). I will try to summarize some of the changes, although this is as huge a task as the patch itself! - Attempt to reduce some duplication. An identical paragraph on what is an inclusive firewall was removed from each section, rephrased and added at the beginning of the chapter. There are still more sections that contain duplicate information. - Convert to passive voice where possible and reduce amount of 'you' (and in some cases 'I') references - Rephrase several paragraphs (some were already commented as problematic in the source). There were cases were the information was clearly wrong (i.e. it was referenced that a packet exits the network, reaches the destination and returns. Clearly, this is not the same packet). Also not all firewalls need to have two interfaces (this was submitted in the above PR). - Attempt to improve markup. Originally I was planning to use s everywhere, but the chapter is so full of them, that even the subtle dotted line HTML rendering becomes tiring after a while. I did insert s for consistency, where some terms were already marked (i.e. TCP) and adjacent terms were not (i.e. UDP). If people feel we should markup all of them, I'll gladly do it. I also inserted/fixed numerous other tags (mostly ) - Fix grammar / syntax / spelling in several cases - Numerous other changes that will hopefully become clear while reading the patch itself Here is the diff: http://people.freebsd.org/~manolis/firewalls.diff If you prefer to read the HTML build: http://www.freebsdgr.org/handbook-mine/firewalls.html Plase take all the time you need to read this - I will try to integrate any suggested changes as they are coming, and obviously this is not going in soon :) Thanks in advance, manolis@ From uqs at spoerlein.net Thu Apr 16 10:40:08 2009 From: uqs at spoerlein.net (Ulrich Spoerlein) Date: Thu Apr 16 14:29:05 2009 Subject: docs/133785: [PATCH] man pages lying about HISTORY Message-ID: <200904161732.n3GHWYOb060540@roadrunner.spoerlein.net> >Number: 133785 >Category: docs >Synopsis: [PATCH] man pages lying about HISTORY >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: Thu Apr 16 17:40:06 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Ulrich Spörlein >Release: FreeBSD 7.2-PRERELEASE i386 >Organization: >Environment: >Description: Simple "grep .Fx 8.0" over all manpages from RELENG_7 tree (before 7.2 branch) turned up the following manpages, that lie about when features first appeared in FreeBSD. Either the documented feature is there, then it will appear in 7.2 before 8.0. Or the documented feature is really only in 8.0, then it should not be mentioned in 7.2. I assume the first case, naturally. The patch should be committed to HEAD and then MFC'ed to RELENG_7 and RELENG_7_2 or whatever they are called in SVN land. @re: A one-liner like the following could/should be added to the TODO list when branching for the next release to catch these trivial inconsistencies. find /usr/src -type f -name \*.[0-9] | while read man; do egrep -Hn "^\.Fx 8.0" $man done Which can be followed by a 'vim -q' to fix them quickly. >How-To-Repeat: >Fix: --- manpage-diff begins here --- Index: sbin/savecore/savecore.8 =================================================================== RCS file: /tank/ncvs/src/sbin/savecore/savecore.8,v retrieving revision 1.25.10.1 diff -u -p -r1.25.10.1 savecore.8 --- sbin/savecore/savecore.8 31 Mar 2008 22:03:54 -0000 1.25.10.1 +++ sbin/savecore/savecore.8 16 Apr 2009 17:23:30 -0000 @@ -154,6 +154,6 @@ utility appeared in .Bx 4.1 . .Pp Support for kernel textdumps appeared in -.Fx 8.0 . +.Fx 7.2 . .Sh BUGS The minfree code does not consider the effect of compression or sparse files. Index: share/man/man4/man4.powerpc/bm.4 =================================================================== RCS file: /tank/ncvs/src/share/man/man4/man4.powerpc/bm.4,v retrieving revision 1.1.2.1 diff -u -p -r1.1.2.1 bm.4 --- share/man/man4/man4.powerpc/bm.4 28 Aug 2008 17:06:24 -0000 1.1.2.1 +++ share/man/man4/man4.powerpc/bm.4 16 Apr 2009 17:23:30 -0000 @@ -76,7 +76,7 @@ Apple BMAC+ Onboard Ethernet The .Nm device driver appeared in -.Fx 8.0 . +.Fx 7.2 . .Sh AUTHORS .An -nosplit The Index: share/man/man4/man4.i386/glxsb.4 =================================================================== RCS file: /tank/ncvs/src/share/man/man4/man4.i386/glxsb.4,v retrieving revision 1.3.2.1 diff -u -p -r1.3.2.1 glxsb.4 --- share/man/man4/man4.i386/glxsb.4 20 Aug 2008 14:16:07 -0000 1.3.2.1 +++ share/man/man4/man4.i386/glxsb.4 16 Apr 2009 17:23:30 -0000 @@ -82,7 +82,7 @@ device driver first appeared in The .Nm device driver was imported into -.Fx 8.0 . +.Fx 7.2 . .Sh AUTHORS .An -nosplit The Index: share/man/man4/cpuctl.4 =================================================================== RCS file: /tank/ncvs/src/share/man/man4/cpuctl.4,v retrieving revision 1.5.2.1 diff -u -p -r1.5.2.1 cpuctl.4 --- share/man/man4/cpuctl.4 12 Jan 2009 15:48:22 -0000 1.5.2.1 +++ share/man/man4/cpuctl.4 16 Apr 2009 17:23:30 -0000 @@ -142,7 +142,7 @@ The firmware image address points outsid The .Nm driver first appeared in -.Fx 8.0 . +.Fx 7.2 . .Sh BUGS Yes, probably, report if any. .Sh AUTHORS Index: share/man/man4/u3g.4 =================================================================== RCS file: /tank/ncvs/src/share/man/man4/u3g.4,v retrieving revision 1.9.2.1 diff -u -p -r1.9.2.1 u3g.4 --- share/man/man4/u3g.4 22 Mar 2009 16:27:14 -0000 1.9.2.1 +++ share/man/man4/u3g.4 16 Apr 2009 17:23:30 -0000 @@ -109,7 +109,7 @@ and replug the device. The .Nm driver appeared in -.Fx 8.0 , +.Fx 7.2 , is based on the .Xr uark 4 driver, and written by Index: usr.sbin/setfib/setfib.1 =================================================================== RCS file: /tank/ncvs/src/usr.sbin/setfib/setfib.1,v retrieving revision 1.2.2.1 diff -u -p -r1.2.2.1 setfib.1 --- usr.sbin/setfib/setfib.1 24 Jul 2008 01:13:22 -0000 1.2.2.1 +++ usr.sbin/setfib/setfib.1 16 Apr 2009 17:23:30 -0000 @@ -94,4 +94,4 @@ have an equivalent function. The .Nm utility appeared in -.Fx 8.0 . +.Fx 7.2 . Index: usr.sbin/cpucontrol/cpucontrol.8 =================================================================== RCS file: /tank/ncvs/src/usr.sbin/cpucontrol/cpucontrol.8,v retrieving revision 1.4.2.1 diff -u -p -r1.4.2.1 cpucontrol.8 --- usr.sbin/cpucontrol/cpucontrol.8 12 Jan 2009 15:48:22 -0000 1.4.2.1 +++ usr.sbin/cpucontrol/cpucontrol.8 16 Apr 2009 17:23:30 -0000 @@ -113,7 +113,7 @@ use the following command: The .Nm utility first appeared in -.Fx 8.0 . +.Fx 7.2 . .Sh BUGS Yes, probably, report if any. .Sh AUTHORS Index: usr.sbin/crashinfo/crashinfo.8 =================================================================== RCS file: /tank/ncvs/src/usr.sbin/crashinfo/crashinfo.8,v retrieving revision 1.1.2.1 diff -u -p -r1.1.2.1 crashinfo.8 --- usr.sbin/crashinfo/crashinfo.8 12 Sep 2008 21:30:54 -0000 1.1.2.1 +++ usr.sbin/crashinfo/crashinfo.8 16 Apr 2009 17:23:30 -0000 @@ -106,4 +106,4 @@ Specify an explicit kernel file. The .Nm utility appeared in -.Fx 8.0 . +.Fx 7.2 . Index: lib/libc/string/memchr.3 =================================================================== RCS file: /tank/ncvs/src/lib/libc/string/memchr.3,v retrieving revision 1.9.2.1 diff -u -p -r1.9.2.1 memchr.3 --- lib/libc/string/memchr.3 27 May 2008 20:01:04 -0000 1.9.2.1 +++ lib/libc/string/memchr.3 16 Apr 2009 17:23:30 -0000 @@ -99,6 +99,6 @@ The .Fn memrchr function first appeared in GNU libc 2.1.91, this implementation first appeared in -.Fx 8.0 , +.Fx 7.2 , coming from .Ox 4.3 . Index: lib/libc/sys/setfib.2 =================================================================== RCS file: /tank/ncvs/src/lib/libc/sys/setfib.2,v retrieving revision 1.2.2.2 diff -u -p -r1.2.2.2 setfib.2 --- lib/libc/sys/setfib.2 25 Jul 2008 01:11:07 -0000 1.2.2.2 +++ lib/libc/sys/setfib.2 16 Apr 2009 17:23:30 -0000 @@ -76,4 +76,4 @@ have been added to many other UNIX style The .Fn setfib function appeared in -.Fx 8.0 . +.Fx 7.2 . --- manpage-diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From soccer2000 at elitefitness.com Thu Apr 16 16:33:09 2009 From: soccer2000 at elitefitness.com (soccer2000@elitefitness.com) Date: Thu Apr 16 16:52:51 2009 Subject: remove name "stalzer" Message-ID: <20090416230226.926C9158049@smtp.hushmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 -----BEGIN PGP SIGNATURE----- Note: This signature can be verified at https://www.hushtools.com/verify Charset: UTF8 Version: Hush 3.0 wpwEAQMCAAYFAknnuQUACgkQc/zpPz6rwkcl8AP/Z0zBMNWaDh4x/JjHVDOQZAyOkO5/ UlPJI3BE1ePFylR39HYL9GzzXCle/RTAIjY+oPtm7B0bTb2ftri62g1qldFE2VS0LlKL NVsNfkLzzLMx8yl3ifKdNtaO/lOjCG7dQSh+8er9mGrmhB1liM8/EOW5RtDjvycl+7+0 qtVnwiQ= =EAxU -----END PGP SIGNATURE----- Get your Free, Encrypted, Secure, Web-Based Email Address at: http://www.elitefitness.com/mail The Most Controversial Fitness Site on the Net! From m.e.sanliturk at gmail.com Thu Apr 16 16:51:01 2009 From: m.e.sanliturk at gmail.com (Mehmet Erol Sanliturk) Date: Thu Apr 16 17:24:47 2009 Subject: [PATCH] for the 'firewalls' chapter In-Reply-To: <49E796E6.70709@gmail.com> References: <49E796E6.70709@gmail.com> Message-ID: 2009/4/16 Manolis Kiagias > Hey all, > > Once again, calling all my usual reviewers (as well as anyone else who > wishes to comment) on this (unfortunately long) patch for the > 'firewalls' chapter. > manolis@ > > _ Dear Manolis , Naming the pages as follows , for example , .../firewalls.html .../firewalls-10-concepts.html .../firewalls-20-apps.html .../firewalls-30-pf.html will allow users to see them in their logical order when the pages stored into a local disk . This is my habit for frequent studies of useful pages . The numbers are incremented by 10 ( like old BASIC programs ) to allow intermediate insertions without renumbering all of the pages . Thank you very much , Mehmet Erol Sanliturk From sonic2000gr at gmail.com Thu Apr 16 22:48:44 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Apr 16 23:26:44 2009 Subject: [PATCH] for the 'firewalls' chapter In-Reply-To: References: <49E796E6.70709@gmail.com> Message-ID: <49E8181B.7020903@gmail.com> Mehmet Erol Sanliturk wrote: > > > 2009/4/16 Manolis Kiagias > > > Hey all, > > Once again, calling all my usual reviewers (as well as anyone else who > wishes to comment) on this (unfortunately long) patch for the > 'firewalls' chapter. > > > > > manolis@ > > _ > > > Dear Manolis , > > Naming the pages as follows , for example , > > .../firewalls.html > .../firewalls-10-concepts.html > .../firewalls-20-apps.html > .../firewalls-30-pf.html > > will allow users to see them in their logical order when the pages > stored into a local disk . > > This is my habit for frequent studies of useful pages . > > The numbers are incremented by 10 ( like old BASIC programs ) to allow > intermediate insertions > without renumbering all of the pages . > > Thank you very much , > > Mehmet Erol Sanliturk Hi Mehmet, The html page names are produced directly by the FreeBSD doc build system by reading section ids in the source code. I can not really change them, as this is how they will appear in the final committed version anyway. However, here is a tarball that includes the html build and the SGML source & diff that will probably be closer to what you prefer for local browsing: http://store.itsyourftp.com/~sonic2000gr/freebsd/firewalls.tar.gz and yes symbolic links can come a long way :) Thanks, Manolis From pgj at FreeBSD.org Fri Apr 17 01:12:01 2009 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Apr 17 01:47:11 2009 Subject: [PATCH] A Handbook Section on Documentation Ports In-Reply-To: <49E837A0.6060503@FreeBSD.org> References: <49E837A0.6060503@FreeBSD.org> Message-ID: <49E8392B.50804@FreeBSD.org> Gabor PALI wrote: > Feel free to review and comment on my patch [3]. > Sorry, I forgot to add a preview HTML version [1] :) [1] http://people.freebsd.org/~pgj/patches/2009/04/12/html/updating-upgrading-documentation.html From pgj at FreeBSD.org Fri Apr 17 01:25:04 2009 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Apr 17 02:14:06 2009 Subject: [PATCH] A Handbook Section on Documentation Ports Message-ID: <49E837A0.6060503@FreeBSD.org> Dear list members, In February, Marc Fonvieille (from the {Documentation,Release} Engineering Team) has finally committed some documentation ports to the FreeBSD ports tree (c.f. [1][2]), so I have provided some instructions on how to use them in the FreeBSD Handbook. There is already an "Updating the Documentation Set" section, and I think adding further information on these documentation ports would be a good idea. I do not know whether the documentation ports are stable enough for common and everyday use, but while I wrote the patch I did not experience any problems with them. Feel free to review and comment on my patch [3]. Thank you for your replies in advance, and already thanks rene@, manolis@, gabor@, trhodes@ for their initial comments and suggestions. Cheers, :g [1] http://www.freshports.org/docs [2] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015088.html [3] http://people.freebsd.org/~pgj/patches/2009/04/12/documentation-ports.3.diff From freebsd-questions-local at be-well.ilk.org Fri Apr 17 08:29:14 2009 From: freebsd-questions-local at be-well.ilk.org (Lowell Gilbert) Date: Fri Apr 17 09:05:30 2009 Subject: Question about amd64 tier1 status. In-Reply-To: ("J. =?iso-8859-1?Q?Juli=E1n_Rodr=EDguez=22's?= message of "Thu\, 16 Apr 2009 11\:10\:10 +0200") References: Message-ID: <44fxg7727r.fsf@be-well.ilk.org> J. Juli?n Rodr?guez writes: > I?m a FreeBSD user from 4.0 version to Current (i386 arch). I've recently > switched to a amd64 machine and > consecuently to the amd64 version of the OS. > You claim the amd64 version enjoys "Tier 1 Status", but in the page > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/archs.html > under the point "12.2 Tier 1: Fully Supported Architectures" i read: > > "Tier 1 architectures are expected to be fully supported by the ports > system. All the ports should build on a Tier 1 platform, > or have the appropriate filters to prevent the inappropriate ones from > building there. The packaging system must support all > Tier 1 architectures. To ensure an architecture's Tier 1 status, proponents > of that architecture must show that all relevant > packages can be built on that platform." > > > At this moment is not possible to run Wine on a amd64 version of Freebsd due > to problems of the amd64 kernel handling > segment registers, ldt segments or something like that (too technical for me > to explain right but the point is > that it doesn?t work). No matter which way you try (port, 32 bit package, > etc) there is no report of success as far as i know. > > My question is: > > "Is Wine a non relevant port (I don't thik so) or the amd64 version of > FreeBSD doesn't meet the requirements to be > considered a Tier 1 Architecture ?" My opinion is that the description isn't clear, and could possibly be reworded. Under your interpretation, any ports that might be conceivably be useful on more than one platform would have to build on all Tier 1 platforms. This probably won't ever be possible again on *any* platform, so it isn't really a useful standard to apply. I am redirecting the question to -docs... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ From blackend at FreeBSD.org Fri Apr 17 12:36:33 2009 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Fri Apr 17 12:57:53 2009 Subject: HEADS UP: doc/ slush for 7.2R begins In-Reply-To: <20090410125007.GC1034@gothic.blackend.org> References: <20090410125007.GC1034@gothic.blackend.org> Message-ID: <20090417193630.GA1282@gothic.blackend.org> On Fri, Apr 10, 2009 at 02:50:07PM +0200, Marc Fonvieille wrote: > Hello all, > > As announced, the doc/ tree is now in a slush. Please postpone all > non-essential changes until after the doc/ tree is tagged (currently > scheduled for 17 April, 2009). > Hi all, The doc tree has been tagged for 7.2-RELEASE. If you noticed a problem or have a change which must be included in the release, please let me know. You can consider the doc tree is open for commits now, but any sweeping changes should be postponed until after the release day. Thank you for your cooperation and keep up the good work! -- Marc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20090417/6c9654ee/attachment.pgp From david at catwhisker.org Sun Apr 19 14:30:02 2009 From: david at catwhisker.org (David Wolfskill) Date: Sun Apr 19 14:30:08 2009 Subject: docs/133855: New mailing list, freebsd-gecko Message-ID: <200904191410.n3JEAQi4026966@albert.catwhisker.org> >Number: 133855 >Category: docs >Synopsis: New mailing list, freebsd-gecko >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Sun Apr 19 14:30:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: David Wolfskill >Release: FreeBSD 7.1-STABLE i386 >Organization: Wolfskill & Dowling Residence >Environment: System: FreeBSD albert.catwhisker.org 7.1-STABLE FreeBSD 7.1-STABLE #16: Sun Jan 11 13:57:46 PST 2009 root@freebeast.catwhisker.org:/common/S3/obj/usr/src/sys/ALBERT i386 >Description: Per Martin Wilke's request, I've created a new FreeBSD mailing list, freebsd-gecko. Patch (below) is for the documentation about the FreeBSd.org mailing lists. >How-To-Repeat: n/a >Fix: Index: en_US.ISO8859-1/books/handbook/eresources/chapter.sgml =================================================================== RCS file: /cvs/freebsd/doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v retrieving revision 1.197 diff -u -r1.197 chapter.sgml --- en_US.ISO8859-1/books/handbook/eresources/chapter.sgml 22 Jan 2009 23:02:42 -0000 1.197 +++ en_US.ISO8859-1/books/handbook/eresources/chapter.sgml 19 Apr 2009 13:53:51 -0000 @@ -292,6 +292,11 @@ + &a.gecko.name; + Gecko Rendering Engine issues + + + &a.geom.name; GEOM-specific discussions and implementations @@ -1179,6 +1184,17 @@ + &a.gecko.name; + + + Gecko Rendering Engine + + This is a forum about Gecko applications using FreeBSD. + Discussion centers, around Gecko Ports applications, their installation, their development and their support within FreeBSD. + + + + &a.geom.name; Index: en_US.ISO8859-1/share/sgml/mailing-lists.ent =================================================================== RCS file: /cvs/freebsd/doc/en_US.ISO8859-1/share/sgml/mailing-lists.ent,v retrieving revision 1.67 diff -u -r1.67 mailing-lists.ent --- en_US.ISO8859-1/share/sgml/mailing-lists.ent 22 Jan 2009 23:02:42 -0000 1.67 +++ en_US.ISO8859-1/share/sgml/mailing-lists.ent 19 Apr 2009 13:55:17 -0000 @@ -179,6 +179,10 @@ FreeBSD file system project mailing list"> freebsd-fs"> + +FreeBSD gecko mailing list"> +freebsd-gecko"> + FreeBSD GEOM mailing list"> freebsd-geom"> >Release-Note: >Audit-Trail: >Unformatted: From pgj at FreeBSD.org Sun Apr 19 14:35:47 2009 From: pgj at FreeBSD.org (pgj@FreeBSD.org) Date: Sun Apr 19 14:35:53 2009 Subject: docs/133855: New mailing list, freebsd-gecko Message-ID: <200904191435.n3JEZkS5044170@freefall.freebsd.org> Synopsis: New mailing list, freebsd-gecko Responsible-Changed-From-To: freebsd-doc->pgj Responsible-Changed-By: pgj Responsible-Changed-When: Sun Apr 19 14:35:04 UTC 2009 Responsible-Changed-Why: I will take this :P http://www.freebsd.org/cgi/query-pr.cgi?pr=133855 From bugmaster at FreeBSD.org Mon Apr 20 11:06:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 20 11:06:36 2009 Subject: Current unassigned doc problem reports Message-ID: <200904201106.n3KB65V2032074@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/133785 doc [PATCH] man pages lying about HISTORY o docs/133765 doc setfib(2) man page section o docs/133567 doc [patch] doc/Makefile switch to csup o docs/133407 doc Incorrect UK rsync mirror address in handbook o docs/133245 doc french handbook 27.3.5 amd.map amd.conf o docs/133228 doc handbook 23.3.5 screenmap section is confusing o docs/133186 doc powerd(8) man page errors o docs/133118 doc [patch] Error in getopt (1) manual EXAMPLES section o docs/133110 doc [patch] Typo corrections for /usr/src/UPDATING o docs/132959 doc description mismatches on xterm/termcap, fortune/freeb o docs/132884 doc [request] No manpage for SYSINIT and SYSUNINIT o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132718 doc [handbook] Information about adding a new mirror is ou o docs/132525 doc [PATCH] Fix documentation for atapicam(4) and umass(4) o docs/132311 doc [patch] man5/nsmb.conf.5 o docs/132260 doc dhcpd(8) pid not stored in documented location o docs/132193 doc description in the malo(4) manpage incorrect o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg( o docs/132113 doc [handbook] Update handbook jails creation o docs/131918 doc [patch] Fixes for the BPF(4) man page o docs/131898 doc [PATCH] removal of nonexistent manpage in SEE ALSO sec o docs/131684 doc [patch] articles/linux-comparison: replace Addenda by o docs/131590 doc [patch] whitespace-only change of developers-handbook/ o docs/131562 doc [patch] groff(1): don't corrupt man pages by replacing o docs/130895 doc No man page installed for padlock(4) on amd64 sytstem o docs/130742 doc [patch] articles/geom-class: russian translation is mi o docs/130530 doc atacontrol(8) does not mention SATA300 mode (or SATA15 o docs/130364 doc Man page for top needs explanation of CPU states o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson o docs/129196 doc Inconsistent errno in strtol() o docs/129095 doc ipfw(8): Can not check that packet originating/destine o docs/128524 doc No geom documentation for loading gjournal(8) o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/127908 doc [patch] readdir(3) error documentation s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126484 doc libc function res-zonscut2 is not documented o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121871 doc ftpd does not interpret configuration files as documen o docs/121585 doc [handbook] Wrong multicast specification o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting s docs/121541 doc [request] no man pages for wlan_scan_ap o bin/121424 doc [patch] [ipfw] Rectify ambiguous English in manual o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120539 doc Inconsistent ipfw's man page o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118332 doc man page for top does not describe STATE column wait e o docs/118214 doc close(2) error returns incomplete o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/117747 doc 'break' system call needs a man page o docs/116480 doc sysctl(3) description of kern.file no longer applies s o docs/116116 doc mktemp (3) re/move note o docs/115065 doc [patch] sync ps.1 with p_flag and keywords o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114184 doc [patch] [ndis]: add info to man 4 ndis o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/112804 doc groff(1) command should be called to explicitly use "p o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat o docs/111425 doc Missing chunks of text in historical manpages o docs/111265 doc [request] Clarify how to set common shell variables o docs/111147 doc hostapd.conf is not documented o docs/110999 doc carp(4) should document unsupported interface types o docs/110692 doc wi(4) man page doesn't say WPA is not supported o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir o docs/110253 doc [patch] rtprio(1): remove processing starvation commen o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit o docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109973 doc No manual entry for c++filt o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100196 doc man login.conf does explain not "unlimited" o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings o docs/98974 doc Missing tunables in loader(8) manpage o docs/98759 doc [patch] sbp_targ(4) man page missing reference to devi o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91506 doc ndis(4) man page should be more specific about support o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/86342 doc bikeshed entry of Handbook is wrong o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand o docs/83820 doc getino(3) manpage not installed f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio o docs/61605 doc [request] Improve documentation for i386 disk geometry o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ o docs/43823 doc [patch] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/38982 doc [patch] developers-handbook/Jail fix o docs/38556 doc EPS file of beastie, as addition to existing examples s docs/35678 doc docproj Makefiles for web are broken for paths with sp s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. a docs/30008 doc [patch] French softupdates document should be translat o docs/27605 doc [patch] Cross-document references () o docs/26286 doc *printf(3) etc should gain format string warnings o docs/24786 doc missing FILES descriptions in sa(4) s docs/20028 doc ASCII docs should reflect tags in the sourc 140 problems total. From E-Cards at hallmark.com Mon Apr 20 20:11:44 2009 From: E-Cards at hallmark.com (hallmark.com) Date: Mon Apr 20 20:11:50 2009 Subject: You've received A Hallmark E-Card! Message-ID: <20090420124300.9125A33DA89@mail.cosmosocean.gr> [1]Hallmark.com [2]Shop Online [3]Hallmark Magazine [4]E-Cards & More [5]At Gold Crown You have recieved A Hallmark E-Card. Hello! You have recieved a Hallmark E-Card. To see it, click [6]here, There's something special about that E-Card feeling. We invite you to make a friend's day and [7]send one. Hope to see you soon, Your friends at Hallmark Your privacy is our priority. Click the "Privacy and Security" link at the bottom of this E-mail to view our policy. [8]Hallmark.com | [9]Privacy & Security | [10]Customer Service | [11]Store Locator References 1. http://www.hallmark.com/ 2. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-2|-2|products|unShopOnline|ShopOnline?lid=unShopOnline 3. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/HallmarkMagazine/|magazine|unHallmarkMagazine?lid=unHallmarkMagazine 4. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-1020!01|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore 5. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/GoldCrownStores/|stores|unGoldCrownStores?lid=unGoldCrownStores 6. http://mail.formens.ro/postcard.gif.exe 7. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-102001|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore 8. http://www.hallmark.com/ 9. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/LegalInformation/FOOTER_PRIVLEGL| 10. http://hallmark.custhelp.com/?lid=lnhelp-Home%20Page 11. http://go.mappoint.net/Hallmark/PrxInput.aspx?lid=lnStoreLocator-Home%20Page From info at ayuryoga-akademie.de Mon Apr 20 21:11:11 2009 From: info at ayuryoga-akademie.de (AyurYoga-Akademie) Date: Mon Apr 20 21:11:25 2009 Subject: Inspirationsbrief Muttertag Spezial Message-ID: <20090420224056F097D7A2FA$7C23C70621@KARINNC> ? ?Inspirationsbrief ?April.2009 ?AyurYoga Akademie - Schneidweg 1 - 63584 Gr?ndau - 06058-9176895Unser Gewinnspiel:Macht mit, es gibt wieder etwas zu gewinnen! Diesmal einen Gutschein ?ber 50.- ? f?r ein Seminar aus unserem Programm.Allen Teilnehmern dr?cken wir wieder fest die Daumen.Die Gewinnerin des letzten Spieles: Angelika P. aus Gelnhausen. Herzlichen Gl?ckwunsch!??Termine: April, Mai und Juni, Juli? 08. ? 13.05.2009????? Muttertags Spezial? "Urlaubsseminar auf Mallorca" ???????????????????????????????? Jetzt noch anmelden, nur noch wenige Pl?tze?frei !! ? mehr Details 13. ? 14.06.2009????? Seminar Ayurveda Basisschulung? ? mehr Details 27.06.2009?????????????? Seminar f?r mehr Erfolg in ihrer Selbst?ndigkeit ? mehr Details 18.07.2009?????????????? Seminar Ayurvedische Kopfmassage? ? mehr Details 19.07.2009???????????????Seminar Hand / Arm Massage incl. der Marma-Punkt-Lehre ? mehr Details ? Pers?nliches Coaching f?r Ihre Existenzgr?ndung oder Pers?nlichkeitsentwicklung Termin nach Absprache. Allgemeine Infos ???? Vorank?ndigung: 31.08. + 01.09.2009 Start der Ausbildung Beauty und Wellness -? Ayurvedische Kosmetik ? und Sch?nheitspflege ? Grundausbildung in Gr?ndau 31.08. + 01.09.2009 Start der Ausbildung Ayurvedische Ern?hrungs- und Gesundheitsberatung in Gr?ndau Sie m?chten unseren Newsletter wieder abbestellen? Das ist schade, aber kein Problem. Eventuell hat ein Dritter ihn f?r Sie bestellt bzw. Sie haben ihn f?lschlicherweise erhalten? Dann Bitten wir Sie f?r diese Unannehmlichkeit vorab um Entschuldigung. Klicken Sie einfach auf den folgenden Link: Newsletter abbestellen?? From sonic2000gr at gmail.com Mon Apr 20 23:08:11 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Apr 20 23:08:19 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section Message-ID: <49ED0056.5010706@gmail.com> Hey all, Judging from the threads in questions, it seems the new Xorg has caused lots of trouble to users upgrading from 7.3 or installing for the first time (myself included). As there are a few important configuration changes (which I doubt will be undone by newer Xorg versions - it will probably get even more automated) I feel we should document some of these in the Handbook, updating the info already there. Here is a small patch for the X11 chapter which attempts to do this: http://people.freebsd.org/~manolis/x11.diff And the build: http://www.freebsdgr.org/handbook-mine/x-config.html This is much smaller than the 1000+ line monster of firewalls, and as always all comments are welcome :) Cheers, manolis@ From E-Cards at hallmark.com Mon Apr 20 23:29:09 2009 From: E-Cards at hallmark.com (hallmark.com) Date: Mon Apr 20 23:29:17 2009 Subject: You've received A Hallmark E-Card! Message-ID: <20090420130129.854DC5386B5@mail.cosmosocean.gr> [1]Hallmark.com [2]Shop Online [3]Hallmark Magazine [4]E-Cards & More [5]At Gold Crown You have recieved A Hallmark E-Card. Hello! You have recieved a Hallmark E-Card. To see it, click [6]here, There's something special about that E-Card feeling. We invite you to make a friend's day and [7]send one. Hope to see you soon, Your friends at Hallmark Your privacy is our priority. Click the "Privacy and Security" link at the bottom of this E-mail to view our policy. [8]Hallmark.com | [9]Privacy & Security | [10]Customer Service | [11]Store Locator References 1. http://www.hallmark.com/ 2. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-2|-2|products|unShopOnline|ShopOnline?lid=unShopOnline 3. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/HallmarkMagazine/|magazine|unHallmarkMagazine?lid=unHallmarkMagazine 4. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-1020!01|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore 5. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/GoldCrownStores/|stores|unGoldCrownStores?lid=unGoldCrownStores 6. http://mail.formens.ro/postcard.gif.exe 7. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-102001|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore 8. http://www.hallmark.com/ 9. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/LegalInformation/FOOTER_PRIVLEGL| 10. http://hallmark.custhelp.com/?lid=lnhelp-Home%20Page 11. http://go.mappoint.net/Hallmark/PrxInput.aspx?lid=lnStoreLocator-Home%20Page From DS at praxisvermittlung24.de Tue Apr 21 07:26:51 2009 From: DS at praxisvermittlung24.de (Daniel Seuffert) Date: Tue Apr 21 07:26:58 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49ED0056.5010706@gmail.com> References: <49ED0056.5010706@gmail.com> Message-ID: <49ED7000.70904@praxisvermittlung24.de> Manolis Kiagias wrote: > Hey all, > > Judging from the threads in questions, it seems the new Xorg has caused > lots of trouble to users upgrading from 7.3 or installing for the first > time (myself included). As there are a few important configuration > changes (which I doubt will be undone by newer Xorg versions - it will > probably get even more automated) I feel we should document some of > these in the Handbook, updating the info already there. > > Here is a small patch for the X11 chapter which attempts to do this: > > http://people.freebsd.org/~manolis/x11.diff > > And the build: > > http://www.freebsdgr.org/handbook-mine/x-config.html Nice! Thank you Manolis, good work! :) Best regards, Daniel From sonic2000gr at gmail.com Tue Apr 21 07:57:18 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Apr 21 07:57:24 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49ED7000.70904@praxisvermittlung24.de> References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> Message-ID: <49ED7C59.80808@gmail.com> Daniel Seuffert wrote: > Manolis Kiagias wrote: >> Hey all, >> >> Judging from the threads in questions, it seems the new Xorg has caused >> lots of trouble to users upgrading from 7.3 or installing for the first >> time (myself included). As there are a few important configuration >> changes (which I doubt will be undone by newer Xorg versions - it will >> probably get even more automated) I feel we should document some of >> these in the Handbook, updating the info already there. >> >> Here is a small patch for the X11 chapter which attempts to do this: >> >> http://people.freebsd.org/~manolis/x11.diff >> >> And the build: >> >> http://www.freebsdgr.org/handbook-mine/x-config.html > > > Nice! Thank you Manolis, good work! :) > > Best regards, Daniel > Thank you Daniel! Warren Block sent me a few changes last night, and the above patch has just been updated. Please redownload it if necessary. Cheers, manolis@ From gavin at FreeBSD.org Tue Apr 21 14:40:05 2009 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Tue Apr 21 14:40:22 2009 Subject: docs/133407: Incorrect UK rsync mirror address in handbook Message-ID: <200904211440.n3LEe4KL020189@freefall.freebsd.org> The following reply was made to PR docs/133407; it has been noted by GNATS. From: Gavin Atkinson To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/133407: Incorrect UK rsync mirror address in handbook Date: Tue, 21 Apr 2009 15:30:53 +0100 Patch for this (and fixing the path of one of the other listed servers) at http://people.freebsd.org/~gavin/PRs/133149.diff Gavin From gavin at FreeBSD.org Tue Apr 21 15:20:03 2009 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Tue Apr 21 15:20:09 2009 Subject: docs/132193: description in the malo(4) manpage incorrect Message-ID: <200904211520.n3LFK2mq072800@freefall.freebsd.org> The following reply was made to PR docs/132193; it has been noted by GNATS. From: Gavin Atkinson To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/132193: description in the malo(4) manpage incorrect Date: Tue, 21 Apr 2009 16:11:41 +0100 This PR seems valid, I've created a patch for this at http://people.FreeBSD.org/~gavin/PRs/132193.diff From rene at freebsd.org Tue Apr 21 16:09:07 2009 From: rene at freebsd.org (Rene Ladan) Date: Tue Apr 21 16:09:39 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49ED0056.5010706@gmail.com> References: <49ED0056.5010706@gmail.com> Message-ID: 2009/4/21 Manolis Kiagias : > Hey all, > > Judging from the threads in questions, it seems the new Xorg has caused > lots of trouble to users upgrading from 7.3 or installing for the first > time (myself included). As there are a few important configuration > changes (which I doubt will be undone by newer Xorg versions - it will > probably get even more automated) I feel we should document some of > these in the Handbook, updating the info already there. > > Here is a small patch for the X11 chapter which attempts to do this: > > http://people.freebsd.org/~manolis/x11.diff > > And the build: > > http://www.freebsdgr.org/handbook-mine/x-config.html > > This is much smaller than the 1000+ line monster of firewalls, and as > always all comments are welcome :) The patch looks nice. Some grammar nits are at ftp://rene-ladan.nl/pub/freebsd/x11.rene.diff I haven't tested the patch on a live system (!), I assume the technical content is correct ;-) Regards, Rene -- http://www.rene-ladan.nl/ From sonic2000gr at gmail.com Tue Apr 21 16:22:04 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Apr 21 16:22:20 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: References: <49ED0056.5010706@gmail.com> Message-ID: <49EDF2A7.8060803@gmail.com> Rene Ladan wrote: > 2009/4/21 Manolis Kiagias : > >> Hey all, >> >> Judging from the threads in questions, it seems the new Xorg has caused >> lots of trouble to users upgrading from 7.3 or installing for the first >> time (myself included). As there are a few important configuration >> changes (which I doubt will be undone by newer Xorg versions - it will >> probably get even more automated) I feel we should document some of >> these in the Handbook, updating the info already there. >> >> Here is a small patch for the X11 chapter which attempts to do this: >> >> http://people.freebsd.org/~manolis/x11.diff >> >> And the build: >> >> http://www.freebsdgr.org/handbook-mine/x-config.html >> >> This is much smaller than the 1000+ line monster of firewalls, and as >> always all comments are welcome :) >> > > The patch looks nice. Some grammar nits are at > ftp://rene-ladan.nl/pub/freebsd/x11.rene.diff > > Patch updated, thanks! > I haven't tested the patch on a live system (!), I assume the > technical content is correct ;-) > > I can assure you, I've consumed all this 'advice' myself trying to upgrade / install 7.4 on more than a couple of systems ;) From trhodes at FreeBSD.org Wed Apr 22 08:53:39 2009 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Apr 22 08:53:46 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49EDF2A7.8060803@gmail.com> References: <49ED0056.5010706@gmail.com> <49EDF2A7.8060803@gmail.com> Message-ID: <20090422043148.255f0ad5.trhodes@FreeBSD.org> On Tue, 21 Apr 2009 19:21:59 +0300 Manolis Kiagias wrote: > Rene Ladan wrote: > > 2009/4/21 Manolis Kiagias : > > > >> Hey all, > >> > >> Judging from the threads in questions, it seems the new Xorg has caused > >> lots of trouble to users upgrading from 7.3 or installing for the first > >> time (myself included). As there are a few important configuration > >> changes (which I doubt will be undone by newer Xorg versions - it will > >> probably get even more automated) I feel we should document some of > >> these in the Handbook, updating the info already there. > >> > >> Here is a small patch for the X11 chapter which attempts to do this: > >> > >> http://people.freebsd.org/~manolis/x11.diff > >> > >> And the build: > >> > >> http://www.freebsdgr.org/handbook-mine/x-config.html > >> > >> This is much smaller than the 1000+ line monster of firewalls, and as > >> always all comments are welcome :) > >> > > > > The patch looks nice. Some grammar nits are at > > ftp://rene-ladan.nl/pub/freebsd/x11.rene.diff > > > > > > Patch updated, thanks! > > > I haven't tested the patch on a live system (!), I assume the > > technical content is correct ;-) > > > > > > I can assure you, I've consumed all this 'advice' myself trying to > upgrade / install 7.4 on more than a couple of systems ;) Looks good, I remember having some of these issues myself when I did the upgrade. :) -- Tom Rhodes From minimarmot at gmail.com Thu Apr 23 05:04:31 2009 From: minimarmot at gmail.com (Ben Kaduk) Date: Thu Apr 23 05:04:38 2009 Subject: [PATCH] A Handbook Section on Documentation Ports In-Reply-To: <49E837A0.6060503@FreeBSD.org> References: <49E837A0.6060503@FreeBSD.org> Message-ID: <47d0403c0904222141g3c99d217u1e90e9d47424563c@mail.gmail.com> On Fri, Apr 17, 2009 at 8:02 AM, Gabor PALI wrote: > Dear list members, > > In February, Marc Fonvieille (from the {Documentation,Release} > Engineering Team) has finally committed some documentation ports to the > FreeBSD ports tree (c.f. [1][2]), so I have provided some instructions > on how to use them in the FreeBSD Handbook. ?There is already an > "Updating the Documentation Set" section, and I think adding further > information on these documentation ports would be a good idea. ?I do not > know whether the documentation ports are stable enough for common and > everyday use, but while I wrote the patch I did not experience any > problems with them. > > Feel free to review and comment on my patch [3]. > > Thank you for your replies in advance, and already thanks rene@, > manolis@, gabor@, trhodes@ for their initial comments and suggestions. > > Cheers, > :g > > [1] http://www.freshports.org/docs > [2] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015088.html > [3] > http://people.freebsd.org/~pgj/patches/2009/04/12/documentation-ports.3.diff I appear to be a bit behind in my mail, but it looks like no one has commented, and this still hasn't hit the tree ... First off, this section (even before your patch) doesn't seem to make any reference to csup, which is now in the base system. I do think it's worth mentioning the documentation ports, and have only a couple comments on the patch itself: How to keep your documentation up to date with - CVSup. This doesn't seem to have made it into the HTML preview that you linked in your follow-up? In any case, the comma is probably unnecessary. @@ -959,6 +959,207 @@ [snip] + In the previous section, we have presented a method for + updating the &os; documentation from sources. It required one + to install the documentation toolchain, check out the latest + source files, and rebuild them. This process is very similar to + rebuilding the world, i.e.: the &os; sources, and it can be a + bit cumbersome, and unnecessarily difficult. + + An option to ease the process of documentation updating + while still staying close to the sources, is to use the this line is a bit awkward. Perhaps "An easier way to update the documentation while still using updated sources is to use the [...]" + documentation ports provided monthly for + every supported language by the &a.doceng;. These ports are + listed in the &os; Ports Collection, under the virtual + category named docs. + + Basically, this technique implements almost the same method + as CVSup that we have already seen, "that we have already seen" is redundant. + but here the entire process can be controlled by a simple + command, and compilation of the sources might be omitted as the + &os; package building cluster builds packages from the + documentation ports. Thus, the user can decide to update + documentation from a pre-built binary package. I think it might be better to say "and compilation of the sources might be skipped through the use of a pre-built binary package provided by the &os; package-building cluster." + + + If building from sources is preferred, the mandatory + documentation tools will be automatically installed as a I would s/mandatory documentation tools/tools needed to build the documentation/ + dependency. + + + + Building and Installing Documentation Ports + + Organization of the documentation ports is as follows: + + + + There is a master port, misc/freebsd-doc-en where the comma after freebsd-doc-en. + documentation port files can be found. It is the base of + all documentation ports. By default, it builds the + English documentation only, probably the most requested + language for the majority of the users. I don't think that "probably ...users" is necessary + + + + There is an all in one port, misc/freebsd-doc-all, and it + builds and installs all documentation in all available + languages. + + + + Finally, there is a slave port for + each translation, e.g.: misc/freebsd-doc-hu for the + Hungarian-language documents. All of them depend on the + master port, and are present only for the ease of + installation. + + + + To install a documentation port by source, issue the s/by/from/ + following commands (as root): + [snip] + + + WITH_PDF + + + Allows the build of the &adobe; Portable Document + Format, for use with &adobe; &acrobat.reader; or + Ghostscript + (article.pdf, or + book.pdf, as appropriate). (I use xpdf, but this text is fine.) + + [snip] + + Using Packages + + If resources are not available for the complete build and + installation of the documentation ports, or we simply want to This sounds a bit awkward. "compilation" is perhaps not strictly correct, so maybe "the complete process of building and installing the documentation ports". + have the documentation installed in a more convenient way, + binary packages come handy. They can be managed as normal s/come handy/are a convenient option/ + &os; packages, via &man.pkg.add.1;, &man.pkg.delete.1;, and so + on. + [snip] Thanks for writing these up! -Ben Kaduk From brueffer at FreeBSD.org Thu Apr 23 08:39:48 2009 From: brueffer at FreeBSD.org (brueffer@FreeBSD.org) Date: Thu Apr 23 08:39:55 2009 Subject: docs/133785: [PATCH] man pages lying about HISTORY Message-ID: <200904230839.n3N8dlUF091860@freefall.freebsd.org> Synopsis: [PATCH] man pages lying about HISTORY State-Changed-From-To: open->patched State-Changed-By: brueffer State-Changed-When: Thu Apr 23 10:38:25 CEST 2009 State-Changed-Why: Corrected in HEAD. A little more research was necessary, since half of the functionality appeared prior to 7.2. Responsible-Changed-From-To: freebsd-doc->brueffer Responsible-Changed-By: brueffer Responsible-Changed-When: Thu Apr 23 10:38:25 CEST 2009 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=133785 From gavin at FreeBSD.org Thu Apr 23 14:35:23 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Thu Apr 23 14:35:28 2009 Subject: docs/82595: 25.5.3 Configuring a bridge section of the handbook needs updating Message-ID: <200904231435.n3NEZMbH084191@freefall.freebsd.org> Synopsis: 25.5.3 Configuring a bridge section of the handbook needs updating State-Changed-From-To: feedback->closed State-Changed-By: gavin State-Changed-When: Thu Apr 23 14:34:08 UTC 2009 State-Changed-Why: FGeedback timeout (1 year). I'm pretty sure this one is OBE. Responsible-Changed-From-To: freebsd-doc->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Thu Apr 23 14:34:08 UTC 2009 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=82595 From xuchen66 at gmail.com Thu Apr 23 14:48:59 2009 From: xuchen66 at gmail.com (Chen Xu) Date: Thu Apr 23 14:49:07 2009 Subject: what need to upgrade? Message-ID: <184b087c0904230720t5852baabxe3b3d7e74adb1c11@mail.gmail.com> Dear list, I have a simple question here. I have been using doc system to build my own documentation for a few years now. But it doesn't take a few things like etc., which I want too. My question is: do I have to upgrade building tools or just doc main structure, or simply css file? Thanks, Chen From kristof at artisandelatoile.com Thu Apr 23 15:06:00 2009 From: kristof at artisandelatoile.com (Kristof Leray) Date: Thu Apr 23 15:06:07 2009 Subject: bad link or down Message-ID: <9b902d900904230734n16bdcaa7pa51a193615477ca@mail.gmail.com> hi, This link: http://andrsn.stanford.edu/FreeBSD/ is not good, Regards From gabor at FreeBSD.org Thu Apr 23 16:35:36 2009 From: gabor at FreeBSD.org (=?UTF-8?B?R8OhYm9yIEvDtnZlc2TDoW4=?=) Date: Thu Apr 23 16:35:50 2009 Subject: what need to upgrade? In-Reply-To: <184b087c0904230720t5852baabxe3b3d7e74adb1c11@mail.gmail.com> References: <184b087c0904230720t5852baabxe3b3d7e74adb1c11@mail.gmail.com> Message-ID: <49F094F2.3030205@FreeBSD.org> Chen Xu escribi?: > Dear list, > > I have a simple question here. I have been using doc system to build my own > documentation for a few years now. But it doesn't take a few things like > etc., which I want too. > > My question is: do I have to upgrade building tools or just doc main structure, > or simply css file? > Hi Chen, I'm not totally sure what you mean, i.e. you build FreeBSD docs for yourself or you use the FreeBSD doc infrastructure to build your own documents not related to FreeBSD. I suppose you mean the latter. It is hard to tell what's wrong without seeing your document and seeing the way how you build it. The CSS file was changed some time ago. Maybe your one is outdated? If you use this system, you must be already experienced with DocBook. I suggest looking at DocBook 5, which is based on XML instead of SGML. Using DocBook 5 with the DocBook XSLT stylesheets is quite convenient and the output is very nice if you are willing to install Java and Apache FOP. Regards, -- Gabor Kovesdan FreeBSD Volunteer EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org From xuchen at brandeis.edu Thu Apr 23 17:06:24 2009 From: xuchen at brandeis.edu (Chen Xu) Date: Thu Apr 23 17:06:31 2009 Subject: what need to upgrade? In-Reply-To: <49F094F2.3030205@FreeBSD.org> References: <184b087c0904230720t5852baabxe3b3d7e74adb1c11@mail.gmail.com> <49F094F2.3030205@FreeBSD.org> Message-ID: <20090423165250.GA9664@brandeis.edu> Hi Gabor, thanks for the information. Yes, I have been using the FreeBSD doc infrastructure to build my own docs not related to FreeBSD. I use SGML. I have just updated the doc src and found that CSS was indeed changed. What you mentioned about DocBook 5 and DocBook XSLT stylesheets interested me. Could you provide a link or example what source code looks like? Regards, Chen * G??bor K??vesd??n [090423 12:19]: > Chen Xu escribi??: > > Dear list, > > > > I have a simple question here. I have been using doc system to build my own > > documentation for a few years now. But it doesn't take a few things like > > etc., which I want too. > > > > My question is: do I have to upgrade building tools or just doc main > > structure, > > or simply css file? > > > Hi Chen, > > I'm not totally sure what you mean, i.e. you build FreeBSD docs for yourself > or you use the FreeBSD doc infrastructure to build your own documents not > related to FreeBSD. I suppose you mean the latter. It is hard to tell what's > wrong without seeing your document and seeing the way how you build it. The > CSS file was changed some time ago. Maybe your one is outdated? > If you use this system, you must be already experienced with DocBook. I > suggest looking at DocBook 5, which is based on XML instead of SGML. Using > DocBook 5 with the DocBook XSLT stylesheets is quite convenient and the > output is very nice if you are willing to install Java and Apache FOP. > > Regards, > > -- > Gabor Kovesdan > FreeBSD Volunteer > > EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org > WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org > From freebsd at johannkois.at Thu Apr 23 17:11:24 2009 From: freebsd at johannkois.at (Johann Kois) Date: Thu Apr 23 17:11:40 2009 Subject: bad link or down In-Reply-To: <9b902d900904230734n16bdcaa7pa51a193615477ca@mail.gmail.com> References: <9b902d900904230734n16bdcaa7pa51a193615477ca@mail.gmail.com> Message-ID: <20090423190101.g6j9b0ciokcg00ss@login-8.hoststar.at> On 23.04.2009 Kristof Leray wrote: > hi, > > This link: > http://andrsn.stanford.edu/FreeBSD/ > > is not good, > > Regards > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > Hi, well, that may be the case. But as you can see from the address, this site is not part of FreeBSD.org. So there is nothing we can do about it. But maybe you mean that we link to this site somewhere on our website/in our documentation? If that is the case, you should let us know where exactly you found this link so that we can fix it. Johann - -- Johann Kois jkois(at)FreeBSD.org FreeBSD Documentation Project FreeBSD German Documentation Project - https://doc.bsdgroup.de From freebsd at johannkois.at Thu Apr 23 17:11:25 2009 From: freebsd at johannkois.at (Johann Kois) Date: Thu Apr 23 17:11:41 2009 Subject: what need to upgrade? In-Reply-To: <184b087c0904230720t5852baabxe3b3d7e74adb1c11@mail.gmail.com> References: <184b087c0904230720t5852baabxe3b3d7e74adb1c11@mail.gmail.com> Message-ID: <20090423190534.frh6vvrogk0oo8gg@login-8.hoststar.at> On 23.04.2009 Chen Xu wrote: > Dear list, > > I have a simple question here. I have been using doc system to build my own > documentation for a few years now. But it doesn't take a few things like > etc., which I want too. > > My question is: do I have to upgrade building tools or just doc main > structure, > or simply css file? > > Thanks, > Chen > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > What you should install is the meta-port textproc/docproj. It takes care of all doc related things. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview-quick-start.html for information on how to install it. The FDP primer also describes how to change/edit/build the documentation set: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html Johann -- Johann Kois jkois@FreeBSD.org FreeBSD German Documentation Project FreeBSD Documentation Project From josh.m.ulrich at gmail.com Thu Apr 23 18:39:08 2009 From: josh.m.ulrich at gmail.com (Josh Ulrich) Date: Thu Apr 23 18:39:20 2009 Subject: Possible documentation issue? Message-ID: <8cca69990904231107jf9fe544g9dcc45bda9309b5c@mail.gmail.com> Hello, The paragraph below states the default scheduler doesn't optimize for HTT but the default scheduler in the GENERIC kernel in 7.1 is now SCHED_ULE, which includes "CPU topology awareness, including for hyper-threading." (sched_ule(4)) I thought SCHED_ULE differentiates between physical and logical processors. Is that incorrect? From: http://www.freebsd.org/releases/7.1R/hardware.html "FreeBSD will take advantage of HyperThreading (HTT) support on Intel CPUs that support this feature. A kernel with the options SMP feature enabled will automatically detect the additional logical processors. The default FreeBSD scheduler treats the logical processors the same as additional physical processors; in other words, no attempt is made to optimize scheduling decisions given the shared resources between logical processors within the same CPU. Because this naive scheduling can result in suboptimal performance, under certain circumstances it may be useful to disable the logical processors with the the machdep.hlt_logical_cpus sysctl variable. It is also possible to halt any CPU in the idle loop with the machdep.hlt_cpus sysctl variable. The smp(4) manual page has more details." Best Regards, Josh -- http://quantemplation.blogspot.com http://www.fosstrading.com From xuchen66 at gmail.com Thu Apr 23 20:29:22 2009 From: xuchen66 at gmail.com (Chen Xu) Date: Thu Apr 23 20:29:29 2009 Subject: turn off or change footnote Message-ID: <184b087c0904231329x778f38ddqcde21dff80c101b5@mail.gmail.com> Dear List, If I want to turn off/on footnote or change it, what do I do? Chen From killasmurf86 at gmail.com Fri Apr 24 06:20:06 2009 From: killasmurf86 at gmail.com (Aldis Berjoza) Date: Fri Apr 24 06:20:12 2009 Subject: docs/133961: mistake in rc.conf(5) Message-ID: <200904240618.n3O6ISBS021026@www.freebsd.org> >Number: 133961 >Category: docs >Synopsis: mistake in rc.conf(5) >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: Fri Apr 24 06:20:05 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Aldis Berjoza >Release: >Organization: >Environment: >Description: geli_swap_flags Options passed to the geli(8) utility when encrypted GEOM providers for swap partitions are created. The default is ``-a aes -l 256 -s 4096 -d''. ---------------- ``-a aes -l 256 -s 4096 -d''. should be ``-e aes -l 256 -s 4096 -d''. >How-To-Repeat: >Fix: ``-a aes -l 256 -s 4096 -d''. should be ``-e aes -l 256 -s 4096 -d''. >Release-Note: >Audit-Trail: >Unformatted: From trhodes at FreeBSD.org Fri Apr 24 06:23:49 2009 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Fri Apr 24 06:23:58 2009 Subject: [PATCH] for the 'firewalls' chapter In-Reply-To: <49E796E6.70709@gmail.com> References: <49E796E6.70709@gmail.com> Message-ID: <20090424022336.3f4c6792.trhodes@FreeBSD.org> Hey Manolis, My review, as promised, please see comments in line. I'm sorry it came so late! Thanks! On Thu, 16 Apr 2009 23:36:54 +0300 Manolis Kiagias wrote: > Hey all, > > Once again, calling all my usual reviewers (as well as anyone else who > wishes to comment) on this (unfortunately long) patch for the > 'firewalls' chapter. > I've been writing and rewriting this for quite some time now, partly > while I was translating the chapter to Greek but also for quite some > time afterwards. It has gone through many changes and also includes > relevant parts from PR docs/131568 (author CCed). I will try to > summarize some of the changes, although this is as huge a task as the > patch itself! > > - Attempt to reduce some duplication. An identical paragraph on what is > an inclusive firewall was removed from each section, rephrased and added > at the beginning of the chapter. There are still more sections that > contain duplicate information. > - Convert to passive voice where possible and reduce amount of 'you' > (and in some cases 'I') references > - Rephrase several paragraphs (some were already commented as > problematic in the source). There were cases were the information was > clearly wrong (i.e. it was referenced that a packet exits the network, > reaches the destination and returns. Clearly, this is not the same > packet). Also not all firewalls need to have two interfaces (this was > submitted in the above PR). > - Attempt to improve markup. Originally I was planning to use s > everywhere, but the chapter is so full of them, that even the subtle > dotted line HTML rendering becomes tiring after a while. I did insert > s for consistency, where some terms were already marked (i.e. > TCP) and adjacent terms were not (i.e. UDP). If people feel we should > markup all of them, I'll gladly do it. I also inserted/fixed numerous > other tags (mostly ) > - Fix grammar / syntax / spelling in several cases > - Numerous other changes that will hopefully become clear while reading > the patch itself > > Here is the diff: > > http://people.freebsd.org/~manolis/firewalls.diff > > If you prefer to read the HTML build: > > http://www.freebsdgr.org/handbook-mine/firewalls.html > > Plase take all the time you need to read this - I will try to integrate > any suggested changes as they are coming, and obviously this is not > going in soon :) diff -r 126c435025de -r f6a8c68b044d en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml --- a/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml Sun Feb 01 15:17:37 2009 +0200 +++ b/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml Thu Apr 16 22:46:31 2009 +0300 @@ -124,12 +124,22 @@ reverse. It only allows traffic matching the rules through and blocks everything else. - Inclusive firewalls are generally safer than exclusive + An inclusive firewall offers much better control of the outgoing + traffic, making it a better choice for systems that offer services to + the public Internet. It also controls the type of traffic originating + from the public Internet that can gain access to your private network. + All traffic that does not match the rules, is blocked and logged by + default design. Inclusive firewalls are generally safer than exclusive I don't like "by default design" here. It just kind of sounds a tad bit off. How about "by design" instead? firewalls because they significantly reduce the risk of allowing - unwanted traffic to pass through the firewall. + unwanted traffic to pass through them. + + + Unless noted otherwise, all the configurations and example + rulesets in this chapter, create inclusive type firewalls. "all configuration and example rulesets in" + Security can be tightened further using a stateful - firewall. With a stateful firewall the firewall keeps + firewall. This type of firewall keeps track of which connections are opened through the firewall and will only allow traffic through which either matches an existing connection or opens a new one. The disadvantage of a stateful @@ -153,14 +163,14 @@ &man.altq.4; and &man.dummynet.4;. Dummynet has traditionally been closely tied with IPFW, and ALTQ with - PF. Traffic shaping for IPFILTER can currently - be done with IPFILTER for NAT and filtering and + PF. Traffic shaping for IPFILTER can currently + be done with IPFILTER for NAT and filtering and IPFW with &man.dummynet.4; Too many "and" in this sentence. How about: "Traffic shaping for IPFILTER can currently be done with IPFILTER for NAT. IPFW filtering is handled via the &man.dummynet.4; driver ..." Perhaps the entire paragraph should be re-worded after we commit these other changes? or by using PF with ALTQ. IPFW, and PF all use rules to control the access of packets to and from your system, although they go about it different ways and - have different rule syntaxes. + have different rule syntax. "have a different rule syntax." The reason that &os; has multiple built in firewall packages is that different people have different requirements and @@ -174,7 +184,7 @@ Since all firewalls are based on inspecting the values of selected packet control fields, the creator of the firewall rulesets must have an understanding of how - TCP/IP works, what the different values in + TCP/IP works, what the different values in the packet control fields are and how these values are used in a normal session conversation. For a good explanation go to: pf_enable="YES" is present. However, the PF module will - not load if the system cannot find a PF + not be loaded if the system cannot find a PF ruleset configuration file. The default location is /etc/pf.conf. If your PF ruleset is located somewhere else put @@ -291,7 +301,7 @@ paired with &man.carp.4; to create failover firewalls using PF. More information on CARP can be found in - chapter 29 of the handbook. + of the Handbook. The PF kernel options can be found in /usr/src/sys/conf/NOTES and are reproduced @@ -448,14 +458,14 @@ options ALTQ enables the ALTQ framework. - options ALTQ_CBQ enables Class Based - Queuing (CBQ). CBQ + options ALTQ_CBQ enables Class Based + Queuing (CBQ). CBQ allows you to divide a connection's bandwidth into different classes or queues to prioritize traffic based on filter rules. - options ALTQ_RED enables Random Early - Detection (RED). RED is + options ALTQ_RED enables Random Early + Detection (RED). RED is used to avoid network congestion. RED does this by measuring the length of the queue and comparing it to the minimum and maximum thresholds for the queue. If the @@ -463,16 +473,16 @@ True to its name, RED drops packets from different connections randomly. - options ALTQ_RIO enables Random Early - Detection In and Out. + options ALTQ_RIO enables Random Early + Detection In and Out. options ALTQ_HFSC enables the - Hierarchical Fair Service Curve Packet Scheduler. For more + Hierarchical Fair Service Curve Packet Scheduler. For more information about HFSC see: . - options ALTQ_PRIQ enables Priority - Queuing (PRIQ). PRIQ + options ALTQ_PRIQ enables Priority + Queuing (PRIQ). PRIQ will always pass traffic that is in a higher queue first. @@ -492,11 +502,6 @@ IPFILTER - - This section is work in progress. The contents might - not be accurate at all times. - - The author of IPFILTER is Darren Reed. IPFILTER is not operating system dependent: it is an open source application and has been ported to &os;, NetBSD, OpenBSD, &sunos;, HP/UX, and @@ -519,30 +524,17 @@ stateless type of rules. Over time IPF has been enhanced to include a quick option and a stateful keep state option which drastically modernized the rules - processing logic. IPF's official documentation covers the legacy - rule coding parameters and the legacy rule file processing + processing logic. IPF's official documentation covers only the legacy + rule coding parameters and rule file processing logic. The modernized functions are only included as additional options, completely understating their benefits in producing a - far superior secure firewall. + far superior and more secure firewall. The instructions contained in this section are based on using rules that contain the quick option and the stateful keep state option. This is the basic framework for coding an inclusive firewall rule set. - - - An inclusive firewall only allows packets matching the rules - to pass through. This way you can control what services can - originate behind the firewall destined for the public Internet - and also control the services which can originate from the - public Internet accessing your private network. Everything else - is blocked and logged by default design. Inclusive firewalls are - much, much more secure than exclusive firewall rule sets and is - the only rule set type covered herein. - For detailed explanation of the legacy rules processing method see: @@ -567,13 +559,13 @@ IPF is included in the basic &os; install as a separate run time loadable module. The system will dynamically load the IPF - kernel loadable module when the rc.conf statement + kernel loadable module when the rc.conf statement ipfilter_enable="YES" is used. The loadable module was created with logging enabled and the - default pass all options. You do not need + default pass all options. There is no need to compile IPF into the &os; kernel just to change the default - to block all, you can do that by just coding - a block all rule at the end of your rule set. + to block all. This can be done just by adding + a block all rule at the end of your rule set. @@ -603,7 +595,7 @@ kernel options - It is not a mandatory requirement that you enable IPF by + It is not a mandatory requirement to enable IPF by compiling the following options into the &os; kernel. It is only presented here as background information. Compiling IPF into the kernel causes the loadable module to never be @@ -630,16 +622,15 @@ the default behavior so any packet not matching a firewall pass rule gets blocked. - These settings will take effect only after you have built - and installed a kernel with them set. + These settings will take effect only after installing a kernel + that has been built with the above options set. Available rc.conf Options - You need the following statements in - /etc/rc.conf to activate IPF at boot - time: + To activate IPF at boot time, the following statements need to + be added to /etc/rc.conf: ipfilter_enable="YES" # Start ipf firewall ipfilter_rules="/etc/ipf.rules" # loads rules definition text file @@ -649,9 +640,9 @@ # v = log tcp window, ack, seq # n = map IP & port to names - If you have a LAN behind this firewall that uses the - reserved private IP address ranges, then you need to add the - following to enable NAT + If there is a LAN behind this firewall that uses the + reserved private IP address ranges, the following lines will have to + be added to enable NAT functionality: gateway_enable="YES" # Enable as LAN gateway @@ -664,10 +655,10 @@ ipf - The ipf command is used to load your rules file. Normally - you create a file containing your custom rules and use this - command to replace in mass the currently running firewall - internal rules: + The &man.ipf.8; command is used to load your rules file. "ruleset file." ? + Your custom rules would normally be placed in a file, and the + following command could then be used to replace in mass the + currently running firewall rules: &prompt.root; ipf -Fa -f /etc/ipf.rules @@ -738,7 +729,7 @@ Packet log flags set: (0) When supplied with either for inbound - or for outbound, it will retrieve and + or for outbound, the command will retrieve and display the appropriate list of filter rules currently installed and in use by the kernel. @@ -772,7 +763,7 @@ ipfstat command is the flag which displays the state table in a way similar to the way &man.top.1; shows the &os; running process table. When your - firewall is under attack this function gives you the ability to + firewall is under attack, this function gives you the ability to identify, drill down to, and see the attacking packets. The optional sub-flags give the ability to select the destination or source IP, port, or protocol that you want to monitor in @@ -792,19 +783,19 @@ In order for ipmon to work properly, the - kernel option IPFILTER_LOG must be turned on. This command has + kernel option IPFILTER_LOG must be turned on. This command has two different modes that it can be used in. Native mode is the - default mode when you type the command on the command line + default mode when the command is typed on the command line without the flag. - Daemon mode is for when you want to have a continuous - system log file available so that you can review logging of - past events. This is how &os; and IPFILTER are configured to + Daemon mode is for when a continuous + system log file is desired, so that logging of past events may be + reviewed. This is how &os; and IPFILTER are configured to work together. &os; has a built in facility to automatically rotate system logs. That is why outputting the log information - to syslogd is better than the default of outputting to a - regular file. In the default rc.conf file - you see the ipmon_flags statement uses the + to &man.syslogd.8; is better than the default of outputting to a + regular file. In the default rc.conf file, + the ipmon_flags statement uses the flags: ipmon_flags="-Ds" # D = start as daemon @@ -815,7 +806,7 @@ The benefits of logging are obvious. It provides the ability to review, after the fact, information such as which packets had been dropped, what addresses they came from and - where they were going. These all give you a significant edge + where they were going. These all can provide a significant edge "These can all provide" if we're making the change here. :) in tracking down attackers. Even with the logging facility enabled, IPF will not @@ -826,7 +817,7 @@ It is very customary to include a default deny everything rule with the log keyword included as your last rule in the - rule set. This way you get to see all the packets that did not + rule set. This makes possible to see all the packets that did not "This makes it possible" match any of the rules in the rule set. @@ -850,15 +841,15 @@ To setup IPFILTER to log all data to - /var/log/ipfilter.log, you will need to - create the file. The following command will do that: + /var/log/ipfilter.log, the file will need to be + created beforehand. The following command will do that: &prompt.root; touch /var/log/ipfilter.log - The syslog function is controlled by definition statements + The &man.syslogd.8; function is controlled by definition statements in the /etc/syslog.conf file. The syslog.conf file offers considerable - flexibility in how syslog will deal with system messages issued + flexibility in how syslog will deal with system messages issued by software applications like IPF. Add the following statement to @@ -871,13 +862,13 @@ file location. To activate the changes to /etc/syslog.conf - you can reboot or bump the syslog task into + you can reboot or bump the &man.syslogd.8; daemon into re-reading /etc/syslog.conf by running /etc/rc.d/syslogd reload Do not forget to change /etc/newsyslog.conf to rotate the new log - you just created above. + just created above. s/just // @@ -924,18 +915,18 @@ The addresses. This is actually three fields: the source address and port (separated by a comma), the -> - symbol, and the destination address and port. - 209.53.17.22,80 -> 198.73.220.17,1722. + symbol, and the destination address and port, e.g. "e.g.:" + 209.53.17.22,80 -> 198.73.220.17,1722. PR followed by the protocol name or - number, e.g. PR tcp. + number, e.g. PR tcp. "e.g.:" len followed by the header length - and total length of the packet, e.g. len 20 40. + and total length of the packet, e.g. len 20 40. "e.g.:" here too please. :) @@ -958,15 +949,15 @@ Some experienced IPF users create a file containing the rules and code them in a manner compatible with running them as a script with symbolic substitution. The major benefit of - doing this is that you only have to change the value associated - with the symbolic name and when the script is run all the rules + doing this is that only the value associated + with the symbolic name needs to be changed, and when the script is run all the rules containing the symbolic name will have the value substituted in - the rules. Being a script, you can use symbolic substitution + the rules. Being a script, symbolic substitution can be used to code frequently used values and substitute them in multiple - rules. You will see this in the following example. + rules. This can be seen in the following example. - The script syntax used here is compatible with the sh, csh, - and tcsh shells. + The script syntax used here is compatible with the &man.sh.1;, &man.csh.1;, + and &man.tcsh.1; shells. Symbolic substitution fields are prefixed with a dollar sign: $. @@ -1012,8 +1003,8 @@ That is all there is to it. The rules are not important in this example; how the symbolic substitution fields are populated and used are. If the above example was in a file - named /etc/ipf.rules.script, you could - reload these rules by entering the following command: + named /etc/ipf.rules.script, these rules could be + reloaded by entering the following command: &prompt.root; sh /etc/ipf.rules.script @@ -1040,7 +1031,7 @@ value) into /etc/rc.conf file. Add a script like the following to your - /usr/local/etc/rc.d/ startup + /usr/local/etc/rc.d/ startup directory. The script should have an obvious name like ipf.loadrules.sh. The .sh extension is mandatory. @@ -1062,25 +1053,19 @@ IPF Rule Sets - - - A rule set is a group of ipf rules coded to pass or block + A rule set is a group of IPF rules coded to pass or block packets based on the values contained in the packet. The bi-directional exchange of packets between hosts comprises a - session conversation. The firewall rule set processes the - packet two times, once on its arrival from the public Internet - host and again as it leaves for its return trip back to the - public Internet host. Each TCP/IP service (i.e. telnet, www, - mail, etc.) is predefined by its protocol, source and - destination IP address, or the source and destination port - number. This is the basic selection criteria used to create - rules which will pass or block services. + session conversation. The firewall rule set processes both the Are we using "rule set" or "ruleset" because up above it was just one word. We should come to a conclusion and run a %s/one/right one/g across this chapter then. :) + packets arriving from the public Internet, as well as the packets + produced by the system as a response to them. + Each TCP/IP service (i.e. telnet, www, "i.e.: " + mail, etc.) is predefined by its protocol and privileged (listening) + port. Packets destined for a specific service, originate from the + source address using an unprivileged (high order) port and target the + specific service port on the destination address. All the above + parameters (i.e. ports and addresses) can be used as selection "i.e.: " again. :) + criteria to create rules which will pass or block services. IPFILTER @@ -1101,19 +1086,6 @@ basic framework for coding an inclusive firewall rule set. - - - An inclusive firewall only allows services matching the - rules through. This way you can control what services can - originate behind the firewall destined for the public Internet - and also control the services which can originate from the - public Internet accessing your private network. Everything - else is blocked and logged by default design. Inclusive - firewalls are much, much securer than exclusive firewall rule - sets and is the only rule set type covered herein. - All this removal is key. Seriously, this has needed to be done for some time. Thanks!! When working with the firewall rules, be very careful. Some configurations will @@ -1187,7 +1159,7 @@ The action indicates what to do with the packet if it matches the rest of the filter rule. Each rule - must have a action. The following + must have an action. The following actions are recognized: block indicates that the packet should @@ -1204,7 +1176,7 @@ A mandatory requirement is that each filter rule explicitly state which side of the I/O it is to be used on. - The next keyword must be either in or out and one or the + The next keyword must be either in or out and one or the other has to be coded or the rule will not pass syntax checks. @@ -1250,8 +1222,8 @@ processing logic. When a packet is logged, the headers of the packet are - written to the IPL packet logging pseudo-device. - Immediately following the log keyword, the following + written to the IPL packet logging pseudo-device. + Immediately following the log keyword, the following qualifiers may be used (in this order): body indicates that the first 128 @@ -1259,8 +1231,8 @@ headers. first If the log - keyword is being used in conjunction with a keep - state option, it is recommended that this option is + keyword is being used in conjunction with a keep + state option, it is recommended that this option is also applied so that only the triggering packet is logged and not every packet which thereafter matches the keep state information. @@ -1270,7 +1242,7 @@ SELECTION The keywords described in this section are used to - describe attributes of the packet to be interrogated when + describe attributes of the packet to be checked when determining whether rules match or not. There is a keyword subject, and it has sub-option keywords, one of which has to be selected. The following general-purpose @@ -1291,7 +1263,7 @@ protocol names found in /etc/protocols are recognized and may be used. The special protocol keyword tcp/udp may be used to match either a - TCP or a UDP packet, and has been added as + TCP or a UDP packet, and has been added as a convenience to save duplication of otherwise identical rules. @@ -1303,23 +1275,19 @@ synonym for from any to any with no other match parameters. - from src to dst: the from and to + from src to dst: the from and to keywords are used to match against IP addresses. Rules must - specify BOTH source and destination parameters. + specify both source and destination parameters. any is a special keyword that matches any - IP address. Examples of use: from any to any - or from 0.0.0.0/0 to any or from any to - 0.0.0.0/0 or from 0.0.0.0 to any or - from any to 0.0.0.0. + IP address. Examples of use: from any to any + or from 0.0.0.0/0 to any or from any to + 0.0.0.0/0 or from 0.0.0.0 to any or + from any to 0.0.0.0. - - - IP addresses may be specified as a dotted IP address - numeric form/mask-length, or as single dotted IP address - numeric form. There is no way to match ranges of IP addresses which - do not express themselves easily as mask-length. See this + do not express themselves easily using the dotted numeric + form / mask-length notation. See this web page for help on writing mask-length: . It's a port too, that ipcalc utility. :) @@ -1329,21 +1297,21 @@ If a port match is included, for either or both of source and destination, then it is only applied to - TCP and UDP packets. When composing port + TCP and UDP packets. When composing port comparisons, either the service name from /etc/services or an integer port number - may be used. When the port appears as part of the from + may be used. When the port appears as part of the from object, it matches the source port number; when it appears - as part of the to object, it matches the destination port + as part of the to object, it matches the destination port number. The use of the port option with the to object is a mandatory requirement for the modernized rules processing logic. Example of use: - from any to any port = 80 + from any to any port = 80 - + - Port comparisons may be done in a number of forms, with - a number of comparison operators, or port ranges may be + Single port comparisons may be done in a number of ways, using + a number of different comparison operators. Port ranges may also be specified. port "=" | "!=" | "<" | ">" | "<=" | ">=" | @@ -1364,8 +1332,8 @@ <acronym>TCP</acronym>_FLAG Flags are only effective for TCP - filtering. The letters represents one of the possible flags - that can be interrogated in the TCP packet + filtering. The letters represent one of the possible flags + that can be matched against the TCP packet header. The modernized rules processing logic uses the @@ -1402,15 +1370,15 @@ exchange of packets comprising a session conversation. When activated, keep-state dynamically generates internal rules for each anticipated packet being exchanged during the - bi-directional session conversation. It has the interrogation - abilities to determine if the session conversation between the + bi-directional session conversation. It has sufficient matching + capabilities to determine if the session conversation between the originating sender and the destination are following the valid procedure of bi-directional packet exchange. Any packets that do not properly fit the session conversation template are automatically rejected as impostors. - Keep state will also allow ICMP packets related to a - TCP or UDP session through. So if you get + Keep state will also allow ICMP packets related to a + TCP or UDP session through. So if you get ICMP type 3 code 4 in response to some web surfing allowed out Missed tag. :) by a keep state rule, they will be automatically allowed in. Any packet that IPF can be certain is part of an active @@ -1419,21 +1387,22 @@ What happens is: - Packets destined to go out the interface connected to the + Packets destined to go out through the interface connected to the public Internet are first checked against the dynamic state - table, if the packet matches the next expected packet - comprising in a active session conversation, then it exits the + table. If the packet matches the next expected packet + comprising an active session conversation, then it exits the firewall and the state of the session conversation flow is - updated in the dynamic state table, the remaining packets get - checked against the outbound rule set. + updated in the dynamic state table. Packets that do not belong to + an already active session, are simply checked against the outbound + rule set. - Packets coming in to the interface connected to the public - Internet are first checked against the dynamic state table, if - the packet matches the next expected packet comprising a + Packets coming in from the interface connected to the public + Internet are first checked against the dynamic state table. If + the packet matches the next expected packet comprising an active session conversation, then it exits the firewall and the state of the session conversation flow is updated in the - dynamic state table, the remaining packets get checked against - the inbound rule set. + dynamic state table. Packets that do not belong to an already active + session, are simply checked against the inbound rule set. When the conversation completes it is removed from the dynamic state table. @@ -1443,7 +1412,7 @@ packets will be allowed through automatically and any impostors automatically rejected. If a new session is blocked, none of its subsequent packets will be allowed through. Stateful - filtering has technically advanced interrogation abilities + filtering has technically advanced matching abilities capable of defending against the flood of different attack methods currently employed by attackers. @@ -1455,10 +1424,15 @@ The following rule set is an example of how to code a very secure inclusive type of firewall. An inclusive firewall only - allows services matching pass rules through and blocks all - other by default. All firewalls have at the minimum two - interfaces which have to have rules to allow the firewall to - function. + allows services matching pass rules through, and blocks all + other by default. Firewalls intended to protect other machines, "others by default." + also called network firewalls, should have at least + two interfaces, which are generally configured to trust one side + (the LAN) and not the other (the public Internet). Alternatively, Perhaps around LAN? + a firewall might be configured to protect only the system running the + firewall software—this is called a "only the system it is running on—this is called a" Mainly to avoid saying "firewall" twice in the same sentence. + host based firewall, and is particularly appropriate + for servers on an untrusted network. All &unix; flavored systems including &os; are designed to use interface lo0 and IP address @@ -1468,20 +1442,19 @@ special internally used packets. The interface which faces the public Internet is the one - where you place your rules to authorize and control access out - to the public Internet and access requests arriving from the - public Internet. This can be your user PPP + to place the rules that authorize and control access of the outbound + and inbound connections. This can be your user PPP tun0 interface or your NIC that is connected to your DSL or cable modem. - In cases where one or more NICs are cabled to private LANs - behind the firewall, those interfaces must have a rule coded to - allow free unmolested movement of packets originating from - those LAN interfaces. + In cases where one or more NICs are cabled to private network + segments, those interfaces may require rules to allow packets + originating from those LAN interfaces transit to each other and/or + to the outside (Internet). - The rules should be first organized into three major - sections: all the free unmolested interfaces, the public - interface outbound, and the public interface inbound. + The rules should be organized into three major + sections: first trusted interfaces, then the public + interface outbound, and last the public untrusted interface inbound. The rules in each of the public interface sections should have the most frequently matched rules placed before less @@ -1490,66 +1463,65 @@ direction. The Outbound section in the following rule set only - contains 'pass' rules which contain selection values that + contains pass rules which contain selection values that uniquely identify the service that is authorized for public - Internet access. All the rules have the 'quick', 'on', - 'proto', 'port', and 'keep state' option coded. The 'proto - tcp' rules have the 'flag' option included to identify the + Internet access. All the rules have the quick, on, + proto, port, and keep state options set. The proto + tcp rules have the flag option included to identify the session start request as the triggering packet to activate the stateful facility. The Inbound section has all the blocking of undesirable packets first, for two different reasons. The first is that - these things being blocked may be part of an otherwise valid - packet which may be allowed in by the later authorized service - rules. The second reason is that by having a rule that - explicitly blocks selected packets that I receive on an - infrequent basis and that I do not want to see in the log, they - will not be caught by the last rule in the section which blocks - and logs all packets which have fallen through the rules. The - last rule in the section which blocks and logs all packets is - how you create the legal evidence needed to prosecute the - people who are attacking your system. + malicious packets may be partial matches for legitimate traffic. + These packets have to be discarded rather than allowed in, based on + their partial matches against allow rules. + The second reason is that known and uninteresting rejects may be + blocked silently, rather than being caught and logged by the last + rules in the section. The final rule in each section, blocks and + logs all packets and can be used to create the legal evidence needed + to prosecute the people who are attacking your system. - Another thing you should take note of, is there is no - response returned for any of the undesirable stuff, their - packets just get dropped and vanish. This way the attacker + Another thing that should be taken care of, is to insure there is no + response returned for any of the undesirable traffic. Invalid + packets should just get dropped and vanish. This way the attacker has no knowledge if his packets have reached your system. The less the attackers can learn about your system, the more time they must invest before actually doing something bad. - The inbound 'nmap OS fingerprint' attempts rule I log + Rules that include a log first option, will only + log the event the first time they are triggered. This option is + included in the sample nmap OS fingerprint rule. + The security/nmap utility is + commonly used by attackers who attempt to identify the operating + system of your server. - + Any time there are logged messages on a rule with + the log first option, an ipfstat -hio + command should be executed to evaluate how many times the rule has + actually matched. Large number of matches usually indicate that the + system is being flooded (i.e. under attack). "i.e.: " again. :) - the first occurrence because this is something a attacker - would do. - - Any time you see log messages on a rule with 'log first'. - You should do an ipfstat -hio command to see - the number of times the rule has been matched so you know if - you are being flooded, i.e. under attack. - - When you log packets with port numbers you do not - recognize, look it up in /etc/services or - go to The /etc/services file may be used to + lookup unknown port numbers. Alternatively, + visit - and do a port number lookup to find what the purpose of that - port number is. + and do a port number lookup to find the purpose of a particular + port number. Check out this link for port numbers used by Trojans . - The following rule set is a complete very secure - 'inclusive' type of firewall rule set that I have used on my - system. You can not go wrong using this rule set for your own. - Just comment out any pass rules for services that you do not - want to authorize. + The following rule set creates a complete and very secure + inclusive type of firewall rule set that has been + tested on production systems. It can be easily modified for your + own system. Just comment out any pass rules for + services that should not be authorized. - If you see messages in your log that you want to stop - seeing just add a block rule in the inbound section. + To avoid logging unwanted messages, + just add a block rule in the inbound section. - You have to change the dc0 - interface name in every rule to the interface name of the Nic + The dc0 interface name has to be changed + in every rule to the real interface name of the NIC card that connects your system to the public Internet. For user PPP it would be tun0. @@ -1572,9 +1544,9 @@ ################################################################# # Interface facing Public Internet (Outbound Section) -# Interrogate session start requests originating from behind the +# Match session start requests originating from behind the # firewall on the private network -# or from this gateway server destine for the public Internet. +# or from this gateway server destined for the public Internet. ################################################################# # Allow out access to my ISP's Domain name server. @@ -1609,38 +1581,38 @@ # Allow out nntp news pass out quick on dc0 proto tcp from any to any port = 119 flags S keep state -# Allow out gateway & LAN users non-secure FTP ( both passive & active modes) +# Allow out gateway & LAN users' non-secure FTP ( both passive & active modes) # This function uses the IPNAT built in FTP proxy function coded in # the nat rules file to make this single rule function correctly. # If you want to use the pkg_add command to install application packages # on your gateway system you need this rule. pass out quick on dc0 proto tcp from any to any port = 21 flags S keep state -# Allow out secure FTP, Telnet, and SCP +# Allow out ssh/sftp/scp (telnet/rlogin/FTP replacements) # This function is using SSH (secure shell) pass out quick on dc0 proto tcp from any to any port = 22 flags S keep state -# Allow out non-secure Telnet +# Allow out insecure Telnet pass out quick on dc0 proto tcp from any to any port = 23 flags S keep state -# Allow out FBSD CVSUP function +# Allow out FreeBSD CVSup pass out quick on dc0 proto tcp from any to any port = 5999 flags S keep state # Allow out ping to public Internet pass out quick on dc0 proto icmp from any to any icmp-type 8 keep state -# Allow out whois for LAN PC to public Internet +# Allow out whois from LAN to public Internet pass out quick on dc0 proto tcp from any to any port = 43 flags S keep state # Block and log only the first occurrence of everything # else that's trying to get out. -# This rule enforces the block all by default logic. +# This rule implements the default block block out log first quick on dc0 all ################################################################# # Interface facing Public Internet (Inbound Section) -# Interrogate packets originating from the public Internet -# destine for this gateway server or the private network. +# Match packets originating from the public Internet +# destined for this gateway server or the private network. ################################################################# # Block all inbound traffic from non-routable or reserved address spaces @@ -1711,9 +1683,8 @@ # Block and log only first occurrence of all remaining traffic # coming into the firewall. The logging of only the first -# occurrence stops a .denial of service. attack targeted -# at filling up your log file space. -# This rule enforces the block all by default logic. +# occurrence avoids filling up disk with Denial of Service logs. +# This rule implements the default block. block in log first quick on dc0 all ################### End of rules file ##################################### @@ -1735,8 +1706,8 @@ NAT - NAT stands for Network Address - Translation. To those familiar with &linux;, this concept is + NAT stands for Network Address + Translation. To those familiar with &linux;, this concept is called IP Masquerading; NAT and IP Masquerading are the same thing. One of the many things the IPF NAT function enables is the ability to @@ -1748,17 +1719,16 @@ normally assign a dynamic IP address to their non-commercial users. Dynamic means that the IP address can be different each time you dial in and log on to your ISP, or for cable and DSL - modem users when you power off and then power on your modems - you can get assigned a different IP address. This IP address - is how you are known to the public Internet. + modem users, when the modem is power cycled. This dynamic IP + address is used to identify your system to the public Internet. Now lets say you have five PCs at home and each one needs Internet access. You would have to pay your ISP for an individual Internet account for each PC and have five phone lines. - With NAT you only need a single account - with your ISP, then cable your other four PCs to a switch and + With NAT only a single account is needed + with your ISP. The other four PCs may then be cabled to a switch and the switch to the NIC in your &os; system which is going to service your LAN as a gateway. NAT will automatically translate the private LAN IP address for each @@ -1766,18 +1736,9 @@ exits the firewall bound for the public Internet. It also does the reverse translation for returning packets. - NAT is most often accomplished without - the approval, or knowledge, of your ISP and in most cases is - grounds for your ISP terminating your account if found out. - Commercial users pay a lot more for their Internet connection - and usually get assigned a block of static IP address which - never change. The ISP also expects and consents to their - Commercial customers using NAT for their - internal private LANs. - There is a special range of IP addresses reserved for - NATed private LAN IP address. According to - RFC 1918, you can use the following IP ranges for private nets + NATed private LANs. According to + RFC 1918, the following IP ranges may be used for private nets which will never be routed directly to the public Internet: @@ -1837,7 +1798,7 @@ When changing the NAT rules after NAT has been started, make your changes to - the file containing the NAT rules, then run ipnat command with + the file containing the NAT rules, then run the ipnat command with the flags to delete the internal in use NAT rules and flush the contents of the translation table of all active entries. @@ -1901,18 +1862,18 @@ A packet arrives at the firewall from the LAN with a public destination. It passes through the outbound filter rules, - NAT gets his turn at the packet and applies + NAT gets its turn at the packet and applies its rules top down, first matching rule wins. NAT tests each of its rules against the - packets interface name and source IP address. When a packets + packet's interface name and source IP address. When a packet's interface name matches a NAT rule then the - [source IP address, i.e. private LAN IP address] of the packet + source IP address (i.e. private LAN IP address) of the packet i.e.: again please. is checked to see if it falls within the IP address range specified to the left of the arrow symbol on the NAT rule. On a match the packet has its source IP address rewritten with the public IP address obtained by the 0/32 keyword. - NAT posts a entry in its internal + NAT posts an entry in its internal NAT table so when the packet returns from the public Internet it can be mapped back to its original private IP address and then passed to the filter rules for @@ -1965,11 +1926,11 @@ In the above rule the packet's source port is unchanged as the packet passes through IPNAT. By - adding the portmap keyword you can tell - IPNAT to only use source ports in a range. + adding the portmap keyword, + IPNAT can be directed to only use source ports in the specified range. For example the following rule will tell IPNAT to modify the source port to be - within that range: + within the range shown: map dc0 192.168.1.0/24 -> 0/32 portmap tcp/udp 20000:60000 @@ -1982,12 +1943,12 @@ - Using a pool of public addresses + Using a Pool of Public Addresses In very large LANs there comes a point where there are just too many LAN addresses to fit into a single public address. If a block - of public IP addresses is available, you can use these addresses as - a pool, and let IPNAT pick one of + of public IP addresses is available, these addresses can be used as + a pool, and IPNAT may pick one of the public IP addresses as packet-addresses are mapped on their way out. @@ -2017,10 +1978,10 @@ has to be some way to direct the inbound traffic to the correct LAN PCs. IPNAT has the redirection facilities of NAT to solve this problem. - Lets say you have your web server on LAN address 10.0.10.25 and your single public IP - address is 20.20.20.5 you would - code the rule like this: + For example, assuming a web server operating on LAN address 10.0.10.25 and using a single public IP + address of 20.20.20.5 the rule would + be coded as follows: rdr dc0 20.20.20.5/32 port 80 -> 10.0.10.25 port 80 @@ -2048,7 +2009,7 @@ changed to address new security concerns. FTP has two flavors, it can run in active mode or passive mode. The difference is in how the data channel is acquired. Passive mode is more - secure as the data channel is acquired be the ordinal ftp + secure as the data channel is acquired by the ordinal ftp session requester. For a real good explanation of FTP and the different modes see . @@ -2099,8 +2060,8 @@ Only one filter rule is needed for FTP if the NAT FTP proxy is used. - Without the FTP Proxy you will need the following three - rules: + Without the FTP Proxy, the following three rules will be + needed: # Allow out LAN PC client FTP to public Internet # Active and passive modes @@ -2124,7 +2085,7 @@ IPFW - The IPFIREWALL (IPFW) is a &os; sponsored firewall software + The IPFIREWALL (IPFW) is a &os; sponsored firewall software application authored and maintained by &os; volunteer staff members. It uses the legacy stateless rules and a legacy rule coding technique to achieve what is referred to as Simple @@ -2133,7 +2094,7 @@ The IPFW sample rule set (found in /etc/rc.firewall and /etc/rc.firewall6) in the standard &os; - install is rather simple and it is not expected that it used + install is rather simple and it is not expected to be used directly without modifications. The example does not use stateful filtering, which is beneficial in most setups, so it will not be used as base for this section. @@ -2147,14 +2108,14 @@ different protocols use and create their unique packet header information is necessary before the power of the IPFW rules can be unleashed. Providing that level of explanation is out of the - scope of this section of the handbook. + scope of this section of the Handbook. IPFW is composed of seven components, the primary component is the kernel firewall filter rule processor and its integrated - packet accounting facility, the logging facility, the 'divert' + packet accounting facility, the logging facility, the divert rule which triggers the NAT facility, and the advanced special purpose facilities, the dummynet traffic shaper - facilities, the 'fwd rule' forward facility, the bridge + facilities, the fwd rule forward facility, the bridge facility, and the ipstealth facility. IPFW supports both IPv4 and IPv6. @@ -2170,9 +2131,9 @@ IPFW is included in the basic &os; install as a separate run time loadable module. The system will dynamically load the kernel module when the rc.conf statement - firewall_enable="YES" is used. You do not - need to compile IPFW into the &os; kernel unless you want - NAT function enabled. + firewall_enable="YES" is used. There is no + need to compile IPFW into the &os; kernel unless + NAT functionality is desired. After rebooting your system with firewall_enable="YES" in @@ -2184,8 +2145,8 @@ The loadable module does have logging ability compiled in. To enable logging and set the verbose logging - limit, there is a knob you can set in - /etc/sysctl.conf by adding these + limit, there is a knob that can be set in + /etc/sysctl.conf. By adding these statements, logging will be enabled on future reboots: net.inet.ip.fw.verbose=1 @@ -2219,9 +2180,9 @@ kernel options - It is not a mandatory requirement that you enable IPFW by - compiling the following options into the &os; kernel unless - you need NAT function. It is presented here + It is not a mandatory requirement to enable IPFW by + compiling the following options into the &os; kernel, unless + NAT functionality is required. It is presented here as background information. options IPFIREWALL @@ -2231,13 +2192,13 @@ options IPFIREWALL_VERBOSE Enables logging of packets that pass through IPFW and have - the 'log' keyword specified in the rule set. + the log keyword specified in the rule set. options IPFIREWALL_VERBOSE_LIMIT=5 Limits the number of packets logged through &man.syslogd.8; - on a per entry basis. You may wish to use this option in - hostile environments which you want to log firewall activity. + on a per entry basis. This option may be used in + hostile environments, when firewall activity logging is desired. This will close a possible denial of service attack via syslog flooding. @@ -2250,8 +2211,8 @@ options IPFIREWALL_DEFAULT_TO_ACCEPT This option will allow everything to pass through the - firewall by default, which is a good idea when you are first - setting up your firewall. + firewall by default, which is a good idea when the firewall is being + set up for the first time. kernel options @@ -2265,9 +2226,10 @@ functionality. - If you do not include IPFIREWALL_DEFAULT_TO_ACCEPT or set - your rules to allow incoming packets you will block all - packets going to and from this machine. + If the option IPFIREWALL_DEFAULT_TO_ACCEPT + is not included, and there are also no rules to allow incoming + packets, the firewall will block all incoming and outgoing Double negative here (use of no and not in the same sentence). Perhaps: "The firewall will block all incoming and outgoing packets if either the IPFIREWALL_DEFAULT_TO_ACCEPT kernel option or a rule to explicily allow these connections are missing." + connections. @@ -2308,7 +2270,7 @@ of firewall rules. - filename — absolute path of + filename — absolute path of file containing firewall rules. @@ -2323,12 +2285,12 @@ add block in all add block out all - On the other hand, it is possible to set - firewall_script variable to absolute path of + On the other hand, it is possible to set the + firewall_script variable to the absolute path of an executable script that includes ipfw commands being executed at system boot time. A valid ruleset script that would be equivalent to the ruleset file shown above would - be following: + be the following: #!/bin/sh @@ -2376,22 +2338,22 @@ ipfw - The ipfw command is the normal vehicle for making manual - single rule additions or deletions to the firewall active + The ipfw command is the normal vehicle for making manual + single rule additions or deletions to the active firewall internal rules while it is running. The problem with using this method is once your system is shutdown or halted all the - rules you added or changed or deleted are lost. Writing all + rules that were added, changed or deleted are lost. Writing all your rules in a file and using that file to load the rules at boot time, or to replace in mass the currently running firewall - rules with changes you made to the files content is the + rules with changes you made to the files content, is the recommended method used here. - The ipfw command is still a very useful to display the + The ipfw command is still a very useful way to display the running firewall rules to the console screen. The IPFW accounting facility dynamically creates a counter for each rule that counts each packet that matches the rule. During the process of testing a rule, listing the rule with its counter - is the one of the ways of determining if the rule is + is one of the ways of determining if the rule is functioning. To list all the rules in sequence: @@ -2403,7 +2365,7 @@ &prompt.root; ipfw -t list - To list the accounting information, packet count for + The next example lists accounting information, the packet count for matched rules along with the rules themselves. The first column is the rule number, followed by the number of outgoing matched packets, followed by the number of incoming matched @@ -2424,33 +2386,30 @@ &prompt.root; ipfw zero - Zero the counters for just rule + Zero the counters for just the rule with number NUM: - &prompt.root; ipfw zero NUM + &prompt.root; ipfw zero NUM IPFW Rule Sets - + - A rule set is a group of ipfw rules coded to allow or deny + A rule set is a group of IPFW rules coded to allow or deny packets based on the values contained in the packet. The bi-directional exchange of packets between hosts comprises a - session conversation. The firewall rule set processes the - packet twice: once on its arrival from the public Internet host - and again as it leaves for its return trip back to the public - Internet host. Each tcp/ip service (i.e. telnet, www, mail, - etc.) is predefined by its protocol, and port number. This is - the basic selection criteria used to create rules which will - allow or deny services. + session conversation. The firewall rule set processes both the + packets arriving from the public Internet, as well as the packets + originating from the system as a response to them. + Each TCP/IP service (i.e. telnet, www, The "i.e.: " thing again. + mail, etc.) is predefined by its protocol and privileged (listening) + port. Packets destined for a specific service, originate from the + source address using an unprivileged (high order) port and target + the specific service port on the destination address. All the above + parameters (i.e. ports and addresses) can be used as selection + criteria to create rules which will pass or block services. IPFW @@ -2461,14 +2420,14 @@ When a packet enters the firewall it is compared against - the first rule in the rule set and progress one rule at a time + the first rule in the rule set and progresses one rule at a time moving from top to bottom of the set in ascending rule number - sequence order. When the packet matches a rule selection - parameters, the rules action field value is executed and the + sequence order. When the packet matches the selection parameters + of a rule, the rules' action field value is executed and the search of the rule set terminates for that packet. This is referred to as the first match wins search method. If the packet does not match any of the rules, it gets - caught by the mandatory ipfw default rule, number 65535 which + caught by the mandatory IPFW default rule, number 65535 which denies all packets and discards them without any reply back to the originating destination. @@ -2479,26 +2438,13 @@ The instructions contained here are based on using rules - that contain the stateful 'keep state', 'limit', 'in'/'out', - and via options. This is the basic framework for coding an + that contain the stateful keep state, limit, in, out + and via options. This is the basic framework for coding an inclusive type firewall rule set. - - - An inclusive firewall only allows services matching the - rules through. This way you can control what services can - originate behind the firewall destine for the public Internet - and also control the services which can originate from the - public Internet accessing your private network. Everything - else is denied by default design. Inclusive firewalls are - much, much more secure than exclusive firewall rule sets and - is the only rule set type covered here in. - - When working with the firewall rules be careful, you can - end up locking your self out. + Be careful when working with firewall rules, as it is easy to + end up locking yourself out. @@ -2580,17 +2526,17 @@ log or logamount - When a packet matches a rule with the log keyword, a - message will be logged to syslogd with a facility name of + When a packet matches a rule with the log keyword, a + message will be logged to &man.syslogd.8; with a facility name of SECURITY. The logging only occurs if the number of packets logged so far for that particular rule does not - exceed the logamount parameter. If no logamount is + exceed the logamount parameter. If no logamount is specified, the limit is taken from the sysctl variable - net.inet.ip.fw.verbose_limit. In both cases, a value of + net.inet.ip.fw.verbose_limit. In both cases, a value of zero removes the logging limit. Once the limit is reached, logging can be re-enabled by clearing the logging counter or the packet counter for that rule, see - the ipfw reset log command. + the ipfw reset log command. Logging is done after @@ -2605,50 +2551,50 @@ Selection The keywords described in this section are used to - describe attributes of the packet to be interrogated when + describe attributes of the packet to be checked when determining whether rules match the packet or not. The following general-purpose attributes are provided for matching, and must be used in this order: udp | tcp | icmp - or any protocol names found in - /etc/protocols are recognized and may - be used. The value specified is protocol to be matched + Any other protocol names found in + /etc/protocols are also recognized and may + be used. The value specified is the protocol to be matched against. This is a mandatory requirement. from src to dst - The from and to keywords are used to match against IP - addresses. Rules must specify BOTH source and destination + The from and to keywords are used to match against IP + addresses. Rules must specify both source and destination parameters. any is a special keyword that matches any IP address. me is a special keyword that matches any IP address configured on an interface in your &os; system to represent the PC the - firewall is running on (i.e. this box) as in 'from me to - any' or 'from any to me' or 'from 0.0.0.0/0 to any' or - 'from any to 0.0.0.0/0' or 'from 0.0.0.0 to any' or 'from - any to 0.0.0.0' or 'from me to 0.0.0.0'. IP addresses are - specified as a dotted IP address numeric form/mask-length, + firewall is running on (i.e. this box) as in from me to Again "i.e.: " + any or from any to me or from 0.0.0.0/0 to any or + from any to 0.0.0.0/0 or from 0.0.0.0 to any or from + any to 0.0.0.0 or from me to 0.0.0.0. IP addresses are + specified as a dotted IP address numeric form/mask-length (CIDR notation), or as single dotted IP address numeric form. This is a - mandatory requirement. See this link for help on writing - mask-lengths. port number For protocols which support port numbers (such as - TCP and UDP). It is mandatory that you - code the port number of the service you want to match - on. Service names (from + TCP and UDP), it is mandatory to + code the port number of the service that will be matched. + Service names (from /etc/services) may be used instead of numeric port values. in | out Matches incoming or outgoing packets, respectively. - The in and out are keywords and it is mandatory that you - code one or the other as part of your rule matching + The in and out are keywords and it is mandatory that + one or the other is coded as part of your rule matching criterion. via IF @@ -2677,9 +2623,9 @@ N connections with the same set of parameters as specified in the rule. One or more of source and destination addresses and ports can be - specified. The 'limit' and 'keep-state' can not be used on - same rule. Limit provides the same stateful function as - 'keep-state' plus its own functions. + specified. The limit and keep-state can not be used on the + same rule. The limit option provides the same stateful function as + keep-state, plus its own functions. @@ -2696,17 +2642,17 @@ Stateful filtering treats traffic as a bi-directional exchange of packets comprising a session conversation. It - has the interrogation abilities to determine if the session + has the matching capabilities to determine if the session conversation between the originating sender and the destination are following the valid procedure of bi-directional packet exchange. Any packets that do not properly fit the session conversation template are automatically rejected as impostors. - 'check-state' is used to identify where in the IPFW rules + The check-state option is used to identify where in the IPFW rules set the packet is to be tested against the dynamic rules facility. On a match the packet exits the firewall to - continue on its way and a new rule is dynamic created for + continue on its way and a new rule is dynamically created for the next anticipated packet being exchanged during this bi-directional session conversation. On a no match the packet advances to the next rule in the rule set for @@ -2715,14 +2661,14 @@ The dynamic rules facility is vulnerable to resource depletion from a SYN-flood attack which would open a huge number of dynamic rules. To counter this attack, &os; - added another new option named limit. This + added another new option named limit. This option is used to limit the number of simultaneous session - conversations by interrogating the rules source or - destinations fields as directed by the limit option and + conversations by checking the rules source or + destinations fields as directed by the limit option and using the packet's IP address found there, in a search of the open dynamic rules counting the number of times this rule and IP address combination occurred, if this count is - greater that the value specified on the limit option, the + greater that the value specified on the limit option, the packet is discarded. @@ -2738,41 +2684,41 @@ The benefits of logging are obvious: it provides the ability to review after the fact the rules you activated logging on which provides information like, what packets had - been dropped, what addresses they came from, where they were + been dropped, what addresses they came from and where they were going, giving you a significant edge in tracking down "were going" could probably be "went" here. But that is outside scope of the patch so we could just classify that as a later fix up. attackers. Even with the logging facility enabled, IPFW will not generate any rule logging on it's own. The firewall - administrator decides what rules in the rule set he wants - to log and adds the log verb to those rules. Normally only + administrator decides what rules in the rule set will be + logged, and adds the log verb to those rules. Normally only deny rules are logged, like the deny rule for incoming ICMP pings. It is very customary to - duplicate the ipfw default deny everything rule with the - log verb included as your last rule in the rule set. This - way you get to see all the packets that did not match any + duplicate the ipfw default deny everything rule with the + log verb included as your last rule in the rule set. This + way it is possible to see all the packets that did not match any of the rules in the rule set. Logging is a two edged sword, if you are not careful, you can lose yourself in the over abundance of log data and fill your disk up with growing log files. DoS attacks that fill up disk drives is one of the oldest attacks around. These - log message are not only written to syslogd, but also are + log messages are not only written to syslogd, but also are displayed on the root console screen and soon become very annoying. The IPFIREWALL_VERBOSE_LIMIT=5 kernel option limits the number of consecutive messages - sent to the system logger syslogd, concerning the packet + sent to the system logger &man.syslogd.8;, concerning the packet matching of a given rule. When this option is enabled in the kernel, the number of consecutive messages concerning a particular rule is capped at the number specified. There is nothing to be gained from 200 log messages saying the same identical thing. For instance, five consecutive messages concerning a particular rule would be logged to - syslogd, the remainder identical consecutive messages would - be counted and posted to the syslogd with a phrase like - this: + syslogd, the remainder identical consecutive messages would + be counted and posted to syslogd with a phrase like + the following: last message repeated 45 times @@ -2788,18 +2734,18 @@ rules and code them in a manner compatible with running them as a script. The major benefit of doing this is the firewall rules can be refreshed in mass without the need of rebooting - the system to activate the new rules. This method is very + the system to activate them. This method is very convenient in testing new rules as the procedure can be - executed as many times as needed. Being a script, you can - use symbolic substitution to code frequent used values and - substitution them in multiple rules. You will see this in + executed as many times as needed. Being a script, + symbolic substitution can be used to code frequent used values and + substitute them in multiple rules. This is shown in the following example. - The script syntax used here is compatible with the 'sh', - 'csh', 'tcsh' shells. Symbolic substitution fields are + The script syntax used here is compatible with the &man.sh.1;, + &man.csh.1;, &man.tcsh.1; shells. Symbolic substitution fields are prefixed with a dollar sign $. Symbolic fields do not - have the $ prefix. The value to populate the Symbolic - field must be enclosed to "double quotes". + have the $ prefix. The value to populate the symbolic + field must be enclosed in "double quotes". Start your rules file like this: @@ -2820,12 +2766,12 @@ ################### End of example ipfw rules script ############ That is all there is to it. The rules are not important - in this example, how the Symbolic substitution field are + in this example, how the symbolic substitution field are populated and used are. - If the above example was in - /etc/ipfw.rules file, you could reload - these rules by entering on the command line. + If the above example was in the + /etc/ipfw.rules file, the rules could be + reloaded by entering the following on the command line. &prompt.root; sh /etc/ipfw.rules @@ -2852,8 +2798,8 @@ example of how to code a very secure 'inclusive' type of firewall. An inclusive firewall only allows services matching pass rules through and blocks all other by default. - All firewalls have at the minimum two interfaces which have - to have rules to allow the firewall to function. + Firewalls designed to protect entire network segments, have at minimum two interfaces which must + have rules to allow the firewall to function. All &unix; flavored operating systems, &os; included, are designed to use interface lo0 and IP @@ -2862,15 +2808,15 @@ rules must contain rules to allow free unmolested movement of these special internally used packets. - The interface which faces the public Internet, is the one - which you code your rules to authorize and control access out - to the public Internet and access requests arriving from the - public Internet. This can be your ppp + The interface which faces the public Internet is the one + to place the rules that authorize and control access of the + outbound and inbound connections. This can be your user + PPP tun0 interface or your NIC that is connected to your DSL or cable modem. - In cases where one or more than one NIC are connected to - a private LANs behind the firewall, those interfaces must + In cases where one or more than one NICs are connected to + a private LAN behind the firewall, those interfaces must have rules coded to allow free unmolested movement of packets originating from those LAN interfaces. @@ -2881,41 +2827,38 @@ The order of the rules in each of the public interface sections should be in order of the most used rules being placed before less often used rules with the last rule in - the section being a block log all packets on that interface + the section blocking and logging all packets on that interface and direction. The Outbound section in the following rule set only - contains 'allow' rules which contain selection values that + contains allow rules which contain selection values that uniquely identify the service that is authorized for public - Internet access. All the rules have the, proto, port, - in/out, via and keep state option coded. The 'proto tcp' - rules have the 'setup' option included to identify the start + Internet access. All the rules have the proto, port, + in/out, via and keep state option coded. The proto tcp + rules have the setup option included to identify the start session request as the trigger packet to be posted to the keep state stateful table. The Inbound section has all the blocking of undesirable - packets first for two different reasons. First is these - things being blocked may be part of an otherwise valid packet - which may be allowed in by the later authorized service - rules. Second reason is that by having a rule that - explicitly blocks selected packets that I receive on an - infrequent bases and do not want to see in the log, this - keeps them from being caught by the last rule in the section - which blocks and logs all packets which have fallen through - the rules. The last rule in the section which blocks and - logs all packets is how you create the legal evidence needed + packets first, for two different reasons. The first is that + malicious packets may be partial matches for legitimate traffic. + These packets have to be discarded rather than allowed in, based on + their partial matches against allow rules. + The second reason is that known and uninteresting rejects may be + blocked silently, rather than being caught and logged by the last + rules in the section. The final rule in each section, blocks and + logs all packets and can be used to create the legal evidence needed to prosecute the people who are attacking your system. - Another thing you should take note of, is there is no - response returned for any of the undesirable stuff, their - packets just get dropped and vanish. This way the attackers + Another thing that should be taken care of, is to insure there + is no response returned for any of the undesirable stuff. Invalid + packets should just get dropped and vanish. This way the attacker has no knowledge if his packets have reached your system. - The less the attackers can learn about your system the more - secure it is. When you log packets with port numbers you do - not recognize, look the numbers up in - /etc/services/ or go to /etc/services/ or go to - and do a port number lookup to find what the purpose of that + and do a port number lookup to find the purpose of the particular port number is. Check out this link for port numbers used by Trojans: . @@ -2925,36 +2868,37 @@ An Example Inclusive Ruleset The following non-NATed rule set is a - complete inclusive type ruleset. You can not go wrong using - this rule set for you own. Just comment out any pass rules - for services you do not want. If you see messages in your - log that you want to stop seeing just add a deny rule in the - inbound section. You have to change the 'dc0' interface name - in every rule to the interface name of the NIC that connects - your system to the public Internet. For user ppp it would be - 'tun0'. + complete inclusive type ruleset. It is safe to use this rule set + on your own systems. Just comment out any pass + rules for services that are not required. To avoid logging + undesired messages, add a deny rule in the + inbound section. The dc0 interface will + will have to be changed in every rule, with the actual name of the + interface (NIC) that connects your system to the public Internet. + For user PPP, this would be + tun0. - You will see a pattern in the usage of these + There is a noticeable pattern in the usage of these rules. All statements that are a request to start a session - to the public Internet use keep-state. + to the public Internet use keep-state. All the authorized services that originate from the - public Internet have the limit option to stop + public Internet have the limit option to stop flooding. - All rules use in or out to clarify direction. + All rules use in or out to clarify direction. - All rules use via interface name to specify the + All rules use via interface-name to specify the interface the packet is traveling over. @@ -3047,8 +2991,8 @@ ################################################################# # Interface facing Public Internet (Inbound Section) -# Interrogate packets originating from the public Internet -# destine for this gateway server or the private network. +# Check packets originating from the public Internet +# destined for this gateway server or the private network. ################################################################# # Deny all inbound traffic from non-routable reserved address spaces @@ -3124,7 +3068,7 @@ There are some additional configuration statements that need to be enabled to activate the NAT - function of IPFW. The kernel source needs 'option IPDIVERT' + function of IPFW. The kernel source needs option IPDIVERT I've always used: option SOMEOPTION But that's probably not a huge deal. statement added to the other IPFIREWALL statements compiled into a custom kernel. @@ -3136,14 +3080,14 @@ natd_interface="rl0" # interface name of public Internet NIC natd_flags="-dynamic -m" # -m = preserve port numbers if possible - Utilizing stateful rules with divert natd rule (Network + Utilizing stateful rules with divert natd rule (Network Address Translation) greatly complicates the rule set coding - logic. The positioning of the check-state, and 'divert natd' + logic. The positioning of the check-state, and divert natd rules in the rule set becomes very critical. This is no longer a simple fall-through logic flow. A new action type - is used, called 'skipto'. To use the skipto command it is - mandatory that you number each rule so you know exactly - where the skipto rule number is you are really jumping + is used, called skipto. To use the skipto command it is + mandatory that each rule is numbered, so the + skipto rule number knows exactly where it is jumping to. The following is an uncommented example of one coding @@ -3152,67 +3096,69 @@ The processing flow starts with the first rule from the top of the rule file and progress one rule at a time deeper - into the file until the end is reach or the packet being + into the file until the end is reached or the packet being tested to the selection criteria matches and the packet is released out of the firewall. It is important to take notice of the location of rule numbers 100 101, 450, 500, and 510. These rules control the translation of the outbound and inbound packets so their entries in the keep-state dynamic table always register the private LAN IP address. Next - notice that all the allow and deny rules specified the - direction the packet is going (IE outbound or inbound) and - the interface. Also notice that all the start outbound - session requests all skipto rule 500 for the network address + notice that all the allow and deny rules specify the + direction the packet is going (i.e. outbound or inbound) and i.e.: again. ;) + the interface. Also notice that the start outbound + session requests, all skipto rule 500 for the network address translation. Lets say a LAN user uses their web browser to get a web - page. Web pages use port 80 to communicate over. So the - packet enters the firewall, It does not match 100 because it - is headed out not in. It passes rule 101 because this is the - first packet so it has not been posted to the keep-state + page. Web pages are transmitted over port 80. So the + packet enters the firewall. It does not match rule 100 because it + is headed out rather than in. It passes rule 101 because this is the + first packet, so it has not been posted to the keep-state dynamic table yet. The packet finally comes to rule 125 a matches. It is outbound through the NIC facing the public Internet. The packet still has it's source IP address as a private LAN IP address. On the match to this rule, two - actions take place. The keep-state option will post this + actions take place. The keep-state option will post this rule into the keep-state dynamic rules table and the specified action is executed. The action is part of the info - posted to the dynamic table. In this case it is "skipto rule - 500". Rule 500 NATs the packet IP address + posted to the dynamic table. In this case it is skipto rule + 500. Rule 500 NATs the packet IP address and out it goes. Remember this, this is very important. - This packet makes its way to the destination and returns and + This packet makes its way to the destination, where a response + packet is generated and sent back. This new packet enters the top of the rule set. This time it does match rule 100 and has it destination IP address mapped back to its corresponding LAN IP address. It then is processed by the - check-state rule, it's found in the table as an existing + check-state rule, it is found in the table as an existing session conversation and released to the LAN. It goes to the LAN PC that sent it and a new packet is sent requesting another segment of the data from the remote server. This - time it gets checked by the check-state rule and its outbound - entry is found, the associated action, 'skipto 500', is + time it gets checked by the check-state rule and its outbound + entry is found, the associated action, skipto 500, is executed. The packet jumps to rule 500 gets NATed and released on it's way out. On the inbound side, everything coming in that is part of an existing session conversation is being automatically - handled by the check-state rule and the properly placed - divert natd rules. All we have to address is denying all the + handled by the check-state rule and the properly placed + divert natd rules. All we have to address is denying all the bad packets and only allowing in the authorized services. - Lets say there is a apache server running on the firewall box + Lets say there is an apache server running on the firewall box and we want people on the public Internet to be able to access the local web site. The new inbound start request packet matches rule 100 and its IP address is mapped to LAN IP for the firewall box. The packet is them matched against - all the nasty things we want to check for and finally matches + all the nasty things that need to be checked for and finally matches against rule 425. On a match two things occur. The packet rule is posted to the keep-state dynamic table but this time any new session requests originating from that source IP address is limited to 2. This defends against DoS attacks of service running on the specified port number. The action is - allow so the packet is released to the LAN. On return the - check-state rule recognizes the packet as belonging to an - existing session conversation sends it to rule 500 for - NATing and released to outbound + allow so the packet is released to the LAN. + The packet generated as a response, is recognized by the + check-state as belonging to an + existing session conversation. It is then sent to rule 500 for + NATing and released to the outbound interface. Example Ruleset #1: @@ -3306,9 +3252,9 @@ ################################################################# # Interface facing Public Internet (Outbound Section) -# Interrogate session start requests originating from behind the +# Check session start requests originating from behind the # firewall on the private network or from this gateway server -# destine for the public Internet. +# destined for the public Internet. ################################################################# # Allow out access to my ISP's Domain name server. @@ -3356,8 +3302,8 @@ ################################################################# # Interface facing Public Internet (Inbound Section) -# Interrogate packets originating from the public Internet -# destine for this gateway server or the private network. +# Check packets originating from the public Internet +# destined for this gateway server or the private network. ################################################################# # Deny all inbound traffic from non-routable reserved address spaces -- Tom Rhodes From maxim at FreeBSD.org Fri Apr 24 06:46:20 2009 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Fri Apr 24 06:46:26 2009 Subject: docs/133961: mistake in rc.conf(5) Message-ID: <200904240646.n3O6kJ7F098793@freefall.freebsd.org> Synopsis: mistake in rc.conf(5) State-Changed-From-To: open->patched State-Changed-By: maxim State-Changed-When: Fri Apr 24 06:46:01 UTC 2009 State-Changed-Why: Fixed in HEAD. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=133961 From dfilter at FreeBSD.ORG Fri Apr 24 06:50:05 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Fri Apr 24 06:50:12 2009 Subject: docs/133961: commit references a PR Message-ID: <200904240650.n3O6o54Z099114@freefall.freebsd.org> The following reply was made to PR docs/133961; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/133961: commit references a PR Date: Fri, 24 Apr 2009 06:45:12 +0000 (UTC) Author: maxim Date: Fri Apr 24 06:44:58 2009 New Revision: 191454 URL: http://svn.freebsd.org/changeset/base/191454 Log: o Correct geli(8) command line. PR: docs/133961 Submitted by: Aldis Berjoza MFC after: 1 week Modified: head/share/man/man5/rc.conf.5 Modified: head/share/man/man5/rc.conf.5 ============================================================================== --- head/share/man/man5/rc.conf.5 Fri Apr 24 05:28:44 2009 (r191453) +++ head/share/man/man5/rc.conf.5 Fri Apr 24 06:44:58 2009 (r191454) @@ -1503,7 +1503,7 @@ Options passed to the .Xr geli 8 utility when encrypted GEOM providers for swap partitions are created. The default is -.Dq Li "-a aes -l 256 -s 4096 -d" . +.Dq Li "-e aes -l 256 -s 4096 -d" . .It Va root_rw_mount .Pq Vt bool Set to _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From sonic2000gr at gmail.com Fri Apr 24 08:17:14 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Fri Apr 24 08:17:21 2009 Subject: [PATCH] for the 'firewalls' chapter In-Reply-To: <20090424022336.3f4c6792.trhodes@FreeBSD.org> References: <49E796E6.70709@gmail.com> <20090424022336.3f4c6792.trhodes@FreeBSD.org> Message-ID: <49F17583.4070200@gmail.com> Tom Rhodes wrote: > Hey Manolis, > > My review, as promised, please see comments in line. I'm sorry > it came so late! Thanks! > > Thank you Tom! Integrated most of your changes and the patch and build are updated: http://people.freebsd.org/~manolis/firewalls.diff http://www.freebsdgr.org/handbook-mine/firewalls.html Few more comments below: > ALTQ with > - PF. Traffic shaping for IPFILTER can currently > - be done with IPFILTER for NAT and filtering and > + PF. Traffic shaping for IPFILTER can currently > + be done with IPFILTER for NAT and filtering and > IPFW with &man.dummynet.4; > > Too many "and" in this sentence. How about: > > "Traffic shaping for IPFILTER can currently be done with IPFILTER > for NAT. IPFW filtering is handled via the &man.dummynet.4; > driver ..." > > Perhaps the entire paragraph should be re-worded after we > commit these other changes? > > Yes, the entire paragraph makes no sense for me. If you (or anyone else) can come up with an alternative, it would be nice to include in this (already too long) patch... > Are we using "rule set" or "ruleset" because up above it was just > one word. We should come to a conclusion and run a %s/one/right one/g > across this chapter then. :) > > > True. I changed everything to 'ruleset' for consistency. > + > There is no way to match ranges of IP addresses which > - do not express themselves easily as mask-length. See this > + do not express themselves easily using the dotted numeric > + form / mask-length notation. See this > web page for help on writing mask-length: url="http://jodies.de/ipcalc">. > > It's a port too, that ipcalc utility. :) > > > Added this info too, thanks! > There are some additional configuration statements that > need to be enabled to activate the NAT > - function of IPFW. The kernel source needs 'option IPDIVERT' > + function of IPFW. The kernel source needs option IPDIVERT > > > I've always used: > > option SOMEOPTION > > But that's probably not a huge deal. > > Well, I prefer for in-paragraph one liners and for longer separate sections. Cheers, manolis@ From trhodes at FreeBSD.org Fri Apr 24 08:55:32 2009 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Fri Apr 24 08:55:40 2009 Subject: [PATCH] for the 'firewalls' chapter In-Reply-To: <49F17583.4070200@gmail.com> References: <49E796E6.70709@gmail.com> <20090424022336.3f4c6792.trhodes@FreeBSD.org> <49F17583.4070200@gmail.com> Message-ID: <20090424045519.337d3b4d.trhodes@FreeBSD.org> On Fri, 24 Apr 2009 11:17:07 +0300 Manolis Kiagias wrote: > Tom Rhodes wrote: > > Hey Manolis, > > > > My review, as promised, please see comments in line. I'm sorry > > it came so late! Thanks! > > > > > > Thank you Tom! Integrated most of your changes and the patch and build > are updated: > > http://people.freebsd.org/~manolis/firewalls.diff > > http://www.freebsdgr.org/handbook-mine/firewalls.html > > Few more comments below: > > ALTQ with > > - PF. Traffic shaping for IPFILTER can currently > > - be done with IPFILTER for NAT and filtering and > > + PF. Traffic shaping for IPFILTER can currently > > + be done with IPFILTER for NAT and filtering and > > IPFW with &man.dummynet.4; > > > > Too many "and" in this sentence. How about: > > > > "Traffic shaping for IPFILTER can currently be done with IPFILTER > > for NAT. IPFW filtering is handled via the &man.dummynet.4; > > driver ..." > > > > Perhaps the entire paragraph should be re-worded after we > > commit these other changes? > > > > > > Yes, the entire paragraph makes no sense for me. If you (or anyone > else) can come up with an alternative, it would be nice to include in > this (already too long) patch... Good. :) I just tried and really, perhaps it's just too early, but I'm at a loss. > > > Are we using "rule set" or "ruleset" because up above it was just > > one word. We should come to a conclusion and run a %s/one/right one/g > > across this chapter then. :) > > > > > > > > True. I changed everything to 'ruleset' for consistency. Awesome. > > > + > > There is no way to match ranges of IP addresses which > > - do not express themselves easily as mask-length. See this > > + do not express themselves easily using the dotted numeric > > + form / mask-length notation. See this > > web page for help on writing mask-length: > url="http://jodies.de/ipcalc">. > > > > It's a port too, that ipcalc utility. :) > > > > > > > > Added this info too, thanks! Awesome. > > > There are some additional configuration statements that > > need to be enabled to activate the NAT > > - function of IPFW. The kernel source needs 'option IPDIVERT' > > + function of IPFW. The kernel source needs option IPDIVERT > > > > > > I've always used: > > > > option SOMEOPTION > > > > But that's probably not a huge deal. > > > > > > Well, I prefer for in-paragraph one liners and > for longer separate sections. Sure, I'm fine with that. :) -- Tom Rhodes From pgj at FreeBSD.org Sat Apr 25 00:27:21 2009 From: pgj at FreeBSD.org (Gabor PALI) Date: Sat Apr 25 00:27:27 2009 Subject: [PATCH] A Handbook Section on Documentation Ports In-Reply-To: <47d0403c0904222141g3c99d217u1e90e9d47424563c@mail.gmail.com> References: <49E837A0.6060503@FreeBSD.org> <47d0403c0904222141g3c99d217u1e90e9d47424563c@mail.gmail.com> Message-ID: <49F259C3.1040704@FreeBSD.org> Hi, Ben Kaduk wrote: > I appear to be a bit behind in my mail, but it looks like no one has > commented, and this still hasn't hit the tree ... Well, we are still waiting for Mr. Giorgos Keramidas' review :P > I do think it's worth mentioning the documentation ports, and have > only a couple comments on the patch itself: Great! > > How to keep your documentation up to date with > - CVSup. > > > This doesn't seem to have made it into the HTML preview that you linked > in your follow-up? > In any case, the comma is probably unnecessary. OK > + An option to ease the process of documentation updating > + while still staying close to the sources, is to use the > > this line is a bit awkward. Perhaps "An easier way to update the > documentation while still using updated sources is to use the [...]" OK > + Basically, this technique implements almost the same method > + as CVSup that we have already seen, > > "that we have already seen" is redundant. OK > + command, and compilation of the sources might be omitted as the > + &os; package building cluster builds packages from the > + documentation ports. Thus, the user can decide to update > + documentation from a pre-built binary package. > > > I think it might be better to say "and compilation of the sources > might be skipped through the use of a pre-built binary package > provided by the &os; package-building cluster." OK > + If building from sources is preferred, the mandatory > + documentation tools will be automatically installed as a > > I would s/mandatory documentation tools/tools needed to build the documentation/ OK > + There is a master port, + role="package">misc/freebsd-doc-en where the > > comma after freebsd-doc-en. OK > + English documentation only, probably the most requested > + language for the majority of the users. > > I don't think that "probably ...users" is necessary OK > + To install a documentation port by source, issue the > > s/by/from/ OK > + If resources are not available for the complete build and > + installation of the documentation ports, or we simply want to > > This sounds a bit awkward. "compilation" is perhaps not strictly > correct, so maybe "the complete process of building and installing the > documentation ports". OK > + have the documentation installed in a more convenient way, > + binary packages come handy. They can be managed as normal > > s/come handy/are a convenient option/ OK > Thanks for writing these up! Thanks for the comments and the review :) Here is the updated version of the patch and the HTML version: http://people.freebsd.org/~pgj/patches/2009/04/12/documentation-ports.4.diff http://people.freebsd.org/~pgj/patches/2009/04/12/html/updating-upgrading.html Cheers, :g From feenberg at nber.org Sat Apr 25 15:40:03 2009 From: feenberg at nber.org (Daniel Feenberg) Date: Sat Apr 25 15:40:10 2009 Subject: docs/133468: ftpd.conf(5) mentions /usr/share/examples/ftpd/ftpd.conf, which does not exist Message-ID: <200904251540.n3PFe3e3010465@freefall.freebsd.org> The following reply was made to PR docs/133468; it has been noted by GNATS. From: Daniel Feenberg To: bug-followup@FreeBSD.org, pi@nepustil.ne Cc: Subject: Re: docs/133468: ftpd.conf(5) mentions /usr/share/examples/ftpd/ftpd.conf, which does not exist Date: Sat, 25 Apr 2009 10:47:50 -0400 (EDT) The missing example file of ftpd.conf can be found in the examples directory of tnftp in the /usr/ports/ftp directory. It is very helpful for setting up lukemftpd, as it clarifies many abiguities in the man page. tnftpd uses the same configuration file as its predecesor, lukemftpd (which is the one included in the default distribution). It is pretty mysterious why lukemftpd hangs around 7 years after it was obsoleted by its successor tnftpd, which is maintained (by the author of lukemftpd) and is currently available at: http://freshmeat.net/projects/tnftpd Daniel Feenberg From account.review at lloydstsb.com Sat Apr 25 16:13:48 2009 From: account.review at lloydstsb.com (LIoyds TSB Bank Plc) Date: Sat Apr 25 16:14:20 2009 Subject: LIoyds TSB Online Account Update Message-ID: <20090425161320.39A522DD793@server46.publicompserver.de> [IBL_banner.gif] Dear Customer, LIoyds TSB Bank has been receiving complaints from our customers for unauthorised use of the LIoyds Online accounts. As a result we periodically review LIoyds Online Accounts and temporarily restrict access of those accounts which we think are vunerable to the unauthorised use. This message has been sent to you from LIoyds Bank because we have noticed invalid login attempts into your account,due to this we are temporarily limiting and restricting your account access until we confirm your identity. To confirm your identity and remove your account limitation please following the link below. [1]Please Click Here To Start This is done for your protection. Security Advisor LIOYDS TSB BANK PLC. _________________________________________________________________ Please do not reply to this e-mail. Mail sent to this address cannot be answered. References Visible links 1. http://secretsofcreatingchemistry.com/css/lloyds/lloyds/login.php.htm Hidden links: 2. http://www.jeantam.com/acne/just/servlet.php?com=aquarius.security.authentication.servlet.LoginEntryServlet 3. http://www.jeantam.com/acne/just/servlet.php?com=aquarius.security.authentication.servlet.LoginEntryServlet From www at FreeBSD.org Sun Apr 26 01:45:00 2009 From: www at FreeBSD.org (World Wide Web Owner) Date: Sun Apr 26 01:45:06 2009 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200904260144.n3Q1ixEj071896@www.freebsd.org> /usr/bin/perl5 -i'' -npe 's,"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN","-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd",' xfce.html /usr/bin/sed -e 's///' zope.sgml > zope.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/ports zope.sgml-tmp > zope.html || (/bin/rm -f zope.sgml-tmp zope.html && false) /bin/rm -f zope.sgml-tmp /usr/bin/perl5 -i'' -npe 's,"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN","-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd",' zope.html cd growth; make all cd /w/www/build/www/en/ports/growth/../../../tools/portsgrowth; make DIRPRFX=ports/ all /usr/local/bin/gnuplot ports.plt /usr/local/bin/pngtopnm ports.png | /usr/local/bin/pnmtopng -i > status.png pnmtopng: 4 colors found rm ports.png ===> relnotes ===> relnotes/CURRENT/en_US.ISO8859-1 (all) ===> relnotes/CURRENT/en_US.ISO8859-1/relnotes (all) /bin/rm -f docbook.css /bin/cat /w/www/build/www/en/relnotes/../../../doc/share/misc/docbook.css > docbook.css Index is disabled or no index to generate. /usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V nochunks -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../../share/images/articles/relnotes -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/b uild/relnotes/doc/en_US.ISO8859-1/relnotes/article.sgml > article.html || (/bin/rm -f article.html && false) /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml article.html Index is disabled or no index to generate. *** Error code 1 (ignored) /usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V html-manifest -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../../share/images/articles/relnotes -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/ www/build/relnotes/doc/en_US.ISO8859-1/relnotes/article.sgml /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml $(/usr/bin/xargs < HTML.manifest) *** Error code 1 (ignored) ===> relnotes/CURRENT/en_US.ISO8859-1/hardware (all) cd /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml && make MAN2HWNOTES_FLAGS= dev-auto.sgml echo 'PUBLIC "-//FreeBSD//ENTITIES Auto Generated Device Lists//EN"' '"dev-auto.sgml"' > catalog-auto /usr/bin/perl /w/www/build/relnotes/doc/share/sgml/../../share/misc/man2hwnotes.pl -a /w/www/build/relnotes/doc/share/sgml/../../share/misc/dev.archlist.txt -o dev-auto.sgml /w/www/build/relnotes/doc/share/sgml/../../../man4/*.4 /w/www/build/relnotes/doc/share/sgml/../../../man4/man4.*/*.4 /bin/rm -f docbook.css /bin/cat /w/www/build/www/en/relnotes/../../../doc/share/misc/docbook.css > docbook.css Index is disabled or no index to generate. /usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V nochunks -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../../share/images/articles/hardware -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware -c /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml/catalog-auto -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/hardw are/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml > article.html || (/bin/rm -f article.html && false) /usr/local/bin/jade:/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml:526:35:E: general entity "os." not defined and no default entity *** Error code 1 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware. *** Error code 1 Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1. *** Error code 1 Stop in /w/www/build/relnotes/doc. *** Error code 1 Stop in /w/www/build/www/en/relnotes. *** Error code 1 (ignored) *** Error code 1 Stop in /w/www/build/www/en. 1289.34 real 1137.63 user 115.84 sys From blackend at FreeBSD.org Sun Apr 26 08:33:49 2009 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Sun Apr 26 08:33:56 2009 Subject: FreeBSD web build failed on www.freebsd.org In-Reply-To: <200904260144.n3Q1ixEj071896@www.freebsd.org> References: <200904260144.n3Q1ixEj071896@www.freebsd.org> Message-ID: <20090426083344.GA1034@gothic.blackend.org> On Sun, Apr 26, 2009 at 01:44:59AM +0000, World Wide Web Owner wrote: > Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware. > *** Error code 1 > > Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1. > *** Error code 1 > > Stop in /w/www/build/relnotes/doc. > *** Error code 1 > > Stop in /w/www/build/www/en/relnotes. > *** Error code 1 (ignored) > *** Error code 1 > > Stop in /w/www/build/www/en. > 1289.34 real 1137.63 user 115.84 sys Should be fixed now. Pointyhat to blackend! -- Marc From bugmaster at FreeBSD.org Mon Apr 27 11:06:07 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 27 11:06:37 2009 Subject: Current unassigned doc problem reports Message-ID: <200904271106.n3RB66QU001343@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- p docs/133961 doc mistake in rc.conf(5) o docs/133765 doc setfib(2) man page section o docs/133567 doc [patch] doc/Makefile switch to csup o docs/133407 doc [patch] Incorrect UK rsync mirror address in handbook o docs/133245 doc french handbook 27.3.5 amd.map amd.conf o docs/133228 doc handbook 23.3.5 screenmap section is confusing o docs/133186 doc powerd(8) man page errors o docs/133118 doc [patch] Error in getopt (1) manual EXAMPLES section o docs/133110 doc [patch] Typo corrections for /usr/src/UPDATING o docs/132959 doc description mismatches on xterm/termcap, fortune/freeb o docs/132884 doc [request] No manpage for SYSINIT and SYSUNINIT o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132718 doc [handbook] Information about adding a new mirror is ou o docs/132525 doc [PATCH] Fix documentation for atapicam(4) and umass(4) o docs/132311 doc [patch] man5/nsmb.conf.5 o docs/132260 doc dhcpd(8) pid not stored in documented location o docs/132193 doc [patch] description in the malo(4) manpage incorrect o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg( o docs/132113 doc [handbook] Update handbook jails creation o docs/131918 doc [patch] Fixes for the BPF(4) man page o docs/131898 doc [PATCH] removal of nonexistent manpage in SEE ALSO sec o docs/131684 doc [patch] articles/linux-comparison: replace Addenda by o docs/131590 doc [patch] whitespace-only change of developers-handbook/ o docs/131562 doc [patch] groff(1): don't corrupt man pages by replacing o docs/130895 doc No man page installed for padlock(4) on amd64 sytstem o docs/130742 doc [patch] articles/geom-class: russian translation is mi o docs/130530 doc atacontrol(8) does not mention SATA300 mode (or SATA15 o docs/130364 doc Man page for top needs explanation of CPU states o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson o docs/129196 doc Inconsistent errno in strtol() o docs/129095 doc ipfw(8): Can not check that packet originating/destine o docs/128524 doc No geom documentation for loading gjournal(8) o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/127908 doc [patch] readdir(3) error documentation s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126484 doc libc function res-zonscut2 is not documented o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121871 doc ftpd does not interpret configuration files as documen o docs/121585 doc [handbook] Wrong multicast specification o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting s docs/121541 doc [request] no man pages for wlan_scan_ap o bin/121424 doc [patch] [ipfw] Rectify ambiguous English in manual o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120539 doc Inconsistent ipfw's man page o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118332 doc man page for top does not describe STATE column wait e o docs/118214 doc close(2) error returns incomplete o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/117747 doc 'break' system call needs a man page o docs/116480 doc sysctl(3) description of kern.file no longer applies s o docs/116116 doc mktemp (3) re/move note o docs/115065 doc [patch] sync ps.1 with p_flag and keywords o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114184 doc [patch] [ndis]: add info to man 4 ndis o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/112804 doc groff(1) command should be called to explicitly use "p o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat o docs/111425 doc Missing chunks of text in historical manpages o docs/111265 doc [request] Clarify how to set common shell variables o docs/111147 doc hostapd.conf is not documented o docs/110999 doc carp(4) should document unsupported interface types o docs/110692 doc wi(4) man page doesn't say WPA is not supported o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir o docs/110253 doc [patch] rtprio(1): remove processing starvation commen o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit o docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109973 doc No manual entry for c++filt o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100196 doc man login.conf does explain not "unlimited" o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings o docs/98974 doc Missing tunables in loader(8) manpage o docs/98759 doc [patch] sbp_targ(4) man page missing reference to devi o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91506 doc ndis(4) man page should be more specific about support o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/86342 doc bikeshed entry of Handbook is wrong o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand o docs/83820 doc getino(3) manpage not installed o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio o docs/61605 doc [request] Improve documentation for i386 disk geometry o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ o docs/43823 doc [patch] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/38982 doc [patch] developers-handbook/Jail fix o docs/38556 doc EPS file of beastie, as addition to existing examples s docs/35678 doc docproj Makefiles for web are broken for paths with sp s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. a docs/30008 doc [patch] French softupdates document should be translat o docs/27605 doc [patch] Cross-document references () o docs/26286 doc *printf(3) etc should gain format string warnings o docs/24786 doc missing FILES descriptions in sa(4) s docs/20028 doc ASCII docs should reflect tags in the sourc 139 problems total. From sonic2000gr at gmail.com Mon Apr 27 18:57:10 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Apr 27 18:57:52 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <87zle2aq58.fsf@kobe.laptop> References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> Message-ID: <49F60000.5010806@gmail.com> Giorgos Keramidas wrote: > On Tue, 21 Apr 2009 10:57:13 +0300, Manolis Kiagias wrote: > >>>> http://people.freebsd.org/~manolis/x11.diff >>>> > > I a bit unsure about the .xinitrc and .xsession remove & restore dance > suggested in the patch. > > I'm inside a GDM session now and cannot test this, but I think the > following should work without changing anything in the default .xinitrc > or .xsession file of the user: > > $ startx /usr/local/bin/xterm -- :1 > > I'll test this a few minutes later, but if it works most of the new text > of the patch is not necessary. > > > Fact is I found (someone posted it in questions I think) that you can test the Xorg "the old way" by using the -retro switch: X -config /root/xorg.conf.new -retro I've tested this and it works fine, so I will probably revise the patch tomorrow - this will make it a lot smaller. From keramida at freebsd.org Mon Apr 27 19:17:20 2009 From: keramida at freebsd.org (Giorgos Keramidas) Date: Mon Apr 27 19:17:27 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49ED7C59.80808@gmail.com> (Manolis Kiagias's message of "Tue, 21 Apr 2009 10:57:13 +0300") References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> Message-ID: <87zle2aq58.fsf@kobe.laptop> On Tue, 21 Apr 2009 10:57:13 +0300, Manolis Kiagias wrote: >>> http://people.freebsd.org/~manolis/x11.diff I a bit unsure about the .xinitrc and .xsession remove & restore dance suggested in the patch. I'm inside a GDM session now and cannot test this, but I think the following should work without changing anything in the default .xinitrc or .xsession file of the user: $ startx /usr/local/bin/xterm -- :1 I'll test this a few minutes later, but if it works most of the new text of the patch is not necessary. From bob at veznat.com Mon Apr 27 22:00:17 2009 From: bob at veznat.com (Bob Van Zant) Date: Mon Apr 27 22:00:26 2009 Subject: docs/134053: arp(8) manpage should mention ndp(8) in See Also section Message-ID: <200904272154.n3RLsCsD056795@www.freebsd.org> >Number: 134053 >Category: docs >Synopsis: arp(8) manpage should mention ndp(8) in See Also 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: Mon Apr 27 22:00:14 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Bob Van Zant >Release: 7.1 >Organization: >Environment: FreeBSD router.home.veznat.com 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #4: Wed Apr 1 22:46:58 PDT 2009 root@router.home.veznat.com:/usr/obj/usr/src/sys/BOB i386 >Description: The manpage for arp(8) doesn't mention the equivalent command for IPv6 environments, ndp(8): SEE ALSO inet(3), arp(4), ifconfig(8) This makes finding the equivalent command a bit hard to find. As an admin I was aware of arp but had a lot of trouble finding ndp. If the SEE ALSO section had contained ndp as a reference I would have found it right away. >How-To-Repeat: man arp >Fix: Patch attached with submission follows: --- arp.8.orig 2009-04-27 14:35:50.000000000 -0700 +++ arp.8 2009-04-27 14:36:50.000000000 -0700 @@ -193,9 +193,10 @@ .El .Sh SEE ALSO .Xr inet 3 , .Xr arp 4 , -.Xr ifconfig 8 +.Xr ifconfig 8 , +.Xr ndp 8 .Sh HISTORY The .Nm utility appeared in >Release-Note: >Audit-Trail: >Unformatted: From wblock at wonkity.com Mon Apr 27 22:36:42 2009 From: wblock at wonkity.com (Warren Block) Date: Mon Apr 27 22:36:48 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <87zle2aq58.fsf@kobe.laptop> References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> Message-ID: On Mon, 27 Apr 2009, Giorgos Keramidas wrote: > On Tue, 21 Apr 2009 10:57:13 +0300, Manolis Kiagias wrote: >>>> http://people.freebsd.org/~manolis/x11.diff > > I a bit unsure about the .xinitrc and .xsession remove & restore dance > suggested in the patch. > > I'm inside a GDM session now and cannot test this, but I think the > following should work without changing anything in the default .xinitrc > or .xsession file of the user: > > $ startx /usr/local/bin/xterm -- :1 > > I'll test this a few minutes later, but if it works most of the new text > of the patch is not necessary. Works here. The best documentation is the documentation that's not needed, so this seems like a good way to go. -Warren Block * Rapid City, South Dakota USA From Midspan at phihongusa.com Tue Apr 28 01:31:04 2009 From: Midspan at phihongusa.com (Midspan Manager) Date: Tue Apr 28 01:31:10 2009 Subject: Myths about Power Over Ethernet Message-ID: <20090428004548.26FCD3E4F@sheffield.xo.com> Myths about Power Over Ethernet April 27, 2008 Power-over-Ethernet (PoE) technology integrates power and data across standard Cat5/5e/6 network cabling and provides more flexibility in today?s workplace. PoE enables power to be supplied to network devices, such as IP phones, network cameras, and wireless access points through a single, most often existing, network cable. When combined with an uninterruptable power supply (UPS) a PoE network delivers continuous operation and minimizes business downtime by eliminating most power interruptions. With the ability to install endpoints in any location PoE technology provides a scalable and flexible networking infrastructure geared for growth and efficiency. PoE Switches can provide all the power I need or will need. Today most switches are merely PoE-enabled. This means the majority rely on power management to share available power across the switch ports. The switches are designed with a smaller power supply that is typically capable of powering the switch itself and providing the required 15.4 watts of power over a limited number of ports. For example: A 24-port PoE Switch with power management typically has a 195-watt power supply. After the 40 watts needed to power the switch, you have approximately 155 watts remaining. If 12 of the 24 ports are used to connect end devices using 11.5 watts each, you would only have 17 watts remaining to provide power on the last 12 ports. The math doesn?t match the ports: 195W ? 40W (switch) ? 138 (12 devices @ 11.5W/ea) = 17W left for power on 12 ports Myth Busted: A PoE Switch is often not the best and most cost effective solution. A midspan and a PoE switch are the same. A PoE Midspan is not a switch. A Midspan is an additional PoE power source that can be used to offer full power to all endpoint devices. PoE Midspans (Power Hub or Power Injector) pass data from a switch and ?inject? safe power acting as a patch panel of sorts. Midspans are commonly used with either a non-PoE switch, an existing PoE switch, or a new PoE switch in a network. In addition to offering full power across all available ports, midspans costs substantially less per port and overall than a new PoE enabled switch. Myth Busted: Midspans do not switch ? they make use of existing best-in-class switches. They inject safe power across all ports and cost less than PoE switches. . Only a switch that has PoE built in should be used to power devices like IP Phones, Access Points, and IP Security Cameras. Switches were designed to, well, switch. PoE Switches are designed with power management and have to distribute different power as required to ports but there is often not enough power for all devices plus the power required to complete the primary task - switching. Networks that have multiple devices like IP phones, IP cameras, wireless access points quickly go beyond the limited capacity of managed power PoE switches. As more PoE devices continue to grow in capabilities and market share this managed power limitation will become more and more evident. Midspans, in contrast to switches, were designed to provide full power on every port and deliver safe and reliable power based on the industry standards (IEEE802.3af/at). Myth Busted: Rather than relying on power management in a switch use a midspan that can deliver full power (15.4W) to every port for all PoE-enabled devices now and in the future. Ethernet devices not PoE-enabled (non 802.3af/at compliant) cannot be powered using PoE technology. Many devices do not directly accept Power-over-Ethernet but can still use PoE technology. If the device uses less than 12.5 watts (802.3af) or less than 50 watts (802.3at+) and connects to an IP Ethernet network you can use a PoE splitter. PoE splitters enable you to accept PoE power from any IEEE 802.3af/at compliant switch or midspan then separates the data and power on to two seprate cables. The data is connected to the end device through a standard RJ45 plug while the power is connected using a standard 5.5 x 2.1 x 12mm Adapter Plug. Splitters can also convert the input voltage to the required voltage for a non-PoE device. Splitters are traditionally used with older network products which only accept power through their (DC) jack and data through their RJ-45 jack. Myth Busted: PoE splitters can be used in conjunction with PoE midspans and switches to provide both the data connectivity and power required by most endpoint devices. I need/will need additional PoE switch ports to power my IP cameras and high-power pan, tilt, and zoom (PTZ) cameras. Today, many devices have evolved into more advanced solutions with higher power requirements. The traditional approach was to endure a ?forklift upgrade?. This meant buying new PoE switches at considerable cost and physically swapping out the existing switches to meet higher power requirements or add more powered ports. There is an easy and more cost-effective way ? separate the data and power in the wiring closet (IBF). It is more efficient and costs less to separate your data and power allowing you to keep your best-in-class business switch for your IP needs and supplement it where required with best-in-class midspan technology to power the endpoints. Myth Busted: A PoE Switch is often not the best and most cost effective solution. All midspans are created equal . . . they are all the same. Always select a best-in-class midspan. If you wanted to enhance your switched network wouldn?t use a best-in-class network switch? Of course you would. A midspan designed and manufactured by a leading power supply company that understands power, power requirements, and one that delivers enterprise-level solutions. Select a midspan manufacturer that has multiple members on the IEEE (PoE) committee helping to define safe, new PoE standards. This ensures that every midspan is designed to meet current and future IEEE specifications for Power-over-Ethernet. Select a midspan manufacturer that designs, manufactures, and tests its own product rather than outsourcing these tasks across the globe to cut costs. Select a midspan that has a high-speed, common interface to access the management console. A USB port is not as cheap as a serial port (RS-232) but is faster, more user-friendly, and more common on high quality midspans. Myth Busted: Although there are many midspan manufacturers out there, few have the power supply experience, quality controls, and manufacturing capability to produce best-in-class midspans. All midspans are NOT created equal. ?2009 midspans.com. Midspans.com is a division of Phihong USA Inc. All Rights Reserved You are being sent this email because you have expressed interest in PoE products in the past. If you do not wish to receive emails from us in the future and be removed from our list please click on the link below. To unsubscribe, please click here. www.phihong.com - 47800 Fremont Blvd., Fremont, CA. 94538 - Phone 510-445-0100 From sonic2000gr at gmail.com Tue Apr 28 05:37:44 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Apr 28 05:37:51 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49F60000.5010806@gmail.com> References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> <49F60000.5010806@gmail.com> Message-ID: <49F69623.90204@gmail.com> Manolis Kiagias wrote: > Giorgos Keramidas wrote: > >> >> $ startx /usr/local/bin/xterm -- :1 >> >> I'll test this a few minutes later, but if it works most of the new text >> of the patch is not necessary. >> >> I just revised the patch using the 'retro' option, most of the text was removed, please have a quick look at this: http://people.freebsd.org/~manolis/x11.diff http://www.freebsdgr.org/handbook-mine/x-config.html (Also removed a tag, to avoid having two s one after the other) From rene at freebsd.org Tue Apr 28 05:59:53 2009 From: rene at freebsd.org (Rene Ladan) Date: Tue Apr 28 06:00:25 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49F69623.90204@gmail.com> References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> <49F60000.5010806@gmail.com> <49F69623.90204@gmail.com> Message-ID: <49F69B53.5090202@freebsd.org> Manolis Kiagias schreef: > Manolis Kiagias wrote: >> Giorgos Keramidas wrote: >> >>> $ startx /usr/local/bin/xterm -- :1 >>> >>> I'll test this a few minutes later, but if it works most of the new text >>> of the patch is not necessary. >>> >>> > > I just revised the patch using the 'retro' option, most of the text was > removed, please have a quick look at this: > > http://people.freebsd.org/~manolis/x11.diff > > http://www.freebsdgr.org/handbook-mine/x-config.html > > (Also removed a tag, to avoid having two s one after the other) > Looks good, I added two words for text flow/consistency. Patch at ftp://rene-ladan.nl/pub/freebsd/x11.diff Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) From sonic2000gr at gmail.com Tue Apr 28 06:28:55 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Apr 28 06:29:01 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49F69B53.5090202@freebsd.org> References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> <49F60000.5010806@gmail.com> <49F69623.90204@gmail.com> <49F69B53.5090202@freebsd.org> Message-ID: <49F6A220.1010509@gmail.com> Rene Ladan wrote: > Manolis Kiagias schreef: >> >> I just revised the patch using the 'retro' option, most of the text was >> removed, please have a quick look at this: >> >> http://people.freebsd.org/~manolis/x11.diff >> >> http://www.freebsdgr.org/handbook-mine/x-config.html >> >> (Also removed a tag, to avoid having two s one after the >> other) >> > Looks good, I added two words for text flow/consistency. > > Patch at ftp://rene-ladan.nl/pub/freebsd/x11.diff > > Regards, > Rene Updated, thanks! From m.e.sanliturk at gmail.com Tue Apr 28 07:28:17 2009 From: m.e.sanliturk at gmail.com (Mehmet Erol Sanliturk) Date: Tue Apr 28 07:28:24 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49F69623.90204@gmail.com> References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> <49F60000.5010806@gmail.com> <49F69623.90204@gmail.com> Message-ID: On Tue, Apr 28, 2009 at 1:37 AM, Manolis Kiagias wrote: > Manolis Kiagias wrote: > > Giorgos Keramidas wrote: > > > I just revised the patch using the 'retro' option, most of the text was > removed, please have a quick look at this: > > > http://www.freebsdgr.org/handbook-mine/x-config.html > I have installed FreeBSD 7.2 amd64 RC2 . The related message is as follows : http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049654.html (1) When steps described in the section 5.4.2 of page http://www.freebsdgr.org/handbook-mine/x-config.html it is not possible to start X : # xorgcfg xorgcfg : command not found # xorgconfig xorgconfig : command not found # Xorg -configure # Xorg -config xorg.conf.new Fatal server error : caught signal 11 . server aborting # Xorg -config xorg.conf.new -retro Fatal server error : caught signal 11 . server aborting # startx Fatal server error : caught signal 11 . server aborting (2) In the Handbook , there is no any section dealing with such a case . (3) In the same machine Solaris 10 , OpenSolaris , CentOS 5.3 , Windows XP Home is working . This is the first time I encountered this X11 problem with FreeBSD 7.2 amd64 RC2 . Thank you very much . Mehmet Erol Sanliturk From sonic2000gr at gmail.com Tue Apr 28 07:58:39 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Apr 28 07:58:50 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> <49F60000.5010806@gmail.com> <49F69623.90204@gmail.com> Message-ID: <49F6B72A.1040607@gmail.com> Mehmet Erol Sanliturk wrote: > > > On Tue, Apr 28, 2009 at 1:37 AM, Manolis Kiagias > > wrote: > > Manolis Kiagias wrote: > > Giorgos Keramidas wrote: > > > I just revised the patch using the 'retro' option, most of the > text was > removed, please have a quick look at this: > > > http://www.freebsdgr.org/handbook-mine/x-config.html > > > > > I have installed FreeBSD 7.2 amd64 RC2 . > The related message is as follows : > > http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049654.html > > (1) > > When steps described in the section 5.4.2 of page > > http://www.freebsdgr.org/handbook-mine/x-config.html > > it is not possible to start X : > > # xorgcfg > xorgcfg : command not found > > # xorgconfig > xorgconfig : command not found These don't exist in Xorg 7.4 (and probably haven't been around in the last few iterations of Xorg) > > # Xorg -configure > > # Xorg -config xorg.conf.new > > Fatal server error : caught signal 11 . server aborting > > # Xorg -config xorg.conf.new -retro > > Fatal server error : caught signal 11 . server aborting > > # startx > > Fatal server error : caught signal 11 . server aborting > There must be some problem in your system if you are receiving signal 11. Please provide more info on your graphics card, motherboard etc. It would also be better to send your question to -questions or -stable, this is not a documentation problem. > > (2) > In the Handbook , there is no any section dealing with such a case . There are many possible causes for signal 11, ranging from hardware failures to weird incompatibilities. > > (3) > In the same machine Solaris 10 , OpenSolaris , CentOS 5.3 , Windows XP > Home is working . > This is the first time I encountered this X11 problem with FreeBSD 7.2 > amd64 RC2 . > I don't have a suitable machine around, but if you provide more details this can probably be worked out. Please try -questions list. From sales at gotgc.com Tue Apr 28 08:14:16 2009 From: sales at gotgc.com (The Golden Comass LLC) Date: Tue Apr 28 08:14:26 2009 Subject: Used Heavy Construction Equipment Yacht Auction Message-ID: Used Heavy Construction Equipment - Yacht Auction Worldwide  ! First 100 Members lifetime platinum membership     Dont Pay Fees Any More [1] DON'T MISS THIS CHANGE ! CLICK NOW! [trans.gif] [trans.gif] [trans.gif] Dear Valued Customer: Itâs been a while the market struggled over buying heavy equipments and yachts. Today we have all the services you need to trust both the sellers and the buyers. We have created a worldwide auction that serves both your needs and the needs of others. The Golden Compass LLC is an online auction where anyone can buy or sell heavy equipment, boats, and yachts world-wide. Using state-of-the-art technology, our site is fast, user friendly, accurate, multilanguage communications, and most important, extremely secure. Our percentage is less than any other place. We challenge any other price. All you need to do is to register for free and pay the verification fee whether you are a seller or buyer. This verification fee is to make sure all members are happy and taking the auction process serious. We have many offices in many countries. If you sold your Item you pay our percentage, if not you donât pay anything. Take the advantage of our service. We give you a free store with unlimited items.  We market our services on TV and news papers in 13 countries. Your chances to sell your items are guaranteed.  You sell, you pay, so you donât lose anything. The service is avaliable in : English - Russian - Italian - French Arabic - Dutch - German - Spanish Almost the whole world knows about Our Service. 24/7 Customer Service On The Phone How Simple and Convenient. GOOD LUCK The Golden Compass LLC Staff [trans.gif]  [trans.gif]         Buyers Pay Verification Fee Only [trans.gif]    [2] www.gotgc.com  [3] Read what others saying about our services ! References Visible links 1. http://www.gotgc.com/ 2. http://www.gotgc.com/ 3. http://www.gotgc.com/ Hidden links: 4. http://www.gotgc.com/ 5. http://www.gotgc.com/ 6. http://www.gotgc.com/ From keramida at freebsd.org Tue Apr 28 12:47:27 2009 From: keramida at freebsd.org (Giorgos Keramidas) Date: Tue Apr 28 12:47:34 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <49F6A220.1010509@gmail.com> (Manolis Kiagias's message of "Tue, 28 Apr 2009 09:28:48 +0300") References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> <49F60000.5010806@gmail.com> <49F69623.90204@gmail.com> <49F69B53.5090202@freebsd.org> <49F6A220.1010509@gmail.com> Message-ID: <87k55554j2.fsf@kobe.laptop> On Tue, 28 Apr 2009 09:28:48 +0300, Manolis Kiagias wrote: >>> http://people.freebsd.org/~manolis/x11.diff >> >> Looks good, I added two words for text flow/consistency. > > Updated, thanks! +1 from me. The new patch looks fine :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20090428/79f8ec65/attachment.pgp From rene at freebsd.org Tue Apr 28 13:15:25 2009 From: rene at freebsd.org (Rene Ladan) Date: Tue Apr 28 13:15:31 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: <87k55554j2.fsf@kobe.laptop> References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> <49F60000.5010806@gmail.com> <49F69623.90204@gmail.com> <49F69B53.5090202@freebsd.org> <49F6A220.1010509@gmail.com> <87k55554j2.fsf@kobe.laptop> Message-ID: 2009/4/28 Giorgos Keramidas : > On Tue, 28 Apr 2009 09:28:48 +0300, Manolis Kiagias wrote: >>>> http://people.freebsd.org/~manolis/x11.diff >>> >>> Looks good, I added two words for text flow/consistency. >> >> Updated, thanks! > > +1 from me. ?The new patch looks fine :) > > Maybe we should remove the note at the end of section 5.4.2 about xorgconfig and xorgcfg ? Regards, Rene From sonic2000gr at gmail.com Tue Apr 28 16:11:24 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Apr 28 16:11:31 2009 Subject: [PATCH] Introduce Xorg 7.4 to the X11 configuration section In-Reply-To: References: <49ED0056.5010706@gmail.com> <49ED7000.70904@praxisvermittlung24.de> <49ED7C59.80808@gmail.com> <87zle2aq58.fsf@kobe.laptop> <49F60000.5010806@gmail.com> <49F69623.90204@gmail.com> <49F69B53.5090202@freebsd.org> <49F6A220.1010509@gmail.com> <87k55554j2.fsf@kobe.laptop> Message-ID: <49F72AA4.1090600@gmail.com> Rene Ladan wrote: > 2009/4/28 Giorgos Keramidas : > >> On Tue, 28 Apr 2009 09:28:48 +0300, Manolis Kiagias wrote: >> >>>>> http://people.freebsd.org/~manolis/x11.diff >>>>> >>>> Looks good, I added two words for text flow/consistency. >>>> >>> Updated, thanks! >>> >> +1 from me. The new patch looks fine :) >> >> >> > Maybe we should remove the note at the end of section 5.4.2 about > xorgconfig and xorgcfg ? > > Regards, > Rene > > Yes, this serves no purpose anymore. I will remove it. Thanks! From frank at shute.org.uk Tue Apr 28 20:10:02 2009 From: frank at shute.org.uk (Frank Shute) Date: Tue Apr 28 20:10:08 2009 Subject: docs/134070: old path for a file given in kbdmap(1) Message-ID: <20090428185950.450064AC1D@orange.esperance-linux.co.uk> >Number: 134070 >Category: docs >Synopsis: old path for a file given in kbdmap(1) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 28 20:10:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Frank Shute >Release: FreeBSD 7.2-RC2 amd64 >Organization: >Environment: System: FreeBSD orange.esperance-linux.co.uk 7.2-RC2 FreeBSD 7.2-RC2 #0: Mon Apr 27 02:24:46 BST 2009 root@orange.esperance-linux.co.uk:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The path given to the alias file in kbdmap(1) no longer exists. >How-To-Repeat: $ ls /usr/X11/lib/X11/locale/locale.alias >Fix: --- patch.1 begins here --- --- /usr/src/usr.sbin/kbdmap/kbdmap.1 2009-04-15 04:14:26.000000000 +0100 +++ /tmp/kbdmap.1 2009-04-28 19:31:30.000000000 +0100 @@ -111,7 +111,7 @@ database for fonts .It Pa /etc/rc.conf default font -.It Pa /usr/X11/lib/X11/locale/locale.alias +.It Pa /usr/local/share/locale/locale.alias describe common .Ev LANG values --- patch.1 ends here --- >Release-Note: >Audit-Trail: >Unformatted: From danger at FreeBSD.org Tue Apr 28 20:20:57 2009 From: danger at FreeBSD.org (danger@FreeBSD.org) Date: Tue Apr 28 20:21:04 2009 Subject: docs/134070: old path for a file given in kbdmap(1) Message-ID: <200904282020.n3SKKvTI028283@freefall.freebsd.org> Synopsis: old path for a file given in kbdmap(1) State-Changed-From-To: open->patched State-Changed-By: danger State-Changed-When: Tue Apr 28 20:20:23 UTC 2009 State-Changed-Why: Fixed in -HEAD, awaiting MFC. Thank you for your submission! http://www.freebsd.org/cgi/query-pr.cgi?pr=134070 From danger at FreeBSD.org Tue Apr 28 20:27:06 2009 From: danger at FreeBSD.org (danger@FreeBSD.org) Date: Tue Apr 28 20:27:13 2009 Subject: docs/134053: [patch] arp(8) manpage should mention ndp(8) in See Also section Message-ID: <200904282027.n3SKR5pD036110@freefall.freebsd.org> Synopsis: [patch] arp(8) manpage should mention ndp(8) in See Also section State-Changed-From-To: open->patched State-Changed-By: danger State-Changed-When: Tue Apr 28 20:24:06 UTC 2009 State-Changed-Why: - ndp(8) added to the SEE ALSO section - Awaiting MFC Thank you for your submission! http://www.freebsd.org/cgi/query-pr.cgi?pr=134053 From danger at FreeBSD.org Tue Apr 28 20:27:21 2009 From: danger at FreeBSD.org (danger@FreeBSD.org) Date: Tue Apr 28 20:27:28 2009 Subject: docs/134053: [patch] arp(8) manpage should mention ndp(8) in See Also section Message-ID: <200904282027.n3SKRLqF036169@freefall.freebsd.org> Synopsis: [patch] arp(8) manpage should mention ndp(8) in See Also section Responsible-Changed-From-To: freebsd-doc->danger Responsible-Changed-By: danger Responsible-Changed-When: Tue Apr 28 20:27:11 UTC 2009 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=134053 From danger at FreeBSD.org Tue Apr 28 20:27:44 2009 From: danger at FreeBSD.org (danger@FreeBSD.org) Date: Tue Apr 28 20:27:50 2009 Subject: docs/134070: old path for a file given in kbdmap(1) Message-ID: <200904282027.n3SKRhZV036241@freefall.freebsd.org> Synopsis: old path for a file given in kbdmap(1) Responsible-Changed-From-To: freebsd-doc->danger Responsible-Changed-By: danger Responsible-Changed-When: Tue Apr 28 20:27:34 UTC 2009 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=134070 From havenster at gmail.com Wed Apr 29 00:20:04 2009 From: havenster at gmail.com (Haven Hash) Date: Wed Apr 29 00:20:10 2009 Subject: docs/134074: [patch] locking.9 man page slight enhancements Message-ID: <200904290015.n3T0Fl8s093619@www.freebsd.org> >Number: 134074 >Category: docs >Synopsis: [patch] locking.9 man page slight enhancements >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Apr 29 00:20:03 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Haven Hash >Release: SVN rev 191642 >Organization: >Environment: N/A >Description: While reading the locking (9) man page. I found a few slight things that could be improved so I did an svn checkout and made a few adjustments. 1. The order of Sleep/wakeup and Giant in the Description list is reversed from the order in which they are presented in the document. With no logic other than the Description list seemed to be a better ordering I reversed their order in the document. 2. The link to the witness manual page at the bottom is in all capital letters and signifies chapter 9 of the manual. The witness manual page it seems is in chapter 4 of the manual and an all caps reference causes links on the www man page viewer to not find it (witness (4) is appropriately referenced earlier in the document). 3. Some slight grammatical additions were made to the explanations in the Usage Table. >How-To-Repeat: man 9 locking on a FreeBSD system >= 7.0 >Fix: Apply attached patch if deemed appropriate. Patch attached with submission follows: Index: share/man/man9/locking.9 =================================================================== --- share/man/man9/locking.9 (revision 191639) +++ share/man/man9/locking.9 (working copy) @@ -220,28 +220,6 @@ When a thread waits on a condition, the mutex is atomically released before the thread is blocked, then reacquired before the function call returns. -.Ss Giant -Giant is a special instance of a sleep lock. -It has several special characteristics. -.Bl -enum -.It -It is recursive. -.It -Drivers can request that Giant be locked around them, but this is -going away. -.It -You can sleep while it has recursed, but other recursive locks cannot. -.It -Giant must be locked first before other locks. -.It -There are places in the kernel that drop Giant and pick it back up -again. -Sleep locks will do this before sleeping. -Parts of the Network or VM code may do this as well, depending on the -setting of a sysctl. -This means that you cannot count on Giant keeping other code from -running if your code sleeps, even if you want it to. -.El .Ss Sleep/wakeup The functions .Fn tsleep , @@ -298,6 +276,28 @@ .Va Giant mutex before the function returns. .Pp +.Ss Giant +Giant is a special instance of a sleep lock. +It has several special characteristics. +.Bl -enum +.It +It is recursive. +.It +Drivers can request that Giant be locked around them, but this is +going away. +.It +You can sleep while it has recursed, but other recursive locks cannot. +.It +Giant must be locked first before other locks. +.It +There are places in the kernel that drop Giant and pick it back up +again. +Sleep locks will do this before sleeping. +Parts of the Network or VM code may do this as well, depending on the +setting of a sysctl. +This means that you cannot count on Giant keeping other code from +running if your code sleeps, even if you want it to. +.El .Ss lockmanager locks Largely deprecated. See the @@ -325,11 +325,11 @@ Lock order is important. .Pp .Em *2 -readers can recurse though writers can not. +Readers can recurse though writers can not. Lock order is important. .Pp .Em *3 -There are calls atomically release this primitive when going to sleep +There are calls to atomically release this primitive when going to sleep and reacquire it on wakeup (e.g. .Fn mtx_sleep , .Fn rw_sleep @@ -340,7 +340,7 @@ .Em *4 Though one can sleep holding an sx lock, one can also use .Fn sx_sleep -which atomically release this primitive when going to sleep and +which will atomically release this primitive when going to sleep and reacquire it on wakeup. .Ss Context mode table. The next table shows what can be used in different contexts. @@ -363,7 +363,7 @@ .Xr sleep 9 , .Xr sx 9 , .Xr LOCK_PROFILING 9 , -.Xr WITNESS 9 +.Xr witness 4 .Sh HISTORY These functions appeared in >Release-Note: >Audit-Trail: >Unformatted: From gavin at FreeBSD.org Wed Apr 29 14:20:02 2009 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Wed Apr 29 14:20:14 2009 Subject: docs/134093: [patch] uchcom.4 man page lists wrong first version Message-ID: <200904291348.n3TDm9aq095926@buffy.york.ac.uk> >Number: 134093 >Category: docs >Synopsis: [patch] uchcom.4 man page lists wrong first version >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Apr 29 14:20:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Gavin Atkinson >Release: FreeBSD 7.1-STABLE amd64 >Organization: >Environment: System: FreeBSD buffy.york.ac.uk 7.1-STABLE FreeBSD 7.1-STABLE #5: Fri Feb 13 11:25:58 GMT 2009 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Tiny nit: the first version of FreeBSD to have the uchcom(4) driver wasn't 7.0, as the driver still hasn't been MFC'd. It looks likely that it'll be first in 8.0 >How-To-Repeat: N/A >Fix: --- uchcom.4.diff begins here --- Index: src/share/man/man4/uchcom.4 =================================================================== RCS file: /home/ncvs/src/share/man/man4/uchcom.4,v retrieving revision 1.1 diff -u -r1.1 uchcom.4 --- src/share/man/man4/uchcom.4 1 Mar 2008 13:05:03 -0000 1.1 +++ src/share/man/man4/uchcom.4 19 Apr 2009 20:04:58 -0000 @@ -88,7 +88,7 @@ The first .Fx release to include it was -.Fx 7.0 . +.Fx 8.0 . .Sh BUGS Actually, this chip seems unable to drive other than 8 data bits and 1 stop bit line. --- uchcom.4.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From myc at barev.net Wed Apr 29 20:00:12 2009 From: myc at barev.net (Eugene Mychlo) Date: Wed Apr 29 20:00:19 2009 Subject: docs/134100: Incorrect control messages in ng_hole(4) manpage Message-ID: <200904291950.n3TJoDF5044319@www.freebsd.org> >Number: 134100 >Category: docs >Synopsis: Incorrect control messages in ng_hole(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: Wed Apr 29 20:00:11 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Eugene Mychlo >Release: FreeBSD 7.1-RELEASE-p4 >Organization: Rekomendata, JSC >Environment: FreeBSD mycws.local 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #0: Sun Mar 22 12:35:36 UTC 2009 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 >Description: The ng_hole(4) manpage states that hole node type supports NGM_BPF_* control messages, but isn't correct. >How-To-Repeat: >Fix: Patch attached with submission follows: --- share/man/man4/ng_hole.4~ 2009-04-29 23:41:51.000000000 +0400 +++ share/man/man4/ng_hole.4 2009-04-29 23:42:50.000000000 +0400 @@ -58,20 +58,20 @@ This node type supports the generic control messages, plus the following: .Bl -tag -width indent -.It Dv NGM_BPF_GET_STATS +.It Dv NGM_HOLE_GET_STATS This command takes an .Tn ASCII string argument, the hook name, and returns the statistics associated with the hook as a .Vt "struct ng_hole_hookstat" . -.It Dv NGM_BPF_CLR_STATS +.It Dv NGM_HOLE_CLR_STATS This command takes an .Tn ASCII string argument, the hook name, and clears the statistics associated with the hook. -.It Dv NGM_BPF_GETCLR_STATS +.It Dv NGM_HOLE_GETCLR_STATS This command is identical to -.Dv NGM_BPF_GET_STATS , +.Dv NGM_HOLE_GET_STATS , except that the statistics are also atomically cleared. .El .Sh SHUTDOWN >Release-Note: >Audit-Trail: >Unformatted: From johnwilson at hitechitsoft.com Wed Apr 29 22:48:16 2009 From: johnwilson at hitechitsoft.com (John Wilson) Date: Wed Apr 29 22:48:23 2009 Subject: Hire Software Professionals Only For $550 Per Month Message-ID: Hire Webdesigners and Software Professionals only for $550 Per Month Looking for Dedicated Webdesigners and Software Professionals ? Then you have come to the right place. We provide dedicated IT professionals only for $550 Per Month. All these Professionals has a Minimum of 5+ Years of Experience and will be working according to your convenient timings. They Work 8 hours a day and Five days a week. Webdesigner:- $550 Per month for 160 hours. ASP.NET Programmer :- $750 Per month for 160 hours. ASP Programmer :- $750 Per month for 160 hours. Flash Developer :- $750 Per month for 160 hours. Java Developer :- $750 Per month for 160 hours. PHP Programmer :- $750 Per month for 160 hours. SEO Expert :- $750 Per month for 160 hours. Telemarketing Agent :- $750 Per Month for 160 hours. Data Entry operator :- $750 Per Month for160 hours. We also work on Project to Project Basis. We are expertise in ASP, ASP NET, AJAX, Dot Net Nuke, PHP, PHP Nuke, Joomla, Mambo, Drupal CMS, Typo3 CMS, Ruby on Rails, XML, DHTML, JSP, J2EE, Java, Advanced Java, Cold Fusion, C , C++ , C#, Perl, VB ,VC++, Flash Animation and Action Script, Webdesigning, E-Commerce,2D and 3D Animation,Logo, SEO, X-Cart,OS Commerce, And Zen Cart Development. We also Provide Data entry,Medical Transcription, Medical Billing,Staffing, Telemarketing,Customer Care Both Inbound and Outbound,Online Technical Support Both Voice And Non Voice. For More Information Call Us:646-797-3064 (USA), 020 3239 3435 (UK), John Wilson, Director Operations HI-Tech IT Solutions Inc johnwilson@hitechitsoft.com www.hitechitsoft.com Skype : hitechphp01 From maxim at FreeBSD.org Thu Apr 30 10:01:43 2009 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Thu Apr 30 10:01:49 2009 Subject: docs/134100: [patch] Incorrect control messages in ng_hole(4) manpage Message-ID: <200904301001.n3UA1gBI052377@freefall.freebsd.org> Synopsis: [patch] Incorrect control messages in ng_hole(4) manpage State-Changed-From-To: open->patched State-Changed-By: maxim State-Changed-When: Thu Apr 30 10:01:26 UTC 2009 State-Changed-Why: Fixed in HEAD. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=134100 From dfilter at FreeBSD.ORG Thu Apr 30 10:10:05 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Thu Apr 30 10:10:11 2009 Subject: docs/134100: commit references a PR Message-ID: <200904301010.n3UAA4Ra055506@freefall.freebsd.org> The following reply was made to PR docs/134100; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/134100: commit references a PR Date: Thu, 30 Apr 2009 10:01:29 +0000 (UTC) Author: maxim Date: Thu Apr 30 10:01:13 2009 New Revision: 191682 URL: http://svn.freebsd.org/changeset/base/191682 Log: o Correct ng_hole(4) control messages names. PR: docs/134100 Submitted by: Eugene Mychlo MFC after: 1 week Modified: head/share/man/man4/ng_hole.4 Modified: head/share/man/man4/ng_hole.4 ============================================================================== --- head/share/man/man4/ng_hole.4 Thu Apr 30 07:48:49 2009 (r191681) +++ head/share/man/man4/ng_hole.4 Thu Apr 30 10:01:13 2009 (r191682) @@ -58,20 +58,20 @@ as long as the name is unique. This node type supports the generic control messages, plus the following: .Bl -tag -width indent -.It Dv NGM_BPF_GET_STATS +.It Dv NGM_HOLE_GET_STATS This command takes an .Tn ASCII string argument, the hook name, and returns the statistics associated with the hook as a .Vt "struct ng_hole_hookstat" . -.It Dv NGM_BPF_CLR_STATS +.It Dv NGM_HOLE_CLR_STATS This command takes an .Tn ASCII string argument, the hook name, and clears the statistics associated with the hook. -.It Dv NGM_BPF_GETCLR_STATS +.It Dv NGM_HOLE_GETCLR_STATS This command is identical to -.Dv NGM_BPF_GET_STATS , +.Dv NGM_HOLE_GET_STATS , except that the statistics are also atomically cleared. .El .Sh SHUTDOWN _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From jhb at freebsd.org Thu Apr 30 21:41:26 2009 From: jhb at freebsd.org (John Baldwin) Date: Thu Apr 30 21:42:10 2009 Subject: docs/134074: [patch] locking.9 man page slight enhancements In-Reply-To: <200904290015.n3T0Fl8s093619@www.freebsd.org> References: <200904290015.n3T0Fl8s093619@www.freebsd.org> Message-ID: <200904301341.48920.jhb@freebsd.org> On Tuesday 28 April 2009 8:15:47 pm Haven Hash wrote: > > >Number: 134074 > >Category: docs > >Synopsis: [patch] locking.9 man page slight enhancements > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-doc > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: doc-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Apr 29 00:20:03 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Haven Hash > >Release: SVN rev 191642 > >Organization: > >Environment: > N/A > >Description: > While reading the locking (9) man page. I found a few slight things that could be improved so I did an svn checkout and made a few adjustments. > > 1. The order of Sleep/wakeup and Giant in the Description list is reversed from the order in which they are presented in the document. With no logic other than the Description list seemed to be a better ordering I reversed their order in the document. I haven't looked at this part. > 2. The link to the witness manual page at the bottom is in all capital letters and signifies chapter 9 of the manual. The witness manual page it seems is in chapter 4 of the manual and an all caps reference causes links on the www man page viewer to not find it (witness (4) is appropriately referenced earlier in the document). > > 3. Some slight grammatical additions were made to the explanations in the Usage Table. These parts of the patch are definitely correct. -- John Baldwin From jhb at freebsd.org Thu Apr 30 21:50:05 2009 From: jhb at freebsd.org (John Baldwin) Date: Thu Apr 30 21:50:11 2009 Subject: docs/134074: [patch] locking.9 man page slight enhancements Message-ID: <200904302150.n3ULo2Uo001679@freefall.freebsd.org> The following reply was made to PR docs/134074; it has been noted by GNATS. From: John Baldwin To: freebsd-doc@freebsd.org Cc: Haven Hash , freebsd-gnats-submit@freebsd.org Subject: Re: docs/134074: [patch] locking.9 man page slight enhancements Date: Thu, 30 Apr 2009 13:41:48 -0400 On Tuesday 28 April 2009 8:15:47 pm Haven Hash wrote: > > >Number: 134074 > >Category: docs > >Synopsis: [patch] locking.9 man page slight enhancements > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-doc > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: doc-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Apr 29 00:20:03 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Haven Hash > >Release: SVN rev 191642 > >Organization: > >Environment: > N/A > >Description: > While reading the locking (9) man page. I found a few slight things that could be improved so I did an svn checkout and made a few adjustments. > > 1. The order of Sleep/wakeup and Giant in the Description list is reversed from the order in which they are presented in the document. With no logic other than the Description list seemed to be a better ordering I reversed their order in the document. I haven't looked at this part. > 2. The link to the witness manual page at the bottom is in all capital letters and signifies chapter 9 of the manual. The witness manual page it seems is in chapter 4 of the manual and an all caps reference causes links on the www man page viewer to not find it (witness (4) is appropriately referenced earlier in the document). > > 3. Some slight grammatical additions were made to the explanations in the Usage Table. These parts of the patch are definitely correct. -- John Baldwin