------- Comment From [email protected] 2018-01-25 10:12 EDT------- (In reply to comment #4) > During the installation (z/VM guest and KVM virtual machine) of Ubuntu > Server 16.04.1 (and 16.04.2) repeating messages of the form: > > " > Select and install software ... 10% can't open /dev/tty4: No such device or > address > can't open /dev/tty2: No such device or address > can't open /dev/tty3: No such device or address > can't open /dev/tty4: No such device or address
... > /dev/tty1 file exists on s390x ubuntu, however, one cannot open that file > doing that results in ENXIO. ... > Imho, if /dev/tty[0-9] devices do not exist, why does kernel create such The /dev/tty[0-9] devices represent the x86 VT consoles. They do not exist on s390x nor should the tty terminal device driver for them be active. So I suspect that these are not created by the kernel and, further, I guess that they are manually created by those utilities that create the install image. That means, these are static created device files rather then dynamically ones handled by udev. > files? Can it be escalated to IBM linux team to not have those files at all? > E.g. make a upstream kernel patch to not create these devices. Maybe I am > crazy, I don't understand things - e.g. is it possible to somehow get a > working /dev/tty1? No there isn't. The only special case is /dev/tty (without a number). This refers to the current terminal of a process (it is not a VT console). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
