From: gleasokr@rintintin.Colorado.EDU (Kris Gleason) Subject: Re: Taylor UUCP 1.03 Callout, need help Date: Thu, 1 Apr 1993 09:30:43 GMT
system@micromed.com (Duane Davis) writes:
>I tried this. Permissions are set to read/write for everyone. running
>uugetty on ttyS1, everything calling out is set to cua1. There are no lock
>files present.
>MINICOM: Cannot open /dev/cua1. Sorry.
>KERMIT : hangs
>UUCICO : ERROR: open (/dev/cua1): Device or resource busy.
>I get the same if I do an "init 5" which disables uugetty. If I reboot with
>uugetty disabled minicom and kermit will work. uucico still doesn't work
>but doesn't give any indication as to why (nothing is written to the log).
[you _sure_ uugetty gets killed when you do an init 5??? sounds like
it dosen't to me]
Ahh... now, there's the _other_ half of the problem that shows up
when the new serial drivers are introduced. You're using getty_ps
2.0.4. There is a new release (2.0.6), but it has a bug that will
probably just annoy you some more.
I will be releasing getty_ps 2.0.7 in about a week (maybe less).
This should fix the problems with `device in use.' I suggest
that everyone wait for 2.0.7. If you're impatient, you can get
2.0.6b, but I don't suggest running it on virtual terminal #1 if
you have the sysv-init package (try it if you don't believe me).
Kris