Re: Just to understand, ARM64 has SMP and ARM32 does not? &, OpenBSD design fine with ARM's weak mem coherency?

[Peter Hessler]

On 2017 Feb 26 (Sun) at 03:56:33 + (+), Tinker wrote:
:Hi misc,
:
:I just wanted to understand what's going on with SMP on ARM -
:
:Did I get it right, that ARM64 has SMP (as of the patches this week), but
:ARM32 does not have SMP and will not get it too?
:
:What was the reason for not implementing SMP on ARM32? (I only need SMP on
:ARM64 so just wanted to ask as to understand what's going on.)

Someone did the workd.  And someone didn't do the work.


-- 
A man wrapped up in himself makes a very small package.

Just to understand, ARM64 has SMP and ARM32 does not? &, OpenBSD design fine with ARM's weak mem coherency?

[Tinker]

Hi misc,

I just wanted to understand what's going on with SMP on ARM -

Did I get it right, that ARM64 has SMP (as of the patches this week), 
but ARM32 does not have SMP and will not get it too?


What was the reason for not implementing SMP on ARM32? (I only need SMP 
on ARM64 so just wanted to ask as to understand what's going on.)



Also, is there any confrontation between OpenBSD's design and ARM's weak 
memory coherency model? (In contrast with AMD64/I386/SPARC64 which all 
have a strong model.)


Thanks!
Tinker

Re: Getting http to work

[Kevin Gerrard]

OpenBSD 6.0
I had this happen to me a few days ago. I set httpd.conf up to use "*"  at
first just to cut down on hiccups. When I had it up and working with php,
and mariadb I changed   "*" to"192.168.3.254" and restarted
httpd.conf. It did not work, even after a reboot. So I put the "*" back in
just  so I could go populate mariadb 10 and php 7. After reading these
emails today it made me remember that, and so I logged into it and changed
it back to the "192.168.3.254" instead of "*", and restarted httpd. I
thought I was going to reproduce the hiccup but instead the dadgum thing
worked!!!

No problems here at all but I did want to say for whatever reason it was,
this exact anomaly did happen to me once also, however upon trying to
reproduce it I could not. 

The only thing I can think of is that I "might" not have rebooted? I really
doubt that is it but a lot on my mind lately and it could easily have been.

Kevin Gerrard

-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Currell Berry
Sent: Saturday, February 25, 2017 5:32 PM
To: Monah Baki
Cc: ludovic coues; openbsd-misc
Subject: Re: Getting http to work

Monah Baki writes:

> # httpd -dnv
> configuration OK
>
> #  rcctl - start httpd
> doing _rc_parse_conf
> doing _rc_quirks
> httpd_flags empty, using default ><
> doing _rc_parse_conf /var/run/rc.d/httpd doing _rc_quirks doing 
> rc_check httpd doing rc_pre configuration OK doing rc_start doing 
> _rc_wait start doing rc_check doing _rc_write_runfile
> (ok)
>
> # /etc/rc.d/httpd start
> httpd(ok)
>
> cat /var/log/messages
>
> Feb 25 15:35:22 nebula httpd[94632]: parent: send server: Can't assign 
> requested address Feb 25 15:36:06 nebula httpd[14026]: parent: send 
> server: Can't assign requested address
>
>
> vi httpd.conf
>
> # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $
>
> #
> # Macros
> #
> ext_addr="*"
>
> #
> # Global Options
> #
> # prefork 3
>
> #
> # Servers
> #
>
> # A minimal default server
> server "default" {
> listen on $ext_addr port 80
> }
>
>
>
> Thanks
>
>
> On Sat, Feb 25, 2017 at 3:27 PM, ludovic coues  wrote:
>> # rcctl - start httpd
>> This command should give you some details on what isn't working.
>> If not, you can try `# httpd -nvv` to check your config and `# httpd 
>> -d` to run httpd directly.
>>
>> 2017-02-25 21:20 GMT+01:00 Monah Baki :
>>> Changing to ext_addr="*"
>>>
>>>
>>> # /etc/rc.d/httpd start
>>> httpd(failed)
>>>
>>> Nothing shows up in /var/log/messages
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Feb 25, 2017 at 12:00 PM, Currell Berry 
wrote:

 Monah Baki writes:

> Hi all,
>
> Installed a fresh install of OpenBSD 6.0 on VMWare workstation and 
> wanted to run default webserver.
>
> In the messages logs I find the following error:
>
>  httpd[23792]: parent: send server: Can't assign requested address
>
>
> em0: flags=8843 mtu 1500
> lladdr 00:0c:29:b3:81:f8
> index 1 priority 0 llprio 3
> groups: egress
> media: Ethernet autoselect (1000baseT full-duplex,master)
> status: active
> inet 192.168.60.129 netmask 0xff00 broadcast 
> 192.168.60.255
>
> In my httpd.conf all I changed was the "ext_addr" Macro, everything
else as is.
>
> $ cat /etc/httpd.conf
> # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $
>
> #
> # Macros
> #
> ext_addr="192.168.60.129"
> # A minimal default server
> server "default" {
> listen on $ext_addr port 80 }
>
>
>
>
> Thank you
> Monah

 Did you try

  ext_addr="*"

 yet?

 Does it report the same error with that in place?

 -- Currell
>>>
>>
>>
>>
>> --
>>
>> Cordialement, Coues Ludovic
>> +336 148 743 42

Some ideas:
You might have an instance of httpd running in the background stopping a
new one from binding to the port.

Run the following commands and examine the output to check what could be
there

# netstat -na -f inet | grep LISTEN
# ps ax

Kill all running instances of httpd, or anything else that is binding to
port 80.

Once you've done that, try starting httpd in no-fork mode and see what
it says:

# httpd -dv

If it still doesn't work, try a different port (change 80 to  for
instance).

-- Currell

Re: Getting http to work

[Monah Baki]

# netstat -na -f inet | grep LISTEN
tcp  0  0  127.0.0.1.25   *.*LISTEN
tcp  0  0  *.22   *.*LISTEN
# httpd -dv
startup
parent: send server: Can't assign requested address
# logger exiting, pid 24061
server exiting, pid 96224
server exiting, pid 68259
server exiting, pid 94930


It's a fresh install so I wasn't expecting any ports listening. Even
if I changed to port 8080 same issue.


Thanks

On Sat, Feb 25, 2017 at 6:31 PM, Currell Berry  wrote:
>
> Monah Baki writes:
>
>> # httpd -dnv
>> configuration OK
>>
>> #  rcctl - start httpd
>> doing _rc_parse_conf
>> doing _rc_quirks
>> httpd_flags empty, using default ><
>> doing _rc_parse_conf /var/run/rc.d/httpd
>> doing _rc_quirks
>> doing rc_check
>> httpd
>> doing rc_pre
>> configuration OK
>> doing rc_start
>> doing _rc_wait start
>> doing rc_check
>> doing _rc_write_runfile
>> (ok)
>>
>> # /etc/rc.d/httpd start
>> httpd(ok)
>>
>> cat /var/log/messages
>>
>> Feb 25 15:35:22 nebula httpd[94632]: parent: send server: Can't assign
>> requested address
>> Feb 25 15:36:06 nebula httpd[14026]: parent: send server: Can't assign
>> requested address
>>
>>
>> vi httpd.conf
>>
>> # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $
>>
>> #
>> # Macros
>> #
>> ext_addr="*"
>>
>> #
>> # Global Options
>> #
>> # prefork 3
>>
>> #
>> # Servers
>> #
>>
>> # A minimal default server
>> server "default" {
>> listen on $ext_addr port 80
>> }
>>
>>
>>
>> Thanks
>>
>>
>> On Sat, Feb 25, 2017 at 3:27 PM, ludovic coues  wrote:
>>> # rcctl - start httpd
>>> This command should give you some details on what isn't working.
>>> If not, you can try `# httpd -nvv` to check your config and `# httpd
>>> -d` to run httpd directly.
>>>
>>> 2017-02-25 21:20 GMT+01:00 Monah Baki :
 Changing to ext_addr="*"


 # /etc/rc.d/httpd start
 httpd(failed)

 Nothing shows up in /var/log/messages






 On Sat, Feb 25, 2017 at 12:00 PM, Currell Berry  
 wrote:
>
> Monah Baki writes:
>
>> Hi all,
>>
>> Installed a fresh install of OpenBSD 6.0 on VMWare workstation and
>> wanted to run default webserver.
>>
>> In the messages logs I find the following error:
>>
>>  httpd[23792]: parent: send server: Can't assign requested address
>>
>>
>> em0: flags=8843 mtu 1500
>> lladdr 00:0c:29:b3:81:f8
>> index 1 priority 0 llprio 3
>> groups: egress
>> media: Ethernet autoselect (1000baseT full-duplex,master)
>> status: active
>> inet 192.168.60.129 netmask 0xff00 broadcast 192.168.60.255
>>
>> In my httpd.conf all I changed was the "ext_addr" Macro, everything else 
>> as is.
>>
>> $ cat /etc/httpd.conf
>> # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $
>>
>> #
>> # Macros
>> #
>> ext_addr="192.168.60.129"
>> # A minimal default server
>> server "default" {
>> listen on $ext_addr port 80
>> }
>>
>>
>>
>>
>> Thank you
>> Monah
>
> Did you try
>
>  ext_addr="*"
>
> yet?
>
> Does it report the same error with that in place?
>
> -- Currell

>>>
>>>
>>>
>>> --
>>>
>>> Cordialement, Coues Ludovic
>>> +336 148 743 42
>
> Some ideas:
> You might have an instance of httpd running in the background stopping a
> new one from binding to the port.
>
> Run the following commands and examine the output to check what could be there
>
> # netstat -na -f inet | grep LISTEN
> # ps ax
>
> Kill all running instances of httpd, or anything else that is binding to
> port 80.
>
> Once you've done that, try starting httpd in no-fork mode and see what
> it says:
>
> # httpd -dv
>
> If it still doesn't work, try a different port (change 80 to  for 
> instance).
>
> -- Currell

Re: Getting http to work

[Currell Berry]

Monah Baki writes:

> # httpd -dnv
> configuration OK
>
> #  rcctl - start httpd
> doing _rc_parse_conf
> doing _rc_quirks
> httpd_flags empty, using default ><
> doing _rc_parse_conf /var/run/rc.d/httpd
> doing _rc_quirks
> doing rc_check
> httpd
> doing rc_pre
> configuration OK
> doing rc_start
> doing _rc_wait start
> doing rc_check
> doing _rc_write_runfile
> (ok)
>
> # /etc/rc.d/httpd start
> httpd(ok)
>
> cat /var/log/messages
>
> Feb 25 15:35:22 nebula httpd[94632]: parent: send server: Can't assign
> requested address
> Feb 25 15:36:06 nebula httpd[14026]: parent: send server: Can't assign
> requested address
>
>
> vi httpd.conf
>
> # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $
>
> #
> # Macros
> #
> ext_addr="*"
>
> #
> # Global Options
> #
> # prefork 3
>
> #
> # Servers
> #
>
> # A minimal default server
> server "default" {
> listen on $ext_addr port 80
> }
>
>
>
> Thanks
>
>
> On Sat, Feb 25, 2017 at 3:27 PM, ludovic coues  wrote:
>> # rcctl - start httpd
>> This command should give you some details on what isn't working.
>> If not, you can try `# httpd -nvv` to check your config and `# httpd
>> -d` to run httpd directly.
>>
>> 2017-02-25 21:20 GMT+01:00 Monah Baki :
>>> Changing to ext_addr="*"
>>>
>>>
>>> # /etc/rc.d/httpd start
>>> httpd(failed)
>>>
>>> Nothing shows up in /var/log/messages
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Feb 25, 2017 at 12:00 PM, Currell Berry  
>>> wrote:

 Monah Baki writes:

> Hi all,
>
> Installed a fresh install of OpenBSD 6.0 on VMWare workstation and
> wanted to run default webserver.
>
> In the messages logs I find the following error:
>
>  httpd[23792]: parent: send server: Can't assign requested address
>
>
> em0: flags=8843 mtu 1500
> lladdr 00:0c:29:b3:81:f8
> index 1 priority 0 llprio 3
> groups: egress
> media: Ethernet autoselect (1000baseT full-duplex,master)
> status: active
> inet 192.168.60.129 netmask 0xff00 broadcast 192.168.60.255
>
> In my httpd.conf all I changed was the "ext_addr" Macro, everything else 
> as is.
>
> $ cat /etc/httpd.conf
> # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $
>
> #
> # Macros
> #
> ext_addr="192.168.60.129"
> # A minimal default server
> server "default" {
> listen on $ext_addr port 80
> }
>
>
>
>
> Thank you
> Monah

 Did you try

  ext_addr="*"

 yet?

 Does it report the same error with that in place?

 -- Currell
>>>
>>
>>
>>
>> --
>>
>> Cordialement, Coues Ludovic
>> +336 148 743 42

Some ideas:
You might have an instance of httpd running in the background stopping a
new one from binding to the port.

Run the following commands and examine the output to check what could be there

# netstat -na -f inet | grep LISTEN
# ps ax

