Supporting OpenBSD

[Radoslav Mirza]

Dear Group,
Are there any resources that point to where I can begin to help with the 
project?

Such as junior jobs, documentation etc.

I recently purchased hardware specifically for OpenBSD support and plan to 
replace Archlinux as my main OS.

I am studying for my CCNA and plan to head down the networking path for a 
career so network related jobs would be fantastic.

I have a new 8 core 1700 Ryzen so I maybe able to help with benchmarking SMP.

Thanks!
PS. I hope this email complies better with the list's standards.

Re: Helping out

[Bryan Vyhmeister]

On Tue, Aug 01, 2017 at 08:19:23PM -0400, Radoslav_Mirza wrote:
> Dear Group, Are there any places to start helping out for a beginner?
> Any junior jobs or todo lists?
> 
> I have a new Ryzen 1700 running OpenBSD so maybe I could help with
> some benchmark tests etc.
> 
> Any pointers of where to go would be great!

There was a recent discussion about ProtonMail not sending plain text
email which this list expects. I would suggest sending with another
address and sending in plain text. Check the archives for more info
about it but base64 encoded emails (like from ProtonMail) will likely be
ignored. Hopefully ProtonMail will correct this problem but they have
"started" on it for more than a year.

Bryan

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Tue, Aug 01, 2017 at 10:12:05PM +0200, Ulf Brosziewski wrote:
> I have the impression that multi-finger clicks are popular
> among Mac users, is it correct?  However, if the new driver
> works it should offer software button areas at the bottom
> edge of the touchpad, as elsewhere.  Are they missing?
> Are they too small?  Or is it "simply" not your habit? Anyway,
> there must be some bug or misconfiguration, the "tp" fields
> are missing in the wsconsctl output:

You are correct. Having used Macs for years and years, I am very
accustomed to multi-finger clicks and they are my "habit" now. I was not
aware of the software button areas. If I hold down a click in the middle
of the touchpad but at the bottom edge for about one second or a little
more, when I release that click, I get a button2 which allows paste.
That works well enough. I have not yet figured out how to get button3
except for Ctrl click.

> > # wsconsctl | grep mouse
> > mouse.type=usb
> > mouse.rawmode=1
> > mouse.scale=0,0,0,0,0,0,0
> > mouse1.type=elantech
> > mouse1.rawmode=0
> > mouse1.scale=-4620,5140,-150,6600,0,0,0
> >
> 
> Would you mind to report the output of the following command?
> # wsconsctl mouse1.tp.param=64,65

Here is the output:

mouse1.tp.param -> 64:1,65:1

> And special thanks again for all your work,

Thank you for your development. I am very excited to see these changes
in OpenBSD.

Bryan

Helping out

[Radoslav_Mirza]

Dear Group,
Are there any places to start helping out for a beginner? Any junior jobs or 
todo lists?

I have a new Ryzen 1700 running OpenBSD so maybe I could help with some 
benchmark tests etc.

Any pointers of where to go would be great!

Thanks.

Sent from ProtonMail mobile

Re: touchpad input driver: testing needed

[Ulf Brosziewski]

The event codes look wrong, they are for right-clicks and left-clicks,
if I'm not mistaken.  Is there a "ButtonMapping" defined for X
somewhere (in your xorg.conf, or by a script), or a "ZAxisMapping"?

Could you have a look at the output of
   $ xmodmap -pp
?

On 08/02/2017 12:22 AM, Olivier Antoine wrote:
> Two-fingers scrolling doesn't work at all. Under a firefox window, it open
> context menu, or act like pressing button.
> 
> $ xinput --test /dev/wsmouse0
> button press   3
> button release 3
> button press   3
> button release 3
> button press   3
> button release 3
> motion a[0]=876 a[1]=497
> button press   3
> button release 3
> button press   3
> button release 3
> button press   3
> button release 3
> button press   1
> button release 1
> button press   1
> button release 1
> button press   1
> button release 1
> button press   1
> button release 1
> button press   3
> button release 3
> button press   1
> button release 1
> button press   1
> button release 1
> button press   3
> button release 3
> button press   3
> button release 3
> 
> 
> 
> On Tue, Aug 1, 2017 at 9:53 PM, Ulf Brosziewski > wrote:
> 
>> Hi,
>>
>> thanks for testing!  Does "NOT OK" mean that two-finger
>> scrolling works badly, or that it doesn't work at all?
>> If possible, could you record the output of
>> $ xinput --test /dev/wsmouse0
>> for a short period of time and perform the scroll gesture?
>>
>> Ulf
>>
>> On 08/01/2017 11:09 AM, Olivier Antoine wrote:
>>> Mouse move: OK
>>> Mouse tapping: OK
>>> Two-fingers scrolling: NOT OK
>>>
>>> Machine Lenovo Thinkpad E130
>>>
>>> # wsconsctl | grep 'mouse'
>>> mouse.type=synaptics
>>> mouse.rawmode=0
>>> mouse.scale=1472,5768,1408,5236,0,66,175
>>> mouse.tp.tapping=1
>>> mouse.tp.scaling=0.160
>>> mouse.tp.swapsides=0
>>> mouse.tp.disable=0
>>> mouse1.type=ps2
>>>
>>>
>>>
>>> On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski <
>>> ulf.brosziew...@t-online.de> wrote:
>>>
 In the long run the synaptics driver, which handles touchpad inputs in
 X, may be a dead end of the input framework, and it's time to prepare
 an alternative.  The kernel contains an internal touchpad input driver
 now, it's a part of wsmouse(4).  It provides standard features -
 two-finger/edge scrolling, software buttons for clickpads, tapping -
 and various kinds of plankton required for usability.

 If you have a new snapshot (from July 27 or later) on a laptop with a
 Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with
 tests, more tests, and tests.  In order to activate the driver, add the
 following entry to /etc/xorg.conf and restart X (if the file isn't
 present, simply create it with this content):

 Section "InputClass"
 Identifier "wsmouse touchpad"
 Driver "ws"
 MatchIsTouchpad "on"
 EndSection

 While I dont't expect bugs in the input processing part of the
 driver ;-), it is difficult to assess how well the automatic
 configuration covers the zoo of models out there, presumably it will
 need some more fine-grained distinctions of hardware properties.  I
 would like to know where it works, works only halfway, or doesn't work
 for you.  As always, a dmesg would be appreciated.  The output of
 # wsconsctl | grep 'mouse'
 could also be of interest here (you must run it as root).

 For now, X will treat the device like a mouse, please don't look for
 touchpad-specific configuration options there.  Tapping can be enabled
 by the command
 # wsconsctl mouse.tp.tapping=1
 If there is more than one wsmouse device, you should look up which one
 has the "tp" fields and if it's not the first one (wsmouse0), add the
 index to the prefix, e.g.
 # wsconsctl mouse2.tp.tapping=1

 The base speed of the pointer can be adjusted by increasing or
 decreasing the value of
 # wsconsctl mouse.tp.scaling
 Please don't confuse it with the 'mouse.scale' field.

 # wsconsctl mouse.tp.swapsides=1
 will invert the order of software buttons areas (swapping external
 buttons must still be configured in X). If edge scrolling is
 enabled, the scroll area will be at the left edge of the touchpad.

 If you are using an external mouse device or a trackpoint, the command
 # wsconsctl mouse.tp.disable=1
 may be helpful.  It will disable pointer movement, scrolling, and
 tapping.  External buttons and software buttons remain enabled.


