Re: OpenBSD on VMware ESXi

[loopw]

On 2019-05-22 11:04, Stuart Henderson wrote:

No idea, I don't run those.



I have some experience:
For over three years I have been running a qemu/KVM on Linux hypervisor 
for a lab that's had at least four running OpenBSD vms with virtio and 
e1000 nics.  The obsd vms have never had a kernel panic, where they 
usually do basic routing/nating for a dev network, but occasionally do a 
lot of iperf traffic while I work on their pf.conf files.





--
Sent from a phone, apologies for poor formatting.

On 22 May 2019 17:20:16 Igor Podlesny  wrote:

On Wed, 22 May 2019 at 23:06, Stuart Henderson  
wrote:

[...]
vmxnet3 suffers kernel panics under some conditions, e1000 is rock 
solid

for me.


Any known similarities in regards of vio -- VirtIO network device
(bhyve, KVM, QEMU, and VirtualBox)?

--
End of message. Next message?

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

[openbsd . ssab]

I have now been running with OpenBSD 6.5 for a couple of weeks
without meeting this problem again, on a fresh install.
I am very careful not to crash or halt the system abruptly !

I suspect the problem may have had to do with the
inteldrm driver and the EFI, as suggested by dmesg(8) :

...
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: LCD0
cpu0: Enhanced SpeedStep 2594 MHz: speeds: 2600, 2500, 2400, 2300, 2200, 2100, 
2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1366x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi, xHCI 1.0
...
vmm0 at mainbus0: VMX/EPT
efifb at mainbus0 not configured
error: [drm:pid0:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo 
underrun on pch transcoder B
error: [drm:pid0:intel_pch_fifo_underrun_irq_handler] *ERROR* PCH transcoder B 
FIFO underrun
...
error: [drm:pid81698:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch 
fifo underrun on pch transcoder B
error: [drm:pid81698:intel_pch_fifo_underrun_irq_handler] *ERROR* PCH 
transcoder B FIFO underrun
error: [drm:pid54999:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch 
fifo underrun on pch transcoder B
error: [drm:pid54999:intel_pch_fifo_underrun_irq_handler] *ERROR* PCH 
transcoder B FIFO underrun

> On Thu, May 2, 2019 at 7:53 PM  wrote:
> >
> > SYMPTOM: Soon after a fresh OpenBSD install intended to use as a
> > laptop / work engine, and consequently a few uses of a graphical
> > session, suddenly the X session cannot start anymore : logging
> > in with a correct user/passwd pair provokes a crash and restart of
> > the
> > X Display Manager, displaying the xdm login screen anew.
> > But I can still log in xdm as root.
> >
> > Xorg.0.log https://pastebin.com/pZDf90TE
> > xenodm.log https://pastebin.com/abjyLCyU
> > dmesg.boot https://pastebin.com/T3UGucB1 (also attached)
> 
> Hi,
> 
> What is the contents of your ~/.xsession & ~/.xsession-errors files?
> 
> I had this same issue, and was able to solve it by removing .xsession
> or replacing it with an empty file.
> 
> Ian
> 
> 

Hi Ian, thanks for your concern.

I had saved the files from my system before re-installing :
sylvain:531$ cat .xsession  


export  ENV=$HOME/.profile
export  LC_CTYPE=fr_FR.UTF-8
sylvain:532$ cat .xsession-errors   


sylvain:533$ 

The .xsession on my present system/home is indeed absent.

Sylvain S

Re: amdgpu report on rx460

[Peter Piwowarski]

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.

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).

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: 
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
cpu2: 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
cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu2: DTLB 64 4KB entries fully associative, 64 

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

[Patrick Harper]

Thank you for helping me keep this thread going.

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

On Thu, 23 May 2019, at 20:04, Daniel Jakots wrote:
> On Thu, 23 May 2019 19:51:45 +, "Patrick Harper"
>  wrote:
> 
> > Our ideas of the setup process aren't equal so I disagree.
> 
> Can you please stop answering to this useless thread?
>

VMM running machines shown as stopped

[Jan Vlach]

Hi misc@

I'm running -current (GENERIC.MP) #37 from May 21 and virtual machines
that are running are still in state STOPPED.

Anyone else seeing this?

### EXHIBIT A
[21:11][janus@samsara:~]$ vmctl status 
   ID   PID VCPUS  MAXMEM  CURMEM TTYOWNERSTATE NAME
3 20969 11.0G916K   ttyp4janus  stopped
04-alpine
1  8321 11.0G1.1M   ttyp3janus  stopped
02-current
2 79289 11.0G248M   ttyp2janus  stopped
03-stable
[21:11][janus@samsara:~]$ ssh stable
Last login: Thu May 23 12:50:57 2019 from 10.0.0.1
OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019

Welcome to OpenBSD: The proactively secure Unix-like operating system.

Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code.  With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.

stable$ ^D
Connection to stable closed.
[21:11][janus@samsara:~]$ vmctl status  
   
   ID   PID VCPUS  MAXMEM  CURMEM TTYOWNERSTATE NAME
3 20969 11.0G   63.6M   ttyp4janus  stopped
04-alpine
1  8321 11.0G182M   ttyp3janus  stopped
02-current
2 79289 11.0G284M   ttyp2janus  stopped
03-stable


### LOGS # vm 2 didn't wan't to start at first, took two vmctl start 2
May 23 21:09:38 samsara vmd[52032]: 03-stable: started vm 2
successfully, tty /dev/ttyp1
May 23 21:10:31 samsara vmd[52032]: 03-stable: started vm 2
successfully, tty /dev/ttyp2
May 23 21:11:15 samsara vmd[52032]: 02-current: started vm 1
successfully, tty /dev/ttyp3
May 23 21:11:16 samsara vmd[52032]: 04-alpine: started vm 3
successfully, tty /dev/ttyp4
May 23 21:11:55 samsara vmd[20969]: vcpu_process_com_data: guest reading
com1 when not ready
May 23 21:12:28 samsara vmd[20969]: vcpu_process_com_data: guest reading
com1 when not ready


### vm.conf
socket owner :wheel


switch "nat" {
interface bridge0
}

ramdisk="/bsd-current.rd"


vm "02-current" {
#boot $ramdisk
memory 1G
disable
owner janus
disk /home/VM/current-disk0.img
interface { switch "nat" }
}
vm "03-stable" {
#boot "/bsd.rd"
memory 1G
disable
owner janus
disk /home/VM/stable-disk0.img
interface { switch "nat" }
}
vm "04-alpine" {
memory 1G
disable
owner janus
#disk /home/VM/alpine-virt-3.9.2-x86_64.iso
disk /home/VM/alpine-disk0.img
interface { switch "nat" }
}

### id janus
uid=1000(janus) gid=1000(janus) groups=1000(janus), 0(wheel),
5(operator), 9(wsrc), 69(network), 117(dialer)

### DMESG

OpenBSD 6.5-current (GENERIC.MP) #36: Mon May 20 16:36:12 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8451125248 (8059MB)
avail mem = 8184889344 (7805MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries)
bios0: vendor LENOVO version "8DET76WW (1.46 )" date 06/21/2018
bios0: LENOVO 4291Z8U
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT 
SSDT DMAR UEFI UEFI UEFI
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) EHC1(S3) 
EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 797.54 MHz, 06-2a-07
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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 797.42 MHz, 06-2a-07
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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)

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

