Re: "Invalid argument" when exec'ing and/or ktrace'ing a file?

2019-05-24 Thread Stuart Henderson
There might be something else wrong with the build as well, but you're at
least likely to bump into this:

Webkit needs memory mappings which are both writable and executable.
OpenBSD denies these by default. Your wkhtmltopdf binary will need to be
linked using the -z wxneeded flag, and it will need to be placed on a
filesystem that has been mounted with the wxallowed flag.

It maybe simpler to adapt the perl code to the newer wkhtmltopdf, rather
than to figure out how to build their wkhtmltopdf the right way.


On 2019-05-24, Adam Thompson  wrote:
> I have a binary - built on this 6.5-STABLE amd64 system by an automatic 
> build process as part of a CPAN module installation, that will not 
> execute:
>
>> rt@rt$ /var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf
>> ksh: /var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf: 
>> Invalid argument
>
> or even allow itself to be ktrace'd:
>
>> rt@rt$ ktrace 
>> /var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf
>> ktrace: exec of 
>> '/var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf' 
>> failed: Invalid argument
>
> At least ktrace(8) told me it was an exec(3) problem.  So off I go to 
> exec(3) which leads me to execve(2), wherein I see:
>
>> [EINVAL] argv did not contain at least one element.
>
> errno(2) confirms the english expansion of "Illegal argument"
>
> file(1) gives me a clue, but I don't know what to do with it:
>
>> rt@rt$ file `locate bin/wkhtmltopdf`
>> /usr/local/bin/wkhtmltopdf:   ELF 
>> 64-bit LSB shared object, x86-64, version 1
>> /var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf: ELF 
>> 64-bit LSB executable, x86-64, version 1
>
> where the version in /usr/local/bin is from ports.
>
> the RT::Extension::TicketPDF version is significantly larger, ~4x, which 
> led me to:
>
>> rt@rt$ ldd `locate bin/wkhtmltopdf`
>> /usr/local/bin/wkhtmltopdf:
>> StartEnd  Type  Open Ref GrpRef Name
>> 041737f61000 04173ac77000 exe   20   0  
>> /usr/local/bin/wkhtmltopdf
>> 0419ee50 0419ee599000 rlib  01   0  
>> /usr/local/lib/libjpeg.so.70.0
>> [...elided...]
>> /var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf:
>> not a dynamic executable
>
> So... how do I figure out why a static binary (whose build process is 
> pretty opaque) won't/can't run?
>
> Clueless at this level, my detailed knowledge of how exec worked under 
> OpenBSD ended in the a.out era.
>
> (oh, the reason I don't use the version from ports?  It's too new for 
> the TicketPDF code. *sigh*)
>
> Thanks for any pointers,
> -Adam
>
>



Re: support new

2019-05-24 Thread Ingo Schwarze
Hi,

Rolf wrote on Fri, May 24, 2019 at 04:55:32PM +0200:
> On Sat, Apr 27, 2019 at 12:38:09PM +0200, Rolf wrote:

>> 0
>> C Belgium
>> P Oost-Vlaanderen
>> T Dendermonde
>> Z 9200
>> O MetaData
>> I Rolf
>> A Oliestraat 50
>> M sa...@metadata.be
>> U https://metadata.be/
>> B +32 477 29 76 04
>> X N/A
>> N Network consulting, installation and maintenance. Hosting services.
 
> Can I ask again to take a look at this?

Committed.

Yours,
  Ingo



RE: dmesg: 6.5 i386 GENERIC on 'Thinkpad R40 (type 2722)'

2019-05-24 Thread zeurkous
Haai,

i...@openbsd.org wrote:
>
> Thank you for your dmesg, however, in the future would you mind sending
> these to dm...@openbsd.org instead of the mailing lists? dmesg@ is a
> special mailbox that will automatically add your dmesg to our archives
> in a more helpful way.

Of course, me's sorry, mewas unaware :)

   --zeur.

-- 
Friggin' Machines!



Re: dmesg: 6.5 i386 GENERIC on 'Thinkpad R40 (type 2722)'

