Re: WARNING: symbol(icudt58_dat) size mismatch, relink your program

2017-08-05 Thread Paul B. Henson
On Sat, Aug 05, 2017 at 12:35:24AM +, Stuart Henderson wrote:

> The ports@ list is a better venue for ports-related queries,
> please see this: https://marc.info/?l=openbsd-ports=150157643516239=2

Ah, ok, thanks for the pointer.

> This is not preventing programs from running.

Hmm, I could've sworn I got that message and then slapd failed to start.
Dunno, maybe I got confused. Once I'm done working with openldap mdb I'll
start over from scratch and try again and see what happens.

Thanks for the info...



Re: touchpad input driver: testing needed

2017-08-05 Thread Paul de Weerd
Hi Ulf,

On Fri, Aug 04, 2017 at 11:26:12PM +0200, Ulf Brosziewski wrote:
| Hi Paul,
| 
| thanks for your help.  Does tapping work when you use
| the synaptics driver?

Nope, it doesn't.

| In the test setup with ws and the internal driver there
| are some restrictions on tapping:
| 1) It is suppressed when the position is an edge area
| (presumably the software button area at the bottom
| edge in this case).

Normally, I'm tapping in the center of the touchpad.  But I've tried
various locations, all don't work.

| 2) The finger must not move by more than a certain
| distance, otherwise, the contact doesn't count as
| "tap".

I've tried quite a few times, but no luck.  I'm pretty sure at least
some of those attempts were in basically the same spot :)

| 3) It is suppressed when hardware buttons are being
| pressed.

I don't even try this :)

| Just to be sure, can you exclude that 1), 2), or 3) is
| the reason for the problem?  And neither one-, two-, nor
| three-finger taps work?

I can: no tapping works, with any number of fingers.  I should,
however, clarify one thing:

| > This doesn't work on my touchpad.  Also, I can't click-and-drag (never
| > worked, in any combination I while playing with the driver settings).

This 'click-and-drag' behaviour does work if I click, keep the button
depressed and then move that same finger around.  So I can't click
with one finger and drag with another.

Cheers,

Paul

-- 
>[<++>-]<+++.>+++[<-->-]<.>+++[<+
+++>-]<.>++[<>-]<+.--.[-]
 http://www.weirdnet.nl/ 



radeondrm(?) change causes console to recognize only 1024x768

2017-08-05 Thread Robert
Hi,

During the last couple of weeks some change (radeondrm update?) caused the 
console to be locked to 1024x768, instead of whatever EDID the TFT supports, 
when using a Radeon card.

I've seen this on two machines; full dmesg and Xorg for one is below.

As a side effect, Xorg also doesn't support higher resolutions out of the box 
anymore. Adding a manual modeline section in xorg.conf is a workaround. But 
when using two TFTs I have to use Xinerama now, which prevents temporarily 
switching one screen to a different solutions ("RandR extension missing"). The 
Xorg log below is without any xorg.conf.

How can I get the console back to full resolution?

regards,
Robert


OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug  3 12:12:07 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17113550848 (16320MB)
avail mem = 16588537856 (15820MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec380 (81 entries)
bios0: vendor Dell Inc. version "A15" date 02/15/2017
bios0: Dell Inc. OptiPlex 3020
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT SLIC SSDT SSDT SSDT HPET SSDT MCFG SSDT
acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) PXSX(S4) RP04(S4) 
PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S0) 
EHC2(S0) XHC_(S0) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, 3292.85 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 3292846410 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, 3292.39 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, 3292.39 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, 3292.39 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (RP01)
acpiprt2 at acpi0: bus 3 (RP04)
acpiprt3 at acpi0: bus 4 (RP05)
acpiprt4 at acpi0: bus 5 (RP06)
acpiprt5 at acpi0: bus 1 (PEG0)
acpiprt6 at acpi0: bus -1 (PEG1)
acpiprt7 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: FN00, resource for FAN0
acpipwrres1 at acpi0: FN01, resource for FAN1
acpipwrres2 at acpi0: FN02, resource for FAN2
acpipwrres3 at acpi0: FN03, resource for FAN3
acpipwrres4 at acpi0: FN04, resource for FAN4
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
"INT3F0D" at acpi0 not configured
acpibtn0 at acpi0: PWRB
"PNP0C14" at acpi0 not configured