>>>
>>
>>
> 

Re: touchpad input driver: testing needed

[Olivier Antoine]

Two-fingers scrolling doesn't work at all. Under a firefox window, it open
context menu, or act like pressing button.

$ xinput --test /dev/wsmouse0
button press   3
button release 3
button press   3
button release 3
button press   3
button release 3
motion a[0]=876 a[1]=497
button press   3
button release 3
button press   3
button release 3
button press   3
button release 3
button press   1
button release 1
button press   1
button release 1
button press   1
button release 1
button press   1
button release 1
button press   3
button release 3
button press   1
button release 1
button press   1
button release 1
button press   3
button release 3
button press   3
button release 3



On Tue, Aug 1, 2017 at 9:53 PM, Ulf Brosziewski  wrote:

> Hi,
>
> thanks for testing!  Does "NOT OK" mean that two-finger
> scrolling works badly, or that it doesn't work at all?
> If possible, could you record the output of
> $ xinput --test /dev/wsmouse0
> for a short period of time and perform the scroll gesture?
>
> Ulf
>
> On 08/01/2017 11:09 AM, Olivier Antoine wrote:
> > Mouse move: OK
> > Mouse tapping: OK
> > Two-fingers scrolling: NOT OK
> >
> > Machine Lenovo Thinkpad E130
> >
> > # wsconsctl | grep 'mouse'
> > mouse.type=synaptics
> > mouse.rawmode=0
> > mouse.scale=1472,5768,1408,5236,0,66,175
> > mouse.tp.tapping=1
> > mouse.tp.scaling=0.160
> > mouse.tp.swapsides=0
> > mouse.tp.disable=0
> > mouse1.type=ps2
> >
> >
> >
> > On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski <
> > ulf.brosziew...@t-online.de> wrote:
> >
> >> In the long run the synaptics driver, which handles touchpad inputs in
> >> X, may be a dead end of the input framework, and it's time to prepare
> >> an alternative.  The kernel contains an internal touchpad input driver
> >> now, it's a part of wsmouse(4).  It provides standard features -
> >> two-finger/edge scrolling, software buttons for clickpads, tapping -
> >> and various kinds of plankton required for usability.
> >>
> >> If you have a new snapshot (from July 27 or later) on a laptop with a
> >> Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with
> >> tests, more tests, and tests.  In order to activate the driver, add the
> >> following entry to /etc/xorg.conf and restart X (if the file isn't
> >> present, simply create it with this content):
> >>
> >> Section "InputClass"
> >> Identifier "wsmouse touchpad"
> >> Driver "ws"
> >> MatchIsTouchpad "on"
> >> EndSection
> >>
> >> While I dont't expect bugs in the input processing part of the
> >> driver ;-), it is difficult to assess how well the automatic
> >> configuration covers the zoo of models out there, presumably it will
> >> need some more fine-grained distinctions of hardware properties.  I
> >> would like to know where it works, works only halfway, or doesn't work
> >> for you.  As always, a dmesg would be appreciated.  The output of
> >> # wsconsctl | grep 'mouse'
> >> could also be of interest here (you must run it as root).
> >>
> >> For now, X will treat the device like a mouse, please don't look for
> >> touchpad-specific configuration options there.  Tapping can be enabled
> >> by the command
> >> # wsconsctl mouse.tp.tapping=1
> >> If there is more than one wsmouse device, you should look up which one
> >> has the "tp" fields and if it's not the first one (wsmouse0), add the
> >> index to the prefix, e.g.
> >> # wsconsctl mouse2.tp.tapping=1
> >>
> >> The base speed of the pointer can be adjusted by increasing or
> >> decreasing the value of
> >> # wsconsctl mouse.tp.scaling
> >> Please don't confuse it with the 'mouse.scale' field.
> >>
> >> # wsconsctl mouse.tp.swapsides=1
> >> will invert the order of software buttons areas (swapping external
> >> buttons must still be configured in X). If edge scrolling is
> >> enabled, the scroll area will be at the left edge of the touchpad.
> >>
> >> If you are using an external mouse device or a trackpoint, the command
> >> # wsconsctl mouse.tp.disable=1
> >> may be helpful.  It will disable pointer movement, scrolling, and
> >> tapping.  External buttons and software buttons remain enabled.
> >>
> >>
> >
>
>