Kill all running instances of httpd, or anything else that is binding to
port 80.

Once you've done that, try starting httpd in no-fork mode and see what
it says:

# httpd -dv

If it still doesn't work, try a different port (change 80 to  for instance).

-- Currell

Re: Conventional config file syntax? and IP address polling question

[Gregor Best]

Hi Mario,

On Sat, Feb 25, 2017 at 02:59:40PM -0600, Mario Campos wrote:
> [...]
> These configuration settings should probably be in a configuration file. I
> read somewhere on the interwebs that OpenBSD config files try to resemble
> each other, or rather, they try to keep to a format/style. Is this
> format/style documented anywhere? Or is there a C library that I should be
> using?
> [...]

pfctl's parse.y should be a good starting point. It's not exactly a
library but provides things like macros, string handling and file
includes for nearly free.

> [...]
> The second question I have is around polling the interface for its IP
> address. Correct me if I'm wrong, but I don't think it's possible to
> register a callback for whenever the interface changes its IP address,
> right? Instead, this daemon will have to poll it periodically?
> [...]

You could use route(4) for that. It has RTM_{NEW,DEL}ADDR messages that
seem to do what you need.

-- 
Gregor

Conventional config file syntax? and IP address polling question

[Mario Campos]

Hi, misc@

I'm planning to develop a semi-generic daemon to serve as a dynamic DNS
client. It seems most of the big-name DNS providers (easyDNS, DynDNS, Dynu,
etc) follow a semi-consistent "API" for updating a domain name's IP address:

http[s]://:@?hostname==&...

These configuration settings should probably be in a configuration file. I
read somewhere on the interwebs that OpenBSD config files try to resemble
each other, or rather, they try to keep to a format/style. Is this
format/style documented anywhere? Or is there a C library that I should be
using? None of my googling has revealed anything. I am thinking something
like this:

interface em0 {
  hostname example.com {
username john
password secret
uri https://api.cp.easydns.com/dyn/generic.php   # I use easyDNS
  }
}


The second question I have is around polling the interface for its IP
address. Correct me if I'm wrong, but I don't think it's possible to
register a callback for whenever the interface changes its IP address,
right? Instead, this daemon will have to poll it periodically?

Thanks!

Re: Getting http to work

[Monah Baki]

# httpd -dnv
configuration OK

#  rcctl - start httpd
doing _rc_parse_conf
doing _rc_quirks
httpd_flags empty, using default ><
doing _rc_parse_conf /var/run/rc.d/httpd
doing _rc_quirks
doing rc_check
httpd
doing rc_pre
configuration OK
doing rc_start
doing _rc_wait start
doing rc_check
doing _rc_write_runfile
(ok)

# /etc/rc.d/httpd start
httpd(ok)

cat /var/log/messages

Feb 25 15:35:22 nebula httpd[94632]: parent: send server: Can't assign
requested address
Feb 25 15:36:06 nebula httpd[14026]: parent: send server: Can't assign
requested address


vi httpd.conf

# $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $

#
# Macros
#
ext_addr="*"

#
# Global Options
#
# prefork 3

#
# Servers
#

# A minimal default server
server "default" {
listen on $ext_addr port 80
}



Thanks


On Sat, Feb 25, 2017 at 3:27 PM, ludovic coues  wrote:
> # rcctl - start httpd
> This command should give you some details on what isn't working.
> If not, you can try `# httpd -nvv` to check your config and `# httpd
> -d` to run httpd directly.
>
> 2017-02-25 21:20 GMT+01:00 Monah Baki :
>> Changing to ext_addr="*"
>>
>>
>> # /etc/rc.d/httpd start
>> httpd(failed)
>>
>> Nothing shows up in /var/log/messages
>>
>>
>>
>>
>>
>>
>> On Sat, Feb 25, 2017 at 12:00 PM, Currell Berry  
>> wrote:
>>>
>>> Monah Baki writes:
>>>
 Hi all,

 Installed a fresh install of OpenBSD 6.0 on VMWare workstation and
 wanted to run default webserver.

 In the messages logs I find the following error:

  httpd[23792]: parent: send server: Can't assign requested address


 em0: flags=8843 mtu 1500
 lladdr 00:0c:29:b3:81:f8
 index 1 priority 0 llprio 3
 groups: egress
 media: Ethernet autoselect (1000baseT full-duplex,master)
 status: active
 inet 192.168.60.129 netmask 0xff00 broadcast 192.168.60.255

 In my httpd.conf all I changed was the "ext_addr" Macro, everything else 
 as is.

 $ cat /etc/httpd.conf
 # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $

 #
 # Macros
 #
 ext_addr="192.168.60.129"
 # A minimal default server
 server "default" {
 listen on $ext_addr port 80
 }




 Thank you
 Monah
>>>
>>> Did you try
>>>
>>>  ext_addr="*"
>>>
>>> yet?
>>>
>>> Does it report the same error with that in place?
>>>
>>> -- Currell
>>
>
>
>
> --
>
> Cordialement, Coues Ludovic
> +336 148 743 42

Re: Getting http to work

[Monah Baki]

Changing to ext_addr="*"


# /etc/rc.d/httpd start
httpd(failed)

Nothing shows up in /var/log/messages






On Sat, Feb 25, 2017 at 12:00 PM, Currell Berry  wrote:
>
> Monah Baki writes:
>
>> Hi all,
>>
>> Installed a fresh install of OpenBSD 6.0 on VMWare workstation and
>> wanted to run default webserver.
>>
>> In the messages logs I find the following error:
>>
>>  httpd[23792]: parent: send server: Can't assign requested address
>>
>>
>> em0: flags=8843 mtu 1500
>> lladdr 00:0c:29:b3:81:f8
>> index 1 priority 0 llprio 3
>> groups: egress
>> media: Ethernet autoselect (1000baseT full-duplex,master)
>> status: active
>> inet 192.168.60.129 netmask 0xff00 broadcast 192.168.60.255
>>
>> In my httpd.conf all I changed was the "ext_addr" Macro, everything else as 
>> is.
>>
>> $ cat /etc/httpd.conf
>> # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $
>>
>> #
>> # Macros
>> #
>> ext_addr="192.168.60.129"
>> # A minimal default server
>> server "default" {
>> listen on $ext_addr port 80
>> }
>>
>>
>>
>>
>> Thank you
>> Monah
>
> Did you try
>
>  ext_addr="*"
>
> yet?
>
> Does it report the same error with that in place?
>
> -- Currell

Re: Are ease-of-reference patches wanted for man pages?

[Currell Berry]

Theo Buehler writes:

