fatal: Fssh_packet_write_poll: Connection from xxx.xxx.xx.xx port yyyyy: Permission denied

Hi, all I've updated to HEAD(r308871) at 2 days ago, and also ports too(r426562). Then all stuffs including applications have been updated and tried to slogin to this host,but can't connect with the message `userauth_pubkey: key type ssh-dss not in PubkeyAcceptedKeyTypes [preauth]' in

Re: tput failing on 10 and 12 systems?

On 22/11/2016 12:49 AM, Adrian Chadd wrote: Hiya, Just to follow through - part of tput is to decode command args, but it then just requests it from the ncurses tputs() call. So it could be tput, but it could also be the BSD ncurses work.

Re: tput failing on 10 and 12 systems?

On 22/11/2016 12:49 AM, Adrian Chadd wrote: Hiya, Just to follow through - part of tput is to decode command args, but it then just requests it from the ncurses tputs() call. So it could be tput, but it could also be the BSD ncurses work. but the ncurses stuff works for things like vim

Re: tput failing on 10 and 12 systems?

Hiya, Just to follow through - part of tput is to decode command args, but it then just requests it from the ncurses tputs() call. So it could be tput, but it could also be the BSD ncurses work. -adrian On 21 November 2016 at 07:54, Julian Elischer wrote: > example on

tput failing on 10 and 12 systems?

example on freefall (FreeBSD 12.0-CURRENT #0 r306376) julian@freefall:tput setaf 4|od -c 000 033 [ m 003 so nothing happens, and tput returns 1. but on a FreeBSD 8 system: [jelischer@alpha ~]$ tput setaf 4|od -c 000 033 [ 3 4 m 005 which make the text change

Re: a dirty trick: i386 nanobsd ports on amd64

On 21/11/2016 04:44, Poul-Henning Kamp wrote: I ran into a interesting problem, and want to share the solution, in case anybody else can use it. I'm upgrading a system which used to be i386 to amd64, but part of its job is to compile i386 nanobsd images. That's a solved problem, but I also