
getty-ps 2.1.0 for linux 2.2 and higher				28-Sep-2002
(This *should* work with Linux 1.0.x, but I don't have a test system...)

Hello, everyone!  For those of you new to getty-ps, please allow me to
introduce myself.  I am Christine Jamison, and I am the current maintainer
of getty-ps.

While I have no idea if anyone out there has been waiting, a new release of
getty-ps is now available!  Prior to my last release of about 6 months ago,
the last "official" release was made in May 1994.  I'm guessing at least a
*few* of you are out there, anxiously awaiting help!  If you did not
download the last release (2.0.8), don't worry - this release includes all
those fixes, and a *bunch* more!  This release is again a big clean-up
release.  These programs have been running cleanly since July 2002 (except
for the last fix), and so this code is solid.  I've also tested getty with
a *lot* of different devices with several types of ports on several
systems since the last release, just to be sure it is a solid as I'm
saying.  I found several *interesting* problems, and they are now all
addressed.

There are several new features in this release, the most noteable being
support of efax.  (Although, to get efax to work reliably, you need to
replace the bsd spooler package!)  And, *lots* of clean up, still.  Again,
if you have been having problems with *any* previous release, I strongly
urge you to upgrade.  This release is upward compatible with all previous
releases.

For those of you who are unfamiliar with getty_ps, here are some of
its features:

	*  A versatile config file allows modems to be initialized
	   with a chat script similar to that used in uucp.

	*  Modems can be used as bi-directional lines.  Getty will
	   monitor a tty port and reset when another program frees
	   the line.

	*  Modems can be set up in "ringback" mode.  Ringback is a
	   special way of answering a modem call.  When in ringback
	   mode, getty will only answer the line when the phone rings
	   once or twice followed by a brief delay, and then rings again.  
	   This allows a single phone line to be used for data and
	   voice calls.

	*  Getty can be scheduled to be "on" and "off" during specified
	   time periods, allowing access to be restricted to certain
	   times (this option _finally_ works with timezones and
	   daylight savings time).

	*  Fidonet mailers are supported (the ifmail package is
	   required to take advantage of this feature).

I have no idea when the next release will be out, although I think one per
year is probably a minimum.  How often more than that depends mostly on
what problems I find and features I decide to add.  I have all the
(published) notes from Kris, but sugestions from users would be most
appreciated.  So, if you have any specific features you would like to see,
let me know!

A last comment about version IDs.  The way I will be assigning version IDs
is as follows:  X.Y.Z, followed by an optional letter.  If an important patch
needs to get out, then I will use the optional trailing letter.  All
patches will be cumulative (so that 2.0.9d includes the patches in 2.0.9a
thru 2.0.9c, *plus* 2.0.9d).  The next release will include all patches from
the previous release (that is, 2.0.10 will be 2.0.9, *plus* 2.0.9a thru
2.0.9d, *plus* whatever I was *planning* to put out in 2.0.10!)  The
expected progression of code and features will just increment the last
number.  If major code changes are done (but still upward compatable), then
the middle number will be incremented.  The first number will be incremented
*only* if a change occurs that makes the code *not* completely upward
compatable (like the format of a configuration file changes).

As always, if you have any problems with or questions about this software,
I would be happy to hear from you!  I *always* return e-mails, but not
always as soon as I would like! <grin>

Christine Jamison <getty-info@nwmagic.net>
