settings, lock file etc

[Adam Lackorzynski]

Hi,

On Fri Mar 16, 2007 at 10:36:22 +0800, sean collins wrote:
> I'm having issues with minicom. I was using 2.1, now on 2.2 - same
> issues. I have a built in serial port and a USB serial port, on Linux
> 2.6.20 i686.
> 
> When I start minicom with no command line arguments, it connects to
> /dev/modem and places a lock file in /var/lock
> 
> If I change Serial device to /dev/ttyUSB0, the lock file remains for
> /dev/modem, so I can't start a second minicom.

This needs changing.

> I'm not convinced the next bit is minicom's fault, it may be
> usbserial, or it may even be a feature! If I start minicom without
> arguments, and change Serial device to ttyUSB0, and alter the port
> settings, I can't use my USB-connected serial port. If I save the
> setup (as usb0, for instance), I can exit and invoke 'minicom usb0',
> and it works!

Well, I don't think it's a feature if it does not work in the first
place.

> I did consider altering the code so that it does what I'm expecting
> (new lock file, apply port settings), but it looks awfully neat and
> tidy as it is! If you want me to try pinning the problems down
> further, please let me know, and I'll do my best.

Don't be shy! Show the patch! :)


Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/