Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Feb 1997 17:13:17 +1100
From:      davidn@unique.usn.blaze.net.au (David Nugent)
To:        freebsd-current@freebsd.org
Subject:   getty patches
Message-ID:  <19970202171317.RP40411@usn.blaze.net.au>

next in thread | raw e-mail | index | archive | help
I have implemented the following in /usr/libexec/getty:

1)	Ability to define a modem initialisation script.
	The port is opened in non-blocking mode, and a
	send/expect chat script is executed. If modem
	initialisation fails, getty recycles.

	gettytab capabilities:

		ic=expect send [expect send ...]
			init chat script
		ct#val
			chat timeout in seconds

2)	Ability to answer incoming phone calls "manually"
	which allows disabling auto-answer mode (so the
	phone is not answered regardless of DTR state).

	gettytab capabilities:

		ac=expect send [expect send ...]
			answer chat script
		ct#val
			chat timeout in seconds

3)	A recycle time value, to getty to be periodically
	recycled and initialised after a given number of
	seconds if there is no activity detected.

	gettytab capabilities:

		rt#val
			recycle time in seconds

4)	A "debug chat" script value, which is a bitmask:

	gettytab capabilities:

		dc#val
			debug chat value:
			bit 0:received data (during chat)
			bit 1:send data
			bit 2:expect data
			bit 3:misc (mainly status)

5)	The 'de' capability now removes extraneous input after
	it pauses, essentially to throw away remaining garbage
	aftera connection via an answer script.

6)	Fixed bugs in the %s, %m, %r and %v macros which don't
	currently work [uname() was never being called, thus
	the values for these were always blank. rlogin seems to
	suffer the same bug].

7)	Sending a sysv-like "issue" file prior the login prompt.
	This is much more useful than the 'im=' capability since
	it can be more easily modified by scripts etc.

	gettytab capabilities:

		if=<filename>

	(I saw some chat about this a while back on the mailing
	list, but alas, no commit resulted).

Does anyone have any objecting to me committing these changes?
I believe they bring our getty more in line with modem technology
that has been available for over a decade now. :-)

The changes are fully backwards compatible. A non-modified
/etc/gettytab should result in precisely the same behaviour
as was present previously apart from items 5 (which should be
benign) and 6 (which fixes an existing bug).


Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970202171317.RP40411>