[Gustavo Rios]

desktop!
Never, at least that

Em qui, 23 de mai de 2019 às 16:00, Patrick Harper
 escreveu:
>
> Our ideas of the setup process aren't equal so I disagree.
>
> --
>   Patrick Harper
>   paia...@fastmail.com
>
> On Thu, 23 May 2019, at 18:16, Raul Miller wrote:
> > This looks like violent agreement. (It's perhaps worth noting that if
> > you change the first word here from "No" to "Yes" that the idea being
> > expressed does not change.)
> >
> > Thanks,
> >
> > --
> > Raul
> >
> > On Thu, May 23, 2019 at 1:35 PM Patrick Harper  wrote:
> > >
> > > No, the installation program should make setup as easy as possible. The 
> > > idea of a common development platform for X being suited only for circa 
> > > 100dpi screens in 2019 is ludicrous. Making users pore  through 
> > > half-a-dozen man pages and config files to make their X systems usable on 
> > > hidpi screens is ludicrous.
> > >
> > > --
> > >   Patrick Harper
> > >   paia...@fastmail.com
> > >
> > > On Thu, 23 May 2019, at 16:58, Ingo Schwarze wrote:
> > > > Hi,
> > > >
> > > > Patrick Harper wrote on Thu, May 23, 2019 at 04:50:54PM +0100:
> > > >
> > > > > I think OpenBSD could be made easier to set up for GUI applications
> > > > > if some configuration that is currently done in files could be moved
> > > > > to the install program.
> > > >
> > > > I very strongly oppose the idea.
> > > >
> > > > > These questions (or similar) could be shown
> > > >
> > > > Absolutely not.  The installer should ask as few questions as possible,
> > > > ideally none whatsoever.  *That* is a way to simplify setup.
> > > >
> > > > The topics you mention have nothing to do with installation.
> > > > They are merely low-importance user configuration that can be done
> > > > at any time if desired.  But almost no user will ever have to consider
> > > > any of those; i certainly didn't, ever, and i have been using many
> > > > OpenBSD computers for almost two decades now, including with a wide
> > > > variety of GUI applications.
> > > >
> > > > Yours,
> > > >   Ingo
> > > >
> > >
> >
>


-- 
Pag Bem Fácil Ltda
www.pagbemfacil.com.br

Re: Modern browser for OpenBSD powerpc

[Dumitru Moldovan]

On Thu, 23 May 2019 10:31:58 +0200, Antal Ispanovity 
wrote:

> 2019-05-23 8:19 GMT+02:00, John Gould :
> > Can someone suggest a modern graphical browser for OpenBSD PowerPC?
> epiphany, if you need JS

Does it work for you?  I was so enthused by the idea (and irony!) of
WebKit browsers packaged in 6.5 for macppc that I booted up an old and
slow PowerMac lying around to update it to latest release.

True, Epiphany (and surf, possibly other WebKit-based browsers too) are
available as packages, but they won't load even the simplest web pages
for me.  Eg. "surf -bdgimnps http://ftp.openbsd.org; opens a blank page
with this error: "WebKit encountered an internal error."

Not to belittle the work done already, I think this is great progress
from the macpcc porters!

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

[Daniel Jakots]

On Thu, 23 May 2019 19:51:45 +, "Patrick Harper"
 wrote:

> Our ideas of the setup process aren't equal so I disagree.

Can you please stop answering to this useless thread?

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

[Patrick Harper]

Our ideas of the setup process aren't equal so I disagree.

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

On Thu, 23 May 2019, at 18:16, Raul Miller wrote:
> This looks like violent agreement. (It's perhaps worth noting that if
> you change the first word here from "No" to "Yes" that the idea being
> expressed does not change.)
> 
> Thanks,
> 
> -- 
> Raul
> 
> On Thu, May 23, 2019 at 1:35 PM Patrick Harper  wrote:
> >
> > No, the installation program should make setup as easy as possible. The 
> > idea of a common development platform for X being suited only for circa 
> > 100dpi screens in 2019 is ludicrous. Making users pore  through 
> > half-a-dozen man pages and config files to make their X systems usable on 
> > hidpi screens is ludicrous.
> >
> > --
> >   Patrick Harper
> >   paia...@fastmail.com
> >
> > On Thu, 23 May 2019, at 16:58, Ingo Schwarze wrote:
> > > Hi,
> > >
> > > Patrick Harper wrote on Thu, May 23, 2019 at 04:50:54PM +0100:
> > >
> > > > I think OpenBSD could be made easier to set up for GUI applications
> > > > if some configuration that is currently done in files could be moved
> > > > to the install program.
> > >
> > > I very strongly oppose the idea.
> > >
> > > > These questions (or similar) could be shown
> > >
> > > Absolutely not.  The installer should ask as few questions as possible,
> > > ideally none whatsoever.  *That* is a way to simplify setup.
> > >
> > > The topics you mention have nothing to do with installation.
> > > They are merely low-importance user configuration that can be done
> > > at any time if desired.  But almost no user will ever have to consider
> > > any of those; i certainly didn't, ever, and i have been using many
> > > OpenBSD computers for almost two decades now, including with a wide
> > > variety of GUI applications.
> > >
> > > Yours,
> > >   Ingo
> > >
> >
>

SOLUTION (with code), WAS: Re: When will be created a great desktop experience for OpenBSD?

[chohag]

Here is a script you can all use which selects a desktop environment,
installs it if necessary, and configures a (eg. your) user's X session
so that it starts when he, she or you log in, facilitating further
user-centric configuration.

Perhaps if you ask really nicely the devs will install it into the base
system somewhere for you and maintain the map of packages to
descriptions because even the densest among you must be aware by now
that you're never getting anything more complicated than this.

Now will you all please stop this and go and do something useful?

Matthew

src/gui-selector.sh:

#!/bin/ksh

default="fvwm"
builtin="cwm fvwm twm"
bloaty="kde gnome xfce"
gnome="gnome" # Is there something for this?
gnome_full=$gnome
gnome_bloat="gnome-extras"
gnome_bin=/usr/local/bin/gnome
kde="kde4-minimal"
kde_full="kde4"
kde_bloat="kde4-extras"
kde_bin=/usr/local/bin/kde4
xfce="xfce"
xfce_full="xfce-extras"
xfce_bloat=$xfce_full
xfce_bin=/usr/local/bin/xfce

cwm_desc="?"
fvwm_desc="Simple, effective, default"
twm_desc="Theo likes it so it must be good"
gnome_desc="We know what you want, except not correctly like Apple"
kde_desc="The only DE ever to kill my X server"
xfce_desc="I heard of this once"

