Current unassigned doc problem reports
(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/186614 docUpdate htdocs/features.html to include 10.x o docs/186608 doctypo in 'ctime(3) man page o docs/186537 doc[patch] removing obsolete vnode (9) man page reference o docs/186464 docOnline-Documentation for carp(4) is outdated p docs/186191 docTypo in bhyveload.8 o docs/185764 docmention of libiconv in FreeBSD 10.0 release note o docs/185531 docetherswitchcfg(8) refers to etherswitch(4) which does o docs/185481 docsh/bash Parameter Expansion +/- syntax not documented o docs/185422 doc[handbook] brazilian portuguese translation to "Append o docs/185421 doc[handbook] brazilian portuguese translation to "Append o docs/185392 doc[handbook] brazilian portuguese translation to "The Fr o docs/185391 doc[handbook] brazilian portuguese translation to "GEOM: o docs/185353 docs nc(1) does not exit after transfer (should be document o docs/185281 doc[handbook] brazilian portuguese translation to "Jails" o docs/185280 doc[handbook] brazilian portuguese translation to "Introd o docs/184758 docerror in rtadvd.conf example o docs/184755 docThe vmstat(8) manualpage synopsis doesn't show all opt o docs/184482 docpasswd (1) man page incorrect info about login.conf o docs/184459 docDocumentation Bug in the man Page for the who Command o docs/184110 docblackhole(4) manpage doesn`t describe net.inet.sctp.b o docs/184051 docUpdate configuration example for staging o docs/184048 docdevelopers handbook, 10.7 Debugging Deadlocks - must i o docs/184046 docbhyve(4) manpage references non-existant manpages bhyv o docs/184029 docDescription of /usr/tests is missing in hier(7) o docs/183927 docmissing info about kernel toolchain in kernel building o docs/183653 doc[patch] Add some more *BSD releases to the groff_mdoc o docs/183427 docOnline man pages don't include latest release + ports o docs/18 docMisnamed constant in bpf(4) o docs/183246 docFreeBSD 8.4-RELEASE Installation Instructions don't pr o docs/183024 doctextdump(4) mentions call doadump, should be textdump o docs/183002 docFix instructions in "6.5.3. Anti-Aliased Fonts" regard o docs/182876 docCURRENT release notes webpage out of date and inconsis o docs/182218 docAdd an ipfilter rc.conf option in handbook for IPv6 o docs/182202 docHandbook pkgng description doesn't mention there are n o docs/181845 docVirtualbox Host Setup needs acd0 in /etc/devfs.conf, a o docs/181844 docFreeBSD Handbook Virtualbox Host Section missing confi o docs/181808 docChapter 15.15 (Resource Limits) misses important infor o docs/181785 doc[patch] Man page for tmpfile() is inconsistent o docs/181390 docseq(1) first appeared in 8th UNIX o docs/181376 docCLOCK_THREAD_CPUTIME_ID is not documented in clock_get o docs/181280 docsuggestion: split zfs man page in a zfs- way o docs/181134 docFix example for boot0cfg utility o docs/180970 doc[request] No manpage for ps_strings o docs/180767 doc[patch] printf.3: fix off-by-one in snprintf descripti o docs/180493 doc[handbook] Single-user mode console confusion o docs/180332 docSSD Kernel Instructions Out of Date: options MFS throw o docs/180331 docSSD Kernel Instructions Out of Date: options MD_ROOT a o docs/180330 docSSD Kernel Instructions Out of Date: pseudo-device no o docs/180027 docMissing man page entries for callout_reset_sbt in time o docs/179988 doc[faq] [patch] ThwackAFAQ - sandbox p docs/179914 docremove inactive user dougb from mergemaster maintainer o docs/179697 docHandbook incomplete WRT Opera flash usage (linproc) o docs/179497 doc[patch] service.8 add csh completion example o docs/179246 doc[patch] gnome porting updates o docs/178818 docgmirror(8) says to use rc.early which is no longer ava o docs/178730 docmove roff papers out of src into doc o docs/178286 doc[PATCH] document the LOCAL_* vars in build(7) o docs/178221 docAddition to handbook jails chapter: warning about make o www/178190 docmyths web page should be updated o docs/178119 doc[ports] Porter's handbook lacks examples for using Opt o docs/177968 docbpf(4): documentation of BIOCROTZBUF is incomple
docs/186625: Handbook rebuilding "world" upgrade procedure wrong mergemaster command
>Number: 186625 >Category: docs >Synopsis: Handbook rebuilding "world" upgrade procedure wrong >mergemaster command >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 Feb 10 11:30:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Wout Decré >Release: >Organization: Canodus >Environment: >Description: Under Procedure 23.2. Overview of Build World Process, step 9: Update any remaining configuration files. # mergemaster -p It suggests you should do the mergemaster command two times with the -p option. Before r43796, this was: # mergemaster >How-To-Repeat: Check http://www.freebsd.org/doc/handbook/makeworld.html >Fix: I think this should just be: # mergemaster >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/185353: nc(1) does not exit after transfer (should be documented)
On 2014-01-05 19:08, lini...@freebsd.org wrote: > Old Synopsis: nc does not exit after transfer > New Synopsis: nc(1) does not exit after transfer (should be documented) > > Responsible-Changed-From-To: freebsd-amd64->freebsd-docs > Responsible-Changed-By: linimon > Responsible-Changed-When: Mon Jan 6 00:07:44 UTC 2014 > Responsible-Changed-Why: > reclassify. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=185353 > ___ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org" > I have sent in a patch upstream to resolve this issue. Once it is committed we can import the updated version of netcat and gain the documentation fix. It is a 1 line diff to the man page, so I've attached a diff against our tree as well, for reference. -- Allan Jude Index: contrib/netcat/nc.1 === --- contrib/netcat/nc.1 (revision 261716) +++ contrib/netcat/nc.1 (working copy) @@ -365,7 +365,7 @@ .Nm process, feeding it the file which is to be transferred: .Pp -.Dl $ nc host.example.com 1234 \*(Lt filename.in +.Dl $ nc -N host.example.com 1234 \*(Lt filename.in .Pp After the file has been transferred, the connection will close automatically. .Sh TALKING TO SERVERS signature.asc Description: OpenPGP digital signature
Re: docs/185353: nc(1) does not exit after transfer (should be documented)
The following reply was made to PR docs/185353; it has been noted by GNATS. From: Allan Jude To: bug-follo...@freebsd.org, r...@robert-eckardt.de Cc: Subject: Re: docs/185353: nc(1) does not exit after transfer (should be documented) Date: Mon, 10 Feb 2014 11:28:30 -0500 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XT7BEsPaqPf8iu4tkvRjj0IVfVVkg2Kte Content-Type: multipart/mixed; boundary="01090605010700040805" This is a multi-part message in MIME format. --01090605010700040805 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have sent in a patch upstream to resolve this issue. Once it is committed we can import the updated version of netcat and gain the documentation fix. It is a 1 line diff to the man page, so I've attached a diff against our tree as well, for reference. --=20 Allan Jude --01090605010700040805 Content-Type: text/plain; charset=windows-1252; name="contrib_netcat.nc.1.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="contrib_netcat.nc.1.diff" Index: contrib/netcat/nc.1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- contrib/netcat/nc.1(revision 261716) +++ contrib/netcat/nc.1(working copy) @@ -365,7 +365,7 @@ .Nm process, feeding it the file which is to be transferred: .Pp -.Dl $ nc host.example.com 1234 \*(Lt filename.in +.Dl $ nc -N host.example.com 1234 \*(Lt filename.in .Pp After the file has been transferred, the connection will close automatic= ally. .Sh TALKING TO SERVERS --01090605010700040805-- --XT7BEsPaqPf8iu4tkvRjj0IVfVVkg2Kte Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJS+P4uAAoJEJrBFpNRJZKfxmIP/3OozGxuoBulAb7w4lkyyUy9 w+mjCk3prdvZ5ofAdx/UYVuHiw8NMj9MAY2FlAY4OXn+rZO/E0UQTcBy8j5oCSjP Ccc0sdt9jfp4itLOyzC8Kc0uU/eKM1FOFJSh5gv8uTAu8aZJ7Ep93R79k90BIHAQ j9XbBByEsapARfMWUb1GLtpAkbTPtkUHhsxzzWpm7B8Asu2E3Y7+bGz6cYDavRHO iB84kwhnEdAyJfImDbHYjq4+uL1vCwPo+yNFSf2x9oROFGiGOqxdjxQYkmis0yBE UR3CnBLSz6CfInMaCUKS1dW6LkioOU0TMVJSUnZxXBiYu3AvNYWmk6UReN88PSCa 8zlyGJ6mOELI4HnjcSMcJMzg8cjK+QUU6k/hVbphB7Lk3YkrHU4akW99ma2xVPjd 6q3xjxIDBX/Hmfh8dRzR4otX/3jWZv6DewfyHz26oPeuCje5eHgLVci0EkXrL/A6 NOK98HVLwVbXL9XDT2tbbfHJ+a4vQYLIN11BZRvnm6vn8anfWhNnmvCCjNKWwlS5 UlCjHs0h6/aOc5Zd8U3h9RJjciCc2zIpHfq7dT8x0efmGyQbcEMCSJ7sIlC+0E8I Yw75rTZWo0zOmpn/yEICcZw2NR3g3Gi9q/S7QGg3S6mOXno8e/paoiyennmhNHsq OaVJB1WZUnrMD4wjfcVj =Ecvw -END PGP SIGNATURE- --XT7BEsPaqPf8iu4tkvRjj0IVfVVkg2Kte-- ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/186608: typo in 'ctime(3) man page
On Sun, 9 Feb 2014, Jamie Landeg-Jones wrote: Description: Another typo. This time in ctime.3 man page.. I realise this is in 'contrib' but there doesn't seem to be any info regarding who this is pulled from. I think that the current ~upstream for the tzcode is supposed to be https://github.com/eggert/tz/ , but I haven't checked particularly recently. (There was some excitement involving a legal action, etc., so it had gone away and/or moved.) That said, I don't see a BUGS section at all in the newctime.3 in that repo, and I also don't see the erroneous line you quote in the history of that repo, so ... I'm not sure what happened. I hope I don't get the reputation for most anal contributor :-( Definitely not! (Is a PR the best way to report something so insignificant? Seems like overkill... Gimme doc commit access!) PR is fine, it gives us a place to look when we need to find things. Anyway The word 'leaves' instead of 'leave' in the following line: "-these functions leaves their result in an internal static object and return" Thanks for pointing it out. I'll try to think about what the best route to a fix is. -Ben ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/186608: typo in 'ctime(3) man page
The following reply was made to PR docs/186608; it has been noted by GNATS. From: Benjamin Kaduk To: Jamie Landeg-Jones Cc: freebsd-gnats-sub...@freebsd.org, freebsd-doc@freebsd.org Subject: Re: docs/186608: typo in 'ctime(3) man page Date: Mon, 10 Feb 2014 14:54:16 -0500 (EST) On Sun, 9 Feb 2014, Jamie Landeg-Jones wrote: > >> Description: > > Another typo. This time in ctime.3 man page.. I realise this is in > 'contrib' but there doesn't seem to be any info regarding who this is > pulled from. I think that the current ~upstream for the tzcode is supposed to be https://github.com/eggert/tz/ , but I haven't checked particularly recently. (There was some excitement involving a legal action, etc., so it had gone away and/or moved.) That said, I don't see a BUGS section at all in the newctime.3 in that repo, and I also don't see the erroneous line you quote in the history of that repo, so ... I'm not sure what happened. > I hope I don't get the reputation for most anal contributor :-( Definitely not! > (Is a PR the best way to report something so insignificant? Seems like > overkill... Gimme doc commit access!) PR is fine, it gives us a place to look when we need to find things. > Anyway The word 'leaves' instead of 'leave' in the following line: > > "-these functions leaves their result in an internal static object and > return" Thanks for pointing it out. I'll try to think about what the best route to a fix is. -Ben ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/185353: nc(1) does not exit after transfer (should be documented)
The following reply was made to PR docs/185353; it has been noted by GNATS. From: Allan Jude To: bug-follo...@freebsd.org, r...@robert-eckardt.de, delp...@freebsd.org Cc: Subject: Re: docs/185353: nc(1) does not exit after transfer (should be documented) Date: Mon, 10 Feb 2014 15:04:09 -0500 The fix has been committed to OpenBSD. http://marc.info/?l=openbsd-cvs&m=139206012706972&w=2 There have been a few other updates to netcat in the mean time, although they are to do with FD passing, which I suspect is an OpenBSD only feature. Hopefully Xin Li or someone else can MFV and pull in the fix for the man page. -- Allan Jude ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: [PATCH] Publish the project's software license policy
On Fri, Feb 07, 2014 at 03:23:58PM -0500, John Baldwin wrote: > A few years ago the core team approved a software license policy for the > project and announced it on developers@; however, it was never published on > the website. The patch below aims to remedy that. Can someone review the > XML > to make sure it is correct? It at least builds ok for me locally. > > http://people.freebsd.org/~jhb/patches/license_policy.patch > Looks good to me. Glen pgpKgeTBwHv75.pgp Description: PGP signature
Re: Possible typo on doc/handbook/ports-using.html ?
> On Feb 9, 2014, at 4:49 PM, Lampros Chaidas wrote: > > Hi there, > > I was just reading through the documentation for getting the ports collection > with the subversion method and noticed the following in "Procedure 5.2. > Subversion Method" - the link is > http://www.freebsd.org/doc/handbook/ports-using.html > > "If the ports tree is not available, Subversion can be installed as > a package: > # pkg install subversion > If pkgng is being used to manage packages, Subversion can be > installed with it instead: > # pkg install subversion" > > It looks like it's the same command in both situations - this looks redundant > to me, is there a difference here that maybe I'm missing? > > Thanks, > - Lampros Both statements are true, however I believe this can be reworded and condensed. I'll put together a patch. - jgh ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Possible typo on doc/handbook/ports-using.html ?
On Mon, Feb 10, 2014 at 08:54:49PM -0800, Jason Helfman wrote: > > > On Feb 9, 2014, at 4:49 PM, Lampros Chaidas wrote: > > > > Hi there, > > > > I was just reading through the documentation for getting the ports > > collection with the subversion method and noticed the following in > > "Procedure 5.2. Subversion Method" - the link is > > http://www.freebsd.org/doc/handbook/ports-using.html > > > > "If the ports tree is not available, Subversion can be installed as > > a package: > > # pkg install subversion > > If pkgng is being used to manage packages, Subversion can be > > installed with it instead: > > # pkg install subversion" > > > > It looks like it's the same command in both situations - this looks > > redundant to me, is there a difference here that maybe I'm missing? > > > > Thanks, > > - Lampros > > Both statements are true, however I believe this can be reworded and > condensed. > > I'll put together a patch. That was introduced in [1] as an attempt to clear texts from mentioning our old package management system (aka pkg_install). 1. http://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/books/handbook/ports/chapter.xml?r1=43693&r2=43747 -- WBR, Taras Korenko ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
