Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 694686

Summary: Boot single-user sets the TTY variables incorrectly
Product: Red Hat Enterprise Linux 6 Reporter: Misty Stanley-Jones <misty>
Component: sysvinitAssignee: Petr Lautrbach <plautrba>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0CC: lcarlon, tscott
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-28 22:14:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Misty Stanley-Jones 2011-04-08 01:50:31 UTC
Description of problem:
If I boot into single-user mode from Grub, I am unable to do things like run the "passwd" command. A strace reveals "Inappropriate ioctl for this device" messages.

Version-Release number of selected component (if applicable):
RHEL 6.0

How reproducible:
Always

Steps to Reproduce:
1. At GRUB menu, press spacebar
2. Press a to get to "append" mode
3. Enter a space, then "single" at the end of the line, and press <enter>
4. When you are dropped at the root prompt, enter "passwd" command
5. You get dropped back to the prompt
6. To see the error message, run "strace passwd" and view the stack trace.
  
Actual results:
Unable to run the "passwd" command (and probably others)

Expected results:
Normal single-user functionality

Additional info:
Tried this in a KVM virtual machine as well as VirtualBox. No physical hardware to test on.

RHEL6 2.6.32-71.el6.x86_64

Comment 1 Misty Stanley-Jones 2011-04-08 01:52:18 UTC
Probably not the right component, as someone else has a working system that has the same version of the init scripts. The $TERM is "linux" on working and non-working system.

Comment 2 Tristan Scott 2011-04-08 01:55:36 UTC
I have 2 KVM instances of RHEL 6 - one works perfectly in single, the other has the same problem. All environment vars are identical in both instances.

initscripts-9.03.17-1.el6.x86_64
bash-4.1.2-3.el6.x86_64

Package versions identical on both systems.

Please contact me if you require more info from either system.

Comment 4 RHEL Program Management 2011-04-08 06:00:17 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.