> si, es casi primitiva la prueba, pero como no se me ocurriò nada mas > inteligente, pregunto por si me pudiesen ayudar con algo mas serio > > SCRIPT(1) System General Commands Manual SCRIPT(1)
Cool. Not only a useful response instead of a flame for incorrect language but also I learned something I didn't know before. The only bad thing is the characters are not coming through correctly (at least for me).
Damon Register
ok, thanks, I sooo sorry (I hope this language match to you) the big thing is: Capture in a Linux box, the output of the serial console of another one Linux, but without installing cu, kermit, etc. (this is by a subject of the application license of this appliance) till now, I have try to configure in syslog, redir all the events to /dev/ttyS0, and execute "tail - f /dev/ttyS0" in the other side, yeah, this attempt is almost primitive, but I haven't no idea how to do this.
nop, I have connected this linux via the serial ports.
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).
Jan Engelhardt -- ok, I try to explain in other way: I have an appliance, whit a serial port/console, and I have to set a
Jan Engelhardt wrote: linux box (with the limitation to install any software ej:cu, kermit, etc) to connect via serial to the appliance. And the point is "How to capture the output of the console of the appliance?" (this is for just in case the box crashes) I have the permission to put and run any script (if necessary), in the linux monitor to do this.