Re: OpenBSD Puffy Stickers

[Rudy Baker]

Alright guys, he gets it. I wouldn't want to have to read two obligatory
leaving letters in one week :)


On Dec 1, 2017 1:31 AM, "Eric Furman"  wrote:

On Thu, Nov 30, 2017, at 11:07 PM, Theo de Raadt wrote:
> > Currently the OpenBSD store has mugs, t-shirts, posters, and CDs. All of
> > those require more expense than stickers. Stickers are rather
inexpensive
> > to produce, can be sold for high markup, and cost very little to ship,
not
> > to mention are very popular, especially in the tech industry.
> >
> > It wouldn't require any new artwork or commissions. If you were to sell
> > Puffy stickers or OpenBSD Logo stickers I'm sure they'd be top-sellers.
> >
> > Case in point, UnixStickers.com charges $2.69 per sticker and that
doesn't
> > include shipping.
>
> Why should I do that?  You only thought of yourself.
>
> What is in it for me?
>
> NOTHING.
>
> So why should I do this for you?
>
> If you think I should, and you repeatedly send mails saying so I can
> only conclude one thing:
>
> You have a self-entitlement issue.
>

This *MIGHT* be a great idea, but...
WHO IS GOING TO DO IT?
I don't want Theo or any of the Devs wasting their time doing crap like
this
that might just turn out to be a wast of time. They should be coding.
People are always asking "What can I do to help the Project"?
What people can do is to DO something and not talk about it.
So, make a batch of stickers yourself and sell them on ebay.
Then you can see for yourself just how Big A Seller they can be.
I'm going to bet that it will turn out to take a lot more time and
effort than you think and that it will turn very little if any profit.
But hey, don't let me stop you.
Good luck.

Re: KVM / Proxmox Hosted OpenBSD Boxes Multiqueue Virtio Query

[Stefan Fritsch]

On Friday, 1 December 2017 02:27:53 CET Tom Smyth wrote:
> Hello All
> I havent seen much by way of advice about multiqueue virtio
> support on OpenBSD and I was wondering do other users use it ?
> does anyone have experience with setting the number of virtio
> queues in Proxmox for an OpenBSD guest ?
> It is suggested by
> proxmox  / KVM to set the number of Queues presented to a vm
> to be = the number of vCPUs you have assigned to the Guest.

openbsd does not yet support multiqueue for virtio and it does not make much 
sense to add that until the network stack is more parallel.

Cheers,
Stefan

Re: Lanner NCA-4010D

[Daniel Ouellet]

No I don't have that one.

To small for a router for me where I want to use it.

I am not saying it's good or bad, I don't have a clue, just that I need
way more port then this have and it is NOT to use at home either.

Now as to where I but them, I sure can put you in touch with my rep. I
have been working with him as far back as December 1989.

I always buy my stuff from him for many years and he always been good to
me oppose to any others that just want the sale and move on, or big
company that have no clue who you are!!!

Not sure where you are, but if in the US, I am sure he would be happy to
help you.

I can provide you his contact in private if you like that.

I sure can recommend him and I did many times in the pass.

Good luck for your setup.

Daniel


On 12/1/17 1:45 AM, Rupert Gallagher wrote:
> Do you have a dmesg for nca-1510?
> 
> http://www.lannerinc.com/products/network-appliances/x86-desktop-network-appliances/nca-1510
> 
> Besides, how did you buy them?
> 
> Sent from ProtonMail Mobile
> 
> On Fri, Dec 1, 2017 at 05:24, Daniel Ouellet  wrote:
> 
>> Just for the records as I know I was looking to find a dmesg for them and 
>> see if that would run OpenBSD before taking the chance to get them and it 
>> might be of interest to others as well. Here it goes with 4 more to come all 
>> run well so far. More update later after I test them as routers and see. 
>> That's why I got them in the first place so will see what I can do with 
>> these to replace Cisco gears! This may help others too. 
>> +++ OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 
>> CEST 2017 
>> r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>>  real mem = 34239832064 (32653MB) avail mem = 33195106304 (31657MB) mpath0 
>> at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: 
>> SMBIOS rev. 3.0 @ 0xeddc0 (101 entries) bios0: vendor American Megatrends 
>> Inc. version "5.11" date 07/29/2016 bios0: Default string Default string 
>> acpi0 at bios0: rev 2 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC 
>> FPDT FIDT MCFG UEFI DBG2 HPET MSCT SLIT SRAT WDDT SSDT SSDT SSDT PRAD DMAR 
>> acpi0: wakeup devices IP2P(S0) XHCI(S0) EHC1(S0) EHC2(S0) RP01(S0) RP02(S0) 
>> RP03(S0) RP04(S0) RP05(S0) RP06(S0) RP07(S0) RP08(S0) BR1A(S0) BR1B(S0) 
>> BR2A(S0) BR2B(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) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.61 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
>>  cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 1995611240 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, IBE cpu1 at mainbus0: apid 2 (application processor) 
>> cpu1: Intel(R) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.38 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,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) Xeon(R) CPU D-1548 @ 
>> 2.00GHz, 1995.38 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,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) Xeon(R) CPU D-1548 @ 
>> 2.00GHz, 1995.38 MHz cpu3: 
>> 

Re: Lanner NCA-4010D

[Rupert Gallagher]

Do you have a dmesg for nca-1510?

http://www.lannerinc.com/products/network-appliances/x86-desktop-network-appliances/nca-1510

Besides, how did you buy them?

Sent from ProtonMail Mobile

On Fri, Dec 1, 2017 at 05:24, Daniel Ouellet  wrote:

> Just for the records as I know I was looking to find a dmesg for them and see 
> if that would run OpenBSD before taking the chance to get them and it might 
> be of interest to others as well. Here it goes with 4 more to come all run 
> well so far. More update later after I test them as routers and see. That's 
> why I got them in the first place so will see what I can do with these to 
> replace Cisco gears! This may help others too. +++ 
> OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017 
> r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP 
> real mem = 34239832064 (32653MB) avail mem = 33195106304 (31657MB) mpath0 at 
> root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: 
> SMBIOS rev. 3.0 @ 0xeddc0 (101 entries) bios0: vendor American Megatrends 
> Inc. version "5.11" date 07/29/2016 bios0: Default string Default string 
> acpi0 at bios0: rev 2 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC 
> FPDT FIDT MCFG UEFI DBG2 HPET MSCT SLIT SRAT WDDT SSDT SSDT SSDT PRAD DMAR 
> acpi0: wakeup devices IP2P(S0) XHCI(S0) EHC1(S0) EHC2(S0) RP01(S0) RP02(S0) 
> RP03(S0) RP04(S0) RP05(S0) RP06(S0) RP07(S0) RP08(S0) BR1A(S0) BR1B(S0) 
> BR2A(S0) BR2B(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) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.61 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
>  cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 1995611240 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, IBE cpu1 at mainbus0: apid 2 (application processor) 
> cpu1: Intel(R) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.38 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,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) Xeon(R) CPU D-1548 @ 
> 2.00GHz, 1995.38 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,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) Xeon(R) CPU D-1548 @ 
> 2.00GHz, 1995.38 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
>  cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at 
> mainbus0: apid 8 (application processor) cpu4: Intel(R) Xeon(R) CPU D-1548 @ 
> 2.00GHz, 1995.38 MHz cpu4: 
> 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
>  cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 4, package 0 cpu5 at 
> mainbus0: apid 10 (application processor) cpu5: Intel(R) Xeon(R) CPU D-1548 @ 
> 2.00GHz, 1995.38 MHz cpu5: 
> 

Re: OpenBSD Puffy Stickers

[Eric Furman]

On Thu, Nov 30, 2017, at 11:07 PM, Theo de Raadt wrote:
> > Currently the OpenBSD store has mugs, t-shirts, posters, and CDs. All of
> > those require more expense than stickers. Stickers are rather inexpensive
> > to produce, can be sold for high markup, and cost very little to ship, not
> > to mention are very popular, especially in the tech industry.
> > 
> > It wouldn't require any new artwork or commissions. If you were to sell
> > Puffy stickers or OpenBSD Logo stickers I'm sure they'd be top-sellers.
> > 
> > Case in point, UnixStickers.com charges $2.69 per sticker and that doesn't
> > include shipping.
> 
> Why should I do that?  You only thought of yourself.
> 
> What is in it for me?
> 
> NOTHING.
> 
> So why should I do this for you?
> 
> If you think I should, and you repeatedly send mails saying so I can
> only conclude one thing:
> 
> You have a self-entitlement issue.
> 

This *MIGHT* be a great idea, but...
WHO IS GOING TO DO IT?
I don't want Theo or any of the Devs wasting their time doing crap like
this
that might just turn out to be a wast of time. They should be coding.
People are always asking "What can I do to help the Project"?
What people can do is to DO something and not talk about it.
So, make a batch of stickers yourself and sell them on ebay.
Then you can see for yourself just how Big A Seller they can be.
I'm going to bet that it will turn out to take a lot more time and
effort than you think and that it will turn very little if any profit.
But hey, don't let me stop you.
Good luck.

Re: xterm(1) changing UTF-8 characters when copy-pasting?

[Anthony J. Bentley]

Hi Ingo,

Ingo Schwarze writes:
> Except in a professional typesetting system like groff or LaTeX, i
> consider anything that makes the end user worry about fonts
> fundamentally broken.

I think everybody's in agreement that xterm is broken and wrong here.

> Fonts that work should be installed by default
> and not configurable, in my opinion.  Toying around with fonts
> causes nothing but grief.

You'll need extra fonts once I finish my patch to add situationally
appropriate emoji to all our manpages.

> +*precompose: false

Sure.

> +*VT100.utf8: 1

xterm(1):
This option and the utf8 resource are overridden by the -lc and
-en options and locale resource.

We set the locale resource, so this appears redundant.

