subiquity/bin/subiquity-service

#!/bin/sh
port=tty1
if [ -n "$1" ]; then
   port=$1
fi
/bin/dmesg -n 1
if [ "$port" = "tty1" ]; then
	$SNAP/bin/subiquity-loadkeys
	setfont $SNAP/subiquity.psf
	exec /sbin/agetty -n --noclear -l $SNAP/usr/bin/python3 -o $SNAP/usr/bin/subiquity $port $TERM
else
	exec /sbin/agetty -n --keep-baud -l $SNAP/usr/bin/python3 -o "$SNAP/usr/bin/subiquity --serial" $port 115200,38400,9600 $TERM
fi
have a subiquity-service be part of the snap 2018-02-09 00:53:03 +00:00			`#!/bin/sh`
Make a unified launcher 2019-03-20 23:28:02 +00:00			`port=tty1`
			`if [ -n "$1" ]; then`
			`port=$1`
			`fi`
have a subiquity-service be part of the snap 2018-02-09 00:53:03 +00:00			`/bin/dmesg -n 1`
Make a unified launcher 2019-03-20 23:28:02 +00:00			`if [ "$port" = "tty1" ]; then`
Abstract resource file lookup relative to SNAP (#998) * Abstract resource file lookup relative to SNAP Using SNAP to find the resource files is a bit of an odd requirement for non-subiquity clients. Start abstracting that away so it's easier to change later. Also move loadkeys to lookup from this, since the previous solution is still a problem for ubuntu-desktop-installer. * Move loadkeys / configure-apt to bin loadkeys / configure-apt are in usr/bin only when we specially put them there by way of snapcraft, which makes things a little harder on non-subiquity clients. Move them to bin, which is to say don't have snapcraft put them in usr/bin. 2021-07-13 22:14:31 +00:00			`$SNAP/bin/subiquity-loadkeys`
Make a unified launcher 2019-03-20 23:28:02 +00:00			`setfont $SNAP/subiquity.psf`
			`exec /sbin/agetty -n --noclear -l $SNAP/usr/bin/python3 -o $SNAP/usr/bin/subiquity $port $TERM`
			`else`
			`exec /sbin/agetty -n --keep-baud -l $SNAP/usr/bin/python3 -o "$SNAP/usr/bin/subiquity --serial" $port 115200,38400,9600 $TERM`
			`fi`