Differences between xterm and pterm12/23/2023 bc PSFTP command-line option: Section 6.1.2īell, disabling: Section 4.5.1, Section 4.5.3 batch PSFTP command-line option: Section 6.1.4 batch PSCP command-line option: Section 5.2.2.5 batch Plink command-line option: Section 7.2.3.1 ‘basic’ authentication (HTTP): Section 4.15.4īatch files: Section 4.29, Section 5.2.3, Section 7.3 ‘AltGr’ key: Section 4.4.7, Section 4.4.8ĪNSI colours: Section 4.12.1, Section 4.12.6ĪNSI graphics: Section 3.3, Section 4.10.4Īpplication Cursor Keys: Section 4.4.4, Section 4.6.1Īpplication Keypad: Section 4.4.5, Section 4.6.1Īre You There, Telnet special command: Section 3.1.3.2Īrguments, command-line: Section 3.8, Section 9.3Īuthentication agent: Section 8.1, Chapter 9Īuthentication agent forwarding: Section 3.8.3.10, Section 4.22.6, Section 9.4Īuthentication, challenge/response: Section 4.22.4, Section 4.22.5Īuthentication, keyboard-interactive: Section 4.22.5Īuthentication, public key: Section 3.8.3.18, Section 4.22.8, Section 4.27.9, Section 5.2.4, Section 6.3, Section 7.2.2, Section 8.1Īuthorized_keys file: Section 8.2.10, Section 8.3Īuto wrap mode: Section 4.3.1, Question A.7.7īackground colour: Section 4.3.5, Question A.7.6īackground colour, default: Section 4.12.5, Section 4.12.6īandwidth: Section 4.13.2, Section 4.14.4, Section 4.18.3 Wouldn't that be fun.Abort Output, Telnet special command: Section 3.1.3.2Ībort Process, Telnet special command: Section 3.1.3.2Īccented characters: Section 3.3, Section 4.4.7Īccess to files, changing: Section 6.2.14Īccount name: Section 2.3, Section 3.8.3.4, Section 5.2.1.1Īccount name, for auto-login: Section 4.14.1Īccount name, local, in Rlogin: Section 4.17.1Īccount name, local, in Windows: Section 4.17.1Īccount names, different: Section 2.3, Section 4.22.7Īctive Telnet negotiation: Section 4.16.2Īddress, IP: Section 3.5, Section 4.1.1, Section 4.13.4Īd-hoc proxy: Section 4.15.1, Section 4.15.5, Section 4.16.2Īdjusting a selection: Section 3.1.1, Section 4.11.2Īdvanced Encryption Standard: Section 4.21Īgent, authentication: Section 8.1, Chapter 9Īgent forwarding: Section 3.8.3.10, Section 4.22.6, Section 9.4Īllocation, of pseudo-terminal: Section 3.8.3.12, Section 4.24.1Īlternate screen: Section 4.6.4, Section 4.7.4, Question A.7.16 Unless of course this system is so old that it uses a TERMCAP database. It all depends on how the remote system's OS has decided to store the terminfo files. ![]() The Mac has a bunch of numbered sub directories, I've seen on some Unix platforms a bunch of first letter subdirectories. Typically it is something likeĪnd then you have to figure out where under the 'terminfo' directory the different TERM files are stored. This is a fun game as you have to figure out where the remote system stores its terminfo files. The next thing to do is see what TERM values the remote system supports. ![]() That would tell you if ssh is passing your TERM environment variable to the remote system. You can easily experiment by setting different local TERM values and see if they appear on the remote system. It might be the one you passed from your system, or it might be some other value. When you login to the remote system you look to see what TERM it thinks it has by default: The Mac already has a valid TERM, unless your remote system has a very limited set of TERM values. You have to issue the export TERM=xterm on the REMOTE system.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |