SEO

On 2007/04/19 13:33, Russell McGregor wrote:
> This fixes command line argument parsing issue in Bug ID: 5441

Well, there were two patches in my PR, and one of them, under the
heading "Another is to break backward compatibility", is what you
posted, along with the doc and usage() patches to go with it.

http://cvs.openbsd.org/cgi-bin/query...s&numbers=5441

Since we have had a release since the change was introduced, I think
the most sensible option would be to adjust the documentation to match
current behaviour, rather than change things twice.

The pfctl(8) manual hasn't matched the legal format since the
getopt(3) portability fix last September. I think this should be
mentioned in upgrade41.html; here is possible wording.

Index: faq/upgrade41.html
================================================== =================
RCS file: /data/cvsroot/OpenBSD/www/faq/upgrade41.html,v
retrieving revision 1.22
diff -u -p -r1.22 upgrade41.html
--- faq/upgrade41.html 12 Apr 2007 23:52:51 -0000 1.22
+++ faq/upgrade41.html 19 Apr 2007 07:38:32 -0000
@@ -350,6 +350,14 @@ So before when running "sysctl hw.sensor
Update your
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd.conf&amp;sektion=5"
>sensorsd.conf(5)</a> file to reflect the new names of your sensors.
+
+<p>
+<li><b>pfctl(8) -o flag no longer accepts whitespace</b><br>
+Due to a getopt(3) change, made for portability reasons, use of the <tt>-o</tt>
+flag with pfctl(8) has changed. Where followed by the optional <b>none</b>,
+<b>basic</b> or <b>profile</b>, whitespace must be removed. To disable the
+ruleset optimizer, use "<tt>pfctl -onone</tt>". Other flags to pfctl(8)
+are unaffected since their arguments are not optional.
</ul>

<a name="etcfiles"></a>