Re: FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Unable to create temporary file, Check permissions in temporary files directory.

[Martijn van Duren]

Hello Stephane,

First, please send mails with questions about packages to ports@ in the
future. I'm not changing list now because I don't want to continue the
discussion, but merely rectify a few of your mistakes and hopefully
prevent people finding this thread in the future from making the same
ones.

If anyone feels like they should continue this thread please change the
list to ports@.

On 07/26/17 23:33, Stephane HUC "PengouinBSD" wrote:
> Hi, all.
> 
> Sorry for the latence!
> 
> Yes, i'm sure all ENV* variables are absolute to the system root.
> As explain on the php-fpm.conf, only few directives are relative to be
> chroot.
> 
> [quote]
> (...)
> ; Per pool prefix
> ; It only applies on the following directives:
> ; - 'access.log'
> ; - 'slowlog'
> ; - 'listen' (unixsocket)
> ; - 'chroot'
> ; - 'chdir'
> ; - 'php_values'
> ; - 'php_admin_values'
> ; When not set, the global prefix (or /usr/local) applies instead.
> ; Note: This directive can also be relative to the global prefix.
> (...)
> [/quote]
> 
> I modified the php-fpm.conf_user as:
> 
> env[TMP] = /var/www/tmp/$pool
> env[TMPDIR] = /var/www/tmp/$pool
> env[TEMP] = /var/www/tmp/$pool
> (...)
> php_admin_value[upload_tmp_dir]=/tmp/$pool
> 
> I created the directory /var/www/tmp/$pool, and chowned user_blog:www on
> this!
> 
> In facts, i was wrong user.
> 
> Now, it's run correctly! ;)

It runs because of sheer luck, not because of a proper configuration,
let alone correctly.

My statements are based on 7.1.7 which I compiled locally and will
hopefully hit the tree soon(tm), but should be equally valid for
other versions of PHP.
Also, I don't know your setup, so my response is based on
speculation, but is hopefully accurate enough for you to figure out
what is going on yourself.

I assume that you try to upload a file to a PHP script and store
it locally. This reaches main/rfc1867.c:1021 in the PHP core.

This tries to open a file based on upload_tmp_dir, which you've
set to /tmp/$pool in your final solution. This succeeds, because
it exists inside your chroot.
The problem here is that you haven't fixed env[{TMP,TMPDIR,TEMP}].

If upload_tmp_dir isn't set php_open_temporary_fd_ex
(main/php_open_temporary_file.c:294) calls php_get_temporary_directory.
This function tries several options, of which one is getenv("TMPDIR");.
Because you've set this variable to /var/www/tmp in your original setup,
but is called *AFTER* the fpm-daemon has chrooted to /var/www it
effectively tries to call /var/www/var/www/tmp, which does not exist.
See also the documentation at http://php.net/manual/en/ini.core.php.

If you hadn't set the environment variable it would've eventually fallen
back to /tmp, which is effectively /var/www/tmp because of the chroot.
Ergo: Fix your environment and unset upload_tmp_dir.

The second problem you hit is that /var/www/tmp is owned by www:www
with 755 permissions (pitfall, these permissions can be reset at any
time to 700). So even if PHP would try to create the intermediate
directories (don't know, haven't checked) it would still fail because of
the permissions on this directory.
Creating the /var/www/tmp/$pool directory with the correct owner
solves the problem indeed, but not because of your env statements.

The problem now is that you've fixed one problem but you've left open an
entire subsection of problems that you happen to not hit, and are still
a risk for people copying your configuration, or even yourself in the
future.
If you were to use tmpfile() you'd probably run into the same problem,
and that's just one example that I thought of, there's probably a lot
more.

So please, make sure you know what you're doing, especially if you claim
you've fixed something. These misconfigurations are always picked up by
other users and will cause problems down the road.

Next time you run into a similar problem go through the following steps:
1) Formulate what you've changed compared to the default configuration
file.
2) Formulate why you've changed these settings.
3) If you happen to solve your particular problem, report it as such
(that it fixes just your use case), unless you've researched why things
failed in the first place and you're absolutely sure your solution is
a generic solution.

Hope this mail helped you understand a little more of the internals and
added a little to your skills to debug such problems yourself.

martijn@
> 
> Thank you all.
> 
> 
> Le 07/26/17 à 01:50, Todd Mortimer a écrit :
>> Hi Stephane,
>>
>> Are you sure that the env[TMP], env[TMPDIR] and env[TEMP] variables are
>> supposed to be relative to the real system root, or relative to the
>> chroot? If I were to guess, I would bet that php is trying to create a
>> file after chrooting itself, and inside the chroot, /var/www/tmp doesn't
>> exist. Try setting those env vars to /tmp and see if that works. 
>>
>> Todd
>>
>> On Tue, Jul 25, 2017 at 09:03:38AM +0200, Stephane HUC "PengouinBSD" wrote:
>>> Hi all.
>>>
>>> I have this error on my,OpenBSD server 

