Due to (what I think is) some sort of bug on the Linux version (Kali v2.0) of my remote computer, my TTY text consoles do not start until I locally sit on the machine and press CtrlAltFn.  I use to remotely login via SSH into that computer, and then I access the TTY n by using ConSpy, so, for example:# conspy 6sends my SSH client (Putty in my case) to TTY6.  But, as long as TTY consoles have not started, I only get a blank screen with the cursor blinking.So I firstly send:# agetty 38400 tty6 &And then the TTY6 starts running, so this time I can login and interact, but I get this strange message:Kali GNU/Linux 2.0 kali tty6kali login: luisPassword:Linux kali 4.0.0-kali1-686-pae #1 SMP Debian 4.0.4-1+kali2 (2015-06-03) i686The programs included with the Kali GNU/Linux system are free software;the exact distribution terms for each program are described in theindividual files in /usr/share/doc/*/copyright.Kali GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extentpermitted by applicable law.-bash: cannot set terminal process group (3662): Inappropriate ioctl for device-bash: no job control in this shellIs the agetty command the proper method to spawn a TTY text virtual console?
How can I spawn a TTY text virtual console?
kali linux;console;tty