EOT is handled by the pty emulation. the terminal program just sends byte value 4 to the pty emulation. it is that emulation that converts it to end-of-file. the shell gets the EOF. Today's shells require several EOF events. Classical shells will exit upon just one such event. that exit by the shell sends SIGCHLD to the terminal. or the terminal gets EOF from the side of the PTY it's reading to get shell session output. then the terminal window closes. same action. same effect. now days just type in the shell command "exit" or hold Ctrl+D to let it repeat.
on IBM mainframes, in VM/CP, i found a bug where any "ASCII" terminal doing EOT followed rapidly by BREAK would cause the entire system to freeze requiring a reboot (IPL). the terminal did not even need to be logged in so anyone could dial up the mainframe if they had ASCII dial up and freeze the whole system. once i got the source code, i wrote a patch to fix the bug and sent it to IBM. they accepted it. the new effect took that particular terminal offline and gave the main operator a message of what happened.
on IBM mainframes, in VM/CP, i found a bug where any "ASCII" terminal doing EOT followed rapidly by BREAK would cause the entire system to freeze requiring a reboot (IPL). the terminal did not even need to be logged in so anyone could dial up the mainframe if they had ASCII dial up and freeze the whole system. once i got the source code, i wrote a patch to fix the bug and sent it to IBM. they accepted it. the new effect took that particular terminal offline and gave the main operator a message of what happened.
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.