Re: touchpad input driver: testing needed

[Ulf Brosziewski]

Hi Bryan,

I have the impression that multi-finger clicks are popular
among Mac users, is it correct?  However, if the new driver
works it should offer software button areas at the bottom
edge of the touchpad, as elsewhere.  Are they missing?
Are they too small?  Or is it "simply" not your habit? Anyway,
there must be some bug or misconfiguration, the "tp" fields
are missing in the wsconsctl output:

>
> # wsconsctl | grep mouse
> mouse.type=usb
> mouse.rawmode=1
> mouse.scale=0,0,0,0,0,0,0
> mouse1.type=elantech
> mouse1.rawmode=0
> mouse1.scale=-4620,5140,-150,6600,0,0,0
>

Would you mind to report the output of the following command?
# wsconsctl mouse1.tp.param=64,65

And special thanks again for all your work,
Ulf


On 08/01/2017 05:13 PM, Bryan Vyhmeister wrote:
> On Mon, Jul 31, 2017 at 05:37:00PM -0700, Bryan Vyhmeister wrote:
>> On Mon, Jul 31, 2017 at 08:09:31PM -0400, Ted Unangst wrote:
>>> Bryan Vyhmeister wrote:
 On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote:
> for you.  As always, a dmesg would be appreciated.  The output of
> # wsconsctl | grep 'mouse'
> could also be of interest here (you must run it as root).

 This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air.
 Anything more than a regular click is not working as can be seen from
 the wsconsctl output. I was using synclient to configure previously
 which did allow the other settings.
>>>
>>> Can you also share your synclient settings?
>>
>> Sure. I was using synclient(1) with the following settings but
>> synclient(1) no longer works with this driver.
>>
>> synclient ClickFinger2=2 ClickFinger3=3 PalmDetect=0 PalmMinWidth=4 
>> PalmMinZ=100
> 
> I wanted to clarify this for the record. Regular click is working fine
> as is two finger scrolling on the MacBook Air. What is not working is
> multi-finger click but that is not currently part of the driver which is
> probably why my synclient settings are significant. I noticed this on
> the MacBook Air because there are no separate touchpad buttons as there
> are on everything else I tested. I would love to see multi-finger click
> as part of the driver since it is essential on any touchpad without
> separate buttons which seems to be the more common scenario these days
> for laptops. Thanks again.
> 
> Bryan
> 
> 

Re: touchpad input driver: testing needed

[Ulf Brosziewski]

Hi,

thanks for testing!  Does "NOT OK" mean that two-finger
scrolling works badly, or that it doesn't work at all?
If possible, could you record the output of
$ xinput --test /dev/wsmouse0
for a short period of time and perform the scroll gesture?

Ulf

On 08/01/2017 11:09 AM, Olivier Antoine wrote:
> Mouse move: OK
> Mouse tapping: OK
> Two-fingers scrolling: NOT OK
> 
> Machine Lenovo Thinkpad E130
> 
> # wsconsctl | grep 'mouse'
> mouse.type=synaptics
> mouse.rawmode=0
> mouse.scale=1472,5768,1408,5236,0,66,175
> mouse.tp.tapping=1
> mouse.tp.scaling=0.160
> mouse.tp.swapsides=0
> mouse.tp.disable=0
> mouse1.type=ps2
> 
> 
> 
> On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski <
> ulf.brosziew...@t-online.de> wrote:
> 
>> In the long run the synaptics driver, which handles touchpad inputs in
>> X, may be a dead end of the input framework, and it's time to prepare
>> an alternative.  The kernel contains an internal touchpad input driver
>> now, it's a part of wsmouse(4).  It provides standard features -
>> two-finger/edge scrolling, software buttons for clickpads, tapping -
>> and various kinds of plankton required for usability.
>>
>> If you have a new snapshot (from July 27 or later) on a laptop with a
>> Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with
>> tests, more tests, and tests.  In order to activate the driver, add the
>> following entry to /etc/xorg.conf and restart X (if the file isn't
>> present, simply create it with this content):
>>
>> Section "InputClass"
>> Identifier "wsmouse touchpad"
>> Driver "ws"
>> MatchIsTouchpad "on"
>> EndSection
>>
>> While I dont't expect bugs in the input processing part of the
>> driver ;-), it is difficult to assess how well the automatic
>> configuration covers the zoo of models out there, presumably it will
>> need some more fine-grained distinctions of hardware properties.  I
>> would like to know where it works, works only halfway, or doesn't work
>> for you.  As always, a dmesg would be appreciated.  The output of
>> # wsconsctl | grep 'mouse'
>> could also be of interest here (you must run it as root).
>>
>> For now, X will treat the device like a mouse, please don't look for
>> touchpad-specific configuration options there.  Tapping can be enabled
>> by the command
>> # wsconsctl mouse.tp.tapping=1
>> If there is more than one wsmouse device, you should look up which one
>> has the "tp" fields and if it's not the first one (wsmouse0), add the
>> index to the prefix, e.g.
>> # wsconsctl mouse2.tp.tapping=1
>>
>> The base speed of the pointer can be adjusted by increasing or
>> decreasing the value of
>> # wsconsctl mouse.tp.scaling
>> Please don't confuse it with the 'mouse.scale' field.
>>
>> # wsconsctl mouse.tp.swapsides=1
>> will invert the order of software buttons areas (swapping external
>> buttons must still be configured in X). If edge scrolling is
>> enabled, the scroll area will be at the left edge of the touchpad.
>>
>> If you are using an external mouse device or a trackpoint, the command
>> # wsconsctl mouse.tp.disable=1
>> may be helpful.  It will disable pointer movement, scrolling, and
>> tapping.  External buttons and software buttons remain enabled.
>>
>>
> 

