<filename>sysctl.conf</filename>
--- handbook.config.chapter.syslog.sgml.diff ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
From bcr at FreeBSD.org Thu May 24 16:49:38 2012
From: bcr at FreeBSD.org (bcr at FreeBSD.org)
Date: Thu, 24 May 2012 16:49:37 GMT
Subject: docs/168305: [PATCH] rewrite of the syslogd and newsyslogd
parts of the config chapter of the handbook
Message-ID: <201205241649.q4OGnbAF026093@freefall.freebsd.org>
Synopsis: [PATCH] rewrite of the syslogd and newsyslogd parts of the config chapter of the handbook
Responsible-Changed-From-To: freebsd-doc->I'll work on this one.
Responsible-Changed-By: bcr
Responsible-Changed-When: Thu May 24 16:49:05 UTC 2012
Responsible-Changed-Why:
http://www.freebsd.org/cgi/query-pr.cgi?pr=168305
From jgh at FreeBSD.org Thu May 24 19:40:07 2012
From: jgh at FreeBSD.org (Jason Helfman)
Date: Thu, 24 May 2012 19:37:35 GMT
Subject: docs/168316: www/java: update news for build25 for openjdk
Message-ID: <201205241937.q4OJbZbA049387@freefall.freebsd.org>
>Number: 168316
>Category: docs
>Synopsis: www/java: update news for build25 for openjdk
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu May 24 19:40:06 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Jason Helfman
>Release: FreeBSD 9.0-STABLE i386
>Organization:
>Environment:
System: FreeBSD freefall.freebsd.org 9.0-STABLE FreeBSD 9.0-STABLE #6 r235139: Tue May 8 21:19:03 UTC 2012 simon at freefall.freebsd.org:/usr/obj/usr/src/sys/FREEFALL i386
>Description:
Add news link for openjdk6 update for build25
>How-To-Repeat:
>Fix:
Index: en/java/dists/16.sgml
===================================================================
--- en/java/dists/16.sgml (revision 38879)
+++ en/java/dists/16.sgml (working copy)
@@ -12,6 +12,12 @@
|
+May 09, 2012: Greg
+Lewis updates the &openjdk; 6 port
+to Build 25.
+
+
+
November 30, 2011: Jung-uk
Kim updates the &openjdk; 6 port
to Build 24.
Index: en/java/news.xml
===================================================================
--- en/java/news.xml (revision 38879)
+++ en/java/news.xml (working copy)
@@ -25,6 +25,28 @@
+ 2012
+
+
+ May
+
+
+ 09
+
+
+ <a href="http://openjdk.java.net/">&openjdk;</a> 6 updated
+ to Build 24.
+
+ Greg Lewis updates
+ the &openjdk; 6 port to
+ Build 25. See the JDK 1.6.x page
+ for more details.
+
+
+
+
+
+
2011
>Release-Note:
>Audit-Trail:
>Unformatted:
From gjb at FreeBSD.org Thu May 24 19:46:03 2012
From: gjb at FreeBSD.org (gjb at FreeBSD.org)
Date: Thu, 24 May 2012 19:46:02 GMT
Subject: docs/168316: www/java: update news for build25 for openjdk
Message-ID: <201205241946.q4OJk2cd067335@freefall.freebsd.org>
Synopsis: www/java: update news for build25 for openjdk
Class-Changed-From-To: sw-bug->doc-bug
Class-Changed-By: gjb
Class-Changed-When: Thu May 24 19:45:29 UTC 2012
Class-Changed-Why:
Reclassify.
Responsible-Changed-From-To: freebsd-doc->gjb
Responsible-Changed-By: gjb
Responsible-Changed-When: Thu May 24 19:45:29 UTC 2012
Responsible-Changed-Why:
I'll take it.
http://www.freebsd.org/cgi/query-pr.cgi?pr=168316
From utisoft at gmail.com Sat May 26 20:13:42 2012
From: utisoft at gmail.com (Chris Rees)
Date: Sat, 26 May 2012 21:13:10 +0100
Subject: New docs for OPTIONS
Message-ID:
Hi all,
We have a new world order for OPTIONS in ports (exciting, isn't it??),
and would very much like to document it.
I've prepared the following patch which has had fairly extensive
review, apart from not having a formal approval by a docs person.
Would anyone mind giving it a check and approving it please? Bapt
plans to commit the code later this week, and it'd be great to have
approval by then!
Thanks,
Chris
http://www.bayofrum.net/~crees/patches/optionsng-docs-patch.diff
http://www.bayofrum.net/~crees/rendered/porters-optionsng.html
From gjb at FreeBSD.org Sat May 26 21:04:36 2012
From: gjb at FreeBSD.org (Glen Barber)
Date: Sat, 26 May 2012 17:04:32 -0400
Subject: New docs for OPTIONS
In-Reply-To:
References:
Message-ID: <20120526210354.GC1369@glenbarber.us>
Hi Chris,
On Sat, May 26, 2012 at 09:13:10PM +0100, Chris Rees wrote:
> Would anyone mind giving it a check and approving it please? Bapt
> plans to commit the code later this week, and it'd be great to have
> approval by then!
>
I think this looks good.
If there are no objections from anyone on docs@ to your patch, please
commit it with my approval after bapt commits his changes.
Glen
From wblock at wonkity.com Sun May 27 16:02:03 2012
From: wblock at wonkity.com (Warren Block)
Date: Sun, 27 May 2012 10:02:01 -0600 (MDT)
Subject: New docs for OPTIONS
In-Reply-To:
References:
Message-ID:
On Sat, 26 May 2012, Chris Rees wrote:
> We have a new world order for OPTIONS in ports (exciting, isn't it??),
> and would very much like to document it.
>
> I've prepared the following patch which has had fairly extensive
> review, apart from not having a formal approval by a docs person.
>
> Would anyone mind giving it a check and approving it please? Bapt
> plans to commit the code later this week, and it'd be great to have
> approval by then!
>
> Thanks,
>
> Chris
>
>
> http://www.bayofrum.net/~crees/patches/optionsng-docs-patch.diff
>
> http://www.bayofrum.net/~crees/rendered/porters-optionsng.html
Attached is a full patch that builds on that. Some simplifications and
clarifications, and an added tip on helpful descriptions.
-------------- next part --------------
Index: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml
===================================================================
--- doc/en_US.ISO8859-1/books/porters-handbook/book.sgml (revision 38891)
+++ doc/en_US.ISO8859-1/books/porters-handbook/book.sgml (working copy)
@@ -3663,19 +3663,17 @@
<makevar>USE_<replaceable>*</replaceable></makevar>
- A number of variables exist in order to encapsulate
- common dependencies that many ports have. Although their
- use is optional, they can help to reduce the verbosity of
+ Several variables exist to define
+ common dependencies shared by many ports. Their
+ use is optional, but helps to reduce the verbosity of
the port Makefiles. Each of them is
styled as
- USE_*. The
- usage of these variables is restricted to the port
+ USE_*.
+ These variables may be used only in the port
Makefiles and
- ports/Mk/bsd.*.mk and is not designed
- to encapsulate user-settable options — use
- WITH_* and
- WITHOUT_* for
- that purpose.
+ ports/Mk/bsd.*.mk. They are not meant
+ for user-settable options — use
+ PORT_OPTIONS for that purpose.
It is always incorrect to set any
@@ -3880,11 +3878,12 @@
Correct Declaration of an Optional Dependency
- OPTIONS= BAR "Enable bar support" off
+ OPTIONS_DEFINE= BAR
+BAR_DESC= Enable bar support
-.include <bsd.port.pre.mk>
+.include <bsd.port.options.mk>
-.if defined(WITH_BAR) && !defined(WITHOUT_BAR)
+.if ${PORTOPTIONS:MBAR}
LIB_DEPENDS= bar:${PORTSDIR}/foo/bar
.endif
@@ -4089,15 +4088,14 @@
Makefile Options
- Some large applications can be built in a number of
- configurations, adding functionality if one of a number of
- libraries or applications is available. Examples include
+ Many applications can be built with optional or differing
+ configurations. Examples include
choice of natural (human) language, GUI versus command-line,
- or type of database to support. Since not all users want
- those libraries or applications, the ports system provides
- hooks that the port author can use to control which
- configuration should be built. Supporting these properly will
- make users happy, and effectively provide 2 or more ports for
+ or type of database to support. Users may need a different
+ configuration than the default, so the ports system provides
+ hooks the port author can use to control which variation
+ will be built. Supporting these options properly will
+ make users happy, and effectively provide two or more ports for
the price of one.
@@ -4109,7 +4107,7 @@
WITHOUT_*
These variables are designed to be set by the system
- administrator. There are many that are standardized in
+ administrator. There are many that are standardized in the
ports/KNOBS
file.
@@ -4131,7 +4129,7 @@
Unless otherwise specified, these variables are only
tested for being set or not set, rather than being set
- to some kind of variable such as YES
+ to a specific value such as YES
or NO.
@@ -4173,11 +4171,11 @@
WITHOUT_X11
- If the port can be built both with and
- without X support, then it should normally be
+ Ports that can be built both with and
+ without X support are normally
built with X support. If this variable is
defined, then the version that does not have X
- support should be built instead.
+ support will be built instead.
@@ -4187,7 +4185,7 @@
Knob Naming
- It is recommended that porters use like-named knobs,
+ Porters should use like-named knobs, both
for the benefit of end-users and to help keep the number
of knob names down. A list of popular knob names can be
found in the
Background
- The OPTIONS variable gives the user
- who installs the port a dialog with the available options
- and saves them to
- /var/db/ports/portname/options.
- Next time when the port has to be rebuild, the options are
- reused. Never again you will have to remember all the
- twenty
- WITH_* and
- WITHOUT_*
- options you used to build this port!
+ The OPTIONS_* variables give the user
+ installing the port a dialog showing the available options,
+ and then saves those options to
+ /var/db/ports/${UNIQUENAME}/options.
+ The next time the port is built, the options are
+ reused.
When the user runs make config (or
runs make build for the first time),
- the framework will check for
- /var/db/ports/portname/options.
- If that file does not exist, it will use the values of
- OPTIONS to create a dialog box where
+ the framework checks for
+ /var/db/ports/${UNIQUENAME}/options.
+ If that file does not exist, the values of
+ OPTIONS_* are used, and a dialog box is displayed where
the options can be enabled or disabled. Then the
options file is saved and the
- selected variables will be used when building the
+ configured variables are used when building the
port.
If a new version of the port adds new
OPTIONS, the dialog will be presented
- to the user, with the saved values of old
+ to the user with the saved values of old
OPTIONS prefilled.
- Use make showconfig to see the
+ make showconfig shows the
saved configuration. Use make rmconfig
to remove the saved configuration.
@@ -4242,50 +4236,141 @@
Syntax
- The syntax for the OPTIONS variable
- is:
+ OPTIONS_DEFINE contains a list of
+ OPTIONS to be used. These are independent
+ of each other and are not grouped:
- OPTIONS= OPTION "descriptive text" default ...
+ OPTIONS_DEFINE= OPT1 OPT2
- The value for default is either ON
- or OFF. Multiple repetitions of these
- three fields are allowed.
+ Once defined, OPTIONS are
+ described (optional, but strongly recommended):
- OPTIONS definition must appear
+ OPT1_DESC= Describe OPT1
+OPT2_DESC= Describe OPT2
+OPT3_DESC= Describe OPT3
+OPT4_DESC= Describe OPT4
+OPT5_DESC= Describe OPT5
+OPT6_DESC= Describe OPT6
+
+
+ ports/Mk/bsd.options.desc.mk
+ has descriptions for many common
+ OPTIONS; there is usually no need
+ to override these.
+
+
+
+ When describing options, view it from the
+ perspective of the user: What does it do?
+ and Why would I want to enable this? Do
+ not just repeat the name. For example, describing the
+ NLS option as
+ include NLS support does not help the
+ user who can already see the option name but may not
+
+ know what it means. Describing it as Native
+ Language Support via gettext utilities is
+ much more helpful.
+
+
+ OPTIONS can be grouped as radio
+ choices, where only one choice from each group is
+ allowed:
+
+ OPTIONS_SINGLE= SG1
+OPTIONS_SINGLE_SG1= OPT3 OPT4
+
+ OPTIONS can also be grouped as
+ multiple-choice lists, where
+ at least one option must be
+ enabled:
+
+ OPTIONS_MULTI= MG1
+OPTIONS_MULTI_MG1= OPT5 OPT6
+
+ OPTIONS are unset by default,
+ unless they are listed in
+ OPTIONS_DEFAULT:
+
+ OPTIONS_DEFAULT= OPT1 OPT3 OPT6
+
+ OPTIONS definitions must appear
before the inclusion of
bsd.port.options.mk. The
- WITH_* and WITHOUT_*
- variables can only be tested after the inclusion of
+ PORT_OPTIONS variable can only be
+ tested after the inclusion of
bsd.port.options.mk. Inclusion of
bsd.port.pre.mk can be used instead,
too, and is still widely used in ports written before the
introduction of bsd.port.options.mk.
But be aware that some variables will not work as expected
after the inclusion of
- bsd.port.pre.mk, typically
+ bsd.port.pre.mk, typically some
USE_* flags.
Simple Use of <makevar>OPTIONS</makevar>
- OPTIONS= FOO "Enable option foo" On \
- BAR "Support feature bar" Off
+ OPTIONS_DEFINE= FOO BAR
+FOO_DESC= Enable option foo
+BAR_DESC= Support feature bar
+OPTIONS_DEFAULT=FOO
+
.include <bsd.port.options.mk>
-.if defined(WITHOUT_FOO)
-CONFIGURE_ARGS+= --without-foo
+.if ${PORT_OPTIONS:MFOO}
+CONFIGURE_ARGS+=--without-foo
.else
-CONFIGURE_ARGS+= --with-foo
+CONFIGURE_ARGS+=--with-foo
.endif
-.if defined(WITH_BAR)
+.if ${PORT_OPTIONS:MBAR}
RUN_DEPENDS+= bar:${PORTSDIR}/bar/bar
.endif
.include <bsd.port.mk>
+
+ Practical Use of <makevar>OPTIONS</makevar>
+
+ OPTIONS_DEFINE= EXAMPLES
+
+OPTIONS_SINGLE= BACKEND
+OPTIONS_SINGLE_BACKEND= MYSQL PGSQL BDB
+
+OPTIONS_MULTI= AUTH
+OPTIONS_MULTI_AUTH= LDAP PAM SSL
+
+EXAMPLES_DESC= Install extra examples
+MYSQL_DESC= Use MySQL as backend
+PGSQL_DESC= Use PostgreSQL as backend
+BDB_DESC= Use Berkeley DB as backend
+LDAP_DESC= Build with LDAP authentication support
+PAM_DESC= Build with PAM support
+SSL_DESC= Build with OpenSSL support
+
+OPTIONS_DEFAULT= PGSQL LDAP SSL
+
+.include <bsd.port.options.mk>
+
+.if ${PORT_OPTIONS:MPGSQL}
+USE_PGSQL= yes
+CONFIGURE_ARGS+= --with-postgres
+.else
+CONFIGURE_ARGS+= --without-postgres
+.endif
+
+.if ${PORT_OPTIONS:MICU}
+LIB_DEPENDS+= icuuc:${PORTSDIR}/devel/icu
+.endif
+
+# Check other OPTIONS
+
+.include <bsd.port.mk>
+
+
Old-Style Use of <makevar>OPTIONS</makevar>
@@ -4301,6 +4386,12 @@
.include <bsd.port.post.mk>
+
+
+ This method of using OPTIONS
+ is deprecated, and will be removed at some point.
+ Do not use this method for new ports.
+
@@ -4317,7 +4408,7 @@
Wrong Handling of an Option
- .if defined(WITH_FOO)
+ .if ${PORT_OPTIONS:MFOO}
LIB_DEPENDS+= foo.0:${PORTSDIR}/devel/foo
CONFIGURE_ARGS+= --enable-foo
.endif
@@ -4336,7 +4427,7 @@
Correct Handling of an Option
- .if defined(WITH_FOO)
+ .if ${PORT_OPTIONS:MFOO}
LIB_DEPENDS+= foo.0:${PORTSDIR}/devel/foo
CONFIGURE_ARGS+= --enable-foo
.else
@@ -7987,7 +8078,7 @@
.include <bsd.port.pre.mk>
-.if defined(WITH_WX) || ${HAVE_WX:Mwx-2.4} != ""
+.if defined(WITH_WX) || !empty(PORT_OPTIONS:MWX) || !empty(HAVE_WX:Mwx-2.4)
USE_WX= 2.4
CONFIGURE_ARGS+= --enable-wx
.endif
@@ -8004,7 +8095,7 @@
.include <bsd.port.pre.mk>
-.if defined(WITH_WXPYTHON) || ${HAVE_WX:Mpython} != ""
+.if defined(WITH_WXPYTHON) || !empty(PORT_OPTIONS:MWXPYTHON) || !empty(HAVE_WX:Mpython)
WX_COMPS+= python
CONFIGURE_ARGS+= --enable-wxpython
.endif
@@ -8495,7 +8586,7 @@
.include <bsd.port.pre.mk>
-.if defined(WITH_LUA5) || ${HAVE_LUA:Mlua-5.[01]} != ""
+.if defined(WITH_LUA5) || !empty(PORT_OPTIONS:MLUA5) || !empty(HAVE_LUA:Mlua-5.[01])
USE_LUA= 5.0-5.1
CONFIGURE_ARGS+= --enable-lua5
.endif
@@ -8512,7 +8603,7 @@
.include <bsd.port.pre.mk>
-.if defined(WITH_TOLUA) || ${HAVE_LUA:Mtolua} != ""
+.if defined(WITH_TOLUA) || !empty(PORT_OPTIONS:MTOLUA) || !empty(HAVE_LUA:Mtolua)
LUA_COMPS+= tolua
CONFIGURE_ARGS+= --enable-tolua
.endif
From crees at FreeBSD.org Sun May 27 18:15:18 2012
From: crees at FreeBSD.org (crees at FreeBSD.org)
Date: Sun, 27 May 2012 18:15:18 GMT
Subject: docs/167020: Bad command-line example in handbook
Message-ID: <201205271815.q4RIFITd021085@freefall.freebsd.org>
Synopsis: Bad command-line example in handbook
State-Changed-From-To: closed->open
State-Changed-By: crees
State-Changed-When: Sun May 27 18:15:17 UTC 2012
State-Changed-Why:
This can be more portable (work with csh and sh) using env;
http://www.bayofrum.net/~crees/patches/handbook-dump-over-ssh.diff
http://www.freebsd.org/cgi/query-pr.cgi?pr=167020
From no-reply at priceangels.com Mon May 28 03:30:36 2012
From: no-reply at priceangels.com (PriceAngels)
Date: Mon, 28 May 2012 05:00:26 +0200
Subject: Dear Customer:Andriod 2.3 Tablet PC 20% off
Message-ID: <0.1.11B.9BC.1CD3C7E08707C9A.0@pmta41036.emsmtp.com>
To view the graphic version (HTML) of this e-mail, click on the
following link or copy it into your browser:
http://emaillink2.priceangels.com/u/gm.php?prm=aUv3Bnf3uC_143435532_217845_8293
About PriceAngels.com
Welcome!
Thank you for visiting PriceAngels.com, where you will find a wide
array of high-quality products at unbelievable wholesale prices, and
more important, we guarantee Free-Shipping all over the world!
Customer-Centric Company
PriceAngels.com is the next generation of online-shopping. Offering
our customers more type of products, more conveniently, and at even
lower wholesale prices has always been the focus of PriceAngels.com. We
provide a best-of-breed online-shopping platform to our customers all
over the world, no matter you?re a wholesaler who is looking for new
merchandise and high profits , a retailer who wants to empower your
commerce offerings, or an individual shopper who is looking for the
latest products with good quality and lower price, you will be satisfied
with us.
We?ve Only Just Begun
From the moment we founded PriceAngels, our vision has been to
empower the people worldwide in buying and selling online. We have
served customers from over 30 countries, and we?re still growing. In the
years to come, you?ll see priceangels.com create new technologies,
expand into more geographies and continue to improve the lives of
wholesalers, retailers and individual shoppers around the world
Our Promises
We promise to:
Free-shipping all over the world.
Source only the best consumer goods and ensure the highest
quality.
Streamline the buying and payment process, and make it as easy
as possible.
Help the customers all over the world discover products and
manufacturers in China.
Deliver the goods to the customers all over the world with
speed and precision
Provide 24-hour customer support on weekdays.
Learn More
To learn more about PriceAngels.com today, explore our website the
products, special offers, and you can also read some customer reviews.
If you want to unsubscribe from our mailing list, use the following
link:
http://emaillink2.priceangels.com/u/un.php?par=aUv3Bnf3uC_217845_8293_$sid$
From bugmaster at FreeBSD.org Mon May 28 11:06:13 2012
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon, 28 May 2012 11:06:11 GMT
Subject: Current unassigned doc problem reports
Message-ID: <201205281106.q4SB6B6J062463@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/167742 doc Update documentation for group 5, and newgrp 1
o docs/167741 doc group(5): Group Passwords do not work and are not docu
o docs/167020 doc Bad command-line example in handbook
o docs/166553 doc find(1): find -delete documentation is misleading
o docs/166358 doc No networking in Jail build via: handbook/jail-tuning
o docs/165657 doc Web site Features page aging
o docs/165551 doc ipfw(8): no info in "ipfw pipe show" about ipv6
o docs/165410 doc [handbook] installer documentation is not up to date
o docs/165249 doc Multibyte characters in manpages still not displaying
o docs/164803 doc Unclear manual page for mount_unionfs(8)
o docs/164800 doc Handbook's installation topic doesn't mention ZFS
o docs/164772 doc incorrect ipfw sched parameters in manual
o docs/164682 doc Handbook contains wrong information about Flash player
o docs/164620 doc Raid 1 issues
o docs/164099 doc gparm(8): man page for gparm set is incorrect and inco
o docs/164034 doc acl(9) documentation lacking
o docs/163879 doc [handbook] handbook does not say about how to force to
o docs/163830 doc device smbios: missing documentation, no manpage
o docs/163576 doc zfs(8) sync property not noted in the manpage
o docs/163149 doc [patch] Red Hat Linux/i386 9 HTML format sudo man page
o docs/162775 doc zpool(1): Document some undocumented zpool import opti
o docs/162433 doc [handbook] QEMU instructions for FreeBSD guests
o docs/162419 doc [request] please document (new) zfs and zpool cmdline
o docs/162404 doc [handbook] IPv6 link-local address compared with IPv4
o docs/162380 doc Documentation lacking for getfacl/setfacl
o docs/161804 doc New documentation: French translation for building-pro
o docs/161754 doc p4tcc(4), est(4) and qpi(4) are not documented
o docs/161496 doc zfs(1): Please document that sysctl vfs.usermount must
o docs/160460 doc [handbook] Network setup guide suggestion
o docs/160447 doc [handbook] Developer's Handbook contains some outdated
o docs/160446 doc [handbook] Handbook sound setup seems outdated
o docs/160445 doc [handbook] Handbook does not mention ACL
o docs/160399 doc Man page for re(4) missing jumbo frames info
o docs/159307 doc [patch] lpd smm chapter unconditionally installed
o docs/159298 doc [handbook] document Konqueror with Webkit support to i
o docs/158388 doc Incorrect documentation of LOCAL_SCRIPT in release(7)
o docs/158387 doc The tree(3) man should mention the RB_FOREACH_SAFE() A
o docs/157908 doc [handbook] Description of post-install should include
o docs/157049 doc FreeBSD Handbook: Chapter 14 (Security) Inaccuracy
p docs/156955 doc bug in share/man/man2/setsockopt.2
o docs/156920 doc isspecial(3) is not helpful
o docs/156853 doc [patch] Update docs: jail(8) security issues with worl
o docs/156815 doc chmod(1): manpage should describe that chmod kicks +t
o docs/156689 doc stf(4) output-only documentation gives bad configurati
f docs/156187 doc [handbook] [patch] Add bsnmpd to handbook
o docs/156081 doc troff falls with troff.core with UTF-8 man with incorr
o docs/155982 doc [handbook] reaper of the dead: remove reference to flo
o docs/155773 doc dialog(1): dialog manpages not updated
o docs/155149 doc [patch] don't encourage using xorg.conf outside of PRE
o docs/154838 doc update cvs-tags information on releng_* to reflect sup
o docs/153958 doc ksu man-page documented, but not installed
a docs/153012 doc [patch] iostat(8) requires an argument to -c option
o docs/151752 doc pw.conf(5) doesn't define format for file clearly
o docs/150991 doc [patch] Install upgtfw using pkg_add as advised in upg
o docs/150917 doc [patch] icmp.4, wrong description of icmplim and icmpl
o docs/150877 doc ambiguity in newsyslog(8) man page about zfs with comp
o docs/150255 doc dtrace description should mention makeoptions DEBUG=-g
o docs/150219 doc zfs(8) manual page misses jail/unjail
o docs/149574 doc [patch] update mi_switch(9) man page
o docs/148987 doc [patch] {MD[245]|SHA_|SHA1_|SHA256_}{End|File|FileChun
o docs/148984 doc [handbook] Mistake in section 16.15.4 of the handbook
o docs/148680 doc [sysctl][patch] Document some sys/kern sysctls
o docs/148071 doc Failover mode between wired and wireless interfaces
o docs/147995 doc elf.5 man page has has missing reference
o docs/146958 doc bad link to "XaQti XMAC II datasheet" in sk(4) manual
o docs/146521 doc [handbook] Update IPv6 system handbook section to ment
o docs/145719 doc [patch] 7.3 relnotes erroneously describes new getpage
o docs/145699 doc hexdump(1) mutes all format qualifier output following
o docs/145644 doc Add artical about creating manpage from scratch
o docs/145069 doc Dialup firewalling with FreeBSD article out dated.
o docs/145066 doc Update for new uart dev names for serial port.
s docs/144818 doc all mailinglist archives dated 19970101 contain traili
o docs/144630 doc [patch] domainname(1) manpage contains old information
o docs/144515 doc [handbook] Expand handbook Table of contents
o docs/144488 doc share/examples/etc/make.conf: contains dangerous examp
o docs/143850 doc procfs(5) manpage for status > controlling terminal is
o docs/143416 doc [handbook] IPFW handbook page issues
o docs/143408 doc man filedesc(9) is missing
o docs/142168 doc [patch] ld(1): ldd(1) not mentioned in ld(1) manpage
o docs/141032 doc misleading documentation for rtadvd.conf(5) raflags se
s docs/140847 doc [request] add documentation on ECMP and new route args
p docs/140457 doc [patch] Grammar fix for isspace(3)
o docs/140444 doc [patch] New Traditional Chinese translation of custom-
o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd
o docs/139336 doc [request] ZFS documentation suggestion
o docs/139165 doc gssapi.3 man page out of sync with between crypto and
o docs/139018 doc translation of submitting.sgml from docproj/submitting
o docs/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca
o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa
o docs/136666 doc [handbook] Configure serial port for remote kernel deb
o docs/136035 doc ftpchroot(5) omits an important option
o docs/134123 doc The RUNQUEUE(9) man page is out of date
o docs/132839 doc [patch] Fix example script in ldap-auth article
o docs/132718 doc [handbook] Information about adding a new mirror is ou
o docs/132260 doc dhcpd(8) pid not stored in documented location
o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/131918 doc [patch] Fixes for the BPF(4) man page
o docs/131626 doc [patch] dump(8) "recommended" cache option confusing
o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or
o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson
o docs/129464 doc using packages system
o docs/129095 doc ipfw(8): Can not check that packet originating/destine
o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages
s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage
o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps
o docs/126484 doc libc function res-zonscut2 is not documented
o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in
f docs/122052 doc minor update on handbook section 20.7.1
o docs/121952 doc Handbook chapter on Network Address Translation wrong
o docs/121585 doc [handbook] Wrong multicast specification
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/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls
o docs/120539 doc Inconsistent ipfw's man page
o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and
o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6
o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting
o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return
o docs/116080 doc PREFIX is documented, but not the more important LOCAL
p 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/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/112682 doc Handbook GEOM_GPT explanation does not provide accurat
o docs/111425 doc Missing chunks of text in historical manpages
o docs/111265 doc [request] Clarify how to set common shell variables
o docs/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/110062 doc [patch] mount_nfs(8) fails to mention a failure condit
p docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max
o docs/109981 doc No manual entry for post-grohtml
o docs/109977 doc No manual entry for ksu
o docs/109973 doc No manual entry for c++filt
o docs/109972 doc No manual entry for zless/bzless
f docs/109226 doc [request] No manual entry for sntp
o docs/109201 doc [request]: manual for callbootd
a docs/108980 doc list of missing man pages
o docs/106135 doc [request] articles/vinum needs to be updated
o docs/105608 doc fdc(4) debugging description staled
o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/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/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/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage
o docs/84932 doc new document: printing with an Epson ALC-3000N on Free
o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively
o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand
o docs/83820 doc getino(3) manpage not installed
o docs/81611 doc [patch] natd runs with -same_ports by default
o docs/78480 doc Networked printer setup unnecessarily complex in handb
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/57298 doc [patch] add using compact flash cards info to handbook
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/51480 doc Multiple undefined references in the FreeBSD manual pa
o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation
o docs/48101 doc [patch] Add documentation on the fixit disk
o docs/43823 doc [patch] update to environ(7) manpage
o docs/41089 doc pax(1) -B option does not mention interaction with -z
o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982 doc [patch] developers-handbook/Jail fix
o docs/38556 doc EPS file of beastie, as addition to existing examples
s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files.
o docs/27605 doc [patch] Cross-document references ()
o docs/26286 doc *printf(3) etc should gain format string warnings
o docs/24786 doc missing FILES descriptions in sa(4)
s docs/20028 doc ASCII docs should reflect tags in the sourc
189 problems total.
From info at rycin.net Mon May 28 15:35:23 2012
From: info at rycin.net (Mr. Zhou)
Date: Mon, 28 May 2012 22:17:54 +0800
Subject: Tablet PC
Message-ID:
Dear doc at FreeBSD.org
The following is our Tablet PC21 introduced:
7" TFT LCD Capacitive(5-Point) 800*480 Pixel Touch Screen
CPU Allwinner A10 Gortex A8 1.5Ghz
Android 4.0 operation system
RAM 512MB DDR3 (Can be expanded to 1GB)
Embeded NAND FLASH 8GB
Office, Email, MSN, Skype, Video, Music Game etc.
Other model please visit our website.
Price:
Sample $85
10pcs $80
50pcs $78
100pcs $75
Paymemt: 30% down payment and paid 70% balance before delivery.
Price term EXW.
Delivery time is 1-3 week after sample and order confirmation.
Guarantee: 12 Months (Artificial damage excluded).
Please feel free to contact us of your any question.
Contact: Mr. Zhou
E-mail: info at rycin.net
TradeManager: cn116545946
Company: Rycin Technology Co., Ltd.
Address: Building E, Baoyuan Industrial Zone, Laodong Road, Xixiang, Baoan,
Shenzhen, China 518102
Website: www.rycin.net
From daze at robobiz.ru Tue May 29 04:54:56 2012
From: daze at robobiz.ru (=?utf-8?B?0KHRgtCw0YLQuNGB0YLQuNC60LA=?=)
Date: Tue, 29 May 2012 08:53:50 +0400
Subject: =?utf-8?b?0J7RhtC10L3QuNGC0Ywg0Y3QutGB0L/QvtGA0YLQvdGL0Lkg0Lg=?=
=?utf-8?b?0LzQv9C+0YDRgtC90YvQuSDQv9C+0YLQtdC90YbQuNCw0Ls=?=
Message-ID:
??????? ?????????? ????????? ????????? ??????* ?????? ?? ???? ??????
? ?????????? ???????????
2011 ?????? ??? ? ?????? ??????.?? ???? ????? ????? ??. ??.
??????? ?????????? ????????? ????????? ?????? ??????????? ?????? (????????
??????) - ??????? ????? ?????????-??????????, ??????????, ???, ???????? ??????????,
????????
?????? ???????????? ???? ?????????? ???: ????????, ???????? ???????? ?
??????.
????????????, ???????? ????????, ?????? ???????? (???????), ?????? ?
?????- ??????????, ??????? ????????
??????? ????? ????????????? ???????????, ?? ????? ????, ????????? ??????,
????? ?????? ? ?.?.
?????? ?????? ??????????????? ????? ?? ??????* ?????? ??? ??????
???????. ?????? ??????? ??????????? ??? ? ?????? ??????? ????????.
?????????? ???????????? ??? ??? ?????? ???????? ?????????? ?????
?????????? ?? ?????? ???????? ?????????? ?????????? ??? ??????.
??????????. ??? ??????. ?????? 2011 ???.
?? ???? ????? ????? ???? ?????? ???????
????: 3.500 ???.
??????????. ??? ???????. ?????? 2011 ???.
????: 3.000 ???.
?? ???????? ????????????
???????????? ??????????? ???
??????? ???. 8-926-524-43-34.
????????.
???? ?? ?????? ?? ??????? ???????? ???????, ????????? ?? ??????
v-sevostyanov at list.ru
From s.bhprivatecorrespodence at gmx.com Tue May 29 07:41:38 2012
From: s.bhprivatecorrespodence at gmx.com (Susan B Holford (Ms))
Date: Tue, 29 May 2012 02:41:28 -0500
Subject: Reply..
Message-ID: <20120529074128.AAFD3873969F@mail.artworkdigital.com.br>
- This mail is in HTML. Some elements may be ommited in plain text. -
Hello,
Compliments and good day to you and your family.?I write you this mail as a reminder once more having waited patiently?for your response to my initial contact with you through snail mail.?However since i assume you did not get it i want to use this medium even though?it might not be the best form of communication in matters like this due to the?ever growing disbelief and illicit scams and fraud associated with it, i?seem to have no choice than to make use of it, coupled with the fact that?it might be just perfect due to the ability to redeem time.
Without wasting much of your time i want to bring you into a business?venture which i think should be of interest and concern to you, since it has?to do with a perceived family member of yours However i need to?be sure that you must have received this communication so i will not divulge?much information about it until i get a response from you.?Kindly respond back to me.
Regards,
Susan
From jesse.hagewood at gmail.com Tue May 29 16:43:41 2012
From: jesse.hagewood at gmail.com (Jesse Hagewood)
Date: Tue, 29 May 2012 12:43:39 -0400
Subject: SoC project: Complete BSD-licensed text processing tools.
Message-ID:
Hey everyone,
I'm one of the students participating in Google Summer of Code this summer,
with FreeBSD as my mentoring organization. I thought I would share my
project on this mailing list, in case it is of interest to anyone.
My project this summer is to add features and/or complete the BSD-licensed
text processing tools mdocml, diff/sdiff/diff3 (ports from OpenBSD) for the
purpose of deprecating groff and the GNU diff utilities in the FreeBSD
source tree.
The first part of my project is to add features and make improvements to
mdocml. Right now, my goal is to try to implement some text-formatting
requests that are missing from roff. The missing requests are:
.ad (adjust margins)
.na
.it
.ns (no-space mode)
.rs (no-space mode off)
.ti (temporary indent)
.ta (tab settings)
.hy (hyphenation)
.ne
.nh
.ni
.ps
I will be spending most of this week implementing them. So far, I have been
working on .ns and .rs, and will have them successfully working probably by
the end of the day.
If you'd like to learn more, here is the project's wiki page:
http://wiki.freebsd.org/SummerOfCode2012/JesseHagewood
SVN repo:
https://socsvn.freebsd.org/socsvn/soc2012/jhagewood/
Also, any questions/comments/criticisms would be greatly appreciated!
-Jesse Hagewood
From bjk at FreeBSD.org Wed May 30 05:01:41 2012
From: bjk at FreeBSD.org (bjk at FreeBSD.org)
Date: Wed, 30 May 2012 05:01:41 GMT
Subject: docs/167020: Bad command-line example in handbook
Message-ID: <201205300501.q4U51fjN095145@freefall.freebsd.org>
Synopsis: Bad command-line example in handbook
Responsible-Changed-From-To: freebsd-doc->bjk
Responsible-Changed-By: bjk
Responsible-Changed-When: Wed May 30 05:01:15 UTC 2012
Responsible-Changed-Why:
I will take this one.
http://www.freebsd.org/cgi/query-pr.cgi?pr=167020
From michael.gullberg at gmail.com Wed May 30 14:24:35 2012
From: michael.gullberg at gmail.com (=?utf-8?B?bWljaGFlbC5ndWxsYmVyZ0BnbWFpbC5jb20=?=)
Date: Wed, 30 May 2012 16:24:27 +0200
Subject: freebsd-doc Digest, Vol 479, Issue 1
Message-ID: <4fc62d9e.c40a700a.321a.0bb9@mx.google.com>
Sent from my HTC
----- Reply message -----
From: freebsd-doc-request at freebsd.org
To:
Subject: freebsd-doc Digest, Vol 479, Issue 1
Date: Mon, May 28, 2012 14:06
Send freebsd-doc mailing list submissions to
freebsd-doc at freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
or, via email, send a message with subject or body 'help' to
freebsd-doc-request at freebsd.org
You can reach the person managing the list at
freebsd-doc-owner at freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-doc digest..."
Today's Topics:
1. Re: New docs for OPTIONS (Warren Block)
2. Re: docs/167020: Bad command-line example in handbook
(crees at FreeBSD.org)
3. Dear Customer:Andriod 2.3 Tablet PC 20% off (PriceAngels)
----------------------------------------------------------------------
Message: 1
Date: Sun, 27 May 2012 10:02:01 -0600 (MDT)
From: Warren Block
Subject: Re: New docs for OPTIONS
To: Chris Rees
Cc: doc at freebsd.org, portmgr at freebsd.org
Message-ID:
Content-Type: text/plain; charset="us-ascii"
On Sat, 26 May 2012, Chris Rees wrote:
> We have a new world order for OPTIONS in ports (exciting, isn't it??),
> and would very much like to document it.
>
> I've prepared the following patch which has had fairly extensive
> review, apart from not having a formal approval by a docs person.
>
> Would anyone mind giving it a check and approving it please? Bapt
> plans to commit the code later this week, and it'd be great to have
> approval by then!
>
> Thanks,
>
> Chris
>
>
> http://www.bayofrum.net/~crees/patches/optionsng-docs-patch.diff
>
> http://www.bayofrum.net/~crees/rendered/porters-optionsng.html
Attached is a full patch that builds on that. Some simplifications and
clarifications, and an added tip on helpful descriptions.
-------------- next part --------------
Index: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml
===================================================================
--- doc/en_US.ISO8859-1/books/porters-handbook/book.sgml (revision 38891)
+++ doc/en_US.ISO8859-1/books/porters-handbook/book.sgml (working copy)
@@ -3663,19 +3663,17 @@
<makevar>USE_<replaceable>*</replaceable></makevar>
- A number of variables exist in order to encapsulate
- common dependencies that many ports have. Although their
- use is optional, they can help to reduce the verbosity of
+ Several variables exist to define
+ common dependencies shared by many ports. Their
+ use is optional, but helps to reduce the verbosity of
the port Makefiles. Each of them is
styled as
- USE_*. The
- usage of these variables is restricted to the port
+ USE_*.
+ These variables may be used only in the port
Makefiles and
- ports/Mk/bsd.*.mk and is not designed
- to encapsulate user-settable options — use
- WITH_* and
- WITHOUT_* for
- that purpose.
+ ports/Mk/bsd.*.mk. They are not meant
+ for user-settable options — use
+ PORT_OPTIONS for that purpose.
It is always incorrect to set any
@@ -3880,11 +3878,12 @@
Correct Declaration of an Optional Dependency
- OPTIONS= BAR "Enable bar support" off
+ OPTIONS_DEFINE= BAR
+BAR_DESC= Enable bar support
-.include <bsd.port.pre.mk>
+.include <bsd.port.options.mk>
-.if defined(WITH_BAR) && !defined(WITHOUT_BAR)
+.if ${PORTOPTIONS:MBAR}
LIB_DEPENDS= bar:${PORTSDIR}/foo/bar
.endif
@@ -4089,15 +4088,14 @@
Makefile Options
- Some large applications can be built in a number of
- configurations, adding functionality if one of a number of
- libraries or applications is available. Examples include
+ Many applications can be built with optional or differing
+ configurations. Examples include
choice of natural (human) language, GUI versus command-line,
- or type of database to support. Since not all users want
- those libraries or applications, the ports system provides
- hooks that the port author can use to control which
- configuration should be built. Supporting these properly will
- make users happy, and effectively provide 2 or more ports for
+ or type of database to support. Users may need a different
+ configuration than the default, so the ports system provides
+ hooks the port author can use to control which variation
+ will be built. Supporting these options properly will
+ make users happy, and effectively provide two or more ports for
the price of one.
@@ -4109,7 +4107,7 @@
WITHOUT_*
These variables are designed to be set by the system
- administrator. There are many that are standardized in
+ administrator. There are many that are standardized in the
ports/KNOBS
file.
@@ -4131,7 +4129,7 @@
Unless otherwise specified, these variables are only
tested for being set or not set, rather than being set
- to some kind of variable such as YES
+ to a specific value such as YES
or NO.
@@ -4173,11 +4171,11 @@
WITHOUT_X11
- If the port can be built both with and
- without X support, then it should normally be
+ Ports that can be built both with and
+ without X support are normally
built with X support. If this variable is
defined, then the version that does not have X
- support should be built instead.
+ support will be built instead.
@@ -4187,7 +4185,7 @@
Knob Naming
- It is recommended that porters use like-named knobs,
+ Porters should use like-named knobs, both
for the benefit of end-users and to help keep the number
of knob names down. A list of popular knob names can be
found in the
Background
- The OPTIONS variable gives the user
- who installs the port a dialog with the available options
- and saves them to
- /var/db/ports/portname/options.
- Next time when the port has to be rebuild, the options are
- reused. Never again you will have to remember all the
- twenty
- WITH_* and
- WITHOUT_*
- options you used to build this port!
+ The OPTIONS_* variables give the user
+ installing the port a dialog showing the available options,
+ and then saves those options to
+ /var/db/ports/${UNIQUENAME}/options.
+ The next time the port is built, the options are
+ reused.
When the user runs make config (or
runs make build for the first time),
- the framework will check for
- /var/db/ports/portname/options.
- If that file does not exist, it will use the values of
- OPTIONS to create a dialog box where
+ the framework checks for
+ /var/db/ports/${UNIQUENAME}/options.
+ If that file does not exist, the values of
+ OPTIONS_* are used, and a dialog box is displayed where
the options can be enabled or disabled. Then the
options file is saved and the
- selected variables will be used when building the
+ configured variables are used when building the
port.
If a new version of the port adds new
OPTIONS, the dialog will be presented
- to the user, with the saved values of old
+ to the user with the saved values of old
OPTIONS prefilled.
- Use make showconfig to see the
+ make showconfig shows the
saved configuration. Use make rmconfig
to remove the saved configuration.
@@ -4242,50 +4236,141 @@
Syntax
- The syntax for the OPTIONS variable
- is:
+ OPTIONS_DEFINE contains a list of
+ OPTIONS to be used. These are independent
+ of each other and are not grouped:
- OPTIONS= OPTION "descriptive text" default ...
+ OPTIONS_DEFINE= OPT1 OPT2
- The value for default is either ON
- or OFF. Multiple repetitions of these
- three fields are allowed.
+ Once defined, OPTIONS are
+ described (optional, but strongly recommended):
- OPTIONS definition must appear
+ OPT1_DESC= Describe OPT1
+OPT2_DESC= Describe OPT2
+OPT3_DESC= Describe OPT3
+OPT4_DESC= Describe OPT4
+OPT5_DESC= Describe OPT5
+OPT6_DESC= Describe OPT6
+
+
+ ports/Mk/bsd.options.desc.mk
+ has descriptions for many common
+ OPTIONS; there is usually no need
+ to override these.
+
+
+
+ When describing options, view it from the
+ perspective of the user: What does it do?
+ and Why would I want to enable this? Do
+ not just repeat the name. For example, describing the
+ NLS option as
+ include NLS support does not help the
+ user who can already see the option name but may not
+
+ know what it means. Describing it as Native
+ Language Support via gettext utilities is
+ much more helpful.
+
+
+ OPTIONS can be grouped as radio
+ choices, where only one choice from each group is
+ allowed:
+
+ OPTIONS_SINGLE= SG1
+OPTIONS_SINGLE_SG1= OPT3 OPT4
+
+ OPTIONS can also be grouped as
+ multiple-choice lists, where
+ at least one option must be
+ enabled:
+
+ OPTIONS_MULTI= MG1
+OPTIONS_MULTI_MG1= OPT5 OPT6
+
+ OPTIONS are unset by default,
+ unless they are listed in
+ OPTIONS_DEFAULT:
+
+ OPTIONS_DEFAULT= OPT1 OPT3 OPT6
+
+ OPTIONS definitions must appear
before the inclusion of
bsd.port.options.mk. The
- WITH_* and WITHOUT_*
- variables can only be tested after the inclusion of
+ PORT_OPTIONS variable can only be
+ tested after the inclusion of
bsd.port.options.mk. Inclusion of
bsd.port.pre.mk can be used instead,
too, and is still widely used in ports written before the
introduction of bsd.port.options.mk.
But be aware that some variables will not work as expected
after the inclusion of
- bsd.port.pre.mk, typically
+ bsd.port.pre.mk, typically some
USE_* flags.
Simple Use of <makevar>OPTIONS</makevar>
- OPTIONS= FOO "Enable option foo" On \
- BAR "Support feature bar" Off
+ OPTIONS_DEFINE= FOO BAR
+FOO_DESC= Enable option foo
+BAR_DESC= Support feature bar
+OPTIONS_DEFAULT=FOO
+
.include <bsd.port.options.mk>
-.if defined(WITHOUT_FOO)
-CONFIGURE_ARGS+= --without-foo
+.if ${PORT_OPTIONS:MFOO}
+CONFIGURE_ARGS+=--without-foo
.else
-CONFIGURE_ARGS+= --with-foo
+CONFIGURE_ARGS+=--with-foo
.endif
-.if defined(WITH_BAR)
+.if ${PORT_OPTIONS:MBAR}
RUN_DEPENDS+= bar:${PORTSDIR}/bar/bar
.endif
.include <bsd.port.mk>
+
+ Practical Use of <makevar>OPTIONS</makevar>
+
+ OPTIONS_DEFINE= EXAMPLES
+
+OPTIONS_SINGLE= BACKEND
+OPTIONS_SINGLE_BACKEND= MYSQL PGSQL BDB
+
+OPTIONS_MULTI= AUTH
+OPTIONS_MULTI_AUTH= LDAP PAM SSL
+
+EXAMPLES_DESC= Install extra examples
+MYSQL_DESC= Use MySQL as backend
+PGSQL_DESC= Use PostgreSQL as backend
+BDB_DESC= Use Berkeley DB as backend
+LDAP_DESC= Build with LDAP authentication support
+PAM_DESC= Build with PAM support
+SSL_DESC= Build with OpenSSL support
+
+OPTIONS_DEFAULT= PGSQL LDAP SSL
+
+.include <bsd.port.options.mk>
+
+.if ${PORT_OPTIONS:MPGSQL}
+USE_PGSQL= yes
+CONFIGURE_ARGS+= --with-postgres
+.else
+CONFIGURE_ARGS+= --without-postgres
+.endif
+
+.if ${PORT_OPTIONS:MICU}
+LIB_DEPENDS+= icuuc:${PORTSDIR}/devel/icu
+.endif
+
+# Check other OPTIONS
+
+.include <bsd.port.mk>
+
+
Old-Style Use of <makevar>OPTIONS</makevar>
@@ -4301,6 +4386,12 @@
.include <bsd.port.post.mk>
+
+
+ This method of using OPTIONS
+ is deprecated, and will be removed at some point.
+ Do not use this method for new ports.
+
@@ -4317,7 +4408,7 @@
Wrong Handling of an Option
- .if defined(WITH_FOO)
+ .if ${PORT_OPTIONS:MFOO}
LIB_DEPENDS+= foo.0:${PORTSDIR}/devel/foo
CONFIGURE_ARGS+= --enable-foo
.endif
@@ -4336,7 +4427,7 @@
Correct Handling of an Option
- .if defined(WITH_FOO)
+ .if ${PORT_OPTIONS:MFOO}
LIB_DEPENDS+= foo.0:${PORTSDIR}/devel/foo
CONFIGURE_ARGS+= --enable-foo
.else
@@ -7987,7 +8078,7 @@
.include <bsd.port.pre.mk>
-.if defined(WITH_WX) || ${HAVE_WX:Mwx-2.4} != ""
+.if defined(WITH_WX) || !empty(PORT_OPTIONS:MWX) || !empty(HAVE_WX:Mwx-2.4)
USE_WX= 2.4
CONFIGURE_ARGS+= --enable-wx
.endif
@@ -8004,7 +8095,7 @@
.include <bsd.port.pre.mk>
-.if defined(WITH_WXPYTHON) || ${HAVE_WX:Mpython} != ""
+.if defined(WITH_WXPYTHON) || !empty(PORT_OPTIONS:MWXPYTHON) || !empty(HAVE_WX:Mpython)
WX_COMPS+= python
CONFIGURE_ARGS+= --enable-wxpython
.endif
@@ -8495,7 +8586,7 @@
.include <bsd.port.pre.mk>
-.if defined(WITH_LUA5) || ${HAVE_LUA:Mlua-5.[01]} != ""
+.if defined(WITH_LUA5) || !empty(PORT_OPTIONS:MLUA5) || !empty(HAVE_LUA:Mlua-5.[01])
USE_LUA= 5.0-5.1
CONFIGURE_ARGS+= --enable-lua5
.endif
@@ -8512,7 +8603,7 @@
.include <bsd.port.pre.mk>
-.if defined(WITH_TOLUA) || ${HAVE_LUA:Mtolua} != ""
+.if defined(WITH_TOLUA) || !empty(PORT_OPTIONS:MTOLUA) || !empty(HAVE_LUA:Mtolua)
LUA_COMPS+= tolua
CONFIGURE_ARGS+= --enable-tolua
.endif
------------------------------
Message: 2
Date: Sun, 27 May 2012 18:15:18 GMT
From: crees at FreeBSD.org
Subject: Re: docs/167020: Bad command-line example in handbook
To: b.heidotting at yahoo.com, crees at FreeBSD.org, freebsd-doc at FreeBSD.org
Message-ID: <201205271815.q4RIFITd021085 at freefall.freebsd.org>
Synopsis: Bad command-line example in handbook
State-Changed-From-To: closed->open
State-Changed-By: crees
State-Changed-When: Sun May 27 18:15:17 UTC 2012
State-Changed-Why:
This can be more portable (work with csh and sh) using env;
http://www.bayofrum.net/~crees/patches/handbook-dump-over-ssh.diff
http://www.freebsd.org/cgi/query-pr.cgi?pr=167020
------------------------------
Message: 3
Date: Mon, 28 May 2012 05:00:26 +0200
From: "PriceAngels"
Subject: Dear Customer:Andriod 2.3 Tablet PC 20% off
To:
Message-ID: <0.1.11B.9BC.1CD3C7E08707C9A.0 at pmta41036.emsmtp.com>
Content-Type: text/plain; charset=iso-8859-1
To view the graphic version (HTML) of this e-mail, click on the
following link or copy it into your browser:
http://emaillink2.priceangels.com/u/gm.php?prm=aUv3Bnf3uC_143435532_217845_8293
About PriceAngels.com
Welcome!
Thank you for visiting PriceAngels.com, where you will find a wide
array of high-quality products at unbelievable wholesale prices, and
more important, we guarantee Free-Shipping all over the world!
Customer-Centric Company
PriceAngels.com is the next generation of online-shopping. Offering
our customers more type of products, more conveniently, and at even
lower wholesale prices has always been the focus of PriceAngels.com. We
provide a best-of-breed online-shopping platform to our customers all
over the world, no matter you?re a wholesaler who is looking for new
merchandise and high profits , a retailer who wants to empower your
commerce offerings, or an individual shopper who is looking for the
latest products with good quality and lower price, you will be satisfied
with us.
We?ve Only Just Begun
From the moment we founded PriceAngels, our vision has been to
empower the people worldwide in buying and selling online. We have
served customers from over 30 countries, and we?re still growing. In the
years to come, you?ll see priceangels.com create new technologies,
expand into more geographies and continue to improve the lives of
wholesalers, retailers and individual shoppers around the world
Our Promises
We promise to:
Free-shipping all over the world.
Source only the best consumer goods and ensure the highest
quality.
Streamline the buying and payment process, and make it as easy
as possible.
Help the customers all over the world discover products and
manufacturers in China.
Deliver the goods to the customers all over the world with
speed and precision
Provide 24-hour customer support on weekdays.
Learn More
To learn more about PriceAngels.com today, explore our website the
products, special offers, and you can also read some customer reviews.
If you want to unsubscribe from our mailing list, use the following
link:
http://emaillink2.priceangels.com/u/un.php?par=aUv3Bnf3uC_217845_8293_$sid$
------------------------------
_______________________________________________
freebsd-doc at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscribe at freebsd.org"
End of freebsd-doc Digest, Vol 479, Issue 1
*******************************************
From secretshopper1112gmail.com at mailserver.radbdg.net Wed May 30 14:24:50 2012
From: secretshopper1112gmail.com at mailserver.radbdg.net (Secret Shopper®)
Date: Wed, 30 May 2012 21:17:08 +0700 (WIT)
Subject: Online Mystery Shopping Assignment.
Message-ID: <20120530141708.4434222146@mailserver.radbdg.net>
We have a mystery shopping assignment in your area and we would like you to participate; Secret Shopper? is accepting applications from qualified individuals to become mystery shoppers. Its fun and rewarding, and you choose when and where you want to shop. You are never obligated to accept an assignment. There is no charge to become a shopper and you do not need previous experience. After you sign up, you will have access to training materials via e-mail, fax or postal mail.
ABOUT US
Secret Shopper? is the premier mystery shopping company, serving clients across America and Canada,Australia,New Zealand with over 500,000 shoppers available and ready to help businesses better serve their customers. We have now commenced our pilot program in Europe and are now seeking to recruit mystery shoppers to carry out prospective assignments. Continual investment in the latest internet and communication technologies coupled with over 16 years of know-how means working with Secret Shopper? is a satisfying and rewarding experience.
Mystery shopping as seen on ABC NEWS, NBC NEWS, L.A.TIMES. Stores and organizations such as The Gap, Walmart, Pizza Hut, and Banks. One amongst many others pay for Secret Shoppers to shop in their establishments and report their experiences. On top of being paid for shopping you are also allowed to keep purchases for free. Secret Shopper? NEVER charge fees to the shopper. Training, tips for improvement, and shopping opportunities are provided free to registered shoppers. Mystery shoppers are either paid a pre-arranged fee for a particular shop, a reimbursement for a purchase or a combination of both.
You are to shop secretly and invest just a token. This fee will be paid upfront. During this shop you will visit the location and make several observations
as regards the customer service. You will be required to interact with the shop attendant. You may conduct the shop alone or as a couple. The preliminary assignment will pay $300 for the duration of five (5) working visits.
Kindly Fill Out the application form below and we will get back to you shortly with the assignment:
PERSONAL INFORMATION:
First Name.............................................
Middle Name.............................................
Last Name.............................................
Street Address .............................................
City, State, Post code .............................................
Cell Phone Number .............................................
Home Phone Number .............................................
Age....................................................................
Current Occupation......................................................
Alternate Email Address .............................................
AVAILABILITY:
Days/Hours Available
Monday .............................................
Tuesday .............................................
Wednesday .............................................
Thursday .............................................
Friday .............................................
Saturday .............................................
Sunday .............................................
Hours Available: from _______ to ______
We await your urgent response. Thank you for your interest. We look forward to working with you.
Sincerely,
Peter Adams
Secret Shopper?
From uqs at FreeBSD.org Wed May 30 18:52:49 2012
From: uqs at FreeBSD.org (Ulrich =?utf-8?B?U3DDtnJsZWlu?=)
Date: Wed, 30 May 2012 20:52:46 +0200
Subject: SoC project: Complete BSD-licensed text processing tools.
In-Reply-To:
References:
Message-ID: <20120530185246.GK10094@acme.spoerlein.net>
On Tue, 2012-05-29 at 12:43:39 -0400, Jesse Hagewood wrote:
> Hey everyone,
>
> I'm one of the students participating in Google Summer of Code this summer,
> with FreeBSD as my mentoring organization. I thought I would share my
> project on this mailing list, in case it is of interest to anyone.
>
> My project this summer is to add features and/or complete the BSD-licensed
> text processing tools mdocml, diff/sdiff/diff3 (ports from OpenBSD) for the
> purpose of deprecating groff and the GNU diff utilities in the FreeBSD
> source tree.
>
> The first part of my project is to add features and make improvements to
> mdocml. Right now, my goal is to try to implement some text-formatting
> requests that are missing from roff. The missing requests are:
>
> .ad (adjust margins)
> .na
> .it
> .ns (no-space mode)
> .rs (no-space mode off)
> .ti (temporary indent)
> .ta (tab settings)
> .hy (hyphenation)
> .ne
> .nh
> .ni
> .ps
>
> I will be spending most of this week implementing them. So far, I have been
> working on .ns and .rs, and will have them successfully working probably by
> the end of the day.
>
> If you'd like to learn more, here is the project's wiki page:
> http://wiki.freebsd.org/SummerOfCode2012/JesseHagewood
>
> SVN repo:
> https://socsvn.freebsd.org/socsvn/soc2012/jhagewood/
>
> Also, any questions/comments/criticisms would be greatly appreciated!
Great! Please keep me in the loop wrt. mdocml as I still hope to get it
in the tree pre-10.x and set fire to groff.
Thanks
Uli
From claudiu.vasadi at gmail.com Thu May 31 07:55:39 2012
From: claudiu.vasadi at gmail.com (claudiu vasadi)
Date: Thu, 31 May 2012 09:55:39 +0200
Subject: 12.13.2 Network Limits - updating to reflect the different settings
between architectures (i386&amd64)
Message-ID:
Hi guys,
Recently I was reading
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html(section
12.13.2. Network limits -
NMBCLUSTERS) and I realised that there is no mention of amd64 and/or i386
architecture. The limit for the i386 architecture is 32768 AFAIK but for
amd64 it can go upto 65.000 and even more (according to memory I think).
I think that the docs should be updated a bit to reflect the different
limits for each architecture.
--
Best regards,
Claudiu Vasadi
From newsletters at priceangels.com Thu May 31 09:54:12 2012
From: newsletters at priceangels.com (PriceAngels)
Date: Thu, 31 May 2012 04:40:40 -0500 (CDT)
Subject: Dear Customer:Save 99%-here is how
Message-ID: <1338457240_SectionID-79275_HitID-1338456826670_SiteID-8693_EmailID-15540082_DB-34_SID-37@ss38.on9mail.com>
Your email program does not support HTML. To view an online version of this email, please click the link below.
http://ss38.on9mail.com/new/en_send_preview_iframe2.aspx?SID=37&NewsletterID=79275&SiteID=8693&EmailID=15540082&HitID=1338456826670&token=4585e8050821c125fc720e2545b544e68a812e66
To unsubscribe, click the link below.
http://ss38.on9mail.com/RWCode/subscribe.asp?SID=37&SiteID=8693&Email=doc at freebsd.org&HitID=1338456826670
From gjb at FreeBSD.org Thu May 31 13:14:50 2012
From: gjb at FreeBSD.org (Glen Barber)
Date: Thu, 31 May 2012 09:14:48 -0400
Subject: 12.13.2 Network Limits - updating to reflect the different
settings between architectures (i386&amd64)
In-Reply-To:
References:
Message-ID: <20120531131447.GC1763@glenbarber.us>
Hi,
On Thu, May 31, 2012 at 09:55:39AM +0200, claudiu vasadi wrote:
> Hi guys,
>
> Recently I was reading
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html(section
> 12.13.2. Network limits -
> NMBCLUSTERS) and I realised that there is no mention of amd64 and/or i386
> architecture. The limit for the i386 architecture is 32768 AFAIK but for
> amd64 it can go upto 65.000 and even more (according to memory I think).
>
> I think that the docs should be updated a bit to reflect the different
> limits for each architecture.
>
I think this may also be device-specific. We should find that out
before updating the document.
Glen
From no-reply at priceangels.com Thu May 31 14:39:03 2012
From: no-reply at priceangels.com (PriceAngels)
Date: Thu, 31 May 2012 16:08:50 +0200
Subject: Dear Customer:Souvenirs for 2012 London Olympic Games From PriceAngels
Message-ID: <0.1.12F.CC2.1CD3F36E761EEE2.0@pmta41047.emsmtp.com>
If this e-mail is not displayed pro= perly, use the following link:
[1]http://emaillink2.priceangels.com/u/gm.php?prm =aUv3Bnf3uC_143435532_220220_80616
[2] 3D"PriceAngels.com"
[3] Home = [4] New Arrivals
[5] Best Sellers = [6] Special Offers
[7] $0.99 Gadgets [8] Drop Shipping [9][im=] < a href="http://b.ems.to/fw/t/WwQ6:ko1:SyRZ2" target="_blank">
[twitter_16.png"]
[10]3D"Must
[11]3D"Free [12] 3D"Fr=
New & On Sale
? 10% OFF 10% OFF 8% OFF
[13]3D"Free [14] [15] 3D"Free = = [16] 3D"Free
[17] Wrist Watch with Date for Men= [18] 1.1-inch
Screen Stereo MP3 Play= er [19] Android4.0.3 1.5GHz 4G 8-inch Five Point Capacitive Tablet PC [20] GPS Navigator
with FM Transmitter/Middle East Map
$22.16 [DEL: $13.98 :DEL] $12.58 = [DEL: $125.82 :DEL]
$113.24<= /strong> [DEL: $65.0= 9 :DEL] $59.88
? ? 15% OFF 10% OFF
= [21] 3D"Free [22] 3D"Free [23]= 3D"Free
[24] 3D"F=
[25] Android 3.5-inc= h Touch Screen Wifi GPS Smartphone
[26] Upper TFT LCD Screen Module for NDS Lite [27] USB 2.0
Charging Data Sync Cable
Android 4.0 Ice Cream Sandwich Tablet PC <= /a>
$136.59 $9.14 [DEL: $3.32 :DEL] $2.82 [DEL: $106.48 :DEL]
$95.83
10% OFF 20% OFF 15% OFF 10% OFF
[28]= 3D"Free [29] 3D"F= [30]3D"Free [31] 3D"Free
[32] Anti-Dust Plug Stopper Headset Hole Pin Stopper
[33] Hard Back Case for iPhone 4S/4 = [34] Nikon F to
Sony NEX Lens Mount = Adapter Ring [35] Lovely Steal= ing
Money Cat Coin Bank
[DEL: $1.88 :DEL] $1.69 [DEL: $10.59 :DEL] $8.47 <= /td>
[DEL: $18.50 :DEL] $15.= 73
[DEL: $1= 5.46 :DEL] $13.14
? [DEL: 12% OFF= :DEL] 10% OFF= ?
<= tr> = [36] 3D"Free [37]3D"Free [38]= 3D"Free
[39] 3D"F=
[40] Bluetooth Wirel= ess Keyboard [41] On-ear Stereo
= Headphones = [42] SOLOPRO 228P 2.4G= 4 Channel R/C
Helicopter [43] = 4-Channel Foam R/C Helicopter Plane
$25.46 [DEL: $10.87 :DEL] $9.57 [DEL: $148.60 :DEL]
$133.74 [DEL: $97.71 :DEL]
8% OFF 10% OFF ? ?
[44]3D"Free= [45] 3D"Free [46] 3D"Free [47] 3D"Free
[48] T10 12V White Light 5-LED Car Turning Signal Light
Bulbs [49] USB 2.0 10.0M Pixels Webcam Camera fo= r PC
Laptop [50] Bluetooth Stereo= Headset Universal Cellphone
Earphone [51] RC Helicopter Copter Airplane Toy with Remote
Control
[DEL: $3= .74 :DEL] $3.44 [DEL: $5.26 :DEL] $4.73 [DEL:
$22.38 :DEL] $15.= 09
[52][3D"h=]
[53]3D"facebook" [54]Faceboo= k [55]3D"twitter" [56]twitter [57]3D"youtube" [58]youtube=
=
Note:Pl= ease do not reply to this email. if you have any questions
please [59]contact= us
Price Angels CO | Limited Flatrm /704 7/F Bright Way Tower= ,33
Mong Kok Road ,Mong Kok, Kl
Tel:+86 755 86382312. [60]Privacy= Notice
Copyright @ 2011 PriceAngels.com. All rights reserved.<= /p>
If you want to unsubscribe from our mailing = list, use the following
link:
[61]http://emaillink2.priceangels.com/u/un.php?par=aUv 3Bnf3uC_220220_80616_$sid$
[e=]
References
1. 3D"http://emaillink2.priceangels=/
2. 3D"http://emaillink2.price=/
3. 3D"http://em=/
4. 3D"http://emaillink2.priceangels=/
5. 3D"http://emaillink2.priceangels.com/u/nrd.php?p 6. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_80 7. file://localhost/tmp/3D" 8. ="http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_80616_220220 9. 3D"http://b.ems.to/fw/t/WwQM:ko 10. 3D"http://emaillink2.priceangel=/
11. 3D"http://e=/
12. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aU 13. 3D"http://ema=/
14. 3D"http://emaillink2.priceangels=/
15. 3D"http://emaillink2.priceangels.com/u/nrd.php?p 16. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_80 17. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3 18. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3B 19. 3D"http://emaillink2.priceangels.com/u/nrd.php?p 20. 3D"http://emai=/
21. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_80616_22 22. 3D"http://e=/
23. 3D"http://emaillink2.priceang=/
24. 3D"http://emaillink2.priceangels.com/u/nrd. 25. 3D"http://emaillink2.priceangels.com/u/n 26. 3D"http://emaill=/
27. ="http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_80616_220220 28. 3D"http://emaillink2.pricea=/
29. 3D"http://emaillink2.priceangels.com/u/nrd. 30. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_ 31. 3D"http:/ 32. 3D"http: 33. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_ 34. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3B 35. 3D"http://emaillink2.priceangels.com/u/ 36. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_80616 37. 3D"http://e=/
38. 3D"http://emaillink2.priceangel=/
39. 3D"http://emaillink2.priceangels.com/u/nrd. 40. 3D"http://emaillink2.priceangels.com/u/n 41. 3D"http://emaillink2.priceangels.com/u/ 42. 3D"http://emaillink2.priceangels.com/u/nrd 43. 3D"http://emaillink2.pricea=/
44. 3D"http://emaillink2.priceangels.com/u/nr 45. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_8 46. file://localhost/tmp/3D" 47. 3D"http://emaillink=/
48. 3D"http://emaill=/
49. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3uC_ 50. 3D"http://emaillink2.priceangels.com/u/nr 51. 3D"http://email=/
52. 3D"http://emaillink=/
53. 3D"http://emaillink2.pricean=/
54. 3D"http://emaillink2.priceangels.co=/
55. 3D"http://emaillink2.priceangels.com/u 56. 3D"http://emaillink2.p=/
57. 3D"http://emaillink2.priceangels.com/u/ 58. 3D"http://emaillink2.priceangels.com/u/nrd.php 59. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=aUv3Bnf3u 60. 3D"http://emaillink2.priceang=/
61. 3D"http://emaillink2.priceangels.=/
From sillyvalley at yandex.ru Thu May 31 17:03:33 2012
From: sillyvalley at yandex.ru (Borzykin Vladimir)
Date: Thu, 31 May 2012 21:03:26 +0400
Subject: Broken links at amd64 Project page
Message-ID: <64281338483806@web25h.yandex.ru>
http://www.freebsd.org/platforms/amd64.html
AMD64 Documentation -- most links redirects to AMD Support & Drivers,
actual documentation moved this way
http://developer.amd.com/documentation/guides/Pages/default.aspx
Best regards,
Vladimir
From gjb at FreeBSD.org Thu May 31 17:36:26 2012
From: gjb at FreeBSD.org (Glen Barber)
Date: Thu, 31 May 2012 13:36:23 -0400
Subject: Broken links at amd64 Project page
In-Reply-To: <64281338483806@web25h.yandex.ru>
References: <64281338483806@web25h.yandex.ru>
Message-ID: <20120531173623.GG1763@glenbarber.us>
Hi,
On Thu, May 31, 2012 at 09:03:26PM +0400, Borzykin Vladimir wrote:
> http://www.freebsd.org/platforms/amd64.html
> AMD64 Documentation -- most links redirects to AMD Support & Drivers,
>
> actual documentation moved this way
> http://developer.amd.com/documentation/guides/Pages/default.aspx
>
Thank you for the report. The page should be updating shortly with
updated links (except one I could not find a replacement for).
Regards,
Glen
From perrin at apotheon.com Thu May 31 22:57:56 2012
From: perrin at apotheon.com (Chad Perrin)
Date: Thu, 31 May 2012 16:57:55 -0600
Subject: SoC project: Complete BSD-licensed text processing tools.
In-Reply-To: <20120530185246.GK10094@acme.spoerlein.net>
References:
<20120530185246.GK10094@acme.spoerlein.net>
Message-ID: <20120531225754.GB19871@hemlock.hydra>
On Wed, May 30, 2012 at 08:52:46PM +0200, Ulrich Sp?rlein wrote:
>
> Great! Please keep me in the loop wrt. mdocml as I still hope to get it
> in the tree pre-10.x and set fire to groff.
Make it a party. I'll bring lighter fluid.
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
|