error() {
  if [[ $# != 0 ]]; then
echo "$@" >&2
  else
cat >&2
  fi
}

abort() {
  error "$@"
  exit 1
}

msg() {
  if [[ $# != 0 ]]; then
echo "$@"
  else
cat
  fi
}

prompt() {
  answer= # NOT local
  echo -n "$@" ''
  read answer
  echo
}

root=
if [[ `id -u` -ne 0 ]]; then
  root=doas
  error < $userhome/.xsession
else
  eval echo exec \$${de}_bin > $userhome/.xsession
fi || abort Could not write to $userhome/.xsession

msg << COMPLETE
$de has been installed and configured as $whose default desktop
environment. You may log out or reboot to enter it.

To install another environment and change $whose default, simply
run this script again.

COMPLETE

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

[Raul Miller]

This looks like violent agreement. (It's perhaps worth noting that if
you change the first word here from "No" to "Yes" that the idea being
expressed does not change.)

Thanks,

-- 
Raul

On Thu, May 23, 2019 at 1:35 PM Patrick Harper  wrote:
>
> No, the installation program should make setup as easy as possible. The idea 
> of a common development platform for X being suited only for circa 100dpi 
> screens in 2019 is ludicrous. Making users pore  through half-a-dozen man 
> pages and config files to make their X systems usable on hidpi screens is 
> ludicrous.
>
> --
>   Patrick Harper
>   paia...@fastmail.com
>
> On Thu, 23 May 2019, at 16:58, Ingo Schwarze wrote:
> > Hi,
> >
> > Patrick Harper wrote on Thu, May 23, 2019 at 04:50:54PM +0100:
> >
> > > I think OpenBSD could be made easier to set up for GUI applications
> > > if some configuration that is currently done in files could be moved
> > > to the install program.
> >
> > I very strongly oppose the idea.
> >
> > > These questions (or similar) could be shown
> >
> > Absolutely not.  The installer should ask as few questions as possible,
> > ideally none whatsoever.  *That* is a way to simplify setup.
> >
> > The topics you mention have nothing to do with installation.
> > They are merely low-importance user configuration that can be done
> > at any time if desired.  But almost no user will ever have to consider
> > any of those; i certainly didn't, ever, and i have been using many
> > OpenBSD computers for almost two decades now, including with a wide
> > variety of GUI applications.
> >
> > Yours,
> >   Ingo
> >
>

Re: Duplicity & /etc/daily.local

[Noth]

On 22/05/2019 04:46, Patrick Wildt wrote:

On Mon, May 20, 2019 at 11:50:13PM +0200, Noth wrote:

Hi misc@,


   I'm trying to run daily backups to a sftp server for various VMs and
devices on my network, and want to use /etc/daily.local for this. I'm
calling this script from the daily.local file:

env 'GNUPG="/usr/local/bin/gpg" PASSPHRASE="mypassword"'
/root/duplicity-hostname.sh

but unfortunately duplicity can't find gnupg and errors out with this error
message:

Traceback (innermost last):
   File "/usr/local/bin/duplicity", line 1562, in 
 with_tempdir(main)
   File "/usr/local/bin/duplicity", line 1548, in with_tempdir
 fn()
   File "/usr/local/bin/duplicity", line 1387, in main
 action = commandline.ProcessCommandLine(sys.argv[1:])
   File "/usr/local/lib/python2.7/site-packages/duplicity/commandline.py", line 
1088, in ProcessCommandLine
 globals.gpg_profile = gpg.GPGProfile()
   File "/usr/local/lib/python2.7/site-packages/duplicity/gpg.py", line 92, in 
__init__
 self.gpg_version = self.get_gpg_version(globals.gpg_binary)
   File "/usr/local/lib/python2.7/site-packages/duplicity/gpg.py", line 107, in 
get_gpg_version
 res = gnupg.run(["--version"], create_fhs=["stdout"])
   File "/usr/local/lib/python2.7/site-packages/duplicity/gpginterface.py", 
line 374, in run
 create_fhs, attach_fhs)
   File "/usr/local/lib/python2.7/site-packages/duplicity/gpginterface.py", 
line 423, in _attach_fork_exec
 self._as_child(process, gnupg_commands, args)
   File "/usr/local/lib/python2.7/site-packages/duplicity/gpginterface.py", 
line 462, in _as_child
 os.execvp(command[0], command)
   File "/usr/local/lib/python2.7/os.py", line 346, in execvp
 _execvpe(file, args)
   File "/usr/local/lib/python2.7/os.py", line 382, in _execvpe
 func(fullname, *argrest)
  OSError: [Errno 2] No such file or directory

GPGError: failed to determine gnupg version of None from


duplicity-hostname.sh content:

#!/bin/ksh
PASSPHRASE=mypassword
/usr/local/bin/duplicity incremental /var sftp://user@backuphost:/hostname/var
/usr/local/bin/duplicity incremental /etc sftp://user@backuphost:/hostname/etc
/usr/local/bin/duplicity incremental /root sftp://user@backuphost:/hostname/root

Can daily.local even handle this or is the environment too limited?

Cheers,

Noth


I have the same setup and it failed for me as well.  I somehow managed
to fix it by setting PATH and also exporting TERM:

PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games
TERM=xterm
export PATH TERM

And you should probably also do something like:

. /root/.passphrase
test -n "$PASSPHRASE" || exit 0
export PASSPHRASE

Patrick


Hello again,

  Sorry about the delay, I haven't been able to look at this till today.

So:

1. adding PATH does make duplicity find gpg. Thanks Antoine Jacoutot for 
the suggestion on getting the env mailed via cron.


2. Next issue is that the sftp connection fails, because it can't 
authenticate the host and wants confirmation on accepting the key. This 
is despite having copied the user public key to 
user/.ssh/.authorized_keys and tested using sftp user@hostname and sftp 
user@hostname.domain . Current state of the script is this:



#!/bin/ksh
export PASSPHRASE="mypassword"
export PATH=${PATH}:/usr/local/bin
/usr/local/bin/duplicity incremental 
--ssh-options="-oStrictHostKeyChecking=no" /var 
sftp://user@backuphost:/hostname/var


As you can see I'm passing the option so it doesn't ask for 
confirmation, but it still happens:



/usr/local/lib/python2.7/site-packages/paramiko/kex_ecdh_nist.py:39: 
CryptographyDeprecationWarning: encode_point has been deprecated on 
EllipticCurvePublicNumbers and will be removed in a future version. Please use 
EllipticCurvePublicKey.public_bytes to obtain both compressed and uncompressed 
point encoding.
  m.add_string(self.Q_C.public_numbers().encode_point())
/usr/local/lib/python2.7/site-packages/paramiko/kex_ecdh_nist.py:92: 
CryptographyDeprecationWarning: Support for unsafe construction of public 
numbers from encoded data will be removed in a future version. Please use 
EllipticCurvePublicKey.from_encoded_point
  self.curve, Q_S_bytes
/usr/local/lib/python2.7/site-packages/paramiko/kex_ecdh_nist.py:103: 
CryptographyDeprecationWarning: encode_point has been deprecated on 
EllipticCurvePublicNumbers and will be removed in a future version. Please use 
EllipticCurvePublicKey.public_bytes to obtain both compressed and uncompressed 
point encoding.
  hm.add_string(self.Q_C.public_numbers().encode_point())
BackendException: ssh connection to dupuser@tombstone:22 failed: EOF when 
reading a line
The authenticity of host 'tombstone' can't be established.
SSH-ED25519 key fingerprint is fd:60:79:e6:d9:06:47:41:b6:54:19:63:9c:b0:d2:89.
Are you sure you want to continue connecting (yes/no)? 
/usr/local/lib/python2.7/site-packages/paramiko


I tried adding StrictHostKeyChecking no to /etc/ssh/ssh_config and 

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

[Patrick Harper]

No, the installation program should make setup as easy as possible. The idea of 
a common development platform for X being suited only for circa 100dpi screens 
in 2019 is ludicrous. Making users pore  through half-a-dozen man pages and 
config files to make their X systems usable on hidpi screens is ludicrous. 

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

On Thu, 23 May 2019, at 16:58, Ingo Schwarze wrote:
> Hi,
> 
> Patrick Harper wrote on Thu, May 23, 2019 at 04:50:54PM +0100:
> 
> > I think OpenBSD could be made easier to set up for GUI applications
> > if some configuration that is currently done in files could be moved
> > to the install program.
> 
> I very strongly oppose the idea.
> 
> > These questions (or similar) could be shown
> 
> Absolutely not.  The installer should ask as few questions as possible,
> ideally none whatsoever.  *That* is a way to simplify setup.
> 
> The topics you mention have nothing to do with installation.
> They are merely low-importance user configuration that can be done
> at any time if desired.  But almost no user will ever have to consider
> any of those; i certainly didn't, ever, and i have been using many
> OpenBSD computers for almost two decades now, including with a wide
> variety of GUI applications.
> 
> Yours,
>   Ingo
>

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

[Kasak]

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 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E 
> (0x2c00), msi, address 00:0d:b9:3f:78:1a
> rgephy2 at re2 phy 7: 

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

[Christopher Turkel]

On Thu, May 23, 2019 at 12:00 PM Ingo Schwarze  wrote:

> Hi,
>
> Patrick Harper wrote on Thu, May 23, 2019 at 04:50:54PM +0100:
>
> > I think OpenBSD could be made easier to set up for GUI applications
> > if some configuration that is currently done in files could be moved
> > to the install program.
>
> I very strongly oppose the idea.
>
> > These questions (or similar) could be shown
>
> Absolutely not.  The installer should ask as few questions as possible,
> ideally none whatsoever.  *That* is a way to simplify setup.
>
> The topics you mention have nothing to do with installation.
> They are merely low-importance user configuration that can be done
> at any time if desired.  But almost no user will ever have to consider
> any of those; i certainly didn't, ever, and i have been using many
> OpenBSD computers for almost two decades now, including with a wide
> variety of GUI applications.
>
> Yours,
>   Ingo
>
>
I actually like the idea of giving the user a choice of WMs if they install
X, but I agree its a low importance idea.

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

[Ingo Schwarze]

Hi,

Patrick Harper wrote on Thu, May 23, 2019 at 04:50:54PM +0100:

> I think OpenBSD could be made easier to set up for GUI applications
> if some configuration that is currently done in files could be moved
> to the install program.

I very strongly oppose the idea.

> These questions (or similar) could be shown

Absolutely not.  The installer should ask as few questions as possible,
ideally none whatsoever.  *That* is a way to simplify setup.

The topics you mention have nothing to do with installation.
They are merely low-importance user configuration that can be done
at any time if desired.  But almost no user will ever have to consider
any of those; i certainly didn't, ever, and i have been using many
OpenBSD computers for almost two decades now, including with a wide
variety of GUI applications.

Yours,
  Ingo

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

[Patrick Harper]

I think OpenBSD could be made easier to set up for GUI applications if some 
configuration that is currently done in files could be moved to the install 
program. 

These questions (or similar) could be shown after the one about xenodm:

'Select a resolution for all screens in dots per inch ('?' for list) [96]'

The options would be 96, 120, 144, 192 and 284. The changes made for a 
different value would not only be the Xserver dpi setting, but also for the 
sizes of fonts and graphical elements in the default configuration files of 
window managers (fvwmrc, cwmrc, twmrc), xclock, xterm, xconsole, xcalc and xman.

'Choose a window manager for X ('cwm' or 'fvwm' or 'twm') [fvwm]'

If cwm is entered here, this question could be shown:

'Do you want cwm key bindings to use the Mod4 (windows) key in place of the 
Meta key? [no]'

There might be a reason for cwm key bindings to not use Mod4, but those who 
have the key available might appreciate not having to create a custom cwmrc so 
they can avoid conflicts with default keyboard shortcuts in some ports.

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

Random system freeze.

[Paco Esteban]

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 -1 (RP04)
acpiprt13 at acpi0: bus 3 (RP05)
acpiprt14 at acpi0: bus 4 (RP06)
acpiprt15 at acpi0: bus -1 (RP07)
acpiprt16 at acpi0: bus -1 (RP08)
acpiprt17 at acpi0: bus 1 (RP17)
acpiprt18 at acpi0: bus -1 (RP18)
acpiprt19 at acpi0: bus -1 (RP19)
acpiprt20 at acpi0: bus -1 (RP20)
acpiprt21 at acpi0: bus -1 (RP14)
acpiprt22 at 

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

[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 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E (0x2c00), 
msi, address 00:0d:b9:3f:78:1a
rgephy2 at re2 phy 7: RTL8169S/8110S/8211 PHY, rev. 4
ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x40: apic 2 int 19, AHCI 
1.2
ahci0: port 0: 3.0Gb/s
ahci0: port 1: 6.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct fixed 
naa.5e83a977c035d166
sd0: 114473MB, 512 bytes/sector, 234441648 sectors, thin
sd1 at scsibus1 targ 1 lun 

Re: Modern browser for OpenBSD powerpc

[Patrick Harper]

Epiphany/GNOME Web is fine, but make sure you have the ports tree loaded for 
stable updates, WebKit is not the safest code base in the world.

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

On Thu, 23 May 2019, at 07:21, John Gould wrote:
> Can someone suggest a modern graphical browser for OpenBSD PowerPC?
> I'm trying to run
> several G5's and g4 mini's on 6.5 as desktop machines. The basic
> install works really well but there doesn't seem to be an up to date
> graphically browser.
> 
> It's thanks to all the work the devs have put into OpenBSD powerpc
> that these machine are still very usable. They are hopelessly out of
> date as far as the Mac OS are concerned!
> 
> Kind regards John.
> 
>

Re: Installer buggy (Re: OpenBSD on VMware ESXi)

[Roderick]

Thanks, Jan, thanks Otto for the personal mail.

Yes, the problem is sure that. I will se with the provider.

When I changed the fdisk partition (first writes), they were not written,
but the disklabel. When I did not, but changed the disklabel, then the
disklabel was not changed. I hope enough dmesg is written before KARL!!!

Rodrigo

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

[Jeremy Evans]

On Thu, May 23, 2019 at 5:37 AM  wrote:

> 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 have also experienced this, though in my case the issue appeared to be
isolated to a single site (which started working correctly after
restarting).  I'm considering downgrading squid locally to the version that
shipped with 6.4 in order to work around the issue.

Jeremy

Re: Installer buggy (Re: OpenBSD on VMware ESXi)

[Jan Vlach]

> On Thu, 23 May 2019, Jan Vlach wrote:
> 
> > IIRC, pvscsi used to eat up first write to the paravirtual storage
> > device with VMware. Not sure what's the current situation as I tend to
> > use LSI Logic SAS.
> 
> I do not understand very much, but yes, something is being eaten up.
> 
> The fsck I mentioned before was not effective, I landed with a system
> with ro mounted root system. It was impossible to do anything reasonable
> with it.
> 
> pci3 at ppb2 bus 3
> vmwpvs0 at pci3 dev 0 function 0 "VMware PVSCSI" rev 0x02: apic 1 int 18
^^
https://marc.info/?l=openbsd-misc=144899602327183=2

I think you're seeing this. Change the Storage adapter in VMware to LSI
Logic SAS or ask your VM provider to do this for you.

JV

Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)

[Ian Darwin]

On 5/23/19 7:51 AM, Roderick wrote:

I wonder that no one noted this bugs before: are there no new people
installing OpenBSD? Or it is a problem only with VMWare?


Yes, the fact that nobody else has run into your problem suggest that it 
might in fact be your problem. Or your provider may be doing something 
strange.


It's great that you are exploring this, and may yet find an actual 
issue, 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.

Re: Installer buggy (Re: OpenBSD on VMware ESXi)

[Roderick]

On Thu, 23 May 2019, Jan Vlach wrote:


IIRC, pvscsi used to eat up first write to the paravirtual storage
device with VMware. Not sure what's the current situation as I tend to
use LSI Logic SAS.


I do not understand very much, but yes, something is being eaten up.

The fsck I mentioned before was not effective, I landed with a system
with ro mounted root system. It was impossible to do anything reasonable
with it.

I booted bsd.rd and did fsck /dev/rsd0a: tice!!!
The first one did not mark it as clean.

And now, I boot, but do not get a compleete /var/run/dmesg.boot for
Tom Smyth. Below is all what I get.

It seems, it was not the installer. :)

Any idea how to continue? How to get the ESXi version?

Thanks
Rodrigo






v 0x00
vga1: aperture needed
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
ppb1 at pci0 dev 17 function 0 "VMware PCI" rev 0x02
pci2 at ppb1 bus 2
ahci0 at pci2 dev 0 function 0 "VMware AHCI" rev 0x00: apic 1 int 18, AHCI 1.3
ahci0: port 0: 6.0Gb/s
scsibus0 at ahci0: 32 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom 
removable
ppb2 at pci0 dev 21 function 0 "VMware PCIE" rev 0x01
pci3 at ppb2 bus 3
vmwpvs0 at pci3 dev 0 function 0 "VMware PVSCSI" rev 0x02: apic 1 int 18
scsibus1 at vmwpvs0: 16 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI4 0/direct fixed 
naa.6000c290fd42ddbb45acd19e285b95bf
sd0: 20480MB, 512 bytes/sector, 41943040 sectors
ppb3 at pci0 dev 21 function 1 "VMware PCIE" rev 0x01
pci4 at ppb3 bus 4
ppb4 at pci0 dev 21 function 2 "VMware PCIE" rev 0x01
pci5 at ppb4 bus 5
ppb5 at pci0 dev 21 function 3 "VMware PCIE" rev 0x01
pci6 at ppb5 bus 6
ppb6 at pci0 dev 21 function 4 "VMware PCIE" rev 0x01
pci7 at ppb6 bus 7
ppb7 at pci0 dev 21 function 5 "VMware PCIE" rev 0x01
pci8 at ppb7 bus 8
ppb8 at pci0 dev 21 function 6 "VMware PCIE" rev 0x01
pci9 at ppb8 bus 9
ppb9 at pci0 dev 21 function 7 "VMware PCIE" rev 0x01
pci10 at ppb9 bus 10
ppb10 at pci0 dev 22 function 0 "VMware PCIE" rev 0x01
pci11 at ppb10 bus 11
vmx0 at pci11 dev 0 function 0 "VMware VMXNET3" rev 0x01: apic 1 int 19, 
address 00:50:56:0a:ad:be
ppb11 at pci0 dev 22 function 1 "VMware PCIE" rev 0x01
pci12 at ppb11 bus 12
ppb12 at pci0 dev 22 function 2 "VMware PCIE" rev 0x01
pci13 at ppb12 bus 13
ppb13 at pci0 dev 22 function 3 "VMware PCIE" rev 0x01
pci14 at ppb13 bus 14
ppb14 at pci0 dev 22 function 4 "VMware PCIE" rev 0x01
pci15 at ppb14 bus 15
ppb15 at pci0 dev 22 function 5 "VMware PCIE" rev 0x01
pci16 at ppb15 bus 16
ppb16 at pci0 dev 22 function 6 "VMware PCIE" rev 0x01
pci17 at ppb16 bus 17
ppb17 at pci0 dev 22 function 7 "VMware PCIE" rev 0x01
pci18 at ppb17 bus 18
ppb18 at pci0 dev 23 function 0 "VMware PCIE" rev 0x01
pci19 at ppb18 bus 19
ppb19 at pci0 dev 23 function 1 "VMware PCIE" rev 0x01
pci20 at ppb19 bus 20
ppb20 at pci0 dev 23 function 2 "VMware PCIE" rev 0x01
pci21 at ppb20 bus 21
ppb21 at pci0 dev 23 function 3 "VMware PCIE" rev 0x01
pci22 at ppb21 bus 22
ppb22 at pci0 dev 23 function 4 "VMware PCIE" rev 0x01
pci23 at ppb22 bus 23
ppb23 at pci0 dev 23 function 5 "VMware PCIE" rev 0x01
pci24 at ppb23 bus 24
ppb24 at pci0 dev 23 function 6 "VMware PCIE" rev 0x01
pci25 at ppb24 bus 25
ppb25 at pci0 dev 23 function 7 "VMware PCIE" rev 0x01
pci26 at ppb25 bus 26
ppb26 at pci0 dev 24 function 0 "VMware PCIE" rev 0x01
pci27 at ppb26 bus 27
ppb27 at pci0 dev 24 function 1 "VMware PCIE" rev 0x01
pci28 at ppb27 bus 28
ppb28 at pci0 dev 24 function 2 "VMware PCIE" rev 0x01
pci29 at ppb28 bus 29
ppb29 at pci0 dev 24 function 3 "VMware PCIE" rev 0x01
pci30 at ppb29 bus 30
ppb30 at pci0 dev 24 function 4 "VMware PCIE" rev 0x01
pci31 at ppb30 bus 31
ppb31 at pci0 dev 24 function 5 "VMware PCIE" rev 0x01
pci32 at ppb31 bus 32
ppb32 at pci0 dev 24 function 6 "VMware PCIE" rev 0x01
pci33 at ppb32 bus 33
ppb33 at pci0 dev 24 function 7 "VMware PCIE" rev 0x01
pci34 at ppb33 bus 34
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
softraid0 at root
scsibus2 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
syncing disks... done
rebooting...
OpenBSD 6.4 (GENERIC) #926: Thu Oct 11 13:43:06 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem  = 536227840 (511MB)
avail mem = 511414272 (487MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 09/19/18, BIOS32 rev. 0 @ 0xfd780, SMBIOS rev. 2.7 @ 
0xe0010 (620 entries)
bios0: vendor Phoenix Technologies LTD version "6.00" date 09/19/2018
bios0: VMware, Inc. VMware Virtual Platform
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3) 
S16F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) S1F0(S3) 
PE50(S3) S1F0(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits

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

[wrh]

Hello,

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.

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
The file descriptor given is always squid's main listening socket:
18 Socket0   00  0.0.0.0:3128  HTTP Socket

Approx 120 clients using this system as their proxy.

Once this error hits, then web clients fail and squid needs to be restarted
to restore operation.


At first I had an LACP based trunk with the system's two em interfaces,
which I thought might be causing the issue (my first time using trunk).  So
I switched to using the single bge interface but the errors still occur.


Can anyone suggest what I should be looking at to find the cause?

Thank you.


# netstat -in
NameMtu   Network Address  Ipkts IfailOpkts Ofail
Colls
lo0 32768   66 0   66 0
  0
lo0 32768 ::1/128 ::1 66 0   66 0
  0
lo0 32768 fe80::%lo0/ fe80::1%lo0 66 0   66 0
  0
lo0 32768 127/8   127.0.0.1   66 0   66 0
  0
bge01500d4:ae:52:c1:07:f2 32563772 0 34912639 0
  0
bge01500  172.16.1/24 172.16.1.16   32563772 0 34912639 0
  0
em0*150000:1b:21:5e:06:410 00 0
  0
em1*150000:1b:21:5e:06:850 00 0
  0
enc0*   00 00 0
  0
pflog0  331360 00 0
  0

# netstat -m
820 mbufs in use:
408 mbufs allocated to data
396 mbufs allocated to packet headers
16 mbufs allocated to socket names and addresses
398/1328 mbuf 2048 byte clusters in use (current/peak)
0/60 mbuf 2112 byte clusters in use (current/peak)
0/200 mbuf 4096 byte clusters in use (current/peak)
0/144 mbuf 8192 byte clusters in use (current/peak)
0/42 mbuf 9216 byte clusters in use (current/peak)
0/60 mbuf 12288 byte clusters in use (current/peak)
0/48 mbuf 16384 byte clusters in use (current/peak)
0/8 mbuf 65536 byte clusters in use (current/peak)
6452/7796/524288 Kbytes allocated to network (current/peak/max)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines


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 = 12865998848 (12269MB)
avail mem = 12466450432 (11888MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0450 (77 entries)
bios0: vendor Dell Inc. version "A16" date 07/06/2012
bios0: Dell Inc. Precision WorkStation T3500
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET TCPA DMAR SLIC SSDT
acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI1(S5) PCI2(S5) PCI3(S5) PCI4(S5)
PCI5(S5) PCI6(S5) KBD_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3)
USB5(S3)
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 W3565 @ 3.20GHz, .80 MHz, 06-1a-05
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 133MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU W3565 @ 3.20GHz, .28 MHz, 06-1a-05
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,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) Xeon(R) CPU W3565 @ 3.20GHz, .28 MHz, 06-1a-05
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,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) Xeon(R) CPU W3565 @ 3.20GHz, .28 MHz, 06-1a-05
cpu3:

Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)

