From eitan.adler at gmail.com  Mon Sep  1 02:46:12 2008
From: eitan.adler at gmail.com (Eitan Adler)
Date: Mon Sep  1 02:46:19 2008
Subject: update to arch-handbook
Message-ID: <cd994e160808311915h64c4a141w8b7d03e7f6f0b864@mail.gmail.com>

http://www.freebsd.org/doc/en/books/arch-handbook/boot-kernel.html

"

To where exactly is the execution passed by the loader, i.e. what is the
kernel's actual entry point. Let us take a look at the command that links
the kernel:

"

should read

" In order to see where the kernel is actually loaded you need to examine
the command that links the kernel "

or something to that extent.  The current text is barely proper English.


-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
From bugmaster at FreeBSD.org  Mon Sep  1 11:06:12 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep  1 11:06:44 2008
Subject: Current unassigned doc problem reports
Message-ID: <200809011106.m81B6CWQ067516@freefall.freebsd.org>

Current FreeBSD problem reports

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including\nexperimental development code and obsolete releases.\n
Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
     a repocopy operation within the CVS repository which
     is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/27605   doc        [patch] Cross-document references (<olink>)
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1

12 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc
o docs/24786   doc        missing FILES descriptions in sa(4)
o docs/26286   doc        *printf(3) etc should gain format string warnings
a docs/30008   doc        [patch] French softupdates document should be translat
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
o docs/38556   doc        EPS file of beastie, as addition to existing examples
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/43823   doc        [PATCH] update to environ(7) manpage
o docs/47818   doc        [patch] ln(1) manpage is confusing
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/50211   doc        [PATCH] doc.docbook.mk: fix textfile creation
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/53596   doc        Updates to mt(1) manual page
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
o docs/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84806   doc        mdoc(7) manpage has section ordering problems
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/104403  doc        man security should mention that the usage of the X Wi
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/105608  doc        fdc(4) debugging description staled
o docs/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
a docs/108980  doc        list of missing man pages
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
o docs/109201  doc        [request]: manual for callbootd
f docs/109226  doc        [request] No manual entry for sntp
o docs/109972  doc        No manual entry for zless/bzless
o docs/109973  doc        No manual entry for c++filt
o docs/109975  doc        No manual entry for elf2aout
o docs/109977  doc        No manual entry for ksu
o docs/109981  doc        No manual entry for post-grohtml
o docs/109983  doc        No manual entry for protoize
o docs/110061  doc        [PATCH] tuning(7) missing reference to vfs.read_max
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/111147  doc        hostapd.conf is not documented
o docs/111263  doc        [request] Information on $EDITOR variable in section 3
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/112481  doc        bug in ppp.linkup example
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/115921  doc        Booting from pst(4) is not supported
o docs/116116  doc        mktemp (3) re/move note
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
o docs/117747  doc        'break' system call needs a man page
o docs/117798  doc        formatting oddity in sysmouse(4)
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/118214  doc        close(2) error returns incomplete
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
s docs/119404  doc        [request] events page should list only last 2 years wo
a docs/119536  doc        a few typos in French handbook (basics)
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119907  doc        Ports compatibility
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120628  doc        PAE documentation errror in handbook
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
o docs/121197  doc        [patch] edits to books/porters-handbook
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/122052  doc        minor update on handbook section 20.7.1
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/123035  doc        [patch] bugs in refuse.README
o docs/123400  doc        gvinum startup in handbook
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/124716  doc        [patch] GEOM RAID1 handbook example only covers boot p
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des
o docs/126445  doc        discussion on WEP settings in wpa_supplicant.conf(5) m
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/126487  doc        fix language on atol(3) manpage
o docs/126590  doc        Write routine called forever in Sample Echo Pseudo-Dev
o docs/126921  doc        [patch] History section of cpuset(1) incorrect
o docs/126934  doc        missing 'crit' in usr.sbin/syslogd/syslog.conf.5

136 problems total.

From sai_anumukonda at adaptec.com  Mon Sep  1 11:31:10 2008
From: sai_anumukonda at adaptec.com (Anumukonda, Sai Praveen)
Date: Mon Sep  1 11:31:16 2008
Subject: (no subject)
Message-ID: <532ABFBDAAC3A34EB12EBA6CEC2838F401E2E26B4F@ADPE2K703.adaptec.com>

Hi,
            I am using FreeBSD6.3. I have downloaded the tarball for    jre1.6  (       diablo-latte-freebsd7-i386-1.6.0_07-b02.tar.bz2<http://www.freebsdfoundation.org/cgi-bin/download?download=diablo-latte-freebsd7-i386-1.6.0_07-b02.tar.bz2> ) from freebsdfoundations.org. After extracting the contents of the tarball,  I ran the command "ldd" on the java executable in the bin folder and this is what i get

java:
        libthr.so.3 => /lib/libthr.so.3 (0x2808a000)
        libc.so.7 => /lib/libc.so.7 (0x2809d000)

Looks like ldd is not able to find the required so files for java to run. But it is mentioned in the site that jre1.6 is for FREEBSD 6.x and FREEBSD7.

Can someone help me out here.
From remko at elvandar.org  Mon Sep  1 15:00:02 2008
From: remko at elvandar.org (Remko Lodder)
Date: Mon Sep  1 15:00:10 2008
Subject: (no subject)
In-Reply-To: <532ABFBDAAC3A34EB12EBA6CEC2838F401E2E26B4F@ADPE2K703.adaptec.com>
References: <532ABFBDAAC3A34EB12EBA6CEC2838F401E2E26B4F@ADPE2K703.adaptec.com>
Message-ID: <0a0c6f7f5bcfb2a965d57969db4fa025.squirrel@galain.elvandar.org>


On Mon, September 1, 2008 1:12 pm, Anumukonda, Sai Praveen wrote:
> Hi,
>             I am using FreeBSD6.3. I have downloaded the tarball for
> jre1.6  (
> diablo-latte-freebsd7-i386-1.6.0_07-b02.tar.bz2<http://www.freebsdfoundation.org/cgi-bin/download?download=diablo-latte-freebsd7-i386-1.6.0_07-b02.tar.bz2>
> ) from freebsdfoundations.org. After extracting the contents
> of the tarball,  I ran the command "ldd" on the java
> executable in the bin folder and this is what i get
>
> java:
>         libthr.so.3 => /lib/libthr.so.3 (0x2808a000)
>         libc.so.7 => /lib/libc.so.7 (0x2809d000)
>
> Looks like ldd is not able to find the required so files for java to run.
> But it is mentioned in the site that jre1.6 is for FREEBSD 6.x and
> FREEBSD7.
>
> Can someone help me out here.


Hello,

I am sorry but I do not unerstand the problem. There are two dynamically
linked libraries found in the java executable. What would be wrong with
this?

For example /bin/kill:

# ldd kill
kill:
        libc.so.7 => /lib/libc.so.7 (0x2807d000)

Same kind of information.

Please -specify- what could be wrong with this so that we can hopefully
help you.

Do note that the documentation team is not here to help you with src
and/or port problems there are other lists that are more effective in
helping you here (freebsd-java@ for example).

That said: thanks for using FreeBSD and taking the time to report this.
Hopefully we can help you resolve the problem so that you can use the
operating system with joy :)

cheers,
remko

-- 
/"\   Best regards,                      | remko@FreeBSD.org
\ /   Remko Lodder                       | remko@EFnet
 X    http://www.evilcoder.org/          |
/ \   ASCII Ribbon Campaign              | Against HTML Mail and News


From unixmania at gmail.com  Mon Sep  1 15:01:34 2008
From: unixmania at gmail.com (Carlos A. M. dos Santos)
Date: Mon Sep  1 15:01:41 2008
Subject: (no subject)
In-Reply-To: <532ABFBDAAC3A34EB12EBA6CEC2838F401E2E26B4F@ADPE2K703.adaptec.com>
References: <532ABFBDAAC3A34EB12EBA6CEC2838F401E2E26B4F@ADPE2K703.adaptec.com>
Message-ID: <e71790db0809010734q4bb8fb12n97f215dd244377f8@mail.gmail.com>

On Mon, Sep 1, 2008 at 8:12 AM, Anumukonda, Sai Praveen
<sai_anumukonda@adaptec.com> wrote:
> Hi,
>            I am using FreeBSD6.3. I have downloaded the tarball for    jre1.6  (       diablo-latte-freebsd7-i386-1.6.0_07-b02.tar.bz2<http://www.freebsdfoundation.org/cgi-bin/download?download=diablo-latte-freebsd7-i386-1.6.0_07-b02.tar.bz2> ) from freebsdfoundations.org. After extracting the contents of the tarball,  I ran the command "ldd" on the java executable in the bin folder and this is what i get
>
> java:
>        libthr.so.3 => /lib/libthr.so.3 (0x2808a000)
>        libc.so.7 => /lib/libc.so.7 (0x2809d000)
>
> Looks like ldd is not able to find the required so files for java to run. But it is mentioned in the site that jre1.6 is for FREEBSD 6.x and FREEBSD7.

You are attempting to use the FreeBSD 7.x binary on a 6.3 system. Try

     http://www.freebsdfoundation.org/cgi-bin/download?download=diablo-jre-freebsd6.i386.1.6.0.07.02.tbz

instead.

-- 
cd /usr/ports/sysutils/life
make clean
From eitan.adler+fbsd at gmail.com  Mon Sep  1 18:50:02 2008
From: eitan.adler+fbsd at gmail.com (Eitan Adler)
Date: Mon Sep  1 18:50:07 2008
Subject: docs/127027: update to fbsd handbook
Message-ID: <200809011841.m81IfMWQ058709@www.freebsd.org>


>Number:         127027
>Category:       docs
>Synopsis:       update to fbsd handbook
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 01 18:50:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Eitan Adler
>Release:        -
>Organization:
>Environment:
-
>Description:
http://www.freebsd.org/doc/en/books/arch-handbook/boot-kernel.html 
"To where exactly is the execution passed by the loader, i.e. what is the kernel's actual entry point. Let us take a look at the command that links the kernel:"
should read 
"In order to see where the kernel is actually loaded you need to examine the command that links the kernel"  or something to that extent.  The current text is barely proper English.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From manolis at FreeBSD.org  Mon Sep  1 20:05:22 2008
From: manolis at FreeBSD.org (manolis@FreeBSD.org)
Date: Mon Sep  1 20:06:35 2008
Subject: docs/127027: update to fbsd handbook
Message-ID: <200809012005.m81K5ILq020524@freefall.freebsd.org>

Synopsis: update to fbsd handbook

Responsible-Changed-From-To: freebsd-doc->manolis
Responsible-Changed-By: manolis
Responsible-Changed-When: Mon Sep 1 20:04:56 UTC 2008
Responsible-Changed-Why: 
Assign to me

http://www.freebsd.org/cgi/query-pr.cgi?pr=127027
From blackend at FreeBSD.org  Tue Sep  2 18:49:17 2008
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Tue Sep  2 18:49:24 2008
Subject: HEADS UP: doc/ slush for 7.1R and 6.4R begins on 8 September, 2008
Message-ID: <20080902184913.GA1031@gothic.blackend.org>

Hi all,

The doc slush will begin on 8 September, 2008.

The purpose of the doc slush is to slow down the rate of change in that
tree in order to allow the translation teams time to finalize their work
and to avoid last-minute breakage for the 7.1-RELEASE (and 6.4-RELEASE).

As usual, this is not a real freeze and requires no formal commit
approval procedure for your commit, but you are kindly requested not to
commit large, structural changes during that period.

Tagging of the doc tree is scheduled to take place on 15 September,
2008.  Thank you for your cooperation and keep up the good work!

-- 
Marc
for doceng@
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080902/fa7cbf51/attachment.pgp
From aWURRuTRhC at yahoo.com  Wed Sep  3 22:50:19 2008
From: aWURRuTRhC at yahoo.com (aWURRuTRhC@yahoo.com)
Date: Wed Sep  3 22:50:27 2008
Subject: =?iso-8859-1?q?Yahoo!=A9=5F=BC=AF=A5=CD=AC=A1+_-_=B5o=B2=7B=A6n?=
	=?iso-8859-1?q?=ABK=A9y=AA=BA=A4k=B8=CB=A7=E5=B5o=AD=F2!=A4p=A5i?=
	=?iso-8859-1?q?=B7R9=A4=B8!?=
Message-ID: <200809032228.m83MSvJe035645@w2.mtf.tw1.yahoo.com>

aWURRuTRhC@yahoo.com ±H¤F¤@«h³Ì·s¬¡°Êµ¹§A³á!!
------------------------------------------------------------
µ¹±zªº¯d¨¥¡G
 
¯uªº¥u­n9¤¸­C

§Ú­è­è¤]¤U¼ÐÅo

¦o­Ì®aªº°Ó«~ ¯uªº¦n«K©y­ò

¦P´Ú¦¡ªº «K©y¦n¦h­ò

http://tw.f4.page.bid.yahoo.com/tw/auction/d34340110?u=may26tw

