add HISTORY to ldap.1

[Rob Pierce]

Ok?

Index: ldap.1
===
RCS file: /cvs/src/usr.bin/ldap/ldap.1,v
retrieving revision 1.7
diff -u -p -r1.7 ldap.1
--- ldap.1  3 Jul 2018 10:10:09 -   1.7
+++ ldap.1  3 Jul 2018 19:19:21 -
@@ -233,6 +233,11 @@ Match Group ldapusers
 .%R RFC 4516
 .%T Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator
 .Re
+.Sh HISTORY
+The
+.Nm
+program first appeared in
+.Ox 6.4 .
 .Sh AUTHORS
 .An -nosplit
 The

ber.3 diff from last ber source commit

[Rob Pierce]

I mistakenly committed modifications to the ber.3 man page (in snmpd).

This man page is currently not linked into the build.

I am sending this diff post-commit for visibility only.

A work in progress. Comments welcome.

Regards,

Index: ber.3
===
RCS file: /cvs/src/usr.sbin/snmpd/ber.3,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -p -r1.13 -r1.14
--- ber.3   1 Oct 2013 12:48:27 -   1.13
+++ ber.3   29 Jun 2018 15:18:03 -  1.14
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ber.3,v 1.13 2013/10/01 12:48:27 reyk Exp $
+.\" $OpenBSD: ber.3,v 1.14 2018/06/29 15:18:03 rob Exp $
 .\"
 .\" Copyright (c) 2007, 2012 Reyk Floeter 
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: October 1 2013 $
+.Dd $Mdocdate: June 29 2018 $
 .Dt BER 3
 .Os
 .Sh NAME
@@ -25,8 +25,10 @@
 .Nm ber_replace_elements ,
 .Nm ber_add_sequence ,
 .Nm ber_add_set ,
+.Nm ber_add_enumerated ,
 .Nm ber_add_integer ,
 .Nm ber_get_integer ,
+.Nm ber_get_enumerated ,
 .Nm ber_add_boolean ,
 .Nm ber_get_boolean ,
 .Nm ber_add_string ,
@@ -40,10 +42,12 @@
 .Nm ber_add_eoc ,
 .Nm ber_get_eoc ,
 .Nm ber_add_oid ,
+.Nm ber_add_noid ,
 .Nm ber_add_oidstring ,
 .Nm ber_get_oid ,
 .Nm ber_oid2ber ,
 .Nm ber_string2oid ,
+.Nm ber_oid_cmp ,
 .Nm ber_printf_elements ,
 .Nm ber_scanf_elements ,
 .Nm ber_get_writebuf ,
@@ -54,7 +58,7 @@
 .Nm ber_free_elements ,
 .Nm ber_calc_len ,
 .Nm ber_set_application ,
-.Nm ber_set_writecallback
+.Nm ber_set_writecallback ,
 .Nm ber_free
 .Nd parse ASN.1 with Basic Encoding Rules
 .Sh SYNOPSIS
@@ -78,6 +82,10 @@
 .Ft "int"
 .Fn "ber_get_integer" "struct ber_element *root" "long long *val"
 .Ft "struct ber_element *"
+.Fn "ber_add_enumerated" "struct ber_element *prev" "long long val"
+.Ft "int"
+.Fn "ber_get_enumerated" "struct ber_element *root" "long long *val"
+.Ft "struct ber_element *"
 .Fn "ber_add_boolean" "struct ber_element *prev" "int bool"
 .Ft "int"
 .Fn "ber_get_boolean" "struct ber_element *root" "int *bool"
@@ -104,6 +112,8 @@
 .Ft "struct ber_element *"
 .Fn "ber_add_oid" "struct ber_element *prev" "struct ber_oid *oid"
 .Ft "struct ber_element *"
+.Fn "ber_add_noid" "struct ber_element *prev" "struct ber_oid *oid, int n"
+.Ft "struct ber_element *"
 .Fn "ber_add_oidstring" "struct ber_element *prev" "const char *string"
 .Ft "int"
 .Fn "ber_get_oid" "struct ber_element *root" "struct ber_oid *oid"
@@ -111,6 +121,8 @@
 .Fn "ber_oid2ber" "struct ber_oid *oid" "u_int8_t *buf" "size_t size"
 .Ft "int"
 .Fn "ber_string2oid" "const char *string" "struct ber_oid *oid"
+.Ft "int"
+.Fn "ber_oid_cmp" "struct ber_oid *oid" "struct ber_oid *oid"
 .Ft "struct ber_element *"
 .Fn "ber_printf_elements" "struct ber_element *prev" "char *format" "..."
 .Ft "int"
@@ -153,6 +165,8 @@ using the
 .Fn ber_add_set ,
 .Fn ber_add_integer ,
 .Fn ber_get_integer ,
+.Fn ber_add_enumerated ,
+.Fn ber_get_enumerated ,
 .Fn ber_add_boolean ,
 .Fn ber_get_boolean ,
 .Fn ber_add_string ,
@@ -182,11 +196,12 @@ struct ber_oid {
 .Ed
 .Pp
 .Fn ber_add_oid ,
+.Fn ber_add_noid ,
 .Fn ber_add_oidstring ,
 .Fn ber_get_oid ,
 .Fn ber_oid2ber ,
-.Fn ber_oid_cmp ,
 .Fn ber_string2oid
+.Fn ber_oid_cmp ,
 .Sh FORMAT STRINGS
 .Fn ber_printf_elements ,
 .Fn ber_scanf_elements
@@ -203,6 +218,7 @@ struct ber_oid {
 .Sh RETURN VALUES
 Upon successful completion
 .Fn ber_get_integer ,
+.Fn ber_get_enumerated ,
 .Fn ber_get_boolean ,
 .Fn ber_get_string ,
 .Fn ber_get_nstring ,
@@ -225,6 +241,9 @@ The
 .Nm ber
 manpage first appeared in
 .Ox 4.3 .
+.Sh STANDARDS
+ITU-T Recommendation X.690, also known as ISO/IEC 8825-1:
+Information technology - ASN.1 encoding rules.
 .Sh AUTHORS
 .An -nosplit
 The
@@ -234,5 +253,13 @@ library was written by
 .An Marc Balmer Aq Mt m...@openbsd.org
 and
 .An Reyk Floeter Aq Mt r...@openbsd.org .
+.Sh CAVEATS
+Only the subset of
+.Nm ber
+data types specified above are supported.
+.Pp
+Indefinite length
+.Nm ber
+encoding is not supported.
 .Sh BUGS
 This manpage is a stub.

Re: event.3: libevent no longer prints to stderr

[Rob Pierce]

On Fri, Aug 04, 2017 at 07:53:19PM +0200, Ingo Schwarze wrote:
> Hi Rob,
> 
> thanks for looking at libevent documentation.  It is in dire need
> of improvements in multiple respects.
> 
> Rob Pierce wrote on Fri, Aug 04, 2017 at 10:21:16AM -0400:
> 
> > As of the last commit to src/lib/libevent/log.c the library
> > no longer prints to stderr.  Update man page accordingly.
> > 
> > Ok?
> 
> But honestly, i'm not convinced that this patch is right.
> 
> Look at event.c.  EVENT_SHOW_METHOD is still inspected (line 154),
> and if it is set, the library does issue a message.
> 
> But looking at the code and at the documentation, i instantly
> see lots and lots of issues that need fixing.  Unsorted:
> 
>  * EVENT_SHOW_METHOD ought to be documented in the ENVIRONMENT
>section.  The section name "ADDITIONAL NOTES" is bogus.
> 
>  * If you document an ENVIRONMENT variable, you should also say
>which value(s) it is supposed to have (in this case, the value
>is ignored, and even an empty value counts as "set", which is
>not at all obvious).
> 
>  * The information is missing that that the variable is ignored
>in setuid and setgid programs as defined by issetugid(2).
> 
>  * Talking about "displaying" something is useless in library
>documentation.  You also have to explain where the message
>will appear.  Certainly not on stdout, right?
> 
>  * In this case, the message won't appear anywhere at all by default,
>not even in the system logs.
> 
>  * To make *any* messages from libevent appear anywhere at all,
>the application program has to supply a logging callback
>function using the public interface function
>event_set_log_callback(3).  Unfortunately, man -k tells me
>that function isn't documented anywhere at all.
>A classic case of user-level RTFS...  :-(

... and there it is! Thanks Ingo. I didn't go deep enough.

>  * Don't you dare add yet more functions to event(3).
>It is already of excessive size and conflating documentation for
>classes of functions almost unrelated to each other - like,
>what's the point of having signal_set(3) and bufferevent_read(3)
>in the same manual page?
> 
> I dimly remeber that somebody tried and started to clean this mess
> up some years ago, but wasn't persistent enough to go anywhere with
> it.  If you want to look at that and don't find it instantly, i can
> dig it up for you.  Or you can simply start from scratch, the old
> discussion didn't go so far that much would be lost starting over.
> 
> If you want to tackle this, expect several days of work,
> involving much reading of code.

I will put it on my list!

Regards,

Rob

> Yours,
>   Ingo
> 
> 
> > Index: event.3
> > ===
> > RCS file: /cvs/src/lib/libevent/event.3,v
> > retrieving revision 1.53
> > diff -u -p -r1.53 event.3
> > --- event.3 29 Jun 2017 01:25:59 -  1.53
> > +++ event.3 4 Aug 2017 14:08:44 -
> > @@ -517,10 +517,6 @@ by setting the environment variable
> >  or
> >  .Va EVENT_NOSELECT ,
> >  respectively.
> > -By setting the environment variable
> > -.Va EVENT_SHOW_METHOD ,
> > -.Nm libevent
> > -displays the kernel notification method that it uses.
> >  .Sh RETURN VALUES
> >  Upon successful completion
> >  .Fn event_add

event.3: libevent no longer prints to stderr

[Rob Pierce]

As of the last commit to src/lib/libevent/log.c the library no longer prints to
stderr. Update man page accordingly.

Ok?

Index: event.3
===
RCS file: /cvs/src/lib/libevent/event.3,v
retrieving revision 1.53
diff -u -p -r1.53 event.3
--- event.3 29 Jun 2017 01:25:59 -  1.53
+++ event.3 4 Aug 2017 14:08:44 -
@@ -517,10 +517,6 @@ by setting the environment variable
 or
 .Va EVENT_NOSELECT ,
 respectively.
-By setting the environment variable
-.Va EVENT_SHOW_METHOD ,
-.Nm libevent
-displays the kernel notification method that it uses.
 .Sh RETURN VALUES
 Upon successful completion
 .Fn event_add

getifaddrs.3 xref to if_nameindex

[Rob Pierce]

if_nameindex(3) references getifaddrs(3). A getifaddrs(3) xref back to
if_nameindex might be helpful. I found it the hard way.

Rob

Index: getifaddrs.3
===
RCS file: /cvs/src/lib/libc/net/getifaddrs.3,v
retrieving revision 1.21
diff -u -p -r1.21 getifaddrs.3
--- getifaddrs.321 Nov 2015 07:48:10 -  1.21
+++ getifaddrs.323 Jul 2017 16:54:33 -
@@ -133,6 +133,7 @@ or
 .Sh SEE ALSO
 .Xr ioctl 2 ,
 .Xr socket 2 ,
+.Xr if_nameindex 3 ,
 .Xr sysctl 3 ,
 .Xr netintro 4 ,
 .Xr ifconfig 8

ifstated.conf.5 diff

[Rob Pierce]

I am not sure that it makes sense to mention implementation details in the man
page in this regard (i.e. libevent). If people want to know the details, they
can read the source code.

In any event, true and false are not reserved words.

Regards,

Rob

Index: ifstated.conf.5
===
RCS file: /cvs/src/usr.sbin/ifstated/ifstated.conf.5,v
retrieving revision 1.9
diff -u -p -r1.9 ifstated.conf.5
--- ifstated.conf.5 24 Apr 2012 14:56:09 -  1.9
+++ ifstated.conf.5 7 Jul 2017 13:36:22 -
@@ -101,10 +101,7 @@ net = '( "ping -q -c 1 -w 1 192.168.0.1 
 .Sh TESTS AND EVENTS
 .Xr ifstated 8
 delegates the process of testing to libevent which associates a value with
-every test, in this case
-.Em true
-or
-.Em false .
+every test, in this case true or false .
 Whenever the value of a test associated with the current state changes,
 an event is triggered and the state's body is processed.
 .Sh STATE DEFINITIONS

missing punctuation in hifn.4 and hardclock.9

[Rob Pierce]

Stumbled across these in my travels.

Rob

Index: man4/hifn.4
===
RCS file: /cvs/src/share/man/man4/hifn.4,v
retrieving revision 1.50
diff -u -p -r1.50 hifn.4
--- man4/hifn.4 10 Dec 2015 21:00:51 -  1.50
+++ man4/hifn.4 27 Sep 2016 04:27:25 -
@@ -36,7 +36,7 @@
 The
 .Nm
 driver supports various cards containing the Hifn 7751, Hifn 7811, Hifn 7951,
-Hifn 7955, Hifn 7956, or Hifn 9751 chipsets, such as
+Hifn 7955, Hifn 7956, or Hifn 9751 chipsets, such as:
 .Bl -tag -width namenamenamena -offset indent
 .It Invertex AEON
 Comes as 128KB SRAM model, or 2MB DRAM model.

Index: man9/hardclock.9
===
RCS file: /cvs/src/share/man/man9/hardclock.9,v
retrieving revision 1.11
diff -u -p -r1.11 hardclock.9
--- man9/hardclock.93 Apr 2016 06:43:59 -   1.11
+++ man9/hardclock.927 Sep 2016 04:27:39 -
@@ -47,7 +47,7 @@ is an opaque, machine dependent structur
 previous machine state.
 .Pp
 .Fn hardclock
-performs a variety of time related housekeeping tasks, such as
+performs a variety of time related housekeeping tasks, such as:
 .Bl -bullet -offset indent
 .It
 If the current process has virtual or profiling interval

Re: minor updates to radiusd.8

[Rob Pierce]

New diff excluding the history section.

Rob

Index: radiusd.8
===
RCS file: /cvs/src/usr.sbin/radiusd/radiusd.8,v
retrieving revision 1.6
diff -u -p -r1.6 radiusd.8
--- radiusd.8   25 Aug 2015 01:12:59 -  1.6
+++ radiusd.8   18 Sep 2016 16:32:01 -
@@ -29,6 +29,12 @@ The
 .Nm
 daemon implements the RADIUS protocol.
 .Pp
+.Nm
+can be enabled during system boot by setting the following in
+.Pa /etc/rc.conf.local :
+.Pp
+.Dl radiusd_flags=\&"\&"
+.Pp
 The options are as follows:
 .Bl -tag -width Ds
 .It Fl d
@@ -49,7 +55,10 @@ Only check the configuration file for va
 Default configuration file.
 .El
 .Sh SEE ALSO
-.Xr radiusd.conf 5
+.Xr radiusd.conf 5 ,
+.Xr radiusctl 8 ,
+.Xr rc.conf 8
+.Sh STANDARDS
 .Rs
 .%R RFC 2865
 .%T "Remote Authentication Dial In User Service (RADIUS)"

minor updates to radiusd.8

[Rob Pierce]

Index: radiusd.8
===
RCS file: /cvs/src/usr.sbin/radiusd/radiusd.8,v
retrieving revision 1.6
diff -u -p -r1.6 radiusd.8
--- radiusd.8   25 Aug 2015 01:12:59 -  1.6
+++ radiusd.8   18 Sep 2016 15:10:26 -
@@ -29,6 +29,12 @@ The
 .Nm
 daemon implements the RADIUS protocol.
 .Pp
+.Nm
+can be enabled during system boot by setting the following in
+.Pa /etc/rc.conf.local :
+.Pp
+.Dl radiusd_flags=\&"\&"
+.Pp
 The options are as follows:
 .Bl -tag -width Ds
 .It Fl d
@@ -49,9 +55,17 @@ Only check the configuration file for va
 Default configuration file.
 .El
 .Sh SEE ALSO
-.Xr radiusd.conf 5
+.Xr radiusd.conf 5 ,
+.Xr radiusctl 8 ,
+.Xr rc.conf 8
+.Sh STANDARDS
 .Rs
 .%R RFC 2865
 .%T "Remote Authentication Dial In User Service (RADIUS)"
 .%D June 2000
 .Re
+.Sh HISTORY
+The
+.Nm
+program first appeared in
+.Ox 5.8 .

some more single user mode in /etc/rc

[Rob Pierce]

I wasn't actually looking for this, but stumbled across it while reviewing
/etc/rc.

Rob

Index: rc
===
RCS file: /cvs/src/etc/rc,v
retrieving revision 1.486
diff -u -p -r1.486 rc
--- rc  10 Jul 2016 09:08:18 -  1.486
+++ rc  5 Sep 2016 14:54:47 -
@@ -262,7 +262,7 @@ do_fsck() {
 stty status '^T'
 
 # Set shell to ignore SIGINT (2), but not children; shell catches SIGQUIT (3)
-# and returns to single user after fsck.
+# and returns to single-user mode after fsck.
 trap : 2
 trap : 3   # Shouldn't be needed.
 
@@ -289,9 +289,9 @@ if [[ $1 == shutdown ]]; then
echo warning: cannot write random seed to disk
fi
 
-   # If we are in secure level 0, assume single user mode.
+   # If we are in secure level 0, assume single-user mode.
if (($(sysctl -n kern.securelevel) == 0)); then
-   echo 'single user: not running shutdown scripts'
+   echo 'single-user mode: not running shutdown scripts'
else
pkg_scripts=${pkg_scripts%%*( )}
if [[ -n $pkg_scripts ]]; then

fix inconsistent man page use of "single user mode"

[Rob Pierce]

init.8 currently has six instances of "single-user mode" and three instances
of "single-user shell", so fix the two "single user mode" outliers.

Also, correct the only other two instances of man pages with "single user
mode" in afterboot.8 and netstart.8.


Index: init.8
===
RCS file: /cvs/src/sbin/init/init.8,v
retrieving revision 1.47
diff -u -p -r1.47 init.8
--- init.8  4 Sep 2011 18:20:48 -   1.47
+++ init.8  5 Sep 2016 12:24:32 -
@@ -68,7 +68,7 @@ file as explained in the
 .Xr rc 8
 manual.
 .It Fl s
-Boot directly into single user mode.
+Boot directly into single-user mode.
 .El
 .Pp
 Single-user mode is also entered if the boot scripts fail.
@@ -265,7 +265,7 @@ When starting a window system or
 the login class
 .Dq default
 is used.
-No resource changes are made when entering single user mode.
+No resource changes are made when entering single-user mode.
 .Sh FILES
 .Bl -tag -width /etc/rc.securelevel -compact
 .It Pa /dev/console

Index: afterboot.8
===
RCS file: /cvs/src/share/man/man8/afterboot.8,v
retrieving revision 1.156
diff -u -p -r1.156 afterboot.8
--- afterboot.8 2 Sep 2016 12:17:33 -   1.156
+++ afterboot.8 5 Sep 2016 12:29:10 -
@@ -386,7 +386,7 @@ For example:
 .Ss System command scripts
 The
 .Pa /etc/rc.*\&
-scripts are invoked at boot time, after single user mode has exited,
+scripts are invoked at boot time, after single-user mode has exited,
 and at shutdown.
 The whole process is controlled, more or less, by the master script
 .Pa /etc/rc .

Index: netstart.8
===
RCS file: /cvs/src/share/man/man8/netstart.8,v
retrieving revision 1.20
diff -u -p -r1.20 netstart.8
--- netstart.8  5 Dec 2015 18:43:12 -   1.20
+++ netstart.8  5 Sep 2016 12:29:10 -
@@ -38,7 +38,7 @@
 .Nm
 is the command script that is invoked by
 .Xr rc 8
-during an automatic reboot and after single user mode is exited;
+during an automatic reboot and after single-user mode is exited;
 it performs network initialization.
 .Pp
 The

Consistent case and full stop in rc.8

[Rob Pierce]

Index: rc.8
===
RCS file: /cvs/src/share/man/man8/rc.8,v
retrieving revision 1.42
diff -u -p -r1.42 rc.8
--- rc.821 Nov 2015 19:43:50 -  1.42
+++ rc.85 Sep 2016 11:34:57 -
@@ -194,11 +194,11 @@ not to run
 .Xr fsck 8
 during the next boot.
 .It Pa /var/run/dmesg.boot
-copy of
+Copy of
 .Xr dmesg 8
 saved by
 .Nm rc
-at boot time
+at boot time.
 .El
 .Sh SEE ALSO
 .Xr sysctl.conf 5 ,

s/separate/separated/ in pledge.2

[Rob Pierce]

Index: pledge.2
===
RCS file: /cvs/src/lib/libc/sys/pledge.2,v
retrieving revision 1.34
diff -u -p -r1.34 pledge.2
--- pledge.21 Sep 2016 10:06:30 -   1.34
+++ pledge.25 Sep 2016 11:08:34 -
@@ -126,7 +126,7 @@ once.
 .Pp
 The
 .Ar promises
-is specified as a string, with space separate keywords:
+is specified as a string, with space separated keywords:
 .Bl -tag -width "tmppath" -offset indent
 .It Va "stdio"
 The following system calls are permitted to allow most basic functions

use router instead of forwarding gateway in faq6.html

[Rob Pierce]

The Background sections in both the Networking and PF - Building a Router FAQ
use the term "router" as oppose to "forwarding gateway".

As such, be consistent with the corresponding title in faq6.html.

This may also be less confusing if relayd(8) is mentioned as providing
application layer gateway functionality as suggested in my last diff sent to
tech@.

Alternatively, if "forwarding gateway" remains, consider referencing IP and/or
network layer / layer 3 in the title.

Regards,

Rob

Index: faq6.html
===
RCS file: /cvs/www/faq/faq6.html,v
retrieving revision 1.383
diff -u -p -r1.383 faq6.html
--- faq6.html   15 Aug 2016 02:22:13 -  1.383
+++ faq6.html   4 Sep 2016 13:37:14 -
@@ -400,8 +400,7 @@ localhostLOCALHOST  UH
 BASE-ADDRESS.MCA LOCALHOST  U
 
 
-Setting up your OpenBSD box as a forwarding
-gateway
+Setting up your OpenBSD box as a router
 
 
 This is covered in more detail here.

Re: remove password advice in afterboot.8 and passwd.1

[Rob Pierce]

> From: "Jason McIntyre" <j...@kerhand.co.uk>
> To: "misc" <misc@openbsd.org>
> Sent: Monday, April 18, 2016 2:03:26 AM
> Subject: Re: remove password advice in afterboot.8 and passwd.1

> On Sun, Apr 17, 2016 at 11:23:14PM -0400, Rob Pierce wrote:
> > Stop giving password advice. Instead, make a general statement about 
> > password
> > strength in passwd.1.

> > Rob


> i don;t see why we should not try to give advice.

After reading https://marc.info/?t=14173169791=1=2 (and other articles)
I thought maybe the advice provided was no longer as relevant as it once was,
and that this advice would require maintenance in two separate documents.

However, after continued reading on the topic, maybe it is still strong advice
that will stand the test of time, good information for new users, and consistent
enough across both manual pages.

Not sure.

Rob

remove password advice in afterboot.8 and passwd.1

[Rob Pierce]

Stop giving password advice. Instead, make a general statement about password
strength in passwd.1.

Rob

Index: afterboot.8
===
RCS file: /cvs/src/share/man/man8/afterboot.8,v
retrieving revision 1.153
diff -u -p -r1.153 afterboot.8
--- afterboot.8 8 Dec 2015 13:36:05 -   1.153
+++ afterboot.8 18 Apr 2016 03:18:04 -
@@ -103,10 +103,6 @@ Change the password for the root user.
 (Note that throughout the documentation, the term
 .Dq superuser
 is a synonym for the root user.)
-Choose a password that has digits and special characters
-as well as from the upper and lower case alphabet.
-Do not choose any word in any language.
-It is common for an intruder to use dictionary attacks.
 Type the following command to change it:
 .Pp
 .Dl $ doas passwd root
@@ -594,6 +590,7 @@ is contained within
 .Xr doas 1 ,
 .Xr ksh 1 ,
 .Xr man 1 ,
+.Xr passwd 1 ,
 .Xr pkg_add 1 ,
 .Xr ps 1 ,
 .Xr vi 1 ,

Index: passwd.1
===
RCS file: /cvs/src/usr.bin/passwd/passwd.1,v
retrieving revision 1.44
diff -u -p -r1.44 passwd.1
--- passwd.126 Nov 2015 19:01:47 -  1.44
+++ passwd.118 Apr 2016 03:18:42 -
@@ -49,13 +49,10 @@ First, the user is prompted for their cu
 If the current password is correctly typed, a new password is requested.
 The new password must be entered twice to avoid typing errors.
 .Pp
-The new password should be at least six characters long and not
-purely alphabetic.
-Its total length must be less than
+Password strength is a function of length and complexity.
+The total password length must be less than
 .Dv _PASSWORD_LEN
 (currently 128 characters).
-A mixture of both lower and uppercase letters, numbers, and
-meta-characters is encouraged.
 .Pp
 The quality of the password can be enforced by specifying an external
 checking program via the

Re: man pages diff

[Rob Pierce]

> From: "Alexander Hall" <alexan...@beard.se>
> To: "Jason McIntyre" <j...@kerhand.co.uk>, "misc" <misc@openbsd.org>
> Cc: "Ingo Schwarze" <schwa...@usta.de>
> Sent: Saturday, April 9, 2016 4:15:10 AM
> Subject: Re: man pages diff

> On April 7, 2016 10:40:24 PM GMT+02:00, Jason McIntyre <j...@kerhand.co.uk>
> wrote:
> >On Thu, Apr 07, 2016 at 10:13:02PM +0200, Ingo Schwarze wrote:
> >> Hi,

> >> Jason McIntyre wrote on Thu, Apr 07, 2016 at 08:35:52PM +0100:
> >> > On Thu, Apr 07, 2016 at 03:15:01PM -0400, Rob Pierce wrote:

> >> >> Change "super user" to "superuser".

> >> > hmm. you have the weight of the man pages behind you, since they
> >> > overwhelmingly use "superuser".

> >> In that case, ...

> >> > the trouble is, i don;t think "super
> >> > user" is wrong, and i'm reluctant to do this...

I just noticed this in afterboot.1 under the "Root password" section:

"Note that throughout the documentation, the term "superuser" is a synonym for
the root user."

Rob

Re: diff for help.1

[Rob Pierce]

> From: "Pavan Maddamsetti"  
> To: "misc"  
> Sent: Friday, April 15, 2016 10:55:28 PM 
> Subject: Re: diff for help.1 
> 
> Why not ed? 

vi(1) mentions ex(1) which is maybe good enough for a new user. 

Both the "Welcome to OpenBSD" email message as well as help.1 reference man
and highlight the -k option, so maybe that is enough. Running man -k editor
lists them all. 

When I reviewed help.1, given the other commands presented (e.g. cd, ls,
cat) I would have expected some mention of a text editor to help a new
user/admin (though afterboot.1 does reference vi(1) under SEE ALSO).

Rob

Re: diff for help.1

[Rob Pierce]

On Fri, Apr 15, 2016 at 04:16:59PM -0400, Rob Pierce wrote:
> Recent FAQ cleanup lost a reference to mg(1) (section 2.2).
> 
> Text editors seem fundamental enough to include in help.1.
> 
> While here, make consistent use of references to command arguments (Ar).
> 
> Rob

Sorry - clean diff with stray comments removed.

Rob

Index: help.1
===
RCS file: /cvs/src/share/man/man1/help.1,v
retrieving revision 1.1
diff -u -p -r1.1 help.1
--- help.1  27 Mar 2015 01:59:26 -  1.1
+++ help.1  15 Apr 2016 23:40:33 -
@@ -88,7 +88,7 @@ in the system password file
 .It Cm man
 Interface to the system manual pages.
 For any of the commands listed below, type
-.Ic man 
+.Ic man Ar command
 for detailed information on what it does and how to use it.
 .It Cm pwd
 Print working directory.
@@ -109,12 +109,18 @@ Type
 for a detailed listing.
 .It Cm cat
 Although it has many more uses,
-.Ic cat filename
+.Ic cat Ar filename
 will print the contents of a plain-text file to the screen.
+.It Cm vi
+Edit text files.
+For example,
+.Ic vi Ar filename .
+See also
+.Xr mg 1 .
 .It Cm mkdir
 Make a directory.
 For example,
-.Ic mkdir foobar .
+.Ic mkdir Ar dirname .
 .It Cm rmdir
 Remove a directory.
 .It Cm rm

diff for help.1

[Rob Pierce]

Recent FAQ cleanup lost a reference to mg(1) (section 2.2).

Text editors seem fundamental enough to include in help.1.

While here, make consistent use of references to command arguments (Ar).

Rob

Index: help.1
===
RCS file: /cvs/src/share/man/man1/help.1,v
retrieving revision 1.1
diff -u -p -r1.1 help.1
--- help.1  27 Mar 2015 01:59:26 -  1.1
+++ help.1  15 Apr 2016 20:14:16 -
@@ -88,7 +88,7 @@ in the system password file
 .It Cm man
 Interface to the system manual pages.
 For any of the commands listed below, type
-.Ic man 
+.Ic man Ar command
 for detailed information on what it does and how to use it.
 .It Cm pwd
 Print working directory.
@@ -109,12 +109,20 @@ Type
 for a detailed listing.
 .It Cm cat
 Although it has many more uses,
-.Ic cat filename
+.Ic cat Ar filename
 will print the contents of a plain-text file to the screen.
+.It Cm vi
+Edit text files.
+.\" For example,
+.\" .Ic vi Ar filename .
+For example,
+.Ic vi Ar filename .
+See also
+.Xr mg 1 .
 .It Cm mkdir
 Make a directory.
 For example,
-.Ic mkdir foobar .
+.Ic mkdir Ar dirname .
 .It Cm rmdir
 Remove a directory.
 .It Cm rm

add "route" promise to pledge.2

[Rob Pierce]

I wasn't sure of where to put it in the list.

How is this?

Rob

Index: pledge.2
===
RCS file: /cvs/src/lib/libc/sys/pledge.2,v
retrieving revision 1.27
diff -u -p -r1.27 pledge.2
--- pledge.211 Mar 2016 06:36:51 -  1.27
+++ pledge.27 Apr 2016 20:00:19 -
@@ -80,7 +80,8 @@ Only the
 and
 .Dv FIONBIO
 operations are allowed by default.
-Use of the "tty" and "ioctl" promises receive more ioctl requests.
+Use of the "tty", "ioctl", "route", "pf" and "audio" promises receive more 
ioctl
+requests.
 .Pp
 .It Xr chmod 2
 .It Xr fchmod 2
@@ -493,6 +494,21 @@ process:
 .Xr setrlimit 2 ,
 .Xr getpriority 2 ,
 .Xr setpriority 2 .
+.It Va "route"
+Allows a subset of
+.Xr ioctl 2
+operations on network interfaces:
+.Pp
+.Dv SIOCGIFADDR ,
+.Dv SIOCGIFFLAGS ,
+.Dv SIOCGIFMETRIC ,
+.Dv SIOCGIFGMEMB ,
+.Dv SIOCGIFRDOMAIN ,
+.Dv SIOCGIFDSTADDR_IN6 ,
+.Dv SIOCGIFNETMASK_IN6 ,
+.Dv SIOCGNBRINFO_IN6 ,
+.Dv SIOCGIFINFO_IN6 ,
+.Dv SIOCGIFMEDIA .
 .It Va "pf"
 Allows a subset of
 .Xr ioctl 2

man pages diff

[Rob Pierce]

Change "super user" to "superuser".

Rob

Index: src/share/man/man4/pty.4
===
RCS file: /cvs/src/share/man/man4/pty.4,v
retrieving revision 1.21
diff -u -p -r1.21 pty.4
--- src/share/man/man4/pty.421 Nov 2015 08:04:20 -  1.21
+++ src/share/man/man4/pty.47 Apr 2016 19:12:07 -
@@ -298,7 +298,7 @@ device nodes following the naming conven
 .Ox .
 Since
 .Pa ptm
-impersonates the super user for some operations it needs to perform
+impersonates the superuser for some operations it needs to perform
 to complete the allocation of a pseudo terminal, the
 .Pa /dev
-directory must also be writeable by the super user.
+directory must also be writeable by the superuser.

Index: src/share/man/man5/login.conf.5
===
RCS file: /cvs/src/share/man/man5/login.conf.5,v
retrieving revision 1.62
diff -u -p -r1.62 login.conf.5
--- src/share/man/man5/login.conf.5 30 Mar 2016 06:58:06 -  1.62
+++ src/share/man/man5/login.conf.5 7 Apr 2016 19:12:07 -
@@ -683,7 +683,7 @@ to indicate if the user is in group whee
 Some authentication types require the user to be in group wheel when using
 the
 .Xr su 1
-program to become super user.
+program to become superuser.
 .El
 .Pp
 When the authentication program is executed,

Index: src/usr.sbin/cron/crontab.1
===
RCS file: /cvs/src/usr.sbin/cron/crontab.1,v
retrieving revision 1.33
diff -u -p -r1.33 crontab.1
--- src/usr.sbin/cron/crontab.1 26 Oct 2015 15:50:06 -  1.33
+++ src/usr.sbin/cron/crontab.1 7 Apr 2016 19:12:07 -
@@ -65,7 +65,7 @@ be listed in the
 .Pa /var/cron/cron.deny
 file in order to use
 .Nm .
-If neither of these files exists then only the super user
+If neither of these files exists then only the superuser
 will be allowed to use
 .Nm .
 .Em NOTE :

faq4.html

[Rob Pierce]

It looks like the cdrkit web site has been down for a while.

Point to the debian package instead, or maybe delete altogether?

Rob

Index: faq4.html
===
RCS file: /cvs/www/faq/faq4.html,v
retrieving revision 1.439
diff -u -p -r1.439 faq4.html
--- faq4.html   1 Apr 2016 15:25:47 -   1.439
+++ faq4.html   2 Apr 2016 14:15:51 -
@@ -266,7 +266,7 @@ In OpenBSD, you can create a CD from an 
 
 Modern Windows and Macintosh systems can directly create CDs from ISO images.
 On Linux or other Unix-like systems, use applications such as
-http://www.cdrkit.org/;>cdrkit.
+https://packages.debian.org/source/sid/cdrkit;>cdrkit.
 
 4.3.3 - Floppies

Re: faq12.html

[Rob Pierce]

> From: "Nick Holland" 
> To: "misc" 
> Sent: Wednesday, March 30, 2016 12:14:23 PM
> Subject: Re: faq12.html

> On 03/30/16 08:49, Theo Buehler wrote:
> >> -The Zaurus has very little current available on its USB port, so many
> >> +The Zaurus has very little currently available on its USB port, so many

> > electrical current?

> both what is there and "electrical current" are/would be precisely
> correct, but "power" might be a more understood word.

> Nick.
I must admit that was a bit of helicopter editing on my part, so it caught me 
off guard. 

Changing "little" to "low" would solve any ambiguity. 

I am embarrassed to say that I studied electrical circuits way back when... 

Re: faq12.html

[Rob Pierce]

> From: "Theo Buehler" 
> To: "misc" 
> Sent: Wednesday, March 30, 2016 8:50:20 AM
> Subject: Re: faq12.html

> > -The Zaurus has very little current available on its USB port, so many
> > +The Zaurus has very little currently available on its USB port, so many

> electrical current?

> > USB devices will not work if they are directly attached to it.
> > You will need to use a powered USB hub to run these devices.
Yes, my mistake. Sorry for the noise. 

faq12.html

[Rob Pierce]

For your consideration.

Index: faq12.html
===
RCS file: /cvs/www/faq/faq12.html,v
retrieving revision 1.125
diff -u -p -r1.125 faq12.html
--- faq12.html  29 Mar 2016 01:27:39 -  1.125
+++ faq12.html  30 Mar 2016 12:30:48 -
@@ -662,7 +662,7 @@ on SIMH page.
 
 12.7.1 - USB devices aren't working properly
 
-The Zaurus has very little current available on its USB port, so many
+The Zaurus has very little currently available on its USB port, so many
 USB devices will not work if they are directly attached to it.
 You will need to use a powered USB hub to run these devices.

reference ipsec.conf in ipsec.4 under SEE ALSO?

[Rob Pierce]

I think it make sense for ipsec.4 to reference it's own configuration file 
under SEE ALSO.

Index: ipsec.4
===
RCS file: /cvs/src/share/man/man4/ipsec.4,v
retrieving revision 1.83
diff -u -p -r1.83 ipsec.4
--- ipsec.4 16 Feb 2015 16:38:54 -  1.83
+++ ipsec.4 18 Mar 2016 20:51:05 -
@@ -378,6 +378,7 @@ allocations).
 .\".Xr ipcomp 4 ,
 .Xr options 4 ,
 .Xr iked 8 ,
+.Xr ipsec.conf 5 ,
 .Xr ipsecctl 8 ,
 .Xr isakmpd 8 ,
 .Xr sysctl 8

minor corrections diff for 59.html

[Rob Pierce]

Some punctuation, case and grammer corrections along with a few hrefs.

For your consideration.

Index: 59.html
===
RCS file: /cvs/www/59.html,v
retrieving revision 1.72
diff -u -p -r1.72 59.html
--- 59.html 16 Mar 2016 19:10:52 -  1.72
+++ 59.html 18 Mar 2016 19:48:20 -
@@ -120,7 +120,7 @@ to 5.9.
 driver now supports sector mode for eMMC devices, such as those found 
on
 some BeagleBone Black boards.
 The http://www.openbsd.org/cgi-bin/man.cgi?query=cnmac;>cnmac(4)
-driver now supports checksum offloading
+driver now supports checksum offloading.
 The http://www.openbsd.org/cgi-bin/man.cgi?query=ipmi;>ipmi(4)
 driver now supports OpenIPMI compatible character device.
 ...
@@ -171,7 +171,7 @@ to 5.9.
 
 Userland programs were audited so that they could be properly annotated
 with pledge(2).
-This resulted in design changes such as
+This resulted in design changes such as:
 
 
 addition of
@@ -206,17 +206,17 @@ to 5.9.
 
 SMP network stack improvements:
 
-The task processing incoming packets can now runs mostly in parallel
+The task processing incoming packets can now run mostly in parallel
 of the rest of the kernel, this include:
 
 http://www.openbsd.org/cgi-bin/man.cgi?query=carp;>carp(4),
 http://www.openbsd.org/cgi-bin/man.cgi?query=trunk;>trunk(4),
 http://www.openbsd.org/cgi-bin/man.cgi?query=vlan;>vlan(4)
 and other pseudo-driver with the exception of
-http://www.openbsd.org/cgi-bin/man.cgi?query=bridge;>bridge(4)
-Ethernet decapsulation, ARP processing and MPLS forwarding path
+http://www.openbsd.org/cgi-bin/man.cgi?query=bridge;>bridge(4).
+Ethernet decapsulation, ARP processing and MPLS forwarding path.
 http://www.openbsd.org/cgi-bin/man.cgi?query=bpf;>bpf(4)
-filter matching
+filter matching.
 
 The Rx and Tx rings of the
 http://www.openbsd.org/cgi-bin/man.cgi?query=ix;>ix(4),
@@ -228,10 +228,10 @@ to 5.9.
 http://www.openbsd.org/cgi-bin/man.cgi?query=gem;>gem(4),
 http://www.openbsd.org/cgi-bin/man.cgi?query=re;>re(4) and
 http://www.openbsd.org/cgi-bin/man.cgi?query=cas;>cas(4)
-drivers can now be processed in parallel of the rest of the kernel
+drivers can now be processed in parallel of the rest of the kernel.
 The Rx ring of the
 http://www.openbsd.org/cgi-bin/man.cgi?query=cnmac;>cnmac(4)
-driver can now be processed in parallel of the rest of the kernel
+driver can now be processed in parallel of the rest of the kernel.
 
 
 
@@ -401,13 +401,20 @@ to 5.9.
 and reduce dynamic linking overhead.
 Handle intra-thread kills via new
 http://www.openbsd.org/cgi-bin/man.cgi?query=thrkill;>thrkill(2)
-system call to tighten pledge(2) restrictions and improve 
pthread_kill(3)
-and pthread_cancel(3) compliance.
+system call to tighten
+http://www.openbsd.org/cgi-bin/man.cgi?query=pledge;>pledge(2).
+restrictions and improve
+http://www.openbsd.org/cgi-bin/man.cgi?query=pthread_kill;>pthread_kill(3)
+and
+http://www.openbsd.org/cgi-bin/man.cgi?query=pthread_cancel;>pthread_cancel(3)
+compliance.
 Added http://www.openbsd.org/cgi-bin/man.cgi?query=getpwnam_shadow;>
 getpwnam_shadow(3)
 and http://www.openbsd.org/cgi-bin/man.cgi?query=getpwuid_shadow;>
 getpwuid_shadow(3)
-to permit tighter pledge(2) restrictions.
+to permit tighter
+http://www.openbsd.org/cgi-bin/man.cgi?query=pledge;>pledge(2).
+restrictions.
 Added support to
 http://www.openbsd.org/cgi-bin/man.cgi?query=ktrace;>ktrace(1)
 the arguments to
@@ -525,7 +532,7 @@ to 5.9.
 based on draft-rsa-dsa-sha2-256-03.txt and
 draft-ssh-ext-info-04.txt.
   http://www.openbsd.org/cgi-bin/man.cgi?query=ssh;>ssh(1):
-Add an AddKeysToAgent client option which can be set to
+add an AddKeysToAgent client option which can be set to
 yes, no, ask, or confirm, and
 defaults to no.  When enabled, a private key that is used
 during authentication will be added to
@@ -578,7 +585,7 @@ to 5.9.
 http://www.openbsd.org/cgi-bin/man.cgi?query=sshd;>sshd(8):
 refine compatibility workarounds for WinSCP.
   Fix a number of memory faults (double-free, free of uninitialised
-memory, etc) in
+memory, etc.) in
 http://www.openbsd.org/cgi-bin/man.cgi?query=ssh;>ssh(1)
 and
 http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-keygen;>ssh-keygen(1).
@@ -676,7 +683,7 @@ to 5.9.
 http://www.openbsd.org/cgi-bin/man.cgi?query=sshd;>sshd(8):
 fix some option parsing memory 

Re: reference ipsec.conf in ipsec.4 under SEE ALSO?

[Rob Pierce]

> From: "Jason McIntyre" <j...@kerhand.co.uk>
> To: "misc" <misc@openbsd.org>
> Sent: Friday, March 18, 2016 5:40:07 PM
> Subject: Re: reference ipsec.conf in ipsec.4 under SEE ALSO?

> On Fri, Mar 18, 2016 at 04:59:29PM -0400, Rob Pierce wrote:
>> I think it make sense for ipsec.4 to reference it's own configuration file 
>> under
> > SEE ALSO.


> fixed, thanks. but note SEE ALSO is sorted by section first, so it should
> be after the options Xr.

> jmc
I totally missed that, thanks! 

Rob 

Re: httpd syscall 72

[Rob Pierce]

>From Stuart in response to a previous inquiry:

Rob

> >> If you need a working version, the diffs aren't committed yet, so you can
> >> rebuild httpd from source and it should work fine.
> >> 
> > Thanks for the info Ted. I'm currently rebuilding the src, following the 
> > "5 - Building the System from Source" page. I just want to ask another 
> > question, can I just rebuild only the httpd from source? Thanks again.
> 
> Yes,
> 
> $ cd /usr/src/usr.sbin/httpd
> $ cvs up -PdA
> $ make obj && make depend && make
> $ su root -c 'make install'
> 

Thank you very much Stuart!

Re: update/upgrade

[Rob Pierce]

On Sun, Sep 20, 2015 at 10:36:12PM -0400, Quartz wrote:
> >Does your embedded storage run NOR/NAND or something like SDHC Memory
> >Cards?
> >
> >If your systems are running SDHC you can easily create clones with a
> >laptop&  the DD utility.
> 
> A couple of them do, but it doesn't matter in this case. The main issue with
> compiling is that it can effectively knock the system offline for hours
> which isn't acceptable. Any process that involves shutting the machine off
> or booting into a separate OS image has the same problem.
> 
> It's just a question of minimizing downtime.

If availability is critical you might consider redundancy with CARP/pfsync.

Re: anoncvs.html.head

[Rob Pierce]

> Thanks Stuart. I am preparing a new diff which I will send shortly.

I am holding off on sending the next diff until I figure out how to ensure
that my diff does not get mangled by my email client. In particular, a
hash (#) in an HTML anchor tag seems to get hosed by my zimbra web client.

Playing with fetchmail, sendmail and mutt on my new OpenBSD desktop.

Almost there...

Rob

anoncvs.html.head

[Rob Pierce]

Simplified diff for consideration.

I kept the change from "file sets" to "source files" as "file sets" has
special meaning in the OpenBSD installation process.

Also, only href the first instances of cvs(1).

Regards,

Index: anoncvs.html.head
===
RCS file: /cvs/www/build/mirrors/anoncvs.html.head,v
retrieving revision 1.42
diff -u -p -r1.42 anoncvs.html.head
--- anoncvs.html.head   2 Sep 2015 13:11:30 -   1.42
+++ anoncvs.html.head   14 Sep 2015 01:01:28 -
@@ -39,7 +39,7 @@ source repositories:
 
   src - Houses all source code for the OpenBSD Operating System.
   ports - Houses the OpenBSD 
Ports.
-  www - Houses all OpenBSD web pages. (Including this one).
+  www - Houses all OpenBSD web pages (including this one).
   xenocara - Houses OpenBSD's active X.org v7 source tree.
   X11 and XF4 - Houses OpenBSD's adaptation of the
   http://www.XFree86.org/;>XFree86-3 and XFree86-4
@@ -135,17 +135,18 @@ Assuming the downloaded files, src.t
 
 
 
-Not all people will wish to unpack all the file sets, but as the system
+Not all people will wish to unpack all the source files, but as the system
 must be kept in sync, you will generally need to set up all trees.
 
 
-You can also just use cvs(1) to "checkout" the source repository
+You can also just use
+http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/cvs.1?query=cvs
+to "checkout" the source repository
 for you. This is discussed in the next section.
 
 
 After this, /usr/src will be a nice checkout area where all
-http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>
-cvs(1) commands will work properly.
+cvs(1) commands will work properly.
 
 Using CVS to Get and Update your 
 Source Tree
@@ -166,10 +167,10 @@ CVS server you are going to use.  A list
 
 
 Once you have chosen which Anonymous CVS Server you will
-use, you can start using cvs. For those of you
+use, you can start using cvs(1). For those of you
 who have CDs you can start with the CVS checkout that is on the CD by using
 the method above to get the sources onto your system.
-If you don't have a CD handy, use the method below to checkout the sources.
+If you don't have a CD handy, use the method below to checkout the sources:
 
 
 First, start out by `get'-ing an initial tree:
@@ -210,9 +211,11 @@ Confirm this, and the fingerprint will t
...
 
 
+
 Note that the above format with SHA256 fingerprints was added after the
 release of OpenBSD 5.6; older versions only use MD5 fingerprints.
 
+
  Anytime afterwards, to `update' this tree:
  (If you are following current):
 
@@ -234,7 +237,7 @@ to merge changes in.
  NOTE:
 If you are updating a source tree that you initially fetched
 from a different server, or from a CD, you must
-add the -d [cvsroot] option to cvs.
+add the -d [cvsroot] option to cvs:
 
# cd /usr/src
# cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd
@@ -299,7 +302,7 @@ operation and get thoroughly involved in
 before getting "commit" access -- as a result of showing useful
 skills and high quality results they will naturally later be given
 developer access.
-As well, people providing patches can create their "diff"s relative
+As well, people providing patches can create their diffs relative
 to the CVS tree, which will ease integration.
 
 Example usages for cvs(1)

Re: Question about quotation rules

[Rob Pierce]

Hey Anthony,

- Original Message -
> From: "Anthony J. Bentley" <anth...@anjbe.name>
> To: "Rob Pierce" <r...@2keys.ca>
> Cc: "misc" <misc@openbsd.org>
> Sent: Saturday, September 12, 2015 12:26:04 AM
> Subject: Re: Question about quotation rules

> Hi Rob,
> 
> Rob Pierce writes:
>> Good evening,
>> 
>> Is there a written/unwritten rule for using quotation marks? Do man pages and
>>  web pages follow the same rules?
>> 
>> When would I use 'this', "this", `this', ``this'', “this“, etc.?
> 
> Generally:
> 
> In manuals, use .Dq and .Sq for double and single quotes.
> 
> In www, use " and '.
> 
> 
> There are some other macros in mdoc(7) that generate quote marks (.Qq
> and friends), when you specifically need straight quotes (e.g., code
> listings) and can't just type " directly (e.g., on a macro line).
> 
> For personal webpages I use UTF-8 quotes (U+2019/A, U+201C/D) directly.
> But for pages with many authors, like www.openbsd.org, it's best to go
> with what's simple and works: " and '. Keep the burden on authors light.
> The text is what's important.
> 
> `` '' is an artifact. The only place they look balanced is on the console
> and in troff's PDF output. Everywhere else (such as the xterm and firefox
> defaults) has displayed this unbalanced for years. " looks better and is
> easier to type.
> 
> --
> Anthony J. Bentley

Great - that is the guidance I was looking for. Thanks!

Re: Question about quotation rules

[Rob Pierce]

- Original Message -
> From: "Random832" <random...@fastmail.com>
> To: "misc" <misc@openbsd.org>
> Sent: Friday, September 11, 2015 8:09:10 PM
> Subject: Re: Question about quotation rules

> Rob Pierce <r...@2keys.ca> writes:
> 
>> Good evening,
>>
>> Is there a written/unwritten rule for using quotation marks? Do man
>> pages and web pages follow the same rules?
>>
>> When would I use 'this', "this", `this', ``this'', “this“, etc.?
>>
>> I guess this can be both a source problem as well as a display problem.
>>
>> Any suggestions regarding reasonable expectations for web page/man
>> page consistency?
> 
> There are macros for quotes in manpages in mdoc(7). The rendering is
> device-dependent - on terminals, it will be unicode quotation marks in
> unicode locales, and ``this'' in non-unicode locales.

Ok - thanks for your response. I have been looking at mdoc...

security.html

[Rob Pierce]

Simplified diff. Full stop and standard unidirectional quotation marks.

Rob

Index: security.html
===
RCS file: /cvs/www/security.html,v
retrieving revision 1.422
diff -u -p -r1.422 security.html
--- security.html   2 Jul 2015 05:49:04 -   1.422
+++ security.html   14 Sep 2015 03:25:38 -
@@ -112,7 +112,7 @@ skills.
 Some members of our security auditing team worked for Secure Networks,
 the company that made the industry's premier network security scanning
 software package Ballista (Secure Networks got purchased by Network
-Associates, Ballista got renamed to Cybercop Scanner, and well...)
+Associates, Ballista got renamed to Cybercop Scanner, and well...).
 That company did a lot of security research, and thus fit in well
 with the OpenBSD stance.  OpenBSD passed Ballista's tests with flying
 colours since day 1.
@@ -126,8 +126,8 @@ have fixed many simple and obvious carel
 and only months later discovered that the problems were in fact
 exploitable.  (Or, more likely someone on
 http://online.securityfocus.com/archive/1;>BUGTRAQ
-would report that other operating systems were vulnerable to a `newly
-discovered problem', and then it would be discovered that OpenBSD had
+would report that other operating systems were vulnerable to a "newly
+discovered problem", and then it would be discovered that OpenBSD had
 been fixed in a previous release).  In other cases we have been saved
 from full exploitability of complex step-by-step attacks because we
 had fixed one of the intermediate steps.  An example of where we
@@ -165,7 +165,7 @@ written somewhere, but perhaps not taken
 The Reward
 
 Our proactive auditing process has really paid off.  Statements like
-``This problem was fixed in OpenBSD about 6 months ago'' have become
+"This problem was fixed in OpenBSD about 6 months ago" have become
 commonplace in security forums like
 http://online.securityfocus.com/archive/1;>BUGTRAQ.

Re: anoncvs.html.head

[Rob Pierce]

- Original Message -
> From: "Stuart Henderson" <s...@spacehopper.org>
> To: "misc" <misc@openbsd.org>
> Sent: Saturday, September 12, 2015 11:58:29 AM
> Subject: Re: anoncvs.html.head

> On 2015-09-11, Rob Pierce <r...@2keys.ca> wrote:
>>src - Houses all source code for the OpenBSD Operating System.
>>ports - Houses the OpenBSD 
>> Ports.
>> -  www - Houses all OpenBSD web pages. (Including this one).
>> +  www - Houses all OpenBSD web pages (including this one).
> 
> I like that
> 
>>xenocara - Houses OpenBSD's active X.org v7 source tree.
>>X11 and XF4 - Houses OpenBSD's adaptation of the
>>http://www.XFree86.org/;>XFree86-3 and XFree86-4
>> @@ -122,7 +122,7 @@ with only one part of the tree.  The two
>>  which contains the files used to create the kernel, and src.tar.gz
>>  which contains all the other "userland" utilities.
>>  In general, however, you will usually want both of them installed.
>> -Assuming the downloaded files, src.tar.gz,
>> +Assuming the downloaded files src.tar.gz,
>> sys.tar.gz and xenocara.tar.gz are in /usr:
> 
> I think this was OK as it was
> 
>> 
>> -Not all people will wish to unpack all the file sets, but as the system
>> +Not all people will wish to unpack all the source file, but as the system
>>  must be kept in sync, you will generally need to set up all trees.
> 
> and this (and the new sentence doesn't quite make sense)
> 
>> 
>> -You can also just use cvs(1) to "checkout" the source repository
>> +You can also just use
>> +> href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1)
>> +to "checkout" the source repository
>>  for you. This is discussed in the next section.
> 
> OK I guess, though I don't think we need to hyperlink every instance of
> a program name
> 
>> @@ -160,16 +162,12 @@ from the errata>  For more information on these "flavors" of OpenBSD, see
>> here.
>>  
>> -Once you have decided which tree to follow, you must choose which 
>> Anonymous
>> -CVS server you are going to use.  A list of these servers is
>> -below.
>> -
>> 
>> -Once you have chosen which Anonymous CVS Server you 
>> will
>> -use, you can start using cvs. For those of you
>> +Once you have decided which tree to follow, and which > href="#CVSROOT">Anonymous CVS Server you will
> 
> Please try and keep <80 columns in the source file where sensible
> 
>> +use, you can start using > href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1).
>> For those of you
>>  who have CDs you can start with the CVS checkout that is on the CD by using
>>  the method above to get the sources onto your 
>> system.
>> -If you don't have a CD handy, use the method below to checkout the sources.
>> +If you don't have a CD handy, use the method below to checkout the sources:
>>  
>> 
>> First, start out by `get'-ing an initial tree:
>> @@ -210,9 +208,11 @@ Confirm this, and the fingerprint will t
>>  ...
>> 
>>  
>> +
>>  Note that the above format with SHA256 fingerprints was added after the
>>  release of OpenBSD 5.6; older versions only use MD5 fingerprints.
>>  
>> +
>>  Anytime afterwards, to `update' this tree:
>>  (If you are following current):
>> 
>> @@ -234,7 +234,7 @@ to merge changes in.
>>  NOTE:
>>  If you are updating a source tree that you initially fetched
>>  from a different server, or from a CD, you must
>> -add the -d [cvsroot] option to cvs.
>> +add the -d [cvsroot] option to cvs:
>> 
>>  # cd /usr/src
>>  # cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd
>> @@ -295,11 +295,11 @@ directory, and a subsequent update will
>>  
>> 
>>  The anoncvs service gives fledgling developers a chance to learn CVS
>> -operation and get thoroughly involved in the development process
>> +operations and get thoroughly involved in the development process
> 
> "operation" already seem ok
> 
>>  before getting "commit" access -- as a result of showing useful
>>  skills and high quality results they will naturally later be given
>>  developer access.
>> -As well, people providing patches can create their "diff"s relative
>> +As well, people providing patches can create their diffs relative
>>  to the CVS tree, which will ease integration.
>>  
> > Example usages for cvs(1)

Thanks Stuart. I am preparing a new diff which I will send shortly.

Re: anoncvs.html.head

[Rob Pierce]

Thanks Benny. I will review again and resubmit.

Some responses in-line below.

- Original Message -
> From: "Benny Lofgren" <bl-li...@lofgren.biz>
> To: "misc" <misc@openbsd.org>
> Sent: Saturday, September 12, 2015 8:01:58 AM
> Subject: Re: anoncvs.html.head

> Hi Rob,
> 
> On 2015-09-12 01:15, Rob Pierce wrote:
>> This diff is a resend against the correct file:
>>  - some punctuation, line spacing and minor grammar fixes
>>  - "file sets" has a special meaning, so don't refer to src.tar.gz,
>>  xenocara.tar.gc,ports.tar.gz as "file sets"
>>  - cvs(1) hrefs
>>  - "diffs" is already used earlier on the page, so don't quote it
>> Index: anoncvs.html.head
>> ===
>> RCS file: /cvs/www/build/mirrors/anoncvs.html.head,v
>> retrieving revision 1.42
>> diff -u -p -r1.42 anoncvs.html.head
>> --- anoncvs.html.head2 Sep 2015 13:11:30 -   1.42
>> +++ anoncvs.html.head11 Sep 2015 22:10:15 -
> 
> Just a few comments inline below. I think you posted this or a similar
> diff to tech@ the other day, so maybe this is in the wrong place, but
> I'll leave the comment as well in misc@ to avoid confusion.
> 
> 
> ...
>> @@ -135,11 +135,13 @@ Assuming the downloaded files, src.t
>>  
>>  
>>  
>> -Not all people will wish to unpack all the file sets, but as the system
>> +Not all people will wish to unpack all the source file, but as the system
> 
> I think "source files" (plural), alternatively "all of the source file"
> depending on your intention?

Yes, I missed that - thanks.

> 
>>  must be kept in sync, you will generally need to set up all trees.
>>  
>>  
>> -You can also just use cvs(1) to "checkout" the source repository
>> +You can also just use
>> +> href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1)
>> +to "checkout" the source repository
> 
> Is that the correct URL? The use of "sektion" (which is a Swedish,
> Danish or German spelling :-) ) instead of "sec" caught my eye.
> 
> When I do the same search directly from www.openbsd.org I get this:
> 
> http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/cvs.1?query=cvs=1
> 
> (I realize that the link you used is the same one already used elsewhere
> in this page. But even if I copy and paste that link into my browser,
> the web server redirects it to the one I pasted here. Maybe there is
> some legacy stuff going on here, perhaps a server side change not yet
> reflected in all of the html pages?)

I will look into that. I must admit that I tend to grab existing text to
complete an href, but in the future I will do the lookup and grab the
actual URL. I was wondering were sektion came from!

>>  for you. This is discussed in the next section.
>>  
>>  
>> @@ -160,16 +162,12 @@ from the errata>  For more information on these "flavors" of OpenBSD, see
>>  here.
>>  
>> -Once you have decided which tree to follow, you must choose which 
>> Anonymous
>> -CVS server you are going to use.  A list of these servers is
>> -below.
>> -
>>  
>> -Once you have chosen which Anonymous CVS Server you 
>> will
>> -use, you can start using cvs. For those of you
>> +Once you have decided which tree to follow, and which > href="#CVSROOT">Anonymous CVS Server you will
>> +use, you can start using > href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1).
>> For those of you
> 
> I don't know about you or the developers, but personally I kind of
> prefer the original wording and paragraph division, except I would
> change the second paragraph's repetitious use of "Once you have..." to
> something like "When you have..." instead.

Ok. I should stay away from "style" changes, and stick to obvious corrections
and/or functional text changes. This just seemed a bit awkward to me.

> 
> 
> And maybe remove the second href to the cvs server list. I don't know
> about official policy here, but having several identical links so close
> to each other in a text always confuses me and makes me click on all of
> them, only to be annoyed I end up in the same place. :-)
> 
> One objection to this would be that people who only read the second
> paragraph in this example would miss the link altogether. I would then
> contend that if you don't have the habit and patience of reading ALL the
> relevant parts of a given piece of documentation

Re: ftp.html

[Rob Pierce]

Thanks Stuart - I totally missed that! I will also correct my anoncvs.html diff 
and resend against the correct file(s). Appreciate the response.

How about this?

Index: ftp.html.head
===
RCS file: /cvs/www/build/mirrors/ftp.html.head,v
retrieving revision 1.21
diff -u -p -r1.21 ftp.html.head
--- ftp.html.head   25 Jul 2015 19:16:47 -  1.21
+++ ftp.html.head   11 Sep 2015 21:09:36 -
@@ -61,7 +61,7 @@ upgrade your system very quickly.
 Download via
   HTTP/FTP
 
-OpenBSD can be also easily installed via HTTP or FTP.
+OpenBSD can also be obtained via HTTP or FTP.
 Typically you need a single small piece of boot media (e.g., a boot floppy)
 and then the rest of the files can be installed from a number of locations,
 including directly off the Internet.

Re: anoncvs.html.head

[Rob Pierce]

See attached.

- Original Message -
From: "Rob Pierce" <r...@2keys.ca>
To: "misc" <misc@openbsd.org>
Sent: Friday, September 11, 2015 6:30:33 PM
Subject: anoncvs.html.head

This diff is a resend against the correct file:

 - some punctuation, line spacing and minor grammar fixes
 - "file sets" has a special meaning, so don't refer to src.tar.gz, 
xenocara.tar.gc,ports.tar.gz as "file sets"
 - cvs(1) hrefs
 - "diffs" is already used earlier on the page, so don't quote it

Rob
Index: anoncvs.html.head
===
RCS file: /cvs/www/build/mirrors/anoncvs.html.head,v
retrieving revision 1.42
diff -u -p -r1.42 anoncvs.html.head
--- anoncvs.html.head   2 Sep 2015 13:11:30 -   1.42
+++ anoncvs.html.head   11 Sep 2015 22:10:15 -
@@ -39,7 +39,7 @@ source repositories:
 
   src - Houses all source code for the OpenBSD Operating System.
   ports - Houses the OpenBSD 
Ports.
-  www - Houses all OpenBSD web pages. (Including this one).
+  www - Houses all OpenBSD web pages (including this one).
   xenocara - Houses OpenBSD's active X.org v7 source tree.
   X11 and XF4 - Houses OpenBSD's adaptation of the
   http://www.XFree86.org/;>XFree86-3 and XFree86-4
@@ -122,7 +122,7 @@ with only one part of the tree.  The two
 which contains the files used to create the kernel, and src.tar.gz
 which contains all the other "userland" utilities.
 In general, however, you will usually want both of them installed.
-Assuming the downloaded files, src.tar.gz,
+Assuming the downloaded files src.tar.gz,
 sys.tar.gz and xenocara.tar.gz are in /usr:
 
 
@@ -135,11 +135,13 @@ Assuming the downloaded files, src.t
 
 
 
-Not all people will wish to unpack all the file sets, but as the system
+Not all people will wish to unpack all the source file, but as the system
 must be kept in sync, you will generally need to set up all trees.
 
 
-You can also just use cvs(1) to "checkout" the source repository
+You can also just use
+http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1)
+to "checkout" the source repository
 for you. This is discussed in the next section.
 
 
@@ -160,16 +162,12 @@ from the erratahere.
 
-Once you have decided which tree to follow, you must choose which Anonymous
-CVS server you are going to use.  A list of these servers is
-below.
-
 
-Once you have chosen which Anonymous CVS Server you will
-use, you can start using cvs. For those of you
+Once you have decided which tree to follow, and which Anonymous CVS Server you will
+use, you can start using http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1).
 For those of you
 who have CDs you can start with the CVS checkout that is on the CD by using
 the method above to get the sources onto your system.
-If you don't have a CD handy, use the method below to checkout the sources.
+If you don't have a CD handy, use the method below to checkout the sources:
 
 
 First, start out by `get'-ing an initial tree:
@@ -210,9 +208,11 @@ Confirm this, and the fingerprint will t
...
 
 
+
 Note that the above format with SHA256 fingerprints was added after the
 release of OpenBSD 5.6; older versions only use MD5 fingerprints.
 
+
  Anytime afterwards, to `update' this tree:
  (If you are following current):
 
@@ -234,7 +234,7 @@ to merge changes in.
  NOTE:
 If you are updating a source tree that you initially fetched
 from a different server, or from a CD, you must
-add the -d [cvsroot] option to cvs.
+add the -d [cvsroot] option to cvs:
 
# cd /usr/src
# cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd
@@ -295,11 +295,11 @@ directory, and a subsequent update will 
 
 
 The anoncvs service gives fledgling developers a chance to learn CVS
-operation and get thoroughly involved in the development process
+operations and get thoroughly involved in the development process
 before getting "commit" access -- as a result of showing useful
 skills and high quality results they will naturally later be given
 developer access.
-As well, people providing patches can create their "diff"s relative
+As well, people providing patches can create their diffs relative
 to the CVS tree, which will ease integration.
 
 Example usages for cvs(1)

anoncvs.html.head

[Rob Pierce]

This diff is a resend against the correct file:

 - some punctuation, line spacing and minor grammar fixes
 - "file sets" has a special meaning, so don't refer to src.tar.gz, 
xenocara.tar.gc,ports.tar.gz as "file sets"
 - cvs(1) hrefs
 - "diffs" is already used earlier on the page, so don't quote it

Rob


Index: anoncvs.html.head
===
RCS file: /cvs/www/build/mirrors/anoncvs.html.head,v
retrieving revision 1.42
diff -u -p -r1.42 anoncvs.html.head
--- anoncvs.html.head   2 Sep 2015 13:11:30 -   1.42
+++ anoncvs.html.head   11 Sep 2015 22:10:15 -
@@ -39,7 +39,7 @@ source repositories:
 
   src - Houses all source code for the OpenBSD Operating System.
   ports - Houses the OpenBSD 
Ports.
-  www - Houses all OpenBSD web pages. (Including this one).
+  www - Houses all OpenBSD web pages (including this one).
   xenocara - Houses OpenBSD's active X.org v7 source tree.
   X11 and XF4 - Houses OpenBSD's adaptation of the
   http://www.XFree86.org/;>XFree86-3 and XFree86-4
@@ -122,7 +122,7 @@ with only one part of the tree.  The two
 which contains the files used to create the kernel, and src.tar.gz
 which contains all the other "userland" utilities.
 In general, however, you will usually want both of them installed.
-Assuming the downloaded files, src.tar.gz,
+Assuming the downloaded files src.tar.gz,
 sys.tar.gz and xenocara.tar.gz are in /usr:
 
 
@@ -135,11 +135,13 @@ Assuming the downloaded files, src.t
 
 
 
-Not all people will wish to unpack all the file sets, but as the system
+Not all people will wish to unpack all the source file, but as the system
 must be kept in sync, you will generally need to set up all trees.
 
 
-You can also just use cvs(1) to "checkout" the source repository
+You can also just use
+http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1)
+to "checkout" the source repository
 for you. This is discussed in the next section.
 
 
@@ -160,16 +162,12 @@ from the erratahere.
 
-Once you have decided which tree to follow, you must choose which Anonymous
-CVS server you are going to use.  A list of these servers is
-below.
-
 
-Once you have chosen which Anonymous CVS Server you will
-use, you can start using cvs. For those of you
+Once you have decided which tree to follow, and which Anonymous CVS Server you will
+use, you can start using http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1).
 For those of you
 who have CDs you can start with the CVS checkout that is on the CD by using
 the method above to get the sources onto your system.
-If you don't have a CD handy, use the method below to checkout the sources.
+If you don't have a CD handy, use the method below to checkout the sources:
 
 
 First, start out by `get'-ing an initial tree:
@@ -210,9 +208,11 @@ Confirm this, and the fingerprint will t
...
 
 
+
 Note that the above format with SHA256 fingerprints was added after the
 release of OpenBSD 5.6; older versions only use MD5 fingerprints.
 
+
  Anytime afterwards, to `update' this tree:
  (If you are following current):
 
@@ -234,7 +234,7 @@ to merge changes in.
  NOTE:
 If you are updating a source tree that you initially fetched
 from a different server, or from a CD, you must
-add the -d [cvsroot] option to cvs.
+add the -d [cvsroot] option to cvs:
 
# cd /usr/src
# cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd
@@ -295,11 +295,11 @@ directory, and a subsequent update will 
 
 
 The anoncvs service gives fledgling developers a chance to learn CVS
-operation and get thoroughly involved in the development process
+operations and get thoroughly involved in the development process
 before getting "commit" access -- as a result of showing useful
 skills and high quality results they will naturally later be given
 developer access.
-As well, people providing patches can create their "diff"s relative
+As well, people providing patches can create their diffs relative
 to the CVS tree, which will ease integration.
 
 Example usages for cvs(1)

[demime 1.01d removed an attachment of type text/x-patch which had a name of 
cvs.diff.anoncvs.html.head]

Question about quotation rules

[Rob Pierce]

Good evening,

Is there a written/unwritten rule for using quotation marks? Do man pages and 
web pages follow the same rules?

When would I use 'this', "this", `this', ``this'', “this“, etc.?

I guess this can be both a source problem as well as a display problem.

Any suggestions regarding reasonable expectations for web page/man page 
consistency?

U+0022  QUOTATION MARK  "
U+0027  APOSTROPHE  '
U+0060  GRAVE ACCENT`
U+00B4  ACUTE ACCENT´ 
U+2018  LEFT SINGLE QUOTATION MARK  ‘
U+2019  RIGHT SINGLE QUOTATION MARK ’
U+201C  LEFT DOUBLE QUOTATION MARK  “
U+201D  RIGHT DOUBLE QUOTATION MARK ”

Many thanks.

Rob

Re: ftp.html

[Rob Pierce]

Agreed about the word order. How about this?

Index: ftp.html
===
RCS file: /cvs/www/ftp.html,v
retrieving revision 1.673
diff -u -p -r1.673 ftp.html
--- ftp.html25 Jul 2015 19:24:18 -  1.673
+++ ftp.html11 Sep 2015 12:30:18 -
@@ -61,7 +61,7 @@ upgrade your system very quickly.
 Download via
   HTTP/FTP
 
-OpenBSD can be also easily installed via HTTP or FTP.
+OpenBSD can also be easily obtained via HTTP or FTP.
 Typically you need a single small piece of boot media (e.g., a boot floppy)
 and then the rest of the files can be installed from a number of locations,
 including directly off the Internet.

ftp.html

[Rob Pierce]

Reword since FTP is no longer used for installation (although the files can 
still be obtained via FTP).

Index: ftp.html
===
RCS file: /cvs/www/ftp.html,v
retrieving revision 1.673
diff -u -p -r1.673 ftp.html
--- ftp.html25 Jul 2015 19:24:18 -  1.673
+++ ftp.html11 Sep 2015 12:30:18 -
@@ -61,7 +61,7 @@ upgrade your system very quickly.
 Download via
   HTTP/FTP
 
-OpenBSD can be also easily installed via HTTP or FTP.
+OpenBSD can be also easily obtained via HTTP or FTP.
 Typically you need a single small piece of boot media (e.g., a boot floppy)
 and then the rest of the files can be installed from a number of locations,
 including directly off the Internet.

faq2.html

[Rob Pierce]

A few full stops and some line spacing.

Rob

Index: faq2.html
===
RCS file: /cvs/www/faq/faq2.html,v
retrieving revision 1.127
diff -u -p -r1.127 faq2.html
--- faq2.html   2 Jul 2015 05:49:04 -   1.127
+++ faq2.html   10 Sep 2015 14:47:30 -
@@ -117,7 +117,7 @@ a message body of "help".
 
 Your subscription to the OpenBSD mail lists can also be maintained through
 the web interface at
-http://lists.openbsd.org;>http://lists.openbsd.org
+http://lists.openbsd.org;>http://lists.openbsd.org.
 
 
 Some of the more popular OpenBSD mailing lists
@@ -345,7 +345,7 @@ characters?
 
 
 This is helpful to get the man page straight, with no non-printable
-characters.
+characters.
 Example:
 
 
@@ -641,7 +641,7 @@ ddb> show panic
 ddb> 
 
 
-In this case, the panic string was "Kernel: page fault trap, code=0"
+In this case, the panic string was "Kernel: page fault trap, code=0".
 
 
 Special note for SMP systems:
@@ -709,7 +709,7 @@ ddb 
 
 This tells us what function calls lead to the crash.
 
-To find out the particular line of C code that caused the crash, you can do 
the following:
+To find out the particular line of C code that caused the crash, you can do 
the following:
 Find the source file where the crashing function is defined in.
 In this example, that would be pf_route() in sys/net/pf.c.
 Recompile that source file with debug information:
@@ -732,7 +732,7 @@ In the output, grep for the function nam
 
 
 Take this first hex number and add the offset from the 'Stopped at' line:
-0x7d88 + 0x263 == 0x7feb.
+0x7d88 + 0x263 == 0x7feb.
 Scroll down to that line
 (the assembler instruction should match the one quoted in the 'Stopped at' 
line),
 then up to the nearest C line number:

href in faq3.html

[Rob Pierce]

Regards,

Index: faq3.html
===
RCS file: /cvs/www/faq/faq3.html,v
retrieving revision 1.93
diff -u -p -r1.93 faq3.html
--- faq3.html   2 Jul 2015 05:49:04 -   1.93
+++ faq3.html   11 Sep 2015 01:15:20 -
@@ -139,7 +139,7 @@ CD is always closer than any mirror. Acc
 In the same directory as the installation sets, each mirror includes a file
 named SHA256 which contains checksums of the various installation files.  You
 can confirm that none of the downloaded files were mangled in transit using
-the sha256(1) command:
+the http://www.openbsd.org/cgi-bin/man.cgi?query=sha256sektion=1;>sha256(1)
 command:
 
 
 $ sha256 -c SHA256

faq6.html correction

[Rob Pierce]

For your consideration.

Rob

Index: faq6.html
===
RCS file: /cvs/www/faq/faq6.html,v
retrieving revision 1.300
diff -u -p -r1.300 faq6.html
--- faq6.html   16 Aug 2012 02:40:18 -  1.300
+++ faq6.html   1 Sep 2012 15:06:57 -
@@ -1882,7 +1882,7 @@ itself synchronized to, the
 a collection of publicly available time servers.
 Once your clock is accurately set, ntpd will hold it at a high
 degree of accuracy, however, if your clock is more than a few minutes
-off, it is ihighly/i recommended that you bring it to close to
+off, it is ihighly/i recommended that you bring it close to
 accurate initially, as it may take days or weeks to bring a very-off
 clock to sync.
 You can do this using the tt-s/tt option of ntpd(8) or any other

/etc/changelist update to comments

[Rob Pierce]

For your consideration.

Rob

Index: changelist
===
RCS file: /cvs/src/etc/changelist,v
retrieving revision 1.76
diff -u -p -r1.76 changelist
--- changelist  20 Sep 2012 12:51:43 -  1.76
+++ changelist  13 Oct 2012 23:32:41 -
@@ -3,7 +3,7 @@
 # List of files which the security script backs up and checks
 # for modifications.
 #
-# Files prefixed with a '+' will have their md5 checksums stored,
+# Files prefixed with a '+' will have their checksums stored,
 # not the actual files.
 #

Re: OpenBSD forked

[Rob Pierce]

11 1010101

- Original Message -
From: Peter J. Philipp p...@centroid.eu
To: Theo de Raadt dera...@cvs.openbsd.org
Cc: open...@laufenberg.ch, t...@tedunangst.com, misc@openbsd.org
Sent: Sunday, June 17, 2012 3:31:36 PM
Subject: Re: OpenBSD forked

Repost: Failed HP 360 Install from USB attached CD

[Rob Pierce]

Good afternoon,

My apologies - the previous post was a little mangled.

I have just attempted an install of the latest snapshot cd51.iso - dated 
07/04/2012 5:55:00 PM on some new HP 360 servers.

I am able to boot of the CD, but the boot hangs immediately after the following 
line is displayed:

   brgphy3 at bnx3 phy1: BCM5709 10/100/100baseT PHY, rev. 8

(see full dmesg below)

This is also the case when trying to install by booting off the OpenBSD 5.0 CD 
disk 1 (and cd50.iso).

I was able to install on the HP 360 servers by moving drives over from an HP 
120 (which didn't have the same problem) with BSD already installed, booting 
off bsd.rd from disk, and reinstalling over the network, and subsequent 
installations booting to bsd.rd on disk to sd1 and swapping drives, etc.

As such, I have OpenBSD 5.0 running on our HP 360 servers, but have never been 
able to boot and install from a USB attached CD (or USB memory stick).

I should mention that when installing I also have a USB attached key board in 
addition to the USB attached CD Drive (see dmesg output below).

This is an inconvenience more than anything, but it might point to some 
underlying issues?

Has anyone seen similar problems?

Many thanks.

Rob

= = = = = USB Keyboard attach, detach, and reattach = = = = =

uhidev2 at uhub4 port 1 configuration 1 interface 0 GASIA GASIA USB KB Pro 
rev 1.10/2.10 addr 2
uhidev2: iclass 3/1
ukbd1 at uhidev2: 8 modifier keys, 6 key codes
wskbd2 at ukbd1 mux 1
wskbd2: connecting to wsdisplay0
uhidev3 at uhub4 port 1 configuration 1 interface 1 GASIA GASIA USB KB Pro 
rev 1.10/2.10 addr 2
uhidev3: iclass 3/0, 2 report ids
uhid0 at uhidev3 reportid 1: input=2, output=0, feature=0
uhid1 at uhidev3 reportid 2: input=1, output=0, feature=0
wskbd2: disconnecting from wsdisplay0
wskbd2 detached
ukbd1 detached
uhidev2 detached
uhid0 detached
uhid1 detached
uhidev3 detached
uhidev2 at uhub4 port 1 configuration 1 interface 0 GASIA GASIA USB KB Pro 
rev 1.10/2.10 addr 2
uhidev2: iclass 3/1
ukbd1 at uhidev2: 8 modifier keys, 6 key codes
wskbd2 at ukbd1 mux 1
wskbd2: connecting to wsdisplay0
uhidev3 at uhub4 port 1 configuration 1 interface 1 GASIA GASIA USB KB Pro 
rev 1.10/2.10 addr 2
uhidev3: iclass 3/0, 2 report ids
uhid0 at uhidev3 reportid 1: input=2, output=0, feature=0
uhid1 at uhidev3 reportid 2: input=1, output=0, feature=0

= = = = = USB attached CD Drive = = = = =

wskbd2: disconnecting from wsdisplay0
wskbd2 detached
ukbd1 detached
uhidev2 detached
uhid0 detached
uhid1 detached
uhidev3 detached
uhidev2 at uhub4 port 1 configuration 1 interface 0 GASIA GASIA USB KB Pro 
rev 1.10/2.10 addr 2
uhidev2: iclass 3/1
ukbd1 at uhidev2: 8 modifier keys, 6 key codes
wskbd2 at ukbd1 mux 1
wskbd2: connecting to wsdisplay0
uhidev3 at uhub4 port 1 configuration 1 interface 1 GASIA GASIA USB KB Pro 
rev 1.10/2.10 addr 2
uhidev3: iclass 3/0, 2 report ids
uhid0 at uhidev3 reportid 1: input=2, output=0, feature=0
uhid1 at uhidev3 reportid 2: input=1, output=0, feature=0
umass0 at uhub1 port 7 configuration 1 interface 0 MediaTek Inc MT1836 rev 
2.00/0.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus3 at umass0: 2 targets, initiator 0
cd0 at scsibus3 targ 1 lun 0: HL-DT-ST, DVDRAM GP10NW20, 1.03 SCSI0 5/cdrom 
removable serial.0e8d1836B3H5824_
cd0 detached
scsibus3 detached
umass0 detached

= = = = = dmesg (USB devices were not present at reboot) = = = = =

OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACP

   
I,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,

   PDCM,DCA,SSE4.1,SSE4.2,POPCNT,AES
real mem  = 3747340288 (3573MB)
avail mem = 3675979776 (3505MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xf, SMBIOS 
rev. 2.7 @  
  0xdf7fe000 (127 entries)
bios0: vendor HP version P68 date 05/05/2011
bios0: HP ProLiant DL360 G7
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP SPCR MCFG HPET  SPMI ERST APIC SRAT  BERT HEST 
DMAR SSDT SS
   DT SSDT SSDT SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 20 (application processor)
cpu1: Intel(R)