I think that would be a problem. Indeed these solutions will not work when the boot phase is stuck in INITRD.
We have had boot problems in the past, either because of an error in /etc/fstab or because of boot disk errors. In those cases we logoff the linux machine and mount the boot disk(s) in our emergency linux guest. There we can repair the boot disk, so fix errors in /etc/fstab or run a filesystemcheck on the disks. When the disks are correct we can release these disks and have the owner attempt to boot again. Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rick Troth Sent: Wednesday, August 16, 2017 6:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Auto login root on 3270 console ttyS0 > sudo nor pmrun address the issue of the "*Enter root password for > maintenance, or CTL-D to continue*" prompt when the system has > problems starting up. Indeed. And that prompt is driven by the INITRD phase, before /sbin/init (or SystemD) gets control and could spawn your console shell. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