§Ö¥h¬Ý¬Ý­ò
µo²{¦n«K©yªº¤k¸Ë§åµo­ò!¤p¥i·R9¤¸!
http://tw.lifestyle.yahoo.com/f15e14e5/080723/145/3v0n2.html
------------------------------------------------------------
Yahoo!©_¼¯¥Í¬¡+
http://lifestyle.yahoo.com.tw/
ª©Åv©Ò¦³ Yahoo!©_¼¯
From reservations at viningstravel.com  Thu Sep  4 23:53:57 2008
From: reservations at viningstravel.com (Missionary Airfare Search)
Date: Thu Sep  4 23:54:04 2008
Subject: Missionary Work Is A Wing-Span Away!
Message-ID: <1053994703-1463747838-1220571461@cherokeetravel.b.topica.com>

<br />
<br />
    <br />
    <u><b>2009 OUTREACH GROUP LEADERS</b></u><br />
<br />
If you don’t get your group space blocked out soon for 2009 you will pay much more!<br />
<br />
Most airlines have spent over <b>3 billion</b> dollars more on fuel during 2008 than the same time period in 2007. They have reduced their fleets.
This means planes fill up faster and fares go up.<br />
<br />
<br />
<u><b>UNPUBLISHED FARE CALCULATIONS</b></u><br />
<br />
You want to go from Nashville to Nairobi. We must price <u>each</u> leg of the trip with <u>each</u> airline we search to arrive at a total fare. For example,
on NW: Nashville – Detroit, Detroit – Amsterdam, and Amsterdam to Nairobi. The same is true on the return. The airlines sell a certain number of
seats on each flight at their very lowest fare. Then they raise the fare – and keep raising it as more purchase - until the plane is full. If the
lowest booking class of service is not available on any of those legs your total fare will be higher.<br />
<br />
The answer is to plan way ahead. Settle on your dates now. We will work with you on this to provide you with the flexibility you need. You must
block out the space – not merely call around for quotes that will change from day to day.<br />
<br />
If you have any questions or comments, please write me, personally: <a href="mailto:Blake@ViningsTravel.com?subject=">Blake@ViningsTravel.com</a>. Also, have you reviewed our website:
<a href="http://cherokeetravel.c.topica.com/maamcHeabKbUoccAj6Seaehtrz/">www.MissionaryAirfareSearch.com</a>?  We were the very first missionary travel agency to have a booking
engine in the United States.  Please read our “Welcome” article on the Home Page to learn of our long history in service to Christ’s ambassadors and about me, personally,
on the “about us” link.  Our fundamental value is an acknowledgement that the funds belong to The Lord. We are passionate about helping you be a
good steward. If you find a lower price – please let us know.<br />
<br />
<br />
<b><u>TRAVEL TIPS FROM OUR MISSIONARIES</u></b><br />
<br />
“I’m going to start rechecking my seat assignments several weeks before departure. Lately the airline reassigned the type of aircraft they were
going to use on my flight and my aisle seats became window seats by the bathroom”…..Randy L.  <i><b><u>EDITOR’S NOTE</u></b></i>:  This is an excellent comment. All
airlines are cutting capacity and re-configuring flight schedules and you may depend on this happening more often. The airline should notify you
of any changes – but don’t count on it.<br />
<br />
“I found a terrific website for guidance on vaccinations and health precautions on the Traveler’s Health page of the Centers for Disease Control
(CDC)”. <a href="http://cherokeetravel.c.topica.com/maamcHeabKbYdccAj6Seaehtrz/">www.cdcgov/travel</a>....Betty B.<br />
<br />
“My husband thinks I’m crazy but I always feed my jewelry chains through straws and tape them at both ends. Then I store it in a zip lock bag.
Do you think this is worth sharing?” ….Sylvia D. <u><i><b>EDITOR’S NOTE</b></i></u>: Yes, Sylvia, it’s a very reasonable tip for anyone who has tried to untangle
these things! We don’t share all the tips we receive. Unlike yours, some are really crazy!<br />
<br />
“Hate wrinkles? I use a Downy product called Wrinkle Releaser. Hang up your garment, spray it, and in five minutes the wrinkles are gone.”….Brenda McN.<br />
<br />
“I put Christmas type bells on my carry-on so that if someone tries to move it I’ll hear it even if I’m not watching.”….Loraine F.<br />
<br />
“I’m 79 now and in all my years of travel for the Lord no one has ever thought of mugging me! It’s because prayer accomplishes things and the
fact I walk around with a tiny but loud whistle in my mouth to discourage anybody”….Laura R.<br /><br />
<br />
<br />
In Christ,<br />
<br />
<br />
Blake Stiles Lawson, President<br />
<a href="mailto:reservations@missionaryairfaresearch.com?subject=">reservations@missionaryairfaresearch.com</a><br />
877.634.1199<br />
770.436.1334<br />
770.928.2659 Fax<br />


====================================================================
Unsubscribe:
   http://topica.com/f/unsub.html/aaaqa2ch7juymxy90qiu8sefdlmz13wv6favw1588j3pxv
Update Your Profile:
   http://topica.com/f/?b1dtE7.ccAj6S.ZnJlZWJz
Confirm Your Subscription:
   http://topica.com/f/?b1dtE7.ccAj6S.ZnJlZWJz.c
Report Unsolicited Email:
   http://topica.com/f/abuse.html?aaaqa2ch7juymxy90qiu8sefdlmz13wv6favw1588j3pxv
Forward to Friend:
   http://www.topica.com/f2f/?f=aaaqa2ch7juymxy90qiu8sefdlmz13wv6favw1588j3pxv&r=freebsd-doc%40freebsd.org
Delivered by Topica:
   http://www.topica.com/?p=T3FOOTER
From jeffrey at goldmark.org  Sun Sep  7 03:00:11 2008
From: jeffrey at goldmark.org (Jeffrey Goldberg)
Date: Sun Sep  7 03:00:17 2008
Subject: docs/127167: add AUTO_UPGRADE to mergemaster(8) man page
Message-ID: <20080907024101.C34732E002A@n118.ewd.goldmark.org>


>Number:         127167
>Category:       docs
>Synopsis:       add AUTO_UPGRADE to mergemaster(8) man page
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 07 03:00:10 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Jeffrey Goldberg
>Release:        FreeBSD 7.1-PRERELEASE i386
>Organization:
>Environment:
System: FreeBSD dobby.ewd.goldmark.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #20: Thu Sep 4 17:09:34 CDT 2008 root@dobby.ewd.goldmark.org:/usr/obj/usr/src/sys/DOBBY i386

>Description:
	man page for mergemaster(8) does not mention the AUTO_UPGRADE directive
	that can appear in mergemaster.rc.  The attached patch to the
	mergemaster.8 fixes that.
>How-To-Repeat:
	man mergemaster
>Fix:
	See patch (diff -u) below.


--- mergemaster.8.orig	2008-09-06 21:27:46.000000000 -0500
+++ mergemaster.8	2008-09-06 21:32:00.000000000 -0500
@@ -24,7 +24,7 @@
 .\"
 .\" $FreeBSD: src/usr.sbin/mergemaster/mergemaster.8,v 1.36 2006/04/30 22:09:47 gordon Exp $
 .\"
-.Dd February 4, 2006
+.Dd September 6, 2008
 .Dt MERGEMASTER 8
 .Os
 .Sh NAME
@@ -312,6 +312,9 @@
 # Automatically install files that do not exist on the system already
 #AUTO_INSTALL=
 #
+# Attempt to auto upgrade files that have not been user modified.
+#AUTO_UPGRADE=
+#
 # Compare /etc/rc.conf[.local] to /etc/defaults/rc.conf
 #COMP_CONFS=yes
 #


>Release-Note:
>Audit-Trail:
>Unformatted:
From linimon at FreeBSD.org  Sun Sep  7 03:08:05 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Sun Sep  7 03:08:12 2008
Subject: docs/127167: [patch] add AUTO_UPGRADE to mergemaster(8) man page
Message-ID: <200809070308.m87385bH022155@freefall.freebsd.org>

Old Synopsis: add AUTO_UPGRADE to mergemaster(8) man page
New Synopsis: [patch] add AUTO_UPGRADE to mergemaster(8) man page

Responsible-Changed-From-To: freebsd-doc->dougb
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Sep 7 03:07:51 UTC 2008
Responsible-Changed-Why: 
Over to maintainer.

http://www.freebsd.org/cgi/query-pr.cgi?pr=127167
From bugmaster at FreeBSD.org  Mon Sep  8 02:30:56 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep  8 02:31:25 2008
Subject: Current unassigned doc problem reports
Message-ID: <200809080230.m882Ut9A010016@freefall.freebsd.org>

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/126934  doc        missing 'crit' in usr.sbin/syslogd/syslog.conf.5
o docs/126921  doc        [patch] History section of cpuset(1) incorrect
o docs/126590  doc        Write routine called forever in Sample Echo Pseudo-Dev
o docs/126487  doc        fix language on atol(3) manpage
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/126445  doc        discussion on WEP settings in wpa_supplicant.conf(5) m
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
o docs/124716  doc        [patch] GEOM RAID1 handbook example only covers boot p
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/123400  doc        gvinum startup in handbook
o docs/123035  doc        [patch] bugs in refuse.README
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o 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 docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121197  doc        [patch] edits to books/porters-handbook
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/120628  doc        PAE documentation errror in handbook
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/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/119907  doc        Ports compatibility
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
a docs/119536  doc        a few typos in French handbook (basics)
s docs/119404  doc        [request] events page should list only last 2 years wo
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
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/117798  doc        formatting oddity in sysmouse(4)
o docs/117747  doc        'break' system call needs a man page
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
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/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/115921  doc        Booting from pst(4) is not supported
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/112481  doc        bug in ppp.linkup example
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/111263  doc        [request] Information on $EDITOR variable in section 3
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/109983  doc        No manual entry for protoize
o docs/109981  doc        No manual entry for post-grohtml
o docs/109977  doc        No manual entry for ksu
o docs/109975  doc        No manual entry for elf2aout
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
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
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/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
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/104403  doc        man security should mention that the usage of the X Wi
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
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/84806   doc        mdoc(7) manpage has section ordering problems
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/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
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/47818   doc        [patch] ln(1) manpage is confusing
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
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
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 (<olink>)
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 <emphasis> tags in the sourc

148 problems total.


Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
     a repocopy operation within the CVS repository which
     is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

From rkramer at mweb.com  Mon Sep  8 07:27:12 2008
From: rkramer at mweb.com (Rudi Kramer - MWEB)
Date: Mon Sep  8 07:27:20 2008
Subject: Incorrect info on
	http://www.freebsd.org/doc/en/books/handbook/x11-wm.html
Message-ID: <39DC135F7F0571489196E0B6F5D58B4A03B460C2@MWBEXCH.mweb.com>

Hello,

I was busy checking the information on
http://www.freebsd.org/doc/en/books/handbook/x11-wm.html and section
5.7.3.1 needs to be updated. 

Current:

5.7.3.1 The KDE Display Manager

ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure


Proposed:

5.7.3.1 The KDE Display Manager


Source: http://freebsd.kde.org/details/kde41.php

Thanks
Rudi 
From sonic2000gr at gmail.com  Mon Sep  8 08:02:35 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Mon Sep  8 08:03:06 2008
Subject: Incorrect info on
	http://www.freebsd.org/doc/en/books/handbook/x11-wm.html
In-Reply-To: <39DC135F7F0571489196E0B6F5D58B4A03B460C2@MWBEXCH.mweb.com>
References: <39DC135F7F0571489196E0B6F5D58B4A03B460C2@MWBEXCH.mweb.com>
Message-ID: <48C4DC2E.2050001@gmail.com>

Rudi Kramer - MWEB wrote:
> Hello,
>
> I was busy checking the information on
> http://www.freebsd.org/doc/en/books/handbook/x11-wm.html and section
> 5.7.3.1 needs to be updated. 
>
> Current:
>
> 5.7.3.1 The KDE Display Manager
>
> ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure
>
>
> Proposed:
>
> 5.7.3.1 The KDE Display Manager
>
>
> Source: http://freebsd.kde.org/details/kde41.php
>
> Thanks
> Rudi 
>   

Actually, the info on the handbook is valid for kde3.X, which is still 
used by most people.
You are right though, a section should be added for KDE4
From schools at edufinder.co.za  Mon Sep  8 10:55:34 2008
From: schools at edufinder.co.za (Info)
Date: Mon Sep  8 10:55:41 2008
Subject: Educators available for teaching
Message-ID: <180f01c9119c$6e55d8e0$4b018aa0$@co.za>

 

Dear School

 

Edufinder is currently sitting with a database of over 700 teachers looking
for placements.

 

With Edufinder networking on campuses final year students from North West
University, UNISA and the Univirsity of Tshwane have also started
registering.  Over 300 students from North West University are expected to
make use of Edufinder's services over the next 2 months.

 

Register on www.edufinder.co.za for a consultant to provide you with more
information.

 

 

 

Best Regards

The Edufinder Team

+27 (11) 692 3675

 

 

From miwi at FreeBSD.org  Mon Sep  8 11:28:43 2008
From: miwi at FreeBSD.org (Martin Wilke)
Date: Mon Sep  8 11:28:53 2008
Subject: Incorrect info on
	http://www.freebsd.org/doc/en/books/handbook/x11-wm.html
In-Reply-To: <39DC135F7F0571489196E0B6F5D58B4A03B460C2@MWBEXCH.mweb.com>
References: <39DC135F7F0571489196E0B6F5D58B4A03B460C2@MWBEXCH.mweb.com>
Message-ID: <20080908111313.GF63175@bsdcrew.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Sep 08, 2008 at 09:12:04AM +0200, Rudi Kramer - MWEB wrote:
> Hello,
> 

Hi

> I was busy checking the information on
> http://www.freebsd.org/doc/en/books/handbook/x11-wm.html and section
> 5.7.3.1 needs to be updated. 
> 
> Current:
> 
> 5.7.3.1 The KDE Display Manager
> 
> ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure
> 
> 
> Proposed:
> 
> 5.7.3.1 The KDE Display Manager
> 
> 
> Source: http://freebsd.kde.org/details/kde41.php

I added the kde4 part, should be avalible in few hours.
Thanks for you infos.

- - Martin

> 
> Thanks
> Rudi 
> _______________________________________________
> 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"
> 

- -- 

+-----------------------+-------------------------------+
|  PGP    : 0x05682353  |  Jabber : miwi(at)BSDCrew.de  |
|  ICQ    : 169139903   |  Mail   : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
|	Mess with the Best, Die like the Rest!		|
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjFCMkACgkQFwpycAVoI1OMxQCgnt2c6rY4JFqrIP4jt+bXHQN4
n9YAoIANBPxV5zmip6vZ+6Th/uIIU/EU
=RnkT
-----END PGP SIGNATURE-----
From blackend at FreeBSD.org  Mon Sep  8 13:09:31 2008
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Mon Sep  8 13:09:38 2008
Subject: HEADS UP: doc/ slush begins
Message-ID: <20080908130927.GA1172@gothic.blackend.org>

Hi all,

As announced, the doc/ tree is now in a slush.  Please postpone all
non-essential changes until after the doc/ tree is tagged (currently
scheduled for 15 September, 2008).

While this is not a real freeze, if you need to commit a relatively
large change to fix or improve our documentation for 7.1-RELEASE (or
6.4-RELEASE), please put a note for translators onto your commit log.

-- 
Marc
for doceng@
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080908/0b1c2436/attachment.pgp
From bruce at cran.org.uk  Mon Sep  8 19:40:02 2008
From: bruce at cran.org.uk (Bruce Cran)
Date: Mon Sep  8 19:40:08 2008
Subject: docs/127219: [patch] style(9) is inconsistent regarding usage of
	sysexits(3)
Message-ID: <200809081931.m88JVjMs066666@www.freebsd.org>


>Number:         127219
>Category:       docs
>Synopsis:       [patch] style(9) is inconsistent regarding usage of sysexits(3)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 08 19:40:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Bruce Cran
>Release:        7.0-RELEASE-p3
>Organization:
>Environment:
FreeBSD tau.draftnet 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #1: Mon Aug  4 00:11:11 BST 2008     brucec@tau.draftnet:/usr/obj/usr/src/sys/MYKERNEL  amd64
>Description:
style(9) is inconsistent regarding the usage of sysexits(3): at one point it says

Exits should be 0 on success, or according to the predefined values in sysexits(3).

But in a later example:

 Use err(3) or warn(3), do not roll your own.

             if ((four = malloc(sizeof(struct foo))) == NULL)
                     err(1, (char *)NULL);
             if ((six = (int *)overflow()) == NULL)
                     errx(1, "number overflowed");
             return (eight);
     }

err and errx exit with a code of 1, which is incorrect according to the previous statement.  Better exit codes might be EX_OSERR and EX_DATAERR.

Also, the cast of NULL to char * isn't required.
>How-To-Repeat:
man 9 style
>Fix:


Patch attached with submission follows:

--- /usr/src/share/man/man9/style.9	2007-01-28 20:51:04.000000000 +0000
+++ style.9	2008-09-08 20:20:31.000000000 +0100
@@ -716,9 +716,9 @@
 do not roll your own.
 .Bd -literal
 	if ((four = malloc(sizeof(struct foo))) == NULL)
-		err(1, (char *)NULL);
+		err(EX_OSERR, NULL);
 	if ((six = (int *)overflow()) == NULL)
-		errx(1, "number overflowed");
+		errx(EX_DATAERR, "number overflowed");
 	return (eight);
 }
 .Ed


>Release-Note:
>Audit-Trail:
>Unformatted:
From bruce at cran.org.uk  Mon Sep  8 20:00:12 2008
From: bruce at cran.org.uk (Bruce Cran)
Date: Mon Sep  8 20:00:19 2008
Subject: docs/127220: [patch] err(3) suggests using exit values from
	sysexits(3) but examples don't
Message-ID: <200809081958.m88JwgPK080011@www.freebsd.org>


>Number:         127220
>Category:       docs
>Synopsis:       [patch] err(3) suggests using exit values from sysexits(3) but examples don't
>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 Sep 08 20:00:11 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Bruce Cran
>Release:        7.0-RELEASE-p3
>Organization:
>Environment:
FreeBSD tau.draftnet 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #1: Mon Aug  4 00:11:11 BST 2008     brucec@tau.draftnet:/usr/obj/usr/src/sys/MYKERNEL  amd64
>Description:
err(3) suggests that exit codes from sysexits(3) be used for the eval parameter, but fails to use them in the examples.
>How-To-Repeat:
man 3 err
>Fix:


Patch attached with submission follows:

--- /usr/src/lib/libc/gen/err.3	2007-01-09 00:27:53.000000000 +0000
+++ err.3	2008-09-08 20:54:20.000000000 +0100
@@ -178,15 +178,15 @@
 Display the current errno information string and exit:
 .Bd -literal -offset indent
 if ((p = malloc(size)) == NULL)
-	err(1, NULL);
+	err(EX_OSERR, NULL);
 if ((fd = open(file_name, O_RDONLY, 0)) == -1)
-	err(1, "%s", file_name);
+	err(EX_NOINPUT, "%s", file_name);
 .Ed
 .Pp
 Display an error message and exit:
 .Bd -literal -offset indent
 if (tm.tm_hour < START_TIME)
-	errx(1, "too early, wait until %s", start_time_string);
+	errx(EX_DATAERR, "too early, wait until %s", start_time_string);
 .Ed
 .Pp
 Warn of an error:
@@ -195,7 +195,7 @@
 	warnx("%s: %s: trying the block device",
 	    raw_device, strerror(errno));
 if ((fd = open(block_device, O_RDONLY, 0)) == -1)
-	err(1, "%s", block_device);
+	err(EX_OSFILE, "%s", block_device);
 .Ed
 .Pp
 Warn of an error without using the global variable


>Release-Note:
>Audit-Trail:
>Unformatted:
From geoffrey at reptiles.org  Mon Sep  8 21:49:08 2008
From: geoffrey at reptiles.org (Geoffrey)
Date: Mon Sep  8 21:49:14 2008
Subject: sane configuration in Freebsd 7
Message-ID: <20080908172940.K64474@gecko.reptiles.org>


Hi

Regarding
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html,

sane-find-scanner won't find a scanner if uscanner is in the kernel (as
it is by default) in Freebsd 7 (uname -a
FreeBSD burp.bogstomp.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #4: Mon
Sep  8 16:11:35 EDT 2008
root@burp.bogstomp.org:/usr/obj/usr/src/sys/BURP  i386)

 	I've also noted the "sane-find-scanner" man page erroneously
states this device is necessary.  I suspect there are other sane
manpages that may do likewise.

 	Cheers.

-- 
first step to autoholic recovery: realising the 3000 lb gorilla on your back
 			  does not become you.
 		http://www.autoholics.org/programme.php