2019-05-24 Thread Ian Sutton
On Sat, May 25, 2019 at 12:07:40AM +0200, zeurk...@volny.cz wrote:
> [not subscribed, please Cc, thanks.]
> 
> OpenBSD 6.5 (GENERIC) #1338: Sat Apr 13 15:07:04 MDT 2019
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC

Hi,

Thank you for your dmesg, however, in the future would you mind sending
these to dm...@openbsd.org instead of the mailing lists? dmesg@ is a
special mailbox that will automatically add your dmesg to our archives
in a more helpful way.

Thanks,
ians



dmesg: 6.5 i386 GENERIC on 'Thinkpad R40 (type 2722)'

2019-05-24 Thread zeurkous
[not subscribed, please Cc, thanks.]

OpenBSD 6.5 (GENERIC) #1338: Sat Apr 13 15:07:04 MDT 2019
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem  = 535707648 (510MB)
avail mem = 510660608 (487MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 07/15/03, BIOS32 rev. 0 @ 0xfd7b0, SMBIOS rev. 2.31 @ 
0xe0010 (53 entries)
bios0: vendor IBM version "1PET46WW (1.14 )" date 07/15/2003
bios0: IBM 27223DG
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT
acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4) USB0(S3) 
USB1(S3) USB2(S3) AC9M(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (PCI1)
acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7
acpitz0 at acpi0: critical temperature is 97 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpicmos0 at acpi0
"IBM0071" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "IBM-02K6928" serial  2694 type LION oem 
"Panasonic"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"PNP0A03" at acpi0 not configured
acpivideo0 at acpi0: VID_
bios0: ROM list: 0xc/0x1 0xe/0x1
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel(R) Pentium(R) M processor 1300MHz ("GenuineIntel" 686-class) 1.30 
GHz, 06-09-05
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,EST,TM2,PERF,MELTDOWN
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: Enhanced SpeedStep 1300 MHz: speeds: 1300, 1200, 1000, 800, 600 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82855PM Host" rev 0x03
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xd000, size 0x1000
ppb0 at pci0 dev 1 function 0 "Intel 82855PM AGP" rev 0x03
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility M7" rev 0x00
drm0 at radeondrm0
radeondrm0: irq 11
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: irq 11
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: irq 11
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: irq 11
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
ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x81
pci2 at ppb1 bus 2
cbb0 at pci2 dev 0 function 0 "TI PCI1510 CardBus" rev 0x00: irq 11
ipw0 at pci2 dev 2 function 0 "Intel PRO/Wireless 2100" rev 0x04: irq 11, 
address XX:CE:NS:OR:ED:XX 
"TI TSB43AB21 FireWire" rev 0x00 at pci2 dev 7 function 0 not configured
fxp0 at pci2 dev 8 function 0 "Intel PRO/100 VE" rev 0x81, i82562: irq 11, 
address XX:CE:NS:OR:ED:XX
inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0xb0
pcmcia0 at cardslot0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DBM LPC" rev 0x01
pciide0 at pci0 dev 31 function 1 "Intel 82801DBM IDE" rev 0x01: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA, 38154MB, 78140160 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0:  ATAPI 5/cdrom 
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev 0x01: irq 11
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 256MB DDR SDRAM non-parity PC2100CL2.5
spdmem1 at iic0 addr 0x51: 256MB DDR SDRAM non-parity PC2100CL2.5
auich0 at pci0 dev 31 function 5 "Intel 82801DB AC97" rev 0x01: irq 11, ICH4
ac97: codec id 0x41445374 (Analog Devices AD1981B)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auich0
"Intel 82801DB Modem" rev 0x01 at pci0 dev 31 function 6 not configured
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 
addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 
addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 
addr 1
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt2 at isa0 port 0x3bc/4: polled
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (b96d3e13d99e46ea.a) swap on wd0b dump on wd0b
initializing kernel modesetting (RV200 0x1002:0x4C57 0x1014:0x0527).
radeon_cp: Failed to 

"Invalid argument" when exec'ing and/or ktrace'ing a file?

2019-05-24 Thread Adam Thompson
I have a binary - built on this 6.5-STABLE amd64 system by an automatic 
build process as part of a CPAN module installation, that will not 
execute:



rt@rt$ /var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf
ksh: /var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf: 
Invalid argument


or even allow itself to be ktrace'd:

rt@rt$ ktrace 
/var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf
ktrace: exec of 
'/var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf' 
failed: Invalid argument


At least ktrace(8) told me it was an exec(3) problem.  So off I go to 
exec(3) which leads me to execve(2), wherein I see:



[EINVAL] argv did not contain at least one element.


errno(2) confirms the english expansion of "Illegal argument"

file(1) gives me a clue, but I don't know what to do with it:


rt@rt$ file `locate bin/wkhtmltopdf`
/usr/local/bin/wkhtmltopdf:   ELF 
64-bit LSB shared object, x86-64, version 1
/var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf: ELF 
64-bit LSB executable, x86-64, version 1


where the version in /usr/local/bin is from ports.

the RT::Extension::TicketPDF version is significantly larger, ~4x, which 
led me to:



rt@rt$ ldd `locate bin/wkhtmltopdf`
/usr/local/bin/wkhtmltopdf:
StartEnd  Type  Open Ref GrpRef Name
041737f61000 04173ac77000 exe   20   0  
/usr/local/bin/wkhtmltopdf
0419ee50 0419ee599000 rlib  01   0  
/usr/local/lib/libjpeg.so.70.0

[...elided...]
/var/www/rt/local/plugins/RT-Extension-TicketPDF/bin/wkhtmltopdf:
not a dynamic executable


So... how do I figure out why a static binary (whose build process is 
pretty opaque) won't/can't run?


Clueless at this level, my detailed knowledge of how exec worked under 
OpenBSD ended in the a.out era.


(oh, the reason I don't use the version from ports?  It's too new for 
the TicketPDF code. *sigh*)


Thanks for any pointers,
-Adam



PF firewall for desktop

2019-05-24 Thread Jean-Francois Simon

Hi,

Out of interest, I'd like to let you know a specific use of OpenBSD with 
PF, in virtualbox, 2 virtual network card Bridged to physical NIC, and 
building up a subnet with NAT and hence running Packet Filter as the 
machine's firewall.



That's the firewall I use under Win7, OpenBSD running in a VM, out of 
pure interest into running BSD and let it purify the network access to 
desktop (without need for additional hardware).



Works well, love it.


Jean-François



Re: productivity/khard (or python) seem slow

2019-05-24 Thread David Mimms

On 2019.05.18 11:39, David Mimms wrote:

On 2019.05.17 11:41, Paco Esteban wrote:

On Thu, 16 May 2019, Joel Carnat wrote:


On Thu 16/05 08:55, Paco Esteban wrote:

Can't say about your VM. On my desktop:

  $ time (khard list | wc -l)
   104
  ( khard list | wc -l; )  0.51s user 0.25s system 97% cpu 0.779 total



Is this on OpenBSD ? The time output looks different.


Of course it is ... (-current though)
That should be zsh that uses an internal builtin instead of
/usr/bin/time I guess (did not check).

Here it is on ksh with base time:

$ time (khard list | wc -l)
 104
0m00.81s real 0m00.59s user 0m00.21s system

Interestingly a bit slower.


What CPU and storage are you running?

My ThinkPad P50:
* Intel Xeon E3-1505M @ 2.80GHz
* 2 x Samsung 960 PRO PCIe NVMe (OpenZFS mirror)
* O/S: Debian Buster

Results:
$ time (khard list | wc -l)
265
( khard list | wc -l; )  0.91s user 0.04s system 100% cpu 0.950 total


My ThinkPad X1 Carbon (4th gen)
* Intel Core i7-6600U @ 2.60GHz (Hyper-threading disabled)
* 1 x Samsung MZ-NLN512 SATA
* O/S: OpenBSD 6.5 -current

Results:
$ time (khard list | wc -l)
   265
( khard list | wc -l; )  2.44s user 2.03s system 100% cpu 4.459 total

The OpenZFS mirror is noticeably slower than a single 960 PRO formatted
as ext4.  Since the X1 has a SATA drive in it, I'll eventually have to
install OpenBSD on my spare Samsung 960 PRO in order to improve overall
performance.

I also tested OpenBSD 6.[45] in VMware Workstation Pro on my P50, and
it ran extremely slow.  So slow that it was unusable.  I figure it's
not optimized for virtualization?  FreeBSD, Linux, and Windows all run
fine in my VMware.


For further comparison, I installed FreeBSD 12.0-RELEASE on my ThinkPad X1
Carbon (4th gen) that was running OpenBSD 6.5 -current and here is the
result:

$ time (khard list | wc -l)
265
( khard list | wc -l; )  1.12s user 0.10s system 100% cpu 1.211 total

DM



Re: When will be created a great desktop experience for OpenBSD?

2019-05-24 Thread Patrick Harper
So you think everyone replying to this thread is an idiot?

-- 
  Patrick Harper
  paia...@fastmail.com

On Fri, 24 May 2019, at 18:38, Jordan Geoghegan wrote:
> 
> On 5/24/19 10:26 AM, Patrick Harper wrote:
> > Is it acceptable for third-parties to produce and distribute physical 
> > copies of releases, using official logos, similar to those made for 6.0 and 
> > prior by the project?
> >
> Can you please stop replying to this thread, I'm so tired of receiving 
> emails from you idiots.
> 
>



Re: When will be created a great desktop experience for OpenBSD?

2019-05-24 Thread Patrick Harper
Is it acceptable for third-parties to produce and distribute physical copies of 
releases, using official logos, similar to those made for 6.0 and prior by the 
project?

-- 
  Patrick Harper
  paia...@fastmail.com



Re: support new

2019-05-24 Thread Rolf

On Sat, Apr 27, 2019 at 12:38:09PM +0200, Rolf wrote:

0
C Belgium
P Oost-Vlaanderen
T Dendermonde
Z 9200
O MetaData
I Rolf
A Oliestraat 50
M sa...@metadata.be
U https://metadata.be/
B +32 477 29 76 04
X N/A
N Network consulting, installation and maintenance. Hosting services.


Can I ask again to take a look at this?



Re: amdgpu report on rx460

2019-05-24 Thread Oriol Demaria

On 23/05/2019 18:26, Peter Piwowarski wrote:

On Thu, 23 May 2019 12:32:05 +0100
Oriol Demaria  wrote:

I saw the commit yesterday, tried recompiling the kernel but the Vega 
8

seems that was not detected. I have a question, does suspend work for
you?


Silly question, but are you sure you enabled the driver in kernel
configuration?
It's not switched on in GENERIC yet.


Not silly question, it wasn't enabled. I compiled a kernel from today 
source with it and tested.



Suspend/resume works with qualifications here. Without amdgpu (i.e. on
GENERIC.MP, displaying with efifb) it never brings any displays up on 
resume

(but otherwise seems to resume correctly). With amdgpu, two of the
three display
outputs are brought back up correctly, but one is not; the card has an 
HDMI, a
DVI-D, and a DisplayPort output, with displays connected to all three, 
but the

DisplayPort output seems to come back up in some invalid mode or other.
Unfortunately all I know is that the monitor claims it's unhappy with 
the mode

it's asked to display, since it doesn't say on-screen what the invalid
parameters are. The first time I tried suspend/resume (in the amdgpu
kernel) the
machine did not resume at all, but I haven't been able to reproduce 
that.

Hibernate doesn't work in the amdgpu kernel; I got a uvm_fault once,
and a second
time the machine went catatonic and wouldn't boot again (I had to 
remove its

backup coin cell to clear it).


