mknod /dev/console can fail

[Jan Kiszka <jan.kiszka@siemens.com>]

Hi all,

just saw this in CI build:

[...]
2019-01-02 19:37:55 - INFO     - | localepurge: Removing disabled auto-generated config file.
2019-01-02 19:37:55 - INFO     - |
2019-01-02 19:37:55 - INFO     - |   To reinstall all the packages which localepurge has been taking care
2019-01-02 19:37:55 - INFO     - |   of before, you can use the following command:
2019-01-02 19:37:55 - INFO     - |
2019-01-02 19:37:55 - INFO     - |     apt-get -u --reinstall --fix-missing install $(dpkg -S LC_MESSAGES | cut -d: -f1 | tr ', ' '' | sort -u)
2019-01-02 19:37:55 - INFO     - |
2019-01-02 19:37:55 - INFO     - | mknod: /dev/console: File exists
2019-01-02 19:37:55 - INFO     - | WARNING: exit code 1 from a shell command.
2019-01-02 19:37:55 - INFO     - | ERROR: Function failed: do_rootfs (log file is located at /builds/ebsy/debian/build/tmp/work/jailhouse-demo-amd64/demo-image-qemu-amd64/temp/log.do_rootfs.66135)


I strongly suspect it comes from debian-configscript.sh:

# Create console device
if [ ! -e /dev/console ]; then
     mknod /dev/console c 5 1
fi


Something must be creating /dev/console in the background while the
config script runs. That is weird. Any ideas what could be the race
partner?

Do we still need this mknod? It date back to e7e59151f7f0. Removing this
would be the safest option because the case might be hard to reproduce -
I've only seen this once so far.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux