Re: GPT autopartion during install

2021-02-18 Thread Sivan !
On Fri, 19 Feb 2021 at 13:14, Sivan ! wrote: > > In new desktop computer with a new ssd, the 6.8 amd installer during > auto partition without any user choices, created the numerous device > (partition)s, which is strange: > > For eg rsd0a-rsd0p ... rsd9a-rsd9p, ie 16x10=160 device partitions ?

GPT autopartion during install

2021-02-18 Thread Sivan !
In new desktop computer with a new ssd, the 6.8 amd installer during auto partition without any user choices, created the numerous device (partition)s, which is strange: For eg rsd0a-rsd0p ... rsd9a-rsd9p, ie 16x10=160 device partitions ? starting with rsd* ; Similarly numerous entries seen

OpenBSD VPN with Debian Buster Strongswan roadwarrior client

2021-02-18 Thread marfabastewart
If anyone else is configuring a VPN between an OpenBSD responder and a Debian Buster initiator with Strongswan on the Debian box, the following notes may spare you some pain. First, configure the OpenBSD responder using the FAQ and the X.509 Certificate Authentication section. A hearty thanks to

Re: using kevent to catch signals

2021-02-18 Thread Sebastien Marie
On Thu, Feb 18, 2021 at 10:23:05PM -0600, Edgar Pettijohn wrote: > I'm having trouble using kevent(2) to catch signals. Below is a sample > program. It should catch SIGHUP and SIGUSR1 and just print it out. > Instead when i send the process sighup with `kill -SIGHUP $PID` it > exits and the word

using kevent to catch signals

2021-02-18 Thread Edgar Pettijohn
I'm having trouble using kevent(2) to catch signals. Below is a sample program. It should catch SIGHUP and SIGUSR1 and just print it out. Instead when i send the process sighup with `kill -SIGHUP $PID` it exits and the word Hangup is writtin to the terminal. If I use `kill -SIGUSR1 $PID` the

Re: amdgpu unstable atm

2021-02-18 Thread rgc
On Fri, Feb 12, 2021 at 07:02:41PM +0900, rgc wrote: > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb 9 10:19:03 MST 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #328: Wed Feb 10 18:08:26 MST 2021 >

Re: Aspeed AST2400 integrated video supported?

2021-02-18 Thread Stuart Henderson
On 2021-02-18, Родин Максим wrote: > Hello > Is that type of video chip on server motherboard (Supermicro X11SSL) > supported? > > Yes

Re: 6.9-BETA Installer crash

2021-02-18 Thread Chris Zakelj
On 2/18/2021 1:07 PM, Stuart Henderson wrote: On 2021-02-18, Chris Zakelj wrote: On 2/18/2021 12:26 PM, Chris Cappuccio wrote: Chris Zakelj [c.zak...@ieee.org] wrote: Thought I'd try using the Dell and ARC-1200 combination with 6.9-BETA I mentioned a couple months ago

Re: 6.9-BETA Installer crash

2021-02-18 Thread Stuart Henderson
On 2021-02-18, Chris Zakelj wrote: > On 2/18/2021 12:26 PM, Chris Cappuccio wrote: >> Chris Zakelj [c.zak...@ieee.org] wrote: >>> Thought I'd try using the Dell and ARC-1200 combination with 6.9-BETA I >>> mentioned a couple months ago >>> (https://marc.info/?l=openbsd-misc=158259981320518), but

Aspeed AST2400 integrated video supported?

2021-02-18 Thread Родин Максим
Hello Is that type of video chip on server motherboard (Supermicro X11SSL) supported? -- Maksim Rodin

Re: 6.9-BETA Installer crash

2021-02-18 Thread Chris Zakelj
On 2/18/2021 12:26 PM, Chris Cappuccio wrote: Chris Zakelj [c.zak...@ieee.org] wrote: Thought I'd try using the Dell and ARC-1200 combination with 6.9-BETA I mentioned a couple months ago (https://marc.info/?l=openbsd-misc=158259981320518), but still no luck. Dmesg of both 6.9-BETA and verbose

Re: 6.9-BETA Installer crash

2021-02-18 Thread Chris Cappuccio
Chris Zakelj [c.zak...@ieee.org] wrote: > Thought I'd try using the Dell and ARC-1200 combination with 6.9-BETA I > mentioned a couple months ago > (https://marc.info/?l=openbsd-misc=158259981320518), but still no luck. > Dmesg of both 6.9-BETA and verbose FreeBSD 12.1-RELEASE attached in case >

Odd wget --timeout behaviour

2021-02-18 Thread Fabio Martins
Hi misc, Playing with wget I am getting an odd behaviour related to --timeout It takes about 7 minutes for the process to die inside a 6.9 VM (vmd) and 2 minutes in real hardware running 6.8, both with internet down but DNS resolving ok. to reproduce (with internet not connected): $ time

Re: tc= in remote(5) example

2021-02-18 Thread Theo de Raadt
Jan Stary wrote: > /etc/examples/remote contains the following stanzas: > > unixhost:\ > :br#9600: > > cua00|For i386,macppc:\ > :dv=/dev/cua00:tc=unixhost: > > cuaa|For sparc:\ > :dv=/dev/cuaa:tc=unixhost: > > > The remote(5)

Re: tc= in remote(5) example

2021-02-18 Thread trondd
On Thu, February 18, 2021 11:38 am, Jan Stary wrote: > /etc/examples/remote contains the following stanzas: > > unixhost:\ > :br#9600: > > cua00|For i386,macppc:\ > :dv=/dev/cua00:tc=unixhost: > > cuaa|For sparc:\ >

tc= in remote(5) example

2021-02-18 Thread Jan Stary
/etc/examples/remote contains the following stanzas: unixhost:\ :br#9600: cua00|For i386,macppc:\ :dv=/dev/cua00:tc=unixhost: cuaa|For sparc:\ :dv=/dev/cuaa:tc=unixhost: The remote(5) manpage describes br, dc, dv but not