>> Are there any guidelines anywhere on what we are going for in a man
>> page?  If not is there a page which is very good and can be held up as a 
>> standard?
>
> Ingo's EuroBSDCon 2014 tutorial slides might be a good place to start:
>
> https://www.openbsd.org/papers/eurobsdcon2014-mandoc-slides.pdf
>
> It should contain all the important pointers and while mandoc has
> evolved since then, I think it shouldn't be too outdated.
>
> One of my favorite pages is the (relatively) new sh(1) manual, but
> usually things aren't that complex :)

Both those links are useful, thanks.

Re: Are ease-of-reference patches wanted for man pages?

[Currell Berry]

Eike Lantzsch writes:

> On Saturday, 25 February 2017 10:16:37 PYST Janne Johansson wrote:
>> 2017-02-25 9:45 GMT+01:00 Currell Berry :
>> > Is feedback / are patches solicited for man-pages in order to improve
>> > their usability to average users (even if this were to make them
>> > somewhat less formal in nature)?
>> >
>> > I find the openbsd man pages very useful, but I do run across things
>> > which I cannot figure out from the man pages and/or faq.  Often I will
>> > then do a web search to look for an answer to my dilemma.  When I find
>> > the answer, I often wish that a piece of information had been included
>> > in the relevant man pages and/or faq which would have prevented me
>> > needing to search through the internet.  Often this piece of information
>> > is a usage example.
>
> Ah, and did I mention these good books?
> https://www.nostarch.com/pf3
> https://www.nostarch.com/obenbsd2e
> I couldn't do without them ...

Those look good, thanks.

Re: APCu/Memcached/Redis - OwnCloud/Nextcloud memory caching - which OpenBSD package?

[Johan Huldtgren]

hello,

> I'm trying to improve the performance of my freshly installed Nextcloud 
> site.  I'm running on my local 1G network and the performance is less 
> than optimal.
> 
> I've done all the SQL tuning, but from looking at the SQL log files, the 
> SQL isn't the slow part.

make sure your SQL encoding is set to unicode/UTF8, I recently did a fresh
install and the encoding ended up as SQL_ASCII and performance was abysmal.
Switching to UTF-8 and performance was as expected. (this was with postgresql)

> I haven't configured a memory cache yet and am a bit confused about 
> which OpenBSD packages correspond to the recommendations documented in:
> https://docs.nextcloud.com/server/11/admin_manual/configuration_server/caching_configuration.html
> 
> APCu , APCu 4.0.6 and up required.
> Memcached 
> Redis , PHP module 2.2.6 and up required.
> 
> The only "APCu" packages are the UPS ones, not quite what I'm looking for :)
> There is no php package for Memcached (php-memcached).  There is Perl, 
> Python & Python3.
> There is a php-predis package at 1.1.1 level, and a 
> pecl-redis-2.2.7p0.tgz package, but is pecl for php?  I'm rather new to 
> all the php modules stuff...
> 
> Is anyone running any of these applications?  If so, what is the name of 
> the OpenBSD package, or did you do a local install?

I've configured my nextcloud installation with redis. The relevant packages
are:

# pkg_info | grep -i redis
pecl-redis-2.2.7p0  PHP interface to redis
redis-3.2.6 persistent key-value database

.jh

APCu/Memcached/Redis - OwnCloud/Nextcloud memory caching - which OpenBSD package?

[Steve Williams]

Hi,

I'm trying to improve the performance of my freshly installed Nextcloud 
site.  I'm running on my local 1G network and the performance is less 
than optimal.

I've done all the SQL tuning, but from looking at the SQL log files, the 
SQL isn't the slow part.

I haven't configured a memory cache yet and am a bit confused about 
which OpenBSD packages correspond to the recommendations documented in:
https://docs.nextcloud.com/server/11/admin_manual/configuration_server/caching_configuration.html

APCu , APCu 4.0.6 and up required.
Memcached 
Redis , PHP module 2.2.6 and up required.

The only "APCu" packages are the UPS ones, not quite what I'm looking for :)
There is no php package for Memcached (php-memcached).  There is Perl, 
Python & Python3.
There is a php-predis package at 1.1.1 level, and a 
pecl-redis-2.2.7p0.tgz package, but is pecl for php?  I'm rather new to 
all the php modules stuff...

Is anyone running any of these applications?  If so, what is the name of 
the OpenBSD package, or did you do a local install?


Thanks,
Steve W.

Re: Are ease-of-reference patches wanted for man pages?

[Theo Buehler]

> Are there any guidelines anywhere on what we are going for in a man
> page?  If not is there a page which is very good and can be held up as a 
> standard?

Ingo's EuroBSDCon 2014 tutorial slides might be a good place to start:

https://www.openbsd.org/papers/eurobsdcon2014-mandoc-slides.pdf

It should contain all the important pointers and while mandoc has
evolved since then, I think it shouldn't be too outdated.

One of my favorite pages is the (relatively) new sh(1) manual, but
usually things aren't that complex :)

Re: Getting http to work

[Currell Berry]

Monah Baki writes:

> Hi all,
>
> Installed a fresh install of OpenBSD 6.0 on VMWare workstation and
> wanted to run default webserver.
>
> In the messages logs I find the following error:
>
>  httpd[23792]: parent: send server: Can't assign requested address
>
>
> em0: flags=8843 mtu 1500
> lladdr 00:0c:29:b3:81:f8
> index 1 priority 0 llprio 3
> groups: egress
> media: Ethernet autoselect (1000baseT full-duplex,master)
> status: active
> inet 192.168.60.129 netmask 0xff00 broadcast 192.168.60.255
>
> In my httpd.conf all I changed was the "ext_addr" Macro, everything else as 
> is.
>
> $ cat /etc/httpd.conf
> # $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $
>
> #
> # Macros
> #
> ext_addr="192.168.60.129"
> # A minimal default server
> server "default" {
> listen on $ext_addr port 80
> }
>
>
>
>
> Thank you
> Monah

Did you try

 ext_addr="*"

yet?

Does it report the same error with that in place?

-- Currell

Re: Are ease-of-reference patches wanted for man pages?

[Currell Berry]

Theo Buehler writes:

> On Sat, Feb 25, 2017 at 07:01:30AM -0300, Eike Lantzsch wrote:
>> On Saturday, 25 February 2017 10:16:37 PYST Janne Johansson wrote:
>> > 2017-02-25 9:45 GMT+01:00 Currell Berry :
>> > > Is feedback / are patches solicited for man-pages in order to improve
>> > > their usability to average users (even if this were to make them
>> > > somewhat less formal in nature)?
>> > >
>> > > I find the openbsd man pages very useful, but I do run across things
>> > > which I cannot figure out from the man pages and/or faq.  Often I will
>> > > then do a web search to look for an answer to my dilemma.  When I find
>> > > the answer, I often wish that a piece of information had been included
>> > > in the relevant man pages and/or faq which would have prevented me
>> > > needing to search through the internet.  Often this piece of information
>> > > is a usage example.
>> > >
>> > > Three recent examples for me were:
>> > > 1. the xorg.conf manual page does not say anything about specifying
>> > > resolution (rough answer -- the mode name generally identifies resolution
>> > > by
>> > > using a string such as "1024x768".  there are various preset modes or
>> > > you can create your own).
>
> Most of the manuals in xenocara/ are not ours and we don't usually
> modify them a lot.  You may want to contact upstream:
> https://www.x.org/wiki/DeveloperStart/
>
>> > > 2. The openbsd disk setup FAQ does not really tell you to use newfs
>> > > after you have used fdisk and disklabel.  It tangentially mentions newfs
>> > > in the portion about "encrypting external disks" and in the answer to
>> > > the prompt "Why does df tell me I have over 100% of my disk used".  I
>> > > think perhaps newfs as the next step in the disk setup process could be
>> > > mentioned in the FAQ, and also that maybe the disklabel utility man page
>> > > could
>> > > include a link to or small comment about newfs.
>> >
>> > Yes, the chapter
>> > Partitions and filesystems
>> >
>> > of faq14 should actually talk about filesystems also, and probably mention
>> > newfs while there, but it almost exclusively discusses partitions and
>> > partitioning.
>
> Sounds totally reasonable, a short sentence or two on newfs certainly
> wouldn't hurt...  I suggest you send a patch to tech@ and tj and I will
> consider it.
>
>> > > 3. Many of the login.conf resource limits appear to be per process, but
>> > > the man page does not in general differentiate the limits that are per
>> > > user and per-process.  So, for instance, cputime is identified as "CPU
>> > > usage limit" but I cannot know without prior knowledge or searching
>> > > whether this is enforced per-process or per-user.
>> >
>> > I think a short notice on how it is applied could well fit into that
>> > manpage, if kept brief. You would have to be careful not to have the same
>> > information typed down in various ways also in limit descriptions (in shell
>> > manpages mostly for ulimit) and setrlimit(2).
>> >
>> > > So, in all of these cases, there is no error in the documentation, it
>> > > just doesn't hold the user's hand very much.  Does OpenBSD want man-page
>> > > patch submissions which attempt to improve the usability of the
>> > > man-pages?  If so,
>> > > where should such patches be submitted?
>
> Patches (including documentation) are best sent to the tech@ mailing
> list.

I will subscribe to tech@ and look to submit some doc patches in the
future.

Are there any guidelines anywhere on what we are going for in a man
page?  If not is there a page which is very good and can be held up as a 
standard?

-- Currell

From SHA1 to SHA256 in dhcpd sync

[Denis Fondras]

Hi,

A patch to get away from SHA1 in dhcpd


Index: sync.c
===
RCS file: /cvs/src/usr.sbin/dhcpd/sync.c,v
retrieving revision 1.23
diff -u -p -r1.23 sync.c
--- sync.c  13 Feb 2017 23:04:05 -  1.23
+++ sync.c  25 Feb 2017 15:12:52 -
@@ -32,7 +32,7 @@
 
 #include 
 #include 
-#include 
+#include 
 #include 
 #include 
 #include 
@@ -140,7 +140,7 @@ sync_init(const char *iface, const char 
}
}
 
