Yes, you can send output to multiple consoles, but only one can get input, and I think the last one wins; also, some messages only make it to one console (I think /dev/console is the problem, it is the last specified console= or current active VT).
serialtty= is handled by some initramfs foo which will create upstart jobs spawning a getty. If you spawn a respawn getty on a non-existing tty, you get regular syslog output that it's not available. We could re-engineer this bit to use udev events to setup gettys on well known consoles if the devices exists?
Yes, you can send output to multiple consoles, but only one can get input, and I think the last one wins; also, some messages only make it to one console (I think /dev/console is the problem, it is the last specified console= or current active VT).
serialtty= is handled by some initramfs foo which will create upstart jobs spawning a getty. If you spawn a respawn getty on a non-existing tty, you get regular syslog output that it's not available. We could re-engineer this bit to use udev events to setup gettys on well known consoles if the devices exists?