[wplug] Serial Port Access in Red Hat 8

[William Powell]

Well, yes, I do know that case matters. 

But it hadn't dawned on me that there might actually be a ttys0(which 
was what the minicom config file defaulted too) and a ttyS0.  It looked 
right, so I went with it.

The listing for ttyS0 is as follows:

crw-rw----      1   root   uucp   4,64   Apr  4 14:46 /dev/ttyS0

minicom doesn't hurl when it starts, so I suspect it will work now.

Thanks.

Lance Tost wrote:

>Could just be a typo in you're post.. but you *are* using /dev/ttyS0, not 
>/dev/ttys0, right?  Remember, case matters in unix... or should I say 
>UNIX....
>
>On Fri, 4 Apr 2003, William Powell wrote:
>
>  
>
>>Date: Fri, 04 Apr 2003 12:48:38 -0500
>>From: William Powell <billpwl1 at attbi.com>
>>Reply-To: wplug at wplug.org
>>To: wplug at wplug.org
>>Subject: [wplug] Serial Port Access in Red Hat 8
>>
>>Redhat 2.4.18.14 running on a 133 P1 Compaq laptop.
>>
>>I am trying to access some serial data coming into the first serial 
>>port(ttyS0?) using minicom.  When I run minicom as either root or a 
>>normal user I get the following error:
>>
>>minicom: cannot open /dev/ttys0: Input/output error
>>
>>The ls -l for /dev/ttys0 are as follows:
>>crw-rw-rw-    1 root    tty    3,    48    Aug 30 2002     /dev/ttys0
>>
>>I added my username to the tty group, but that didn't have any effect. 
>>
>>Is this caused by a lockdown by some security tool that I haven't 
>>detected yet?
>>
>>
>>I can capture this serial data fine using Win98 on com1.
>>
>>
>>Bill
>>
>>
>>_______________________________________________
>>wplug mailing list
>>wplug at wplug.org
>>http://www.wplug.org/mailman/listinfo/wplug
>>
>>    
>>
>
>  
>