sig_cloud/diskimage-builder
11
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
diskimage-builder/diskimage_builder/elements/enable-serial-console/install.d/20-stty

16 lines
414 B
Text
Raw Normal View History

/bin/bash all the things. Since we are using bash syntax in some of the element fragments, we should make sure we use bash for all of them, so that things don't break on systems where /bin/sh != /bin/bash. Change-Id: If2f043c57aa4e1492b7f9839213ef6123f683612
2013-11-07 04:25:34 +00:00
#!/bin/bash
Standarise tracing for scripts There is a wide variety of tracing options through the various shell scripts. Some use "set -eux", others explicity set xtrace and others do nothing. There is a "-x" option to bin/disk-image-create but it doesn't flow down to the many scripts it calls. This adds a global integer variable set by disk-image-create DIB_DEBUG_TRACE. All scripts have a stanza added to detect this and turn on tracing. Any other tracing methods are rolled into this. So the standard header is --- if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then set -x fi set -eu set -o pipefail --- Multiple -x options can be specified to dib-create-image, which increases the value of DIB_DEBUG_TRACE. If script authors feel their script should only trace at higher levels, they should modify the "-gt" value. If they feel it should trace by default, they can modify the default value also. Changes to pachset 16 : scripts which currently trace themselves by default have retained this behaviour with DIB_DEBUG_TRACE defaulting to "1". This was done by running [1] on patch set 15. See the thread beginning at [2] dib-lint is also updated to look for the variable being matched. [1] https://gist.github.com/ianw/71bbda9e6acc74ccd0fd [2] http://lists.openstack.org/pipermail/openstack-dev/2014-November/051575.html Change-Id: I6c5a962260741dcf6f89da9a33b96372a719b7b0
2014-09-04 04:56:29 +00:00
if [ ${DIB_DEBUG_TRACE:-1} -gt 0 ]; then
set -x
fi
set -eu
set -u and -o pipefail everywhere As with the previous similar changes, this is intended to catch problems as they happen instead of ignoring them and continuing on to potentially fail later. Setting this on all existing scripts will allow us to enforce use via Jenkins. Change-Id: Iad2d490c86dceab148ea9ab08f457c49a5d5352e
2014-04-03 02:24:15 +00:00
set -o pipefail
Standarise tracing for scripts There is a wide variety of tracing options through the various shell scripts. Some use "set -eux", others explicity set xtrace and others do nothing. There is a "-x" option to bin/disk-image-create but it doesn't flow down to the many scripts it calls. This adds a global integer variable set by disk-image-create DIB_DEBUG_TRACE. All scripts have a stanza added to detect this and turn on tracing. Any other tracing methods are rolled into this. So the standard header is --- if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then set -x fi set -eu set -o pipefail --- Multiple -x options can be specified to dib-create-image, which increases the value of DIB_DEBUG_TRACE. If script authors feel their script should only trace at higher levels, they should modify the "-gt" value. If they feel it should trace by default, they can modify the default value also. Changes to pachset 16 : scripts which currently trace themselves by default have retained this behaviour with DIB_DEBUG_TRACE defaulting to "1". This was done by running [1] on patch set 15. See the thread beginning at [2] dib-lint is also updated to look for the variable being matched. [1] https://gist.github.com/ianw/71bbda9e6acc74ccd0fd [2] http://lists.openstack.org/pipermail/openstack-dev/2014-November/051575.html Change-Id: I6c5a962260741dcf6f89da9a33b96372a719b7b0
2014-09-04 04:56:29 +00:00
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
SCRIPTDIR=$(dirname $0)
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
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
if [ "$DIB_INIT_SYSTEM" == "upstart" ]; then
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
install -m 0644 -o root -g root ${SCRIPTDIR}/ttySx.conf /etc/init/ttySx.conf
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
elif [ "$DIB_INIT_SYSTEM" == "systemd" ]; then
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
install -D -g root -o root -m 0644 ${SCRIPTDIR}/serial-console-udev.rules /etc/udev/rules.d/99-serial-console.rules
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
fi
Reference in a new issue Copy permalink