![]() Some of you will argue that I could remap the escape sequences for each program so they will not match, but hindsight is 20/20: it does not do me any good once they are already running inside each other. So, if I want to send a CTRL-A X (exit) to minicom, screen will think I am talking to it and then lock the screen. But, problem is that screen and minicom by default use the same CTRL-A sequence to enter commands. At first that does not seem to be a bad idea after all, it would be nice to connect to the console of, say, a Brocade fabric switch, start something there, log out, and then come back to it later. I really should not do that because you can connect to a serial port from screen by doing something like :screen /dev/ttyUSB0 115200(some devices I use have their default port speed set to 9600, others like the one in this example to 115200)īut, force of habit (read: lazyness) or distraction (did you see that ant crawling up the wall?) caused me to start minicom right in screen. The problem begins when I try to use them together. I also like screen, which allows me to run multiple sessions on different machines and stop and resume them as needed kinda like running vnc/rdp but in command-line. And I have used it long enough to remember some of the commands. ![]() ![]() You see, I like to use minicom as a terminal program since it plays nice with my usb-to-serial cables and my serial devices (Sun and AIX workstations, Seagate Dockstar, Pogoplug, routers, switches). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |