diskimage-builder/elements/serial-console/README.md

Start getty on active serial consoles.

With ILO and other remote admin environments, having a serial console can be
useful for debugging and troubleshooting.

For upstart:
  If ttyS1 exists, getty will run on that, otherwise on ttyS0.

For systemd:
  We dynamically start a getty on any active serial port via udev rules.
serial-console: Use udev rules to startup getty Update the systemd serial port element implementation so that it uses udev rules. Much nicer than hard coding ttyS0 and ttyS1. The udev rule only adds real serial device types (i.e. == 4). See: define TTY_DRIVER_TYPE_SERIAL 0x0003 from include/linux/tty_driver.h. Change-Id: I5d7de4815fd09c01693b7da4b8949f22fee20745 2014-03-19 20:21:43 +00:00			`Start getty on active serial consoles.`
Add an element to configure a serial console. With ILO and other remote machine management cards, a serial console is actually useful. Change-Id: I86f74d9dae3821b4682df813c5b52a83a29a138a 2013-05-09 06:39:37 +00:00
			`With ILO and other remote admin environments, having a serial console can be`
Implement serial-console for systemd. Update install.d/20-stty so that we try to start a getty on ttyS0 and ttyS1 when using systemd. Change-Id: Id5b605c74bf82855af0af4d0f95659cdd3a7b3a0 2014-01-13 18:02:54 +00:00			`useful for debugging and troubleshooting.`

			`For upstart:`
			`If ttyS1 exists, getty will run on that, otherwise on ttyS0.`

			`For systemd:`
serial-console: Use udev rules to startup getty Update the systemd serial port element implementation so that it uses udev rules. Much nicer than hard coding ttyS0 and ttyS1. The udev rule only adds real serial device types (i.e. == 4). See: define TTY_DRIVER_TYPE_SERIAL 0x0003 from include/linux/tty_driver.h. Change-Id: I5d7de4815fd09c01693b7da4b8949f22fee20745 2014-03-19 20:21:43 +00:00			`We dynamically start a getty on any active serial port via udev rules.`