Summarizing, hibernate works with framebuffer. Amdgpu driver detects 
additional screens but is unstable, the graphics card seems to hang 
occassionally and then you have to reboot. Real pity because it would 
make my life easier. Suspend doesn't work at all with either UEFI fb or 
amdgpu.


Sent a bug report. Will try new kernel as I see some more commits that 
may fix issues.


Thanks!

Representative dmesg including a suspend/resume cycle, first from 
GENERIC.MP
and then (after a warm reboot) from the amdgpu kernel (not very 
interesting, I

think):

OpenBSD 6.5-current (GENERIC.MP) #0: Wed May 22 00:24:09 EDT 2019

pe...@shoebox-kvm-openbsd-current.foo:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17111023616 (16318MB)
avail mem = 16582344704 (15814MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xe8980 (56 entries)
bios0: vendor American Megatrends Inc. version "F25" date 01/16/2019
bios0: Gigabyte Technology Co., Ltd. AB350M-Gaming 3
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT CRAT CDIT SSDT MCFG
HPET SSDT UEFI IVRS SSDT SSDT WSMT
acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP3(S4) GPP4(S4) GPP5(S4)
GPP6(S4) GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4)
GPPD(S4) GPPE(S4) GPPF(S4) GP17(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 Ryzen 7 1700 Eight-Core Processor, 2994.86 MHz, 17-01-01
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,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully 
associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully 
associative

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 Ryzen 7 1700 Eight-Core Processor, 2994.38 MHz, 17-01-01
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,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully 
associative
cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully 
associative

cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD Ryzen 7 1700 Eight-Core Processor, 2994.38 MHz, 17-01-01
cpu2:

Re: Random system freeze.

2019-05-24 Thread Gregory Edigarov

Hi Paco,

could you please check if you can login over  network when the system 
freeze?

if so - please do a backtrace of the X server.
i.e.:

su -
gdb /usr/X11R6/bin/X `pgrep  X`
bt

just curious, if you'll my condition also.
that may help developers in problem identification.

thanks.

On 23.05.19 18:35, Paco Esteban wrote:

Hi misc@,

I've been having some system freezes lately, as others using intel
graphics.

Sometimes it does not hit in days but sometimes the system hangs 2 or 3
times a day.

I was wondering if there's any iformation I can supply to devs that
could be useful (besides dmesg ...).

Cheers,
Paco.

OpenBSD 6.5-current (GENERIC.MP) #37: Tue May 21 19:41:49 MDT 2019
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16567697408 (15800MB)
avail mem = 16055463936 (15311MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x67493000 (88 entries)
bios0: vendor American Megatrends Inc. version "F4" date 09/04/2015
bios0: Gigabyte Technology Co., Ltd. Z170N-WIFI-CF
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT SSDT UEFI LPIT SSDT SSDT 
SSDT DBGP DBG2 SSDT SSDT BGRT DMAR ASF!
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) 
PS2K(S3) PS2M(S3) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) 
PXSX(S4) RP12(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) Core(TM) i5-6500 CPU @ 3.20GHz, 3601.34 MHz, 06-5e-03
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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
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) Core(TM) i5-6500 CPU @ 3.20GHz, 3500.01 MHz, 06-5e-03
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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz, 3400.00 MHz, 06-5e-03
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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz, 3300.00 MHz, 06-5e-03
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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpihpet0 at acpi0: 2399 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 5 (RP09)
acpiprt5 at acpi0: bus -1 (RP10)
acpiprt6 at acpi0: bus -1 (RP11)
acpiprt7 at acpi0: bus -1 (RP12)
acpiprt8 at acpi0: bus 6 (RP13)
acpiprt9 at acpi0: bus 2 (RP01)
acpiprt10 at acpi0: bus -1 (RP02)
acpiprt11 at acpi0: bus -1 (RP03)
acpiprt12 at acpi0: bus 

