Re: Char devices drivers

[Pete Zaitcev <zaitcev@redhat.com>]

>> > Can anyone explain what is the utility of the callout devices 
>> > in the char drivers ???

The utility is this (mind, it is only a nice idea in someone's
empty head, in reality it does not really work that way):

1. You run getty on /dev/cua0 or /dev/cua1.
2. Getty waits for the carrier, and keeps /dev/cuaN open.
3. Meanwhile, you can use cu, kermit, and uucico to dial
   out using /dev/ttya or /dev/ttyb.

Sounds very nifty, and this is how SunOS worked and Solaris
tries to (with devices renamed a bit). The devil is details,
or course. The hellishly complicated semantics of this
twin-tailed device makes the driver pretty buggy.

>[...]
> So eliminating cua means more work for the programmer but less confusion
> for users.  Overall, it's a good thing since there are many more users
> than programmers.
> 
> 			David Lawyer

I think it's more important that devices work as advertised
more often if drivers are simpler. In my expirience, users
are not really confused by callout devices, but rather are
annoyed when they step on a bug.

-- Pete