Jan Engelhardt wrote:
I did not fully understand the original post, though. screen can connect to a serial port and at the same time log it (as does minicom), script is really just a wrapper around your current tty, and there is also e.g. ttyrpld for kernel-level tty monitoring. Last but not least, you can also manually play with inb or open(/dev/ttyS0).
ok, I try to explain in other way: I have an appliance, whit a serial port/console, and I have to set [up] a linux box (with the limitation to install any software ej:cu, kermit, etc) to connect via serial to the appliance.
"Limitation to install"? Allowed to install something or not allowed? Note that you can always "install" (read: put some binaries) into your home directory and run them from there.
The appliance, and the linux box are licensed, so I have a contract with my service support that limit to me.
And the point is "How to capture the output of the console of the appliance?" (this is for just in case the box crashes)
See above. screen/script/minicom/ttyrpld can do that, using various techniques at different levels. I am not sure if kermit includes a built-in logging facility.
I have the permission to put and run any script (if necessary), in the linux monitor to do this.
All except ttyrpld do not require any kernel modification (the latter serves a special purpose though) and should therefore be easy-to-use. Besides the program, only permission on /dev/ttyS0 is needed, so you can run it with an unprivileged user account, or even a chroot.
OK, many thanks
Jan Engelhardt