> +*VT100.font2: -misc-fixed-medium-r-normal--8-80-75-75-c-50-iso10646-1
> +*VT100.font:  -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646
> -1
> +*VT100.font3: -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1
> +*VT100.font4: -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1
> +*VT100.font5: -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
> +*VT100.font6: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1

These are already the default according to appres(1).

-- 
Anthony J. Bentley

Re: OpenBSD Puffy Stickers

[Nicolai]

On Thu, Nov 30, 2017 at 10:17:22PM -0600, Jay Williams wrote:
> > Why should I do that?  You only thought of yourself.
> 
> Why then do you have any products on the OpenBSD store?

In a previous mail from Theo in this thread, he stated that stickers
were "a loss-generating venture."  You responded by top-posting, stating
that "I'm sure they'd be top-sellers."  Didn't seem like you read his
mail.

Feel free to pay an artist to create original artwork and then sell that
artwork as stickers, and then donate all the money to OpenBSD.  THAT is
how you can accomplish your goal of funding OpenBSD - you don't need to
debate anyone here.  Just do it.

Theo said he won't do it.  You may as well argue with him about what his
favorite music is or something else that's entirely up to him... these
kinds of things aren't debatable issues.

Un-asked for advice is nearly always bad advice.

Nicolai

Re: OpenBSD Puffy Stickers

[Richard Thornton]

I don't like stickers on my computers.  I don't do bumper stickers either.

On Thu, Nov 30, 2017 at 11:29 PM, Theo de Raadt  wrote:

> > My goal is not to rip off anyone, but to help the project.
>
> You cannot help the project by begging on a mailing list that
> I partake in business.
>
> Get over yourself Jay.
>
>

Lanner FW-8759A

[Daniel Ouellet]

OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017

r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17104031744 (16311MB)
avail mem = 16578637824 (15810MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec200 (78 entries)
bios0: vendor American Megatrends Inc. version "4.6.5" date 03/02/2015
bios0: INTEL Corporation DENLOW_WS
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC FPDT SSDT MCFG HPET SSDT SSDT ASF! DMAR
EINJ ERST HEST BERT
acpi0: wakeup devices PXSX(S0) RP01(S0) PXSX(S0) RP02(S0) PXSX(S0)
RP03(S0) PXSX(S0) RP04(S0) PXSX(S0) RP05(S0) PXSX(S0) RP06(S0) PXSX(S0)
RP07(S0) PXSX(S0) GLAN(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) Xeon(R) CPU E3-1271 v3 @ 3.60GHz, 3600.50 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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 3600496320 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) Xeon(R) CPU E3-1271 v3 @ 3.60GHz, 3600.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,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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,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) Xeon(R) CPU E3-1271 v3 @ 3.60GHz, 3600.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,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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,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) Xeon(R) CPU E3-1271 v3 @ 3.60GHz, 3600.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,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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz, 3600.00 MHz
cpu4:
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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz, 3600.00 MHz
cpu5:
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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 1, package 0
cpu6 at mainbus0: apid 5 (application processor)
cpu6: Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz, 3600.00 MHz
cpu6:
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,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 1, core 2, package 0
cpu7 at mainbus0: apid 7 (application processor)
cpu7: Intel(R) 

Lanner FW-7573B

[Daniel Ouellet]

OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017

r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17149325312 (16354MB)
avail mem = 16622563328 (15852MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x7f4e3000 (54 entries)
bios0: vendor American Megatrends Inc. version "5.6.5" date 04/07/2017
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP FPDT MCFG WDAT UEFI APIC BDAT HPET SSDT SPCR
HEST BERT ERST EINJ
acpi0: wakeup devices PEX1(S0) PEX2(S0) PEX3(S0) PEX4(S0) EHC1(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU C2518 @ 1.74GHz, 1750.32 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: TSC frequency 1750316400 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 83MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU C2518 @ 1.74GHz, 1750.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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Atom(TM) CPU C2518 @ 1.74GHz, 1750.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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Atom(TM) CPU C2518 @ 1.74GHz, 1750.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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEX1)
acpiprt2 at acpi0: bus 2 (PEX2)
acpiprt3 at acpi0: bus 3 (PEX3)
acpiprt4 at acpi0: bus 4 (PEX4)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpicpu2 at acpi0: C1(@1 halt!)
acpicpu3 at acpi0: C1(@1 halt!)
"PNP0003" at acpi0 not configured
"PNP0400" at acpi0 not configured
"PNP0C33" at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1f0d
rev 0x02
ppb0 at pci0 dev 1 function 0 "Intel Atom C2000 PCIE" rev 0x02: msi
pci1 at ppb0 bus 1
em0 at pci1 dev 0 function 0 "Intel I210" rev 0x03: msi, address
00:90:0b:68:32:a2
ppb1 at pci0 dev 2 function 0 "Intel Atom C2000 PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
em1 at pci2 dev 0 function 0 "Intel I210" rev 0x03: msi, address
00:90:0b:68:32:a3
ppb2 at pci0 dev 3 function 0 "Intel Atom C2000 PCIE" rev 0x02: msi
pci3 at ppb2 bus 3
ppb3 at pci0 dev 4 function 0 "Intel Atom C2000 PCIE" rev 0x02: msi
pci4 at ppb3 bus 4
vendor "Intel", unknown product 0x1f18 (class processor subclass
Co-processor, rev 0x02) at pci0 dev 11 function 0 not configured
pchb1 at pci0 dev 14 function 0 "Intel Atom C2000 RAS" rev 0x02
"Intel Atom C2000 RCEC" rev 0x02 at pci0 dev 15 function 0 not configured
"Intel Atom C2000 SMBus" rev 0x02 at pci0 dev 19 function 0 not configured
em2 at pci0 dev 20 function 0 "Intel I354 SGMII" rev 0x03: msi, address
00:90:0b:68:32:9e
em3 at pci0 dev 20 function 1 "Intel I354 SGMII" rev 0x03: msi, address
00:90:0b:68:32:9f
em4 at pci0 dev 20 function 2 "Intel I354 SGMII" rev 0x03: msi, address
00:90:0b:68:32:a0
em5 at pci0 dev 20 function 3 "Intel I354 SGMII" rev 0x03: msi, address
00:90:0b:68:32:a1
ehci0 at pci0 dev 22 function 0 "Intel Atom C2000 USB" rev 0x02: apic 2
int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
ahci0 at pci0 dev 23 function 0 "Intel Atom C2000 AHCI" rev 0x02: msi,
AHCI 1.3
ahci0: port 3: 3.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 3 lun 0:  SCSI3 

Lanner NCA-5510A

[Daniel Ouellet]

OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017

r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 68589015040 (65411MB)
avail mem = 66503278592 (63422MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xeca30 (50 entries)
bios0: vendor American Megatrends Inc. version "5.11" date 08/16/2016
bios0: Default string Default string
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG UEFI HPET MSCT SLIT SRAT
WDDT SSDT SSDT SSDT PRAD DMAR
acpi0: wakeup devices IP2P(S4) XHCI(S4) EHC1(S4) EHC2(S4) RP01(S4)
RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) BR1A(S4)
BR1B(S4) BR2A(S4) BR2B(S4) [...]
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) Xeon(R) CPU E5-2623 v4 @ 2.60GHz, 2594.40 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2594398760 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, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz, 2593.99 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,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) Xeon(R) CPU E5-2623 v4 @ 2.60GHz, 2593.99 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,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) Xeon(R) CPU E5-2623 v4 @ 2.60GHz, 2593.99 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz, 2593.99 MHz
cpu4:
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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz, 2593.99 MHz
cpu5:
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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 1, package 0
cpu6 at mainbus0: apid 5 (application processor)
cpu6: Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz, 2593.99 MHz
cpu6:

Lanner NCA-5210B

[Daniel Ouellet]

OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017

r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3428722 (32698MB)
avail mem = 33241083904 (31701MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x9fae8000 (82 entries)
bios0: vendor American Megatrends Inc. version "5.12" date 07/14/2017
bios0: Default string Default string
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT SSDT SSDT HPET SSDT
SSDT UEFI SSDT LPIT SSDT SSDT SSDT SSDT DBGP DBG2 DMAR ASF! WSMT
acpi0: wakeup devices PEGP(S0) PEG0(S0) PEGP(S0) PEG1(S0) PEGP(S0)
PEG2(S0) PXSX(S0) RP09(S0) PXSX(S0) RP10(S0) PXSX(S0) RP11(S0) PXSX(S0)
RP12(S0) PXSX(S0) RP13(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) Xeon(R) CPU E3-1280 v6 @ 3.90GHz, 3912.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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 391200 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, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E3-1280 v6 @ 3.90GHz, 3912.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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,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 4 (application processor)
cpu2: Intel(R) Xeon(R) CPU E3-1280 v6 @ 3.90GHz, 3912.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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,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) Xeon(R) CPU E3-1280 v6 @ 3.90GHz, 3912.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,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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Xeon(R) CPU E3-1280 v6 @ 3.90GHz, 3912.00 MHz
cpu4:
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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Xeon(R) CPU E3-1280 v6 @ 3.90GHz, 3912.00 MHz
cpu5:
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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 1, package 0
cpu6 at mainbus0: apid 5 (application processor)
cpu6: Intel(R) Xeon(R) CPU E3-1280 v6 @ 3.90GHz, 3912.00 MHz
cpu6:

Lanner NCA-4010D

[Daniel Ouellet]

Just for the records as I know I was looking to find a dmesg for them
and see if that would run OpenBSD before taking the chance to get them
and it might be of interest to others as well.

Here it goes with 4 more to come all run well so far.

More update later after I test them as routers and see.

That's why I got them in the first place so will see what I can do with
these to replace Cisco gears!

This may help others too.

+++

OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017

