Re: openssl in head returning "certificate expired" when it has not expired

2021-02-01 Thread Benjamin Kaduk
On Tue, Feb 02, 2021 at 03:48:06AM +, Rick Macklem wrote: > Benjamin Kaduk wrote: > >On Tue, Feb 02, 2021 at 12:46:25AM +, Rick Macklem wrote: > >> I've recently been testing the daemons that do the > >> non-application data stuff for nfs-over-tls with the > >> openssl in head. > >> > >> Th

Re: openssl in head returning "certificate expired" when it has not expired

2021-02-01 Thread Rick Macklem
Benjamin Kaduk wrote: >On Tue, Feb 02, 2021 at 12:46:25AM +, Rick Macklem wrote: >> I've recently been testing the daemons that do the >> non-application data stuff for nfs-over-tls with the >> openssl in head. >> >> These daemons work fine with both ports/security/openssl (openssl-1.1.1h) >> a

Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

2021-02-01 Thread Yasuhiro Kimura
From: Toomas Soome via freebsd-current Subject: Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3 Date: Tue, 2 Feb 2021 00:35:49 +0200 > Should be fixed on current now. Confirmed. Would you please MFC to stable/13? Best Regards. --- Y

Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread Rodney W. Grimes
On some day Glen Barber wrote: > On Mon, Feb 01, 2021 at 09:38:33PM +, tech-lists wrote: > > On Mon, Feb 01, 2021 at 09:27:44PM +, Glen Barber wrote: > > > On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote: > > > > Found > > > > A pre-built version of pkg could not be found for you

Re: How to setup ZFS mirrored boot device

2021-02-01 Thread joe mcguckin
I did a scrub, it finished within 30 seconds. But the error was that it could not find the boot device it was looking for. I’ve seen this before: If you create a boot device in slot 0 (gets named da0) then move that drive to a different slot, FreeBSD will fail in the same manner. Joe McGuckin

Re: openssl in head returning "certificate expired" when it has not expired

2021-02-01 Thread Benjamin Kaduk
On Tue, Feb 02, 2021 at 12:46:25AM +, Rick Macklem wrote: > I've recently been testing the daemons that do the > non-application data stuff for nfs-over-tls with the > openssl in head. > > These daemons work fine with both ports/security/openssl (openssl-1.1.1h) > and ports/security/openssl-de

openssl in head returning "certificate expired" when it has not expired

2021-02-01 Thread Rick Macklem
I've recently been testing the daemons that do the non-application data stuff for nfs-over-tls with the openssl in head. These daemons work fine with both ports/security/openssl (openssl-1.1.1h) and ports/security/openssl-devel (openssl3-alpha). However, when linked to the openssl in head, the ba

Re: How to setup ZFS mirrored boot device

2021-02-01 Thread Tim Rice
On 2/1/21 3:56 PM, joe mcguckin wrote: > I tried this but it’s not quite working. > > LSI controller flashed with IT firmware. > > 2) 1T SSD drives > > During the install process, I select to create a mirrored ZFS root. It > appears to be created > and there is a zroot dataset. zpool status sho

How to setup ZFS mirrored boot device

2021-02-01 Thread joe mcguckin
I tried this but it’s not quite working. LSI controller flashed with IT firmware. 2) 1T SSD drives During the install process, I select to create a mirrored ZFS root. It appears to be created and there is a zroot dataset. zpool status shows everythings ok. Now it gets interesting: I pull one

Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

2021-02-01 Thread Toomas Soome via freebsd-current
> On 1. Feb 2021, at 05:35, Yasuhiro Kimura wrote: > > From: Yasuhiro Kimura mailto:y...@utahime.org>> > Subject: Setting for displaying utf8 characters on all vt consoles results in > panic on 14-CURRENT and 13.0-ALPHA3 > Date: Mon, 01 Feb 2021 11:41:35 +0900 (JST) > >> To display utf8 chara

Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread Glen Barber
On Mon, Feb 01, 2021 at 09:38:33PM +, tech-lists wrote: > On Mon, Feb 01, 2021 at 09:27:44PM +, Glen Barber wrote: > > On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote: > > > Found > > > A pre-built version of pkg could not be found for your system. > > > Consider changing PACKAGE

Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread tech-lists
On Mon, Feb 01, 2021 at 09:27:44PM +, Glen Barber wrote: On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote: Found A pre-built version of pkg could not be found for your system. Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'. root@generic:/usr/src/releas

Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread Glen Barber
On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote: > Hello, > > I also tried to build a release and failed. My context is different to > yours, though. The failure error is different. Just thought I'd mention > it as "make release on -current is broken for me as well". In my > context, it

Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-02-01 Thread Glen Barber
On Sun, Jan 31, 2021 at 04:29:09PM +0900, Yasuhiro Kimura wrote: > Hello, > > I tried release build with /usr/src/release/release.sh on 14-CURRENT > amd64 under followin conditions. > > * 14-CURRENT amd64 > * f17fc5439f5 + revert of 84eaf2ccc6a (Workaroud of the problem > reported as bug 253087

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-02-01 Thread Guido Falsi via freebsd-current
On 01/02/21 04:24, Rick Macklem wrote: Rick Macklem wrote: Guido Falsi wrote: [good stuff snipped] Performed a full bisect. Tracked it down to commit aa906e2a4957, adding KTLS support to embedded OpenSSL. I filed a bug report about this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25313