Does pf's Sources table ever get cleared?

[Markus Wernig]

Hi all

I have a pair of OBSD 6.1 firewalls, on which some rules require source
tracking, i.e. have a max-src-conn or similar statement as in:

pass  log  quick on { em0 vlan1 } inet proto tcp  from any  to
 port { 80, 443 } modulate state ( max-src-conn 50,
max-src-conn-rate 25/5, overload  flush global )

This works perfectly, any hosts that surpass that limit get blocked.

But on the other hand, the Sources table (as seen with pfctl -s Sources)
keeps growing. With every allowed connection, there are two new entries.
And it seems that the Sources table expands in one direction only. I.e.
even long after the relative connection has been flushed from the state
table, there are still the entries in the Sources table.

No matter what happens, the Sources keep expanding until the src-nodes
hard limit is reached. At which point only a reboot will help.

I've tried to flush them with pfctl -F Sources, but without success:

wall0101 # pfctl -s Sources | wc -l
 512
wall0101 # pfctl -F Sources
source tracking entries cleared
wall0101 # pfctl -s Sources | wc -l
 514

Is there any reason (presumably in my ruleset, but didn't find it) that
would keep entries in the Sources table from being cleared?
Shouldn't the tracking entries be removed when the corresponding states
are flushed and shouldn't pfctl -F Sources clear the Sources table?

Thx /markus

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Mon, Jul 31, 2017 at 05:37:00PM -0700, Bryan Vyhmeister wrote:
> On Mon, Jul 31, 2017 at 08:09:31PM -0400, Ted Unangst wrote:
> > Bryan Vyhmeister wrote:
> > > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote:
> > > > for you.  As always, a dmesg would be appreciated.  The output of
> > > > # wsconsctl | grep 'mouse'
> > > > could also be of interest here (you must run it as root).
> > > 
> > > This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air.
> > > Anything more than a regular click is not working as can be seen from
> > > the wsconsctl output. I was using synclient to configure previously
> > > which did allow the other settings.
> > 
> > Can you also share your synclient settings?
> 
> Sure. I was using synclient(1) with the following settings but
> synclient(1) no longer works with this driver.
> 
> synclient ClickFinger2=2 ClickFinger3=3 PalmDetect=0 PalmMinWidth=4 
> PalmMinZ=100

I wanted to clarify this for the record. Regular click is working fine
as is two finger scrolling on the MacBook Air. What is not working is
multi-finger click but that is not currently part of the driver which is
probably why my synclient settings are significant. I noticed this on
the MacBook Air because there are no separate touchpad buttons as there
are on everything else I tested. I would love to see multi-finger click
as part of the driver since it is essential on any touchpad without
separate buttons which seems to be the more common scenario these days
for laptops. Thanks again.

Bryan

Re: Split zone DNS?

[Stuart Henderson]

On 2017-07-31, Kenneth Gober  wrote:
> It's not totally clear whether
> it's even possible using nsd/unbound and the base dhcpd, but what I've
> seen indicates that it is not.

It could be done with some helper software to read the lease db
and convert to a zone file, or by reading logs and constructing
unbound-control commands to add/remove entries.

There's nothing pre-written afaik.

> So, what I am doing instead is I'm using isc-dhcp-server and isc-bind
> (from packages).

dnsmasq would be another option here.

Re: Calculate the frequency of the tsc timecounter

[Adam Steen]

Hi Mike

Please see the output below (I did have to update a few DPRINTF's with
the change to clang, did you want a diff for checking in?)
I appreciate you having a look.

Cheers
Adam

root on sd0a (15cc7df693e2251e.a) swap on sd0b dump on sd0b
vm_impl_init_vmx: created vm_map @ 0x80b99000
vm_resetcpu: resetting vm 1 vcpu 0 to power on defaults
guest eptp = 0x39eb8f01e
vmm_alloc_vpid: allocated VPID/ASID 1
vmx_handle_exit: unhandled exit 2147483681 (unknown)
vcpu @ 0x800032ffc000
 rax=0x rbx=0x rcx=0x
 rdx=0x rbp=0x rdi=0x5000
 rsi=0x  r8=0x  r9=0x
 r10=0x r11=0x r12=0x
 r13=0x r14=0x r15=0x
 rip=0x0010 rsp=0x1ff8
 cr0=0x0020 (pg cd nw am wp NE et ts em mp pe)
 cr2=0x
 cr3=0x (pwt pcd)
 cr4=0x2000 (pke smap smep osxsave pcide fsgsbase smxe
VMXE osxmmexcpt osfxsr pce pge mce pae pse de tsd pvi vme)
 --Guest Segment Info--
 cs=0x0008 rpl=0 base=0x limit=0x a/r=0xa099
  granularity=1 dib=0 l(64 bit)=1 present=1 sys=1 type=code, x only, accessed
code, r/x
 ds=0x0010 rpl=0 base=0x limit=0x a/r=0xc093
  granularity=1 dib=1 l(64 bit)=0 present=1 sys=1 type=data, r/w, accessed
 es=0x0010 rpl=0 base=0x limit=0x a/r=0xc093
  granularity=1 dib=1 l(64 bit)=0 present=1 sys=1 type=data, r/w, accessed
 fs=0x0010 rpl=0 base=0x limit=0x a/r=0xc093
  granularity=1 dib=1 l(64 bit)=0 present=1 sys=1 type=data, r/w, accessed
 gs=0x0010 rpl=0 base=0x limit=0x a/r=0xc093
  granularity=1 dib=1 l(64 bit)=0 present=1 sys=1 type=data, r/w, accessed
 ss=0x0010 rpl=0 base=0x limit=0x a/r=0xc093
  granularity=1 dib=1 l(64 bit)=0 present=1 sys=1 type=data, r/w, accessed
 tr=0x base=0x limit=0x a/r=0x008b
  granularity=0 dib=0 l(64 bit)=0 present=1 sys=0 type=tss (busy)
 gdtr base=0x1000 limit=0x0017
 idtr base=0x limit=0x
 ldtr=0x base=0x limit=0x a/r=0x1
  (unusable)
 --Guest MSRs @ 0xff039b869000 (paddr: 0x00039b869000)--
  MSR 0 @ 0xff039b869000 : 0xc080 (EFER),
value=0x0500 (sce LME LMA nxe)
  MSR 1 @ 0xff039b869010 : 0xc081 (STAR), value=0x
  MSR 2 @ 0xff039b869020 : 0xc082 (LSTAR), value=0x
  MSR 3 @ 0xff039b869030 : 0xc083 (CSTAR), value=0x
  MSR 4 @ 0xff039b869040 : 0xc084 (SFMASK), value=0x
  MSR 5 @ 0xff039b869050 : 0xc102 (KGSBASE), value=0x
vcpu @ 0x800032ffc000
parent vm @ 0xff0395ee7000
mode: VMX
pinbased ctls: 0x7f0016
true pinbased ctls: 0x7f0016
 EXTERNAL_INT_EXITING: Can set:Yes Can clear:Yes
 NMI_EXITING: Can set:Yes Can clear:Yes
 VIRTUAL_NMIS: Can set:Yes Can clear:Yes
 ACTIVATE_VMX_PREEMPTION_TIMER: Can set:Yes Can clear:Yes
 PROCESS_POSTED_INTERRUPTS: Can set:No Can clear:Yes
procbased ctls: 0xfff9fffe0401e172
true procbased ctls: 0xfff9fffe04006172
 INTERRUPT_WINDOW_EXITING: Can set:Yes Can clear:Yes
 USE_TSC_OFFSETTING: Can set:Yes Can clear:Yes
 HLT_EXITING: Can set:Yes Can clear:Yes
 INVLPG_EXITING: Can set:Yes Can clear:Yes
 MWAIT_EXITING: Can set:Yes Can clear:Yes
 RDPMC_EXITING: Can set:Yes Can clear:Yes
 RDTSC_EXITING: Can set:Yes Can clear:Yes
 CR3_LOAD_EXITING: Can set:Yes Can clear:Yes
 CR3_STORE_EXITING: Can set:Yes Can clear:Yes
 CR8_LOAD_EXITING: Can set:Yes Can clear:Yes
 CR8_STORE_EXITING: Can set:Yes Can clear:Yes
 USE_TPR_SHADOW: Can set:Yes Can clear:Yes
 NMI_WINDOW_EXITING: Can set:Yes Can clear:Yes
 MOV_DR_EXITING: Can set:Yes Can clear:Yes
 UNCONDITIONAL_IO_EXITING: Can set:Yes Can clear:Yes
 USE_IO_BITMAPS: Can set:Yes Can clear:Yes
 MONITOR_TRAP_FLAG: Can set:Yes Can clear:Yes
 USE_MSR_BITMAPS: Can set:Yes Can clear:Yes
 MONITOR_EXITING: Can set:Yes Can clear:Yes
 PAUSE_EXITING: Can set:Yes Can clear:Yes
procbased2 ctls: 0xff
 VIRTUALIZE_APIC: Can set:Yes Can clear:Yes
 ENABLE_EPT: Can set:Yes Can clear:Yes
 DESCRIPTOR_TABLE_EXITING: Can set:Yes Can clear:Yes
 ENABLE_RDTSCP: Can set:Yes Can clear:Yes
 VIRTUALIZE_X2APIC_MODE: Can set:Yes Can clear:Yes
 ENABLE_VPID: Can set:Yes Can clear:Yes
 WBINVD_EXITING: Can set:Yes Can clear:Yes
 UNRESTRICTED_GUEST: Can set:Yes Can clear:Yes
 APIC_REGISTER_VIRTUALIZATION: Can set:No Can clear:Yes
 VIRTUAL_INTERRUPT_DELIVERY: Can set:No Can clear:Yes
 PAUSE_LOOP_EXITING: Can 

Re: touchpad input driver: testing needed

[Olivier Antoine]

Mouse move: OK
Mouse tapping: OK
Two-fingers scrolling: NOT OK

Machine Lenovo Thinkpad E130

# wsconsctl | grep 'mouse'
mouse.type=synaptics
mouse.rawmode=0
mouse.scale=1472,5768,1408,5236,0,66,175
mouse.tp.tapping=1
mouse.tp.scaling=0.160
mouse.tp.swapsides=0
mouse.tp.disable=0
mouse1.type=ps2



On Mon, Jul 31, 2017 at 11:02 PM, Ulf Brosziewski <
ulf.brosziew...@t-online.de> wrote:

> In the long run the synaptics driver, which handles touchpad inputs in
> X, may be a dead end of the input framework, and it's time to prepare
> an alternative.  The kernel contains an internal touchpad input driver
> now, it's a part of wsmouse(4).  It provides standard features -
> two-finger/edge scrolling, software buttons for clickpads, tapping -
> and various kinds of plankton required for usability.
>
> If you have a new snapshot (from July 27 or later) on a laptop with a
> Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with
> tests, more tests, and tests.  In order to activate the driver, add the
> following entry to /etc/xorg.conf and restart X (if the file isn't
> present, simply create it with this content):
>
> Section "InputClass"
> Identifier "wsmouse touchpad"
> Driver "ws"
> MatchIsTouchpad "on"
> EndSection
>
> While I dont't expect bugs in the input processing part of the
> driver ;-), it is difficult to assess how well the automatic
> configuration covers the zoo of models out there, presumably it will
> need some more fine-grained distinctions of hardware properties.  I
> would like to know where it works, works only halfway, or doesn't work
> for you.  As always, a dmesg would be appreciated.  The output of
> # wsconsctl | grep 'mouse'
> could also be of interest here (you must run it as root).
>
> For now, X will treat the device like a mouse, please don't look for
> touchpad-specific configuration options there.  Tapping can be enabled
> by the command
> # wsconsctl mouse.tp.tapping=1
> If there is more than one wsmouse device, you should look up which one
> has the "tp" fields and if it's not the first one (wsmouse0), add the
> index to the prefix, e.g.
> # wsconsctl mouse2.tp.tapping=1
>
> The base speed of the pointer can be adjusted by increasing or
> decreasing the value of
> # wsconsctl mouse.tp.scaling
> Please don't confuse it with the 'mouse.scale' field.
>
> # wsconsctl mouse.tp.swapsides=1
> will invert the order of software buttons areas (swapping external
> buttons must still be configured in X). If edge scrolling is
> enabled, the scroll area will be at the left edge of the touchpad.
>
> If you are using an external mouse device or a trackpoint, the command
> # wsconsctl mouse.tp.disable=1
> may be helpful.  It will disable pointer movement, scrolling, and
> tapping.  External buttons and software buttons remain enabled.
>
>