r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34239832064 (32653MB)
avail mem = 33195106304 (31657MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xeddc0 (101 entries)
bios0: vendor American Megatrends Inc. version "5.11" date 07/29/2016
bios0: Default string Default string
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG UEFI DBG2 HPET MSCT SLIT
SRAT WDDT SSDT SSDT SSDT PRAD DMAR
acpi0: wakeup devices IP2P(S0) XHCI(S0) EHC1(S0) EHC2(S0) RP01(S0)
RP02(S0) RP03(S0) RP04(S0) RP05(S0) RP06(S0) RP07(S0) RP08(S0) BR1A(S0)
BR1B(S0) BR2A(S0) BR2B(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) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.61 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 1995611240 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, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.38 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,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) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.38 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,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) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.38 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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 8 (application processor)
cpu4: Intel(R) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.38 MHz
cpu4:
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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 0, core 4, package 0
cpu5 at mainbus0: apid 10 (application processor)
cpu5: Intel(R) Xeon(R) CPU D-1548 @ 2.00GHz, 1995.38 MHz
cpu5:
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,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache

Re: OpenBSD Puffy Stickers

[Theo de Raadt]

> My goal is not to rip off anyone, but to help the project.

You cannot help the project by begging on a mailing list that
I partake in business.

Get over yourself Jay.

Re: broken EHCI USB on AMD chipset?

[Paul B. Henson]

On Tue, Nov 28, 2017 at 08:03:05PM -0800, Paul B. Henson wrote:

> The EHCI ports seem to work fine under Linux, including the LTE modem
> when attached to them, so this seems to be an issue with openbsd, not
> faulty hardware per se.

I tested FreeBSD on this box as well, it detected the EHCI ports as:

usbus1: EHCI version 1.0
usbus1 on ehci0
usbus1: 480Mbps High Speed USB v2.0
usbus2: EHCI version 1.0
usbus2 on ehci1
usbus2: 480Mbps High Speed USB v2.0
ugen1.1:  at usbus1
ugen2.1:  at usbus2
uhub0:  on usbus1
 on usbus2
ugen1.2:  at usbus1
uhub3: 
on usb
us1
ugen2.2:  at usbus2
uhub4: 
on usb
us2

As far as I can tell the ports work ok under FreeBSD, detecting hot plug
and removal of devices, and the interrupt count from vmstat -i increases
when doing so. FreeBSD doesn't support the Sierra Wireless card I have
but I'm guessing it would work.

So it just seems to be an issue with OpenBSD and this board or USB
chipset or something. I turned on debugging in the ehci and uhub code,
but when I plug something in nothing whatsoever happens, so that wasn't
very useful. Any suggestions on other debugging to enable or any other
approach to figure out what's going on here?

Thanks...

Re: OpenBSD Puffy Stickers

[Jay Williams]

> Why should I do that?  You only thought of yourself.

Why then do you have any products on the OpenBSD store?

> What is in it for me?
> 
> NOTHING.

The whole idea is to generate some extra cash for OpenBSD. 

This little sticker giveaway has netted the OpenBSD Foundation at least
$50, some of which are first-time donors, all for some little pieces of
paper with adhesive on the back. My goal is not to rip off anyone, but 
to help the project.

-- 
Jay Williams

> On Nov 30, 2017, at 10:07 PM, Theo de Raadt  wrote:
> 
>> Currently the OpenBSD store has mugs, t-shirts, posters, and CDs. All of
>> those require more expense than stickers. Stickers are rather inexpensive
>> to produce, can be sold for high markup, and cost very little to ship, not
>> to mention are very popular, especially in the tech industry.
>> 
>> It wouldn't require any new artwork or commissions. If you were to sell
>> Puffy stickers or OpenBSD Logo stickers I'm sure they'd be top-sellers.
>> 
>> Case in point, UnixStickers.com charges $2.69 per sticker and that doesn't
>> include shipping.
> 
> Why should I do that?  You only thought of yourself.
> 
> What is in it for me?
> 
> NOTHING.
> 
> So why should I do this for you?
> 
> If you think I should, and you repeatedly send mails saying so I can
> only conclude one thing:
> 
> You have a self-entitlement issue.

Re: OpenBSD Puffy Stickers

[Theo de Raadt]

> Currently the OpenBSD store has mugs, t-shirts, posters, and CDs. All of
> those require more expense than stickers. Stickers are rather inexpensive
> to produce, can be sold for high markup, and cost very little to ship, not
> to mention are very popular, especially in the tech industry.
> 
> It wouldn't require any new artwork or commissions. If you were to sell
> Puffy stickers or OpenBSD Logo stickers I'm sure they'd be top-sellers.
> 
> Case in point, UnixStickers.com charges $2.69 per sticker and that doesn't
> include shipping.

Why should I do that?  You only thought of yourself.

What is in it for me?

NOTHING.

So why should I do this for you?

If you think I should, and you repeatedly send mails saying so I can
only conclude one thing:

You have a self-entitlement issue.

Re: OpenBSD Puffy Stickers

[Jay Williams]

Currently the OpenBSD store has mugs, t-shirts, posters, and CDs. All of
those require more expense than stickers. Stickers are rather inexpensive
to produce, can be sold for high markup, and cost very little to ship, not
to mention are very popular, especially in the tech industry.

It wouldn't require any new artwork or commissions. If you were to sell
Puffy stickers or OpenBSD Logo stickers I'm sure they'd be top-sellers.

Case in point, UnixStickers.com charges $2.69 per sticker and that doesn't
include shipping.

-- 
Jay Williams

> On Nov 30, 2017, at 6:44 PM, Theo de Raadt  wrote:
> 
>> Jay Williams wrote on Wed, Nov 29, 2017 at 11:34:21AM -0600:
>> 
>>> P.S. Does anyone know why the official OpenBSD store doesn't sell
>>> stickers? I bet they'd be a big seller!
>> 
>> People loved them while they were still sold, but in the end, even
>> though they were accompanied by installable CDs sets also containing
>> the source tree, they no longer generated enough revenue to justify
>> the investment in terms of time and money required to produce them.
> 
> During that time, people would buy stickers from shops that used
> our art without permission.  And didn't give back.
> 
> Now, people are chatting about buying them from stores that don't give
> a cent back.  Basically, they are copyright violations.  Unauthorized.
> Theft.  I paid people to draw them.
> 
> It was a loss-generating venture.
> 
> I learned my lesson.  I won't put any effort into anything like that
> again, because I don't like being stabbed in the back by community
> who will buy from people who steal from me.
> 
> 
> 
> 
> 
> 

Re: PATCH: cwm move window to {top,bottom}{left,right} corners

[Артур Истомин]

On Thu, Nov 30, 2017 at 09:09:40PM +0100, Thuban wrote:
> This feature sounds very useful to me.

