Configuring Xenix for 1200/2400 baud access, uucp log management

[Marty Connor]

In article <10387 at steinmetz.ge.com>, davidsen at steinmetz.ge.com (William E. Davidsen Jr) writes:
>  B) unless there is a political reason for doing things low to high,
> change the speeds to cycle from highest to lowest, repeating the first
> one. This takes care of connect noise. I have been running a BBS for
> several years, and I use 2400-2400-1200-300 without problems. It will
> require minor changes in others login scripts if they're still using
> 1200.
> 

"We've got to stop meeting like this."

I was trying to call up random at 1200 baud on its 2400 baud modems
today and was having a lot of trouble getting the autobauding to work
right.  After reading your message it occured to me that the
/etc/gettydefs file was set up to do:  2400-300-1200, so if a person
dialed in at 1200 he or she had to hit break twice (and this didn't
work right 100% of the time either!).  so I made the relevant
gettydefs lines look like:

    #
    # 3-2-1: 2400 - 1200 - 300 baud cycle	(dialin modems)
    #

    1 # B300  HUPCL OPOST CR1 NL1 #
	    B300 CS8 SANE HUPCL TAB3 IXANY #\r\n@!login: # 3

    2 # B1200 HUPCL OPOST CR1 ECHOE NL1 #
	    B1200 CS8 SANE HUPCL TAB3 ECHOE IXANY #\r\n@!login: # 1

    3 # B2400  HUPCL OPOST CR1 ECHOE NL1 #
	    B2400 CS8 SANE HUPCL TAB3 ECHOE IXANY #\r\n@!login: # 2


so that when you call in, you get a getty listening at 2400 baud, and
then 1200, and then 300.  Makes a little more sense.  If you have
people complaining that reaching your system at 1200 baud is a pain,
you might try this little tweak to your gettydefs file.  Double your
money back guarantee. ahem.  Anyway, random.entity.com and
mcp.entity.com seem to like it...

-- 
----------------
Marty Connor
Director of Innovation, The Entity
mdc at mcp.entity.com, ...{harvard|uunet}!mit-eddie!spt!mcp!mdc