src-test2/libexec/getty/main.c, branch release/5.2.1_cvsFreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=release%2F5.2.1_cvs2004-02-23T15:32:56ZThis commit was manufactured by cvs2svn to create tag2004-02-23T15:32:56Zcvs2svncvs2svn@FreeBSD.org2004-02-23T15:32:56Zurn:sha1:84a7b99b4e02a260bf7ff9b540032f4cb7bc612a
'RELENG_5_2_1_RELEASE'.
This commit was manufactured to restore the state of the 5.2.1-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.
Prototype defttymode() instead of just declaring it.2003-07-18T16:25:55ZYaroslav Tykhiyytykhiy@gmail.com2003-07-18T16:25:55Zurn:sha1:0183b0b8b87573d62a51fbbc3defc29832dd3ef5- Use the initial terminal mode instead of the current mode2003-06-18T13:22:44ZYaroslav Tykhiyytykhiy@gmail.com2003-06-18T13:22:44Zurn:sha1:b19ab1ce699c9fe531bd599a552136b47e52c238
as the source of defaults for terminal device parameters.
- Do duplucate code reduction and simplification enabled by
the above.
Reviewed by: green
MFC after: 1 month
In the last clean-up of this code, the fact that the default tty mode2003-06-14T08:26:47ZBrian Feldmangreen@FreeBSD.org2003-06-14T08:26:47Zurn:sha1:7ce06101b88f68f31c09b74299254c321443da16
information could only be gleaned from the the tty descriptor itself
was neglected, so never did the tty's default settings get copied from
the kernel. Specifically, this caused all manner of ctrl-keys to not
work. Fix this by calling dogettytab() in all the proper places, and
retrieving the terminfo temporarily in dogettytab().
Read gettytab(5) soon enough to fill in all necessary values.2003-06-10T18:30:41ZYaroslav Tykhiyytykhiy@gmail.com2003-06-10T18:30:41Zurn:sha1:3cd7e22936f308f84ec65629d1fee568a4abdc7d
Re-read gettytab(5) only if needed.
This fixes bugs introduced as long ago as in getty/main.c rev.1.15.
PR: bin/18181
MFC after: 1 month
Spot one more place where boolean variables were incremented2003-06-10T16:34:03ZYaroslav Tykhiyytykhiy@gmail.com2003-06-10T16:34:03Zurn:sha1:5f596fa5d0203cbe6ecd4f9d4b70318eeccc4221
instead of just being assigned a truth value.
Coding style fix: Use "foo = 1" instead of "foo++" to assign2003-06-10T15:38:35ZYaroslav Tykhiyytykhiy@gmail.com2003-06-10T15:38:35Zurn:sha1:8b52276d101bd9642e7f485ca68b2126b77e6f60
the truth value to a boolean variable, especially when inside
a loop. The variable can overflow otherwise, at least in theory.
Fix some minor bugs, namely:2003-06-06T14:36:41ZYaroslav Tykhiyytykhiy@gmail.com2003-06-06T14:36:41Zurn:sha1:f648dfd92939b4015c42637db3ca68024a2b764f
- Initialize "rval", which would be used uninitialized
if al or pl options were set.
- Don't pass an empty string to login(1) as a user name
(this could be triggered by entering a name and then killing it
with backspace or ^U.)
- Don't loop endlessly if the al option specifies a bogus (i.e.,
not alphanumeric) auto-login name.
- Don't pass a bogus user name to login(1) if a good name were
entered and then killed with ^U.
- Exit with status 0, not 1, on receiving an EOF character,
since it's not a error condition.
MFC after: 1 week
Fix a typo (missed &&).2003-01-20T10:33:35ZMaxim Sobolevsobomax@FreeBSD.org2003-01-20T10:33:35Zurn:sha1:0fd652782b682f93e3834c40039e1d2cf330d054
Submitted by: marcus
Add a new gettytab(5) option - `pl', which if set tells getty that the line2003-01-19T20:59:52ZMaxim Sobolevsobomax@FreeBSD.org2003-01-19T20:59:52Zurn:sha1:9b76604885d5030519371bd511ee34b40c254e86
in question is PPP-only line, i.e. no PPP-sequence detection is necessary and
PPP login program referenced by `pp' should be started automatically instead of
login(1)
Feature suggested and sponsored by: United Networks of Ukraine
No reply from: re
MFC after: 2 weeks