RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Booting with init=/bin/sh does not work

Steps to Reproduce:
1. Press 'e' in grub boot menu, append "init=/bin/sh" to kernel command line
2. Boot the system

Actual results:
After initramfs stage finishes, "sh-4.2#" prompt does appear, but it is unusable: tty is in wrong mode: <enter> results in the prompt re-printed on the same line, not next line.
about half of the entered chars are "eaten": typing "ls<enter>" results in "sh: l: command not found".

Expected results:
Usable shell

This has nothing to do with initscripts.

(In reply to Denys Vlasenko from comment #0)
> Description of problem:
> Booting with init=/bin/sh does not work
> 
> Steps to Reproduce:
> 1. Press 'e' in grub boot menu, append "init=/bin/sh" to kernel command line
> 2. Boot the system
> 
> Actual results:
> After initramfs stage finishes, "sh-4.2#" prompt does appear, but it is
> unusable: tty is in wrong mode: <enter> results in the prompt re-printed on
> the same line, not next line.
> about half of the entered chars are "eaten": typing "ls<enter>" results in
> "sh: l: command not found".
> 
> Expected results:
> Usable shell

Does it help to disable plymouth?

Add "rd.plymouth=0 plymouth.enable=0" to the kernel cmdline.

Anyway, you better use runlevel 1 or "s" for a rescue shell.

Add "1" or "s" to the kernel cmdline.

even better add "emergency" to the kernel command line

'emergency' will ask you for root password. It cannot be used for root password change.

init=/bin/sh is working if rhgb is removed.

reassigning to plymouth, which had code to detect "init=/bin/sh", IIRC

*** This bug has been marked as a duplicate of bug 1098332 ***