This feature was in original calmwm and was very useful for me too.
> 
> * Julien Steinhauser  le [22-11-2017 21:27:34 +0100]:
> > A long time ago sent Dimitris Papastamos a patch to misc which
> > let one send X clients to corners.[0]
> > 
> > I think it is useful so thank you Dimitris!
> > With some minor editing it still builds on current.
> > 
> > I have no use of window-move-{up,down,right,left}{,-big} but X client
> > corner warping is done on a regular basis.
> > 
> > At the time it did not receive the attention it (IMO) deserves.
> > Maybe was it because "feature" was written on the first line? ;)
> > I know featuritis is considered a disease around here and
> > I'm happy it is but here is an updated version anyway.
> > 
> > This version lacks the keybindings from the initial patch,
> > it also lacks for now a change in the man pages.
> > I use it with the following in ~/.cwmrc:
> > 
> > bind-key 4S-Leftwindow-movebottomleft
> > bind-key 4S-Right   window-movebottomright
> > bind-key 4S-XF86Backwindow-movetopleft
> > bind-key 4S-XF86Forward window-movetopright
> > 
> > I know these are not standards keys found on every keyboard,
> > but Thinkpads are not exotic beasts in this land so it might
> > be an helpful start to some of you and every declinaison of h j k l
> > was already in use in the default config.
> > 
> > OK?
> > 
> > [0] https://marc.info/?l=openbsd-misc=140344759017419=2
> > 
> > Index: calmwm.h
> > ===
> > RCS file: /cvs/xenocara/app/cwm/calmwm.h,v
> > retrieving revision 1.341
> > diff -u -p -r1.341 calmwm.h
> > --- calmwm.h14 Jul 2017 17:23:38 -  1.341
> > +++ calmwm.h22 Nov 2017 19:21:47 -
> > @@ -54,6 +54,10 @@
> >  #define CWM_DOWN   0x0002
> >  #define CWM_LEFT   0x0004
> >  #define CWM_RIGHT  0x0008
> > +#define CWM_TOP_LEFT0x0100
> > +#define CWM_BOTTOM_LEFT 0x0200
> > +#define CWM_TOP_RIGHT  0x0400
> > +#define CWM_BOTTOM_RIGHT   0x0800
> >  #define CWM_BIGAMOUNT  0x0010
> >  #define DIRECTIONMASK  (CWM_UP | CWM_DOWN | CWM_LEFT | CWM_RIGHT)
> >  
> > @@ -476,6 +480,7 @@ void 
> > kbfunc_client_toggle_hmaximize(v
> >  voidkbfunc_client_toggle_vmaximize(void *, struct 
> > cargs *);
> >  voidkbfunc_client_htile(void *, struct cargs *);
> >  voidkbfunc_client_vtile(void *, struct cargs *);
> > +voidkbfunc_client_move_edge(void *, struct cargs 
> > *);
> >  voidkbfunc_client_cycle(void *, struct cargs *);
> >  voidkbfunc_client_toggle_group(void *, struct 
> > cargs *);
> >  voidkbfunc_client_movetogroup(void *, struct cargs 
> > *);
> > Index: conf.c
> > ===
> > RCS file: /cvs/xenocara/app/cwm/conf.c,v
> > retrieving revision 1.233
> > diff -u -p -r1.233 conf.c
> > --- conf.c  14 Jul 2017 17:23:38 -  1.233
> > +++ conf.c  22 Nov 2017 19:21:48 -
> > @@ -67,6 +67,14 @@ static const struct {
> > { "window-delete", kbfunc_client_delete, CWM_CONTEXT_CC, 0 },
> > { "window-htile", kbfunc_client_htile, CWM_CONTEXT_CC, 0 },
> > { "window-vtile", kbfunc_client_vtile, CWM_CONTEXT_CC, 0 },
> > +   { "window-movetopleft", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> > +   (CWM_TOP_LEFT) },
> > +   { "window-movebottomleft", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> > +   (CWM_BOTTOM_LEFT) },
> > +   { "window-movetopright", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> > +   (CWM_TOP_RIGHT) },
> > +   { "window-movebottomright", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> > +   (CWM_BOTTOM_RIGHT) },
> > { "window-stick", kbfunc_client_toggle_sticky, CWM_CONTEXT_CC, 0 },
> > { "window-fullscreen", kbfunc_client_toggle_fullscreen, CWM_CONTEXT_CC, 
> > 0 },
> > { "window-maximize", kbfunc_client_toggle_maximize, CWM_CONTEXT_CC, 0 },
> > @@ -666,6 +674,51 @@ conf_grab_mouse(Window win)
> > BUTTONMASK, GrabModeAsync, GrabModeSync,
> > None, None);
> > }
> > +   }
> > +}
> > +
> > +void
> > +kbfunc_client_move_edge(void *ctx, struct cargs *cargs)
> > +{
> > +   struct client_ctx   *cc = ctx;
> > +   struct screen_ctx   *sc = cc->sc;
> > +   struct geom xine;
> > +   int  flags;
> > +
> > +   /*
> > +* pick screen that the middle of the window is on.
> > +* that's probably more fair than if just the origin of
> > +* a window is poking over a boundary
> > +*/
> > +   xine = screen_area(sc,
> > +   cc->geom.x + cc->geom.w / 2,
> > +   cc->geom.y + cc->geom.h 

KVM / Proxmox Hosted OpenBSD Boxes Multiqueue Virtio Query

[Tom Smyth]

Hello All
I havent seen much by way of advice about multiqueue virtio
support on OpenBSD and I was wondering do other users use it ?
does anyone have experience with setting the number of virtio
queues in Proxmox for an OpenBSD guest ?
It is suggested by
proxmox  / KVM to set the number of Queues presented to a vm
to be = the number of vCPUs you have assigned to the Guest.

Any tips advice would be appreciated

Cheers

Re: pcengines apu boards

[Paul B. Henson]

> From: Eike Lantzsch
> Sent: Thursday, November 30, 2017 3:12 PM
> 
> here: APU2C4 with one SATA drive of 6TB and one 4TB via USB3 and an

Hmm, I didn't think the apu2 had USB3, but double checking the specs I see
it does. My friend that said he had an APU2 must actually have an original
APU, as his board doesn't have USB3. Yeah, the external xHCI USB3 ports work
fine on my APU3, it's the EHCI ones that are screwed up, they are only
available via two internal headers or if you use the Mini PCI slot. There
probably aren't very many people that are routing the internal USB headers
to external connectors, so unless somebody is using a USB Mini PCI expansion
card on an APU2/3, they probably aren't using the EHCI controller.

Thanks for the info.

Re: pcengines apu boards

[Paul B. Henson]

> From: Bryan Everly
> Sent: Thursday, November 30, 2017 2:46 PM
> 
> I'm running my primary firewall at home on an apu2...

Cool. Have you ever tried using an internal Mini PCI card in it?

Re: pcengines apu boards

[Paul B. Henson]

> From: Base Pr1me
> Sent: Thursday, November 30, 2017 2:08 PM
> 
> I run 5 apu2 devices with no problems. I don't have any apu3 devices ... yet.

Thanks for the feedback. Do you by any chance have any USB type Mini PCI cards 
installed internally? I initially noticed the issue with a mini PCI LTE modem 
card. Then I realized it was a more generic USB problem; I believe the apu2 has 
USB1 and USB2 ports, the apu3 has two USB3 ports externally, and then the mini 
PCI and a couple of internal headers are USB2. The USB3 ports, using the xHCI 
driver, work fine, I suppose in the worst case I could use an external Mini PCI 
to USB adapter and plug the card in outside of the case, but that just seems so 
kludgy .

I actually found a friend locally who had a apu2 board, he couldn't get the LTE 
card to work on the internal mini PCI slot, which also appeared to be EHCI 
based, and it would sometimes work and sometimes not plugged into the external 
USB ports. It was really weird, when plugged into the same external port, 
sometimes the device would show up on the EHCI bus (and not work) and sometimes 
it would show up on the OHCI bus (and work). He didn't seem to have any trouble 
with USB flash drives on the EHCI bus on his apu2 though.

Re: OpenBSD Puffy Stickers

[Theo de Raadt]

>Jay Williams wrote on Wed, Nov 29, 2017 at 11:34:21AM -0600:
>
>> P.S. Does anyone know why the official OpenBSD store doesn't sell
>> stickers? I bet they'd be a big seller!
>
>People loved them while they were still sold, but in the end, even
>though they were accompanied by installable CDs sets also containing
>the source tree, they no longer generated enough revenue to justify
>the investment in terms of time and money required to produce them.

During that time, people would buy stickers from shops that used
our art without permission.  And didn't give back.

Now, people are chatting about buying them from stores that don't give
a cent back.  Basically, they are copyright violations.  Unauthorized.
Theft.  I paid people to draw them.

It was a loss-generating venture.

I learned my lesson.  I won't put any effort into anything like that
again, because I don't like being stabbed in the back by community
who will buy from people who steal from me.

Re: sensorsd and acpiac0.indicator0?

[Job Snijders]

Dear Ingo,

On Tue, Nov 28, 2017 at 08:28:02PM +0100, Ingo Schwarze wrote:
> Job Snijders wrote on Mon, Nov 27, 2017 at 03:12:10PM +:
> > I'm tweaking how my laptop behaves depending on whether it is
> > pluggde into AC or not. Any hints or alternative suggestions are
> > welcome. This is my config: /etc/sensorsd.conf:
> > 
> > acpiac0.indicator0:command=/etc/sensorsd/ac_power %2
> 
> I am using:
> 
>   hw.sensors.acpiac0.indicator0:low=1:command=/etc/sensorsd/acpiac %2 %3 %4
> 
> The "%3 %4" is just useful for debugging, you don't need it.
> But are you sure you can omit "hw.sensors."?
> The sensorsd.conf(5) manual only says:
> 
>   Sensors may be specified by their full hw.sensors sysctl(8)
>   variable name or by type, with the full name taking precedence.
> 
> The string "acpiac0.indicator0" seems to be neither.

I tried both fully qualified and shortened, and based on your email also
with "low=1". Still the event doesn't fire reliably.

> > echo $1 >> /root/test
> 
> Using logger(1) might feel more professional ;-) For example, i'm
> using:
> 
>   logger -p daemon.info -t acpiac status=$1 low=$2 high=$3

Thank you, that is indeed a better approach :)

Kind regards,

Job

sftp-server

[Edgar Pettijohn]

I was looking into how best to secure a sftp-server.  The manual
mentions a -Q option to query protocol features supported.  I added the
following line to sshd_config.

Subsystem   sftp/usr/libexec/sftp-server sftp -Q requests

So far I'm not sure how to get at the information provided by this
command line option.  Or am I doing it wrong?

Any insight is greatly appreciated.

Edgar

Re: pcengines apu boards

[Emille Blanc]

On 30.11.2017 14:08, Base Pr1me wrote:
I run 5 apu2 devices with no problems. I don't have any apu3 devices 
... yet.