dmesg
Description: Binary data

Re: Opensmtpd-extras documentation

[Markus Rosjat]

ok turns out it's not a LDAP problem at all ...

since openSMTPD doesn't authenticate with a plain password at all it 
will always fail.


regards

markus

Am 31.07.2017 um 17:44 schrieb Markus Rosjat:


 


Hi there,
Is there some documentation on the ldapFilter ? It's kinda frustrating to see a 
535 Auth failed even you are sure you got the right credentials.
I have openldap running but without some basic info on how to pass looked  up 
information  on to smtpd I'm lost here
Regards
Markus
Von meinem Samsung Gerät gesendet.



--
Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de

G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden

http://www.ghweb.de
fon: +49 351 8107220   fax: +49 351 8107227

Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before 
you print it, think about your responsibility and commitment to the 
ENVIRONMENT

Re: Calculate the frequency of the tsc timecounter

[Mike Larkin]

On Tue, Aug 01, 2017 at 07:32:19AM +0800, Adam Steen wrote:
> On Tue, Aug 1, 2017 at 7:26 AM, Adam Steen  wrote:
> > Mike Belopuhov wrote:
> >
> >> To be able to use TSC as a timecounter source on OpenBSD or Solo5
> >> you'd have to improve the in-kernel measurement of the TSC frequency
> >> first. I've tried to perform 10 measurements and take an average and
> >> it does improve accuracy, however I believe we need to poach another
> >> bit from Linux and re-calibrate TSC via HPET:
> >>
> >>  
> >> http://elixir.free-electrons.com/linux/v4.12.4/source/arch/x86/kernel/tsc.c#L409
> >>
> >> I think this is the most sane thing we can do. Here's a complete
> >> procedure that Linux kernel undertakes:
> >>
> >>  
> >> http://elixir.free-electrons.com/linux/v4.12.4/source/arch/x86/kernel/tsc.c#L751
> >>
> >> Regards,
> >> Mike
> >
> > Looks like i have more sort out!
> >
> > Mike Larkin wrote:
> >> If you point me to a bootable image that causes this failure, I might be
> >> able to figure out what vmm(4) doesn't like.
> >>
> >> Nothing in lines 122-134 of the file indicated above should cause this.
> >
> > This is where things get a little more interesting, Solo5
> > (https://github.com/adamsteen/solo5) is actually two parts Solo5 the
> > Unikernel and ukvm the userland side of a hypervisor (currently
> > running with kvm and bhyve), I have been porting to run ukvm directly
> > with vmm. I expect the cause of "vmx_handle_exit: unhandled exit
> > 2147483681 (unknown)" is the register setup in
> > https://github.com/adamsteen/solo5/blob/master/ukvm/ukvm_hv_openbsd_x86_64.c,
> > lines 118-147
> >
> > the constants are ukvm constants.
> >
> > struct vm_resetcpu_params vrp = {
> > .vrp_vm_id = hvb->vcp_id,
> > .vrp_vcpu_id = hvb->vcpu_id,
> > .vrp_init_state = {
> > .vrs_gprs[VCPU_REGS_RFLAGS] = X86_RFLAGS_INIT,
> > .vrs_gprs[VCPU_REGS_RIP] = gpa_ep,
> > .vrs_gprs[VCPU_REGS_RSP] = hv->mem_size - 8,
> > .vrs_gprs[VCPU_REGS_RDI] = X86_BOOT_INFO_BASE,
> > .vrs_crs[VCPU_REGS_CR0] = X86_CR0_INIT,
> > .vrs_crs[VCPU_REGS_CR3] = X86_CR3_INIT,
> > .vrs_crs[VCPU_REGS_CR4] = X86_CR4_INIT,
> > .vrs_sregs[VCPU_REGS_CS] = sreg_to_vsi(_x86_sreg_code),
> > .vrs_sregs[VCPU_REGS_DS] = sreg_to_vsi(_x86_sreg_data),
> > .vrs_sregs[VCPU_REGS_ES] = sreg_to_vsi(_x86_sreg_data),
> > .vrs_sregs[VCPU_REGS_FS] = sreg_to_vsi(_x86_sreg_data),
> > .vrs_sregs[VCPU_REGS_GS] = sreg_to_vsi(_x86_sreg_data),
> > .vrs_sregs[VCPU_REGS_SS] = sreg_to_vsi(_x86_sreg_data),
> > .vrs_gdtr = { 0x0, X86_GDTR_LIMIT, 0x0, X86_GDT_BASE},
> > .vrs_idtr = { 0x0, 0x, 0x0, 0x0},
> > .vrs_sregs[VCPU_REGS_LDTR] = 
> > sreg_to_vsi(_x86_sreg_unusable),
> > .vrs_sregs[VCPU_REGS_TR] = sreg_to_vsi(_x86_sreg_tr),
> > .vrs_msrs[VCPU_REGS_EFER] = X86_EFER_INIT,
> > .vrs_msrs[VCPU_REGS_STAR] = 0ULL,
> > .vrs_msrs[VCPU_REGS_LSTAR] = 0ULL,
> > .vrs_msrs[VCPU_REGS_CSTAR] = 0ULL,
> > .vrs_msrs[VCPU_REGS_SFMASK] = 0ULL,
> > .vrs_msrs[VCPU_REGS_KGSBASE] = 0ULL,
> > .vrs_crs[VCPU_REGS_XCR0] = XCR0_X87
> > }
> > };
> >
> > the three specific OpenBSD files are
> > https://github.com/adamsteen/solo5/blob/master/ukvm/ukvm_hv_openbsd.h
> > https://github.com/adamsteen/solo5/blob/master/ukvm/ukvm_hv_openbsd.c
> > https://github.com/adamsteen/solo5/blob/master/ukvm/ukvm_hv_openbsd_x86_64.c
> > with small changes in ukvm/ukvm_elf.c and ukvm/ukvm_module_net.c
> >
> > I could upload a binary image for you but It won't run with vmd its
> > has ukvm specific hypercalls designed to simplify things.
> >
> > Cheers
> > Adam
> >
> > ps i am currently trying to document the differences in what vmm is
> > expecting and ukvm is expecting.
> 

I'd recommend enabling VMM_DEBUG and seeing if that prints more useful
information after the unhandled exit. That error code is usually because of
invalid VMCS content, but since you're rolling your own vmm interface, it's
not clear what might have been missed. If you send me that information
(from dmesg, it will be a lot) I may be able to help.

-ml


> One more thing
> 
> Please note currently i have to build the bootable binary image of
> solo5 with a cross compiler as i have not figured out the
> discrepancies between OpenBSD's ld and solo5's linker script.
> 
> Cheers
> Adam

Re: Changing default compiler for usr/ports buiding

[Denis]

Ok, but how to point cmake-3.5.2 to build the needed "source" which
using Boost 1.53 or higher libraries ver.?

Boost 1.59.0 itself was downloaded from boost web site and builded from
sources using gcc 4.9 already. Some patches have been installed.

I have tried to point cmake-3.5.2 to Boost-1.59.0 (builded from source
by gcc 4.9) by using some documented hints
cmake -DBoost_NO_SYSTEM_PATHS=ON -DBOOST_ROOT=/boost-gcc49/output
-DBOOST_INCLUDEDIR=/boost-gcc49/output/include -
DBOOST_LIBRARYDIR=/boost-gcc49/output/lib
-DCMAKE_INSTALL_PREFIX=/build/src-output

But Cmake wan't see the prebuilded Boost 1.59.0 libraries, but clearly
sees the paths to Boost ROOT dir, include, and lib dirs.

So I tried to build Boost 1.58 which is a part of ports of OpenBSD 6.0
amd64 by newer compiler gcc 4.9 which is required for the sources build...

What can I do to have Boost 1.58 or Boost 1.59 builded by gcc 4.9 and
working with cmake-3.5.2 ?

Thanks for answer in advance.

On 31.07.2017 21:34, Marc Espie wrote:
> On Mon, Jul 31, 2017 at 05:47:59PM +0300, Denis wrote:
>> I'm trying to change default compiler to build some ports.
>> Tried to do it using bsd.port.mk and by system variables CXX=eg++
>> CPP=egcc, but nothing changes while building a port.
>>
>> How can I force the default gcc 4.2 to egcc (gcc 4.9)?
>>
>> Thanks
> You can't.
>
> Things generally won't work.
>
> Current uses clang on i386 and amd64.
>
> And that's wildly incompatible with gcc 4.2 or 4.9...
>