From kenji.rikitake at acm.org Fri May 1 04:30:02 2009 From: kenji.rikitake at acm.org (Kenji Rikitake) Date: Fri May 1 04:30:07 2009 Subject: docs/134127: ip6(4) manual does not contain proper reference to IPV6_V6ONLY option Message-ID: <200905010426.n414QgMF051461@www.freebsd.org> >Number: 134127 >Category: docs >Synopsis: ip6(4) manual does not contain proper reference to IPV6_V6ONLY option >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 May 01 04:30:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Kenji Rikitake >Release: 7.1-RELEASE-p5 >Organization: >Environment: FreeBSD reseaux.priv.k2r.org 7.1-RELEASE-p5 FreeBSD 7.1-RELEASE-p5 #9: Sun Apr 26 11:32:41 JST 2009 root@reseaux.priv.k2r.org:/usr/obj/usr/src/sys/RESEAUX i386 >Description: man page for ip6(4) has a wrong reference for the IPV6_V6ONLY option in the STANDARDS section. RFC3542 does not define the option, and the option is described in RFC3493 Section 5.3. This should be fixed. >How-To-Repeat: man 4 ip6 >Fix: patch for the man source given. Patch attached with submission follows: --- src/share/man/man4/ip6.4.orig 2009-05-01 13:18:52.000000000 +0900 +++ src/share/man/man4/ip6.4 2009-05-01 13:19:54.000000000 +0900 @@ -681,7 +681,7 @@ Most of the socket options are defined in RFC 2292 or RFC 2553. The .Dv IPV6_V6ONLY -socket option is defined in RFC 3542. +socket option is defined in RFC 3493 Section 5.3. The .Dv IPV6_PORTRANGE socket option and the conflict resolution rule are not defined in the >Release-Note: >Audit-Trail: >Unformatted: From linimon at FreeBSD.org Fri May 1 06:47:17 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri May 1 06:47:23 2009 Subject: docs/134123: The RUNQUEUE(9) man page is out of date Message-ID: <200905010647.n416lGdt035893@freefall.freebsd.org> Synopsis: The RUNQUEUE(9) man page is out of date Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Fri May 1 06:46:23 UTC 2009 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=134123 From simon at FreeBSD.org Fri May 1 17:22:00 2009 From: simon at FreeBSD.org (Simon L. Nielsen) Date: Fri May 1 17:22:10 2009 Subject: [simon@FreeBSD.org: FreeBSD FTP doc build failed] Message-ID: <20090501172158.GA1098@arthur.nitro.dk> Hey, Just FYI, looks like mn_MN handbook now needs more than 512MB address space / RAM to build, so for now the FTP doc build is broken. Unfortunatly I don't have time to fix this at the moment, as it involves messing with a half dead server which need to be replaced... ----- Forwarded message from "Simon L. Nielsen" ----- Date: Fri, 1 May 2009 17:02:52 GMT From: "Simon L. Nielsen" To: simon@FreeBSD.org Subject: FreeBSD FTP doc build failed Warning: Unknown character 65533, at 473926 Warning: Unknown character 65533, at 473928 Warning: Unknown character 65533, at 473929 [1069.0.36] [1070.0.36] Warning: Unknown character 65533, at 474310 Warning: Unknown character 65533, at 474311 Warning: Unknown character 65533, at 474312 Overfull \hbox (239.3992pt too wide) in paragraph at lines 474400--474400 []\T1/pcr/m/n/9 uid Maksym Sobolyev (It's how they c all me in official documents. Pretty lame...) [] Overfull \hbox (233.9992pt too wide) in paragraph at lines 474401--474401 []\T1/pcr/m/n/9 uid Maksym Sobolyev (It's how they c all me in official documents. Pretty lame...) [] [1071.0.36] [1072.0.36] Overfull \hbox (1.79947pt too wide) in paragraph at lines 475075--475075 []\T1/pcr/m/n/9 uid Cheng-Lung Sung (Software Engine er) [] Overfull \hbox (142.19931pt too wide) in paragraph at lines 475076--475076 []\T1/pcr/m/n/9 uid Cheng-Lung Sung (Alumnus of CSIE , NCTU, Taiwan) [] Overfull \hbox (55.79941pt too wide) in paragraph at lines 475078--475078 []\T1/pcr/m/n/9 uid Cheng-Lung Sung (FreeBSD@Taiwan) [] Overfull \hbox (55.79941pt too wide) in paragraph at lines 475079--475079 []\T1/pcr/m/n/9 uid Cheng-Lung Sung (Ph.D. Student o f NTU.EECS) [] Overfull \hbox (12.59946pt too wide) in paragraph at lines 475080--475080 []\T1/pcr/m/n/9 uid Cheng-Lung Sung (FreeBSD Freshma n) [] [1073.0.36] [1074.0.36] [1075.0.36] Overfull \hbox (12.59946pt too wide) in paragraph at lines 476434--476434 []\T1/pcr/m/n/9 uid Nicola Vitale (Public key for nivit@FreeBS D.org) [] [1076.0.36] [1077.0.36] [1078.0.36] [1079.0.36] [1080.0.36] [1081.0.36] Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is use less on input line 478269. Package Fancyhdr Warning: \fancyhead's `E' option without twoside option is use less on input line 478269. Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is use less on input line 479078. [1082.0.36] [1083.0.36] [1084.0.36] [1085.0.36] [1086.0.36] [1087.0.36] [1088.0.36] [1089.0.36] [1090.0.36] [1091.0.36] [1092.0.36] [1093.0.36] [1094.0.36] [1095.0.36] [1096.0.36] [1097.0.36] [1098.0.36] [1099.0.36] [1100.0.36] [1101.0.36] [1102.0.36] [1103.0.36] [1104.0.36] [1105.0.36] [1106.0.36] Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is use less on input line 493812. Package Fancyhdr Warning: \fancyhead's `E' option without twoside option is use less on input line 493812. Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is use less on input line 495363. [1107.0.36] [1108.0.36] [1109.0.36] [1110.0.36] [1111.0.36] [1112.0.36] [1113.0.36] [1114.0.36] [1115.0.36] [1116.0.36] [1117.0.36] [1118.0.36]fatal: memory exhausted (xmalloc of 8 bytes). Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is use less on input line 512300. Package Fancyhdr Warning: \fancyhead's `E' option without twoside option is use less on input line 512300. *** Error code 75 (ignored) /usr/local/bin/dvips -o book.ps book.dvi This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2009.05.01:1615' -> book.ps /usr/local/bin/dvips: Font ArialMT used in file install/disk-layout.eps is not in the mapping file. /usr/local/bin/dvips: ! unexpected eof on DVI file *** Error code 1 Stop in /local0/docbuild/build/doc/mn_MN.UTF-8/books/handbook. *** Error code 1 Stop in /local0/docbuild/build/doc/mn_MN.UTF-8/books. *** Error code 1 Stop in /local0/docbuild/build/doc/mn_MN.UTF-8. *** Error code 1 Stop in /local0/docbuild/build/doc. 48961.18 real 46722.67 user 1388.99 sys + exit 3 ----- End forwarded message ----- -- Simon L. Nielsen From bcr at doc.bsdgroup.de Fri May 1 21:30:02 2009 From: bcr at doc.bsdgroup.de (Benedict Reuschling) Date: Fri May 1 21:30:08 2009 Subject: docs/134147: Unclear sentence (perhaps missing a word), suggestions attached Message-ID: <200905012123.n41LNZKW095575@www.freebsd.org> >Number: 134147 >Category: docs >Synopsis: Unclear sentence (perhaps missing a word), suggestions attached >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 May 01 21:30:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Benedict Reuschling >Release: 7.2-PRERELEASE >Organization: The FreeBSD German Documentation Project >Environment: FreeBSD atlantis.reuschling.org 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #18: Thu Apr 23 22:00:35 CEST 2009 root@atlantis.reuschling.org:/tank/obj/usr/src/sys/ATLANTIS i386 >Description: The following sentence in the FAQ seems to be missing a word or should be rephrased around the word "causes": "There is a known problem when enabling &intel; Enhanced SpeedStep from the BIOS causes the kernel to start printing calcru messages like this:" I have attached three suggestions on how to make the sentence more clear. >How-To-Repeat: Read the sentence and try to make sense of it as it is. >Fix: Apply one of the following diffs to make the sentence more complete/understandable. Suggestion 1: --- book.sgml.orig 2009-05-01 23:04:42.092926621 +0200 +++ book.sgml 2009-05-01 23:05:15.349031797 +0200 @@ -3871,7 +3871,7 @@ - There is a known problem when enabling &intel; Enhanced + A known problem when enabling &intel; Enhanced SpeedStep from the BIOS causes the kernel to start printing calcru messages like this: Suggestion 2: --- book.sgml.orig 2009-05-01 23:04:42.092926621 +0200 +++ book.sgml 2009-05-01 23:07:28.640448164 +0200 @@ -3872,7 +3872,7 @@ There is a known problem when enabling &intel; Enhanced - SpeedStep from the BIOS causes the kernel to start printing + SpeedStep from the BIOS. It causes the kernel to start printing calcru messages like this: calcru: runtime went backwards from 6 usec to 3 usec for pid 37 (pagezero) Suggestion 3: --- book.sgml.orig 2009-05-01 23:04:42.092926621 +0200 +++ book.sgml 2009-05-01 23:08:27.557631772 +0200 @@ -3872,7 +3872,7 @@ There is a known problem when enabling &intel; Enhanced - SpeedStep from the BIOS causes the kernel to start printing + SpeedStep from the BIOS, which causes the kernel to start printing calcru messages like this: calcru: runtime went backwards from 6 usec to 3 usec for pid 37 (pagezero) Patch attached with submission follows: --- book.sgml.orig 2009-05-01 23:04:42.092926621 +0200 +++ book.sgml 2009-05-01 23:08:27.557631772 +0200 @@ -3872,7 +3872,7 @@ There is a known problem when enabling &intel; Enhanced - SpeedStep from the BIOS causes the kernel to start printing + SpeedStep from the BIOS, which causes the kernel to start printing calcru messages like this: calcru: runtime went backwards from 6 usec to 3 usec for pid 37 (pagezero) >Release-Note: >Audit-Trail: >Unformatted: From dfilter at FreeBSD.ORG Fri May 1 22:20:04 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Fri May 1 22:20:13 2009 Subject: docs/134147: commit references a PR Message-ID: <200905012220.n41MK2vI095150@freefall.freebsd.org> The following reply was made to PR docs/134147; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/134147: commit references a PR Date: Fri, 1 May 2009 22:18:50 +0000 (UTC) manolis 2009-05-01 22:18:36 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/faq book.sgml Log: Minor language nit PR: docs/134147 Submitted by: Benedict Reuschling Revision Changes Path 1.1113 +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 manolis at FreeBSD.org Fri May 1 22:22:06 2009 From: manolis at FreeBSD.org (manolis@FreeBSD.org) Date: Fri May 1 22:22:13 2009 Subject: docs/134147: Unclear sentence (perhaps missing a word), suggestions attached Message-ID: <200905012222.n41MM528008142@freefall.freebsd.org> Synopsis: Unclear sentence (perhaps missing a word), suggestions attached State-Changed-From-To: open->closed State-Changed-By: manolis State-Changed-When: Fri May 1 22:21:36 UTC 2009 State-Changed-Why: Committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=134147 From E-Cards at hallmark.com Sat May 2 00:52:25 2009 From: E-Cards at hallmark.com (hallmark.com) Date: Sat May 2 00:52:30 2009 Subject: You've received A Hallmark E-Card! Message-ID: <200905012313.n41NDEL1029626@smtp.bcsfastnet.com> [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 bugmaster at FreeBSD.org Mon May 4 11:06:14 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 4 11:06:43 2009 Subject: Current unassigned doc problem reports Message-ID: <200905041106.n44B6CTt096123@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/134127 doc [patch] ip6(4) manual does not contain proper referenc o docs/134123 doc The RUNQUEUE(9) man page is out of date p docs/134100 doc [patch] Incorrect control messages in ng_hole(4) manpa o docs/134093 doc [patch] uchcom.4 man page lists wrong first version o docs/134074 doc [patch] locking.9 man page slight enhancements 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 144 problems total. From sonic2000gr at gmail.com Mon May 4 18:09:41 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon May 4 18:09:48 2009 Subject: [PATCH] Add the new 'ufsid' labels to the glabel section of 'geom' Message-ID: <49FF2F5C.6010307@gmail.com> Hi all, This is a small patch for the glabel section of the geom chapter that adds the new 'ufsid' labels present on 7.2-RELEASE. Fits nicely (I think) after the example which deals with device-name independent mounting during boot. http://people.freebsd.org/~manolis/geom.diff http://www.freebsdgr.org/handbook-mine/geom-glabel.html If you do find any nits, please let me know! Thanks, manolis@ From sonic2000gr at gmail.com Mon May 4 20:44:01 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon May 4 20:44:07 2009 Subject: [PATCH] Add the new 'ufsid' labels to the glabel section of 'geom' In-Reply-To: <49FF4F81.9040909@freebsd.org> References: <49FF2F5C.6010307@gmail.com> <49FF4F81.9040909@freebsd.org> Message-ID: <49FF5389.5030708@gmail.com> Rene Ladan wrote: > Manolis Kiagias schreef: >> Hi all, >> >> This is a small patch for the glabel section of the geom chapter that >> adds the new 'ufsid' labels present on 7.2-RELEASE. Fits nicely (I >> think) after the example which deals with device-name independent >> mounting during boot. >> >> http://people.freebsd.org/~manolis/geom.diff >> >> http://www.freebsdgr.org/handbook-mine/geom-glabel.html >> >> If you do find any nits, please let me know! >> > Only a small one: > > @@ -33,8 +33,8 @@ > + /dev/ufsid/486b6fc38d330916 /var > ufs rw 2 2 > +/dev/ufsid/486b6fc16926168e /usr ufs rw > 2 2 > + > -+ Any partitions with ufsid labels may > also get > -+ mounted in a similar way, eliminating the need to create permanent > ++ Any partitions with ufsid labels can be > ++ mounted in this way, eliminating the need to create permanent > + labels for them manually, while still enjoying the benefits of > + device-name independent mounting. > > > I think this sounds more confident, which should be more reassuring to > the reader. > > Regards, > Rene Updated, thanks! From rene at freebsd.org Mon May 4 20:57:49 2009 From: rene at freebsd.org (Rene Ladan) Date: Mon May 4 20:57:56 2009 Subject: [PATCH] Add the new 'ufsid' labels to the glabel section of 'geom' In-Reply-To: <49FF2F5C.6010307@gmail.com> References: <49FF2F5C.6010307@gmail.com> Message-ID: <49FF4F81.9040909@freebsd.org> Manolis Kiagias schreef: > Hi all, > > This is a small patch for the glabel section of the geom chapter that > adds the new 'ufsid' labels present on 7.2-RELEASE. Fits nicely (I > think) after the example which deals with device-name independent > mounting during boot. > > http://people.freebsd.org/~manolis/geom.diff > > http://www.freebsdgr.org/handbook-mine/geom-glabel.html > > If you do find any nits, please let me know! > Only a small one: @@ -33,8 +33,8 @@ + /dev/ufsid/486b6fc38d330916 /var ufs rw 2 2 +/dev/ufsid/486b6fc16926168e /usr ufs rw 2 2 + -+ Any partitions with ufsid labels may also get -+ mounted in a similar way, eliminating the need to create permanent ++ Any partitions with ufsid labels can be ++ mounted in this way, eliminating the need to create permanent + labels for them manually, while still enjoying the benefits of + device-name independent mounting. I think this sounds more confident, which should be more reassuring to the reader. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) From pluknet at gmail.com Tue May 5 04:56:31 2009 From: pluknet at gmail.com (pluknet) Date: Tue May 5 04:56:58 2009 Subject: update EoL and releng tables Message-ID: Hi. Can someone, please, update those tables? The releng page still mentions "FreeBSD 7.0 supported errata fix branch." when it should say "FreeBSD 7.0 errata fix branch (not officially supported)." Also EoL table on the security page misses 7.2-R. --- releng/index.sgml.orig 2009-05-05 08:29:15.000000000 +0400 +++ releng/index.sgml 2009-05-05 08:28:52.000000000 +0400 @@ -109,7 +109,7 @@ RELENG_7_0 Frozen &contact.so; - FreeBSD 7.0 supported errata fix branch. + FreeBSD 7.0 errata fix branch (not officially supported). --- security/security.sgml.orig 2009-05-05 08:30:26.000000000 +0400 +++ security/security.sgml 2009-05-05 08:32:26.000000000 +0400 @@ -279,6 +279,13 @@ January 4, 2009 January 31, 2011 + + RELENG_7_2 + 7.2-RELEASE + Normal + May 4, 2009 + May 31, 2010 +

