1 |
[ This is my second try because the first time my e-mail address was |
2 |
not the subscribed address due to a bug. This means that Jan |
3 |
Kundrát's reply to this message may get threaded strangely or be |
4 |
missing. ] |
5 |
|
6 |
Jan Kundrát <jkt@g.o> writes: |
7 |
|
8 |
> Joe Wells wrote: |
9 |
>> The best solution to this that I can think of is to extend OpenSSH |
10 |
>> with the capability to copy terminfo information to ~/.terminfo on the |
11 |
>> remote system. |
12 |
> |
13 |
> IMHO automated overwriting files in $HOME on every login is a *very* bad |
14 |
> thing. |
15 |
|
16 |
Hi, Jan! |
17 |
|
18 |
In reply, my first question is: What makes you think files would be |
19 |
overwritten? These would be new files. Look at how the terminfo |
20 |
database is structured. Adding a new terminal description is done by |
21 |
adding a new file (possibly in a new directory, if there are no other |
22 |
descriptions whose name begins with the same character). |
23 |
|
24 |
My second question is: What would be wrong with overwriting files in |
25 |
$HOME on every login? I currently have a bunch of files/directories |
26 |
in $HOME (e.g., .history, .gconfd, .fonts.cache-1, .bash_history, |
27 |
.recently-used, .Xauthority, .macromedia, .adobe, .subversion, .nvu, |
28 |
.gnome, .mozilla, .java, etc.), that regularly get overwritten by |
29 |
various random programs, without my asking, and things continue to |
30 |
work. Some of these changes even automatically happen every time I |
31 |
log in. The SSH program regularly rewrites files (e.g., |
32 |
~/.ssh/known_hosts) successfully. |
33 |
|
34 |
> And if you wanted to remove those "-via-ssh-#" lines after |
35 |
> logout, what will happen if your connection hungs? |
36 |
|
37 |
I'm sorry, but I don't understand the question at all. What |
38 |
"-via-ssh-#" lines? There are no such lines in my proposal. |
39 |
|
40 |
-- |
41 |
Joe |
42 |
|
43 |
P.S. As I do not get this mailing list (I'm subscribed, but to the |
44 |
no-mail version), if anyone wants me to see any replies, it would help |
45 |
to send a copy of the e-mail to me, as I probably won't have time to |
46 |
check the forum. |
47 |
|
48 |
-- |
49 |
gentoo-dev@g.o mailing list |