Re: Whine: "Could not open /dev/crypto: No such file or directory"
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 >> r...@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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Whine: "Could not open /dev/crypto: No such file or directory"
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 r...@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. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Whine: "Could not open /dev/crypto: No such file or directory"
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 r...@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] Peace, david -- David H. Wolfskill da...@catwhisker.org If POTUS nominates one who's "dumb as a rock" for Cabinet, who's at fault? See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
