As user I run xminicom to access a VAX system via cua1 from RedHat 5.2. Two days ago I had five power outages in one morning, during which I discovered that my UPS battery was shot. Generally my Linux took the abuse quite well, but here is something I'm having trouble resolving. Root can use the xminicom as before, but user can't start the xminicom window. I entered user's xminicom configuration and ascertained that the config file existed and duplicated that of root. Am I correc to infer that the problem likely resides between minicom and cua? The obvious thing was permissions, but user has rwx permission for cua1. When I run minicom, a lock file pops up in /var/block/LCL..cua0, but it is a lock file for cua0, not cua1! That happens when root successfully runs minicom (which I'm doing right now), and so it apparently does not block cua1. Can anyone explain this? I tried to run #cu -l /dev/cua1 as both root and user. In both cases I get a message permission denied and line in use (when the line is not in use). That seems something new, but don't know what to make of it. Will failure to see /dev/modem->/dev/cua1 cause xminicom to abend? It seems almost as if my wires got crossed, but I'm definitely on cua1 (COM2). Haines Brown