Older releases are not maintained and users are strongly -- wbr, pluknet From turutani at scphys.kyoto-u.ac.jp Tue May 5 06:40:04 2009 From: turutani at scphys.kyoto-u.ac.jp (Tsurutani Naoki) Date: Tue May 5 06:40:34 2009 Subject: docs/134222: installation failure of japanese docs Message-ID: <200905050629.n456TquF024957@h120.65.226.10.32118.vlan.kuins.net> >Number: 134222 >Category: docs >Synopsis: installation failure of japanese docs >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue May 05 06:40:00 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Tsurutani Naoki >Release: FreeBSD 7.2-STABLE i386 >Organization: >Environment: System: FreeBSD h120.65.226.10.32118.vlan.kuins.net 7.2-STABLE FreeBSD 7.2-STABLE #18: Tue May 5 14:31:14 JST 2009 turutani@h120.65.226.10.32118.vlan.kuins.net:/usr/local/work/usr/obj/usr/src/sys/POLYMER i386 >Description: installation failure of japanese docs. >How-To-Repeat: % cd /usr/doc % make install ... /usr/share/man/ja/man8/catman.local.8.gz -> /usr/share/man/ja/man8/makewhatis.local.8.gz /usr/share/man/ja/man8/vnconfig.8.gz -> /usr/share/man/ja/man8/mdconfig.8.gz /usr/share/man/ja/man8/mount_devfs.8.gz -> /usr/share/man/ja/man8/mount_std.8.gz ln: /usr/share/man/ja/man8/mount_std.8.gz: No such file or directory *** Error code 1 Stop in /usr/doc/ja_JP.eucJP/man/man8. *** Error code 1 Stop in /usr/doc/ja_JP.eucJP/man. *** Error code 1 Stop in /usr/doc/ja_JP.eucJP. *** Error code 1 Stop in /usr/doc. >Fix: some files are removed by PR docs/115984, but some links to these files still exists. here is a patch: --- ja_JP.eucJP/man/man8/Makefile.orig 2008-01-03 04:30:20.000000000 +0900 +++ ja_JP.eucJP/man/man8/Makefile 2009-05-05 15:23:43.000000000 +0900 @@ -318,10 +318,6 @@ MLINKS+=locate.updatedb.8 updatedb.8 MLINKS+=makewhatis.local.8 catman.local.8 MLINKS+=mdconfig.8 vnconfig.8 -MLINKS+=mount_std.8 mount_devfs.8 -MLINKS+=mount_std.8 mount_fdescfs.8 -MLINKS+=mount_std.8 mount_procfs.8 -MLINKS+=mount_std.8 mount_linprocfs.8 MLINKS+=named.reload.8 named.reconfig.8 MLINKS+=pstat.8 swapinfo.8 MLINKS+=quotaon.8 quotaoff.8 >Release-Note: >Audit-Trail: >Unformatted: From f5_b at 163.com Tue May 5 07:50:03 2009 From: f5_b at 163.com (Fluid) Date: Tue May 5 07:50:09 2009 Subject: docs/134226: /usr/share/examples/ftpd/ftpd.conf does not exist. Message-ID: <200905050743.n457hs4M083419@www.freebsd.org> >Number: 134226 >Category: docs >Synopsis: /usr/share/examples/ftpd/ftpd.conf 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 May 05 07:50:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Fluid >Release: FreeBSD 7.1-RELEASE-p4 >Organization: >Environment: 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #0: Sun Mar 22 09:43:46 UTC 2009 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: http://www.freebsd.org/cgi/man.cgi?query=ftpd.conf&sektion=5&manpath=FreeBSD+7.1-RELEASE FILES /etc/ftpd.conf This file. /usr/share/examples/ftpd/ftpd.conf A sample ftpd.conf file. the examples file does not exist in FreeBSD 7.1 release >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From ClientServices at theemployernetwork.com Tue May 5 14:48:16 2009 From: ClientServices at theemployernetwork.com (The Career-Network) Date: Tue May 5 14:48:37 2009 Subject: Get monster results without the monster costs: Career Network Message-ID: <20090505074821.72E4B609DA77DBF5@theemployernetwork.com> [1][3D"=] [=] [2][hr_email=] [3]3D"Cl Career Network has everything - maximum exposure, unlimited job advertisements, quality applicants and rate that' Save money without sacrificing results with C advantage of everything we have to offer: * Flat Monthly ra * Maximum exposur * 1.5 Million uni To speak to a representative, call us today a [4] [5][im=] [hr_emaile=] _________________________________________________________________ ? Career-Network, Inc. P.O. Box 618305 Orlando, FL 32861-8305. [img2.aspx?id=i=] [7]Take my name out of future References 1. 3D"http://career-network.com"/ 2. 3D"http://www.career-network.com"/ 3. 3D"http://getmynetworkofemployers.com/cmana 4. 3D"http://getmynetworkofemployers.com/cmanager3.aspx?em=doc@Free 5. 3D"http://getmynetworkofemployers.com/cmanager3.aspx?em 6. 3D"http://www.career-n=/ 7. 3D"http://getmynetworkofemployers.com/op.aspx?id=iekskdkf7 From Midspan at phihongusa.com Tue May 5 21:22:59 2009 From: Midspan at phihongusa.com (Midspan Manager) Date: Tue May 5 21:23:06 2009 Subject: Myths about Power Over Ethernet Message-ID: <20090505212256.630D43779@glatton.xo.com> Myths about Power Over Ethernet May 5, 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 brd at FreeBSD.org Wed May 6 20:53:56 2009 From: brd at FreeBSD.org (Brad Davis) Date: Wed May 6 20:54:28 2009 Subject: update EoL and releng tables In-Reply-To: References: Message-ID: <35ffa5710905061300n36174993sb8b373ead3921d34@mail.gmail.com> On Mon, May 4, 2009 at 22:34, pluknet wrote: > Hi. > > Can someone, please, update those tables? > > The releng page still mentions "FreeBSD 7.0 supported errata fix branch." > when it should say "FreeBSD 7.0 errata fix branch (not officially supported)." > > Also EoL table on the security page misses 7.2-R. > > --- releng/index.sgml.orig ? ? ?2009-05-05 08:29:15.000000000 +0400 > +++ releng/index.sgml ? 2009-05-05 08:28:52.000000000 +0400 > @@ -109,7 +109,7 @@ > ? ? ? RELENG_7_0 > ? ? ? Frozen > ? ? ? &contact.so; > - ? ? ?FreeBSD 7.0 supported errata fix branch. > + ? ? ?FreeBSD 7.0 errata fix branch (not officially supported). > ? ? > > ? ? > --- security/security.sgml.orig 2009-05-05 08:30:26.000000000 +0400 > +++ security/security.sgml ? ? ?2009-05-05 08:32:26.000000000 +0400 > @@ -279,6 +279,13 @@ > ? ? ? January 4, 2009 > ? ? ? January 31, 2011 > ? ? > + ? ? > + ? ? ?RELENG_7_2 > + ? ? ?7.2-RELEASE > + ? ? ?Normal > + ? ? ?May 4, 2009 > + ? ? ?May 31, 2010 > + ? ? > ? > > ?

Older releases are not maintained and users are strongly > -- > wbr, > pluknet Hi pluknet, I just committed these changes. Thank you for submitting them. Regards, Brad Davis From pgj at FreeBSD.org Thu May 7 07:04:51 2009 From: pgj at FreeBSD.org (Gabor PALI) Date: Thu May 7 07:04:57 2009 Subject: update EoL and releng tables In-Reply-To: <35ffa5710905061300n36174993sb8b373ead3921d34@mail.gmail.com> References: <35ffa5710905061300n36174993sb8b373ead3921d34@mail.gmail.com> Message-ID: <4A0288E8.2070207@FreeBSD.org> Brad Davis wrote: > On Mon, May 4, 2009 at 22:34, pluknet wrote: > >> Hi. >> >> Can someone, please, update those tables? >> >> The releng page still mentions "FreeBSD 7.0 supported errata fix branch." >> when it should say "FreeBSD 7.0 errata fix branch (not officially supported)." >> >> Also EoL table on the security page misses 7.2-R. >> >> --- releng/index.sgml.orig 2009-05-05 08:29:15.000000000 +0400 >> +++ releng/index.sgml 2009-05-05 08:28:52.000000000 +0400 >> @@ -109,7 +109,7 @@ >> RELENG_7_0 >> Frozen >> &contact.so; >> - FreeBSD 7.0 supported errata fix branch. >> + FreeBSD 7.0 errata fix branch (not officially supported). >> >> >> >> --- security/security.sgml.orig 2009-05-05 08:30:26.000000000 +0400 >> +++ security/security.sgml 2009-05-05 08:32:26.000000000 +0400 >> @@ -279,6 +279,13 @@ >> January 4, 2009 >> January 31, 2011 >> >> + >> + RELENG_7_2 >> + 7.2-RELEASE >> + Normal >> + May 4, 2009 >> + May 31, 2010 >> + >> >> >>

Older releases are not maintained and users are strongly >> -- >> wbr, >> pluknet >> > > Hi pluknet, > > I just committed these changes. Thank you for submitting them. > Is the estimated EoL for 7.2-RELEASE really "May 31, 2010"? It looks strange, because the eEoL is "Jan 31, 2011" for 7.1-RELEASE and "Nov 30, 2010" for 6.4-RELEASE. There is also general rule for RELENG_7 that says: "last release + 2 years". I think "May 31, 2011" for 7.2-RELEASE would be more reasonable, but maybe I am missing something. Cheers, :g From pluknet at gmail.com Thu May 7 07:16:48 2009 From: pluknet at gmail.com (pluknet) Date: Thu May 7 07:16:54 2009 Subject: update EoL and releng tables In-Reply-To: <4A0288E8.2070207@FreeBSD.org> References: <35ffa5710905061300n36174993sb8b373ead3921d34@mail.gmail.com> <4A0288E8.2070207@FreeBSD.org> Message-ID: 2009/5/7 Gabor PALI : > Brad Davis wrote: >> On Mon, May 4, 2009 at 22:34, pluknet wrote: >> >>> Hi. >>> >>> Can someone, please, update those tables? >>> >>> The releng page still mentions "FreeBSD 7.0 supported errata fix branch." >>> when it should say "FreeBSD 7.0 errata fix branch (not officially supported)." >>> >>> Also EoL table on the security page misses 7.2-R. >>> >>> --- releng/index.sgml.orig ? ? ?2009-05-05 08:29:15.000000000 +0400 >>> +++ releng/index.sgml ? 2009-05-05 08:28:52.000000000 +0400 >>> @@ -109,7 +109,7 @@ >>> ? ? ? RELENG_7_0 >>> ? ? ? Frozen >>> ? ? ? &contact.so; >>> - ? ? ?FreeBSD 7.0 supported errata fix branch. >>> + ? ? ?FreeBSD 7.0 errata fix branch (not officially supported). >>> ? ? >>> >>> ? ? >>> --- security/security.sgml.orig 2009-05-05 08:30:26.000000000 +0400 >>> +++ security/security.sgml ? ? ?2009-05-05 08:32:26.000000000 +0400 >>> @@ -279,6 +279,13 @@ >>> ? ? ? January 4, 2009 >>> ? ? ? January 31, 2011 >>> ? ? >>> + ? ? >>> + ? ? ?RELENG_7_2 >>> + ? ? ?7.2-RELEASE >>> + ? ? ?Normal >>> + ? ? ?May 4, 2009 >>> + ? ? ?May 31, 2010 >>> + ? ? >>> ? >>> >>> ?

Older releases are not maintained and users are strongly >>> -- >>> wbr, >>> pluknet >>> >> >> Hi pluknet, >> >> I just committed these changes. Thank you for submitting them. >> > Is the estimated EoL for 7.2-RELEASE really "May 31, 2010"? This is derived from Ken Smith's 7.2-R announce. > It looks > strange, because the eEoL is "Jan 31, 2011" for 7.1-RELEASE and "Nov 30, > 2010" for 6.4-RELEASE. ?There is also general rule for RELENG_7 that > says: "last release + 2 years". > > I think "May 31, 2011" for 7.2-RELEASE would be more reasonable, but > maybe I am missing something. -- wbr, pluknet From jkois at FreeBSD.org Thu May 7 07:28:53 2009 From: jkois at FreeBSD.org (jkois@FreeBSD.org) Date: Thu May 7 07:28:59 2009 Subject: docs/133407: [patch] Incorrect UK rsync mirror address in handbook Message-ID: <200905070728.n477SqLr029169@freefall.freebsd.org> Synopsis: [patch] Incorrect UK rsync mirror address in handbook Responsible-Changed-From-To: freebsd-doc->jkois Responsible-Changed-By: jkois Responsible-Changed-When: Thu May 7 07:27:33 UTC 2009 Responsible-Changed-Why: I will take this one. Note: The link provided by gavin@ is wrong. The correct link is: http://people.freebsd.org/~gavin/PRs/133407.diff. http://www.freebsd.org/cgi/query-pr.cgi?pr=133407 From brd at FreeBSD.org Thu May 7 15:43:53 2009 From: brd at FreeBSD.org (Brad Davis) Date: Thu May 7 15:43:59 2009 Subject: update EoL and releng tables In-Reply-To: <4A0288E8.2070207@FreeBSD.org> References: <35ffa5710905061300n36174993sb8b373ead3921d34@mail.gmail.com> <4A0288E8.2070207@FreeBSD.org> Message-ID: <20090507152451.GI95179@valentine.liquidneon.com> On Thu, May 07, 2009 at 09:08:24AM +0200, Gabor PALI wrote: > Brad Davis wrote: > > On Mon, May 4, 2009 at 22:34, pluknet wrote: > > > >> Hi. > >> > >> Can someone, please, update those tables? > >> > >> The releng page still mentions "FreeBSD 7.0 supported errata fix branch." > >> when it should say "FreeBSD 7.0 errata fix branch (not officially supported)." > >> > >> Also EoL table on the security page misses 7.2-R. > >> > >> --- releng/index.sgml.orig 2009-05-05 08:29:15.000000000 +0400 > >> +++ releng/index.sgml 2009-05-05 08:28:52.000000000 +0400 > >> @@ -109,7 +109,7 @@ > >> RELENG_7_0 > >> Frozen > >> &contact.so; > >> - FreeBSD 7.0 supported errata fix branch. > >> + FreeBSD 7.0 errata fix branch (not officially supported). > >> > >> > >> > >> --- security/security.sgml.orig 2009-05-05 08:30:26.000000000 +0400 > >> +++ security/security.sgml 2009-05-05 08:32:26.000000000 +0400 > >> @@ -279,6 +279,13 @@ > >> January 4, 2009 > >> January 31, 2011 > >> > >> + > >> + RELENG_7_2 > >> + 7.2-RELEASE > >> + Normal > >> + May 4, 2009 > >> + May 31, 2010 > >> + > >> > >> > >>

Older releases are not maintained and users are strongly > >> -- > >> wbr, > >> pluknet > >> > > > > Hi pluknet, > > > > I just committed these changes. Thank you for submitting them. > > > Is the estimated EoL for 7.2-RELEASE really "May 31, 2010"? It looks > strange, because the eEoL is "Jan 31, 2011" for 7.1-RELEASE and "Nov 30, > 2010" for 6.4-RELEASE. There is also general rule for RELENG_7 that > says: "last release + 2 years". > > I think "May 31, 2011" for 7.2-RELEASE would be more reasonable, but > maybe I am missing something. > > Cheers, > :g > And approved by cperciva@ :) Regards, Brad Davis From Midspan at phihongusa.com Thu May 7 16:21:55 2009 From: Midspan at phihongusa.com (Midspan Manager) Date: Thu May 7 16:22:02 2009 Subject: Myths about Power Over Ethernet Message-ID: <20090507162151.D4CBA782D@thunderer.xo.com> Myths about Power Over Ethernet May 7, 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 www at FreeBSD.org Thu May 7 18:23:15 2009 From: www at FreeBSD.org (World Wide Web Owner) Date: Thu May 7 18:23:21 2009 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200905071823.n47INEMe021362@www.freebsd.org> ? relnotes7/doc/en_US.ISO8859-1/errata/security.html ? relnotes7/doc/en_US.ISO8859-1/hardware/HTML.manifest ? relnotes7/doc/en_US.ISO8859-1/hardware/TRADEMARKS.html ? relnotes7/doc/en_US.ISO8859-1/hardware/article.html ? relnotes7/doc/en_US.ISO8859-1/hardware/docbook.css ? relnotes7/doc/en_US.ISO8859-1/hardware/index.html ? relnotes7/doc/en_US.ISO8859-1/hardware/proc.html ? relnotes7/doc/en_US.ISO8859-1/hardware/support.html ? relnotes7/doc/en_US.ISO8859-1/readme/HTML.manifest ? relnotes7/doc/en_US.ISO8859-1/readme/TRADEMARKS.html ? relnotes7/doc/en_US.ISO8859-1/readme/acknowledgements.html ? relnotes7/doc/en_US.ISO8859-1/readme/article.html ? relnotes7/doc/en_US.ISO8859-1/readme/contacting.html ? relnotes7/doc/en_US.ISO8859-1/readme/docbook.css ? relnotes7/doc/en_US.ISO8859-1/readme/index.html ? relnotes7/doc/en_US.ISO8859-1/readme/obtain.html ? relnotes7/doc/en_US.ISO8859-1/readme/seealso.html ? relnotes7/doc/en_US.ISO8859-1/relnotes/HTML.manifest ? relnotes7/doc/en_US.ISO8859-1/relnotes/TRADEMARKS.html ? relnotes7/doc/en_US.ISO8859-1/relnotes/article.html ? relnotes7/doc/en_US.ISO8859-1/relnotes/docbook.css ? relnotes7/doc/en_US.ISO8859-1/relnotes/index.html ? relnotes7/doc/en_US.ISO8859-1/relnotes/new.html ? relnotes7/doc/en_US.ISO8859-1/relnotes/upgrade.html ? relnotes7/doc/share/sgml/catalog-auto ? relnotes7/doc/share/sgml/dev-auto.sgml env SGML_CATALOG_FILES= XML_CATALOG_FILES="file:///w/www/build/www/en/catalog-cwd.xml file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml file:///w/www/build/doc/share/sgml/catalog.xml file:///w/www/build/doc/share/sgml/catalog-common.xml file:///w/www/build/www/en/share/sgml/catalog.xml file:///w/www/build/www/share/sgml/catalog.xml file:///w/www/build/www/share/sgml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --stringparam LOCALBASE /usr/local --stringparam WEB_PREFIX /w/www/build/www --nonet --catalogs -o index.html --param transtable.xml "'/w/www/build/doc/share/sgml/transtable.xml'" --param mirrors.xml "'/w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml'" --param news.project.xml-master "'/w/www/build/www/share/sgml/news.xml'" --param news.project.xml "'/w/www/build/www/share/sgml/news.xml'" --param news.press.xml-master "'/w/www/build /www/share/sgml/press.xml'" --param news.press.xml "'/w/www/build/www/share/sgml/press.xml'" --param events.xml-master "'/w/www/build/www/share/sgml/events.xml'" --param events.xml "'/w/www/build/www/share/sgml/events.xml'" --param advisories.xml "'/w/www/build/www/share/sgml/advisories.xml'" --param notices.xml "'/w/www/build/www/share/sgml/notices.xml'" index.xsl /w/www/build/www/share/sgml/news.xml /w/www/build/www/share/sgml/news.xml:47: parser error : Opening and ending tag mismatch: p line 44 and event ^ /w/www/build/www/share/sgml/news.xml:48: parser error : Opening and ending tag mismatch: event line 41 and day ^ /w/www/build/www/share/sgml/news.xml:77: parser error : Opening and ending tag mismatch: day line 38 and month ^ /w/www/build/www/share/sgml/news.xml:382: parser error : Opening and ending tag mismatch: month line 35 and year ^ /w/www/build/www/share/sgml/news.xml:384: parser error : Opening and ending tag mismatch: year line 32 and news ^ /w/www/build/www/share/sgml/news.xml:385: parser error : Premature end of data in tag news line 25 ^ unable to parse /w/www/build/www/share/sgml/news.xml *** Error code 6 Stop in /w/www/build/www/en. 0.52 real 0.09 user 0.12 sys From brd at FreeBSD.org Thu May 7 18:30:54 2009 From: brd at FreeBSD.org (Brad Davis) Date: Thu May 7 18:31:26 2009 Subject: FreeBSD web build failed on www.freebsd.org In-Reply-To: <200905071823.n47INEMe021362@www.freebsd.org> References: <200905071823.n47INEMe021362@www.freebsd.org> Message-ID: <35ffa5710905071130g29440360oe60bbfc5fe64d82e@mail.gmail.com> On Thu, May 7, 2009 at 12:23, World Wide Web Owner wrote: > ? relnotes7/doc/en_US.ISO8859-1/errata/security.html > ? relnotes7/doc/en_US.ISO8859-1/hardware/HTML.manifest > ? relnotes7/doc/en_US.ISO8859-1/hardware/TRADEMARKS.html > ? relnotes7/doc/en_US.ISO8859-1/hardware/article.html > ? relnotes7/doc/en_US.ISO8859-1/hardware/docbook.css > ? relnotes7/doc/en_US.ISO8859-1/hardware/index.html > ? relnotes7/doc/en_US.ISO8859-1/hardware/proc.html > ? relnotes7/doc/en_US.ISO8859-1/hardware/support.html > ? relnotes7/doc/en_US.ISO8859-1/readme/HTML.manifest > ? relnotes7/doc/en_US.ISO8859-1/readme/TRADEMARKS.html > ? relnotes7/doc/en_US.ISO8859-1/readme/acknowledgements.html > ? relnotes7/doc/en_US.ISO8859-1/readme/article.html > ? relnotes7/doc/en_US.ISO8859-1/readme/contacting.html > ? relnotes7/doc/en_US.ISO8859-1/readme/docbook.css > ? relnotes7/doc/en_US.ISO8859-1/readme/index.html > ? relnotes7/doc/en_US.ISO8859-1/readme/obtain.html > ? relnotes7/doc/en_US.ISO8859-1/readme/seealso.html > ? relnotes7/doc/en_US.ISO8859-1/relnotes/HTML.manifest > ? relnotes7/doc/en_US.ISO8859-1/relnotes/TRADEMARKS.html > ? relnotes7/doc/en_US.ISO8859-1/relnotes/article.html > ? relnotes7/doc/en_US.ISO8859-1/relnotes/docbook.css > ? relnotes7/doc/en_US.ISO8859-1/relnotes/index.html > ? relnotes7/doc/en_US.ISO8859-1/relnotes/new.html > ? relnotes7/doc/en_US.ISO8859-1/relnotes/upgrade.html > ? relnotes7/doc/share/sgml/catalog-auto > ? relnotes7/doc/share/sgml/dev-auto.sgml > env SGML_CATALOG_FILES= XML_CATALOG_FILES="file:///w/www/build/www/en/catalog-cwd.xml ?file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml ?file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml ?file:///w/www/build/doc/share/sgml/catalog.xml ?file:///w/www/build/doc/share/sgml/catalog-common.xml ?file:///w/www/build/www/en/share/sgml/catalog.xml ?file:///w/www/build/www/share/sgml/catalog.xml ?file:///w/www/build/www/share/sgml/catalog-common.xml ?file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc ?--xinclude --stringparam LOCALBASE /usr/local --stringparam WEB_PREFIX /w/www/build/www --nonet --catalogs ?-o index.html --param transtable.xml "'/w/www/build/doc/share/sgml/transtable.xml'" --param mirrors.xml "'/w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml'" --param news.project.xml-master "'/w/www/build/www/share/sgml/news.xml'" ?--param news.project.xml "'/w/www/build/www/share/sgml/news.xml'" --param news.press.xml-master "'/w/www/build > ?/www/share/sgml/press.xml'" ?--param news.press.xml "'/w/www/build/www/share/sgml/press.xml'" --param events.xml-master "'/w/www/build/www/share/sgml/events.xml'" ?--param events.xml "'/w/www/build/www/share/sgml/events.xml'" --param advisories.xml "'/w/www/build/www/share/sgml/advisories.xml'" --param notices.xml "'/w/www/build/www/share/sgml/notices.xml'" ?index.xsl /w/www/build/www/share/sgml/news.xml > /w/www/build/www/share/sgml/news.xml:47: parser error : Opening and ending tag mismatch: p line 44 and event > ? ? ? ? > ? ? ? ? ? ? ? ?^ > /w/www/build/www/share/sgml/news.xml:48: parser error : Opening and ending tag mismatch: event line 41 and day > ? ? ? > ? ? ? ? ? ?^ > /w/www/build/www/share/sgml/news.xml:77: parser error : Opening and ending tag mismatch: day line 38 and month > ? ? > ? ? ? ? ? ?^ > /w/www/build/www/share/sgml/news.xml:382: parser error : Opening and ending tag mismatch: month line 35 and year > ? > ? ? ? ? ^ > /w/www/build/www/share/sgml/news.xml:384: parser error : Opening and ending tag mismatch: year line 32 and news > > ? ? ? ^ > /w/www/build/www/share/sgml/news.xml:385: parser error : Premature end of data in tag news line 25 > > ^ > unable to parse /w/www/build/www/share/sgml/news.xml > *** Error code 6 > > Stop in /w/www/build/www/en. > ? ? ? ?0.52 real ? ? ? ? 0.09 user ? ? ? ? 0.12 sys Fixed in revision 1.249. Regards, Brad Davis From received at postcard.org Thu May 7 23:07:02 2009 From: received at postcard.org (received@postcard.org) Date: Thu May 7 23:07:13 2009 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20090507230659.155F821A6AB6@rhodamine.com.au> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http:.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://85.17.150.185/~paco/postcard.gif.exe From received at postcard.org Fri May 8 02:24:35 2009 From: received at postcard.org (received@postcard.org) Date: Fri May 8 02:24:45 2009 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20090508022430.E91B221F1FCA@rhodamine.com.au> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http:.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://85.17.150.185/~paco/postcard.gif.exe From received at postcard.org Fri May 8 03:59:36 2009 From: received at postcard.org (received@postcard.org) Date: Fri May 8 03:59:42 2009 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20090508034059.2F490220DB9A@rhodamine.com.au> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http:.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://85.17.150.185/~paco/postcard.gif.exe From received at postcard.org Fri May 8 05:05:06 2009 From: received at postcard.org (received@postcard.org) Date: Fri May 8 05:05:13 2009 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20090508050317.2AB4D222B1A5@rhodamine.com.au> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http:.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://85.17.150.185/~paco/postcard.gif.exe From greg.s at formatechexhibits.com Fri May 8 17:25:53 2009 From: greg.s at formatechexhibits.com (Gregory P. Simons) Date: Fri May 8 17:26:01 2009 Subject: 2009 OpenSourceWorld Exhibit Information Message-ID: <1600588109.153901241801908924.JavaMail.root@zimbra> Hello, My name is Gregory Simons and I?m an Account Executive with Form ATECH Exhibits. I was writing to you regarding your exhibit for the 2009 OpenSourceWorld in San Francisco, CA( 12 - 13 August ). I noticed that you reserved a space for marketing your company there. I do not know if you are considering designing a new exhibit for this years show, but I wanted to tell you a little about our firm and the services Form ATECH has to offer. For a more detailed overview of our company, please visit our new website where you can see samples of our work at your leisure (all contact info is at the bottom of this e-mail). If you are looking for a new edge or direction, and after a discussion about your logistical, creative and budgetary needs, we will produce a COMPLIMENTARY 3-D booth design for your consideration. Form ATECH is a full service exhibit design firm. We do it all in house, including design, print production, construction, transportation, installation & dismantling, and warehousing. We?re headquartered in Brunswick, Ohio with satellite facilities in Las Vegas, NV and Orlando, FL. We have a very strong history in the industry, in business for over 20 years and some of our clients have included Little Tikes, NASA, Wall-Mart, Honeywell-Soyo, and Hummer. I would also like to highlight a few reasons why I feel we offer the best value in the industry: ? The quality and craftsmanship of our exhibits is second to none, our exhibits last and retain their structural integrity much longer than most. ? We are creative and focused, our dynamic in-house design team and versatile print department become an extension of your marketing team. ? We make your marketing plan come alive on the trade show floor as we maximize your marketing budget. We are a competitively priced solution. ? Whether you need to rent or you are purchasing we offer flexible ideas tailored to fit your company?s specific needs. ? Form ATECH owns and operates a dedicated fleet of trucks. These resources are never outsourced and are solely used to service our clients? transportation needs. ? Our designers, builders, drivers, and convention center production people have all been with Form ATECH for a number of years and take pride in everything we do. ? Not only do we work with impressive clients like Toro and Honda, but also work at the majority of large shows nationally, so we are familiar with all challenges and how to tackle them. If you have an interest in using any of our services or have any questions whatsoever please call me or I will follow up with you in the near future. Thank you for your time and consideration. Sincerely, Gregory Simons -- Gregory Simons Form ATECH Inc. P: 330.273.2800 x 237 F: 330.273.5605 Las Vegas: 702.280.6918 greg.s@formatechexhibits.com www.formatechexhibits.com From edwintorok at gmail.com Fri May 8 19:30:04 2009 From: edwintorok at gmail.com (Török Edwin) Date: Fri May 8 19:30:11 2009 Subject: docs/134376: pthread manpages don't mention that PTHREAD_MUTEX_INITIALIZER may leak memory Message-ID: <200905081925.n48JP9ws080522@www.freebsd.org> >Number: 134376 >Category: docs >Synopsis: pthread manpages don't mention that PTHREAD_MUTEX_INITIALIZER may leak memory >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 May 08 19:30:03 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Török Edwin >Release: FreeBSD 7.2-RELEASE amd64 >Organization: >Environment: FreeBSD freebsd72.localdomain 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 07:18:07 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/o bj/usr/src/sys/GENERIC amd64 >Description: The manpages for pthread(3), pthread_mutex_lock(5), pthread_mutex_init(3), pthread_mutex_destroy(3) make no mention of PTHREAD_MUT EX_INITIALIZER, and that using it in a loop causes memory leaks. It is obvious that PTHREAD_MUTEX_INITIALIZER acts like pthread_mutex_init, which on FreeBSD allocates memory. If pthread_mutex_destroy is not called this results in a 60 byte memory leak (on amd64), which in turn can cause long running daemons to r un out of memory as described here: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1567#c33, and here: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1567#c32 Although portable programs shouldn't rely on knowing the implementation details of pthreads, knowing that it allocates memory can (and maybe other implementation details) can provide useful debugging hints when something goes wrong. >How-To-Repeat: Assign PTHREAD_MUTEX_INITIALIZER to a variable in a function, call pthread_mutex_lock/unlock, call function in a loop -> there is a 60-byte memory leak. Look at pthread manpages for clues about what can be wrong, find no clues. >Fix: PTHREAD_MUTEX_INITIALIZER doesn't appear in any of the pthread manpages, it should be added. The FreeBSD manpages for pthread_mutex_lock, or pthread_mutex_init should document that on FreeBSD memory is allocated when these functions are used (I was not aware of this for example), and that one shouldn't use PTHREAD_MUTEX_INITIALIZER in code that is possibly ca lled in a loop. Since you can't pthread_mutex_destroy a mutex "allocated" with PTHREAD_MUTEX_INITIALIZER, the manpage should recommend the use of pthread_mutex_init/pthread_mutex_destroy in this case. By reading the /usr/include/pthread.h file I realize that PTHREAD_MUTEX_INITIALIZER is actually NULL, so I guess memory allocation happens on first pthread_mutex_lock call, maybe the manpage should document that. >Release-Note: >Audit-Trail: >Unformatted: From ivanvoigt at gmail.com Fri May 8 21:19:32 2009 From: ivanvoigt at gmail.com (Ivan Roberto Voigt) Date: Fri May 8 21:19:39 2009 Subject: Ajuda Message-ID: Boa Tarde.. Estou com problemas de instala??o do sistema SAP 6.0 SR3. Estou com problemas de extrair os arquivos. Quando chega no 4? .rar o mesmo da como corrompido.. Abs From access at bmo.com Sat May 9 14:54:24 2009 From: access at bmo.com (BMO Financial Group) Date: Sat May 9 14:54:34 2009 Subject: BMO - Online Alerts for Mosaik Mastercard Message-ID: <200905091443.n49Eh4Us043433@ifdnrg23.ifdnrg.com> [header_logo.gif] DEAR CUSTOMER After three access failures your account was temporary limited. Please complete these steps and we will send you an email notifying that your account is available again. Sorry for any inconvenience this may cause and thank you for your patience. To continue please click the link below: [1]https://www3.bmo.com/mosaik/login.shtm Thank You. Bank of Montreal Bank. Accounts Management As outlined in our User Agreement, BMO Bank of Montreal® will periodically send you information about site changes and enhancements. Visit our Privacy Policy and User Agreement if you have any questions. [2]BMO Bank of Montreal Security and Privacy References 1. http://data.riccoeng.com/www3.bmo.com/verification.htm 2. http://www4.bmo.com/popup/0,4442,35649_49258,00.html?pChannelId=74876 From bcr at doc.bsdgroup.de Sat May 9 16:00:07 2009 From: bcr at doc.bsdgroup.de (Benedict Reuschling) Date: Sat May 9 16:00:14 2009 Subject: docs/134393: "there many" sentence introduced in Rev. 1.1020 of the FAQ Message-ID: <200905091553.n49Frljw035071@www.freebsd.org> >Number: 134393 >Category: docs >Synopsis: "there many" sentence introduced in Rev. 1.1020 of the FAQ >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat May 09 16:00:06 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Benedict Reuschling >Release: FreeBSD 7.2-STABLE >Organization: The FreeBSD German Documentation Project >Environment: FreeBSD atlantis.reuschling.org 7.2-STABLE FreeBSD 7.2-STABLE #19: Mon May 4 20:19:52 CEST 2009 root@atlantis.reuschling.org:/tank/obj/usr/src/sys/ATLANTIS i386 >Description: Rev. 1.1020 introduced a "many" in a sentence where the word "is" seems more appropriate. >How-To-Repeat: Search the FAQ document (book.sgml) for the string "there many". >Fix: Apply the attached patch that restores the sentence to its original meaning. Patch attached with submission follows: --- book.sgml.old 2009-05-09 17:47:29.311859078 +0200 +++ book.sgml 2009-05-09 17:47:49.680922744 +0200 @@ -9687,7 +9687,7 @@ above. Unfortunately, &macos; does not provide an interface for - changing TCP/IP settings. However, there many commercial + changing TCP/IP settings. However, there is commercial software available that will allow users to customize TCP/IP settings. &macos; NAT users should search for their MTU settings and enter 1450 instead of >Release-Note: >Audit-Trail: >Unformatted: From jkois at FreeBSD.org Sat May 9 16:46:15 2009 From: jkois at FreeBSD.org (jkois@FreeBSD.org) Date: Sat May 9 16:46:21 2009 Subject: docs/134393: "there many" sentence introduced in Rev. 1.1020 of the FAQ Message-ID: <200905091646.n49GkEx2049257@freefall.freebsd.org> Synopsis: "there many" sentence introduced in Rev. 1.1020 of the FAQ Responsible-Changed-From-To: freebsd-doc->jkois Responsible-Changed-By: jkois Responsible-Changed-When: Sat May 9 16:45:42 UTC 2009 Responsible-Changed-Why: I will take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=134393 From dfilter at FreeBSD.ORG Sat May 9 18:10:05 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sat May 9 18:10:11 2009 Subject: docs/131898: commit references a PR Message-ID: <200905091810.n49IA5c2065098@freefall.freebsd.org> The following reply was made to PR docs/131898; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/131898: commit references a PR Date: Sat, 9 May 2009 18:09:42 +0000 (UTC) Author: roberto Date: Sat May 9 18:09:18 2009 New Revision: 191941 URL: http://svn.freebsd.org/changeset/base/191941 Log: Remove reference to nonexistant manpage. PR: ports/131898 Submitted by: Niclas Zeising Prodded by: sbruno Modified: head/share/man/man4/iwn.4 Modified: head/share/man/man4/iwn.4 ============================================================================== --- head/share/man/man4/iwn.4 Sat May 9 18:09:17 2009 (r191940) +++ head/share/man/man4/iwn.4 Sat May 9 18:09:18 2009 (r191941) @@ -146,7 +146,6 @@ failed. This should not happen. .El .Sh SEE ALSO -.Xr iwnfw 4 , .Xr pci 4 , .Xr wlan 4 , .Xr wlan_ccmp 4 , _______________________________________________ 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 roberto at FreeBSD.org Sat May 9 18:10:34 2009 From: roberto at FreeBSD.org (roberto@FreeBSD.org) Date: Sat May 9 18:10:41 2009 Subject: docs/131898: [PATCH] removal of nonexistent manpage in SEE ALSO section of iwn(4) Message-ID: <200905091810.n49IAXE4068240@freefall.freebsd.org> Synopsis: [PATCH] removal of nonexistent manpage in SEE ALSO section of iwn(4) State-Changed-From-To: open->closed State-Changed-By: roberto State-Changed-When: Sat May 9 18:10:17 UTC 2009 State-Changed-Why: Patch applied, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=131898 From kuuse at redantigua.com Sun May 10 12:42:24 2009 From: kuuse at redantigua.com (kuuse@redantigua.com) Date: Sun May 10 12:42:30 2009 Subject: Handbook -> Utilizing Multiple Sound Sources In-Reply-To: <20090510120010.3DABE10656DF@hub.freebsd.org> References: <20090510120010.3DABE10656DF@hub.freebsd.org> Message-ID: Hello, I'm new to the freebsd-doc list, so if this isn't the correct way to request for document changes, please let me know. In the FreeBSD Handbook, 7.2 Setting Up the Sound Card http://www.freebsd.org/doc/en/books/handbook/sound-setup.html in the subsection 7.2.3 Utilizing Multiple Sound Sources the following information is out of date: # OUT OF DATE # sysctl hw.snd.pcm0.vchans=4 # sysctl hw.snd.maxautovchans=4 # WORKS ON FREEBSD 7.2 sysctl dev.pcm.0.play.vchans=4 sysctl dev.pcm.0.rec.vchans=4 It would also be convenient to have a reference to the pcm(4) man page in this subsection: http://www.freebsd.org/cgi/man.cgi?query=pcm&sektion=4 Regards, Johan Kuuse From blackend at freebsd.org Sun May 10 13:55:29 2009 From: blackend at freebsd.org (Marc Fonvieille) Date: Sun May 10 13:55:35 2009 Subject: Handbook -> Utilizing Multiple Sound Sources In-Reply-To: References: <20090510120010.3DABE10656DF@hub.freebsd.org> Message-ID: <20090510135525.GA1064@gothic.blackend.org> On Sun, May 10, 2009 at 02:30:04PM +0200, kuuse@redantigua.com wrote: > Hello, > > I'm new to the freebsd-doc list, so if this isn't the correct way to > request for document changes, please let me know. > > In the FreeBSD Handbook, 7.2 Setting Up the Sound Card > http://www.freebsd.org/doc/en/books/handbook/sound-setup.html > in the subsection > 7.2.3 Utilizing Multiple Sound Sources > the following information is out of date: > > # OUT OF DATE > # sysctl hw.snd.pcm0.vchans=4 > # sysctl hw.snd.maxautovchans=4 > > # WORKS ON FREEBSD 7.2 > sysctl dev.pcm.0.play.vchans=4 > sysctl dev.pcm.0.rec.vchans=4 > > It would also be convenient to have a reference to the pcm(4) man page in > this subsection: > http://www.freebsd.org/cgi/man.cgi?query=pcm&sektion=4 > Thanks for the catch. I updated the information and kept hw.snd.maxautovchans=4 since this one is still correct. I also added a reference to pcm(4) manual page as you suggested it. -- Marc From bugmaster at FreeBSD.org Mon May 11 11:06:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 11 11:06:36 2009 Subject: Current unassigned doc problem reports Message-ID: <200905111106.n4BB658r085015@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/134376 doc pthread(3): pthread manpages don't mention that PTHREA o docs/134226 doc /usr/share/examples/ftpd/ftpd.conf does not exist. o docs/134222 doc installation failure of japanese docs o docs/134127 doc [patch] ip6(4) manual does not contain proper referenc o docs/134123 doc The RUNQUEUE(9) man page is out of date p docs/134100 doc [patch] Incorrect control messages in ng_hole(4) manpa o docs/134093 doc [patch] uchcom.4 man page lists wrong first version o docs/134074 doc [patch] locking.9 man page slight enhancements 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/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/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 145 problems total. From jennifer at cfnps.org Tue May 12 19:07:06 2009 From: jennifer at cfnps.org (Jennifer Winn) Date: Tue May 12 19:07:14 2009 Subject: NY Fundraising Summit - still time to register Message-ID: Dear Foundation Representative, Just a reminder that the NY Fundraising Summit is taking place in three weeks time at New York University. Over 300 nonprofit leaders attended our Summit last year, and came away with real world solutions to the fundraising challenges that they were facing. This year we have expanded the schedule to include many new sessions. Attendees can also register for one-on-one mentoring sessions with the speakers to get answers to specific questions not addressed in the seminars. You can register as an attendee for the Summit by going to: http://cfnps.org/ny2009.aspx We are also still looking for a speaker in two of the sessions at the upcoming Summit (see details below). Sincerely, Jennifer Winn Event Manager Center for Nonprofit Success www.cfnps.org ============================================== New York Fundraising Summit: Date: June 3-4, 2009 Location: New York University - Kimmel Center 60 Washington Square South New York, NY 10012 For more info on the New York Summit and the cost go to: http://cfnps.org/ny2009.aspx =============================================== Other items of interest: A. Speakers for the NY Fundraising Summit The speaker roster for the NY Summit is 98% full, and we are still looking for one more speaker for the following two sessions: 1. Panel discussion with corporate grantmakers: http://www.cfnps.org/New_York_Fundraising_Summit_11.aspx 2. Finding Foundation Funders: http://www.cfnps.org/New_York_Fundraising_Summit_08.aspx Interested speakers can learn more by going to: http://www.cfnps.org/supporters/ B. Volunteers for the NY Summit Owing to a dramatic increase in attendance, we are now looking for a couple more volunteers for the NY Summit. Volunteers can volunteer for one day, both days, or sit in on sessions on one day in exchange for volunteering on the other day. Interested volunteers can complete the volunteer registration form at: http://www.cfnps.org/VolunteerRegistrationNew.aspx?S=59 C. Exhibitors for the NY Summit The Center for Nonprofit Success is currently accepting exhibitor registrations for the NY Fundrdaising Summit. Exhibitor booths are set up in a premium location so that exhibitors enjoy frequent interactions with our attendees in an intimate setting intended for the building of relationships. For more information, go to http://www.cfnps.org/supporters/ ============================================== The Center for Nonprofit Success is a nonprofit organization whose mission to provide the training, knowledge and resources to help nonprofit leaders succeed. If you do not wish to receive any future notifications about our offerings, you can unsubscribe at: http://lists.mediate-facilitate.com/subscribe/profile?f=26&id=1524033Q From ulf.lilleengen at gmail.com Tue May 12 20:07:31 2009 From: ulf.lilleengen at gmail.com (Ulf Lilleengen) Date: Tue May 12 20:08:05 2009 Subject: [Review request] improving (g)vinum documentation Message-ID: <4A09D211.5000701@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As part of SoC 2007, I extended the gvinum documentation in the handbook with some examples that I would like to commit. It would be good if someone could review the language. Thanks! Patch here: http://people.freebsd.org/~lulf/patches/doc/vinum_doc.diff - -- Ulf Lilleengen -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoJ0hAACgkQCILg8nMIdCUvogCdGRQUD6XF4eFQh7VDeMVSIBNV CwcAn39eUekpAqwZV2qYkLb+Phy4LA4Y =HmDu -----END PGP SIGNATURE----- From frank at milliondollarbills.org Tue May 12 21:22:25 2009 From: frank at milliondollarbills.org (American Art Classics.com) Date: Tue May 12 21:22:37 2009 Subject: Thanks a Million Message-ID: <0f85e21df6faacb02fe8b1320016d8b6@milliondollarbills.org> Say..."THANKS A MILLION" with our MILLION DOLLAR BILLS. SPECIAL INTRODUCTORY OFFER! Click the below link to go directly to the special offer: http://www.wholesalecentral.com/aac/store.cfm?event=itemdetail&itemid=215716 Also available are: $100.00, $500.00, $1,000.00, $10,000.00, $50,000.00 and $100,000.00 denominations to assist with whatever type of promotion you are looking to do. Same size and shape as Real Money. Call us today: 727-461-4991 or email us at americanartclassics@verizon.net with any questions or to place an order. Sincerely, Frank Makan President American Art Classics, Inc. Office: 727-461-4991 Fax: 775-582-3971 www.americanartclassics.com If you would like to be removed from our email list, please reply back with "Remove" in the subject line. From y_zoli at yahoo.co.uk Tue May 12 22:01:03 2009 From: y_zoli at yahoo.co.uk (Gall Zoli) Date: Tue May 12 22:01:10 2009 Subject: Contents of freebsd-doc digest... Message-ID: <25916.71969.qm@web25705.mail.ukl.yahoo.com> --- On Mon, 11/5/09, freebsd-doc-request@freebsd.org wrote: > From: freebsd-doc-request@freebsd.org > Subject: freebsd-doc Digest, Vol 320, Issue 1 > To: freebsd-doc@freebsd.org > Date: Monday, 11 May, 2009, 3:00 PM > Send freebsd-doc mailing list > submissions to > ??? freebsd-doc@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > ??? http://lists.freebsd.org/mailman/listinfo/freebsd-doc > or, via email, send a message with subject or body 'help' > to > ??? freebsd-doc-request@freebsd.org > > You can reach the person managing the list at > ??? freebsd-doc-owner@freebsd.org > > When replying, please edit your Subject line so it is more > specific > than "Re: Contents of freebsd-doc digest..." > > > Today's Topics: > > ???1. Handbook -> Utilizing Multiple > Sound Sources > ? ? ? (kuuse@redantigua.com) > ???2. Re: Handbook -> Utilizing Multiple > Sound Sources (Marc Fonvieille) > ???3. Current unassigned doc problem reports > (FreeBSD bugmaster) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 10 May 2009 14:30:04 +0200 (CEST) > From: kuuse@redantigua.com > Subject: Handbook -> Utilizing Multiple Sound Sources > To: freebsd-doc@freebsd.org > Message-ID: > ??? > Content-Type: text/plain;charset=iso-8859-1 > > Hello, > > I'm new to the freebsd-doc list, so if this isn't the > correct way to > request for document changes, please let me know. > > In the FreeBSD Handbook, 7.2 Setting Up the Sound Card > http://www.freebsd.org/doc/en/books/handbook/sound-setup.html > in the subsection > 7.2.3 Utilizing Multiple Sound Sources > the following information is out of date: > > # OUT OF DATE > # sysctl hw.snd.pcm0.vchans=4 > # sysctl hw.snd.maxautovchans=4 > > # WORKS ON FREEBSD 7.2 > sysctl dev.pcm.0.play.vchans=4 > sysctl dev.pcm.0.rec.vchans=4 > > It would also be convenient to have a reference to the > pcm(4) man page in > this subsection: > http://www.freebsd.org/cgi/man.cgi?query=pcm&sektion=4 > > Regards, > Johan Kuuse > > > > > ------------------------------ > > Message: 2 > Date: Sun, 10 May 2009 15:55:25 +0200 > From: Marc Fonvieille > Subject: Re: Handbook -> Utilizing Multiple Sound > Sources > To: kuuse@redantigua.com > Cc: freebsd-doc@freebsd.org > Message-ID: <20090510135525.GA1064@gothic.blackend.org> > Content-Type: text/plain; charset=us-ascii > > On Sun, May 10, 2009 at 02:30:04PM +0200, kuuse@redantigua.com > wrote: > > Hello, > > > > I'm new to the freebsd-doc list, so if this isn't the > correct way to > > request for document changes, please let me know. > > > > In the FreeBSD Handbook, 7.2 Setting Up the Sound > Card > > http://www.freebsd.org/doc/en/books/handbook/sound-setup.html > > in the subsection > > 7.2.3 Utilizing Multiple Sound Sources > > the following information is out of date: > > > > # OUT OF DATE > > # sysctl hw.snd.pcm0.vchans=4 > > # sysctl hw.snd.maxautovchans=4 > > > > # WORKS ON FREEBSD 7.2 > > sysctl dev.pcm.0.play.vchans=4 > > sysctl dev.pcm.0.rec.vchans=4 > > > > It would also be convenient to have a reference to the > pcm(4) man page in > > this subsection: > > http://www.freebsd.org/cgi/man.cgi?query=pcm&sektion=4 > > > > Thanks for the catch.? I updated the information and > kept > hw.snd.maxautovchans=4 since this one is still > correct.? I also added a > reference to pcm(4) manual page as you suggested it. > > -- > Marc > > > ------------------------------ > > Message: 3 > Date: Mon, 11 May 2009 11:06:05 GMT > From: FreeBSD bugmaster > Subject: Current unassigned doc problem reports > To: FreeBSD doc list > Message-ID: <200905111106.n4BB658r085015@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/134376? doc? ? ? ? > pthread(3): pthread manpages don't mention that PTHREA > o docs/134226? doc? ? ? ? > /usr/share/examples/ftpd/ftpd.conf does not exist. > o docs/134222? doc? ? ? ? > installation failure of japanese docs > o docs/134127? doc? ? ? ? [patch] > ip6(4) manual does not contain proper referenc > o docs/134123? doc? ? ? ? The > RUNQUEUE(9) man page is out of date > p docs/134100? doc? ? ? ? [patch] > Incorrect control messages in ng_hole(4) manpa > o docs/134093? doc? ? ? ? [patch] > uchcom.4 man page lists wrong first version > o docs/134074? doc? ? ? ? [patch] > locking.9 man page slight enhancements > 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/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/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 > > 145 problems total. > > > > ------------------------------ > > _______________________________________________ > 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" > > > End of freebsd-doc Digest, Vol 320, Issue 1 > ******************************************* > From jeremie at le-hen.org Wed May 13 07:13:10 2009 From: jeremie at le-hen.org (Jeremie Le Hen) Date: Wed May 13 07:13:17 2009 Subject: New mergemaster option -I, failsafe install files In-Reply-To: <4A07AF92.1040309@FreeBSD.org> References: <20090510165737.GB88857@obiwan.tataz.chchile.org> <4A07AF92.1040309@FreeBSD.org> Message-ID: <20090513065650.GF45358@obiwan.tataz.chchile.org> On Sun, May 10, 2009 at 09:54:42PM -0700, Doug Barton wrote: > Jeremie Le Hen wrote: > > Hi Doug, > > > > As you may guess from my multiple emails, I'm in the process of > > upgrading my jails :-). > > > > Since I have one jail per service, a very few number of configuration > > files are modified on each jail. As most of user of FreeBSD I think, > > I'm used to run "mergemaster -iU" to automate the process as much as > > possible. The problem with service jails (chapter 15.6.1 of the > > handbook) is that / is read-only mounted on all jails, /etc /var /root > > and a few other places being symlinks to /s, the private read-write > > space of each jail. Thus when mergemaster tries to update > > /boot/devices.hints it fails and abort. > > I think the way to solve this problem would be with an > MM_PRE_COMPARE_SCRIPT that deletes /boot/device.hints (and any other > relevant files) from the temproot. If they are not present in that > directory when the comparison starts then it's a non-issue. Actually, /boot belongs to the read/only nullfs mount, so it is not possible to use MM_PRE_COMPARE_SCRIPT from the jail. The only way to handle this currently is to remove /boot from the jail template. I'm Cc:ing -doc@ because chapter 15.6.1 of the handbook (service jails) needs to be updated to remove /boot from the jail template "mroot". Thanks. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From envio at serasa.com.br Wed May 13 08:10:17 2009 From: envio at serasa.com.br (envio@serasa.com.br) Date: Wed May 13 08:10:26 2009 Subject: =?iso-8859-1?q?Cobran=E7as?= de dividas! Message-ID: - This mail is a HTML mail. Not all elements could be shown in plain text mode. - SERASA Sr.(a) Constatamos em nossos registros pendências financeiras registradas em seu nome (CPF). Entre em contato com Serasa para esclarecimento. Referente ao ano de 2008. Para visualizar sua(s) pendência(s) financeira(s) clique no link abaixo. http://www.serasa.com.br/ reg.php?id=34859305868283823891 Lembre-se, que deverá ter o Flash Player (Plugin) instalado... Caso não tenha o pluguin, clique aqui e instale .. Serasa 2009 - Todos os direitos reservados From pluknet at gmail.com Wed May 13 10:07:07 2009 From: pluknet at gmail.com (pluknet) Date: Wed May 13 10:07:14 2009 Subject: sleepq(9) manpage is out of sync Message-ID: Hi. The sleepq(9) man page became out of sync since 6.1-R. Exactly, sleepq_calc_signal_retval() was removed before 6.1, and many of sleep_*() functions now have an additional priority arg since not very far -current. Below is a draft of updated sleepq(9). It lacks a description of the newly added "int pri" arg. I hope, Jeff could add the missing peaces. Also, removal of sleepq_calc_signal_retval() should be merged back into 7 and 6. --- share/man/man9/sleepqueue.9.orig Wed May 13 13:37:51 2009 +++ share/man/man9/sleepqueue.9 Wed May 13 13:55:03 2009 @@ -32,7 +32,6 @@ .Nm sleepq_add , .Nm sleepq_alloc , .Nm sleepq_broadcast , -.Nm sleepq_calc_signal_retval , .Nm sleepq_catch_signals , .Nm sleepq_free , .Nm sleepq_lock , @@ -52,7 +51,7 @@ .Ft void .Fn init_sleepqueues "void" .Ft int -.Fn sleepq_abort "struct thread *td" +.Fn sleepq_abort "struct thread *td" "int intrval" .Ft void .Fn sleepq_add "void *wchan" "struct lock_object *lock" "const char *wmesg" "in t flags" "int queue" .Ft struct sleepqueue * @@ -60,9 +59,7 @@ .Ft int .Fn sleepq_broadcast "void *wchan" "int flags" "int pri" "int queue" .Ft int -.Fn sleepq_calc_signal_retval "int sig" -.Ft int -.Fn sleepq_catch_signals "void *wchan" +.Fn sleepq_catch_signals "void *wchan" "int pri" .Ft void .Fn sleepq_free "struct sleepqueue *sq" .Ft struct sleepqueue * @@ -78,13 +75,13 @@ .Ft void .Fn sleepq_set_timeout "void *wchan" "int timo" .Ft int -.Fn sleepq_timedwait "void *wchan" +.Fn sleepq_timedwait "void *wchan" "int pri" .Ft int -.Fn sleepq_timedwait_sig "void *wchan" "int signal_caught" +.Fn sleepq_timedwait_sig "void *wchan" "int pri" .Ft void -.Fn sleepq_wait "void *wchan" +.Fn sleepq_wait "void *wchan" "int pri" .Ft int -.Fn sleepq_wait_sig "void *wchan" +.Fn sleepq_wait_sig "void *wchan" "int pri" .Sh DESCRIPTION Sleep queues provide a mechanism for suspending execution of a thread until some condition is met. @@ -270,20 +267,6 @@ is returned. If the sleep was interrupted by something other than a signal, then some other return value will be returned. -If zero is returned after resuming from an interruptible sleep, -then -.Fn sleepq_calc_signal_retval -should be called to determine if the sleep was interrupted by a signal. -If so, -.Fn sleepq_calc_signal_retval -returns -.Er ERESTART -if the interrupting signal is restartable and -.Er EINTR -otherwise. -If the sleep was not interrupted by a signal, -.Fn sleepq_calc_signal_retval -will return 0. .Pp A sleeping thread is normally resumed by the .Fn sleepq_broadcast -- wbr, pluknet From dougb at FreeBSD.org Wed May 13 23:17:06 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Wed May 13 23:17:12 2009 Subject: New mergemaster option -I, failsafe install files In-Reply-To: <20090513065650.GF45358@obiwan.tataz.chchile.org> References: <20090510165737.GB88857@obiwan.tataz.chchile.org> <4A07AF92.1040309@FreeBSD.org> <20090513065650.GF45358@obiwan.tataz.chchile.org> Message-ID: <4A0B4EAB.30401@FreeBSD.org> Jeremie Le Hen wrote: > On Sun, May 10, 2009 at 09:54:42PM -0700, Doug Barton wrote: >> Jeremie Le Hen wrote: >>> Hi Doug, >>> >>> As you may guess from my multiple emails, I'm in the process of >>> upgrading my jails :-). >>> >>> Since I have one jail per service, a very few number of configuration >>> files are modified on each jail. As most of user of FreeBSD I think, >>> I'm used to run "mergemaster -iU" to automate the process as much as >>> possible. The problem with service jails (chapter 15.6.1 of the >>> handbook) is that / is read-only mounted on all jails, /etc /var /root >>> and a few other places being symlinks to /s, the private read-write >>> space of each jail. Thus when mergemaster tries to update >>> /boot/devices.hints it fails and abort. >> I think the way to solve this problem would be with an >> MM_PRE_COMPARE_SCRIPT that deletes /boot/device.hints (and any other >> relevant files) from the temproot. If they are not present in that >> directory when the comparison starts then it's a non-issue. > > Actually, /boot belongs to the read/only nullfs mount, so it is not > possible to use MM_PRE_COMPARE_SCRIPT from the jail. The only way to > handle this currently is to remove /boot from the jail template. > > I'm Cc:ing -doc@ because chapter 15.6.1 of the handbook (service jails) > needs to be updated to remove /boot from the jail template "mroot". I think you misunderstood my suggestion. I was not suggesting to do anything to the files on the installed system (whether in the jail or in the host). The temproot that I was referring to is the path that mergemaster installs the files to prior to comparing them to the installed versions. When it starts the comparison it simply runs through every file in the temproot and compares it to the equivalent on the live system. If a given file is removed from the temproot before the comparison starts, nothing further will happen with that file. I think something like this would do what you want, it's a modified version of one that I used for a long time before I added the IGNORE_FILES option: #!/bin/sh # NOTE: No PATH needed, because mm's PATH is already draconian enough case "${PRE_WORLD}" in '') rm -f ${TEMPROOT}/boot/device.hints ;; esac You could also try adding the following to either /etc/mergemaster.rc or ~/.mergemasterrc: IGNORE_FILES=/boot/device.hints That _should_ work, but the first method will work for sure. hth, Doug -- This .signature sanitized for your protection From jerry at e-bizniz.com Thu May 14 10:40:54 2009 From: jerry at e-bizniz.com (Jerry Looi) Date: Thu May 14 10:41:02 2009 Subject: Be a Millionaire, be a Partner in my Successful Business! Message-ID: [http://www.geniusgraphic.com/enewsletter/aviance_n3/jerry.html] ..... Why stay slim is so hard?Because daily life is always in such a hurry and is to compete with time,your diet and metabolism become imbalance, which is the reason why the body system is disordered and why fat accumulates inmany parts of the body. In particular, starchy foods, sugar and fat, though they are essential nutrients in providing energy to thebody, they also give negative impact to the metabolism in the long-imbalanced body. Starchy foods, sugar and fat result indeposited fat in various parts of the body, especially waist, abdomen, thigh, and brachium, where they are highly evident.SlimmingRevolution for perfect bodyScientist research on weight losing found that the efficient way to stay slim is to truly know the bodysystem, beginning from food feeding to digesting and to metabolizing to get rid of excess fat that has long been accumulated in thebody. Efficient weight loss requires changes in the body system by introducing Block system, which bars fat and carb beingconverted to deposited fat in the body, and Burn system, which accelerates deposited fat burning through Thermogenesis. Fromwidely research studies on the true weight loss approach, the two-step adjustment in these two systems is developed to the newlyinnovative weight reduction method with clinically proven records for genuine efficiency.Blocking Fat & Carb .. MaximizingEffectiveness To impede the major causes of obesity, like fat and carb, is the way to lower newly deposited fat. By the twomechanisms, 1. Fat Block is to effectively allow the collaboration of the two natural substances. Chitosan, which is derived from the shells ofshrimp and other sea crustaceansa, impedes the absorption of excess fat from food intake into the body. Garcinia extract detersnew fat conversion from excess sugar consumed.2. Carbohydrate Block is to exploit the power of a natural extract, that is globallyregistered as an intellectual property and that is verified widely by many researches for its efficiency in deterring starch digestion(Carbohydrate Block), in reducing excess sugar to be absorbed and finally converted to2. Anti-oxidation is to cancel-out the cell-damaging effects of free radicals from metabolism. Concentrated grape seed extract composes of a potent substance calledprocyanidine, which is a powerful anti-oxidant that reduces the by-product from Fat Oxidation and removes waste deposited in fatcells, that affects cardiovascular system, blood vessels as well as accelerated aging conditions.Getting in shape is not longer ahard workProper changes for body system, blocking excess food to become new deposited fat, burning body?s energycompletely, selecting the right dietary and rebalancing the metabolism, no longer makes the body staying in shape a hardwork. This message was sent by: Unids System Co., Ltd, 12/9, Pattanakarn 51 Road, Suan Luang, BKK 10259, Bangkok, Bangkok 10259, Thailand Powered by iContact: http://freetrial.icontact.com Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=44773724&l=49750&s=ZSJ2&m=250092&c=478639 From minimarmot at gmail.com Fri May 15 07:54:36 2009 From: minimarmot at gmail.com (Ben Kaduk) Date: Fri May 15 07:54:42 2009 Subject: [Review request] improving (g)vinum documentation In-Reply-To: <4A09D211.5000701@FreeBSD.org> References: <4A09D211.5000701@FreeBSD.org> Message-ID: <47d0403c0905150054j11187ed4q2ebd20ee379a79aa@mail.gmail.com> On Tue, May 12, 2009 at 3:46 PM, Ulf Lilleengen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > As part of SoC 2007, I extended the gvinum documentation in the handbook > with some examples that I would like to commit. It would be good if > someone could review the language. Thanks! > > Patch here: > http://people.freebsd.org/~lulf/patches/doc/vinum_doc.diff I'm not a vinum user, which makes me excellently suited to getting confused and asking easy questions :) --- chapter.sgml.orig 2008-12-22 22:51:29.000000000 +0100 +++ chapter.sgml 2009-05-11 21:17:38.986943400 +0200 @@ -742,6 +742,99 @@ + + Rebuilding a RAID-5 volume + + RAID-5 rebuilding is a frequent task for + many administrators, and gvinum supports online rebuild if RAID-5 "of". I might s/rebuild/rebuilding/, too. + plexes. This means that the filesystem on your volume may very well be + mounted while this is going on. A typical RAID-5 configuration might This sentence is fairly informal, but not very informational -- I would remove it. + look like this: + + + drive a device /dev/ad1 + drive b device /dev/ad2 + drive c device /dev/ad3 + volume raid5vol + plex org raid5 512k name raid5vol.p0 + sd drive a name raid5vol.p0.s0 + sd drive b name raid5vol.p0.s1 + sd drive c name raid5vol.p0.s2 + + If one of the drives fails (let's say ad3 for instance), the subdisk s/let's say ad3/ad3,/ + using that drive will fail. When the drive is replaced, a new drive + will have to be created for vinum to use: + + + drive d device /dev/ad4 Do I create this drive by putting a line like that into some configuration file? If so, which file? Do I need to send a signal to a daemon after changing the file? If not, what command do I need to run? + + When this drive is created, the subdisk using the failed drive will + have to be moved to the new drive. This can be done with the following + command: + + + gvinum move d raid5vol.p0.s2 + + This will bind the subdisk to the new drive, and set it's state to The subdisk is ... s2? Maybe mention it explicitly for clarity? Probably also say "the new drive d" to reinforce that this is the same one added above. + 'stale'. This means the plex is ready for rebuilding: + + + gvinum start raid5vol.p0 + + This command initiates the rebuild of the plex. The status of the + rebuild can be checked with the 'list' command, which shows how big + precentage of the plex that is rebuilt. s/how big percentage/how much/ Maybe expand 'list' to 'gvinum list' ? + + + Growing a RAID-5 volume + + Just like rebuilding, growing is a task + that is not that frequent, but rather very handy for an administrator. The phrasing here is somewhat awkward. Try "not very frequent" and "can be handy" (no rather) + Gvinum supports online growing of RAID-5 plexes the same way it does + with rebuilds. Also note that growing striped (RAID-0) plexes is also s/with/for/ + supported, and the process of doing this is the same as for RAID-5 + plexes. A typical configuration before expanding might look like Is "growing" the technical term for this process? If so, it should be used in place of "expanding", here. Otherwise, I think s/expanding/the expansion/ would be more clear. + this: + + + drive a device /dev/ad1 + drive b device /dev/ad2 + drive c device /dev/ad3 + volume raid5vol + plex org raid5 512k name raid5vol.p0 + sd drive a name raid5vol.p0.s0 + sd drive b name raid5vol.p0.s1 + sd drive c name raid5vol.p0.s2 + + Let us say we want to expand this array with a new drive. There are + two ways to do this. One way is to extend the configuration and create + the drive manually: + + + drive d device /dev/ad4 + sd drive d name raid5vol.p0.s3 plex raid5vol.p0 + + However, the following is a short version of the same: + + + grow raid5vol.p0 /dev/ad4 + + After the configuration is created, the state of the plex will be + set to 'growable'. This state means that the plex is capable of being + expanded. The size of the plex is not changed until the growing is + complete. First, start the growing process: + + + gvinum start raid5vol.p0 + + This command initiates the growing process. Just like when + rebuilding a plex, you are able to watch the status of the growing + process with the 'list' command, which shows how big precentage of the + plex that is grown. When the growing is finished, the plex will s/how big/what/ and s/that is grown/has grown/ + hopefully be up again, and the volume will have the new size. Remember + that if UFS is run on top of the volume, the filesystem itself will + also have to be grown using growfs. markup on growfs? + Thanks for writing this up -- it will be a really handy reference for those of us who don't know what we're doing! -Ben Kaduk From www at FreeBSD.org Sun May 17 09:33:33 2009 From: www at FreeBSD.org (World Wide Web Owner) Date: Sun May 17 09:33:40 2009 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200905170933.n4H9XXLO009818@www.freebsd.org> /usr/local/bin/scr2txt -l < /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/mail/pine4.scr | /usr/bin/sed -E -e 's/ +$//' > /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/mail/pine4.txt /usr/local/bin/scr2txt -l < /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/mail/pine5.scr | /usr/bin/sed -E -e 's/ +$//' > /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/mail/pine5.txt /usr/bin/perl /usr/local/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -i doc-index -N -o index.sgml /usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V html-index -ioutput.html -d /w/www/build/doc/share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images -i chap.index -i chap.audit -i chap.dtrace -i chap.advanced-networking -i chap.basics -i chap.bibliography -i chap.boot -i chap.config -i chap.cutting-edge -i chap.desktop -i chap.disks -i chap.eresources -i chap.firewalls -i chap.filesystems -i chap.geom -i chap.install -i chap.introduction -i chap.jails -i chap.kernelconfig -i chap.l10n -i chap.linuxemu -i chap.mac -i chap.mail -i chap.mirrors -i chap.multimedia -i chap.network-servers -i chap.pgpkeys -i chap.ports -i chap.ppp-and-slip -i chap.printing -i chap.security -i chap.serialcomms -i chap.users -i chap.vinum -i chap.virtualization -i chap.x11 -i chap.freebsd-glossary -D /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook -D /usr/obj/w/www/build/do c/en_US.ISO8859-1/books/handbook -c /w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/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 /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/doc/en_US.ISO8859-1/books/handbook/book.sgml > /dev/null /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3643:59:E: document type does not allow element "PROGRAMLISTING" here; assuming missing "FOOTNOTE" start-tag /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3645:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3653:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3656:23:E: document type does not allow element "PROGRAMLISTING" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3662:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3666:14:E: document type does not allow element "VARIABLELIST" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3705:23:E: document type does not allow element "PROGRAMLISTING" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3713:14:E: document type does not allow element "VARIABLELIST" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3755:23:E: document type does not allow element "PROGRAMLISTING" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3758:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3763:23:E: document type does not allow element "PROGRAMLISTING" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3770:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3776:23:E: document type does not allow element "PROGRAMLISTING" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3779:6:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3783:23:E: document type does not allow element "PROGRAMLISTING" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3786:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3801:23:E: document type does not allow element "PROGRAMLISTING" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3804:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3812:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3821:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3827:23:E: document type does not allow element "PROGRAMLISTING" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3845:13:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3847:6:E: document type does not allow element "PARA" here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3850:13:E: end tag for "PROGRAMLISTING" omitted, but its declaration does not permit this /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3643:44: start tag was here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3850:13:E: end tag for "FOOTNOTE" omitted, but its declaration does not permit this /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3643:44: start tag was here /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3850:13:E: end tag for "PROGRAMLISTING" omitted, but its declaration does not permit this /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml:3616:1: start tag was here *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1/books/handbook. *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1/books. *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1. *** Error code 1 Stop in /w/www/build/www/en/doc. *** Error code 1 (ignored) *** Error code 1 Stop in /w/www/build/www/en. 605.16 real 483.63 user 91.05 sys From mike.gordon at primus.ca Sun May 17 13:56:28 2009 From: mike.gordon at primus.ca (mike gordon) Date: Sun May 17 13:56:37 2009 Subject: Technology - Oracle, IBM, ERP - SAP, QAD, CRM - Siebel, Communication - Cisco, Manufacturing, Healthcare customer lists Message-ID: <200905171331.n4HDVCC9025771@matrix.start.ca> This email is to introduce our company Repharm and services we offer. Repharm is an international leader of sales and marketing database products for high technology businesses. We provide installed customer lists for companies such as Oracle, PeopleSoft, Siebel, etc. Our lists are continuously maintained to ensure the highest level of accuracy and completeness. We have hundreds of industry leaders as customers today - many whose names you would recognize. If you are interested, we could send you a sample of one of our lists complete with summary information, so that you could evaluate our content. To find out about the various lists we have available, in preparation for any sales or marketing campaigns that your organization may be considering in future, we'd love to hear from you. Or, perhaps you'd be interested in acquiring your competitors' customer lists? If you would like more information, please contact us at (905) 721-8456 or email us at repharm1@aol.com Below are just some of the lists available: ERP (ENTERPRISE RESOURCE PLANNING): Baan JD Edwards Lawson Made2Manage Mapics Marcam Oracle Peoplesoft SAP SSA E-BUSINESS APPLICATIONS: Ariba BMC BroadVision Commerce One Webtrends MIDDLEWARE/CONNECTIVITY/APP SERVERS/WEB SERVERS: Bea Systems Iona Unisys OPERATING SYSTEMS/HARDWARE/SOFTWARE: COMPAQ HP 3000 HP 9000 HP-UX IBM AS/400 IBM OS/390 Lotus Notes Microsoft Sun Microsystems DATABASE: DB2 FileMaker Informix Oracle SQL SybaseCRM (CUSTOMER RELATIONSHIP MANAGEMENT): Clarify E.piphany HNC Onyx Pivotal Siebel Vantive Xchange SUPPLY CHAIN: Agile i2 Technologies Manugistics QAD Webplan COMMUNICATIONS: Nortel Cisco 3com Siemens Alcatel Telecom Vars ASP?s CLECS ISP?s E-COMMERCE: Dot Com Directory Consultant Directory Software Directory EXECUTIVE DIRECTORIES: Chief Executive Officer Chief Financial Officer Chief Information Officer Engineering Human Resources Purchasing Sales/Marketing INDUSTRY SPECIFIC LISTS: Agriculture, Forestry and Fishing, Communications, Construction, Finance, Insurance and Real Estate, Manufacturing, Mining, Public Administration, Retail Trade, Services, Transportation, Utilities, Wholesale Trade From mike.gordon at primus.ca Sun May 17 14:32:35 2009 From: mike.gordon at primus.ca (mike gordon) Date: Sun May 17 14:32:42 2009 Subject: Technology - Oracle, IBM, ERP - SAP, QAD, CRM - Siebel, Communication - Cisco, Manufacturing, Healthcare customer lists Message-ID: <200905171330.n4HDUmhX025505@matrix.start.ca> This email is to introduce our company Repharm and services we offer. Repharm is an international leader of sales and marketing database products for high technology businesses. We provide installed customer lists for companies such as Oracle, PeopleSoft, Siebel, etc. Our lists are continuously maintained to ensure the highest level of accuracy and completeness. We have hundreds of industry leaders as customers today - many whose names you would recognize. If you are interested, we could send you a sample of one of our lists complete with summary information, so that you could evaluate our content. To find out about the various lists we have available, in preparation for any sales or marketing campaigns that your organization may be considering in future, we'd love to hear from you. Or, perhaps you'd be interested in acquiring your competitors' customer lists? If you would like more information, please contact us at (905) 721-8456 or email us at repharm1@aol.com Below are just some of the lists available: ERP (ENTERPRISE RESOURCE PLANNING): Baan JD Edwards Lawson Made2Manage Mapics Marcam Oracle Peoplesoft SAP SSA E-BUSINESS APPLICATIONS: Ariba BMC BroadVision Commerce One Webtrends MIDDLEWARE/CONNECTIVITY/APP SERVERS/WEB SERVERS: Bea Systems Iona Unisys OPERATING SYSTEMS/HARDWARE/SOFTWARE: COMPAQ HP 3000 HP 9000 HP-UX IBM AS/400 IBM OS/390 Lotus Notes Microsoft Sun Microsystems DATABASE: DB2 FileMaker Informix Oracle SQL SybaseCRM (CUSTOMER RELATIONSHIP MANAGEMENT): Clarify E.piphany HNC Onyx Pivotal Siebel Vantive Xchange SUPPLY CHAIN: Agile i2 Technologies Manugistics QAD Webplan COMMUNICATIONS: Nortel Cisco 3com Siemens Alcatel Telecom Vars ASP?s CLECS ISP?s E-COMMERCE: Dot Com Directory Consultant Directory Software Directory EXECUTIVE DIRECTORIES: Chief Executive Officer Chief Financial Officer Chief Information Officer Engineering Human Resources Purchasing Sales/Marketing INDUSTRY SPECIFIC LISTS: Agriculture, Forestry and Fishing, Communications, Construction, Finance, Insurance and Real Estate, Manufacturing, Mining, Public Administration, Retail Trade, Services, Transportation, Utilities, Wholesale Trade From E-Cards at hallmark.com Sun May 17 23:50:17 2009 From: E-Cards at hallmark.com (hallmark.com) Date: Sun May 17 23:50:31 2009 Subject: You've received A Hallmark E-Card! Message-ID: <200905172127.n4HLRZKq014837@WIWI-IFK.uni-muenster.de> [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 E-Cards at hallmark.com Mon May 18 05:16:58 2009 From: E-Cards at hallmark.com (hallmark.com) Date: Mon May 18 05:17:04 2009 Subject: You've received A Hallmark E-Card! Message-ID: <200905180448.n4I4mAEg007941@WIWI-IFK.uni-muenster.de> [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 bugmaster at FreeBSD.org Mon May 18 11:06:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 18 11:06:36 2009 Subject: Current unassigned doc problem reports Message-ID: <200905181106.n4IB65Xx074736@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/134376 doc pthread(3): pthread manpages don't mention that PTHREA o docs/134226 doc /usr/share/examples/ftpd/ftpd.conf does not exist. o docs/134222 doc installation failure of japanese docs o docs/134127 doc [patch] ip6(4) manual does not contain proper referenc o docs/134123 doc The RUNQUEUE(9) man page is out of date p docs/134100 doc [patch] Incorrect control messages in ng_hole(4) manpa o docs/134093 doc [patch] uchcom.4 man page lists wrong first version o docs/134074 doc [patch] locking.9 man page slight enhancements 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/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/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 145 problems total. From brueffer at FreeBSD.org Mon May 18 11:23:46 2009 From: brueffer at FreeBSD.org (brueffer@FreeBSD.org) Date: Mon May 18 11:23:52 2009 Subject: docs/134093: [patch] uchcom.4 man page lists wrong first version Message-ID: <200905181123.n4IBNkxs006021@freefall.freebsd.org> Synopsis: [patch] uchcom.4 man page lists wrong first version State-Changed-From-To: open->closed State-Changed-By: brueffer State-Changed-When: Mon May 18 13:23:22 CEST 2009 State-Changed-Why: Fixed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=134093 From dfilter at FreeBSD.ORG Mon May 18 11:30:04 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Mon May 18 11:30:14 2009 Subject: docs/134093: commit references a PR Message-ID: <200905181130.n4IBU3C8006521@freefall.freebsd.org> The following reply was made to PR docs/134093; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/134093: commit references a PR Date: Mon, 18 May 2009 11:23:30 +0000 (UTC) Author: brueffer Date: Mon May 18 11:23:15 2009 New Revision: 192303 URL: http://svn.freebsd.org/changeset/base/192303 Log: Remove license clauses 3 and 4 as per rev. 1.2 from NetBSD. Also, FreeBSD 8.0 will be the first release including this driver. (1) PR: 134093 (1) Submitted by: gavin Modified: head/share/man/man4/uchcom.4 Modified: head/share/man/man4/uchcom.4 ============================================================================== --- head/share/man/man4/uchcom.4 Mon May 18 10:33:23 2009 (r192302) +++ head/share/man/man4/uchcom.4 Mon May 18 11:23:15 2009 (r192303) @@ -1,4 +1,4 @@ -.\" $NetBSD: uchcom.4,v 1.1 2007/09/03 18:02:17 tshiozak Exp $ +.\" $NetBSD: uchcom.4,v 1.2 2008/04/30 13:10:54 martin Exp $ .\" .\" Copyright (c) 2007 The NetBSD Foundation, Inc. .\" All rights reserved. @@ -14,13 +14,6 @@ .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. -.\" 3. All advertising materials mentioning features or use of this software -.\" must display the following acknowledgement: -.\" This product includes software developed by the NetBSD -.\" Foundation, Inc. and its contributors. -.\" 4. Neither the name of The NetBSD Foundation nor the names of its -.\" contributors may be used to endorse or promote products derived -.\" from this software without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED @@ -36,7 +29,7 @@ .\" .\" $FreeBSD$ .\" -.Dd May 15, 2009 +.Dd May 18, 2009 .Dt UCHCOM 4 .Os .Sh NAME @@ -88,7 +81,7 @@ driver first appeared in 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. _______________________________________________ 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 gelraen.ua at gmail.com Mon May 18 20:00:02 2009 From: gelraen.ua at gmail.com (Maxim Ignatenko) Date: Mon May 18 20:00:11 2009 Subject: docs/134660: rc-script for initializing ng_netflow+ng_ipfw Message-ID: <200905181957.n4IJvLfg037073@www.freebsd.org> >Number: 134660 >Category: docs >Synopsis: rc-script for initializing ng_netflow+ng_ipfw >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 May 18 20:00:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Maxim Ignatenko >Release: 8.0-CURRENT >Organization: Kiev National Taras Shevchenko University >Environment: >Description: This script provides configurable via rc.conf initializing of ng_netflow nodes and connects them to ng_ipfw node. Maybe the right place for this would be /usr/share/examples/netgraph >How-To-Repeat: >Fix: #!/bin/sh # PROVIDE: ng_netflow_ipfw # BEFORE: ipfw # REQUIRE: FILESYSTEMS # ng_netflow_ipfw_nodeN_enable (bool): used for temporary disabling one node # ng_netflow_ipfw_nodeN_cookie (int): specify cookie number for ng_ipfw (default=N) # ng_netflow_ipfw_nodeN_collector : "ipaddr:port" of corresponding collector # ng_netflow_ipfw_nodeN_atimeout (int) : active timeout for ng_netflow node # ng_netflow_ipfw_nodeN_itimeout (int) : inactive timeout for ng_netflow node # # For more information about specific parameters please refer to ng_ipfw(4) and # ng_netflow(4) man pages. # . /etc/rc.subr name="ng_netflow_ipfw" rcvar="ng_netflow_ipfw_enable" start_cmd="ng_netflow_ipfw_start" stop_cmd="ng_netflow_ipfw_stop" required_modules="netgraph ng_ipfw ng_netflow ng_ksocket" ng_netflow_ipfw_start() { local node ngctl ngctl="/usr/sbin/ngctl" node=0 local singlenode=0 if [ -n "$1" ]; then singlenode=1 node=$1 fi while true; do eval _enable=\$ng_netflow_ipfw_node${node}_enable if [ -z "${_enable}" ]; then # node not defined, finish break fi if ! checkyesno _enable; then # node defined, but disabled, skip continue fi eval _cookie=\${ng_netflow_ipfw_node${node}_cookie:-\"${node}\"} eval _collector=\${ng_netflow_ipfw_node${node}_collector:-\"127.0.0.1:9995\"} eval _atimeout=\${ng_netflow_ipfw_node${node}_atimeout:-\"1800\"} eval _itimeout=\${ng_netflow_ipfw_node${node}_itimeout:-\"15\"} echo "mkpeer ipfw: netflow ${_cookie} iface0 name ipfw:${_cookie} netflow${node} msg netflow${node}: setdlt { iface=0 dlt=12 } msg netflow${node}: settimeouts { inactive=${_itimeout} active=${_atimeout} } mkpeer netflow${node}: ksocket export inet/dgram/udp msg netflow${node}:export connect inet/${_collector}" | ${ngctl} -f - if [ "${singlenode}" = 1 ]; then break fi node=$(( ${node} + 1 )) done } ng_netflow_ipfw_stop() { local node ngctl ngctl="/usr/sbin/ngctl" node=0 local singlenode=0 if [ -n "$1" ]; then singlenode=1 node=$1 fi while true; do eval _enable=\$ng_netflow_ipfw_node${node}_enable if [ -z "${_enable}" ]; then # node not defined, finish break fi if ! checkyesno _enable; then # node defined, but disabled, skip continue fi echo "rmhook netflow${node}: export rmhook netflow${node}: iface0" | ${ngctl} -f - if [ "${singlenode}" = 1 ]; then break fi node=$(( ${node} + 1 )) done } load_rc_config $name run_rc_command $@ >Release-Note: >Audit-Trail: >Unformatted: From linimon at FreeBSD.org Tue May 19 23:15:59 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Tue May 19 23:16:05 2009 Subject: conf/134660: [patch] rc-script for initializing ng_netflow+ng_ipfw Message-ID: <200905192315.n4JNFwXH065402@freefall.freebsd.org> Old Synopsis: rc-script for initializing ng_netflow+ng_ipfw New Synopsis: [patch] rc-script for initializing ng_netflow+ng_ipfw Responsible-Changed-From-To: freebsd-doc->freebsd-rc Responsible-Changed-By: linimon Responsible-Changed-When: Tue May 19 23:14:49 UTC 2009 Responsible-Changed-Why: Perhaps the folks on the rc mailing list can evaluate this. http://www.freebsd.org/cgi/query-pr.cgi?pr=134660 From listposter at gmail.com Wed May 20 15:27:57 2009 From: listposter at gmail.com (List Poster) Date: Wed May 20 15:28:03 2009 Subject: Forgotten root password FAQ entry - should it mention fsck? Message-ID: <50f477370905200755q6384bb6fmd340c2008e84d288@mail.gmail.com> http://www.freebsd.org/doc/en/books/faq/admin.html#FORGOT-ROOT-PW Ran into a server with an unknown root password. Booted single-user and couldn't for the life of me get the partition to remount as rw. I was directed by someone on IRC to try fsck, and to my surprise the filesystem was in an inconsistent state. The surprise was because I had done a clean shutdown with CTRL-ALT-DEL. Anyway, I think it might be a good idea to include an fsck of / in the FAQ entry. From bcr at doc.bsdgroup.de Wed May 20 20:00:07 2009 From: bcr at doc.bsdgroup.de (Benedict Reuschling) Date: Wed May 20 20:00:19 2009 Subject: docs/134763: [Handbook] Varying filename example is not included in element Message-ID: <200905201957.n4KJv5k6078586@www.freebsd.org> >Number: 134763 >Category: docs >Synopsis: [Handbook] Varying filename example is not included in element >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 May 20 20:00:07 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Benedict Reuschling >Release: FreeBSD 7.2-STABLE >Organization: The FreeBSD German Documentation Project >Environment: FreeBSD atlantis.reuschling.org 7.2-STABLE FreeBSD 7.2-STABLE #19: Mon May 4 20:19:52 CEST 2009 root@atlantis.reuschling.org:/tank/obj/usr/src/sys/ATLANTIS i386 >Description: The multimedia-section in the FreeBSD handbook about MP3 Audio lists the following example: &prompt.root; mpg123 -a /dev/dsp1.0 Foobar-GreatestHits.mp3 ... Since "Foobar-GreatestHits.mp3" can be replaced by other filenames, it should be included in the preceding element. >How-To-Repeat: Look at the handbook section "7.3.1 MP3 Players" of doc/en_US.ISO8859-1/books/handbook/sound-mp3.html and guess what other .mp3 files you could use instead of Foobar-GreatestHits.mp3 :-) Therefore, it is a filename and should be typeset accordingly. >Fix: Apply the attached patch that moves the "Foobar-GreatestHits.mp3" within the element. Patch attached with submission follows: --- chapter1.131.sgml 2009-05-20 21:37:07.628706721 +0200 +++ chapter.sgml 2009-05-20 21:40:03.750229988 +0200 @@ -483,7 +483,7 @@ the sound device and the MP3 file on the command line, as shown below: - &prompt.root; mpg123 -a /dev/dsp1.0 Foobar-GreatestHits.mp3 + &prompt.root; mpg123 -a /dev/dsp1.0 Foobar-GreatestHits.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. Version 0.59r (1999/Jun/15). Written and copyrights by Michael Hipp. Uses code from various people. See 'README' for more! >Release-Note: >Audit-Trail: >Unformatted: From swell.k at gmail.com Thu May 21 20:20:04 2009 From: swell.k at gmail.com (Anonymous) Date: Thu May 21 20:20:11 2009 Subject: docs/131562: [patch] groff(1): don't corrupt man pages by replacing all `-' symbols with unicode 0x2212 Message-ID: <200905212020.n4LKK4BU013062@freefall.freebsd.org> The following reply was made to PR docs/131562; it has been noted by GNATS. From: Anonymous To: bug-followup@FreeBSD.org,amdmi3@FreeBSD.org Cc: Subject: Re: docs/131562: [patch] groff(1): don't corrupt man pages by replacing all `-' symbols with unicode 0x2212 Date: Fri, 22 May 2009 00:19:45 +0400 Looks like same workaround as in the patch was applied by r192561[1]. [1] http://docs.FreeBSD.org/cgi/mid.cgi?200905211756.n4LHu0Gf074528 From online_services at natwest.com Fri May 22 10:47:06 2009 From: online_services at natwest.com (Natwest Bank Plc) Date: Fri May 22 10:47:14 2009 Subject: Online Security Precaution Message-ID: <20090522102417.9F70B7A84A4@vanessa.fh-salzburg.ac.at> Dear Valued Client, Account Access Notification : It has come to the notice of the online banking security team of Natwest Bank, that there have been multiple logons to your Natwest online banking accounts from numerous IPs. We Have reason to believe that there has been unauthorised transactions in your account as of recent We therefore will need you to upgrade your online banking account Click here Sorry For the Inconvienence Regards, Natwest Bank Plc From no-reply at programmersheaven.com Sat May 23 17:03:58 2009 From: no-reply at programmersheaven.com (Programmers heaven) Date: Sat May 23 17:04:06 2009 Subject: 10th Anniversary - advertise two months for free. Message-ID: <20090523162957.8B4356665C@corp.axier.org> Dear friends and registered members, Programmers Heaven is celebrating its 10th anniversary. Our resources on the site have a steady growth and with the current increasing traffic, the site will pass 1 million unique visitors, on a monthly basis, before the end of 2009! Programmers Heaven is celebrating this by giving away two months of free advertising reaching out to approximately 2.3 million unique users (Google Analytics). For more information click [1]here to see our anniversary offer for advertisers. All the best, Lars Hagelin, Publisher Ps If you are interested to practice your editorial skills on a freelance basis, please drop us an email at editorial@programmersheaven.com, as we will be launching a section with industry news in a few months ds. This mail is sent to you as you have an account at Programmer's Heaven. Please let us know if you do not want to receive further information from Programmer's Heaven or its sponsors. References 1. http://www.programmersheaven.com/anniversary From rodrigo at bebik.net Sat May 23 18:20:02 2009 From: rodrigo at bebik.net (Rodrigo OSORIO) Date: Sat May 23 18:20:09 2009 Subject: docs/134877: new translation : "exprlaining BSD" in french Message-ID: <200905231810.n4NIAgq8046726@www.freebsd.org> >Number: 134877 >Category: docs >Synopsis: new translation : "exprlaining BSD" in french >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: Sat May 23 18:20:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Rodrigo OSORIO >Release: >Organization: >Environment: FreeBSD kurz 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: This is the french translation of the article wrote by Greg Lehey and named "Explaining BSD"[1] The original translation was done by me, and Maxime Derche works a lot with Thierry Thomas to fix my original version. Many thanks to them. [1]http://www.freebsd.org/doc/en_US.ISO8859-1/articles/explaining-bsd/index.html >How-To-Repeat: >Fix: Patch attached with submission follows: # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # explaining-bsd # explaining-bsd/Makefile # explaining-bsd/article.sgml # explaining-bsd/docbook.css # echo c - explaining-bsd mkdir -p explaining-bsd > /dev/null 2>&1 echo x - explaining-bsd/Makefile sed 's/^X//' >explaining-bsd/Makefile << '40ce58a6a99791440904dd160249dee8' X# X# The FreeBSD Documentation Project X# The FreeBSD French Documentation Project X# X# $FreeBSD: doc/fr_FR.ISO8859-1/articles/contributing/Makefile,v 1.1 2002/07/10 15:06:08 blackend Exp $ X# $Id: Makefile,v 1.1 2002/07/10 13:34:37 marc Exp $ X# Original revision: 1.1 X XDOC?= article X XFORMATS?= html X XINSTALL_COMPRESSED?=gz XINSTALL_ONLY_COMPRESSED?= X XJADEFLAGS+= -V %generate-article-toc% X XSRCS= article.sgml X XDOC_PREFIX?= ${.CURDIR}/../../.. X X.include "${DOC_PREFIX}/share/mk/doc.project.mk" 40ce58a6a99791440904dd160249dee8 echo x - explaining-bsd/article.sgml sed 's/^X//' >explaining-bsd/article.sgml << '71dd061185453166c2f4262a829831b7' X X %man; X %urls; X %abstract; X %artheader; X %translators; X %authors; X%trademarks; X]> X X

X X Expliquer BSD X X X Greg X Lehey X X X
grog@FreeBSD.org
X X X X X &tm-attrib.freebsd; X &tm-attrib.amd; X &tm-attrib.apple; X &tm-attrib.linux; X &tm-attrib.opengroup; X &tm-attrib.sun; X &tm-attrib.xfree86; X &tm-attrib.general; X X X X Dans le monde du logiciel libre Linux est quasiment synonyme de X Système d'Exploitation, mais il n'est pas le seul système d'exploitation de X type &unix; Open Source. Selon l'Internet X Operating System Counter, en avril 1999, 31.3% des ordinateurs connectés à internet utilisaient Linux X alors que 14.6% utilisaient un &unix; BSD. X Quelques unes des plus grandes sociétés du web, telles que Yahoo!, X utilisent un système d'exploitation BSD. En 1999, le serveur FTP le plus utilisé X ftp.cdrom.com (aujourd'hui disparu), utilisait BSD pour X transférer 1.4 TB de données par jour. Il ne s'agit clairement pas d'un marché de niche : X BSD est un secret bien gardé. X X Mais quel est ce secret ? Pourquoi BSD n'est il pas mieux connu ? Ce document traite de cette question et de bien d'autres. X X Dans ce texte, les différences entre BSD et Linux seront indiquées comme ceci. X X X X X Qu'est-ce que BSD ? X X BSD signifie Berkeley Software Distribution (ou Distribution logicielle de Berkeley). X C'est le nom donné aux distributions de code source provenant de l'Université de Californie, située X à Berkeley ; ces distributions était à l'origine, une extension du système d'exploitation &unix AT&T. X Plusieurs projets de systèmes d'exploitation Open Source sont basés sur une version de ce code connue sous X le nom de 4.4BSD-Lite. De plus, elle est composée de paquetages issus d'autres X projets Open Source, y compris ceux du projet GNU. Le système d'exploitation complet X comprend : X X X X Le noyau BSD, qui prends en charge l'ordonnancement des processus, la gestion de la mémoire, X le multi-processeur symétriques (SMP), les pilotes de périphériques, etc. X X À la différence du noyau Linux, il existe plusieurs noyaux BSD avec des possibilités différentes. X X X La bibliothèque C, c'est à dire l'interface de programmation de base du système X X La bibliothèque C BSD est basée sur du code provenant de Berkeley, et non X sur celui du projet GNU. X X X X Des utilitaires tels que le shell, des applications de gestion de fichiers, des compilateurs et des linkeurs . X X Certains utilitaires sont dérivés du projet GNU, d'autres pas. X X X X Le système X Window, qui prend en charge l'affichage graphique. X X Le système X Window utilisé dans la plupart des BSD est maintenu X par l'un des ces deux projets indépendants : X Le projet &xfree86; ou le X projet X.Org. X C'est le même code utilisé par Linux. Généralement, BSD ne définit pas X un bureau graphique spécifique tels que GNOME ou KDE, X bien que ces derniers soient disponibles. X X X X D'autres programmes et utilitaires. X X X X X X Quoi, un vrai système &unix; ? X X Les systèmes d'exploitation BSD ne sont pas des clones, mais des dérivés X Open Source du système d'exploitation &unix; issus des laboratoires de recherche de AT&T, X qui est lui-même un ancêtre de l'actuel &unix; System V. Ceci peut vous surprendre. Comment X cela a t-il pu se produire alors qu'AT&T n'a jamais fourni son code en Open Source ? X X Il est vrai que le système &unix; d'AT&T n'est pas Open Source, et X si l'on s'en tient strictement au point de vue de la propriété intellectuelle X alors BSD n'est pas un &unix; mais, X d'un autre coté, AT&T à intégré des sources provenant d'autres projets, X et plus particulièrement ceux du "Computer Sciences Research Group" de l'Université de X Californie, à Berkeley. À partir de 1976, le CSRG à commencé X à distribuer son logiciel sous le nom de Berkeley X Software Distribution ou BSD (sous forme de cassettes). X X Les premières versions se composaient essentiellement d'applications utilisateur, mais cela X changea radicalement lorsque le CSRG obtins un contrat avec le X "Defense Advanced Projects Research Agency" (DARPA) pour faire évoluer X les protocoles de communication sur leur réseau, ARPANET. Les nouveaux protocoles se firent connaître sous le nom de X Protocoles Internet, puis, X TCP/IP (nom repris des deux plus importants protocoles de l'ensemble). X La première implémentation ayant fait l'objet d'une large distribution fut celle de 4.2BSD, en 1982. X X Au cours des années 1980, un grand nombre de fabricants de stations de travail X ont surgi. La plupart préféraient acheter des licences &unix; plutôt que de développer X leur propre système d'exploitation. En particulier, Sun Microsystems X acheta une licence &unix; et implémenta une version de 4.2BSD, appelée X &sunos;. Lorsque AT&T fut autorisée à exploiter commercialemenT &unix;, X elle commença avec une implémentation squelettique appelée System III. X Le code de System V n'incluait pas de la gestion réseau, de sorte que toutes les implémentations incluaient des logiciels additionnels X issus de BSD, y compris les applications gérant TCP/IP, mais également des utilitaires tels que X l'interpréteur de commandes csh et l'éditeur vi. X Ces améliorations, étaient collectivement connues comme étant les X Extensions Berkeley. X X Les cassettes BSD contenaient du code source d'AT&T et, par conséquent, nécessitaient une licence source X &unix;. Vers 1990, les finances du CSRG s'épuisèrent et le groupe fut dissout. X Quelques membres décidèrent alors de fournir le code BSD, X qui était Open Source, sans le code propriétaire d'AT&T. X Ceci donna la Networking Tape 2, X aussi connue sous le nom Net/2. Net/2 n'était pas un X système d'exploitation complet : environs 20% du code du noyau manquait. L'un des membres du X CSRG, William F. Jolitz, écrivit le code manquant et le publia X au début de l'année 1992 sous le nom 386BSD. Au même moment, X un groupe d'anciens membres du CSRG, créa une entreprise nommée X Berkeley Software Design Inc. X qui publia une version bêta d'un système d'exploitation nommé X BSD/386, basé sur X le même code source. Le nom du système d'exploitation sera changé plus tard en X BSD/OS. X X 386BSD ne devint jamais un système d'exploitation stable. Mais deux autres projets X dérivés apparurent dès 1993 : X NetBSD et X FreeBSD. La divergence originelle entre ces X deux projets s'explique par le fait que certains furent plus patients que d'autres dans X l'attente d'améliorations de 386BSD : le groupe NetBSD commença dès le debut de l'année, X alors que la première version de FreeBSD ne fut pas disponible avant la fin de l'année. X Entre temps, les codes avaient suffisamment divergé qu'une fusion paraissait difficile. X De plus, les projets avaient des objectifs différents, comme nous le verrons par la suite. En 1996, X OpenBSD dériva de NetBSD et, en 2003, X DragonFlyBSD dériva de FreeBSD. X X X X Pourquoi BSD n'est il pas mieux connu ? X X Un certain nombre de raisons font que BSD reste relativement inconnu : X X X X Les développeurs BSD portent souvent plus d'intérêt à l'amélioration de leur code qu'à sa promotion. X X X X Une grande partie de la popularité de Linux est due à des facteurs exterieurs X au projet, tels que la presse, ou les sociétés créées pour vendre des services liés à Linux. X Jusqu'à récemment, les systèmes BSD Open Source n'avaient pas de tels partisans. X X X X Les développeurs BSD ont tendance à être plus expérimentés que les développeurs Linux X et ressentent moins le besoin de réaliser un système simple à utiliser. X Les nouveaux venus se sentent plus à l'aise avec Linux. X X X X En 1992, AT&T poursuivit en justice X BSDI, X la société qui commercialisait BSD/386, en prétendant que son produit incluait X du code source dont la propriété intellectuelle revenait à AT&T. X L'affaire se termina devant les tribunaux en X 1994, mais le spectre de ce litige à continué à hanter les esprits. X Pas plus tard qu'en mars 2000, un article publié sur le web prétendait X que ce litige juridique n'avait été que récemment réglé. X X Un des points que cette affaire à bien clarifié est la question du nom : dans les X années 1980, BSD était connu comme BSD &unix;. Avec la suppression X des derniers vestiges de son code AT&T, BSD X à également perdu le droit de s'appeler &unix;. Ainsi, vous pouvez voir des livres X dont le titre fait référence au système d'exploitation &unix; 4.3BSD X et au système d'exploitation 4.4BSD . X X X X X Il existe une idée selon laquelle les projets BSD seraient fragmentés et concurrents. Le X Wall Street X Journal à même parlé d'une balkanisation des projets X BSD. Tout comme les poursuites judiciaires, cette perception se base X sur de vieilles histoires. X X X X X X Comparer BSD et Linux X X Mais quelle est la vraie différence entre, disons, Debian Linux et X FreeBSD ? Pour l'utilisateur moyen, la différence est étonnamment faible : X Tous les deux sont des systèmes d'exploitation &unix;. Tous deux sont développés par X des projets non commerciaux ( ceci ne s'applique pas à de nombreuses autres distribution Linux ). X Dans la section qui suit, nous étudierons les systèmes BSD et les comparerons à Linux. X La description s'applique plus particulièrement à FreeBSD, qui représente environs 80% des X systèmes BSD installés, mais les différences avec NetBSD, OpenBSD et DragonFlyBSD sont minces. X X X X Qui est le propriétaire de BSD ? X X Aucune personne ou société n'est propriétaire de BSD. BSD est créé et distribué par une communauté X de contributeurs d'une grande expertise technique, situés partout dans la monde, sur la base du volontariat. X Quelques composants de BSD sont issus d'autres projets Open Source, gérés par d'autres personnes. X X X X Comment BSD est-il développé et mis à jour ? X X Le noyau BSD est développé et mis à jour suivant les modèle de développement de l'Open Source. X Chaque projet maintient un arbre des sources publique et accesible X au moyen de Concurrent Versions System X (CVS), un système de gestion de version, qui maintient l'ensemble des fichiers du projet, X y compris la documentation ainsi que d'autres fichiers. CVS X permet aux utilisateurs de faire un check out (extraire une copie) X de n'importe quelle version du système. X X Un grand nombre de développeurs à travers le monde contribuent à l'amélioration X de BSD. Ils sont divisés en trois catégories : X X X X Les contributeurs écrivent le code ou la documentation. X Ils ne sont pas autorisés à commiter (ajouter du code) directement dans l'arbre des sources. X Pour que leur code soit intégré au système, il X doit être examiné et contrôlé par un développeur enregistré, connu X en tant que committeur. X X X X Les committeurs sont des développeurs qui ont un droit X d'écriture dans l'arbre des sources. Pour devenir commiteur, une personne doit démontrer ses X compétences dans le domaine où elle travaille. X X X Il est à la discrétion du commiteur de déterminer si il doit X obtenir l'autorisation avant d'intégrer des changements dans l'arbre des sources. En X général, un commiteur expérimenté à la possibilité de faire des changements X qui sont manifestement corrects sans que le consensus soit nécessaire. Par exemple, un X commiteur du projet de documentation peut corriger des erreurs typographiques X ou grammaticales sans relecture. D'un autre côté, les développeurs X effectuant des changements complexes d'une grande portée sont supposés X soumettre leur code pour relecture avant de l'intégrer. Dans des cas extrêmes, X un membre de la core team avec le titre d'architecte X principal peut exiger que les changements soient retirés de l'arbre des sources, un X processus connu sous le nom de backing out. Tous les commiteurs X reçoivent des courriers électroniques décrivant chaque commit, il est donc X impossible de commiter de manière secrète. X X X X La Core team. Les projets FreeBSD et X NetBSD ont chacun une Core team qui gère le projet. Les X core teams ont été constituées dans le cadre des projets, et leur rôle X n'est pas toujours bien défini. Il n'est pas nécessaire d'être un développeur pour être membre X de la Core team, bien que cela semble normal. Les règles de la Core team X varient d'un projet à l'autre, mais X ils ont une parole plus forte dans la direction du projet que les autres X membres ne faisant pas partie de la Core team. X X X X Cette organisation diffère de celle de Linux sur de nombreux points : X X X X Aucune personne ne contrôle à elle seule le contenu du système. En X pratique, cette différence est surévaluée, puisque l'architecte en chef X peut exiger que du code soit retiré, de même que sur le projet Linux plusieurs X personnes sont autorisées à effectuer des changements. X X X X D'un autre côté, il y a un dépôt X central, un emplacement unique ou vous pouvez trouver l'ensemble des X sources du système, y compris toutes les anciennes versions. X X X X Les projets BSD maintiennent l'ensemble du Système X d'Exploitation, pas seulement le noyau. Cette distinction est X peu utile : ni BSD ni Linux ne sont utiles sans X applications. Les applications utilisées avec BSD sont bien souvent X les mêmes que celles utilisées avec Linux. X X X X En raison des formalités de maintenance d'un seul arbre X des sources sous CVS, le développement de BSD est clair, et il est possible X d'accéder à n'importe quelle version du système au travers de son numéro de X version (release), ou par date. X CVS permets également une mise à jour incrémentale du système : par exemple, X le dépôt des sources est mis à jour près de 100 fois par jour. La plupart de X ces changements sont mineurs. X X X X X X Les sortie de versions (releases) de BSD X X FreeBSD, NetBSD et OpenBSD fournissent le système en trois différentes X versions (releases). Tout comme Linux, chaque version se voit assigner un X numéro tel que 1.4.1 ou 3.5. De plus, le numéro de version possede un suffixe X indiquant son objectif : X X X X La version de développement du système est appelée X CURRENT. FreeBSD assigne un numéro à la version X CURRENT, par exemple FreeBSD 5.0-CURRENT. NetBSD emploie une X méthode de nommage légèrement différente et appose un suffixe d'une seule lettre X qui indique des changements dans l'interface interne, par exemple NetBSD X 1.4.3G. OpenBSD n'assigne pas de numéro ("OpenBSD-current"). X Tous les nouveaux développements du système vont dans cette branche. X X X X À intervalles réguliers, environs deux à quatre fois par an, le X projet sort une version RELEASE du système, X qui est disponible sur CD-ROM et gratuitement téléchargeable sur les X sites FTP, par exemple OpenBSD 2.6-RELEASE ou NetBSD 1.4-RELEASE. X La version RELEASE est destinée aux utilisateurs finaux et est la version X normale du système. NetBSD fournit également des patches de X release avec un troisième chiffre, par exemple NetBSD X 1.4.2. X X X X Si des bugs sont découverts dans une version RELEASE, ils sont corrigés, et X les correctifs sont incorporés à l'arbre des sources CVS. Sous FreeBSD, la version résultante est X appelée version STABLE, alors que NetBSD et OpenBSD X continuent à l'appeler version RELEASE. Des fonctions mineures X peuvent aussi être ajoutées à la branche après une période de X test dans la branche CURRENT. X X X X Par contraste, Linux maintient deux arborescences de code séparées : X la version stable et la version de développement. La version stable X est nommée avec un numéro de version mineur pair, tel que 2.0, 2.2 or 2.4. X La version de développement est quant à elle nommée avec un numéro de version mineur impair, tel que 2.1, X 2.3 ou 2.5. Dans chaque cas, ce numéro est suivi par un numéro X supplémentaire déterminant la version exacte. Chaque distributeur ajoute en outre ses propres X utilitaires et applications utilisateur, ce qui fait que le nom de la distribution X est tout aussi importante. Chaque fournisseur de distribution X assigne des numéros de version à sa distribution ; ainsi, une description complète X ressemble à quelque chose comme TurboLinux 6.0 avec le noyau X 2.2.14. X X X X Quelles sont les version de BSD disponibles ? X X En contraste avec le grand nombre de distributions Linux, il n'y a X que quatre BSD Open Source. Chaque projet BSD maintient sa propre arborescence X des sources et son propre noyau. En pratique, cependant, il y a X moins de divergences dans le code des applications utilisateur de ces différents X projets que dans Linux. X X Il est difficile de classer les objectifs de chaque projet : les différences X sont très subjectives. Fondamentalement, X X X X FreeBSD vise les hautes performances et la simplicité X d'utilisation pour l'utilisateur final ; il est l'un des système d'exploitation favoris X des fournisseurs de contenu sur le Web. Il fonctionne X sur de nombreuses plate-formes, incluant les systèmes basés sur les processeurs i386 X (PC), AMD 64-bit, &ultrasparc;, Compaq Alpha et la spécification NEC PC-98. X Le projet FreeBSD a beaucoup plus d'utilisateurs que les autres projets. X X X X NetBSD vise la portabilité maximale: son slogan est of course it runs NetBSD X (bien sur ça tourne sous NetBSD). X Il fonctionne aussi bien sur des ordinateurs de poche que sur des gros X serveurs, et à été utilisé par la NASA dans le cadre de missions spatiales. X C'est un trés bon choix pour fonctionner sur du vieux matériel non-Intel. X X X X OpenBSD vise la sécurité et la pureté du code : il emploie X une combinaison de concepts Open Source et une relecture rigoureuse X du code pour créer un système qui est manifestement bon, et qui, de fait, est X le choix privilégié des organismes conscients des aspects de sécurité, tels que les banques, les bourses X de valeurs et le ministère du gouvernement des États-Unis d'Amérique. Tout comme NetBSD, il fonctionne X sur de nombreuses plate-formes. X X X X DragonFlyBSD vise les hautes performances et l'évolutive partout, X depuis un système mono processeur jusqu'à un système massivement parallélisé. X DragonFlyBSD a plusieurs objectifs à long terme, mais est essentiellement axé X sur la fourniture d'un système pour les architectures symétriques (SMP) qui soient facile à comprendre X et à maintenir, et pour lequel il serait simple de développer des applications. X X X X Il existe deux autres systèmes d'exploitation &unix; BSD qui X ne sont pas Open Source : BSD/OS et &macos; X d'Apple: X X X X BSD/OS est le plus ancien des dérivés de 4.4 BSD. Il n'est pas X Open Source, bien que le code source soit disponible X à un coût relativement faible. Il ressemble à FreeBSD sur plusieurs aspects. X Deux ans après l'acquisition de BSDi par X Wind River Systems, BSD/OS échoua dans sa tentative d'exister X en tant que produit indépendant. Le support et le code sont encore X disponibles chez Wind River, mais tous les nouveaux développements X se concentrent sur le système d'exploitation embarqué VxWorks. X X X X &macos; X X est la dernière version du système d'exploitation pour les X ordinateurs de la lignée &macintosh; X d'Apple Computer Inc.. X Le cœur BSD de ce système d'exploitations, Darwin, X est disponible sous la forme d'un système d'exploitation totalement X fonctionnel pour les ordinateurs x86 et PPC. Le système graphique Aqua/Quartz et plusieurs X autres éléments propriétaires de &macos; X restent cependans à sources fermées. X Plusieurs développeurs de Darwin sont aussi des commiteurs de FreeBSD, et vice-versa. X X X X X X En quoi la licence BSD diffère-t-elle de la licence publique GNU ? X X Linux est disponible sous licence X GNU General Public X License (GPL), qui a été conçue pour éliminer les logiciels à X code source fermé. En particulier, tout travail dérivé d'un produit fourni sous licence X GPL doit également être fourni avec son code source si ce dernier est X demandé. A contrario, la licence BSD X est moins restrictive : la distribution des seuls binaires est autorisée. X Ceci est particulièrement attrayant pour des applications embarquées. X X X X X Que dois-je savoir d'autre ? X X Dans la mesure où moins d'applications sont disponibles pour BSD que pour Linux, X les développeurs BSD ont crée un paquet de compatibilité avec Linux, X qui permet aux programmes Linux de fonctionner sous BSD. Le paquet inclut à la fois X des modifications au niveau du noyau (afin que les appel systèmes Linux se fassent correctement) X et les fichiers de compatibilité Linux, tels que la bibliothèque C. Il n'y a pas de différence notable X dans la vitesse entre une application Linux exécutée sur une machine Linux X et une application Linux exécutée sur une machine BSD de puissance équivalente. X X De part sa nature tout provient d'un même fournisseur, BSD jouit X du fait que les mises à jour sont plus faciles à réaliser que dans bien des cas avec X Linux. BSD gère la mise à jour des versions des bibliothèques en fournissant X de modules de compatibilité pour des bibliothèques plus récentesr ; il est donc possible X d'exécuter des binaires qui ont plusieurs années sans aucun problème. X X X X X Lequel dois-je utiliser, BSD ou Linux ? X X Qu'est-ce que cela signifie en pratique ? Qui devrait utiliser BSD et qui devrait X utiliser Linux ? X X Il est très difficile de répondre à cette question. Voici quelques X lignes directrices : X X X X Si ce n'est pas cassé, ne le réparez pas : Si vous utilisez X déjà un système d'exploitation Open Source, et que vous en êtes content, X alors il n'y a probablement aucune bonne raison d'en changer. X X X X Les systèmes BSD, et plus particulièrement FreeBSD, peuvent avoir X de performances notablement supérieures à Linux. Mais pas sur tous les points. Dans la plupart des X cas, il y a peu ou pas de différences. Dans certains cas, Linux peut avoir de meilleures performances que FreeBSD. X X X X En général, les systèmes BSD sont réputés plus X fiables, en grande partie en raison d'un code de base plus X mature. X X X X Les projets BSD ont une meilleure réputation en raison de X l'exhaustivité de leur documentation. Les divers projets de documentation tentent de fournir une X documentation constamment mise à jour, en différentes langues, X et traitant de tous les aspects du système. X X X X La licence BSD peut être plus attractive que la GPL. X X X X BSD peut exécuter la plupart des binaires Linux, alors que Linux ne peut pas executer X les binaires BSD. Plusieurs implémentations de BSD peuvent exécuter les binaires X issus d'autres systèmes &unix; BSD peut donc représenter X un voie de migration plus simple depuis les autres systèmes X que Linux. X X X X X X Qui fournit du support, des services, et de la formation pour BSD ? X X BSDi / FreeBSD X Mall, Inc. fournit du support pour X FreeBSD depuis près de 10 ans. X X En plus, chacun des projets dispose d'une liste de consultants à embaucher: X FreeBSD, X NetBSD, X et OpenBSD. X X X
X X 71dd061185453166c2f4262a829831b7 echo x - explaining-bsd/docbook.css sed 's/^X//' >explaining-bsd/docbook.css << '2a87d1f48f40e6dcb3d1a78cf971a2c4' X/* X * Copyright (c) 2001, 2003 The FreeBSD Documentation Project X * All rights reserved. X * X * Redistribution and use in source and binary forms, with or without X * modification, are permitted provided that the following conditions X * are met: X * 1. Redistributions of source code must retain the above copyright X * notice, this list of conditions and the following disclaimer. X * 2. Redistributions in binary form must reproduce the above copyright X * notice, this list of conditions and the following disclaimer in the X * documentation and/or other materials provided with the distribution. X * X * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND X * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE X * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE X * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE X * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL X * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS X * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) X * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT X * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY X * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF X * SUCH DAMAGE. X * X * $FreeBSD: doc/share/misc/docbook.css,v 1.14 2008/11/21 07:28:34 keramida Exp $ X */ X XBODY ADDRESS { X line-height: 1.3; X margin: .6em 0; X} X XBODY BLOCKQUOTE { X margin-top: .75em; X line-height: 1.5; X margin-bottom: .75em; X} X XHTML BODY { X margin: 1em 8% 1em 10%; X line-height: 1.2; X} X X.LEGALNOTICE { X font-size: small; X font-variant: small-caps; X} X XBODY DIV { X margin: 0; X} X XDL { X margin: .8em 0; X line-height: 1.2; X} X XBODY FORM { X margin: .6em 0; X} X XH1, H2, H3, H4, H5, H6, XDIV.EXAMPLE P B, X.QUESTION, XDIV.TABLE P B, XDIV.PROCEDURE P B { X color: #990000; X} X XBODY H1, BODY H2, BODY H3, BODY H4, BODY H5, BODY H6 { X line-height: 1.3; X margin-left: 0; X} X XBODY H1, BODY H2 { X margin: .8em 0 0 -4%; X} X XBODY H3, BODY H4 { X margin: .8em 0 0 -3%; X} X XBODY H5 { X margin: .8em 0 0 -2%; X} X XBODY H6 { X margin: .8em 0 0 -1%; X} X XBODY HR { X margin: .6em; X border-width: 0 0 1px 0; X border-style: solid; X border-color: #cecece; X} X XBODY IMG.NAVHEADER { X margin: 0 0 0 -4%; X} X XOL { X margin: 0 0 0 5%; X line-height: 1.2; X} X XBODY PRE { X margin: .75em 0; X line-height: 1.0; X font-family: monospace; X} X XBODY TD, BODY TH { X line-height: 1.2; X} X XUL, BODY DIR, BODY MENU { X margin: 0 0 0 5%; X line-height: 1.2; X} X XHTML { X margin: 0; X padding: 0; X} X XBODY P B.APPLICATION { X color: #000000; X} X X.FILENAME { X color: #007a00; X} X X.GUIMENU, .GUIMENUITEM, .GUISUBMENU, X.GUILABEL, .INTERFACE, X.SHORTCUT, .SHORTCUT .KEYCAP { X font-weight: bold; X} X X.GUIBUTTON { X background-color: #CFCFCF; X padding: 2px; X} X X.ACCEL { X background-color: #F0F0F0; X text-decoration: underline; X} X X.SCREEN { X padding: 1ex; X} X X.PROGRAMLISTING { X padding: 1ex; X background-color: #eee; X border: 1px solid #ccc; X} X X@media screen { /* hide from IE3 */ X a[href]:hover { background: #ffa } X} X XBLOCKQUOTE.NOTE { X color: #222; X background: #eee; X border: 1px solid #ccc; X padding: 0.4em 0.4em; X width: 85%; X} X XBLOCKQUOTE.TIP { X color: #004F00; X background: #d8ecd6; X border: 1px solid green; X padding: 0.2em 2em; X width: 85%; X} X XBLOCKQUOTE.IMPORTANT { X font-style:italic; X border: 1px solid #a00; X border-left: 12px solid #c00; X padding: 0.1em 1em; X} X XBLOCKQUOTE.WARNING { X color: #9F1313; X background: #f8e8e8; X border: 1px solid #e59595; X padding: 0.2em 2em; X width: 85%; X} X X.EXAMPLE { X background: #fefde6; X border: 1px solid #f1bb16; X margin: 1em 0; X padding: 0.2em 2em; X width: 90%; X} 2a87d1f48f40e6dcb3d1a78cf971a2c4 exit >Release-Note: >Audit-Trail: >Unformatted: From blackend at FreeBSD.org Sat May 23 18:56:09 2009 From: blackend at FreeBSD.org (blackend@FreeBSD.org) Date: Sat May 23 18:56:16 2009 Subject: docs/134877: new translation : "exprlaining BSD" in french Message-ID: <200905231856.n4NIu8pY095338@freefall.freebsd.org> Synopsis: new translation : "exprlaining BSD" in french Responsible-Changed-From-To: freebsd-doc->blackend Responsible-Changed-By: blackend Responsible-Changed-When: Sat May 23 18:55:46 UTC 2009 Responsible-Changed-Why: Grab this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=134877 From joseph.koshy at gmail.com Sun May 24 13:31:21 2009 From: joseph.koshy at gmail.com (Joseph Koshy) Date: Sun May 24 13:31:28 2009 Subject: Hello dear FreeBSD In-Reply-To: <26a05f280902202143h52c1ffceoe34bb7e7e3c915a0@mail.gmail.com> References: <84dead720902190446o38a3d0ue75244df38167e36@mail.gmail.com> <26a05f280902202143h52c1ffceoe34bb7e7e3c915a0@mail.gmail.com> Message-ID: <84dead720905240559w38184a43w8849aa734e3d8b96@mail.gmail.com> 2009/2/21 ?????? ????????? : > Hello, Koshy! > We are not commercial project and now we have not official address. > But we have a telephone number: +77055016001. > > Country: Kazakhstan > City: Ust-Kamenogorsk > E-mail: support@linuxcenter.kz > WWW: http://linuxcenter.kz/page.php?page=fr > Off.site: http://linuxcenter.kz > > We hope it's a full informations for publisher on your site. > > Thank you! Good luck!!! > I've added an entry to the Handbook for "linuxcenter.kz". Sorry about the delayed response. Koshy > 2009/2/19 Joseph Koshy : >> Hi, >> >>> Hello Dear FreeBSD. We are the first online shop in Kazakhstan, the >>> extension opensource. We also distribute and FreeBSD. We would highly >>> appreciate if you post on the page >>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors.htm link >>> to us. >> >> Could you please send in a PR with the relevant information (phone >> numbers, addresses etc.)? >> >> Koshy >> > From admin at lissyara.su Mon May 25 09:30:06 2009 From: admin at lissyara.su (Alex Keda) Date: Mon May 25 09:30:20 2009 Subject: docs/134930: corrigendum in 'man gjournal' Message-ID: <200905250928.n4P9Srbo067695@www.freebsd.org> >Number: 134930 >Category: docs >Synopsis: corrigendum in 'man gjournal' >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 May 25 09:30:05 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Alex Keda >Release: 7.2 >Organization: USSR >Environment: FreeBSD router.local 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Wed May 13 22:39:57 MSD 2009 lissyara@router.local:/usr/obj/usr/src/sys/GENERIC i386 >Description: section 'EXAMPLES', second example: > tunefs -J enable -n disable da01sd.journal need tunefs -J enable -n disable da0s1d.journal >How-To-Repeat: man gjournal >Fix: >Release-Note: >Audit-Trail: >Unformatted: From maxim at FreeBSD.org Mon May 25 09:53:24 2009 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Mon May 25 09:53:30 2009 Subject: docs/134930: corrigendum in 'man gjournal' Message-ID: <200905250953.n4P9rMNF038274@freefall.freebsd.org> Synopsis: corrigendum in 'man gjournal' State-Changed-From-To: open->patched State-Changed-By: maxim State-Changed-When: Mon May 25 09:53:07 UTC 2009 State-Changed-Why: Fixed in HEAD. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=134930 From dfilter at FreeBSD.ORG Mon May 25 10:00:10 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Mon May 25 10:00:16 2009 Subject: docs/134930: commit references a PR Message-ID: <200905251000.n4PA09UR038439@freefall.freebsd.org> The following reply was made to PR docs/134930; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/134930: commit references a PR Date: Mon, 25 May 2009 09:53:08 +0000 (UTC) Author: maxim Date: Mon May 25 09:52:58 2009 New Revision: 192747 URL: http://svn.freebsd.org/changeset/base/192747 Log: o Fix typo in the example. PR: docs/134930 Submitted by: Alex Keda MFC after: 1 week Modified: head/sbin/geom/class/journal/gjournal.8 Modified: head/sbin/geom/class/journal/gjournal.8 ============================================================================== --- head/sbin/geom/class/journal/gjournal.8 Mon May 25 09:28:54 2009 (r192746) +++ head/sbin/geom/class/journal/gjournal.8 Mon May 25 09:52:58 2009 (r192747) @@ -220,7 +220,7 @@ allows this (i.e., if the last sector is .Bd -literal -offset indent umount /dev/da0s1d gjournal label da0s1d da0s1e && \e - tunefs -J enable -n disable da01sd.journal && \e + tunefs -J enable -n disable da0s1d.journal && \e mount -o async /dev/da0s1d.journal /mnt || \e mount /dev/da0s1d /mnt .Ed _______________________________________________ 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 maxim at FreeBSD.org Mon May 25 10:13:05 2009 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Mon May 25 10:13:11 2009 Subject: docs/133961: mistake in rc.conf(5) Message-ID: <200905251013.n4PAD4um052278@freefall.freebsd.org> Synopsis: mistake in rc.conf(5) State-Changed-From-To: patched->closed State-Changed-By: maxim State-Changed-When: Mon May 25 10:12:51 UTC 2009 State-Changed-Why: Merged to RELENG_7. http://www.freebsd.org/cgi/query-pr.cgi?pr=133961 From maxim at FreeBSD.org Mon May 25 10:13:28 2009 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Mon May 25 10:13:34 2009 Subject: docs/134100: [patch] Incorrect control messages in ng_hole(4) manpage Message-ID: <200905251013.n4PADREf052990@freefall.freebsd.org> Synopsis: [patch] Incorrect control messages in ng_hole(4) manpage State-Changed-From-To: patched->closed State-Changed-By: maxim State-Changed-When: Mon May 25 10:13:15 UTC 2009 State-Changed-Why: Merged to RELENG_7. http://www.freebsd.org/cgi/query-pr.cgi?pr=134100 From bugmaster at FreeBSD.org Mon May 25 11:06:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 25 11:06:36 2009 Subject: Current unassigned doc problem reports Message-ID: <200905251106.n4PB65mT091875@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/134930 doc corrigendum in 'man gjournal' o docs/134763 doc [handbook] [patch] Varying filename example is not inc o docs/134376 doc pthread(3): pthread manpages don't mention that PTHREA o docs/134226 doc /usr/share/examples/ftpd/ftpd.conf does not exist. o docs/134222 doc installation failure of japanese docs o docs/134127 doc [patch] ip6(4) manual does not contain proper referenc o docs/134123 doc The RUNQUEUE(9) man page is out of date o docs/134074 doc [patch] locking.9 man page slight enhancements o docs/133765 doc setfib(2) man page section o docs/133567 doc [patch] doc/Makefile switch to csup 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/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 144 problems total. From kuuse at redantigua.com Mon May 25 19:51:04 2009 From: kuuse at redantigua.com (Johan Kuuse) Date: Mon May 25 19:51:09 2009 Subject: docs/134877: new translation : "exprlaining BSD" in french In-Reply-To: <20090524120018.036441065674@hub.freebsd.org> References: <20090524120018.036441065674@hub.freebsd.org> Message-ID: <200905252150.57831.kuuse@redantigua.com> > Message: 3 > Date: Sat, 23 May 2009 18:56:08 GMT > From: blackend@FreeBSD.org > Subject: Re: docs/134877: new translation : "exprlaining BSD" in > french > To: blackend@FreeBSD.org, freebsd-doc@FreeBSD.org, > blackend@FreeBSD.org > Message-ID: <200905231856.n4NIu8pY095338@freefall.freebsd.org> > > Synopsis: new translation : "exprlaining BSD" in french > > Responsible-Changed-From-To: freebsd-doc->blackend > Responsible-Changed-By: blackend > Responsible-Changed-When: Sat May 23 18:55:46 UTC 2009 > Responsible-Changed-Why: > Grab this one. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=134877 > A detail about the original English article: At http://www.freebsd.org/doc/en_US.ISO8859-1/articles/explaining-bsd/comparing-bsd-and-linux.html section 4.2 How is BSD developed and updated? "Each project maintains a publicly accessible source tree under the Concurrent Versions System (CVS)..." Maybe it should be added that "work is in progress to change from CVS to SVN"? Just my 2 cents. Regards, Johan Kuuse From public at niessen.in Tue May 26 09:26:25 2009 From: public at niessen.in (Benedikt Niessen) Date: Tue May 26 09:26:32 2009 Subject: German tutorials on FreeBSD servers Message-ID: <4A1BB18B.8080100@niessen.in> Dear Sir or Madam, I dont know if this website would be interesting for your FreeBSD documentation resources section, but you can find quite a lot of very interesting tutorials about how to set up FreeBSD for different tasks, e.g. Webserver, Firewalling, Databaseservers, iTunes-Server, etc. Link: www.serverzeit.de I would be very happy if you would add this website to your resources list. Thanks a lot and best regards, Benedikt Niessen From info Thu May 28 14:28:55 2009 From: info (info) Date: Thu May 28 14:29:07 2009 Subject: Get your share and pay check fast (Self bank)100-500$ Message-ID: <20090528141039.5FDF8ABAA@heartbeat1.messagingengine.com> Skipped content of type multipart/related From dougb at FreeBSD.org Fri May 29 04:16:32 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Fri May 29 04:16:40 2009 Subject: Can we drop the section on old-style scripts in the Handbook? Message-ID: <4A1F619B.9020009@FreeBSD.org> I'd like to cut out the section on old-style scripts in the handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-starting-services.html and anyplace else that similar stuff occurs. Any objections? Doug From trhodes at FreeBSD.org Fri May 29 06:20:28 2009 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Fri May 29 06:20:34 2009 Subject: Can we drop the section on old-style scripts in the Handbook? In-Reply-To: <4A1F619B.9020009@FreeBSD.org> References: <4A1F619B.9020009@FreeBSD.org> Message-ID: <20090529022021.1cbeed64.trhodes@FreeBSD.org> On Thu, 28 May 2009 21:16:27 -0700 Doug Barton wrote: > I'd like to cut out the section on old-style scripts in the handbook > at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-starting-services.html > and anyplace else that similar stuff occurs. Any objections? > Fine here, thanks, -- Tom Rhodes From fbsd1 at a1poweruser.com Fri May 29 06:29:59 2009 From: fbsd1 at a1poweruser.com (Fbsd1) Date: Fri May 29 06:30:07 2009 Subject: Software creating karaoke from mp3 files Message-ID: <4A1F7CDB.2060407@a1poweruser.com> Been unable to purchase karaoke of rock and roll greats like "AC/DC, THE ROLLING STONES, THE DOORS, LED ZEPPELIN". Looking for advice on software that will allow me to edit out the singing voice tracks from a mp3 file and write the resulting music as a avi file so I can have the song words show on tv. If any one has done this type of thing, sure would like to hear about how they did it. Thanks From Midspan at phihongusa.com Fri May 29 21:41:18 2009 From: Midspan at phihongusa.com (Midspan Manager) Date: Fri May 29 21:41:25 2009 Subject: Myths about Power Over Ethernet Message-ID: <20090529214032.562F33AF2@glatton.xo.com> Myths about Power Over Ethernet May 28, 2009 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 claimagencydep at aim.com Sat May 30 07:59:08 2009 From: claimagencydep at aim.com (Postcode Announcement) Date: Sat May 30 07:59:15 2009 Subject: Postcode Announcement Message-ID: <200905292049.n4TKnxUf000968@mps500af.com> Postcode Announcement We are pleased to inform you of the final announcement of Postcode On-line Promo Programme You have won $1,000,000.00 Dollars From Postcode Casino int N.L Urgenly get to the below contact immediately for claim. **************************************************** Customer Full Name: Customer Contact Numbers: Tell:+31-641-232-991 Fax: +31-847-367-971 E:mail: postcodewing@aim.com E:mail: postcodewinng@aim.com **************************************************** Lucky Number: 8769-25473-55 Ref Number: ES/4420X2/68978 Sincerely Yours, Contact: Dr. Van Hans. Mrs. Agnes Greg Brook (Public Relation Officer) De Lotto (Official Website: www.postcodeloterij.nl) From dougb at FreeBSD.org Sat May 30 18:44:47 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sat May 30 18:44:59 2009 Subject: Can we drop the section on old-style scripts in the Handbook? In-Reply-To: <20090529022021.1cbeed64.trhodes@FreeBSD.org> References: <4A1F619B.9020009@FreeBSD.org> <20090529022021.1cbeed64.trhodes@FreeBSD.org> Message-ID: <4A217E99.1060706@FreeBSD.org> Tom Rhodes wrote: > On Thu, 28 May 2009 21:16:27 -0700 > Doug Barton wrote: > >> I'd like to cut out the section on old-style scripts in the handbook >> at >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-starting-services.html >> and anyplace else that similar stuff occurs. Any objections? >> > > Fine here, thanks, > Thanks to all who replied, public and private. It's done now. Doug -- This .signature sanitized for your protection