our best guess is that it's login the program which is doing that, it doesn'

our best guess is that it's login the program which is doing that, it doesn't seem like a thing sh would do

but regardless of what does it, it persists even after netbsd exits which is why bash was also messing up on the linux side

and we can fix it with just a quick tput reset in either OS