From: rlm@helen.surfcty.com (Robert L. McMillin) Subject: Re: Taylor UUCP 1.03 Callout, need help Date: Thu, 1 Apr 1993 00:17:40 GMT
In article <gleasokr.733603383@rintintin.Colorado.EDU> gleasokr@rintintin.Colorado.EDU (Kris Gleason) writes:
> system@micromed.com (Duane Davis) writes:
>
> >levin@world.std.com (Levin F Magruder) writes:
>
> >> Hopefully this *is* a linux question, if not, someone please point me
> >> in the right direction. I read the FAQ that said "don't expect to be
> >> spoonfed," I've been working on this for a few days and I'm just not
> >> getting anywhere.
> >>
> >> Basic problem:
> >>
> >> When uucico is run in master mode, I believe everthing goes fine up
> >> to the point of picking up the phone and dialing. It never picks
> >> up. "ps" shows uucico running, it never terminates. It does lock
> >> the resource.
> ><STUFF DELETED>
>
> >I'd like to know the answer too. I've been fighting with the same problem
> >for more than a week, have left messages here and have also asked on the
> >IRC #LINUX channel. Either no one knows the answer or they don't feel my
> >question is worth an answer. Most likely the latter. This newsgroup
> >doesn't seem to be very friendly towards new *nix users.
I'll second that. Telling people to RTFM only works when they can
*find* The Fantastic Manual. I understand that the documentation
volunteers are helping with this, so we may see some improvement in this
area presently.
> [weekly posting]
>
> To make uucico, kermit, seyon, etc work with linux 0.99.5 and higher, The
> callout devices must be created. To create these devices,
>
> mknod /dev/cua0 c 5 64
> mknod /dev/cua1 c 5 65
> mknod /dev/cua2 c 5 66
> ...
> etc
>
> The major number of the callout devices is 5, minor number is the same as
> the corresponding ttyS (callin) device.
>
> After you do this, run all things that call out (everything but getty) on
> the /dev/cua devices, and getty on the /dev/ttyS devices. This should
> clear up your modem problems.
Yes, I did all of these things. kermit -l /dev/cua1 reports back with a
"?can't open device" error and then exits. Even as root.
I gave up on /dev/cua*... I have the following entry in my
/etc/inittab:
S1:6:respawn:/bin/uugetty -w CONNECT 38400 ttyS1
This *works*.
Here's the output of ls -l /dev/cua*:
crw-rw-rw- 1 root root 5, 64 Mar 28 05:57 cua0
crw-rw-rw- 1 root root 5, 65 Mar 28 07:39 cua1
crw-rw-rw- 1 root root 5, 66 Mar 28 05:57 cua2
So it's not permissions that keep kermit from opening /dev/cua1.