On Tue, Sep 05, 2017 at 12:20:58AM -0700, Mike Larkin wrote: > On Sun, Sep 03, 2017 at 10:22:07PM -0700, Mike Larkin wrote: > > On Sun, Sep 03, 2017 at 03:03:22PM -0400, Dave Voutila wrote: > > > Decided to test using the "virt" Alpine build and it creates the error > > > I alluded to but couldn't remember. Login as root succeeds, but when > > > it tries to properly exec busybox's ash process it errors out with: > > > > > > -ash: can't access tty; job control turned off > > > > > > Still results in writing the prompt, but ash appears to exit and > > > return you to the login prompt. > > > > > > Looking into the source for busybox, it seems to be triggered here: > > > https://git.busybox.net/busybox/tree/shell/ash.c?h=1_27_stable#n3857 > > > > > > The call is to tcgetpgrp(3) trying to get the process group for the > > > TTY file descriptor. > > > > > > I'm a wee bit in over my head at this point, but figured I'd share the > > > latest. I'm honestly not sure if this is an issue with Alpine, but I > > > think if I can get it to work with a serial console in QEMU then it's > > > possibly a deficiency in VMD/SeaBIOS. > > > > > > -Dave Voutila > > > > > > > shrug. nobody else has reported any issues at all with alpine. as a matter > > of fact it was the first linux distribution we got working and is part > > of my set of VMs I test with regularly. > > > > -ml > > > > Just to make sure there wasn't something odd going on, I reproduced this test > using the standard alpine ISO just now using -current: > > # vmctl start test -i 1 -d > /home/mlarkin/Downloads/alpine-standard-3.6.2-x86_64.iso -d test.raw -m 1024M > -c > > At the boot: prompt, I used: > > boot: hardened console=ttyS0,115200 > > > Alpine then booted as follows: > > [ 0.000000] ACPI BIOS Error (bug): A valid RSDP was not found > (20160831/tbxfroot-244) > [ 0.086666] ACPI BIOS Error (bug): A valid RSDP was not found > (20160831/tbxfroot-244) > [ 0.089999] dmi: Firmware registration failed. > > > OpenRC 0.24.1.faeb98e61b is starting up Linux 4.9.32-0-hardened (x86_64) > > * /proc is already mounted > * Mounting /run ... * /run/openrc: creating directory > * /run/lock: creating directory > * /run/lock: correcting owner > * Caching service dependencies ... [ ok ] > * Remounting devtmpfs on /dev ... [ ok ] > * Mounting /dev/mqueue ... [ ok ] > * Mounting modloop ... [ ok ] > * Mounting security filesystem ... [ ok ] > * Mounting persistent storage (pstore) filesystem ... [ ok ] > * Mounting cgroup filesystem ... [ ok ] > * Starting busybox mdev ... [ ok ] > * Loading hardware drivers ... [ ok ] > * Loading modules ... [ ok ] > * Setting system clock using the hardware clock [UTC] ... [ ok ] > * Checking local filesystems ... [ ok ] > * Remounting filesystems ... [ ok ] > * Mounting local filesystems ... [ ok ] > * Configuring kernel parameters ... [ ok ] > * Migrating /var/lock to /run/lock ... [ ok ] > * Migrating /var/run to /run ... [ ok ] > * Creating user login records ... [ ok ] > * Wiping /tmp directory ... [ ok ] > * Setting hostname ... [ ok ] > * Starting busybox klogd ... [ ok ] > * Starting busybox syslog ... [ ok ] > > Welcome to Alpine Linux 3.6 > Kernel 4.9.32-0-hardened on an x86_64 (/dev/ttyS0) > > localhost login: root > Welcome to Alpine! > > The Alpine Wiki contains a large amount of how-to guides and general > information about administrating Alpine systems. > See <http://wiki.alpinelinux.org>. > > You can setup the system with the command: setup-alpine > > You may change this message by editing /etc/motd. > > localhost:~# > > > ... I then went on to install the system using setup-alpine and the docs > from the alpine web site. No issues were seen, and the system booted up > subsequently without the ISO (of course, after setting serial console > in the boot config). > > I am going to pull down a snapshot and retest to see if there is something > that may have snuck in that's not in my tree. > > -ml >
I just upgraded to this snap: OpenBSD 6.2-beta (GENERIC.MP) #70: Tue Sep 5 00:00:55 MDT 2017 and I had the same result as I just posted. No issues seen. Can you try to upgrade to the latest snap and try using a command line like mine and see if this is still a problem? Otherwise I'm not sure why your machine is behaving incorrectly. -ml