[Arnaud BRAND]

The web console copy/paste functionnality is a VMWare limitation.
I don't think it ever worked.
It think would require the console to emulate/simulate key presses
depending on what is pasted and somehow assuming what the VM keymap is.

I didn't try to install 6.5 on ESXI yet, but I definitely installed 6.4.
On a lot of ESXi versions from 5.5 to 6.7.
So you could try to install 6.4 to see if you have the same problems ?

Never experienced your problems, although I experienced some strange
behaviors with disklabeling (if I remember well sometimes it couldn't
install the bootloader or wouldn't boot after install).

They were resolved by :
- dropping to the shell at the start of the install
- fdisk -i 
- return to the install and proceed normally

Never tried to install a custom label on ESXi, but did it sucessfully
on virtualbox with 6.5 without any issue (not even needed to fdisk -i).

What ESXi version are you running ?
What disk controller are you showing to OpenBSD ?

AB

Le 2019-05-23 12:17, Roderick a écrit :

On Thu, 23 May 2019, Otto Moerbeek wrote:


You must be doing something wrong. Since it installer surely leats you
use a custom label. But since you are not showgin waht you did and you
start insulting remarks, you won't get much help.


Excuse me, although my words was not flowers, they were no insult.
And there was no intention to insult, but it is realy nerving to deal
with this web console. I cannot even do "copy and paste" in it for
showing what I did. That is why I described it. It is sure a bug there.
As said: it is not my previous experience with OpenBSD.

There is sure a bug there:

(1) if you installed a label before, the installer does not offer
it to you.

(2) it changes the "custom label" you write in the process. Really
changes it. That can never be something else than a bug.

(3) "disklabel -E /dev/sd0" puts alway cpg=1. The installer in
the autoinstall puts numbers like 10277, 16384.

Rodrigo

Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)

[Tom Smyth]

include a copy of dmesg
and you might get info about the virtual hardware / hypervisor you
are running on


On Thu, 23 May 2019 at 12:58, Roderick  wrote:

>
> On Thu, 23 May 2019, Arnaud BRAND wrote:
>
> > So you could try to install 6.4 to see if you have the same problems ?
>
> Just copied bsd.rd from 6.4 in the root of the running system and
> booted it. It was a litle better.
>
> My settings to fdisk, namely change of offset from 64 to 2048, were
> ignored, and so the automatic disklabel offered an offset of 64.
>
> My settings to disklabel were this time not ignored.
>
> I will proceed to do "fdisk -i", perhaps reinstall, perhaps not.
>
> The changing of the offset from 64 to 2048 did help: after a "hardware
> shutdown" I got again a bootable system, although a fsck is necessary.
>
> I wonder that no one noted this bugs before: are there no new people
> installing OpenBSD? Or it is a problem only with VMWare?
>
> > What ESXi version are you running ?
>
> No idea. I must ask the hoster.
>
> > What disk controller are you showing to OpenBSD ?
>
> sd0
>
> Thanks
> Rodrigo
>
>

-- 
Kindest regards,
Tom Smyth.

Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)

[Roderick]

On Thu, 23 May 2019, Arnaud BRAND wrote:


So you could try to install 6.4 to see if you have the same problems ?


Just copied bsd.rd from 6.4 in the root of the running system and
booted it. It was a litle better.

My settings to fdisk, namely change of offset from 64 to 2048, were
ignored, and so the automatic disklabel offered an offset of 64.

My settings to disklabel were this time not ignored.

I will proceed to do "fdisk -i", perhaps reinstall, perhaps not.

The changing of the offset from 64 to 2048 did help: after a "hardware
shutdown" I got again a bootable system, although a fsck is necessary.

I wonder that no one noted this bugs before: are there no new people
installing OpenBSD? Or it is a problem only with VMWare?


What ESXi version are you running ?


No idea. I must ask the hoster.


What disk controller are you showing to OpenBSD ?


sd0

Thanks
Rodrigo

Re: Installer buggy (Re: OpenBSD on VMware ESXi)

[Jan Vlach]

Hi Rodrigo,

IIRC, pvscsi used to eat up first write to the paravirtual storage
device with VMware. Not sure what's the current situation as I tend to
use LSI Logic SAS.

Also, the first eaten-up write would explain why you're still seeing
Linux partitions instead of OpenBSD.


# fdisk sd0
Disk: sd0   geometry: 14593/255/63 [234441648 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: 00  0   0   0 -  0   0   0 [   0:   0 ]
unused
 1: 00  0   0   0 -  0   0   0 [   0:   0 ]
unused
 2: 00  0   0   0 -  0   0   0 [   0:   0 ]
unused
*3: A6  0   1   2 -  14592 254  63 [  64:   234436481 ]
OpenBSD

jvl

P.S. Description or even screenshots would help to know where you got
stuck.

Re: amdgpu report on rx460

[Oriol Demaria]

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?


---
Oriol Demaria
2FFED630C16E4FF8

On 23/05/2019 03:56, Peter Piwowarski wrote:
I've tried the new amdgpu driver on my RX460 (4G VRAM), and it seems to 
work
reasonably. KMS picks up the appropriate console resolution, and X 
appears to

work. There is some strange behavior with xrandr when setting rotation
on one of
my displays (1920x1200->1200x1920) that I don't quite understand; its 
idea of

the mouse pointer's position seems to be confused. Changing virtual
desktop size
by disabling displays outright doesn't seem to cause any problems. I 
can play
with it more and report further if that information would be helpful. 
OpenGL
seems to work, but not entirely correctly. I only had time today to 
test
glxgears (fine) and 0ad (some obvious artifacts, and doesn't quite 
reach 60fps
at 1920x1200 as it should be able to, presumably has something to do 
with the
powerplay error visible in dmesg; images available on request. I also 
see
display corruption in my xterms after exiting, which is resolved by 
restarting
X). dmesg quickly fills up with stub messages upon starting X, but I 
assume
that's known. :) If there's anything I can test on this hardware to 
assist

development, I'm happy to do so. dmesg without X, post fw_update:

OpenBSD 6.5-current (GENERIC.AMDGPU.MP) #0: Wed May 22 19:51:55 EDT 
2019


pe...@shoebox-kvm-openbsd-current.foo:/usr/src/sys/arch/amd64/compile/GENERIC.AMDGPU.MP
real mem = 17111023616 (16318MB)
avail mem = 16579829760 (15811MB)
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.87 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:
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
cpu2: 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
cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully 
associative
cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully 
associative

cpu2: smt 0, core 1, package 

Re: Installer buggy (Re: OpenBSD on VMware ESXi)

[Roderick]

Some more details about my experience. Excuseme that I dont take
fotos of the screen and just describe, with the data y wrote down.

As I wrote, yesterday my instalation did not work. Today morning
I began to inspect with the shell of cd65.iso the partitions.

fdisk gave me  41943040 sectors divided as follows:

  startsize
0*  2048 997376  Linux files
1 999424   40943616  Linux LVM

disklabel gave me the sizes I typed:

a   409600   0   4.2BSD
b  1048576   409600  swap
c 41943040   0
e 40484864  1458176  4.2BSD

you see there the offset zero, no MBR. That is why the system did not
boot. I went to the shell and did "fdisk -iy sd0". Now I have a partition
3 with the whole, 64 till 41942976. I started the installer and
got an installation, as described, only with the automatic set values.

The server hoster offers two kinds of shutting down the system by
clicking on their web plattform: software and hardware. If I restart
with "hardware", the system does not go up anymore, unless I reinstall
the whole system. I though the hoster spoiled my disk because it
writes in the first 2048 sectors. I went to install again, but with
an offset of 2048 in the OpenBSD fdisk partition: no way, the installer
ignores my settings.

Rodrigo

Re: Modern browser for OpenBSD powerpc

[ropers]

Thanks for sharing, and if you know a way to administer and use all
the functionality of Gmail without ever logging into Gmail's web
interface, let me know.

On 23/05/2019, Craig Skinner  wrote:
> On Thu, 23 May 2019 11:25:12 +0200 ropers wrote:
>> OP has a Gmail address, 
>
> Which works with an IMAP client, such as claws-mail.
>
> Web is not mail.
>
> Cheers,
> --
> Craig Skinner | http://linkd.in/yGqkv7
>
>

Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)

[Roderick]

On Thu, 23 May 2019, Otto Moerbeek wrote:


You must be doing something wrong. Since it installer surely leats you
use a custom label. But since you are not showgin waht you did and you
start insulting remarks, you won't get much help.


Excuse me, although my words was not flowers, they were no insult.
And there was no intention to insult, but it is realy nerving to deal
with this web console. I cannot even do "copy and paste" in it for
showing what I did. That is why I described it. It is sure a bug there.
As said: it is not my previous experience with OpenBSD.

There is sure a bug there:

(1) if you installed a label before, the installer does not offer
it to you.

(2) it changes the "custom label" you write in the process. Really
changes it. That can never be something else than a bug.

(3) "disklabel -E /dev/sd0" puts alway cpg=1. The installer in
the autoinstall puts numbers like 10277, 16384.

Rodrigo

Re: Modern browser for OpenBSD powerpc

[Craig Skinner]

On Thu, 23 May 2019 11:25:12 +0200 ropers wrote:
> OP has a Gmail address, 

Which works with an IMAP client, such as claws-mail.

Web is not mail.

Cheers,
-- 
Craig Skinner | http://linkd.in/yGqkv7

how to setup wireless for redundent firewalls ?

[shadrock uhuru]

hi everyone
i have two firewalls setup with carp and pfsync
with my wireless router fed straight into the switch connected to the lan ,
this is fine for me as a single user of my network.
i would like to improve the setup to include other users while allowing
them  access to the internet and limiting their access to my network.
i will be adding another network port  to both firewalls ,
i assume i will need to have two wireless routers,
one plugged into each firewall,
are the two wireless routers setup to have
the same ssid and password for smooth fail-over ?