From blackend at FreeBSD.org  Tue Sep  9 06:04:48 2008
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Tue Sep  9 06:04:54 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080908172940.K64474@gecko.reptiles.org>
References: <20080908172940.K64474@gecko.reptiles.org>
Message-ID: <20080909055234.GA98761@abigail.blackend.org>

On Mon, Sep 08, 2008 at 05:36:18PM -0400, Geoffrey wrote:
> 
> Hi
> 
> Regarding
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html,
> 
> sane-find-scanner won't find a scanner if uscanner is in the kernel (as

Hello,

I'm not sure to understand you.  What do you mean by "sane-find-scanner
won't find a scanner if uscanner is in the kernel" ?

> it is by default) in Freebsd 7 (uname -a
> FreeBSD burp.bogstomp.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #4: Mon
> Sep  8 16:11:35 EDT 2008
> root@burp.bogstomp.org:/usr/obj/usr/src/sys/BURP  i386)
> 
> 	I've also noted the "sane-find-scanner" man page erroneously
> states this device is necessary.  I suspect there are other sane
> manpages that may do likewise.

This manual page as others from the SANE project are written for Linux,
so the content related to devices, etc, can be confusing.

> http://lists.freebsd.org/mailman/listinfo/freebsd-doc
> To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"

-- 
Marc
From geoffrey at reptiles.org  Tue Sep  9 10:59:07 2008
From: geoffrey at reptiles.org (Geoffrey)
Date: Tue Sep  9 10:59:14 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909055234.GA98761@abigail.blackend.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
Message-ID: <20080909064619.Y64474@gecko.reptiles.org>

On Tue, 9 Sep 2008, Marc Fonvieille wrote:

Hi Marc

> On Mon, Sep 08, 2008 at 05:36:18PM -0400, Geoffrey wrote:
>>
>> Hi
>>
>> Regarding
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html,
>>
>> sane-find-scanner won't find a scanner if uscanner is in the kernel (as
>
> Hello,
>
> I'm not sure to understand you.  What do you mean by "sane-find-scanner
> won't find a scanner if uscanner is in the kernel" ?
>
 	Sorry.  I need to be more specific.  "sane-find-scanner" will
not find a usb scanner if:

BURP:#device            uscanner        # Scanners

 	is not remarked out in your kernel config file OR if you load
the kld uscanner.  Sane uses usblib and usblib can't find the scanner
if uscanner is loaded.
 	Yes, you have to build and install a new kernel to do this as
uscanner is in the generic kernel:
 	GENERIC:device          uscanner        # Scanners


>> it is by default) in Freebsd 7 (uname -a
>> FreeBSD burp.bogstomp.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #4: Mon
>> Sep  8 16:11:35 EDT 2008
>> root@burp.bogstomp.org:/usr/obj/usr/src/sys/BURP  i386)
>>
>> 	I've also noted the "sane-find-scanner" man page erroneously
>> states this device is necessary.  I suspect there are other sane
>> manpages that may do likewise.
>
> This manual page as others from the SANE project are written for Linux,
> so the content related to devices, etc, can be confusing.
>
 	Ah.  This is true.  However uscanner is a local modification.
As far as I can determine linux used a different kernel device for
scanners (though I may be wrong).  Regardless, with the uscanner
references omitted the man page is correct in stating the scanner kernel
device interferes with usblib discovery of the scanner.  Usblib uses
ugen.  Uscanner just gets in the way.

>> http://lists.freebsd.org/mailman/listinfo/freebsd-doc
>> To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"
>
 	Cheers.

-- 
first step to autoholic recovery: realising the 3000 lb gorilla on your back
 			  does not become you.
 		http://www.autoholics.org/programme.php
From koitsu at FreeBSD.org  Tue Sep  9 11:32:26 2008
From: koitsu at FreeBSD.org (Jeremy Chadwick)
Date: Tue Sep  9 11:32:33 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909064619.Y64474@gecko.reptiles.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
Message-ID: <20080909111624.GA94373@icarus.home.lan>

On Tue, Sep 09, 2008 at 06:59:04AM -0400, Geoffrey wrote:
> On Tue, 9 Sep 2008, Marc Fonvieille wrote:
>> I'm not sure to understand you.  What do you mean by "sane-find-scanner
>> won't find a scanner if uscanner is in the kernel" ?
>>
> 	Sorry.  I need to be more specific.  "sane-find-scanner" will
> not find a usb scanner if:
>
> BURP:#device            uscanner        # Scanners
>
> 	is not remarked out in your kernel config file OR if you load
> the kld uscanner.
>
> Sane uses usblib and usblib can't find the scanner
> if uscanner is loaded.
> 	Yes, you have to build and install a new kernel to do this as
> uscanner is in the generic kernel:
> 	GENERIC:device          uscanner        # Scanners
>
> ...
>
> 	Ah.  This is true.  However uscanner is a local modification.
> As far as I can determine linux used a different kernel device for
> scanners (though I may be wrong).  Regardless, with the uscanner
> references omitted the man page is correct in stating the scanner kernel
> device interferes with usblib discovery of the scanner.  Usblib uses
> ugen.  Uscanner just gets in the way.

I think what Geoffrey is trying to say is the following:

When the uscanner driver (either built into the kernel, or loaded as
kernel module) is used, it causes sane-find-scanner (usblib) to
fail detection of a scanner.  Meaning, uscanner is getting in the
way of the detection.

This is a problem because "device uscanner" is enabled by default
in the GENERIC kernel, which means sane-find-scanner will fail unless
you rebuild your kernel with uscanner disabled/removed.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |

From geoffrey at reptiles.org  Tue Sep  9 13:21:46 2008
From: geoffrey at reptiles.org (Geoffrey)
Date: Tue Sep  9 13:21:53 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909111624.GA94373@icarus.home.lan>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
	<20080909111624.GA94373@icarus.home.lan>
Message-ID: <20080909091346.F64474@gecko.reptiles.org>

On Tue, 9 Sep 2008, Jeremy Chadwick wrote:

> On Tue, Sep 09, 2008 at 06:59:04AM -0400, Geoffrey wrote:
>> On Tue, 9 Sep 2008, Marc Fonvieille wrote:
>>> I'm not sure to understand you.  What do you mean by "sane-find-scanner
>>> won't find a scanner if uscanner is in the kernel" ?
>>>
>> 	Sorry.  I need to be more specific.  "sane-find-scanner" will
>> not find a usb scanner if:
>>
>> BURP:#device            uscanner        # Scanners
>>
>> 	is not remarked out in your kernel config file OR if you load
>> the kld uscanner.
>>
>> Sane uses usblib and usblib can't find the scanner
>> if uscanner is loaded.
>> 	Yes, you have to build and install a new kernel to do this as
>> uscanner is in the generic kernel:
>> 	GENERIC:device          uscanner        # Scanners
>>
>> ...
>>
>> 	Ah.  This is true.  However uscanner is a local modification.
>> As far as I can determine linux used a different kernel device for
>> scanners (though I may be wrong).  Regardless, with the uscanner
>> references omitted the man page is correct in stating the scanner kernel
>> device interferes with usblib discovery of the scanner.  Usblib uses
>> ugen.  Uscanner just gets in the way.
>
> I think what Geoffrey is trying to say is the following:
>
> When the uscanner driver (either built into the kernel, or loaded as
> kernel module) is used, it causes sane-find-scanner (usblib) to
> fail detection of a scanner.  Meaning, uscanner is getting in the
> way of the detection.
>
> This is a problem because "device uscanner" is enabled by default
> in the GENERIC kernel, which means sane-find-scanner will fail unless
> you rebuild your kernel with uscanner disabled/removed.
>
>
 	YES!  Absolutely.

 	Which is quite different from what the sane-find-scanner man
page and the relevant handbook page say.  I believe there may be other
misplaced uscanner references in the man pages but did not find them.
 	In fairness sane did use uscanner at one time and it may be
possible to still use uscanner with sane but the man pages do not cover
this and the handbook does not successfully explain how.

 	Cheers!
-- 
first step to autoholic recovery: realising the 3000 lb gorilla on your back
 			  does not become you.
 		http://www.autoholics.org/programme.php
From wblock at wonkity.com  Tue Sep  9 14:03:49 2008
From: wblock at wonkity.com (Warren Block)
Date: Tue Sep  9 14:03:56 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909064619.Y64474@gecko.reptiles.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
Message-ID: <alpine.BSF.2.00.0809090733480.2388@wonkity.com>

On Tue, 9 Sep 2008, Geoffrey wrote:
> 	Sorry.  I need to be more specific.  "sane-find-scanner" will
> not find a usb scanner if:
>
> BURP:#device            uscanner        # Scanners
>
> 	is not remarked out in your kernel config file OR if you load
> the kld uscanner.  Sane uses usblib and usblib can't find the scanner
> if uscanner is loaded.
> 	Yes, you have to build and install a new kernel to do this as
> uscanner is in the generic kernel:
> 	GENERIC:device          uscanner        # Scanners

It finds mine if given it the uscanner device:

% sane-find-scanner /dev/uscanner0

     # sane-find-scanner will now attempt to detect your scanner. If the
     # result is different from what you expected, first make sure your
     # scanner is powered up and properly connected to your computer.

     # No SCSI scanners found. If you expected something different, make sure that
     # you have loaded a kernel SCSI driver for your SCSI adapter.

   found USB scanner (vendor=0x04b8, product=0x010a) at /dev/uscanner0
     # Your USB scanner was detected. It may or may not be supported by
     # SANE. Try scanimage -L and read the backend's manpage.

Instead of modifying the generic kernel, just change the Handbook note 
on using sane-find-scanner to include /dev/uscanner0 when checking for 
USB scanners.

-Warren Block * Rapid City, South Dakota USA
From geoffrey at reptiles.org  Tue Sep  9 14:48:49 2008
From: geoffrey at reptiles.org (Geoffrey)
Date: Tue Sep  9 14:48:55 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <alpine.BSF.2.00.0809090733480.2388@wonkity.com>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
	<alpine.BSF.2.00.0809090733480.2388@wonkity.com>
Message-ID: <20080909103426.N64474@gecko.reptiles.org>

On Tue, 9 Sep 2008, Warren Block wrote:

> On Tue, 9 Sep 2008, Geoffrey wrote:
>> 	Sorry.  I need to be more specific.  "sane-find-scanner" will
>> not find a usb scanner if:
>> 
>> BURP:#device            uscanner        # Scanners
>>
>> 	is not remarked out in your kernel config file OR if you load
>> the kld uscanner.  Sane uses usblib and usblib can't find the scanner
>> if uscanner is loaded.
>> 	Yes, you have to build and install a new kernel to do this as
>> uscanner is in the generic kernel:
>> 	GENERIC:device          uscanner        # Scanners
>
> It finds mine if given it the uscanner device:
>
> % sane-find-scanner /dev/uscanner0
>
>    # sane-find-scanner will now attempt to detect your scanner. If the
>    # result is different from what you expected, first make sure your
>    # scanner is powered up and properly connected to your computer.
>
>    # No SCSI scanners found. If you expected something different, make sure 
> that
>    # you have loaded a kernel SCSI driver for your SCSI adapter.
>
>  found USB scanner (vendor=0x04b8, product=0x010a) at /dev/uscanner0
>    # Your USB scanner was detected. It may or may not be supported by
>    # SANE. Try scanimage -L and read the backend's manpage.
>
> Instead of modifying the generic kernel, just change the Handbook note on 
> using sane-find-scanner to include /dev/uscanner0 when checking for USB 
> scanners.
>
> -Warren Block * Rapid City, South Dakota USA
>
 	/dev/uscanner0 was not being created in my installation.  This
was the source of my grief.  That said the kernel somewhat saw it:

Sep  8 13:25:41 burp kernel: device_attach: uscanner0 attach
returned 6
Sep  8 13:26:27 burp kernel: ugen0: at uhub0 port 3 (addr 3)
disconnected
Sep  8 13:26:27 burp kernel: ugen0: detached
Sep  8 13:26:33 burp kernel: uscanner0: at uhub0 port 2 (addr 2)
disconnected
Sep  8 13:26:38 burp root: Unknown USB device: vendor 0x05d8 product
0x4002 bus uhub0
Sep  8 13:26:38 burp kernel: uscanner0: <vendor 0x05d8 product 0x4002,
class 255/255, rev 1.10/1.00, addr 2> on uhub0
Sep  8 13:26:38 burp kernel: uscanner0: bulk-in and/or bulk-out endpoint
not found

 	From the documentation there appear to be conflicts in vendor
and device ids and if you check these against usbdevs, usbdevs will see
this device and vendor as something quite different from what they are.
That said the kernel is not using usbdevs at this point.  The man page
sane-usb explains the workaround for this.

 	What Freebsd are you using Warren?

 	Cheers.


-- 
first step to autoholic recovery: realising the 3000 lb gorilla on your back
 			  does not become you.
 		http://www.autoholics.org/programme.php
From blackend at FreeBSD.org  Tue Sep  9 16:26:09 2008
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Tue Sep  9 16:26:15 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909064619.Y64474@gecko.reptiles.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
Message-ID: <20080909162604.GA1032@gothic.blackend.org>

On Tue, Sep 09, 2008 at 06:59:04AM -0400, Geoffrey wrote:
> On Tue, 9 Sep 2008, Marc Fonvieille wrote:
> 
> Hi Marc
> 
> > On Mon, Sep 08, 2008 at 05:36:18PM -0400, Geoffrey wrote:
> >>
> >> Hi
> >>
> >> Regarding
> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html,
> >>
> >> sane-find-scanner won't find a scanner if uscanner is in the kernel (as
> >
> > Hello,
> >
> > I'm not sure to understand you.  What do you mean by "sane-find-scanner
> > won't find a scanner if uscanner is in the kernel" ?
> >
>  	Sorry.  I need to be more specific.  "sane-find-scanner" will
> not find a usb scanner if:
> 
> BURP:#device            uscanner        # Scanners
> 
>  	is not remarked out in your kernel config file OR if you load
> the kld uscanner.  Sane uses usblib and usblib can't find the scanner
> if uscanner is loaded.
>  	Yes, you have to build and install a new kernel to do this as
> uscanner is in the generic kernel:
>  	GENERIC:device          uscanner        # Scanners
>
[...]

% sane-find-scanner -q
found USB scanner (vendor=0x04a9, product=0x220e) at /dev/uscanner0

% kldstat -v | grep scanner
267 uhub/uscanner

I can reproduce the same behavior on another machine (both of them run a
kernel with uscanner support in).

You should check your configuration and maybe see if your scanner does
not need you to load a firmware.

-- 
Marc
From frtzkatz at yahoo.com  Tue Sep  9 16:30:03 2008
From: frtzkatz at yahoo.com (Fritz Katz)
Date: Tue Sep  9 16:30:09 2008
Subject: docs/127253: Error in Handbook:
	http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
Message-ID: <200809091627.m89GRJYG070708@www.freebsd.org>


>Number:         127253
>Category:       docs
>Synopsis:       Error in Handbook: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
>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 Sep 09 16:30:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Fritz Katz
>Release:        7.0-RELEASE i386
>Organization:
AAArt
>Environment:
# uname -rm
7.0-RELEASE i386

>Description:
   This page in the handbook appears to give bad advice:
      http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
    
        # ddd -k /var/crash/kernel.0 /var/crash/vmcore.0
        
   Is the handbook out-of-date? Has the '-k' option been removed from 'ddd'?

   I think the correct invocation for 'ddd' should be:
   
        # ddd --debugger kgdb kernel.debug /var/crash/vmcore.0
    
    Following instructions in the handbook results in this message: 
    "GDB could not be started.", and the ddd console window prints:
    
        GNU DDD 3.3.11 (i386-portbld-freebsd7.0), 
          by Dorothea Lutkehaus and Andreas Zeller. 
        ...
        gdb: unrecognized option '-k'
        Use 'gdb --help' for a complete list of options.

    Which appears to be correct since,
        # ddd --help
    and
        # gdb --help
    shows there is no option '-k' 
    _________________
    
    also, the second option, '/var/crash/kernel.0', also appears to
    be incorrect. That file or executable does not exist. 
    
    Is that the executable? If so, my 'kernel' is located in:
    
       # cd /usr/obj/usr/src/sys/AAART/
       # ls kernel*
         kernel  kernel.debug   kernel.symbols
    
    _________________

    Attempting:
        # ddd --core=/var/crash/vmcore.0
    gives this message:
        "/var/crash/vmcore.0" is not a core dump: File format not recognized
        (gdb)
        
  However, the instructions for the command line debugger, 'kgdb', on this
  page are OK:
  
    http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
  
  and the /var/crash/vmcore.0 is recognized.
 
  # cd /usr/obj/usr/src/sys/AAART/
  # kgdb kernel.debug /var/crash/vmcore.0 
>How-To-Repeat:

Read the handbook and attempt to follow it's instructions.
>Fix:
Replace the offending line in the Handbook with:

  # ddd --debugger kgdb kernel.debug /var/crash/vmcore.0