-   sync_key = SHA1File(DHCP_SYNC_KEY, NULL);
+   sync_key = SHA256File(DHCP_SYNC_KEY, NULL);
if (sync_key == NULL) {
if (errno != ENOENT) {
log_warn("failed to open sync key");
@@ -270,7 +270,7 @@ sync_recv(void)
/* Compute and validate HMAC */
memcpy(hmac[0], hdr->sh_hmac, DHCP_SYNC_HMAC_LEN);
explicit_bzero(hdr->sh_hmac, DHCP_SYNC_HMAC_LEN);
-   HMAC(EVP_sha1(), sync_key, strlen(sync_key), buf, len,
+   HMAC(EVP_sha256(), sync_key, strlen(sync_key), buf, len,
hmac[1], _len);
if (bcmp(hmac[0], hmac[1], DHCP_SYNC_HMAC_LEN) != 0)
goto trunc;
@@ -404,7 +404,7 @@ sync_lease(struct lease *lease)
memset(, 0, sizeof(pad));
 
HMAC_CTX_init();
-   HMAC_Init(, sync_key, strlen(sync_key), EVP_sha1());
+   HMAC_Init(, sync_key, strlen(sync_key), EVP_sha256());
 
leaselen = sizeof(lv);
padlen = DHCP_ALIGN(leaselen) - leaselen;
Index: sync.h
===
RCS file: /cvs/src/usr.sbin/dhcpd/sync.h,v
retrieving revision 1.5
diff -u -p -r1.5 sync.h
--- sync.h  4 Oct 2016 22:47:51 -   1.5
+++ sync.h  25 Feb 2017 15:12:52 -
@@ -20,6 +20,8 @@
 #ifndef _DHCPD_SYNC
 #define _DHCPD_SYNC
 
+#include 
+
 /*
  * dhcpd(8) synchronisation protocol.
  *
@@ -28,14 +30,14 @@
  * It is a simple Type-Length-Value based protocol, it allows easy
  * extension with future subtypes and bulk transfers by sending multiple
  * entries at once. The unencrypted messages will be authenticated using
- * HMAC-SHA1.
+ * HMAC-SHA256.
  *
  */
 
 #define DHCP_SYNC_VERSION  1
 #define DHCP_SYNC_MCASTADDR"224.0.1.240"   /* XXX choose valid address */
 #define DHCP_SYNC_MCASTTTL IP_DEFAULT_MULTICAST_TTL
-#define DHCP_SYNC_HMAC_LEN 20  /* SHA1 */
+#define DHCP_SYNC_HMAC_LEN SHA256_DIGEST_LENGTH
 #define DHCP_SYNC_MAXSIZE  1408
 #define DHCP_SYNC_KEY  "/var/db/dhcpd.key"

Re: Static binaries on newer releases

[Martijn Rijkeboer]

On 02/24/17 13:07, Juan Francisco Cantero Hurtado wrote:
> On Fri, Feb 24, 2017 at 11:08:21AM +0100, Martijn Rijkeboer wrote:
>> Hi,
>>
>> If I have a static binary compiled on OpenBSD release X, is that binary
>> expected to also run on release X+1, X+2 and X+Y? For example, a static
>> binary that is compiled on OpenBSD 6.0, is it expected to also run on
>> 6.1, 6.2 and 6.3? The reason for asking is a Haskell stack issue [0]
>> that involves GHC bindists.
> 
> In addition to Sebastien's comment, take a look to
> https://github.com/golang/go/issues/15227 . Go has also the same
> problem.

Thanks, I will check that issue.

Kind regards,


Martijn Rijkeboer

Re: Static binaries on newer releases

[Martijn Rijkeboer]

On 02/24/17 12:07, Sebastien Marie wrote:
> On Fri, Feb 24, 2017 at 11:08:21AM +0100, Martijn Rijkeboer wrote:
>> Hi,
>>
>> If I have a static binary compiled on OpenBSD release X, is that binary
>> expected to also run on release X+1, X+2 and X+Y? For example, a static
>> binary that is compiled on OpenBSD 6.0, is it expected to also run on
>> 6.1, 6.2 and 6.3? The reason for asking is a Haskell stack issue [0]
>> that involves GHC bindists.
>>
> 
> The generic answer will be "no".
> 
> The example is the switch from 5.4 to 5.5 release which included time_t
> change (32 to 64 bits) - see https://www.openbsd.org/faq/upgrade55.html#time_t
> 
> But generally, an old binary (from release X) is able to run on a new
> kernel (from release X+1), but nothing more could be expected: old
> things are cleaned, so an old binary could be able to run or not (it
> just depends if relying on old API/ABI with kernel - syscalls, struct
> size...).

Thanks for your answer. This is what I was expecting, but wanted to
make sure before adding the info to the stack issue.

Kind regards,


Martijn Rijkeboer

Re: Are ease-of-reference patches wanted for man pages?

[Theo Buehler]

On Sat, Feb 25, 2017 at 07:01:30AM -0300, Eike Lantzsch wrote:
> On Saturday, 25 February 2017 10:16:37 PYST Janne Johansson wrote:
> > 2017-02-25 9:45 GMT+01:00 Currell Berry :
> > > Is feedback / are patches solicited for man-pages in order to improve
> > > their usability to average users (even if this were to make them
> > > somewhat less formal in nature)?
> > >
> > > I find the openbsd man pages very useful, but I do run across things
> > > which I cannot figure out from the man pages and/or faq.  Often I will
> > > then do a web search to look for an answer to my dilemma.  When I find
> > > the answer, I often wish that a piece of information had been included
> > > in the relevant man pages and/or faq which would have prevented me
> > > needing to search through the internet.  Often this piece of information
> > > is a usage example.
> > >
> > > Three recent examples for me were:
> > > 1. the xorg.conf manual page does not say anything about specifying
> > > resolution (rough answer -- the mode name generally identifies resolution
> > > by
> > > using a string such as "1024x768".  there are various preset modes or
> > > you can create your own).

Most of the manuals in xenocara/ are not ours and we don't usually
modify them a lot.  You may want to contact upstream:
https://www.x.org/wiki/DeveloperStart/

> > > 2. The openbsd disk setup FAQ does not really tell you to use newfs
> > > after you have used fdisk and disklabel.  It tangentially mentions newfs
> > > in the portion about "encrypting external disks" and in the answer to
> > > the prompt "Why does df tell me I have over 100% of my disk used".  I
> > > think perhaps newfs as the next step in the disk setup process could be
> > > mentioned in the FAQ, and also that maybe the disklabel utility man page
> > > could
> > > include a link to or small comment about newfs.
> >
> > Yes, the chapter
> > Partitions and filesystems
> >
> > of faq14 should actually talk about filesystems also, and probably mention
> > newfs while there, but it almost exclusively discusses partitions and
> > partitioning.

Sounds totally reasonable, a short sentence or two on newfs certainly
wouldn't hurt...  I suggest you send a patch to tech@ and tj and I will
consider it.

> > > 3. Many of the login.conf resource limits appear to be per process, but
> > > the man page does not in general differentiate the limits that are per
> > > user and per-process.  So, for instance, cputime is identified as "CPU
> > > usage limit" but I cannot know without prior knowledge or searching
> > > whether this is enforced per-process or per-user.
> >
> > I think a short notice on how it is applied could well fit into that
> > manpage, if kept brief. You would have to be careful not to have the same
> > information typed down in various ways also in limit descriptions (in shell
> > manpages mostly for ulimit) and setrlimit(2).
> >
> > > So, in all of these cases, there is no error in the documentation, it
> > > just doesn't hold the user's hand very much.  Does OpenBSD want man-page
> > > patch submissions which attempt to improve the usability of the
> > > man-pages?  If so,
> > > where should such patches be submitted?

Patches (including documentation) are best sent to the tech@ mailing
list.

From SHA1 to SHA256 in spamd sync

[Denis Fondras]

Hi,

A patch to get away from SHA1 in spamd


Index: sync.c
===
RCS file: /cvs/src/libexec/spamd/sync.c,v
retrieving revision 1.12
diff -u -p -r1.12 sync.c
--- sync.c  20 Oct 2016 21:09:46 -  1.12
+++ sync.c  25 Feb 2017 14:18:17 -
@@ -30,7 +30,7 @@
 #include 
 #include 
 #include 
-#include 
+#include 
 #include 
 #include 
 
@@ -142,7 +142,7 @@ sync_init(const char *iface, const char 
}
}
 
-   sync_key = SHA1File(SPAM_SYNC_KEY, NULL);
+   sync_key = SHA256File(SPAM_SYNC_KEY, NULL);
if (sync_key == NULL) {
if (errno != ENOENT) {
fprintf(stderr, "failed to open sync key: %s\n",
@@ -276,7 +276,7 @@ sync_recv(void)
/* Compute and validate HMAC */
memcpy(hmac[0], hdr->sh_hmac, SPAM_SYNC_HMAC_LEN);
explicit_bzero(hdr->sh_hmac, SPAM_SYNC_HMAC_LEN);
-   HMAC(EVP_sha1(), sync_key, strlen(sync_key), buf, len,
+   HMAC(EVP_sha256(), sync_key, strlen(sync_key), buf, len,
hmac[1], _len);
if (bcmp(hmac[0], hmac[1], SPAM_SYNC_HMAC_LEN) != 0)
goto trunc;
@@ -441,7 +441,7 @@ sync_update(time_t now, char *helo, char
helolen = strlen(helo) + 1;
 
HMAC_CTX_init();
-   HMAC_Init(, sync_key, strlen(sync_key), EVP_sha1());
+   HMAC_Init(, sync_key, strlen(sync_key), EVP_sha256());
 
sglen = sizeof(sg) + fromlen + tolen + helolen;
padlen = SPAM_ALIGN(sglen) - sglen;
@@ -523,7 +523,7 @@ sync_addr(time_t now, time_t expire, cha
memset(, 0, sizeof(sd));
 
HMAC_CTX_init();
-   HMAC_Init(, sync_key, strlen(sync_key), EVP_sha1());
+   HMAC_Init(, sync_key, strlen(sync_key), EVP_sha256());
 
/* Add SPAM sync packet header */
hdr.sh_version = SPAM_SYNC_VERSION;
Index: sync.h
===
RCS file: /cvs/src/libexec/spamd/sync.h,v
retrieving revision 1.3
diff -u -p -r1.3 sync.h
--- sync.h  22 May 2008 19:54:11 -  1.3
+++ sync.h  25 Feb 2017 14:18:17 -
@@ -19,6 +19,8 @@
 #ifndef _SPAMD_SYNC
 #define _SPAMD_SYNC
 
+#include 
+
 /*
  * spamd(8) synchronisation protocol.
  *
@@ -27,7 +29,7 @@
  * It is a simple Type-Length-Value based protocol, it allows easy
  * extension with future subtypes and bulk transfers by sending multiple
  * entries at once. The unencrypted messages will be authenticated using
- * HMAC-SHA1.
+ * HMAC-SHA256.
  *
  * the spamd(8) synchronisation protocol is not intended to be used as
  * a public SPAM sender database or distribution between vendors.
@@ -36,7 +38,7 @@
 #define SPAM_SYNC_VERSION  2
 #define SPAM_SYNC_MCASTADDR"224.0.1.240"   /* XXX choose valid address */
 #define SPAM_SYNC_MCASTTTL IP_DEFAULT_MULTICAST_TTL
-#define SPAM_SYNC_HMAC_LEN 20  /* SHA1 */
+#define SPAM_SYNC_HMAC_LEN SHA256_DIGEST_LENGTH
 #define SPAM_SYNC_MAXSIZE  1408
 #define SPAM_SYNC_KEY  "/etc/mail/spamd.key"

Getting http to work

[Monah Baki]

Hi all,

Installed a fresh install of OpenBSD 6.0 on VMWare workstation and
wanted to run default webserver.

In the messages logs I find the following error:

 httpd[23792]: parent: send server: Can't assign requested address


em0: flags=8843 mtu 1500
lladdr 00:0c:29:b3:81:f8
index 1 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT full-duplex,master)
status: active
inet 192.168.60.129 netmask 0xff00 broadcast 192.168.60.255

In my httpd.conf all I changed was the "ext_addr" Macro, everything else as is.

$ cat /etc/httpd.conf
# $OpenBSD: httpd.conf,v 1.14 2015/02/04 08:39:35 florian Exp $

#
# Macros
#
ext_addr="192.168.60.129"
# A minimal default server
server "default" {
listen on $ext_addr port 80
}




Thank you
Monah

Re: Is OpenBSD using SHA1 anywhere?

[ludovic coues]

HMAC-SHA1 is used

https://www.schneier.com/blog/archives/2005/02/sha1_broken.html
"although it doesn't affect applications such as HMAC where collisions
aren't important"

2017-02-25 10:56 GMT+01:00 minek van :
> In the blog:
> https://blog.filippo.io/so-i-lost-my-openbsd-fde-password/
> I seen that "sha1" is still used, but afaik 6.1 will have a different FDE.
>
>> Sent: Thursday, February 23, 2017 at 5:27 PM
>> From: "Christian Weisgerber" 
>> To: misc@openbsd.org
>> Subject: Re: Is OpenBSD using SHA1 anywhere?
>>
>> On 2017-02-23, Marc Espie  wrote:
>>
>> > Talking from the ports side, ports and packages moved to SHA256
>> > back in 2007/2008.
>>
>> To be expressly clear: Marc is referring to the ports and packages
>> infrastructure here.  The packaged third-party software still
>> contains many uses of SHA1; some may be harmless, some are embedded
>> into protocols that can't be easily changed.
>>
>> > Ports distinfo made it the only default in 2007, and pkg tools moved 
>> > straight
>> > from md5 to sha1.
>>^^^
>>   to sha256
>>
>> (Unfortunate typo.)
>>
>> --
>> Christian "naddy" Weisgerber  na...@mips.inka.de
>



-- 

Cordialement, Coues Ludovic
+336 148 743 42

Re: Are ease-of-reference patches wanted for man pages?

[Eike Lantzsch]

On Saturday, 25 February 2017 10:16:37 PYST Janne Johansson wrote:
> 2017-02-25 9:45 GMT+01:00 Currell Berry :
> > Is feedback / are patches solicited for man-pages in order to improve
> > their usability to average users (even if this were to make them
> > somewhat less formal in nature)?
> >
> > I find the openbsd man pages very useful, but I do run across things
> > which I cannot figure out from the man pages and/or faq.  Often I will
> > then do a web search to look for an answer to my dilemma.  When I find
> > the answer, I often wish that a piece of information had been included
> > in the relevant man pages and/or faq which would have prevented me
> > needing to search through the internet.  Often this piece of information
> > is a usage example.

Ah, and did I mention these good books?
https://www.nostarch.com/pf3
https://www.nostarch.com/obenbsd2e
I couldn't do without them ...
--
Eike Lantzsch ZP6CGE

“Do you actually know what you are reading?”
He said: “Really, how could I ever do so unless
someone guided me?” ... (Acts 8:30, 31)

Re: Are ease-of-reference patches wanted for man pages?

[Eike Lantzsch]

On Saturday, 25 February 2017 10:16:37 PYST Janne Johansson wrote:
> 2017-02-25 9:45 GMT+01:00 Currell Berry :
> > Is feedback / are patches solicited for man-pages in order to improve
> > their usability to average users (even if this were to make them
> > somewhat less formal in nature)?
> >
> > I find the openbsd man pages very useful, but I do run across things
> > which I cannot figure out from the man pages and/or faq.  Often I will
> > then do a web search to look for an answer to my dilemma.  When I find
> > the answer, I often wish that a piece of information had been included
> > in the relevant man pages and/or faq which would have prevented me
> > needing to search through the internet.  Often this piece of information
> > is a usage example.
> >
> > Three recent examples for me were:
> > 1. the xorg.conf manual page does not say anything about specifying
> > resolution (rough answer -- the mode name generally identifies resolution
> > by
> > using a string such as "1024x768".  there are various preset modes or
> > you can create your own).
> >
> > 2. The openbsd disk setup FAQ does not really tell you to use newfs
> > after you have used fdisk and disklabel.  It tangentially mentions newfs
> > in the portion about "encrypting external disks" and in the answer to
> > the prompt "Why does df tell me I have over 100% of my disk used".  I
> > think perhaps newfs as the next step in the disk setup process could be
> > mentioned in the FAQ, and also that maybe the disklabel utility man page
> > could
> > include a link to or small comment about newfs.
>
> Yes, the chapter
> Partitions and filesystems
>
> of faq14 should actually talk about filesystems also, and probably mention
> newfs while there, but it almost exclusively discusses partitions and
> partitioning.
>
> > 3. Many of the login.conf resource limits appear to be per process, but
> > the man page does not in general differentiate the limits that are per
> > user and per-process.  So, for instance, cputime is identified as "CPU
> > usage limit" but I cannot know without prior knowledge or searching
> > whether this is enforced per-process or per-user.
>
> I think a short notice on how it is applied could well fit into that
> manpage, if kept brief. You would have to be careful not to have the same
> information typed down in various ways also in limit descriptions (in shell
> manpages mostly for ulimit) and setrlimit(2).
>
> > So, in all of these cases, there is no error in the documentation, it
> > just doesn't hold the user's hand very much.  Does OpenBSD want man-page
> > patch submissions which attempt to improve the usability of the
> > man-pages?  If so,
> > where should such patches be submitted?
> >
> > Thanks,
> > Currell
> > --
> > Currell Berry
> > http://www.cvberry.com

I second both - OP and comment.

--
Eike Lantzsch ZP6CGE

“Do you actually know what you are reading?”
He said: “Really, how could I ever do so unless
someone guided me?” ... (Acts 8:30, 31)

Re: Is OpenBSD using SHA1 anywhere?

[minek van]

In the blog: 
https://blog.filippo.io/so-i-lost-my-openbsd-fde-password/
I seen that "sha1" is still used, but afaik 6.1 will have a different FDE. 

> Sent: Thursday, February 23, 2017 at 5:27 PM
> From: "Christian Weisgerber" 
> To: misc@openbsd.org
> Subject: Re: Is OpenBSD using SHA1 anywhere?
>
> On 2017-02-23, Marc Espie  wrote:
> 
> > Talking from the ports side, ports and packages moved to SHA256 
> > back in 2007/2008.
> 
> To be expressly clear: Marc is referring to the ports and packages
> infrastructure here.  The packaged third-party software still
> contains many uses of SHA1; some may be harmless, some are embedded
> into protocols that can't be easily changed.
> 
> > Ports distinfo made it the only default in 2007, and pkg tools moved 
> > straight
> > from md5 to sha1.
>^^^
>   to sha256
> 
> (Unfortunate typo.)
> 
> -- 
> Christian "naddy" Weisgerber  na...@mips.inka.de

Re: Are ease-of-reference patches wanted for man pages?

[Janne Johansson]

2017-02-25 9:45 GMT+01:00 Currell Berry :

> Is feedback / are patches solicited for man-pages in order to improve
> their usability to average users (even if this were to make them
> somewhat less formal in nature)?
>
> I find the openbsd man pages very useful, but I do run across things
> which I cannot figure out from the man pages and/or faq.  Often I will
> then do a web search to look for an answer to my dilemma.  When I find
> the answer, I often wish that a piece of information had been included
> in the relevant man pages and/or faq which would have prevented me
> needing to search through the internet.  Often this piece of information
> is a usage example.
>
> Three recent examples for me were:
> 1. the xorg.conf manual page does not say anything about specifying
> resolution (rough answer -- the mode name generally identifies resolution
> by
> using a string such as "1024x768".  there are various preset modes or
> you can create your own).
>
> 2. The openbsd disk setup FAQ does not really tell you to use newfs
> after you have used fdisk and disklabel.  It tangentially mentions newfs
> in the portion about "encrypting external disks" and in the answer to
> the prompt "Why does df tell me I have over 100% of my disk used".  I
> think perhaps newfs as the next step in the disk setup process could be
> mentioned in the FAQ, and also that maybe the disklabel utility man page
> could
> include a link to or small comment about newfs.
>
>
Yes, the chapter
Partitions and filesystems

of faq14 should actually talk about filesystems also, and probably mention
newfs while there, but it almost exclusively discusses partitions and
partitioning.



> 3. Many of the login.conf resource limits appear to be per process, but
> the man page does not in general differentiate the limits that are per
> user and per-process.  So, for instance, cputime is identified as "CPU
> usage limit" but I cannot know without prior knowledge or searching
> whether this is enforced per-process or per-user.
>
>
I think a short notice on how it is applied could well fit into that
manpage, if kept brief. You would have to be careful not to have the same
information typed down in various ways also in limit descriptions (in shell
manpages mostly for ulimit) and setrlimit(2).


> So, in all of these cases, there is no error in the documentation, it
> just doesn't hold the user's hand very much.  Does OpenBSD want man-page
> patch submissions which attempt to improve the usability of the
> man-pages?  If so,
> where should such patches be submitted?
>
> Thanks,
> Currell
> --
> Currell Berry
> http://www.cvberry.com
>
>


-- 
May the most significant bit of your life be positive.

Are ease-of-reference patches wanted for man pages?

[Currell Berry]

Is feedback / are patches solicited for man-pages in order to improve
their usability to average users (even if this were to make them
somewhat less formal in nature)?

I find the openbsd man pages very useful, but I do run across things
which I cannot figure out from the man pages and/or faq.  Often I will
then do a web search to look for an answer to my dilemma.  When I find
the answer, I often wish that a piece of information had been included
in the relevant man pages and/or faq which would have prevented me
needing to search through the internet.  Often this piece of information
is a usage example.

Three recent examples for me were:
1. the xorg.conf manual page does not say anything about specifying
resolution (rough answer -- the mode name generally identifies resolution by
using a string such as "1024x768".  there are various preset modes or
you can create your own).

2. The openbsd disk setup FAQ does not really tell you to use newfs
after you have used fdisk and disklabel.  It tangentially mentions newfs
in the portion about "encrypting external disks" and in the answer to
the prompt "Why does df tell me I have over 100% of my disk used".  I
think perhaps newfs as the next step in the disk setup process could be
mentioned in the FAQ, and also that maybe the disklabel utility man page could
include a link to or small comment about newfs.

3. Many of the login.conf resource limits appear to be per process, but
the man page does not in general differentiate the limits that are per
user and per-process.  So, for instance, cputime is identified as "CPU
usage limit" but I cannot know without prior knowledge or searching
whether this is enforced per-process or per-user.

So, in all of these cases, there is no error in the documentation, it
just doesn't hold the user's hand very much.  Does OpenBSD want man-page
patch submissions which attempt to improve the usability of the man-pages?  If 
so,
where should such patches be submitted?

Thanks,
Currell
-- 
Currell Berry
http://www.cvberry.com