1 |
On Wed, Jul 08, 2020 at 03:42:29PM -0400, Walter Dnes wrote |
2 |
|
3 |
> As I mentioned in another post, the "toe" command shows which TERM |
4 |
> types you terminal supports. xterm (the app) doesn't support "linux" |
5 |
> TERM type. The solution was to set TERM to "xterm" at both ends. |
6 |
> Basically, run "toe" on both machines and find a common entry that they |
7 |
> both support. |
8 |
|
9 |
I've got a bootable install running... yay! There's still some setup |
10 |
to do, but I can handle it from my desktop. One thing I might forward |
11 |
to the maintainers as a documentation bug/suggestion... |
12 |
|
13 |
If you're doing a remote install via ssh, *BEFORE THE REBOOT* run |
14 |
"ssh-keygen" on the install target, and then... |
15 |
|
16 |
scp ~/.ssh/id_rsa.pub root@<install_target>:/mnt/gentoo/root/.ssh/authorized_keys |
17 |
|
18 |
This allows a root connection from your machine to the target machine, |
19 |
so that you're not locked out <G>. In my case, I only had to walk a few |
20 |
steps to the laptop, run ssh-keygen, edit /etc/ssh/sshd.config, restart |
21 |
sshd, and login manually via ssh. If you're doing a really remote |
22 |
install, it could be embarressing. After uploading my key, I've changed |
23 |
sshd.config back and restarted sshd. |
24 |
|
25 |
-- |
26 |
Walter Dnes <waltdnes@××××××××.org> |
27 |
I don't run "desktop environments"; I run useful applications |