>Release-Note:
>Audit-Trail:
>Unformatted:
From geoffrey at reptiles.org  Tue Sep  9 16:35:09 2008
From: geoffrey at reptiles.org (Geoffrey)
Date: Tue Sep  9 16:35:16 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909162604.GA1032@gothic.blackend.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
	<20080909162604.GA1032@gothic.blackend.org>
Message-ID: <20080909122947.X64474@gecko.reptiles.org>

On Tue, 9 Sep 2008, Marc Fonvieille wrote:

> On Tue, Sep 09, 2008 at 06:59:04AM -0400, Geoffrey wrote:
>> On Tue, 9 Sep 2008, Marc Fonvieille wrote:
>>
>> Hi Marc
>>
>>> On Mon, Sep 08, 2008 at 05:36:18PM -0400, Geoffrey wrote:
>>>>
>>>> Hi
>>>>
>>>> Regarding
>>>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html,
>>>>
>>>> sane-find-scanner won't find a scanner if uscanner is in the kernel (as
>>>
>>> Hello,
>>>
>>> I'm not sure to understand you.  What do you mean by "sane-find-scanner
>>> won't find a scanner if uscanner is in the kernel" ?
>>>
>>  	Sorry.  I need to be more specific.  "sane-find-scanner" will
>> not find a usb scanner if:
>>
>> BURP:#device            uscanner        # Scanners
>>
>>  	is not remarked out in your kernel config file OR if you load
>> the kld uscanner.  Sane uses usblib and usblib can't find the scanner
>> if uscanner is loaded.
>>  	Yes, you have to build and install a new kernel to do this as
>> uscanner is in the generic kernel:
>>  	GENERIC:device          uscanner        # Scanners
>>
> [...]
>
> % sane-find-scanner -q
> found USB scanner (vendor=0x04a9, product=0x220e) at /dev/uscanner0
>
> % kldstat -v | grep scanner
> 267 uhub/uscanner
>
> I can reproduce the same behavior on another machine (both of them run a
> kernel with uscanner support in).
>
> You should check your configuration and maybe see if your scanner does
> not need you to load a firmware.
>
 	Please attach your `uname -a`.  As I've noted I'm running
FreeBSD burp.bogstomp.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #4: Mon
Sep  8 16:11:35 EDT 2008
root@burp.bogstomp.org:/usr/obj/usr/src/sys/BURP  i386

 	/dev/uscanner0 is not being created on my installation.  From
the manpages (excepting those that were modified) sane appears to not
want uscanner as it is presently configured to use usblib which uses
ugen*.  Ugen* can't see the scanner with uscanner in the kernel or
loaded as a module on my installation.

 	cheers.

-- 
first step to autoholic recovery: realising the 3000 lb gorilla on your back
 			  does not become you.
 		http://www.autoholics.org/programme.php
From blackend at freebsd.org  Tue Sep  9 16:40:09 2008
From: blackend at freebsd.org (Marc Fonvieille)
Date: Tue Sep  9 16:40:15 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909103426.N64474@gecko.reptiles.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
	<alpine.BSF.2.00.0809090733480.2388@wonkity.com>
	<20080909103426.N64474@gecko.reptiles.org>
Message-ID: <20080909164006.GB1032@gothic.blackend.org>

On Tue, Sep 09, 2008 at 10:48:47AM -0400, Geoffrey wrote:
>  	/dev/uscanner0 was not being created in my installation.  This
> was the source of my grief.  That said the kernel somewhat saw it:
> 
> Sep  8 13:25:41 burp kernel: device_attach: uscanner0 attach
> returned 6
> Sep  8 13:26:27 burp kernel: ugen0: at uhub0 port 3 (addr 3)
> disconnected
> Sep  8 13:26:27 burp kernel: ugen0: detached
> Sep  8 13:26:33 burp kernel: uscanner0: at uhub0 port 2 (addr 2)
> disconnected
> Sep  8 13:26:38 burp root: Unknown USB device: vendor 0x05d8 product
> 0x4002 bus uhub0
> Sep  8 13:26:38 burp kernel: uscanner0: <vendor 0x05d8 product 0x4002,
> class 255/255, rev 1.10/1.00, addr 2> on uhub0
> Sep  8 13:26:38 burp kernel: uscanner0: bulk-in and/or bulk-out endpoint
> not found
> 
>  	From the documentation there appear to be conflicts in vendor
> and device ids and if you check these against usbdevs, usbdevs will see
> this device and vendor as something quite different from what they are.
> That said the kernel is not using usbdevs at this point.  The man page
> sane-usb explains the workaround for this.
>

What kind of scanner are you using?  Is your scanner listed in
uscanner(4) manual page?

>From a quick glance, your scanner is just not supported (maybe cause of
lack of USB IDs definition in /src/sys/dev/usb/usbdevs) by uscanner(4).
I can be wrong.  You should talk with people from freebsd-usb mailing
list since I doubt it's a doc related issue.

-- 
Marc
From wblock at wonkity.com  Tue Sep  9 16:48:16 2008
From: wblock at wonkity.com (Warren Block)
Date: Tue Sep  9 16:48:22 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909103426.N64474@gecko.reptiles.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
	<alpine.BSF.2.00.0809090733480.2388@wonkity.com>
	<20080909103426.N64474@gecko.reptiles.org>
Message-ID: <alpine.BSF.2.00.0809091003150.2898@wonkity.com>

On Tue, 9 Sep 2008, Geoffrey wrote:
> On Tue, 9 Sep 2008, Warren Block wrote:
>
>> Instead of modifying the generic kernel, just change the Handbook note on 
>> using sane-find-scanner to include /dev/uscanner0 when checking for USB 
>> scanners.
>>
> 	/dev/uscanner0 was not being created in my installation.  This
> was the source of my grief.  That said the kernel somewhat saw it:
>
> Sep  8 13:25:41 burp kernel: device_attach: uscanner0 attach returned 6
> Sep  8 13:26:27 burp kernel: ugen0: at uhub0 port 3 (addr 3) disconnected
> Sep  8 13:26:27 burp kernel: ugen0: detached
> Sep  8 13:26:33 burp kernel: uscanner0: at uhub0 port 2 (addr 2) disconnected

Ignoring those as they appear to be from when the scanner was detached.

> Sep  8 13:26:38 burp root: Unknown USB device: vendor 0x05d8 product 0x4002 bus uhub0

>From devd?

> Sep  8 13:26:38 burp kernel: uscanner0: <vendor 0x05d8 product 0x4002, class 255/255, rev 1.10/1.00, addr 2> on uhub0

Okay.

> Sep  8 13:26:38 burp kernel: uscanner0: bulk-in and/or bulk-out endpoint not found

That's from uscanner_attach in uscanner.c, and it quits there.  But is 
it due to a firmware-less scanner or FreeBSD USB code?

You should probably say exactly what brand and model of scanner you're 
using.

> 	From the documentation there appear to be conflicts in vendor
> and device ids and if you check these against usbdevs, usbdevs will see
> this device and vendor as something quite different from what they are.

For that vendor and product, I only see the one entry.  But it's one of 
those scanners that needs a firmware download, gt68xx.  Maybe on those 
you have to use ugen to load the firmware, then load uscanner?  I plead 
ignorance due to lack of hardware to try.

Use of scanners that need firmware uploads is probably an area that 
should be expanded in the Handbook.  At present, it's mentioned but just 
refers to the sane driver man page, which in this case is 
libusb-specific.

> 	What Freebsd are you using Warren?

At the moment:

7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Sep  3 09:45:37 MDT 2008

-Warren Block * Rapid City, South Dakota USA
From koitsu at FreeBSD.org  Tue Sep  9 16:58:24 2008
From: koitsu at FreeBSD.org (Jeremy Chadwick)
Date: Tue Sep  9 16:58:30 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909122947.X64474@gecko.reptiles.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
	<20080909162604.GA1032@gothic.blackend.org>
	<20080909122947.X64474@gecko.reptiles.org>
Message-ID: <20080909164821.GA2891@icarus.home.lan>

On Tue, Sep 09, 2008 at 12:35:06PM -0400, Geoffrey wrote:
> On Tue, 9 Sep 2008, Marc Fonvieille wrote:
>
>> On Tue, Sep 09, 2008 at 06:59:04AM -0400, Geoffrey wrote:
>>> On Tue, 9 Sep 2008, Marc Fonvieille wrote:
>>>
>>> Hi Marc
>>>
>>>> On Mon, Sep 08, 2008 at 05:36:18PM -0400, Geoffrey wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Regarding
>>>>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html,
>>>>>
>>>>> sane-find-scanner won't find a scanner if uscanner is in the kernel (as
>>>>
>>>> Hello,
>>>>
>>>> I'm not sure to understand you.  What do you mean by "sane-find-scanner
>>>> won't find a scanner if uscanner is in the kernel" ?
>>>>
>>>  	Sorry.  I need to be more specific.  "sane-find-scanner" will
>>> not find a usb scanner if:
>>>
>>> BURP:#device            uscanner        # Scanners
>>>
>>>  	is not remarked out in your kernel config file OR if you load
>>> the kld uscanner.  Sane uses usblib and usblib can't find the scanner
>>> if uscanner is loaded.
>>>  	Yes, you have to build and install a new kernel to do this as
>>> uscanner is in the generic kernel:
>>>  	GENERIC:device          uscanner        # Scanners
>>>
>> [...]
>>
>> % sane-find-scanner -q
>> found USB scanner (vendor=0x04a9, product=0x220e) at /dev/uscanner0
>>
>> % kldstat -v | grep scanner
>> 267 uhub/uscanner
>>
>> I can reproduce the same behavior on another machine (both of them run a
>> kernel with uscanner support in).
>>
>> You should check your configuration and maybe see if your scanner does
>> not need you to load a firmware.
>>
> 	Please attach your `uname -a`.  As I've noted I'm running
> FreeBSD burp.bogstomp.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #4: Mon
> Sep  8 16:11:35 EDT 2008
> root@burp.bogstomp.org:/usr/obj/usr/src/sys/BURP  i386
>
> 	/dev/uscanner0 is not being created on my installation.  From
> the manpages (excepting those that were modified) sane appears to not
> want uscanner as it is presently configured to use usblib which uses
> ugen*.  Ugen* can't see the scanner with uscanner in the kernel or
> loaded as a module on my installation.

Okay, so with that information combined with the dmesg output you
provided earlier (not quoted above), it's safe to say the problem here
is that your scanner is not recognised by uscanner(4), and needs code
written or USB device IDs added to the list to get support for it.
Devices which aren't recognised often show up as ugen(4) devices.

This thread should definitely be moved to freebsd-usb.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |

From blackend at FreeBSD.org  Tue Sep  9 16:59:52 2008
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Tue Sep  9 16:59:59 2008
Subject: sane configuration in Freebsd 7
In-Reply-To: <20080909122947.X64474@gecko.reptiles.org>
References: <20080908172940.K64474@gecko.reptiles.org>
	<20080909055234.GA98761@abigail.blackend.org>
	<20080909064619.Y64474@gecko.reptiles.org>
	<20080909162604.GA1032@gothic.blackend.org>
	<20080909122947.X64474@gecko.reptiles.org>
Message-ID: <20080909165949.GC1032@gothic.blackend.org>

On Tue, Sep 09, 2008 at 12:35:06PM -0400, Geoffrey wrote:
> >>
> > [...]
> >
> > % sane-find-scanner -q
> > found USB scanner (vendor=0x04a9, product=0x220e) at /dev/uscanner0
> >
> > % kldstat -v | grep scanner
> > 267 uhub/uscanner
> >
> > I can reproduce the same behavior on another machine (both of them run a
> > kernel with uscanner support in).
> >
> > You should check your configuration and maybe see if your scanner does
> > not need you to load a firmware.
> >
>  	Please attach your `uname -a`.  As I've noted I'm running
> FreeBSD burp.bogstomp.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #4: Mon
> Sep  8 16:11:35 EDT 2008
> root@burp.bogstomp.org:/usr/obj/usr/src/sys/BURP  i386
>

Both run 7.0-STABLE from June

>  	/dev/uscanner0 is not being created on my installation.  From
> the manpages (excepting those that were modified) sane appears to not
> want uscanner as it is presently configured to use usblib which uses
> ugen*.  Ugen* can't see the scanner with uscanner in the kernel or
> loaded as a module on my installation.

