Thanks for the advice. I've moved from being completely lost to being somewhat
confused. :-) At least it's a step in the right direction. Here is what I've
tried and the (rather confusing) results.
> A busy serial port
is usually because you are running something else on > the port: a minicom, or
a *getty (check /etc/inittab). Try >
> fuser /dev/ttyS1
This gave no results whatsoever.
> ls -lR /var/lock
This gave me:
total 5
drwxrwxrwx 2 root root 1024 Aug 10 20:26 emacs
drwxr-xr-x 2 root root 1024 Dec 15 10:50 network
drwxr-xr-x 2 root root 1024 Aug 10 23:37 samba.d
drwxr-xr-x 2 root root 1024 Dec 15 10:50 subsys
drwxr-xr-x 2 uucp uucp 1024 Aug 10 20:23 uucp
/var/lock/emacs:
total 0
/var/lock/network:
total 2
-rw-r--r-- 1 root root 29 Dec 15 10:50 eth0
-rw-r--r-- 1 root root 29 Dec 15 10:50 lo
/var/lock/samba.d:
total 0
/var/lock/subsys:
total 0
-rw-r--r-- 1 root root 0 Dec 15 10:50 amd
-rw-r--r-- 1 root root 0 Dec 15 10:50 atd
-rw-r--r-- 1 root root 0 Dec 15 10:50 cron
-rw-r--r-- 1 root root 0 Dec 15 10:50 httpd
-rw-r--r-- 1 root root 0 Dec 15 10:50 inet
-rw-r--r-- 1 root root 0 Dec 15 10:50 mta
-rw-r--r-- 1 root root 0 Dec 15 10:50 rstatd
-rw-r--r-- 1 root root 0 Dec 15 10:50 syslog
/var/lock/uucp:
total 0
So there doesn't appear to be a lock file. My suspicion now turns to the irq.
Perhaps, in configuring my ethernet card, I caused a conflict. The only
problem is that I haven't been able to figure out what irq my com2 is using.
When I try:
[peter@noname peter]$ /sbin/setserial /dev/ttyS1
/dev/ttyS1: Device or resource busy
So I'm being told the device is busy, but I can't figure out what's causing it.
You can see where my confusion comes from.
On a small side note, where is the hostname for the system stored. I can set
it with hostname, but I'm back to noname on reboot. Editing /etc/hosts doesn't
do it.
Thanks again.
