Date: Thu, 13 Dec 2018 20:08:47 -0500 From: Jung-uk Kim <jkim@FreeBSD.org> To: Yuri Pankov <yuripv@yuripv.net>, current@freebsd.org Subject: Re: Whine: "Could not open /dev/crypto: No such file or directory" Message-ID: <e4db807a-653b-53b8-ea10-e82bd4edb600@FreeBSD.org> In-Reply-To: <65886b0d-75c6-fa18-2391-dfc1a0b51c41@yuripv.net> References: <20181213130138.GZ67514@albert.catwhisker.org> <65886b0d-75c6-fa18-2391-dfc1a0b51c41@yuripv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18. 12. 13., Yuri Pankov wrote: > David Wolfskill wrote: >> After update from r341844 to r342042, I see the above-cited "whine" when >> I attempt to use an SSH client on the upgraded machine. SSH client >> function seems OK, so the message is (apparently) merely annoying: >> >> freebeast(13.0-C)[2] uname -a >> FreeBSD freebeast.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT >> #403 r342042M/342042: Thu Dec 13 04:50:25 PST 2018 >> root@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC >> amd64 >> freebeast(13.0-C)[3] ssh albert hostname >> Could not open /dev/crypto: No such file or directory >> albert.catwhisker.org >> freebeast(13.0-C)[4] echo $? >> 0 >> freebeast(13.0-C)[5] > > It's r342009, and I followed up on that commit. r342057 should shut up the error message. https://svnweb.freebsd.org/changeset/base/342057 Jung-uk Kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e4db807a-653b-53b8-ea10-e82bd4edb600>