Use tset -I for all terminals, not just xterm.

Terminal initialization is usually only needed for hardware terminals,
which are rare these days, and the initialization strings result
in a bunch of e

Use tset -I for all terminals, not just xterm.

Terminal initialization is usually only needed for hardware terminals,
which are rare these days, and the initialization strings result
in a bunch of extra newlines on pseudo-terminals. OK nicm@

show more ...

reminding people about afterboot on every single login is stupid.

Skip terminal initialization when logging in from an xterm, we
can be fairly sure the terminal is already initialized. Avoids
a one second pause on login. Requested and OK deraadt@

Only have tset prompt for the terminal type if it is "unknown" or
not listed in /etc/ttys. OK deraadt@ guenther@

remove balony advice, recommended by beck

also tell root to use afterboot(8); ok millert

add missing rcs ids
ok millert@

rm trailing whitespace

Ok, I'll say it again: "fix ^C in termtype prompt for real this time"
The bottom line is that the 'set noglob' has to be in effect *before*
the eval, but if the user hits ^C we don't want their shell

Ok, I'll say it again: "fix ^C in termtype prompt for real this time"
The bottom line is that the 'set noglob' has to be in effect *before*
the eval, but if the user hits ^C we don't want their shell to still
have noglob set. So, we now catch the ^C and continue on like the tset
completed OK. Egad.

show more ...

fix ^C in termtype prompt for real this time

Kill tset alias and just use expanded form in dot.login.
Fixes the problem where if you hit ^C at the root termtype
prompt noglob never gets unset.

mail describes the afterboot thing now

new afterboot man page, and root logins will be told about it

differentiate between logging in as root and using "su -"

initial import of NetBSD tree