Re: [gentoo-user] [SOLVED] SSH xterm not working properly during install
On Wed, Jul 08, 2020 at 03:42:29PM -0400, Walter Dnes wrote > As I mentioned in another post, the "toe" command shows which TERM > types you terminal supports. xterm (the app) doesn't support "linux" > TERM type. The solution was to set TERM to "xterm" at both ends. > Basically, run "toe" on both machines and find a common entry that they > both support. I've got a bootable install running... yay! There's still some setup to do, but I can handle it from my desktop. One thing I might forward to the maintainers as a documentation bug/suggestion... If you're doing a remote install via ssh, *BEFORE THE REBOOT* run "ssh-keygen" on the install target, and then... scp ~/.ssh/id_rsa.pub root@:/mnt/gentoo/root/.ssh/authorized_keys This allows a root connection from your machine to the target machine, so that you're not locked out . In my case, I only had to walk a few steps to the laptop, run ssh-keygen, edit /etc/ssh/sshd.config, restart sshd, and login manually via ssh. If you're doing a really remote install, it could be embarressing. After uploading my key, I've changed sshd.config back and restarted sshd. -- Walter Dnes I don't run "desktop environments"; I run useful applications
[gentoo-user] [SOLVED] SSH xterm not working properly during install
On Wed, Jul 08, 2020 at 01:48:42PM -, Grant Edwards wrote > I've been installing Gentoo that way for almost 20 years and never had > a problem. I very rarely use xterm though -- I used aterm for years, > switched to rxvt, and then to urxvt. As I mentioned in another post, the "toe" command shows which TERM types you terminal supports. xterm (the app) doesn't support "linux" TERM type. The solution was to set TERM to "xterm" at both ends. Basically, run "toe" on both machines and find a common entry that they both support. -- Walter Dnes I don't run "desktop environments"; I run useful applications
[gentoo-user] [SOLVED] SSH xterm not working properly during install
On Tue, Jul 07, 2020 at 10:58:48PM -0600, Grant Taylor wrote > On 7/7/20 10:40 PM, Walter Dnes wrote: > > Thanks, I missed that. I'll try again and see how it goes. > > If you continue to have problems, I would very much like to know the > particulars. > > My experience has been that changing the TERM environment variable has > had very little success in fixing things like this. > > In fact, the only way that I see it working is if you are TERM is set to > something MASSIVELY wrong for your actual terminal. I.e. trying to send > fancy xterm / ANSI control sequences to an old dumb terminal like a VT100. Once you know what questions to ask, things become easier. Knowing that it was a TERM mismatch, a bit of googling turned up the "toe" command, which lists what your terminal supports. It looks like the install CD defaults to TERM="linux", which xterm (the app) doesn't support, according to "toe". Setting TERM on both ends to "xterm" solves the problem. -- Walter Dnes I don't run "desktop environments"; I run useful applications
