[comp.unix.i386] On SCO Unix 3.2, Can a uugetty

john@beaudin.UUCP (John Beaudin) (07/12/90)

Am I supposed to be able to set this up thru uunstall? I tried, but noticed
that 19200 wasn't obviously supported. I didn't have success doing it 
manually either. Thanks all.
-- 
My .signature is awaiting apropriate display technology

wht@n4hgf.Mt-Park.GA.US (Warren Tucker) (07/13/90)

In article <1369@beaudin.UUCP> john@beaudin.UUCP (John Beaudin) writes:
>Am I supposed to be able to set this up thru uunstall? I tried, but noticed
>that 19200 wasn't obviously supported. I didn't have success doing it 
>manually either. Thanks all.
>-- 
>My .signature is awaiting apropriate display technology

The gettydef handler does not know about B19200.  Try EXTA :-)
 
---------------------------------------------------------------------
Warren Tucker, TuckerWare  emory!n4hgf!wht or wht@n4hgf.Mt-Park.GA.US
Any perceptible delay will eventually get on your nerves. --Bob Hyers

jpp@specialix.co.uk (John Pettitt) (07/13/90)

wht@n4hgf.Mt-Park.GA.US (Warren Tucker) writes:
>The gettydef handler does not know about B19200.  Try EXTA :-)

The real fun one is select EXTB for 38,400, uugetty masks this 
and ends up bith B0.   Setting a port to B0 causes is to hang up :-(




-- 
John Pettitt, Specialix International, 
Email: jpp@specialix.com Tel +44 (0) 9323 54254 Fax +44 (0) 9323 52781
Disclaimer: Me, say that ?  Never, it's a forged posting !

gsn@sclcig.uucp (Georg Nikodym) (07/14/90)

In article <1369@beaudin.UUCP> john@beaudin.UUCP (John Beaudin) writes:
>Am I supposed to be able to set this up thru uunstall? I tried, but noticed
>that 19200 wasn't obviously supported. I didn't have success doing it 
>manually either. Thanks all.

You're right.  /usr/lib/uucp/uugetty does not recognize the "B19200" mnemonic
in a gettydef.  You'll have to use "EXTA" for that.  I found this out by
using the -c option to check the gettydefs file.  It complaned.  So I used
strings to find out what the right one was.

What you might want to do is set up a different set of gettydefs for
your modem, so as to remove this problem (the problem being that getty
does seem to recognize "B19200", so you can't be lazy and use the same
gettydefs for getty and uugetty.

Hope that helped,
-- 
-----------------------------------------------------------------------------
| Georg S. Nikodym  -  (416) 442-2238                                       |
|                                                                           |
| Southam Business Information and Communications Group, Don Mills, Ontario |
| gsn@sclcig.UUCP -or- ...!uunet!moore!sclcig!gsn                           |
|                                                                           |
| "The floggings will continue until morale improves" -Jose Castel-Branco   |
-----------------------------------------------------------------------------

john@beaudin.UUCP (John Beaudin) (07/16/90)

wht@n4hgf.Mt-Park.GA.US (Warren Tucker) writes:
>The gettydef handler does not know about B19200.  Try EXTA :-)

This EXTA item rings a bell ( I think ), but not loud enough for me to hear.
What is it? Where does it get referenced? Does your smiley mean use it
or don't use it?
-- 
My .signature is awaiting apropriate display technology

guy@auspex.auspex.com (Guy Harris) (07/18/90)

>This EXTA item rings a bell ( I think ), but not loud enough for me to hear.
>What is it?

A historical item.  The DEC DH-11 serial line mux had support for line
speeds up to 9600, plus two other speeds called "external A" and
"external B", which were to be driven by external clocks.  The UNIX tty
driver's line speed codes were basically those of the DH-11.

Later serial port hardware on various machines supported 19.2 and
sometimes 38.4 KB; the codes for "external A" and "external B" were
hijacked for those speeds on many UNIX systems.  I think Mr. Tucker is
saying that SCO UNIX 3.2 is one such system.  (Although I'm somewhat
surprised it doesn't grok "B19200" as well; the S5R3.0 "uugetty" code
appears as if it'll support that speed if "B19200" is defined in
<sys/termio.h>, and the S5R3.0 <sys/termio.h> defines both B19200 and
EXTA as the same code.)

rogerk@sco.COM (Roger Knopf 5502) (07/18/90)

In article <1371@beaudin.UUCP> john@beaudin.UUCP (John Beaudin) writes:
>wht@n4hgf.Mt-Park.GA.US (Warren Tucker) writes:
>>The gettydef handler does not know about B19200.  Try EXTA :-)
>
>This EXTA item rings a bell ( I think ), but not loud enough for me to hear.
>What is it? Where does it get referenced? Does your smiley mean use it
>or don't use it?

EXTA is a baud rate setting just like B9600. EXTA and EXTB are the
two extra baud rates that are implementation-specific. To be
specific for our implementation, EXTA==19200 and EXTB==38400.

-- 
Roger Knopf                                      <standard disclaimer applies>
SCO Consulting Services			  "The True Believers will...formulate
uunet!sco!rogerk  or  rogerk@sco.com       a message that even a monkey could
408-425-7222 (voice) 408-458-4227 (fax)    understand."             --Jeff Tye

john@beaudin.UUCP (John Beaudin) (07/21/90)

rogerk@sco.COM (Roger Knopf 5502) writes:

>EXTA is a baud rate setting just like B9600. EXTA and EXTB are the
>two extra baud rates that are implementation-specific. To be
>specific for our implementation, EXTA==19200 and EXTB==38400.

OK, I tried setting up init.base & inittab with uugetty running EXTA. I was
able to uucico out ok and to access the modem at 19200 manually. However,
the modem (a telebit TB+) hangs up abruptly as soon as an incoming caller's
carrier sensing is finished without a successful login.
What is the explanation/fix for this phenom? Thanks as always.
-- 
My .signature is awaiting apropriate display technology