Hola Hèctor, On Tue, Feb 15, 2011 at 10:15:29AM +0000, Hector Oron wrote: > El 15 de febrer de 2011 8:20, Lluís Batlle i Rossell > <[email protected]> ha escrit: > > > Trying to list some problems of minicom: > > - It requires 'root' to run, for most useful things. The code is full of > > "if(getuid())", and requires some files in /etc. > > zumbi@enorme:/tmp/minicom-2.5$ grep -nRH getuid * > src/minicom.c:1234: if ((pwd = getpwuid(getuid())) == NULL) { Uhm, the code changed since the last time I used it :)
> About files in /etc, do you mean it just looks for /etc/termcap on the > wkeys code? /etc/minicomrc and other config files. Maybe it changed too, in newer versions. > > - It always emulates a terminal, 'translating' the chosen terminal > > emulation to > > curses operations for the terminal you use minicom in. This emulation is > > quite > > minimal, and usually breaks unicode and disables any powerful terminal > > feature, setting a 'vt100' or so in the middlle. > > Sorry I do not see the problem, maybe a misconfiguration on your side? Well, minicom emulates a terminal more limited than what my xterm may be. > > - It's meant for MODEMs, and it's hard to get it working without a DTR > > signal in > > the serial port. > > Disable hardware flow control (C-a O > Serial port setup > F) CTS/RTS is the hardware flow control. I talked about DTR. I think it has to do with what it says about Ready/Not ready in the status bar. I remember as if minicom did not send or show anything if DTR was down. > > - It usually sends a Hayes sequence when starting. > > Maybe you need $ minicom -o This avoids the lockfiles :) > Just to mention another application: 'seyon' I did not know it. Thank you. Atentament, Lluís. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