Re: Software caused connection abort (53) squid 4.6 on OpenBSD 6.5

2019-05-24 Thread wrh
I have applied that diff to my system and will post once I know the results.

Thank you.

On Thu, May 23, 2019 at 11:41 AM Kasak  wrote:

> Have you seen this https://github.com/squid-cache/squid/pull/404 ?
>
> 23 мая 2019 г., в 18:12, Marcus MERIGHI  написал(а):
>
> Hello,
>
> same here.
>
> I guess bugs@ or ports@ would be better.
>
> w...@wootsie.com (w...@wootsie.com), 2019.05.23 (Thu) 14:36 (CEST):
>
> I have been running into a repeatable error reported by squid 4.6 from
>
> packages once the system has been under a steady load for ~12 hours.
>
>
> I would not call it repeatable because I can't repeat it at will.
> I did not notice the 12 hours interval. But I have by far less users
> behind squid.
>
> Example squid cache.log entry:
>
> 2019/05/22 15:03:41 kid1| oldAccept  FD 18, 0.0.0.0 [ job2]: (53) Software
>
> caused connection abort
>
>
> 2019/05/23 11:51:43 kid1| oldAccept  FD 18, 0.0.0.0 [ job4]: (53)
>  Software caused connection abort
>
> I see this on one machine with windows clients (max. 4) behind it.
> I do not see this on another machine with an OpenBSD client (just 1)
> behind it.
>
> Both are pcengines APUs, but different versions. dmesgs below.
>
> Both setups are up for years, the problem on one of the machines showed
> right after upgrading last week.
>
> Marcus
>
> the machine that does *not* show the symptom:
>
> OpenBSD 6.5 (GENERIC.MP) #0: Wed Apr 24 23:38:54 CEST 2019
>r...@syspatch-65-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
> GENERIC.MP
> real mem = 4246003712 (4049MB)
> avail mem = 4107694080 (3917MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf16d820 (7 entries)
> bios0: vendor coreboot version "4.0" date 09/08/2014
> bios0: PC Engines APU
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S1 S3 S4 S5
> acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT
> acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4)
> PBR7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3)
> UOH3(S3) UOH4(S3) UOH5(S3) [...]
> acpitimer0 at acpi0: 3579545 Hz, 32 bits
> acpihpet0 at acpi0: 14318180 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: AMD G-T40E Processor, 1000.14 MHz, 14-02-00
> 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,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
> cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
> 64b/line 16-way L2 cache
> cpu0: 8 4MB entries fully associative
> cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully
> associative
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 200MHz
> cpu0: mwait min=64, max=64, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: AMD G-T40E Processor, 1000.00 MHz, 14-02-00
> 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,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
> cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
> 64b/line 16-way L2 cache
> cpu1: 8 4MB entries fully associative
> cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully
> associative
> cpu1: smt 0, core 1, package 0
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
> acpiprt0 at acpi0: bus -1 (AGPB)
> acpiprt1 at acpi0: bus -1 (HDMI)
> acpiprt2 at acpi0: bus 1 (PBR4)
> acpiprt3 at acpi0: bus 2 (PBR5)
> acpiprt4 at acpi0: bus 3 (PBR6)
> acpiprt5 at acpi0: bus -1 (PBR7)
> acpiprt6 at acpi0: bus 5 (PE20)
> acpiprt7 at acpi0: bus -1 (PE21)
> acpiprt8 at acpi0: bus -1 (PE22)
> acpiprt9 at acpi0: bus -1 (PE23)
> acpiprt10 at acpi0: bus 0 (PCI0)
> acpiprt11 at acpi0: bus 4 (PIBR)
> acpicpu0 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS
> acpicpu1 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS
> acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
> acpicmos0 at acpi0
> acpibtn0 at acpi0: PWRB
> cpu0: 1000 MHz: speeds: 1000 800 MHz
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "AMD AMD64 14h Host" rev 0x00
> ppb0 at pci0 dev 4 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
> pci1 at ppb0 bus 1
> re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E
> (0x2c00), msi, address 00:0d:b9:3f:78:18
> rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 4
> ppb1 at pci0 dev 5 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
> pci2 at ppb1 bus 2
> re1 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E
> (0x2c00), msi, address 00:0d:b9:3f:78:19
> rgephy1 at re1 phy 7: RTL8169S/8110S/8211 PHY, rev. 4
> ppb2 at pci0 dev 6 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
> pci3 at ppb2 bus 3
> re2 at pci3 dev 0 