shadrock

Re: Installer sucks ! (Re: OpenBSD on VMware ESXi)

[Otto Moerbeek]

On Thu, May 23, 2019 at 08:42:05AM +, Roderick wrote:

> 
> Please, delete the cc to b...@openbsd.org in any answer.
> 
> I am now, after hours typing in the damned web console and dealing
> with the buggy installer, a little bit furious. This is definitively
> not the OpenBSD I know!
> 
> I did manage to install OpenBSD in VMWare, with the "autopartition", but I
> want a custom partition due to my spare resources. I will now do a pause to
> calm myself and then continue trying. I appreciate any hint
> and thank for it very much.

You must be doing something wrong. Since it installer surely leats you
use a custom label. But since you are not showgin waht you did and you
start insulting remarks, you won't get much help.


> My remarks:
> 
> (1) There no way to write a custom disklabel. After doing it, after giving the
> command w and leaving with x, or after leaving with q, the installer
> overwrites it with something arbitrary that may be unusable (then
> one will note it no later than when loading the sets due to error
> "cannot determine prefetch ...").OA

see above

> 
> (2) "disklabel -E" in cd65.iso puts a cpg=1 for all partitions: is that
>  correct?

yes. The cpg field is used for some redundant fs metadata these days
and will be filled in by newfs.

> 
> (4) No way to leave the disklabel as it is. I wrote one with the shell
> of cd65.iso (and cpg=1), also did nefwfs on the partitions, but
> the installer do not show the partition it anywhere. One is compelled
> to type again, and again comes the unusable arbitrary modification.

see above

> 
> (5) Auto allocaton puts partitions for X11 even if one selects
> that one will run no X11.

You can easily edit the auto label and delete partitions you do not want.

> 
> (6) No vi in cd65.iso (but at least ed).
> 
> Rodrigo
> 

Re: Modern browser for OpenBSD powerpc

[ropers]

On 23/05/2019, Jordan Geoghegan  wrote:
>
> On 5/22/19 11:19 PM, John Gould wrote:
>> Can someone suggest a modern graphical browser for OpenBSD PowerPC?
>
> Dillo is a pretty good browser that works on macppc. It doesn't support
> javascript, but is perfectly adequate for reading non-terrible websites.

( By your definition, almost *all* websites are terrible today (not
that I necessarily disagree). I don't know what percentage of websites
don't include or require JavaScript, but it's got to be in the single
digits now. A non-JavaScript browser cannot honestly claim to be
modern anymore. )

OP has a Gmail address, and while there *is* a plain HTML version of
Gmail that *doesn't* require JavaScript, Google *does* require
JavaScript to sign you in (:facepalm:). So even if you enable cookies,
which Dillo disables by default, see man dillo, you will still hit a
stupid and arbitrary roadblock. If anyone knows how to sign in and
access  without JavaScript (with
Dillo), I'd be interested in hearing about that.

I also have some minor cosmetic client-side Stylish fixes for basic
HTML Gmail that I could post if people were interested. This is
getting pretty OT, but if people want to hear it, giz a shout.

Installer sucks ! (Re: OpenBSD on VMware ESXi)

[Roderick]

Please, delete the cc to b...@openbsd.org in any answer.

I am now, after hours typing in the damned web console and dealing
with the buggy installer, a little bit furious. This is definitively
not the OpenBSD I know!

I did manage to install OpenBSD in VMWare, with the "autopartition", but 
I want a custom partition due to my spare resources. I will now do a 
pause to calm myself and then continue trying. I appreciate any hint

and thank for it very much.

My remarks:

(1) There no way to write a custom disklabel. After doing it, after giving the
command w and leaving with x, or after leaving with q, the installer
overwrites it with something arbitrary that may be unusable (then
one will note it no later than when loading the sets due to error
"cannot determine prefetch ...").

(2) "disklabel -E" in cd65.iso puts a cpg=1 for all partitions: is that
 correct?

(4) No way to leave the disklabel as it is. I wrote one with the shell
of cd65.iso (and cpg=1), also did nefwfs on the partitions, but
the installer do not show the partition it anywhere. One is compelled
to type again, and again comes the unusable arbitrary modification.

(5) Auto allocaton puts partitions for X11 even if one selects
that one will run no X11.

(6) No vi in cd65.iso (but at least ed).

Rodrigo

Re: Modern browser for OpenBSD powerpc

[Antal Ispanovity]

2019-05-23 8:19 GMT+02:00, John Gould :
> Can someone suggest a modern graphical browser for OpenBSD PowerPC?
epiphany, if you need JS

> I'm trying to run
> several G5's and g4 mini's on 6.5 as desktop machines. The basic
> install works really well but there doesn't seem to be an up to date
> graphically browser.
>
> It's thanks to all the work the devs have put into OpenBSD powerpc
> that these machine are still very usable. They are hopelessly out of
> date as far as the Mac OS are concerned!
>
> Kind regards John.
>
>

Re: Modern browser for OpenBSD powerpc

[Dumitru Moldovan]

On Thu, May 23, 2019 at 07:19:25AM +0100, John Gould wrote:

Can someone suggest a modern graphical browser for OpenBSD PowerPC?
I'm trying to run
several G5's and g4 mini's on 6.5 as desktop machines. The basic
install works really well but there doesn't seem to be an up to date
graphically browser.

It's thanks to all the work the devs have put into OpenBSD powerpc
that these machine are still very usable. They are hopelessly out of
date as far as the Mac OS are concerned!


Try netsurf, it's the best one I've found in the 6.4 macppc packages.
There is substantial progress in porting for macppc in 6.5, haven't
tried the new release, but it seems it hasn't resulted in a better
graphical web browser yet.

Re: Modern browser for OpenBSD powerpc

[Jordan Geoghegan]

On 5/22/19 11:19 PM, John Gould wrote:

Can someone suggest a modern graphical browser for OpenBSD PowerPC?


Dillo is a pretty good browser that works on macppc. It doesn't support 
javascript, but is perfectly adequate for reading non-terrible websites.

Modern browser for OpenBSD powerpc

[John Gould]

Can someone suggest a modern graphical browser for OpenBSD PowerPC?
I'm trying to run
several G5's and g4 mini's on 6.5 as desktop machines. The basic
install works really well but there doesn't seem to be an up to date
graphically browser.

It's thanks to all the work the devs have put into OpenBSD powerpc
that these machine are still very usable. They are hopelessly out of
date as far as the Mac OS are concerned!

Kind regards John.