Re: Nmap Hangs while scanning

2017-08-05 Thread Zuleyha Torku
Ofcourse, you are right. I did not see that lines mentioning "no space
left" at first sight. Sorry, I'll look into that problem first.

Thank you so much

On 5 Aug 2017 5:22 p.m., "Ax0n"  wrote:

> From your dmesg, my first suggestion would be to look at the cause of
> what's filling up / and /home (per the snippet from your dmesg pasted below
> my response). Next, I'd upgrade to a supported release (OpenBSD 6.1) and
> fully update it with syspatch, then try nmap again. If it persists, try
> again using the latest snapshot (-CURRENT) if you can. I use nmap
> frequently from i386, sparc64 and amd64 and haven't had this problem. It
> still looks like nmap might be exhausting your hard drive space. What
> arguments are you passing to nmap? We don't need to see the IP addresses
> you're scanning, but it would help to know how many IPs are you scanning at
> a time as well.
>
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
>
> On Sat, Aug 5, 2017 at 8:29 AM, Zuleyha Torku 
> wrote:
>
>> Hi
>> I'm trying to scan a bunch of IP address with nmap on OpenBSD 5.9 amd64.
>> After a few moments nmap hangs but not crash or fall into unresponsive
>> state. When I check with tcpdump it stops packet generation. No Error
>> messages, no warning. Cpu and Mem. usages are normal as usual.
>>
>> I could not get any error that help me to define what is the problem even
>> if I set verbose option.
>> Have you ever seen this behaviour ? How can I go further ?
>>
>>
>>
>>
>> OpenBSD 5.9 (GENERIC) #1761: Fri Feb 26 01:15:04 MST 2016
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
>> real mem = 1056817152 (1007MB)
>> avail mem = 1020686336 (973MB)
>> mpath0 at root
>> scsibus0 at mpath0: 256 targets
>> mainbus0 at root
>> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6a20 (9 entries)
>> bios0: vendor SeaBIOS version "
>> rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org" date 04/01/2014
>> bios0: QEMU Standard PC (i440FX + PIIX, 1996)

Re: Nmap Hangs while scanning

2017-08-05 Thread Ax0n
>From your dmesg, my first suggestion would be to look at the cause of
what's filling up / and /home (per the snippet from your dmesg pasted below
my response). Next, I'd upgrade to a supported release (OpenBSD 6.1) and
fully update it with syspatch, then try nmap again. If it persists, try
again using the latest snapshot (-CURRENT) if you can. I use nmap
frequently from i386, sparc64 and amd64 and haven't had this problem. It
still looks like nmap might be exhausting your hard drive space. What
arguments are you passing to nmap? We don't need to see the IP addresses
you're scanning, but it would help to know how many IPs are you scanning at
a time as well.

uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full

On Sat, Aug 5, 2017 at 8:29 AM, Zuleyha Torku 
wrote:

> Hi
> I'm trying to scan a bunch of IP address with nmap on OpenBSD 5.9 amd64.
> After a few moments nmap hangs but not crash or fall into unresponsive
> state. When I check with tcpdump it stops packet generation. No Error
> messages, no warning. Cpu and Mem. usages are normal as usual.
>
> I could not get any error that help me to define what is the problem even
> if I set verbose option.
> Have you ever seen this behaviour ? How can I go further ?
>
>
>
>
> OpenBSD 5.9 (GENERIC) #1761: Fri Feb 26 01:15:04 MST 2016
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> real mem = 1056817152 (1007MB)
> avail mem = 1020686336 (973MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6a20 (9 entries)
> bios0: vendor SeaBIOS version "
> rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org" date 04/01/2014
> bios0: QEMU Standard PC (i440FX + PIIX, 1996)
> acpi0 at bios0: rev 0
> acpi0: sleep states S3 S4 S5
> acpi0: tables DSDT FACP APIC HPET
> acpi0: wakeup devices
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Westmere E56xx/L56xx/X56xx (Nehalem-C), 2200.29 MHz
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> 

Nmap Hangs while scanning

2017-08-05 Thread Zuleyha Torku
Hi
I'm trying to scan a bunch of IP address with nmap on OpenBSD 5.9 amd64.
After a few moments nmap hangs but not crash or fall into unresponsive
state. When I check with tcpdump it stops packet generation. No Error
messages, no warning. Cpu and Mem. usages are normal as usual.

I could not get any error that help me to define what is the problem even
if I set verbose option.
Have you ever seen this behaviour ? How can I go further ?




OpenBSD 5.9 (GENERIC) #1761: Fri Feb 26 01:15:04 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1056817152 (1007MB)
avail mem = 1020686336 (973MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6a20 (9 entries)
bios0: vendor SeaBIOS version "
rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org" date 04/01/2014
bios0: QEMU Standard PC (i440FX + PIIX, 1996)
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Westmere E56xx/L56xx/X56xx (Nehalem-C), 2200.29 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,HV,NXE,LONG,LAHF,ARAT
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 999MHz
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
pvbus0 at mainbus0: KVM
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel
0 wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int
9
iic0 at piixpm0
vga1 at pci0 dev 2 function 0 "Bochs VGA" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
vio0 at virtio0: address 52:54:00:a5:1f:57
virtio0: apic 0 int 11
eap0 at pci0 dev 4 function 0 "Ensoniq AudioPCI" rev 0x00: apic 0 int 11
audio0 at eap0
midi0 at eap0: 
virtio1 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00
vioblk0 at virtio1
scsibus1 at vioblk0: 2 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct fixed
sd0: 51200MB, 512 bytes/sector, 104857600 sectors
virtio1: apic 0 int 10
virtio2 at pci0 dev 6 function 0 "Qumranet Virtio Memory" rev 0x00
viomb0 at virtio2
virtio2: apic 0 int 10
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 1: density unknown
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
nvram: invalid checksum
uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet"
rev 2.00/0.00 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 3 buttons, Z dir
wsmouse1 at ums0 mux 0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (0077973165a15151.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
clock: unknown CMOS layout
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 

Re: touchpad input driver: testing needed

2017-08-05 Thread Niklas Wennerstrand
This is from a Dell xps 9333 model which has a Synaptics
touchpad which has been working fine otherwise and appears to continue
to work fine with your driver.

wsconsctl

mouse.type=synaptics
mouse.rawmode=0
mouse.scale=1472,5676,1408,4722,0,45,60
mouse.tp.tapping=1
mouse.tp.scaling=0.172
mouse.tp.swapsides=0
mouse.tp.disable=0


dmesg:


Aug  5 09:06:14 dark /bsd: OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug  3 
12:12:07 MDT 2017
Aug  5 09:06:14 dark /bsd: 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Aug  5 09:06:14 dark /bsd: real mem = 8068243456 (7694MB)
Aug  5 09:06:14 dark /bsd: avail mem = 7817363456 (7455MB)
Aug  5 09:06:14 dark /bsd: mpath0 at root
Aug  5 09:06:14 dark /bsd: scsibus0 at mpath0: 256 targets
Aug  5 09:06:14 dark /bsd: mainbus0 at root
Aug  5 09:06:14 dark /bsd: bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0fc0 (69 
entries)
Aug  5 09:06:14 dark /bsd: bios0: vendor Dell Inc. version "A08" date 08/31/2015
Aug  5 09:06:14 dark /bsd: bios0: Dell Inc. XPS13 9333
Aug  5 09:06:14 dark /bsd: acpi0 at bios0: rev 2
Aug  5 09:06:14 dark /bsd: acpi0: sleep states S0 S1 S3 S4 S5
Aug  5 09:06:14 dark /bsd: acpi0: tables DSDT FACP ASF! HPET LPIT APIC MCFG 
SSDT SSDT SSDT SSDT UEFI POAT BATB FPDT SLIC UEFI CSRT
Aug  5 09:06:14 dark /bsd: acpi0: wakeup devices P0P1(S4) GLAN(S4) EHC1(S4) 
EHC2(S4) XHC_(S4) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) 
PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) […]
Aug  5 09:06:14 dark /bsd: acpitimer0 at acpi0: 3579545 Hz, 24 bits
Aug  5 09:06:14 dark /bsd: acpihpet0 at acpi0: 14318179 Hz
Aug  5 09:06:14 dark /bsd: acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
Aug  5 09:06:14 dark /bsd: cpu0 at mainbus0: apid 0 (boot processor)
Aug  5 09:06:14 dark /bsd: cpu0: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 
2594.44 MHz
Aug  5 09:06:14 dark /bsd: cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
Aug  5 09:06:14 dark /bsd: cpu0: 256KB 64b/line 8-way L2 cache
Aug  5 09:06:14 dark /bsd: cpu0: TSC frequency 2594437250 Hz
Aug  5 09:06:14 dark /bsd: cpu0: smt 0, core 0, package 0
Aug  5 09:06:14 dark /bsd: mtrr: Pentium Pro MTRR support, 10 var ranges, 88 
fixed ranges
Aug  5 09:06:14 dark /bsd: cpu0: apic clock running at 99MHz
Aug  5 09:06:14 dark /bsd: cpu0: mwait min=64, max=64, 
C-substates=0.2.1.2.4.1.1.1, IBE
Aug  5 09:06:14 dark /bsd: cpu1 at mainbus0: apid 1 (application processor)
Aug  5 09:06:14 dark /bsd: cpu1: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 
2594.00 MHz
Aug  5 09:06:14 dark /bsd: cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
Aug  5 09:06:14 dark /bsd: cpu1: 256KB 64b/line 8-way L2 cache
Aug  5 09:06:14 dark /bsd: cpu1: smt 1, core 0, package 0
Aug  5 09:06:14 dark /bsd: cpu2 at mainbus0: apid 2 (application processor)
Aug  5 09:06:14 dark /bsd: cpu2: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 
2594.00 MHz
Aug  5 09:06:14 dark /bsd: cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
Aug  5 09:06:14 dark /bsd: cpu2: 256KB 64b/line 8-way L2 cache
Aug  5 09:06:14 dark /bsd: cpu2: smt 0, core 1, package 0
Aug  5 09:06:14 dark /bsd: cpu3 at mainbus0: apid 3 (application processor)
Aug  5 09:06:14 dark /bsd: cpu3: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 
2594.00 MHz
Aug  5 09:06:14 dark /bsd: cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
Aug  5 09:06:14 dark /bsd: cpu3: 256KB 64b/line 8-way L2 cache
Aug  5 09:06:14 dark /bsd: cpu3: smt 1, core 1, package 0
Aug  5 09:06:14 dark /bsd: ioapic0 at mainbus0: apid 2 pa 0xfec0, version 
20, 40 pins
Aug  5 09:06:14 dark /bsd: acpimcfg0 at acpi0 addr 0xf800, bus 0-63
Aug  5 09:06:14 dark /bsd: acpiprt0 at acpi0: bus 0 (PCI0)
Aug  5 09:06:14 dark /bsd: acpiprt1 at acpi0: bus -1 (P0P1)
Aug  5 09:06:14 dark /bsd: acpiprt2 at acpi0: 

Re: touchpad input driver: testing needed

2017-08-05 Thread Daniel Gracia
Hi there!

A ThinkPad T460s over here working like a charm; some verbose output below.

Regards,

$
$ doas wsconsctl | grep mouse
wsconsctl: Use explicit arg to view keyboard.map.
mouse.type=synaptics
mouse.rawmode=0
mouse.scale=1472,5676,1408,4762,0,45,69
mouse.tp.tapping=1
mouse.tp.scaling=0.171
mouse.tp.swapsides=0
mouse.tp.disable=0
mouse1.type=ps2
$
$ dmesg
OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug  3 12:12:07 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8304578560 (7919MB)
avail mem = 8046538752 (7673MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xcf054000 (65 entries)
bios0: vendor LENOVO version "N1CET58W (1.26 )" date 06/30/2017
bios0: LENOVO 20F9005CMS
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP TCPA SSDT SSDT TPM2 UEFI SSDT SSDT ECDT HPET APIC
MCFG SSDT DBGP DBG2 BOOT BATB SLIC SSDT SSDT MSDM DMAR ASF! FPDT UEFI
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpihpet0 at acpi0: 2399 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 24 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 23MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 2 (EXP1)
acpiprt5 at acpi0: bus -1 (EXP2)
acpiprt6 at acpi0: bus 4 (EXP3)
acpiprt7 at acpi0: bus -1 (EXP5)
acpiprt8 at acpi0: bus -1 (RP09)
acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI
acpipwrres1 at acpi0: PG00, resource for PEG0
acpipwrres2 at acpi0: PG01, resource for PEG1
acpipwrres3 at acpi0: PG02, resource for PEG2
acpipwrres4 at acpi0: WRST
acpipwrres5 at acpi0: WRST
acpitz0 at acpi0: critical temperature is 128 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"LEN0071" at acpi0 not configured
"LEN004B" at acpi0 not configured
"INT3F0D" at acpi0 not configured
acpibat0 at acpi0: BAT0 model 

Re: Please Advise on licencing

2017-08-05 Thread Siju George
Thank you so much Ingo. Things are very clear.  :-)

On Aug 5, 2017 8:58 AM, "Ingo Schwarze"  wrote:

> Hi Siju,
>
> Siju George wrote on Sat, Aug 05, 2017 at 06:50:12AM +0530:
>
> > In a code repository should the licence wording be on every file ?
>
> Best practice is:
>
>  1. To have at least one line containing "Copyright (c) ..."
> at the top of each file containing copyrightable content.
>
>  2. Each author (natural person, NOT legal entity like corporations
> or foundations) who made copyrightable contributions to the
> file of which at least parts are still contained in the
> file must be mentioned on such a line.
> If an author did transfer their economic rights (which doesn't
> really make much sense for ISC or BSD 2-clause licensed code,
> but nonetheless, it is occasionally done), you can list the
> legal entity that acquired the economic rights, but then it
> becomes important to add a line, below the Copyright notice,
> reading, for example:
>   Parts of this file were written by (name of natural person)
>   for (name of legal entity).
> The reason is that the actual authors retain some inalienable
> rights, even when working for hire or contract, and the right
> to be know of as the author is one of these rights that can
> neither be sold nor be given away.
>
>  3. Each Copyright line must contain one year number, separated
> with commas, for each year in which that author made copyrightable
> additions to the file that are still present in the file.  Ranges
> of years separated with dashes are only acceptable if that
> author also made such contributions in each of the years between
> the endpoints of the range.  Usually, only use ranges on lines
> that would otherwise become too long.
>
> Look at /usr/src/usr.bin/mandoc/mdoc_term.c for an example
> demonstrating all these rules.
>
> The full text of the license should follow this Copyright notice
> in each file.
>
>
> That said, from a legal standpoint, it is sufficient to have one
> license for each Work, so having one Copyright notice for the whole
> Work (e.g., program or package) is legally sufficient, too.  But
> that is not a particularly good idea for several reasons:
>
>  1. It is less clear and can cause doubt as to which files are
> covered by the central Copyright notice and license.
>
>  2. It is very hard to maintain correctly.  Care is already needed
> when maintaining the notices in individual files, and maintaining
> a central notice correctly is even harder because it is no
> longer even clear in which files to look for the contributions
> of the various authors.
>
>  3. In practice, you will probably sooner or later include files
> from third parties that are available under free licenses.  In
> that case, leaving the Copyright notices and licenses in place
> in those included files is usually required by the third party
> licenses, and those licenses often differs slightly from the
> one you are using for your own Work.  So you end up with some
> files with Copyright notices and licenses and some without,
> which exacerbates the problem explained in item 1.
>
>  4. People maintaining other software will occasionally pick files
> from your software and copy them to their own package.  If you
> failed to add a Copyright notice and license to a file that
> gets picked in this way, there is a higher risk that the person
> taking the file forgets to copy your Copyright notice and license
> into the file before redistributing it.  And worse, how is that
> person even supposed to figure out who, and during which years,
> contributed to that particular file?  Basically, that poor soul
> will be forced to analyze the complete VCS commit history for
> the file and reconstruct the Copyright notice from scratch.
>
> > Or just in a file named "Licence" in the root folder ?
>
> Best practice is to do that *in addition*, because with many files,
> it can be hard to figure out the full list of Copyright holders and
> applicable licenses, and also because you almost certainly want to
> state *somewhere* which the preferred license is for new contributions
> to the project.
>
> For an example of such an additional central file demonstrating
> many useful features of such a central file, refer to
>
>   http://mandoc.bsd.lv/LICENSE
>
>
> Oh, and very important:  Never add any Copyright or license goo to
> the displayed text of any manual page or the stdout or stderr output
> of any program.  Copyright notices and licenses belong into the
> source code (of programs and documentation), *NEVER UNDER ANY
> CIRCUMSTANCES* into any text displayed to the user.  I regard
> displaying Copyright notices or licenses to the user as exceedingly
> impolite, because you are basically slapping the user into the face
> with this sneer: i value your time so little that i