The fact you don't have /dev/uscanner0 is simply cause uscanner(4) was
unable to attach correctly your scanner to the system therefore the
fallback to ugen.
According to src/sys/dev/usb/usbdevs you have an Ultima 1200 UB Plus and
this one should work with uscanner(4).  There is a conflict/problem
somewhere :(
You should, as I said in a previous mail, contact freebsd-usb mailing
list and maybe fill in a PR.


-- 
Marc
From jhb at freebsd.org  Tue Sep  9 21:04:26 2008
From: jhb at freebsd.org (John Baldwin)
Date: Tue Sep  9 21:04:32 2008
Subject: docs/127253: Error in Handbook:
	http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
In-Reply-To: <200809091627.m89GRJYG070708@www.freebsd.org>
References: <200809091627.m89GRJYG070708@www.freebsd.org>
Message-ID: <200809091322.00250.jhb@freebsd.org>

On Tuesday 09 September 2008 12:27:19 pm Fritz Katz wrote:
> 
> >Number:         127253
> >Category:       docs
> >Synopsis:       Error in Handbook: 
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
> >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 Sep 09 16:30:02 UTC 2008
> >Closed-Date:
> >Last-Modified:
> >Originator:     Fritz Katz
> >Release:        7.0-RELEASE i386
> >Organization:
> AAArt
> >Environment:
> # uname -rm
> 7.0-RELEASE i386
> 
> >Description:
>    This page in the handbook appears to give bad advice:
>       
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
>     
>         # ddd -k /var/crash/kernel.0 /var/crash/vmcore.0
>         
>    Is the handbook out-of-date? Has the '-k' option been removed from 'ddd'?
> 
>    I think the correct invocation for 'ddd' should be:
>    
>         # ddd --debugger kgdb kernel.debug /var/crash/vmcore.0
>     
>     Following instructions in the handbook results in this message: 
>     "GDB could not be started.", and the ddd console window prints:
>     
>         GNU DDD 3.3.11 (i386-portbld-freebsd7.0), 
>           by Dorothea Lutkehaus and Andreas Zeller. 
>         ...
>         gdb: unrecognized option '-k'
>         Use 'gdb --help' for a complete list of options.
> 
>     Which appears to be correct since,
>         # ddd --help
>     and
>         # gdb --help
>     shows there is no option '-k' 
>     _________________
>     
>     also, the second option, '/var/crash/kernel.0', also appears to
>     be incorrect. That file or executable does not exist. 
>     
>     Is that the executable? If so, my 'kernel' is located in:
>     
>        # cd /usr/obj/usr/src/sys/AAART/
>        # ls kernel*
>          kernel  kernel.debug   kernel.symbols
>     
>     _________________
> 
>     Attempting:
>         # ddd --core=/var/crash/vmcore.0
>     gives this message:
>         "/var/crash/vmcore.0" is not a core dump: File format not recognized
>         (gdb)
>         
>   However, the instructions for the command line debugger, 'kgdb', on this
>   page are OK:
>   
>     
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
>   
>   and the /var/crash/vmcore.0 is recognized.
>  
>   # cd /usr/obj/usr/src/sys/AAART/
>   # kgdb kernel.debug /var/crash/vmcore.0 
> >How-To-Repeat:
> 
> Read the handbook and attempt to follow it's instructions.
> >Fix:
> Replace the offending line in the Handbook with:
> 
>   # ddd --debugger kgdb kernel.debug /var/crash/vmcore.0

I think your updates are correct.  The old usage is from FreeBSD 4.x when one 
used 'gdb -k' rather than 'kgdb'.  Crash dumps on 4.x also left a kernel 
image in /var/crash which explains the /var/crash/kernel.0 reference.

-- 
John Baldwin
From jhb at freebsd.org  Tue Sep  9 21:10:08 2008
From: jhb at freebsd.org (John Baldwin)
Date: Tue Sep  9 21:10:22 2008
Subject: docs/127253: Error in Handbook:
	http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
Message-ID: <200809092110.m89LA8Si011364@freefall.freebsd.org>

The following reply was made to PR docs/127253; it has been noted by GNATS.

From: John Baldwin <jhb@freebsd.org>
To: freebsd-doc@freebsd.org
Cc: Fritz Katz <frtzkatz@yahoo.com>, freebsd-gnats-submit@freebsd.org
Subject: Re: docs/127253: Error in Handbook: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
Date: Tue, 9 Sep 2008 13:22:00 -0400

 On Tuesday 09 September 2008 12:27:19 pm Fritz Katz wrote:
 > 
 > >Number:         127253
 > >Category:       docs
 > >Synopsis:       Error in Handbook: 
 http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
 > >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 Sep 09 16:30:02 UTC 2008
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Fritz Katz
 > >Release:        7.0-RELEASE i386
 > >Organization:
 > AAArt
 > >Environment:
 > # uname -rm
 > 7.0-RELEASE i386
 > 
 > >Description:
 >    This page in the handbook appears to give bad advice:
 >       
 http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
 >     
 >         # ddd -k /var/crash/kernel.0 /var/crash/vmcore.0
 >         
 >    Is the handbook out-of-date? Has the '-k' option been removed from 'ddd'?
 > 
 >    I think the correct invocation for 'ddd' should be:
 >    
 >         # ddd --debugger kgdb kernel.debug /var/crash/vmcore.0
 >     
 >     Following instructions in the handbook results in this message: 
 >     "GDB could not be started.", and the ddd console window prints:
 >     
 >         GNU DDD 3.3.11 (i386-portbld-freebsd7.0), 
 >           by Dorothea Lutkehaus and Andreas Zeller. 
 >         ...
 >         gdb: unrecognized option '-k'
 >         Use 'gdb --help' for a complete list of options.
 > 
 >     Which appears to be correct since,
 >         # ddd --help
 >     and
 >         # gdb --help
 >     shows there is no option '-k' 
 >     _________________
 >     
 >     also, the second option, '/var/crash/kernel.0', also appears to
 >     be incorrect. That file or executable does not exist. 
 >     
 >     Is that the executable? If so, my 'kernel' is located in:
 >     
 >        # cd /usr/obj/usr/src/sys/AAART/
 >        # ls kernel*
 >          kernel  kernel.debug   kernel.symbols
 >     
 >     _________________
 > 
 >     Attempting:
 >         # ddd --core=/var/crash/vmcore.0
 >     gives this message:
 >         "/var/crash/vmcore.0" is not a core dump: File format not recognized
 >         (gdb)
 >         
 >   However, the instructions for the command line debugger, 'kgdb', on this
 >   page are OK:
 >   
 >     
 http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
 >   
 >   and the /var/crash/vmcore.0 is recognized.
 >  
 >   # cd /usr/obj/usr/src/sys/AAART/
 >   # kgdb kernel.debug /var/crash/vmcore.0 
 > >How-To-Repeat:
 > 
 > Read the handbook and attempt to follow it's instructions.
 > >Fix:
 > Replace the offending line in the Handbook with:
 > 
 >   # ddd --debugger kgdb kernel.debug /var/crash/vmcore.0
 
 I think your updates are correct.  The old usage is from FreeBSD 4.x when one 
 used 'gdb -k' rather than 'kgdb'.  Crash dumps on 4.x also left a kernel 
 image in /var/crash which explains the /var/crash/kernel.0 reference.
 
 -- 
 John Baldwin
From trhodes at FreeBSD.org  Wed Sep 10 05:42:57 2008
From: trhodes at FreeBSD.org (trhodes@FreeBSD.org)
Date: Wed Sep 10 05:43:04 2008
Subject: docs/124716: [patch] GEOM RAID1 handbook example only covers
	boot partition
Message-ID: <200809100542.m8A5gujI065055@freefall.freebsd.org>

Synopsis: [patch] GEOM RAID1 handbook example only covers boot partition

State-Changed-From-To: open->analyzed
State-Changed-By: trhodes
State-Changed-When: Wed Sep 10 05:41:07 UTC 2008
State-Changed-Why: 
Working on a new gmirror section, would like to further
investigate this idea.  Take the PR.


Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Wed Sep 10 05:41:07 UTC 2008
Responsible-Changed-Why: 
Working on a new gmirror section, would like to further
investigate this idea.  Take the PR.

http://www.freebsd.org/cgi/query-pr.cgi?pr=124716
From alex at braske.net  Thu Sep 11 07:30:03 2008
From: alex at braske.net (Aleksandr Stankevic)
Date: Thu Sep 11 07:30:09 2008
Subject: docs/127290: FAQ book: discourage the use of port 53 for outgoing
	DNS queries
Message-ID: <200809110721.m8B7LKaV079112@www.freebsd.org>


>Number:         127290
>Category:       docs
>Synopsis:       FAQ book: discourage the use of port 53 for outgoing DNS queries
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 11 07:30:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Aleksandr Stankevic
>Release:        
>Organization:
>Environment:
>Description:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/security.html#EXTRA-NAMED-PORT

-- quote --
BIND uses a random high-numbered port for outgoing queries. If you want to use port 53 for outgoing queries, either to get past a firewall or to make yourself feel better, you can try the following in /etc/namedb/named.conf:

options {
        query-source address * port 53;
};

You can replace the * with a single IP address if you want to tighten things further.
-- quote --

We should discourage the use of query-source address * port 53 because of the last vulnerability in DNS.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From pgj at FreeBSD.org  Thu Sep 11 11:40:08 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Thu Sep 11 11:40:14 2008
Subject: docs/127290: FAQ book: discourage the use of port 53 for
	outgoing DNS queries
Message-ID: <200809111140.m8BBe7g8085071@freefall.freebsd.org>

Synopsis: FAQ book: discourage the use of port 53 for outgoing DNS queries

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Thu Sep 11 11:38:38 UTC 2008
Responsible-Changed-Why: 
Take.

http://www.freebsd.org/cgi/query-pr.cgi?pr=127290
From mohacsi at niif.hu  Thu Sep 11 15:30:26 2008
From: mohacsi at niif.hu (Mohacsi Janos)
Date: Thu Sep 11 15:30:33 2008
Subject: update ftp mirror contact
Message-ID: <alpine.BSF.2.00.0809111724300.86157@mignon.ki.iif.hu>

Dear Sirs,
 	Can you update
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html#HANDBOOK-MIRRORS-CHAPTER-SGML-MIRRORS-HU-FTP
my contact is no longer mohacsi@ik.bme.hu, but rather janos.mohacsi@bsd.hu
Best Regards,


Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F  4300 6F64 7B00 70EF 9882
From danger at rulez.sk  Thu Sep 11 16:37:45 2008
From: danger at rulez.sk (Daniel Gerzo)
Date: Thu Sep 11 16:37:51 2008
Subject: update ftp mirror contact
In-Reply-To: <alpine.BSF.2.00.0809111724300.86157@mignon.ki.iif.hu>
References: <alpine.BSF.2.00.0809111724300.86157@mignon.ki.iif.hu>
Message-ID: <b28ab462192a3d405baa28d7d2c81b98@services.rulez.sk>


Hello Janos,

I have updated your email as per your request.
It should appear on the web site in next 48 hours.
Thank you for your submission!

On Thu, 11 Sep 2008 17:30:15 +0200 (CEST), Mohacsi Janos <mohacsi@niif.hu>
wrote:
> Dear Sirs,
>  	Can you update
>
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html#HANDBOOK-MIRRORS-CHAPTER-SGML-MIRRORS-HU-FTP
> my contact is no longer mohacsi@ik.bme.hu, but rather
janos.mohacsi@bsd.hu
> Best Regards,
> 
> 
> Janos Mohacsi

-- 
S pozdravom / Best regards
  Daniel Ger?o

From gavin at FreeBSD.org  Thu Sep 11 18:48:35 2008
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Thu Sep 11 18:48:42 2008
Subject: docs/127253: Error in Handbook:
	http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html
Message-ID: <200809111848.m8BImZIu035570@freefall.freebsd.org>

Synopsis: Error in Handbook: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-ddd.html

Responsible-Changed-From-To: freebsd-doc->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Thu Sep 11 18:44:21 UTC 2008
Responsible-Changed-Why: 
I'm already working on this section

http://www.freebsd.org/cgi/query-pr.cgi?pr=127253
From shatsillo at gov.spb.ru  Fri Sep 12 14:32:11 2008
From: shatsillo at gov.spb.ru (=?koi8-r?Q?=F7=C9=D4=C1=CC=C9=CA_?= =?koi8-r?Q?=FB=C1=C3=C9=CC=CC=CF?=)
Date: Fri Sep 12 14:32:19 2008
Subject: mistake in http://www.freebsd.org/releases/7.0R/hardware.html#SOUND
Message-ID: <1221228977.96999.35.camel@cat>

Hello!

mistake in http://www.freebsd.org/releases/7.0R/hardware.html#SOUND
about driver snd_emu10kx - in second string

[i386,amd64] The snd_emu10kx(4) driver does support the following sound
cards (although they are named similar to some supported ones):

but in man we see does not support

--
with best regards
system administrator of SPb government
Shatsillo Vit


From carock at epconline.com  Sat Sep 13 15:10:02 2008
From: carock at epconline.com (Chuck Rock)
Date: Sat Sep 13 15:10:11 2008
Subject: docs/127359: Undocumented firewall_xxx options for rc.conf in
	stable branch
Message-ID: <200809131502.m8DF2Xvp056654@www.freebsd.org>


>Number:         127359
>Category:       docs
>Synopsis:       Undocumented firewall_xxx options for rc.conf in stable branch
>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 Sep 13 15:10:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Chuck Rock
>Release:        7.0-RELEASE-p4
>Organization:
EPC, Inc.
>Environment:
FreeBSD boss4.epconline.net 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #0: Tue Sep  2 19:32:35 UTC 2008     root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
Theres no informatoin in man ipfw or man rc.conf about these options found in /etc/defaults/rc.conf for the firewall.

firewall_myservices=""          # List of TCP ports on which this host
firewall_allowservices=""       # List of IPs which has access to
                                #  $firewall_myservices
firewall_trusted=""             # List of IPs which has full access to this host
firewall_logdeny="NO"           # Set to YES to log default denied incoming
firewall_nologports="135-139,445 1026,1027 1433,1434" # List of TCP/UDP ports

An explanation was provided to moe for some of them by Giorgos Keramidas on the comp.unix.bsd.freebsd.misc news group.

He asked that I submit a PR so he can work on it.

Some of the options are explained by him as follows.

The lists are space- or TAB-separated.

These rc.conf options are only used in for-loops of shell code in the
`/etc/rc.firewall' script.  You can delimit entries with space or TAB
characters.  If you carefully quote the list of values, you can even use
multiple lines like:

    firewall_trusted="192.168.1.1/32
       192.168.1.3 192.168.1.254"

The firewall_allowservices and firewall_myservices work closely
together:

    * The first one is a simple (space separated) list of hosts that
      connections may originate from.

    * The second is a simple (space separated) list of local services
      that will be open for all hosts in ${firewall_allowservices}.

One rule is added to the final firewall ruleset for every combination of
`firewall_allowservices' and `firewall_myservices', so if you use in
your `rc.conf' file something like:

    firewall_allowservices="192.168.1.1 192.168.1.2"
    firewall_myservices="ssh smtp"

Then your final firewall will contain the rules:

    add pass tcp from 192.168.1.1 to me ssh
    add pass tcp from 192.168.1.2 to me ssh
    add pass tcp from 192.168.1.1 to me smtp
    add pass tcp from 192.168.1.2 to me smtp

If you are planning to use these options, it's worth considering at
least the following details too:

  * Only TCP services are enabled by these rules.  If you have a UDP
    service, you will have to either (a) edit your `rc.firewall' script,
    or (b) roll your own ruleset.

  * The `firewall_allowservices' and `firewall_myservices' options are
    *only* valid if you are using the pre-configure `workstation' type
    for your firewall ruleset.  If you are using any other set of
    firewall rules, the current `rc.firewall' script will completely
    ignore any `rc.conf' value configured for `firewall_allowservices'
    and `firewall_myservices'!

>How-To-Repeat:
grep firewall /etc/defaults/rc.conf

'man rc.conf' and search for any of the options listed above in description will show no results.

Same for 'man ipfw'


>Fix:
Giorgos Keramidas in the news group said

This is a bug.  The firewall_xxx options seem very under-documented.
The bug is even more important because the code has already found its
way to a STABLE branch, but the documentation bits are still missing.

Please take a moment to open a problem report and send me the number, or
let me know that you don't have the time to do that just now, so I can
open one myself.  Then I can work a bit to refine the explanation I
wrote above, and commit it to the rc.conf manpage.

>Release-Note:
>Audit-Trail:
>Unformatted:
From alex7070m at gmail.com  Sat Sep 13 18:44:32 2008
From: alex7070m at gmail.com (Alexander)
Date: Sat Sep 13 18:44:39 2008
Subject: from site
Message-ID: <003301c915cc$5a9e1130$a7c2725c@alex>

Good day! I write from your site http://www.freebsd.org . I am looking for information about the  CronTab commands syntax to get MySQL database backup, for the case where the MySQL database is on a separate server (host database). I would be grateful to you for information on this subject. 

Sincerely, Alexander
From keramida at FreeBSD.org  Sat Sep 13 19:19:24 2008
From: keramida at FreeBSD.org (keramida@FreeBSD.org)
Date: Sat Sep 13 19:19:30 2008
Subject: docs/127359: Undocumented firewall_xxx options for rc.conf in
	stable branch
Message-ID: <200809131919.m8DJJN6B058544@freefall.freebsd.org>

Synopsis: Undocumented firewall_xxx options for rc.conf in stable branch

Responsible-Changed-From-To: freebsd-doc->keramida
Responsible-Changed-By: keramida
Responsible-Changed-When: Sat Sep 13 19:18:43 UTC 2008
Responsible-Changed-Why: 
I'll update rc.conf.5 for the new options.

http://www.freebsd.org/cgi/query-pr.cgi?pr=127359
From que_deseja at hotmail.com  Sun Sep 14 07:11:30 2008
From: que_deseja at hotmail.com (Desmond Chapman)
Date: Sun Sep 14 07:11:36 2008
Subject: kde4
Message-ID: <BLU126-W26EDA08AB6F65495F3809CED530@phx.gbl>


Since kde4 uses a different path for the startup script, will this be reflected in the handbook?
 [ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure]  to [ttyv8 "/usr/local/kde4/bin/kdm -nodaemon" xterm on secure] ?


_________________________________________________________________
See how Windows connects the people, information, and fun that are part of your life.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093175mrt/direct/01/
From arved at FreeBSD.org  Sun Sep 14 08:16:27 2008
From: arved at FreeBSD.org (Tilman Linneweh)
Date: Sun Sep 14 08:16:32 2008
Subject: kde4
In-Reply-To: <BLU126-W26EDA08AB6F65495F3809CED530@phx.gbl>
References: <BLU126-W26EDA08AB6F65495F3809CED530@phx.gbl>
Message-ID: <52A81706-0743-4288-B86B-C4EFD0389280@FreeBSD.org>


On Sep 14, 2008, at 8:59, Desmond Chapman wrote:
> Since kde4 uses a different path for the startup script, will this  
> be reflected in the handbook?
>  [ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure]  to [ttyv8  
> "/usr/local/kde4/bin/kdm -nodaemon" xterm on secure] ?

Well once kde3 becomes obsolete, kde4 will probably move to /usr/ 
local. So i don't think the statusquo needs to be documented.
From sonic2000gr at gmail.com  Sun Sep 14 09:12:15 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Sun Sep 14 09:12:22 2008
Subject: kde4
In-Reply-To: <BLU126-W26EDA08AB6F65495F3809CED530@phx.gbl>
References: <BLU126-W26EDA08AB6F65495F3809CED530@phx.gbl>
Message-ID: <48CCCEF6.9010607@gmail.com>

Desmond Chapman wrote:
> Since kde4 uses a different path for the startup script, will this be reflected in the handbook?
>  [ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure]  to [ttyv8 "/usr/local/kde4/bin/kdm -nodaemon" xterm on secure] ?
>
>   

Actually, this has been recently added to the handbook, see:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html

section 5.7.3.1
From trhodes at FreeBSD.org  Sun Sep 14 10:31:13 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Sun Sep 14 10:31:25 2008
Subject: from site
In-Reply-To: <003301c915cc$5a9e1130$a7c2725c@alex>
References: <003301c915cc$5a9e1130$a7c2725c@alex>
Message-ID: <20080914063056.7e8271f8.trhodes@FreeBSD.org>

On Sat, 13 Sep 2008 21:11:32 +0300
"Alexander" <alex7070m@gmail.com> wrote:

> Good day! I write from your site http://www.freebsd.org . I am looking for information about the  CronTab commands syntax to get MySQL database backup, for the case where the MySQL database is on a separate server (host database). I would be grateful to you for information on this subject. 

There is documentation on cron(8) in the handbook:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/

-- 
Tom Rhodes
From bugmaster at FreeBSD.org  Mon Sep 15 15:07:33 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep 15 15:08:05 2008
Subject: Current unassigned doc problem reports
Message-ID: <200809151507.m8FF7W8G016229@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/127220  doc        [patch] err(3) suggests using exit values from sysexit
o docs/127219  doc        [patch] style(9) is inconsistent regarding usage of sy
o docs/126934  doc        missing 'crit' in usr.sbin/syslogd/syslog.conf.5
o docs/126921  doc        [patch] History section of cpuset(1) incorrect
o docs/126590  doc        Write routine called forever in Sample Echo Pseudo-Dev
o docs/126487  doc        fix language on atol(3) manpage
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/126445  doc        discussion on WEP settings in wpa_supplicant.conf(5) m
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/123400  doc        gvinum startup in handbook
o docs/123035  doc        [patch] bugs in refuse.README
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o 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 docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121197  doc        [patch] edits to books/porters-handbook
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/120628  doc        PAE documentation errror in handbook
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/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/119907  doc        Ports compatibility
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
a docs/119536  doc        a few typos in French handbook (basics)
s docs/119404  doc        [request] events page should list only last 2 years wo
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
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/117798  doc        formatting oddity in sysmouse(4)
o docs/117747  doc        'break' system call needs a man page
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
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/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/115921  doc        Booting from pst(4) is not supported
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/112481  doc        bug in ppp.linkup example
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/111263  doc        [request] Information on $EDITOR variable in section 3
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/109983  doc        No manual entry for protoize
o docs/109981  doc        No manual entry for post-grohtml
o docs/109977  doc        No manual entry for ksu
o docs/109975  doc        No manual entry for elf2aout
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
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
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/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
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/104403  doc        man security should mention that the usage of the X Wi
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
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/84806   doc        mdoc(7) manpage has section ordering problems
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/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
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/47818   doc        [patch] ln(1) manpage is confusing
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
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
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 (<olink>)
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 <emphasis> tags in the sourc

149 problems total.

From mick at cs.wisc.edu  Mon Sep 15 16:10:05 2008
From: mick at cs.wisc.edu (Mick Charles Beaver)
Date: Mon Sep 15 16:10:16 2008
Subject: docs/127401: typo in portsnap man page
Message-ID: <200809151607.m8FG7iPm083852@www.freebsd.org>


>Number:         127401
>Category:       docs
>Synopsis:       typo in portsnap man page
>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 Sep 15 16:10:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mick Charles Beaver
>Release:        7.0
>Organization:
>Environment:
>Description:
PORTSNAP(8) has a small typo:

-f conffile  Read the configuration from from conffile.  (default:
                  /etc/portsnap.conf)

Notice that "from" is repeated.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From joel at FreeBSD.org  Mon Sep 15 16:30:14 2008
From: joel at FreeBSD.org (joel@FreeBSD.org)
Date: Mon Sep 15 16:30:21 2008
Subject: docs/98759: [patch] sbp_targ(4) man page missing reference to
	device targ
Message-ID: <200809151630.m8FGUELa028425@freefall.freebsd.org>

Synopsis: [patch] sbp_targ(4) man page missing reference to device targ

Responsible-Changed-From-To: joel->freebsd-doc
Responsible-Changed-By: joel
Responsible-Changed-When: Mon Sep 15 16:29:25 UTC 2008
Responsible-Changed-Why: 
Over to docs.

http://www.freebsd.org/cgi/query-pr.cgi?pr=98759
From danger at FreeBSD.org  Mon Sep 15 16:30:47 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Mon Sep 15 16:30:54 2008
Subject: docs/127401: typo in portsnap man page
Message-ID: <200809151630.m8FGUluS028529@freefall.freebsd.org>

Synopsis: typo in portsnap man page

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Mon Sep 15 16:30:32 UTC 2008
Responsible-Changed-Why: 
I will take care

http://www.freebsd.org/cgi/query-pr.cgi?pr=127401
From joel at FreeBSD.org  Mon Sep 15 16:31:13 2008
From: joel at FreeBSD.org (joel@FreeBSD.org)
Date: Mon Sep 15 16:31:19 2008
Subject: docs/85100: NOTES: ICH audio device support statement is
	ambiguous
Message-ID: <200809151631.m8FGVDkM028632@freefall.freebsd.org>

Synopsis: NOTES: ICH audio device support statement is ambiguous

Responsible-Changed-From-To: joel->freebsd-doc
Responsible-Changed-By: joel
Responsible-Changed-When: Mon Sep 15 16:30:47 UTC 2008
Responsible-Changed-Why: 
Over to docs.

http://www.freebsd.org/cgi/query-pr.cgi?pr=85100
From joel at FreeBSD.org  Mon Sep 15 16:32:02 2008
From: joel at FreeBSD.org (joel@FreeBSD.org)
Date: Mon Sep 15 16:32:09 2008
Subject: docs/84538: [patch] sk(4) driver supports Marvell 88E800x chip
	too
Message-ID: <200809151632.m8FGW2MU028738@freefall.freebsd.org>

Synopsis: [patch] sk(4) driver supports Marvell 88E800x chip too

Responsible-Changed-From-To: joel->freebsd-doc
Responsible-Changed-By: joel
Responsible-Changed-When: Mon Sep 15 16:31:39 UTC 2008
Responsible-Changed-Why: 
Over to docs.

http://www.freebsd.org/cgi/query-pr.cgi?pr=84538
From nick at anywi.com  Mon Sep 15 19:20:02 2008
From: nick at anywi.com (Nick Hibma)
Date: Mon Sep 15 19:20:09 2008
Subject: docs/127406: update umodem man page: Sony Ericsson W810i
Message-ID: <1221506196.249999.72270.nullmailer@van-laarhoven.org>


>Number:         127406
>Category:       docs
>Synopsis:       update umodem man page: Sony Ericsson W810i
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 15 19:20:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Nick Hibma
>Release:        FreeBSD 7.0-STABLE i386
>Organization:
AnyWi Technologies
>Environment:
System: FreeBSD hind.van-laarhoven.org 7.0-STABLE FreeBSD 7.0-STABLE #3: Thu Aug 14 21:10:55 CEST 2008 toor@hind.van-laarhoven.org:/usr/src/sys/i386/compile/HIND i386

>Description:

umodem supports the Sony Ericsson W810i phone. Listing all devices is not a
good idea, but adding this one, might give people with another Sony Ericsson
phone perhaps an idea to try this driver for their phone.

After all umodem is not a very commonly used driver. Usually a serial
connection is a bulk pipe, no more.
>How-To-Repeat:
...
addr 1: UHCI root hub, Intel, device uhub2
 addr 2: Sony Ericsson W810, Sony Ericsson, device ucom0
...
>Fix:
Index: umodem.4
===================================================================
RCS file: /home/ncvs/src/share/man/man4/umodem.4,v
retrieving revision 1.10
diff -u -r1.10 umodem.4
--- umodem.4	21 Aug 2007 13:20:13 -0000	1.10
+++ umodem.4	15 Sep 2008 19:11:24 -0000
@@ -96,6 +96,8 @@
 Yamaha Broadband Wireless Router RTW65b
 .It
 ELSA MicroLink 56k USB modem
+.It
+Sony Ericsson W810i phone
 .El
 .Sh SEE ALSO
 .Xr tty 4 ,
>Release-Note:
>Audit-Trail:
>Unformatted:
From jhb at freebsd.org  Mon Sep 15 19:28:37 2008
From: jhb at freebsd.org (John Baldwin)
Date: Mon Sep 15 19:28:43 2008
Subject: docs/127359: Undocumented firewall_xxx options for rc.conf in
	stable branch
In-Reply-To: <200809131919.m8DJJN6B058544@freefall.freebsd.org>
References: <200809131919.m8DJJN6B058544@freefall.freebsd.org>
Message-ID: <200809151408.26110.jhb@freebsd.org>

On Saturday 13 September 2008 03:19:23 pm keramida@freebsd.org wrote:
> Synopsis: Undocumented firewall_xxx options for rc.conf in stable branch
> 
> Responsible-Changed-From-To: freebsd-doc->keramida
> Responsible-Changed-By: keramida
> Responsible-Changed-When: Sat Sep 13 19:18:43 UTC 2008
> Responsible-Changed-Why: 
> I'll update rc.conf.5 for the new options.
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=127359

It's probably worth documenting the other new firewall_* options I added 
recently for "simple" and "client" as well.

-- 
John Baldwin
From keramida at freebsd.org  Mon Sep 15 20:01:00 2008
From: keramida at freebsd.org (Giorgos Keramidas)
Date: Mon Sep 15 20:01:08 2008
Subject: docs/127359: Undocumented firewall_xxx options for rc.conf in
	stable branch
In-Reply-To: <200809151408.26110.jhb@freebsd.org> (John Baldwin's message of
	"Mon, 15 Sep 2008 14:08:25 -0400")
References: <200809131919.m8DJJN6B058544@freefall.freebsd.org>
	<200809151408.26110.jhb@freebsd.org>
Message-ID: <87iqsx42en.fsf@kobe.laptop>

On Mon, 15 Sep 2008 14:08:25 -0400, John Baldwin <jhb@freebsd.org> wrote:
> On Saturday 13 September 2008 03:19:23 pm keramida@freebsd.org wrote:
>> Synopsis: Undocumented firewall_xxx options for rc.conf in stable branch
>>
>> Responsible-Changed-From-To: freebsd-doc->keramida
>> Responsible-Changed-By: keramida
>> Responsible-Changed-When: Sat Sep 13 19:18:43 UTC 2008
>> Responsible-Changed-Why:
>> I'll update rc.conf.5 for the new options.
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=127359
>
> It's probably worth documenting the other new firewall_* options I
> added recently for "simple" and "client" as well.

Good point, thanks :)

I'm going through the ``Tom's Handbook'' patches by trhodes now, and
then take care of this one.

From blackend at FreeBSD.org  Tue Sep 16 20:04:00 2008
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Tue Sep 16 20:06:56 2008
Subject: HEADS UP: doc/ slush begins
In-Reply-To: <20080908130927.GA1172@gothic.blackend.org>
References: <20080908130927.GA1172@gothic.blackend.org>
Message-ID: <20080916200357.GA1027@gothic.blackend.org>

On Mon, Sep 08, 2008 at 03:09:27PM +0200, Marc Fonvieille wrote:
> Hi all,
> 
> As announced, the doc/ tree is now in a slush.  Please postpone all
> non-essential changes until after the doc/ tree is tagged (currently
> scheduled for 15 September, 2008).
> 
> While this is not a real freeze, if you need to commit a relatively
> large change to fix or improve our documentation for 7.1-RELEASE (or
> 6.4-RELEASE), please put a note for translators onto your commit log.
> 

The doc tree has been tagged for both 6.4-RELEASE and 7.1-RELEASE.  If
you noticed a problem or have a change which must be included in the
release, please let me know.

You can consider the doc tree is open for commits now, but any sweeping
changes should be postponed until after the release day.

Thank you for your cooperation and keep up the good work!

-- 
Marc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080916/54208e74/attachment.pgp
From remko at FreeBSD.org  Tue Sep 16 20:43:40 2008
From: remko at FreeBSD.org (Remko Lodder)
Date: Tue Sep 16 20:43:47 2008
Subject: HEADS UP: doc/ slush begins
In-Reply-To: <20080916200357.GA1027@gothic.blackend.org>
References: <20080908130927.GA1172@gothic.blackend.org>
	<20080916200357.GA1027@gothic.blackend.org>
Message-ID: <48D01461.6070409@FreeBSD.org>

Marc Fonvieille wrote:
> On Mon, Sep 08, 2008 at 03:09:27PM +0200, Marc Fonvieille wrote:
>> Hi all,
>>
>> As announced, the doc/ tree is now in a slush.  Please postpone all
>> non-essential changes until after the doc/ tree is tagged (currently
>> scheduled for 15 September, 2008).
>>
>> While this is not a real freeze, if you need to commit a relatively
>> large change to fix or improve our documentation for 7.1-RELEASE (or
>> 6.4-RELEASE), please put a note for translators onto your commit log.
>>
> 
> The doc tree has been tagged for both 6.4-RELEASE and 7.1-RELEASE.  If
> you noticed a problem or have a change which must be included in the
> release, please let me know.
> 
> You can consider the doc tree is open for commits now, but any sweeping
> changes should be postponed until after the release day.
> 
> Thank you for your cooperation and keep up the good work!
> 

Yay, thanks everyone involved for the good work. Congratulations for 
being accepted into re@ Marc !

:-)

Cheers,
remko

-- 

/"\   Best regards,                      | remko@FreeBSD.org
\ /   Remko Lodder                       | remko@EFnet
  X    http://www.evilcoder.org/          |
/ \   ASCII Ribbon Campaign              | Against HTML Mail and News
From edwin at mavetju.org  Wed Sep 17 04:10:03 2008
From: edwin at mavetju.org (Edwin Groothuis)
Date: Wed Sep 17 04:10:08 2008
Subject: docs/127432: [patch] update fsck_ffs(8) man-page with regarding to
	exit status
Message-ID: <20080917040320.9308836E@k7.mavetju>


>Number:         127432
>Category:       docs
>Synopsis:       [patch] update fsck_ffs(8) man-page with regarding to exit status
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Sep 17 04:10:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Edwin Groothuis
>Release:        FreeBSD 7.0-RELEASE-p1 i386
>Organization:
-
>Environment:
System: FreeBSD k7.mavetju 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #2: Wed May 28 08:12:56 EST 2008 edwin@k7.mavetju:/usr/src/sys/i386/compile/k7 i386


>Description:

While looking for a way to find out if a file system is clean (before
mounting it), I noticed it wasn't documented in the man-page.


EXIT STATUS
     The fsck_ffs utility exits 0 on success, and >0 if an error occurs.

     If the option -F is used, fsck_ffs exits 7 if the file system is clean.



>How-To-Repeat:
>Fix:

Index: fsck_ffs.8
===================================================================
--- fsck_ffs.8	(revision 183065)
+++ fsck_ffs.8	(working copy)
@@ -321,6 +321,12 @@
 .El
 .Sh EXIT STATUS
 .Ex -std
+.Pp
+If the option
+.Fl F
+is used,
+.Nm
+exits 7 if the file system is clean.
 .Sh DIAGNOSTICS
 The diagnostics produced by
 .Nm
>Release-Note:
>Audit-Trail:
>Unformatted:
From dfilter at FreeBSD.ORG  Wed Sep 17 07:00:09 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Wed Sep 17 07:00:18 2008
Subject: docs/127432: commit references a PR
Message-ID: <200809170700.m8H709Rw023632@freefall.freebsd.org>

The following reply was made to PR docs/127432; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/127432: commit references a PR
Date: Wed, 17 Sep 2008 06:56:44 +0000 (UTC)

 svn         2008-09-17 06:56:31 UTC
 
   FreeBSD src repository
 
   Modified files:
     sbin/fsck_ffs        fsck_ffs.8 
   Log:
   SVN rev 183110 on 2008-09-17 06:56:31Z by svn
   
   Document the -F 's return statement.
   If the application returns succesfully
   the return code is 7 (which means the
   filesystem is clean).
   
   PR:             127432
   Submitted by:   edwin
   MFC after:      3 days
   
   Revision  Changes    Path
   1.36      +6 -0      src/sbin/fsck_ffs/fsck_ffs.8
 _______________________________________________
 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 remko at FreeBSD.org  Wed Sep 17 07:07:44 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Wed Sep 17 07:07:53 2008
Subject: docs/127432: [patch] update fsck_ffs(8) man-page with regarding
	to exit status
Message-ID: <200809170707.m8H77i7w023736@freefall.freebsd.org>

Synopsis: [patch] update fsck_ffs(8) man-page with regarding to exit status

State-Changed-From-To: open->patched
State-Changed-By: remko
State-Changed-When: Wed Sep 17 07:07:29 UTC 2008
State-Changed-Why: 
Patched in current


Responsible-Changed-From-To: freebsd-doc->remko
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Sep 17 07:07:29 UTC 2008
Responsible-Changed-Why: 
Reassign to myself

http://www.freebsd.org/cgi/query-pr.cgi?pr=127432
From max at love2party.net  Wed Sep 17 12:24:32 2008
From: max at love2party.net (Max Laier)
Date: Wed Sep 17 12:24:38 2008
Subject: PC-BSD 7 released
Message-ID: <200809171411.54296.max@love2party.net>

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080917/38a01a5b/attachment.pgp
From ale at FreeBSD.org  Wed Sep 17 13:13:40 2008
From: ale at FreeBSD.org (Alex Dupre)
Date: Wed Sep 17 13:13:46 2008
Subject: PC-BSD 7 released
In-Reply-To: <200809171411.54296.max@love2party.net>
References: <200809171411.54296.max@love2party.net>
Message-ID: <48D0FC41.50600@FreeBSD.org>

Max Laier ha scritto:
> since I'm not sure about the status of www wrt the doc slush etc. ... would 
> anyone with a doc-hat care to commit something like the attached?  Thanks.

Committed, www is not freezed.

-- 
Alex Dupre
From eitan.adler at gmail.com  Wed Sep 17 22:50:01 2008
From: eitan.adler at gmail.com (Eitan Adler)
Date: Wed Sep 17 22:50:07 2008
Subject: proposal man ports change
Message-ID: <cd994e160809171549r2b0f6b3cr6cd76b0291b4d5a@mail.gmail.com>

man ports has

--     It is possible to download and use ports from the FreeBSD repository that
     are newer than the installed system; however it is important to install
     the appropriate ``Upgrade Kit'' from http://www.FreeBSD.org/ports/ first!
     The portcheckout(1) (ports/ports-mgmt/portcheckout) script (also a port,
     of course!) will help to download new ports.

Which as far as I know is not used that often.

Also man ports makes no mention of "make update" or portsnap.


Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
From kalten at sbox.tu-graz.ac.at  Thu Sep 18 00:59:34 2008
From: kalten at sbox.tu-graz.ac.at (Kalten)
Date: Thu Sep 18 01:00:05 2008
Subject: little error in network-bluetooth.html
Message-ID: <864p4ei9s1.fsf@sbox.tugraz.at>

Hello.

Just a little error in network-bluetooth.html[1] in section?29.4.2
?Plugging in the Device?:

The file /usr/share/examples/netgraph/bluetooth/rc.bluetooth does not
exist any more?although there is still an empty directory
/usr/share/examples/netgraph/bluetooth/ there.
FreeBSD_version says
Compilation release date: 700110
Execution environment release date: 700110

I suppose, you should write ?use /etc/rc.d/bluetooth? instead and delete
/usr/share/examples/netgraph/bluetooth/ from the filesystem (btw. still
there in 7.1-PRERELEASE at 700112 according to FreeBSD_version).

No big thing ;-)

Nice greatings from Graz (in Styria/Austria)!

 Kalten

Footnotes:
[1] http://www.freebsd.org/doc/en/books/handbook/network-bluetooth.html
    http://www.freebsd.org/doc/de/books/handbook/network-bluetooth.html
-- 
----FORTUNE-Spruch------------------------------------------------------
You'll wish that you had done some of the
hard things when they were easier to do.
------------------------------------------------------------------------
From newsletter at email.pctools.com  Thu Sep 18 01:52:29 2008
From: newsletter at email.pctools.com (PC Tools Newsletter)
Date: Thu Sep 18 01:52:36 2008
Subject: You Talk ... We Listen
Message-ID: <48D1B0D9.000004BC@omp.email.pctools.com>


   <!-- START Opening Header Text -->
   If you are unable to see the imag   @email.pctools.com to your Safe Sender list. <!-- END
   Opening Header Text -->
   <!-- START LOGO Placeholder -->[1] 3D"PC <!-- END LOGO Placeh   older --> 3D"" <!-- START Newsletter Month --> 3D"" <!--
   END Newsletter Month -->
   <!-- START Forward to a Friend -->[2] 3D"   Friend -->
   <!-- START Hero Image -
   Have your   Are we meeting YOUR needs?   short survey by the end of Septe   make this newsletter more valuable
   We will thank you for your efforts by giving   Award Winning Privacy Guardian.<
   [4]Click here   Tips & Tricks
   1.
   Be wary of files that you execute as they may contain a malici   application. This method of infection is commonly used by
   hackers.<   2.
   Disable file/printer sharing whilst not in use as this may pro   an opening for hackers to gain entry to your PC.
   3.
   If in use, secure your File/Printer sharing with permission a   and passwords to make unlawful entry more difficult.
   4.
   Do not run unnecessary applications that require an internet/   connection. Leaving them running in the background is like leavin   your front door open.
   5. [5]Get a Firewall. Firewalls are a usefu   attacks and preventing illegal entry into your PC as th   and inform what comes and goes from your computer.
   <!-- START Threa   the following: Low -
   https://secure.pctools.com/res/images/threat/threat_l   Medium - https://secure.pctools.com/res/images/threat/threa   t_medium.gif High -
   https://secure.pctools.com/res/images/threat/threat_   -->
   3D"   3D"" Top Threats 3D""
   Below are some of the latest threats identified b   3D""
   [6]Worm.AutoRun.GEN
   3D"   [7]RogueAntiSpyware.
   PCHealthCenter
   3D"   [8]HackTool.Winlocker.C
   3D"   [9]Trojan-Downloader.VBS.BL
   3D"   The above infections can be detected and cleaned    Internet Security and [10]Spyware Doctor with AntiVirus!<   3D"" 3D"" 3D""
   <!-- END Threats Table --><!-- START News Table -->
   3D"   3D"" News     3D""

   [11]PC Tools' Security Software Adds ThreatFire <
   [12]Doctor Remedy To Nasty Internet Viruses

   [13]Review: PC Tools Desktop Maestro 3
   3D"" 3D"" 3D""

   3D""
   <!-- END News Table -->
   <!-- START Footer Placeholder -->
   3D""
   ="" ="" =""    ="" <   SECURE & PROTECT<   3D"" [14]Spyware Doctor with AntiVirus 3D"" [15]Registry M   echanic
   3D"" [16]PC Tools I      3D""
   <!-- END Footer Placeholder -->

   This message was inte   You have received this message because   Tools newsletter and special promotions'.

   [18]Upda   us plea
   PC T   Units A & B, Block 4, Shannon Business Park   Ireland.
   Copyright ? 2008 PC Tools. A


   [sns.rsys=]

References

   Visible links
   1. 3D"https://email.pctoo=/
   2. 3D"https://email.pct=/
   3. 3D"https://email.pctools.com/servlet/   4. 3D"https://email.pctools.com/servlet/   5. 3D"https://email.pctools.com/servlet/cc6?iJl   6. 3D"https://email.pctools.com/servlet/cc6?iJltkQT   7. 3D"https://email.pctools.com/servlet/cc6?iJltkQT   8. 3D"https://email.pctools.com/servlet/cc6?iJltkQT   9. 3D"https://email.pctools.com/servlet/cc6?iJltkQT  10. 3D"https://email.pctools.com/servlet/c  11. 3D"https://email.pctools.com/servlet/cc6?iJltkQTYRQ  12. 3D"https://email.pctools.com/servlet/cc6?iJltkQTYRQ  13. 3D"https://email.pctools.com/servlet/cc6?iJltkQTYRQ  14. 3D"https://email.pctools.com/servlet/cc6?iJltkQTYRQTVK  15. 3D"https://email=/
  16. 3D"https://email=/
  17. 3D"https://email.pctools.com/s  18. 3D"https://email.pctools.com=/
  19. 3D"https://email.pctools.com/
   Hidden links:
  20. ="https://email.pctools.com/servlet/cc6?iJltkQTYRQTVKhJxMjLLIkKQhjn
From pav at FreeBSD.org  Thu Sep 18 07:52:05 2008
From: pav at FreeBSD.org (Pav Lucistnik)
Date: Thu Sep 18 07:52:35 2008
Subject: little error in network-bluetooth.html
In-Reply-To: <864p4ei9s1.fsf@sbox.tugraz.at>
References: <864p4ei9s1.fsf@sbox.tugraz.at>
Message-ID: <1221723143.12231.5.camel@pav.hide.vol.cz>

Kalten p??e v ?t 18. 09. 2008 v 02:21 +0200:
> Hello.
> 
> Just a little error in network-bluetooth.html[1] in section 29.4.2
> ?Plugging in the Device?:
> 
> The file /usr/share/examples/netgraph/bluetooth/rc.bluetooth does not
> exist any more?although there is still an empty directory
> /usr/share/examples/netgraph/bluetooth/ there.
> FreeBSD_version says
> Compilation release date: 700110
> Execution environment release date: 700110
> 
> I suppose, you should write ?use /etc/rc.d/bluetooth? instead and delete
> /usr/share/examples/netgraph/bluetooth/ from the filesystem (btw. still
> there in 7.1-PRERELEASE at 700112 according to FreeBSD_version).
> 
> No big thing ;-)
> 
> Nice greatings from Graz (in Styria/Austria)!

That's true. I will fix the Handbook.

-- 
Pav Lucistnik <pav@oook.cz>
              <pav@FreeBSD.org>

An arrow (+0,+0) {@f0} finds a mark. It dies.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?=
	=?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?=
	=?ISO-8859-1?Q?_zpr=E1vy?=
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080918/b074d1cf/attachment.pgp
From dektec at vip.163.com  Mon Sep 22 03:07:15 2008
From: dektec at vip.163.com (Leo Peng in Dektec)
Date: Mon Sep 22 03:07:18 2008
Subject: Bench top Wave Solder Presses from Dektec
Message-ID: <1222051582_SectionID-284907_HitID-1222051431000_SiteID-30068_EmailID-37325963_DB-2@eb13.ebhost7.com>

 
Your email program does not support HTML. To view an online version of this email, please click the link below.
http://www.emailbrain.com/rwcode/content.asp?SID=1&SiteID=30068&Section=284907&EmailID=37325963&HitID=1222051431000

To unsubscribe, click the link below.
http://www.emailbrain.com/RWCode/subscribe.asp?SID=1&SiteID=30068&Email=doc@freebsd.org&HitID=1222051431000
From bugmaster at FreeBSD.org  Mon Sep 22 11:06:07 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep 22 11:06:28 2008
Subject: Current unassigned doc problem reports
Message-ID: <200809221106.m8MB66HJ014402@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/127406  doc        [patch] update umodem man page: Sony Ericsson W810i
o docs/127220  doc        [patch] err(3) suggests using exit values from sysexit
o docs/127219  doc        [patch] style(9) is inconsistent regarding usage of sy
o docs/126934  doc        missing 'crit' in usr.sbin/syslogd/syslog.conf.5
o docs/126921  doc        [patch] History section of cpuset(1) incorrect
o docs/126590  doc        [patch] Write routine called forever in Sample Echo Ps
o docs/126487  doc        fix language on atol(3) manpage
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/126445  doc        discussion on WEP settings in wpa_supplicant.conf(5) m
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/123400  doc        gvinum startup in handbook
o docs/123035  doc        [patch] bugs in refuse.README
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o 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 docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121197  doc        [patch] edits to books/porters-handbook
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/120628  doc        PAE documentation errror in handbook
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/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/119907  doc        Ports compatibility
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
a docs/119536  doc        a few typos in French handbook (basics)
s docs/119404  doc        [request] events page should list only last 2 years wo
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
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/117798  doc        formatting oddity in sysmouse(4)
o docs/117747  doc        'break' system call needs a man page
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
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/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/115921  doc        Booting from pst(4) is not supported
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/112481  doc        bug in ppp.linkup example
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/111263  doc        [request] Information on $EDITOR variable in section 3
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/109983  doc        No manual entry for protoize
o docs/109981  doc        No manual entry for post-grohtml
o docs/109977  doc        No manual entry for ksu
o docs/109975  doc        No manual entry for elf2aout
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
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
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/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
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/104403  doc        man security should mention that the usage of the X Wi
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
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/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85100   doc        NOTES: ICH audio device support statement is ambiguous
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/84806   doc        mdoc(7) manpage has section ordering problems
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84538   doc        [patch] sk(4) driver supports Marvell 88E800x chip too
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
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/47818   doc        [patch] ln(1) manpage is confusing
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
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
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 (<olink>)
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 <emphasis> tags in the sourc

153 problems total.

From walt at relnor.com  Tue Sep 23 14:10:02 2008
From: walt at relnor.com (Walter Venable)
Date: Tue Sep 23 14:10:04 2008
Subject: docs/127575: Update to ports (7) as it is missing a few make targets
Message-ID: <200809231402.m8NE2vcA057890@relnor.com>


>Number:         127575
>Category:       docs
>Synopsis:       Update to ports (7) as it is missing a few make targets
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep 23 14:10:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Walter Venable
>Release:        FreeBSD 7.0-RELEASE-p4 amd64
>Organization:
>Environment:
System: FreeBSD relnor.com 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #0: Wed Sep 3 18:20:26 EDT 2008 root@relnor.com:/usr/obj/usr/src/sys/RELNKERN7 amd64

>Description:
I noticed that a few make targets were missing from man 7 ports, so I have added them with this patch.

>How-To-Repeat:
Apply the patch below.  It was generated with "diff -ruN ports.7 ports.7.new":

>Fix:
--- ports.7     2008-09-23 09:56:24.000000000 -0400
+++ ports.7.new 2008-09-23 09:53:30.000000000 -0400
@@ -196,9 +196,12 @@
 .It Cm fetch-recursive-list
 Show list of files that would be retrieved by
 .Cm fetch-recursive .
+.It Cm run-depends-list , build-depends-list
+Print a list of all the compile and run dependencies, and dependencies
+of those dependencies, by port directory.
 .It Cm pretty-print-run-depends-list , pretty-print-build-depends-list
 Print a list of all the compile and run dependencies, and dependencies
-of those dependencies.
+of those dependencies, by port name and version.
 .It Cm missing
 Print a list of missing dependencies to be installed for the port.
 .It Cm clean
@@ -249,6 +252,8 @@
 Like
 .Cm package ,
 but makes a package for each depending port as well.
+.It Cm package-name
+Prints the name with version of the port.
 .It Cm readmes
 Create a port's
 .Pa README.html .


>Release-Note:
>Audit-Trail:
>Unformatted:
From mitya at yandex-team.ru  Wed Sep 24 06:50:02 2008
From: mitya at yandex-team.ru (Dmitry Sivachenko)
Date: Wed Sep 24 06:50:05 2008
Subject: docs/127602: Incomplete information in nsswitch.conf(5)
Message-ID: <200809240630.m8O6UTOt012762@cavia.yandex.ru>


>Number:         127602
>Category:       docs
>Synopsis:       Incomplete information in nsswitch.conf(5)
>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 Sep 24 06:50:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Dmitry Sivachenko
>Release:        FreeBSD 7.1-PRERELEASE i386
>Organization:
Yandex
>Environment:
System: FreeBSD cavia.yandex.ru 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Sep 12 12:35:08 MSD 2008 mitya@cavia.yandex.ru:/usr/obj/usr/src/sys/CAVIA i386


	
>Description:
Looks like netgroup database can be centralized via NIS, but nsswitch.conf(5)
man page does not mention that fact.

Also fix a typo (lack of comma).
>How-To-Repeat:
	
>Fix:


--- nsswitch.conf.5.old	2007-10-19 04:18:19.000000000 +0400
+++ nsswitch.conf.5	2008-09-24 10:24:08.000000000 +0400
@@ -141,9 +141,13 @@
 .Xr getrpcbynumber 3 ,
 .Xr getrpcent 3
 .It proto
-.Xr getprotobyname 3
+.Xr getprotobyname 3 ,
 .Xr getprotobynumber 3 ,
 .Xr getprotoent 3
+.It netgroup
+.Xr getnetgrent 3 ,
+.Xr setnetgrent 3 ,
+.Xr innetgr 3
 .El
 .Ss Status codes
 The following status codes are available:
>Release-Note:
>Audit-Trail:
>Unformatted:
From r.c.ladan at gmail.com  Thu Sep 25 09:03:56 2008
From: r.c.ladan at gmail.com (Rene Ladan)
Date: Thu Sep 25 09:04:08 2008
Subject: Fwd: PERFORCE change 150423 for review
In-Reply-To: <200809250836.m8P8a02v018952@repoman.freebsd.org>
References: <200809250836.m8P8a02v018952@repoman.freebsd.org>
Message-ID: <e890cae60809250139o6c065cb3qa32253f0ee40bac@mail.gmail.com>

FYI,

I noticed this while updating the Dutch translation of the security chapter.

The fix is available in Perforce.

Regards,
Rene

---------- Forwarded message ----------
From: Rene Ladan <rene@freebsd.org>
Date: 2008/9/25
Subject: PERFORCE change 150423 for review
To: Perforce Change Reviews <perforce@freebsd.org>


http://perforce.freebsd.org/chv.cgi?CH=150423

Change 150423 by rene@rene_self on 2008/09/25 08:35:13

       Fix typo (k5destroy -> kdestroy) in chapter 14.8.2 of English version
       Remove reminder in Dutch version

Affected files ...

.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#7
edit
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#4
edit

Differences ...

==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#7
(text+ko) ====

@@ -2277,7 +2277,7 @@
       <para>The ticket can then be revoked when you have
         finished:</para>

-       <screen>&prompt.user; <userinput>k5destroy</userinput></screen>
+       <screen>&prompt.user; <userinput>kdestroy</userinput></screen>
      </sect2>

      <sect2>

==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#4
(text+ko) ====

@@ -2455,7 +2455,6 @@
      <para>Het ticket kan worden ingenomen wanneer u klaar bent:</para>

      <screen>&prompt.user; <userinput>kdestroy</userinput></screen>
-       <!--(rene) in en_US-versie veranderen (k5destroy->kdestroy)-->
    </sect2>

    <sect2>
From remko at elvandar.org  Thu Sep 25 10:00:16 2008
From: remko at elvandar.org (Remko Lodder)
Date: Thu Sep 25 10:00:22 2008
Subject: Fwd: PERFORCE change 150423 for review
In-Reply-To: <e890cae60809250139o6c065cb3qa32253f0ee40bac@mail.gmail.com>
References: <200809250836.m8P8a02v018952@repoman.freebsd.org>
	<e890cae60809250139o6c065cb3qa32253f0ee40bac@mail.gmail.com>
Message-ID: <b099a2dafefc0469d865e6400b64eb1b.squirrel@galain.elvandar.org>


On Thu, September 25, 2008 10:39 am, Rene Ladan wrote:
> FYI,
>
> I noticed this while updating the Dutch translation of the security
> chapter.
>
> The fix is available in Perforce.
>
> Regards,
> Rene
>

Hey,

Already fixed, I noticed the commit in Perforce :)

Cheers
remko

-- 
/"\   Best regards,                      | remko@FreeBSD.org
\ /   Remko Lodder                       | remko@EFnet
 X    http://www.evilcoder.org/          |
/ \   ASCII Ribbon Campaign              | Against HTML Mail and News


From mrsgracesanders101 at live.com  Fri Sep 26 04:56:42 2008
From: mrsgracesanders101 at live.com (YAHOO AWARD CENTER)
Date: Fri Sep 26 04:56:48 2008
Subject: YOU ARE A WINNER OF YAHOO AWARD GRANTS JULY 2008
Message-ID: <20080925093901.32676.qmail@server1.wangsolutions.com>


Yahoo & Window Live Awards Centre
124 Stockport Road, Longsight,
Manchester M60 2DB - United 
KingdomTel:+447031925532.
 
 
This is to inform you that you have won a prize money of Three million,Two Hundred Thousand  Great Britain Pounds (GBP 3,200,000.00) for the month of July, 2008 Prize   promotion which is organized by YAHOO A WARDS  & WINDOWS LIVE.

YAHOO collects all the email addresses of the people that are active online, among the millions that subscribed to Yahoo and Hotmail and few from other e-mail providers. Six people are selected monthly to benefit from this promotion and you are one of the Selected Winners which your e-mail address won the Jackpot Prize while other five winners won One Million Great Britain Pounds(GBP 1,000,000.00) each.

                                                    PAYMENT OF PRIZE / CLAIMS
 
Winners shall be paid in accordance with their Settlement Centers. Yahoo Prize Award must be claimed not later than 10 days from date of Draw Notification. Any prize not claimed within this period will be forfeited and returned to its source as unclaimed.
 
Stated below are your identification numbers:
 
BATCH NUMBER:            MFI/06/APA-43658
REFERENCE NUMBER:    2007234522
PIN:                                 1207
You are requested to contact our Assistant co-ordinator in Manchester and send your winning identification numbers to him:
 
 
Co-ordinator's Name:  Rev Fr. Niculai Anton
E-Mail:awardcenter44@yahoo.co.th 
Tel:+447031925532
 
You are advised to send the following information to our co-ordinator to facilitate the release of of your fund to you.
 
1. Full name..............................................
2. Country.................................................
3. Contact Address................................
4. Telephone Number............................
5. fax Number..........................................
5. Marital Status.....................................
6. Occupation..........................................
7. Sex.........................................................
8. Date of Birth/Age ...............................
9. Identity card(carte identite).............
 
Congratulations!! once again.
Yours in service,
                
  
Mrs. Grace Sanders(Awards coordinator)
-------------------------------------------------------------------------------------------------------------------------------------------------
WARNING!
You must keep strict confidentiality of your Prize Award claims to yourself until your money is successfully handed over to you to avoid disqualification that may arise from double claims.
Yahoo Awards Team shall not be held liable for any loss of funds arising from the above mentioned.



From trhodes at FreeBSD.org  Sun Sep 28 13:13:52 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Sun Sep 28 13:14:04 2008
Subject: cvs commit: doc/en_US.ISO8859-1/books/handbook Makefile
 book.sgml chapters.ent
In-Reply-To: <200809281254.m8SCsE38033076@repoman.freebsd.org>
References: <200809281254.m8SCsE38033076@repoman.freebsd.org>
Message-ID: <20080928091333.14034cc2.trhodes@FreeBSD.org>

On Sun, 28 Sep 2008 12:54:12 +0000 (UTC)
Tom Rhodes <trhodes@FreeBSD.org> wrote:

> trhodes     2008-09-28 12:54:12 UTC
> 
>   FreeBSD doc repository
> 
>   Modified files:
>     en_US.ISO8859-1/books/handbook Makefile book.sgml chapters.ent 
>   Log:
>   Add the DTrace, file systems, and Updating chapters to the build.  They
>   need a bit more fleshing out, but there is no reason why they should
>   remain local patches anymore.
>   
>   Reviewed by:    remko, pgj, manolis, keramida
>   
>   Revision  Changes    Path
>   1.110     +3 -0      doc/en_US.ISO8859-1/books/handbook/Makefile
>   1.173     +6 -0      doc/en_US.ISO8859-1/books/handbook/book.sgml
>   1.38      +3 -0      doc/en_US.ISO8859-1/books/handbook/chapters.ent
> 

Though not reviewed by John and Pawel, they're both busy and
I'm cool with that, everything documented was tested and it
works fine.  Thanks to all my reviewers of course.  :P

-- 
Tom Rhodes
From trhodes at FreeBSD.org  Sun Sep 28 13:28:01 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Sun Sep 28 13:28:12 2008
Subject: cvs commit: doc/en_US.ISO8859-1/books/handbook Makefile
 book.sgml chapters.ent
In-Reply-To: <200809281254.m8SCsE38033076@repoman.freebsd.org>
References: <200809281254.m8SCsE38033076@repoman.freebsd.org>
Message-ID: <20080928090329.0e44569a.trhodes@FreeBSD.org>

On Sun, 28 Sep 2008 12:54:12 +0000 (UTC)
Tom Rhodes <trhodes@FreeBSD.org> wrote:

> trhodes     2008-09-28 12:54:12 UTC
> 
>   FreeBSD doc repository
> 
>   Modified files:
>     en_US.ISO8859-1/books/handbook Makefile book.sgml chapters.ent 
>   Log:
>   Add the DTrace, file systems, and Updating chapters to the build.  They
>   need a bit more fleshing out, but there is no reason why they should
>   remain local patches anymore.
>   
>   Reviewed by:    remko, pgj, manolis, keramida
>   
>   Revision  Changes    Path
>   1.110     +3 -0      doc/en_US.ISO8859-1/books/handbook/Makefile
>   1.173     +6 -0      doc/en_US.ISO8859-1/books/handbook/book.sgml
>   1.38      +3 -0      doc/en_US.ISO8859-1/books/handbook/chapters.ent
> 

Though not reviewed by John and Pawel, they're both busy and
I'm cool with that, everything documented was tested and it
works fine.  Thanks to all my reviewers of course.  :P

-- 
Tom Rhodes
From pluknet at gmail.com  Sun Sep 28 14:38:06 2008
From: pluknet at gmail.com (pluknet)
Date: Sun Sep 28 14:38:13 2008
Subject: doc/share/sgml/man-refs.ent lacks of iwn(4)
Message-ID: <a31046fc0809280705y1d17524uedd5103b3ab13e2b@mail.gmail.com>

As Intel 4965 wireless driver manpage iwn(4) has been committed in
-current in April 2008,
can someone add the appropriate entry in man-refs.ent ?

Thanks,
pluknet
From eitanadlerlist at gmail.com  Sun Sep 28 15:32:57 2008
From: eitanadlerlist at gmail.com (Eitan Adler)
Date: Sun Sep 28 15:33:04 2008
Subject: csup man page
Message-ID: <48DF9D14.7030007@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Csup does not fail with "-g". This should be documented as a
compatibility feature.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjfnRQACgkQtl8kq+nCzNGuKwCfZUH5DQS/8KRoh9P1TFRVzMbO
TAgAn0Foj+uU0XWFMj1CMFJZUYJR8uo+
=m93R
-----END PGP SIGNATURE-----
From danger at FreeBSD.org  Sun Sep 28 19:28:54 2008
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Sun Sep 28 19:29:24 2008
Subject: doc/share/sgml/man-refs.ent lacks of iwn(4)
In-Reply-To: <a31046fc0809280705y1d17524uedd5103b3ab13e2b@mail.gmail.com>
References: <a31046fc0809280705y1d17524uedd5103b3ab13e2b@mail.gmail.com>
Message-ID: <1381304720.20080928210952@rulez.sk>

Hello pluknet,

Sunday, September 28, 2008, 4:05:52 PM, you wrote:

> As Intel 4965 wireless driver manpage iwn(4) has been committed in
> -current in April 2008,
> can someone add the appropriate entry in man-refs.ent ?

I have added it there as per your request.

-- 
Best regards,
 Daniel                            mailto:danger@FreeBSD.org

From eitanadlerlist at gmail.com  Sun Sep 28 19:43:21 2008
From: eitanadlerlist at gmail.com (Eitan Adler)
Date: Sun Sep 28 19:43:28 2008
Subject: csup man page
In-Reply-To: <48DF9D14.7030007@gmail.com>
References: <48DF9D14.7030007@gmail.com>
Message-ID: <48DFDE43.30702@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Csup does not fail with "-g". This should be documented as a
compatibility feature.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjf3kMACgkQtl8kq+nCzNFv6QCghdoKhURLupeqfFQmpsepE3Lw
RYsAoIjLjHlIuHUv55C5q+SxBodzBT7J
=9lDs
-----END PGP SIGNATURE-----
From miggyx at peteslan.net  Sun Sep 28 20:15:48 2008
From: miggyx at peteslan.net (Peter Membrey)
Date: Sun Sep 28 20:15:54 2008
Subject: Contributing documentation
Message-ID: <bca11b1e0809281243y7586c3a4jdb0d0dd760d474d7@mail.gmail.com>

Hi guys,

I'd like to contribute some towards completing some of the items on
the to-do list but I'm not really sure how to get started.

Can someone point me in the right direction? :)

Cheers

Pete
From murray at stokely.org  Sun Sep 28 21:35:00 2008
From: murray at stokely.org (Murray Stokely)
Date: Sun Sep 28 21:35:07 2008
Subject: Contributing documentation
In-Reply-To: <bca11b1e0809281243y7586c3a4jdb0d0dd760d474d7@mail.gmail.com>
References: <bca11b1e0809281243y7586c3a4jdb0d0dd760d474d7@mail.gmail.com>
Message-ID: <2a7894eb0809281407s3862311ftbbb9945d52ea6e3b@mail.gmail.com>

Hi Peter, start with the FreeBSD Doc Project Primer, here :

http://www.freebsd.org/doc/en/books/fdp-primer/

You can then check out the source copy of man pages, freebsd articles
or books from CVS and start sending patches to improve them to this
list.

       - Murray


On Sun, Sep 28, 2008 at 12:43 PM, Peter Membrey <miggyx@peteslan.net> wrote:
> Hi guys,
>
> I'd like to contribute some towards completing some of the items on
> the to-do list but I'm not really sure how to get started.
>
> Can someone point me in the right direction? :)
>
> Cheers
>
> Pete
> _______________________________________________
> 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"
>
From marketing at desm.gr  Mon Sep 29 02:25:41 2008
From: marketing at desm.gr (DESM S.A.)
Date: Mon Sep 29 02:25:53 2008
Subject: Desm S.A. Newsletter No74
Message-ID: <CEB41E10.1C921F3@NICK>

This message is in MIME format. Since your mail reader does not understand =
this format, some or all of this message may not be legible.From bugmaster at FreeBSD.org  Mon Sep 29 11:06:06 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep 29 11:06:43 2008
Subject: Current unassigned doc problem reports
Message-ID: <200809291106.m8TB65fS039847@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/127602  doc        [patch] Incomplete information in nsswitch.conf(5)
o docs/127575  doc        [patch] Update to ports (7) as it is missing a few mak
o docs/127406  doc        [patch] update umodem man page: Sony Ericsson W810i
o docs/127220  doc        [patch] err(3) suggests using exit values from sysexit
o docs/127219  doc        [patch] style(9) is inconsistent regarding usage of sy
o docs/126934  doc        missing 'crit' in usr.sbin/syslogd/syslog.conf.5
o docs/126921  doc        [patch] History section of cpuset(1) incorrect
o docs/126590  doc        [patch] Write routine called forever in Sample Echo Ps
o docs/126487  doc        fix language on atol(3) manpage
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/126445  doc        discussion on WEP settings in wpa_supplicant.conf(5) m
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/123400  doc        gvinum startup in handbook
o docs/123035  doc        [patch] bugs in refuse.README
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o 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 docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121197  doc        [patch] edits to books/porters-handbook
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/120628  doc        PAE documentation errror in handbook
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/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/119907  doc        Ports compatibility
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
a docs/119536  doc        a few typos in French handbook (basics)
s docs/119404  doc        [request] events page should list only last 2 years wo
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
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/117798  doc        formatting oddity in sysmouse(4)
o docs/117747  doc        'break' system call needs a man page
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
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/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/115921  doc        Booting from pst(4) is not supported
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/112481  doc        bug in ppp.linkup example
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/111263  doc        [request] Information on $EDITOR variable in section 3
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/109983  doc        No manual entry for protoize
o docs/109981  doc        No manual entry for post-grohtml
o docs/109977  doc        No manual entry for ksu
o docs/109975  doc        No manual entry for elf2aout
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
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
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/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
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/104403  doc        man security should mention that the usage of the X Wi
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
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/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85100   doc        NOTES: ICH audio device support statement is ambiguous
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/84806   doc        mdoc(7) manpage has section ordering problems
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84538   doc        [patch] sk(4) driver supports Marvell 88E800x chip too
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
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/47818   doc        [patch] ln(1) manpage is confusing
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
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
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 (<olink>)
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 <emphasis> tags in the sourc

155 problems total.

From newsletter at email.pctools.com  Tue Sep 30 06:59:41 2008
From: newsletter at email.pctools.com (PC Tools Newsletter)
Date: Tue Sep 30 06:59:48 2008
Subject: Don't be scared of scams!
Message-ID: <48E1CE5C.00000569@omp.email.pctools.com>


Can't see the pictures? Select "Always display images" or view this 
message in your browser 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VS
 
. 

PC Tools 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VT
 

https://email.pctools.com/servlet/ff/c?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VgVUUUWYA 

Take Malware Head On 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VU
 

Rogueware and ransomware are all types of online ?scams? designed to 
trick you into downloading and installing malware. Socially engineered 
scams have become a significant force to contend with - often blurring 
the line of what is legitimate and illegitimate software. PC Tools? 
newly released Internet Security 2009 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VW
 
will offer you integrated protection that will provide you with both 
email and web security. 

Read more 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VY
 
about how these online scams are tricking their way onto your computer 

Tips & Tricks 

Tips for avoiding scams & staying safe online: 

1. 

Ensure your e-mail scanning feature is ON by default, this ensures 
that all emails received with attachments are scanned for malware as 
soon as they hit your inbox. 

2. 

Always keep your security software up to date. Smart Update: is an 
automatic and silent self-updating feature found in Spyware Doctor, PC 
Tools AntiVirus and PC Tools Internet Security that keeps your 
protection up to date at all times. 

3. 

Install only trusted software from known and reputable vendors such as 
PC Tools. 

4. 

Use different passwords, particularly when transacting online. Ensure 
your password includes a combination of letters, numbers and 
upper/lower case. 

5. 

Use a separate credit card for online transactions that has a low 
credit limit. 

Purchase Internet Security 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VA
 
today! 

Top Threats 

Below are some of the latest threats identified by PC Tools 

Adware.AdMedia 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VB
 

Exploit.MSWord 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VC
 

Trojan-Spy.Pophot.WX 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VD
 

Trojan.FakeAlert 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSR
 

Trojan.KillAV.A 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSS
 

The above infections can be detected and cleaned using 
PC Tools Internet Security 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VST
 
and Spyware Doctor with AntiVirus 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSU
 
! 

News 

PC World's Registry Mechanic 8 Review 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSW
 

The Wall Street Journal recommends Spyware Doctor 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSY
 

Tech Spotlight: Internet Security 2009 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSA
 

Pocket Lint's Spyware Doctor review 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSB
 

SECURE & PROTECT REPAIR & OPTIMIZE Spyware Doctor with AntiVirus Registry Mechanic PC Tools Internet Security Desktop Maestro 

This message was intended for 'doc@freebsd.org' 
You have received this message because you are subscribed to 'PC Tools 
newsletter and special promotions'. 

Update your subscriptions 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSCVLuHptVKhJxMjLLIkKQhjn
 
| 

Unsubscribe 

https://email.pctools.com/servlet/cc6?iJltkQTBTQSVKhJxMjLLIkKQhjnV2VSDVLuHptVKhJxMjLLIkKQhjn
 

| To contact us please email reply-newsletter@email.pctools.com 
mailto:reply-newsletter@email.pctools.com 

mailto:reply-newsletter@email.pctools.com 

PC Tools Limited
Units A & B, Block 4, Shannon Business Park, Shannon, Co. Clare, Ireland.
Copyright ? 2008 PC Tools. All rights reserved.
 

mailto:reply-newsletter@email.pctools.com