Re: bgpd acting up, dropping connected/static network statements

2019-05-24 Thread openbsd
Hello,

I finally got to testing this and the bug seems to be fixed. What is
the recommended way of implementing this fix into a critical
production environment?

Should we wait for a syspatch (will one be made available for this bug)?


On Fri, May 3, 2019 at 12:12 PM Claudio Jeker  wrote:
>
> On Fri, May 03, 2019 at 11:52:07AM +0200, open...@kene.nu wrote:
> > Much appreciated, will test. Did this also affect previous versions
> > (specifically thinking about 6.3 and 6.4)?
>
> No. This code was changed after 6.4
>
> > On Fri, May 3, 2019 at 11:43 AM Claudio Jeker  
> > wrote:
> > >
> > > On Fri, May 03, 2019 at 09:59:40AM +0200, open...@kene.nu wrote:
> > > > Hello,
> > > >
> > > > I am seeing strange behaviour of bgpd in 6.5.
> > > >
> > > > Not sure what causes the networks in bgpd to disappear but they do
> > > > disappear and performing a netstart pick the network back up again in
> > > > bgpd. I cannot see this in either 6.4 or 6.3. One triggering factor
> > > > seems to be restarting the bgpd process.
> > > >
> > > > Excerpt form the daemon logs (bgpd restart or reload):
> > > > May  3 07:44:25 host bgpd[94972]: Rib Loc-RIB: neighbor 172.30.198.4
> > > > (LOCAL) AS64712: announce 10.1.150.0/24
> > > > May  3 07:44:25 host bgpd[94972]: Rib Loc-RIB: neighbor 172.30.198.4
> > > > (LOCAL) AS64712: withdraw announce 10.1.150.0/24
> > > >
> > > > If one performs a netstart, of relevant vlan interfaces, the
> > > > announcements seem to survive a bgpd reload. Static routes never
> > > > survive a restart or reload.
> > > >
> > > > Some additional commands to show behaviour:
> > > > # uname -a
> > > > OpenBSD host 6.5 GENERIC.MP#3 amd64
> > > > # ifconfig vlan190
> > > > vlan190: flags=8943 mtu 
> > > > 1500
> > > > lladdr 
> > > > index 33 priority 0 llprio 3
> > > > encap: vnetid 190 parent em0 txprio packet
> > > > groups: vlan
> > > > media: Ethernet autoselect (1000baseT full-duplex,master)
> > > > status: active
> > > > inet 10.1.150.2 netmask 0xff00 broadcast 10.1.150.255
> > > > # grep connected /etc/bgpd.conf
> > > > network inet connected set community 65000:64712
> > > > # bgpctl sh ip bgp 10.1.150.0/24
> > > > flags: * = Valid, > = Selected, I = via IBGP, A = Announced,
> > > >S = Stale, E = Error
> > > > origin validation state: N = not-found, V = valid, ! = invalid
> > > > origin: i = IGP, e = EGP, ? = Incomplete
> > > >
> > > > flags ovs destination  gateway  lpref   med aspath 
> > > > origin
> > > > # sh /etc/netstart vlan150
> > > > # bgpctl sh ip bgp 10.1.150.0/24
> > > > flags: * = Valid, > = Selected, I = via IBGP, A = Announced,
> > > >S = Stale, E = Error
> > > > origin validation state: N = not-found, V = valid, ! = invalid
> > > > origin: i = IGP, e = EGP, ? = Incomplete
> > > >
> > > > flags ovs destination  gateway  lpref   med aspath 
> > > > origin
> > > > AI*>N 10.1.150.0/240.0.0.0100 0 i
> > > >
> > > >
> > > > My bgpd.conf:
> > > > # GLOBALS
> > > > AS 64712
> > > > router-id 172.30.198.4
> > > > holdtime 9
> > > > log updates
> > > >
> > > > prefix-set internal { 10.0.0.0/8 prefixlen >= 16, 10.60.0.0/15,
> > > > 172.20.0.0/16 prefixlen <= 32, 172.29.0.0/16 prefixlen >= 24,
> > > > 172.29.248.10/31 prefixlen = 32, 172.30.0.0/16 prefixlen >= 24 }
> > > >
> > > > # DEFAULT FILTERING
> > > > deny from any
> > > > deny to any
> > > >
> > > > # NETWORK STATEMENTS
> > > > network 172.30.198.4/32 set community 65000:64712
> > > > network inet connected set community 65000:64712
> > > > network inet static set community 65000:64712
> > > >
> > > > # NEIGHBORS
> > > > group "vpn" {
> > > > announce IPv6 none
> > > > route-reflector
> > > > remote-as 64712
> > > >
> > > > neighbor 10.1.230.9 {
> > > > descr "vpn1"
> > > > }
> > > > neighbor 10.1.230.10 {
> > > > descr "vpn2"
> > > > }
> > > > }
> > > >
> > > > # SOURCE FILTERING
> > > > allow to group "vpn" prefix-set internal community 65000:64712
> > > > # DEST FILTERING
> > > > allow from group "vpn" prefix-set internal
> > > > # TRAFFIC ENGINEERING
> > > > match to group "vpn" set nexthop 10.1.230.12
> > > > match to any prefix 172.30.198.4/32 set nexthop self
> > > >
> > >
> > > Thanks for the detailed report. I quick workaround is to reload the config
> > > twice. Then the networks are added again. The proper fix is attached.
> > >
> > > The problem was that when already present networks were readded the
> > > function kr_net_redist_add() returned 0 which was propegated to
> > > kr_net_match() which then caused kr_redistribute() to actually remove the
> > > prefix.
> > >
> > > I changed the code to only return 0 when there is actually the case that
> > > the network being added is shadowed by another one and therefor this
> > > prefix should be removed. While there I also fixed a memory leak ;)
> > >
> > > Please test.
> > > --
> > > :wq Claudio
> > >
> > > Index: kroute.c
> > > 