On 11/30/17 3:00 PM, Paul B. Henson wrote:
I was wondering if anybody is successfully running openbsd on 
pcengines apu
boards? I have one of their APU3 series, specifically a apu3b4 with 
OpenBSD
6.2 on it but I can't get the USB2 EHCI ports functioning correctly 
(for one
thing, they don't detect a hot plugged device), I'm not sure if it's 
an
issue with the ehci driver and the amd ehci chipset or possibly 
something in
the bios acpi tables. But just as a data point, it would be 
interesting to
know if the problem is specific to my board or endemic to the 
design, so if
anyone has an APU series board with fully functional USB2 ports on 
the ehci

controller, I would much appreciate hearing which board it is, which
specific AMD chipset is driving the controller, and what bios 
version you

are running (and what OpenBSD version too).

Thanks much.



No problems here running on APU and APU2 boards, or their USB ports for 
peripherals and Flash drives - The latter usually a Kingston 
datatraveler.

I too have not yet seen or tried an APU3.

Re: OpenBSD Puffy Stickers

[Mikko Laine]

"x9p"  wrote:

> +1 for stickers. I would buy them.

As would I. Sports bottles cannot sell better than strickers, can they?

-- 
  Mikko Laine
  http://mlaine.sdfeu.org/

Re: pcengines apu boards

[Eike Lantzsch]

On Thursday, November 30, 2017 5:45:32 PM -03 Bryan Everly wrote:
> I'm running my primary firewall at home on an apu2...
> 
> On Thu, 2017-11-30 at 15:08 -0700, Base Pr1me wrote:
> > I run 5 apu2 devices with no problems. I don't have any apu3 devices
> > ... yet.
> > 
> > On 11/30/17 3:00 PM, Paul B. Henson wrote:
> > > I was wondering if anybody is successfully running openbsd on
> > > pcengines apu
> > > boards? I have one of their APU3 series, specifically a apu3b4 with
> > > OpenBSD
> > > 6.2 on it but I can't get the USB2 EHCI ports functioning correctly
> > > (for one
> > > thing, they don't detect a hot plugged device), I'm not sure if
> > > it's an
> > > issue with the ehci driver and the amd ehci chipset or possibly
> > > something in
> > > the bios acpi tables. But just as a data point, it would be
> > > interesting to
> > > know if the problem is specific to my board or endemic to the
> > > design, so if
> > > anyone has an APU series board with fully functional USB2 ports on
> > > the ehci
> > > controller, I would much appreciate hearing which board it is,
> > > which
> > > specific AMD chipset is driving the controller, and what bios
> > > version you
> > > are running (and what OpenBSD version too).
> > > 
> > > Thanks much.
can't say anything about APU3 but ...

here: APU2C4 with one SATA drive of 6TB and one 4TB via USB3 and an adaptor to 
SATA as a home file server. OBSD 6.2 release.
No problems so far

OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017
r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
GENERIC.MP
real mem = 4261072896 (4063MB)
avail mem = 4124913664 (3933MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdffb7020 (7 entries)
bios0: vendor coreboot version "88a4f96" date 03/07/2016
bios0: PC Engines apu2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S2 S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HEST SSDT SSDT HPET
acpi0: wakeup devices PWRB(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PBR8(S4) 
UOH1(S3) UOH3(S3) UOH5(S3) XHC0(S4)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD GX-412TC SOC, 998.27 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,
3DNOWP,OSVW,IBS,SKINIT,TOPEXT,ITSC,BMI1
cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 
16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu0: TSC frequency 998269680 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD GX-412TC SOC, 998.12 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,
3DNOWP,OSVW,IBS,SKINIT,TOPEXT,ITSC,BMI1
cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 
16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD GX-412TC SOC, 998.12 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,
3DNOWP,OSVW,IBS,SKINIT,TOPEXT,ITSC,BMI1
cpu2: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 
16-way L2 cache
cpu2: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu2: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: AMD GX-412TC SOC, 998.12 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,
3DNOWP,OSVW,IBS,SKINIT,TOPEXT,ITSC,BMI1
cpu3: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 
16-way L2 cache
cpu3: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu3: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu3: smt 0, core 3, package 0

Re: pcengines apu boards

[Bryan Everly]

I'm running my primary firewall at home on an apu2...

On Thu, 2017-11-30 at 15:08 -0700, Base Pr1me wrote:
> I run 5 apu2 devices with no problems. I don't have any apu3 devices
> ... yet.
> 
> On 11/30/17 3:00 PM, Paul B. Henson wrote:
> > I was wondering if anybody is successfully running openbsd on
> > pcengines apu
> > boards? I have one of their APU3 series, specifically a apu3b4 with
> > OpenBSD
> > 6.2 on it but I can't get the USB2 EHCI ports functioning correctly
> > (for one
> > thing, they don't detect a hot plugged device), I'm not sure if
> > it's an
> > issue with the ehci driver and the amd ehci chipset or possibly
> > something in
> > the bios acpi tables. But just as a data point, it would be
> > interesting to
> > know if the problem is specific to my board or endemic to the
> > design, so if
> > anyone has an APU series board with fully functional USB2 ports on
> > the ehci
> > controller, I would much appreciate hearing which board it is,
> > which
> > specific AMD chipset is driving the controller, and what bios
> > version you
> > are running (and what OpenBSD version too).
> > 
> > Thanks much.
> > 
> 
> 

Re: pcengines apu boards

[Base Pr1me]

I run 5 apu2 devices with no problems. I don't have any apu3 devices ... yet.

On 11/30/17 3:00 PM, Paul B. Henson wrote:

I was wondering if anybody is successfully running openbsd on pcengines apu
boards? I have one of their APU3 series, specifically a apu3b4 with OpenBSD
6.2 on it but I can't get the USB2 EHCI ports functioning correctly (for one
thing, they don't detect a hot plugged device), I'm not sure if it's an
issue with the ehci driver and the amd ehci chipset or possibly something in
the bios acpi tables. But just as a data point, it would be interesting to
know if the problem is specific to my board or endemic to the design, so if
anyone has an APU series board with fully functional USB2 ports on the ehci
controller, I would much appreciate hearing which board it is, which
specific AMD chipset is driving the controller, and what bios version you
are running (and what OpenBSD version too).

Thanks much.

Re: OpenBSD Puffy Stickers

[x9p]

+1 for stickers. I would buy them.

cheers.

x9p

> I like putting stickers on my laptop, but alas after searching high and
> low over the internet I wasn't able to find any good OpenBSD stickers
> So, I got a few printed up myself at StickerMule so now all of my laptops
> and even my car can show support for OpenBSD.
>
> That being said, I have 7 extra Puffy stickers available if anyone else
> would like to have one. They're 3" wide, and have a matte UV coating on
> the outside, so they'll work indoors or outdoors.
>
> If you'd like one, you can send me your address, and I'll drop one in
> the mail for you. Even better, you can make a donation to the OpenBSD
> Foundation as "payment." It's my small way of saying thank you to the
> amazing OpenBSD community.
>
> --
> Jay Williams
>
> P.S. Does anyone know why the official OpenBSD store doesn't sell
> stickers? I bet they'd be a big seller!
>
>

pcengines apu boards

[Paul B. Henson]

I was wondering if anybody is successfully running openbsd on pcengines apu
boards? I have one of their APU3 series, specifically a apu3b4 with OpenBSD
6.2 on it but I can't get the USB2 EHCI ports functioning correctly (for one
thing, they don't detect a hot plugged device), I'm not sure if it's an
issue with the ehci driver and the amd ehci chipset or possibly something in
the bios acpi tables. But just as a data point, it would be interesting to
know if the problem is specific to my board or endemic to the design, so if
anyone has an APU series board with fully functional USB2 ports on the ehci
controller, I would much appreciate hearing which board it is, which
specific AMD chipset is driving the controller, and what bios version you
are running (and what OpenBSD version too).

Thanks much.

Re: PATCH: cwm move window to {top,bottom}{left,right} corners

[Okan Demirmen]

On Thu 2017.11.30 at 13:41 -0500, Okan Demirmen wrote:
> Hi,
> 
> On Wed, Nov 22, 2017 at 3:27 PM, Julien Steinhauser  wrote:
> 
> > A long time ago sent Dimitris Papastamos a patch to misc which
> > let one send X clients to corners.[0]
> >
> > I think it is useful so thank you Dimitris!
> > With some minor editing it still builds on current.
> >
> > I have no use of window-move-{up,down,right,left}{,-big} but X client
> > corner warping is done on a regular basis.
> >
> > At the time it did not receive the attention it (IMO) deserves.
> > Maybe was it because "feature" was written on the first line? ;)
> > I know featuritis is considered a disease around here and
> > I'm happy it is but here is an updated version anyway.
> > ??
> >
> >
> ???I'm not opposed to this completely...I would in fact consider implementing
> this on-top of the snapping we already have allow snap'ing to an edge,
> regardless if one wants to snap to one or two edges.
> ???

A rough cut (no manpage bits yet) would be something like the below; it
allows one to "snap" to any edge or corner.

Incidentally, I dislike we used up/down/left/right from the beginning,
not sure of the trouble changing to all to cardinal directions or not...

Index: calmwm.h
===
RCS file: /home/open/cvs/xenocara/app/cwm/calmwm.h,v
retrieving revision 1.341
diff -u -p -r1.341 calmwm.h
--- calmwm.h14 Jul 2017 17:23:38 -  1.341
+++ calmwm.h30 Nov 2017 20:58:32 -
@@ -461,6 +461,7 @@ void 
screen_assert_clients_within(str
 
 voidkbfunc_cwm_status(void *, struct cargs *);
 voidkbfunc_ptrmove(void *, struct cargs *);
+voidkbfunc_client_snap(void *, struct cargs *);
 voidkbfunc_client_move(void *, struct cargs *);
 voidkbfunc_client_resize(void *, struct cargs *);
 voidkbfunc_client_delete(void *, struct cargs *);
Index: conf.c
===
RCS file: /home/open/cvs/xenocara/app/cwm/conf.c,v
retrieving revision 1.233
diff -u -p -r1.233 conf.c
--- conf.c  14 Jul 2017 17:23:38 -  1.233
+++ conf.c  30 Nov 2017 20:58:17 -
@@ -92,6 +92,24 @@ static const struct {
{ "window-movetogroup-8", kbfunc_client_movetogroup, CWM_CONTEXT_CC, 8 
},
{ "window-movetogroup-9", kbfunc_client_movetogroup, CWM_CONTEXT_CC, 9 
},
 
+   { "window-snap-up", kbfunc_client_snap, CWM_CONTEXT_CC,
+   (CWM_UP) },
+   { "window-snap-down", kbfunc_client_snap, CWM_CONTEXT_CC,
+   (CWM_DOWN) },
+   { "window-snap-left", kbfunc_client_snap, CWM_CONTEXT_CC,
+   (CWM_LEFT) },
+   { "window-snap-right", kbfunc_client_snap, CWM_CONTEXT_CC,
+   (CWM_RIGHT) },
+
+   { "window-snap-up-right", kbfunc_client_snap, CWM_CONTEXT_CC,
+   (CWM_UP|CWM_RIGHT) },
+   { "window-snap-up-left", kbfunc_client_snap, CWM_CONTEXT_CC,
+   (CWM_UP|CWM_LEFT) },
+   { "window-snap-down-right", kbfunc_client_snap, CWM_CONTEXT_CC,
+   (CWM_DOWN|CWM_RIGHT) },
+   { "window-snap-down-left", kbfunc_client_snap, CWM_CONTEXT_CC,
+   (CWM_DOWN|CWM_LEFT) },
+
{ "window-move", kbfunc_client_move, CWM_CONTEXT_CC, 0 },
{ "window-move-up", kbfunc_client_move, CWM_CONTEXT_CC,
(CWM_UP) },
Index: kbfunc.c
===
RCS file: /home/open/cvs/xenocara/app/cwm/kbfunc.c,v
retrieving revision 1.149
diff -u -p -r1.149 kbfunc.c
--- kbfunc.c14 Jul 2017 18:01:46 -  1.149
+++ kbfunc.c30 Nov 2017 21:01:12 -
@@ -287,6 +287,42 @@ kbfunc_client_resize_mb(void *ctx, struc
 }
 
 void
+kbfunc_client_snap(void *ctx, struct cargs *cargs)
+{
+   struct client_ctx   *cc = ctx;
+   struct screen_ctx   *sc = cc->sc;
+   struct geom  area;
+   int  flags;
+
+   area = screen_area(sc,
+   cc->geom.x + cc->geom.w / 2,
+   cc->geom.y + cc->geom.h / 2, CWM_GAP);
+
+   flags = cargs->flag;
+   while (flags) {
+   if (flags & CWM_UP) {
+   cc->geom.y = area.y;
+   flags &= ~CWM_UP;
+   }
+   if (flags & CWM_LEFT) {
+   cc->geom.x = area.x;
+   flags &= ~CWM_LEFT;
+   }
+   if (flags & CWM_RIGHT) {
+   cc->geom.x = area.x + area.w - cc->geom.w -
+   (cc->bwidth * 2);
+   flags &= ~CWM_RIGHT;
+   }
+   if (flags & CWM_DOWN) {
+   cc->geom.y = area.y + area.h - cc->geom.h -
+   (cc->bwidth * 2);
+   flags &= ~CWM_DOWN;
+   }
+   }
+   client_move(cc);
+}
+
+void
 

Re: PATCH: cwm move window to {top,bottom}{left,right} corners

[Thuban]

This feature sounds very useful to me.

* Julien Steinhauser  le [22-11-2017 21:27:34 +0100]:
> A long time ago sent Dimitris Papastamos a patch to misc which
> let one send X clients to corners.[0]
> 
> I think it is useful so thank you Dimitris!
> With some minor editing it still builds on current.
> 
> I have no use of window-move-{up,down,right,left}{,-big} but X client
> corner warping is done on a regular basis.
> 
> At the time it did not receive the attention it (IMO) deserves.
> Maybe was it because "feature" was written on the first line? ;)
> I know featuritis is considered a disease around here and
> I'm happy it is but here is an updated version anyway.
> 
> This version lacks the keybindings from the initial patch,
> it also lacks for now a change in the man pages.
> I use it with the following in ~/.cwmrc:
> 
> bind-key 4S-Left  window-movebottomleft
> bind-key 4S-Right window-movebottomright
> bind-key 4S-XF86Back  window-movetopleft
> bind-key 4S-XF86Forward   window-movetopright
> 
> I know these are not standards keys found on every keyboard,
> but Thinkpads are not exotic beasts in this land so it might
> be an helpful start to some of you and every declinaison of h j k l
> was already in use in the default config.
> 
> OK?
> 
> [0] https://marc.info/?l=openbsd-misc=140344759017419=2
> 
> Index: calmwm.h
> ===
> RCS file: /cvs/xenocara/app/cwm/calmwm.h,v
> retrieving revision 1.341
> diff -u -p -r1.341 calmwm.h
> --- calmwm.h  14 Jul 2017 17:23:38 -  1.341
> +++ calmwm.h  22 Nov 2017 19:21:47 -
> @@ -54,6 +54,10 @@
>  #define CWM_DOWN 0x0002
>  #define CWM_LEFT 0x0004
>  #define CWM_RIGHT0x0008
> +#define CWM_TOP_LEFT0x0100
> +#define CWM_BOTTOM_LEFT 0x0200
> +#define CWM_TOP_RIGHT0x0400
> +#define CWM_BOTTOM_RIGHT 0x0800
>  #define CWM_BIGAMOUNT0x0010
>  #define DIRECTIONMASK(CWM_UP | CWM_DOWN | CWM_LEFT | CWM_RIGHT)
>  
> @@ -476,6 +480,7 @@ void   
> kbfunc_client_toggle_hmaximize(v
>  void  kbfunc_client_toggle_vmaximize(void *, struct cargs *);
>  void  kbfunc_client_htile(void *, struct cargs *);
>  void  kbfunc_client_vtile(void *, struct cargs *);
> +void  kbfunc_client_move_edge(void *, struct cargs *);
>  void  kbfunc_client_cycle(void *, struct cargs *);
>  void  kbfunc_client_toggle_group(void *, struct cargs *);
>  void  kbfunc_client_movetogroup(void *, struct cargs *);
> Index: conf.c
> ===
> RCS file: /cvs/xenocara/app/cwm/conf.c,v
> retrieving revision 1.233
> diff -u -p -r1.233 conf.c
> --- conf.c14 Jul 2017 17:23:38 -  1.233
> +++ conf.c22 Nov 2017 19:21:48 -
> @@ -67,6 +67,14 @@ static const struct {
>   { "window-delete", kbfunc_client_delete, CWM_CONTEXT_CC, 0 },
>   { "window-htile", kbfunc_client_htile, CWM_CONTEXT_CC, 0 },
>   { "window-vtile", kbfunc_client_vtile, CWM_CONTEXT_CC, 0 },
> + { "window-movetopleft", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> + (CWM_TOP_LEFT) },
> + { "window-movebottomleft", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> + (CWM_BOTTOM_LEFT) },
> + { "window-movetopright", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> + (CWM_TOP_RIGHT) },
> + { "window-movebottomright", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> + (CWM_BOTTOM_RIGHT) },
>   { "window-stick", kbfunc_client_toggle_sticky, CWM_CONTEXT_CC, 0 },
>   { "window-fullscreen", kbfunc_client_toggle_fullscreen, CWM_CONTEXT_CC, 
> 0 },
>   { "window-maximize", kbfunc_client_toggle_maximize, CWM_CONTEXT_CC, 0 },
> @@ -666,6 +674,51 @@ conf_grab_mouse(Window win)
>   BUTTONMASK, GrabModeAsync, GrabModeSync,
>   None, None);
>   }
> + }
> +}
> +
> +void
> +kbfunc_client_move_edge(void *ctx, struct cargs *cargs)
> +{
> + struct client_ctx   *cc = ctx;
> + struct screen_ctx   *sc = cc->sc;
> + struct geom xine;
> + int  flags;
> +
> + /*
> +  * pick screen that the middle of the window is on.
> +  * that's probably more fair than if just the origin of
> +  * a window is poking over a boundary
> +  */
> + xine = screen_area(sc,
> + cc->geom.x + cc->geom.w / 2,
> + cc->geom.y + cc->geom.h / 2, CWM_GAP);
> +
> + flags = cargs->flag;
> +
> + switch (flags) {
> + case CWM_TOP_LEFT:
> +  cc->geom.x = xine.x;
> +  cc->geom.y = xine.y;
> +  client_move(cc);
> +  break;
> + case CWM_BOTTOM_LEFT:
> +  cc->geom.x = xine.x;
> +  

Re: OpenBSD Puffy Stickers

[Jay Williams]

StickerMule was fantastic. I can't remember the last time I've been more
impressed by an ordering process and professional service. The stickers look
fantastic too, so no complaints from me.

By the way, there are two stickers lefts up for grabs.

-- 
Jay Williams

> On Nov 30, 2017, at 2:48 PM, flipchan  wrote:
> 
> Was stickermule good ? Good quality ?
> 
> On November 29, 2017 6:34:21 PM GMT+01:00, Jay Williams  wrote:
>> I like putting stickers on my laptop, but alas after searching high and
>> low over the internet I wasn't able to find any good OpenBSD stickers
>> So, I got a few printed up myself at StickerMule so now all of my
>> laptops
>> and even my car can show support for OpenBSD.
>> 
>> That being said, I have 7 extra Puffy stickers available if anyone else
>> would like to have one. They're 3" wide, and have a matte UV coating on
>> the outside, so they'll work indoors or outdoors.
>> 
>> If you'd like one, you can send me your address, and I'll drop one in
>> the mail for you. Even better, you can make a donation to the OpenBSD
>> Foundation as "payment." It's my small way of saying thank you to the 
>> amazing OpenBSD community.
>> 
>> -- 
>> Jay Williams
>> 
>> P.S. Does anyone know why the official OpenBSD store doesn't sell
>> stickers? I bet they'd be a big seller!
> 
> -- 
> Take Care Sincerely flipchan layerprox dev

Re: OpenBSD Puffy Stickers

[flipchan]

Was stickermule good ? Good quality ?

On November 29, 2017 6:34:21 PM GMT+01:00, Jay Williams  wrote:
>I like putting stickers on my laptop, but alas after searching high and
>low over the internet I wasn't able to find any good OpenBSD stickers
>So, I got a few printed up myself at StickerMule so now all of my
>laptops
>and even my car can show support for OpenBSD.
>
>That being said, I have 7 extra Puffy stickers available if anyone else
>would like to have one. They're 3" wide, and have a matte UV coating on
>the outside, so they'll work indoors or outdoors.
>
>If you'd like one, you can send me your address, and I'll drop one in
>the mail for you. Even better, you can make a donation to the OpenBSD
>Foundation as "payment." It's my small way of saying thank you to the 
>amazing OpenBSD community.
>
>-- 
>Jay Williams
>
>P.S. Does anyone know why the official OpenBSD store doesn't sell
>stickers? I bet they'd be a big seller!

-- 
Take Care Sincerely flipchan layerprox dev

Re: OpenBSD Puffy Stickers

[webmaster]

>  Original Message 
> Subject: Re: OpenBSD Puffy Stickers
> From: Rupert Gallagher 
> Date: Thu, November 30, 2017 1:30 pm
> To: Ingo Schwarze , Jay Williams 
> Cc: misc@openbsd.org
> 
> 
> Don't give up on marketing.
> 

Really?
I can count on one hand the number of people since I started using it
that
would let me boot OpenBSD off of a USB stick.

OpenBSD users and developers wander in on their own accord.
There is just something to fall in love with seeing things like code
audit,
security, cryptography that the US wants to stop.
The website is all the marketing that's needed.

Feeling secure,
Chris Bennett

Re: obligatory leaving letter

[Charlie Eddy]

Can someone advise what occurred in NetBSD re this user?

Re: [cwm] list all available items

[Charlie Eddy]

Just a note that cwm is an old welsh word for a mountain pass, one of the
few OED words with no vowel

Re: OpenBSD Puffy Stickers

[Rupert Gallagher]

Don't give up on marketing.

Sent from ProtonMail Mobile

On Thu, Nov 30, 2017 at 15:02, Ingo Schwarze  wrote:

> Hi, Jay Williams wrote on Wed, Nov 29, 2017 at 11:34:21AM -0600: > P.S. Does 
> anyone know why the official OpenBSD store doesn't sell > stickers? I bet 
> they'd be a big seller! People loved them while they were still sold, but in 
> the end, even though they were accompanied by installable CDs sets also 
> containing the source tree, they no longer generated enough revenue to 
> justify the investment in terms of time and money required to produce them. 
> Yours, Ingo

Re: PATCH: cwm move window to {top,bottom}{left,right} corners

[Okan Demirmen]

Hi,

On Wed, Nov 22, 2017 at 3:27 PM, Julien Steinhauser  wrote:

> A long time ago sent Dimitris Papastamos a patch to misc which
> let one send X clients to corners.[0]
>
> I think it is useful so thank you Dimitris!
> With some minor editing it still builds on current.
>
> I have no use of window-move-{up,down,right,left}{,-big} but X client
> corner warping is done on a regular basis.
>
> At the time it did not receive the attention it (IMO) deserves.
> Maybe was it because "feature" was written on the first line? ;)
> I know featuritis is considered a disease around here and
> I'm happy it is but here is an updated version anyway.
> ​​
>
>
​I'm not opposed to this completely...I would in fact consider implementing
this on-top of the snapping we already have allow snap'ing to an edge,
regardless if one wants to snap to one or two edges.
​

> This version lacks the keybindings from the initial patch,
> it also lacks for now a change in the man pages.
> I use it with the following in ~/.cwmrc:
>
> bind-key 4S-Leftwindow-movebottomleft
> bind-key 4S-Right   window-movebottomright
> bind-key 4S-XF86Backwindow-movetopleft
> bind-key 4S-XF86Forward window-movetopright
>
> I know these are not standards keys found on every keyboard,
> but Thinkpads are not exotic beasts in this land so it might
> be an helpful start to some of you and every declinaison of h j k l
> was already in use in the default config.
>
> OK?
>
> [0] https://marc.info/?l=openbsd-misc=140344759017419=2
>
> Index: calmwm.h
> ===
> RCS file: /cvs/xenocara/app/cwm/calmwm.h,v
> retrieving revision 1.341
> diff -u -p -r1.341 calmwm.h
> --- calmwm.h14 Jul 2017 17:23:38 -  1.341
> +++ calmwm.h22 Nov 2017 19:21:47 -
> @@ -54,6 +54,10 @@
>  #define CWM_DOWN   0x0002
>  #define CWM_LEFT   0x0004
>  #define CWM_RIGHT  0x0008
> +#define CWM_TOP_LEFT0x0100
> +#define CWM_BOTTOM_LEFT 0x0200
> +#define CWM_TOP_RIGHT  0x0400
> +#define CWM_BOTTOM_RIGHT   0x0800
>  #define CWM_BIGAMOUNT  0x0010
>  #define DIRECTIONMASK  (CWM_UP | CWM_DOWN | CWM_LEFT | CWM_RIGHT)
>
> @@ -476,6 +480,7 @@ void kbfunc_client_toggle_
> hmaximize(v
>  voidkbfunc_client_toggle_vmaximize(void *, struct
> cargs *);
>  voidkbfunc_client_htile(void *, struct cargs *);
>  voidkbfunc_client_vtile(void *, struct cargs *);
> +voidkbfunc_client_move_edge(void *, struct cargs *);
>  voidkbfunc_client_cycle(void *, struct cargs *);
>  voidkbfunc_client_toggle_group(void *, struct cargs
> *);
>  voidkbfunc_client_movetogroup(void *, struct cargs *);
> Index: conf.c
> ===
> RCS file: /cvs/xenocara/app/cwm/conf.c,v
> retrieving revision 1.233
> diff -u -p -r1.233 conf.c
> --- conf.c  14 Jul 2017 17:23:38 -  1.233
> +++ conf.c  22 Nov 2017 19:21:48 -
> @@ -67,6 +67,14 @@ static const struct {
> { "window-delete", kbfunc_client_delete, CWM_CONTEXT_CC, 0 },
> { "window-htile", kbfunc_client_htile, CWM_CONTEXT_CC, 0 },
> { "window-vtile", kbfunc_client_vtile, CWM_CONTEXT_CC, 0 },
> +   { "window-movetopleft", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> +   (CWM_TOP_LEFT) },
> +   { "window-movebottomleft", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> +   (CWM_BOTTOM_LEFT) },
> +   { "window-movetopright", kbfunc_client_move_edge, CWM_CONTEXT_CC,
> +   (CWM_TOP_RIGHT) },
> +   { "window-movebottomright", kbfunc_client_move_edge,
> CWM_CONTEXT_CC,
> +   (CWM_BOTTOM_RIGHT) },
> { "window-stick", kbfunc_client_toggle_sticky, CWM_CONTEXT_CC, 0 },
> { "window-fullscreen", kbfunc_client_toggle_fullscreen,
> CWM_CONTEXT_CC, 0 },
> { "window-maximize", kbfunc_client_toggle_maximize,
> CWM_CONTEXT_CC, 0 },
> @@ -666,6 +674,51 @@ conf_grab_mouse(Window win)
> BUTTONMASK, GrabModeAsync, GrabModeSync,
> None, None);
> }
> +   }
> +}
> +
> +void
> +kbfunc_client_move_edge(void *ctx, struct cargs *cargs)
> +{
> +   struct client_ctx   *cc = ctx;
> +   struct screen_ctx   *sc = cc->sc;
> +   struct geom xine;
> +   int  flags;
> +
> +   /*
> +* pick screen that the middle of the window is on.
> +* that's probably more fair than if just the origin of
> +* a window is poking over a boundary
> +*/
> +   xine = screen_area(sc,
> +   cc->geom.x + cc->geom.w / 2,
> +   cc->geom.y + cc->geom.h / 2, CWM_GAP);
> +
> +   flags = cargs->flag;
> +
> +   switch (flags) {
> 

Re: [cwm] list all available items

[Okan Demirmen]

On Mon, Nov 6, 2017 at 4:06 PM, Julien Steinhauser  wrote:

> Hello !
>

​Hi​

>
> Using cwm and loving it, Thank you Okan and all devs before you
> who got involved in the development. Just minor things
> I'd change from the defaults. Here is one:
>
> When using a menu, I much more often than not hit ^a to list
> all available items, especially when calling kbfunc_menu_client
> and I'm sure I'm not the only one.
>
> The following patch inverts the default behavior, giving instant feedback
> as soon a menu is launched, with all available items being listed.
>
>
​So taking away the 'list all' option altogether?
​
This would be jarring I believe for the 'exec' and 'wm' menus -there's no
reason to list every item in the path :) As you are aware, the button
invocations of the menus default to listing all items, though 'exec' and
'wm' are not available menus via buttons.

However, there might be a balance to apply across the board - right now the
menu will max out at the current region height, maybe we clamp the menus
down to something much less than that, so a full on "list all" by default
isn't too much. Though perhaps a better way is to list-all only when the
height or number of items is some number, maybe by default or not. There
are a lot of ways and I'd prefer to not have a button for each behaviour.
​

> On the first keystroke, the behavior is back to what it was
> before this patch.
>
> Regards,
> Julien
>
> Index: cwm.1
> ===
> RCS file: /cvs/xenocara/app/cwm/cwm.1,v
> retrieving revision 1.58
> diff -u -p -r1.58 cwm.1
> --- cwm.1   21 Jul 2017 15:55:37 -  1.58
> +++ cwm.1   6 Nov 2017 20:17:14 -
> @@ -179,8 +179,6 @@ Previous item.
>  Backspace.
>  .It Ic C-u
>  Clear input.
> -.It Ic C-a
> -List all available items.
>  .It Ic [Esc]
>  Cancel.
>  .El
> Index: menu.c
> ===
> RCS file: /cvs/xenocara/app/cwm/menu.c,v
> retrieving revision 1.102
> diff -u -p -r1.102 menu.c
> --- menu.c  25 Apr 2017 12:08:05 -  1.102
> +++ menu.c  6 Nov 2017 20:17:14 -
> @@ -40,7 +40,7 @@
>  enum ctltype {
> CTL_NONE = -1,
> CTL_ERASEONE = 0, CTL_WIPE, CTL_UP, CTL_DOWN, CTL_RETURN,
> -   CTL_TAB, CTL_ABORT, CTL_ALL
> +   CTL_TAB, CTL_ABORT
>  };
>
>  struct menu_ctx {
> @@ -115,6 +115,7 @@ menu_filter(struct screen_ctx *sc, struc
> evmask |= KEYMASK; /* accept keys as well */
> (void)strlcpy(mc.promptstr, prompt, sizeof(mc.promptstr));
> mc.hasprompt = 1;
> +   mc.list = !mc.list; /* List all available items */
> }
>
> XSelectInput(X_Dpy, sc->menu.win, evmask);
> @@ -294,9 +295,6 @@ menu_handle_key(XEvent *e, struct menu_c
> mc->changed = 1;
> }
> break;
> -   case CTL_ALL:
> -   mc->list = !mc->list;
> -   break;
> case CTL_ABORT:
> mi = xmalloc(sizeof(*mi));
> mi->text[0] = '\0';
> @@ -565,10 +563,6 @@ menu_keycode(XKeyEvent *ev, enum ctltype
> case XK_h:
> case XK_H:
> *ctl = CTL_ERASEONE;
> -   break;
> -   case XK_a:
> -   case XK_A:
> -   *ctl = CTL_ALL;
> break;
> case XK_bracketleft:
> *ctl = CTL_ABORT;
>
>

Re: xterm(1) changing UTF-8 characters when copy-pasting?

[Ingo Schwarze]

Hi,

Allan Streib wrote on Thu, Nov 30, 2017 at 12:09:13PM -0500:
> Philippe Meunier  writes:
>> Allan Streib wrote:

>>> Are you using xterm(1) or uxterm(1)?

>> uxterm does not exist anymore on OpenBSD 6.1:
>> https://www.openbsd.org/faq/upgrade61.html

> Hm. Well that's one that I overlooked. I've been upgrading since 5.x
> and I never removed uxterm. I'm on 6.2 now and still using it.

It's a trivial but wordy wrapper script.  The only things it does
that i could imagine to be relevant are setting two command line
options: -class UXTerm and -en UTF-8.

The -en option is a deprecated way to hardcode UTF-8 mode for
systems that do not support setlocale(3), so don't use it.
It can't be what helps you here, as UTF-8 works in general.

The -class UXTerm option causes /usr/X11R6/share/X11/app-defaults/UXTerm
to be used instead of /usr/X11R6/share/X11/app-defaults/XTerm.
The UXTerm file was also deleted, as it contains only font stuff
and nobody considered that relevant for anything.

Does the following make things work better for you?
You can apply it directly to /usr/X11R6/share/X11/app-defaults/XTerm
if you want to.  It just copies the UXTerm.ad stuff over and disables
the Precompose resource.  Frankly, i don't have the slightest idea
what the font resources mean, not even after reading the comment
in UXterm.ad, but maybe they are needed for some reason.

Except in a professional typesetting system like groff or LaTeX, i
consider anything that makes the end user worry about fonts
fundamentally broken.  Fonts that work should be installed by default
and not configurable, in my opinion.  Toying around with fonts
causes nothing but grief.

Yours,
  Ingo


Index: XTerm.ad
===
RCS file: /cvs/xenocara/app/xterm/XTerm.ad,v
retrieving revision 1.18
diff -u -p -r1.18 XTerm.ad
--- XTerm.ad15 Jul 2017 19:20:51 -  1.18
+++ XTerm.ad30 Nov 2017 17:52:26 -
@@ -266,6 +266,14 @@
 ! locales.  Even for people using the C/POSIX locale for everything,
 ! that's safer and more usable than the upstream default of "medium".
 *locale: UTF-8
+*precompose: false
+*VT100.utf8: 1
+*VT100.font2: -misc-fixed-medium-r-normal--8-80-75-75-c-50-iso10646-1
+*VT100.font:  -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1
+*VT100.font3: -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1
+*VT100.font4: -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1
+*VT100.font5: -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
+*VT100.font6: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
 
 ! ScrollBar by default
 *scrollBar: true

Re: xterm(1) changing UTF-8 characters when copy-pasting?

[Allan Streib]

Philippe Meunier  writes:

> Allan Streib wrote:
>>Are you using xterm(1) or uxterm(1)?
>
> uxterm does not exist anymore on OpenBSD 6.1:
> https://www.openbsd.org/faq/upgrade61.html

Hm. Well that's one that I overlooked. I've been upgrading since 5.x and
I never removed uxterm. I'm on 6.2 now and still using it.

Allan

Re: xterm(1) changing UTF-8 characters when copy-pasting?

[Philippe Meunier]

Allan Streib wrote:
>Are you using xterm(1) or uxterm(1)?

uxterm does not exist anymore on OpenBSD 6.1:
https://www.openbsd.org/faq/upgrade61.html

Philippe

Re: xterm(1) changing UTF-8 characters when copy-pasting?

[Allan Streib]

Philippe Meunier  writes:

> So there seems to be two problems:
>
> - Copy-pasting the result of printf "e\xcc\x81\n" never works correctly in
>   xterm, regardless of whether I use TrueType fonts or not.  xterm
>   copy-pastes the correct sequence of bytes but that sequence is not
>   displayed correctly.  That's the same problem I noticed in my previous
>   email.
>
> - When using TrueType fonts, printf "e\xcc\x81\n" does not show the accent.

Are you using xterm(1) or uxterm(1)?

When I start uxterm I don't see these behaviors. I see the correct
accented e in all cases.

Allan

Re: OpenBSD Puffy Stickers

[Ingo Schwarze]

Hi,

Jay Williams wrote on Wed, Nov 29, 2017 at 11:34:21AM -0600:

> P.S. Does anyone know why the official OpenBSD store doesn't sell
> stickers? I bet they'd be a big seller!

People loved them while they were still sold, but in the end, even
though they were accompanied by installable CDs sets also containing
the source tree, they no longer generated enough revenue to justify
the investment in terms of time and money required to produce them.

Yours,
  Ingo

Re: xterm(1) changing UTF-8 characters when copy-pasting?

[Philippe Meunier]

Anthony J. Bentley wrote:
>I get the same result, but only when using TrueType fonts (default or no).

If I use TrueType fonts:

$ printf "e\xcc\x81\n"

only shows the letter 'e', and when I try to copy-paste it I get a letter
'e' followed by a question mark inside a circle.  If I then redraw the line
I get an 'e' by itself but od(1) shows that it is still e\xcc\x81.

Using TrueType fonts:

$ printf "\xc3\xa9\n"

works fine and I can copy-paste the accented 'e' without problem.



Without TrueType fonts:

$ printf "e\xcc\x81\n"

works fine but when I try to copy-paste the accented 'e' I get a letter 'e'
followed by a question mark inside a circle.  If I then redraw the line I
get the correct accented 'e' again (which od(1) shows is still e\xcc\x81).

Without TrueType fonts:

$ printf "\xc3\xa9\n"

works fine and I can copy-paste the accented 'e' without problem.



So there seems to be two problems:

- Copy-pasting the result of printf "e\xcc\x81\n" never works correctly in
  xterm, regardless of whether I use TrueType fonts or not.  xterm
  copy-pastes the correct sequence of bytes but that sequence is not
  displayed correctly.  That's the same problem I noticed in my previous
  email.

- When using TrueType fonts, printf "e\xcc\x81\n" does not show the accent.

On a note related to this second problem, I never use TrueType fonts in
xterm anyway because then xterm can't display Thai or Chinese or Korean
characters (at least with the default font; I haven't tried to use any
other font).  So I suspect that this second problem is more a font problem
than an xterm bug.

Here's my current config:

$ xrdb -query
xterm*background:   black
xterm*foreground:   white
xterm*metaSendsEscape:  true
xterm*multiScroll:  true
xterm*precompose:   false
xterm*saveLines:256
xterm*scrollBar:true
xterm*scrollKey:true
xterm*scrollTtyOutput:  false
xterm*utf8Title:true
xterm*utmpInhibit:  true
xterm*visualBell:   true

and:

$ set | egrep -i utf
LC_CTYPE=en_US.UTF-8
XTERM_LOCALE=en_US.UTF-8

Philippe

Re: obligatory leaving letter

[Marc Espie]

On Thu, Nov 30, 2017 at 02:26:44AM +0100, Ingo Schwarze wrote:
> Admittedly, if you look at the list of developers, it is impossible
> to deny that OpenBSD is not the most succcessful project ever with
> respect to inclusiveness.  

I had to do a double-take to grok that one.

EDOUBLENEGATIVEABUSE

You're usually clearer, Ingo :)

Re: obligatory leaving letter

[Marc Espie]

On Tue, Nov 28, 2017 at 05:17:05PM -0600, Jay Williams wrote:
> As a new user to OpenBSD, who is trying to learn as much as I can, seeing a
> message like this is very disheartening. OpenBSD's security focus and passion
> for clean, minimal and secure code is something that the world definitely
> needs.

Don't feel like this, the guy is an ass who managed to piss of both the
NetBSD and the OpenBSD community.

It takes a special kind of talent to do that.

Re: Testing IKEv2 with Android devices

[Stuart Henderson]

On 2017-11-29, C. L. Martinez  wrote:
> On Wed, Nov 29, 2017 at 9:33 AM, Stuart Henderson  
> wrote:
>> On 2017-11-26, C. L. Martinez  wrote:
>>>
>>> Ok, it is seems the prolem is that iked(8) does not know how to perform 
>>> Diffie-Hellman group negotiation:
>>>
>>> https://marc.info/?l=openbsd-tech=151136800328145=2
>>>
>>>  Am I correct? What is the current status for Tim's fix?
>>
>> patrick@ has been following this rabbit hole, try his latest diff.
>>
>
> Thanks Stuart. Are you referring to this one:
> https://marc.info/?l=openbsd-tech=151187345915827=2?

I think you'll need the "don't include DH transform in IKE_AUTH msgs"
one as well. But basically just look for all of his recent tech@ mails
about iked.

Re: xterm(1) changing UTF-8 characters when copy-pasting?

[Anthony J. Bentley]

Philippe Meunier writes:
> The strange part is that, when I copy the first filename and paste
> it to become the second filename, the second filename is shown without
> any accent, even though the first and second filenames are now the exact
> same sequence of bytes (I checked using od(1)).  So on the command line
> it actually looks like this:
>
> $ cp Thérèse Therese
> cp: Thérèse and Thérèse are identical (not copied).
>
> which looks wrong but works as expected.  I tried to play with various
> things like the allowPasteControls resource but to no avail.  It looks
> like an xterm bug to me but at this point I'm not even sure of that...
> Anyone has any clue?

I get the same result, but only when using TrueType fonts (default or no).
If I Ctrl-rightclick and uncheck "TrueType Fonts", the accents show up.
So it looks like xterm's rendering of combining characters is broken, or
unimplemented.