From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9CADB138359 for ; Wed, 8 Jul 2020 13:48:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C50B4E080E; Wed, 8 Jul 2020 13:48:48 +0000 (UTC) Received: from ciao.gmane.io (static.214.254.202.116.clients.your-server.de [116.202.254.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 85EE5E07D8 for ; Wed, 8 Jul 2020 13:48:48 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jtARL-0006MP-3N for gentoo-user@lists.gentoo.org; Wed, 08 Jul 2020 15:48:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Grant Edwards Subject: [gentoo-user] Re: SSH xterm not working properly during install Date: Wed, 8 Jul 2020 13:48:42 -0000 (UTC) Message-ID: References: <20200708020225.GB27227@waltdnes.org> User-Agent: slrn/1.0.3 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: d03d98d4-039d-48aa-9882-6ee1a0256077 X-Archives-Hash: 555193f86c1df2c742d1ddfb05b565b2 On 2020-07-08, Walter Dnes wrote: > Today I decided to ssh into the install, and cut + paste stuff into > an ssh xterm into the install. This went flying along really fast > until I went to emerge after having updated make.conf. I got a slew > of weird errors. 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. > It turns out that make.conf was majorly butchered after I had done > some "simple" edits over ssh. This seems to be a terminfo problem, so > it may apply to more than just nano. -- Grant