Re: user unable to log in xenodm / Xorg session | XIO fatal io error 35

2019-05-24 Thread Mihai Popescu
> I suspect the problem may have had to do ...

Why the hell did you contact the list then? To confirm your suspicion(s)?



Re: OpenBSD on VMware ESXi

2019-05-24 Thread Roderick



On Thu, 23 May 2019, Ian Darwin wrote:


..., but if you just wanted hosting in a hurry and cheap, vultr.com offers
an entry-level vhost with OpenBSD 6.5 (or half a dozen others including BSDs
and Linuxes) already installed (or you can use any ISO to install from)
for US$2.50/month, with console access. I'm hosting my secondary DNS there
and have had zero issues so far, though I didn't do a full reinstall.


Well, I was just testing for being prepared when I need "hosting in a
hurry and cheap". Waiting till one is in need makes the need and the
price bigger.

It was an offer of ionos.de, 500MB Ram, 10 GB SSD, 1vCore, Linux OS.
For me OK, I like to test under spare resources. What runs under spare
resources, runs much better under better conditions: it is a way to
select what to run.

The price of ionos.de: 1 EUR/Month, bound to 1 year, but one can
end the contract in the first 30 days. Probably an offer to
catch customers.

The answer to my question to change to "LSI Logic SAS" was: they cannot
do individual adaptions, but I can take a root server from them.

This answer is perfectly acceptable, as also the ugly Web Console, if
one can rely in their offer of 1 Eur/month, if it is not a trap to
catch customers. They are not saying me, I must take a root server
from them.

It is possible to boot a CD and install an own OS. It would have been
wonderfull to run OpenBSD, unfortunately almost worked.

Rodrigo



Re: When will be created a great desktop experience for OpenBSD?

2019-05-24 Thread Peter Kay
There's a very simple solution to this : create your own post install setup 
program and stick it in ports. If it becomes wildly popular then a line could 
be added to afterboot to point users at it.


In the meantime I'm quite happy not answering X questions when installing 
OpenBSD as a firewall.


You're also wrong about FVWM and HDPI screens. FVWM is very flexible, but a 
pain to configure (I use cwm). The majority of users still use 1080p monitors 
(go check the Steam hardware survey).