Bug 16756 - Ctrl-D after fatal fsck doesn't produce expected behavior
Ctrl-D after fatal fsck doesn't produce expected behavior
Status: CLOSED RAWHIDE
Product: Red Hat Raw Hide
Classification: Retired
Component: initscripts (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
: 16757 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-22 17:46 EDT by compwiz
Modified: 2014-03-16 22:16 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-22 17:46:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description compwiz 2000-08-22 17:46:09 EDT
When fsck finds a really serious error, and you are given a choice of
either pressing Ctrl-D for normal startup or typing in the root password
doesn't bypass fsck when pressing Ctrl-D, pretty much leaving you in a loop
every time you restart and Ctrl-D'ing, if you don't have a rescue/boot
disk.
Comment 1 Bill Nottingham 2000-08-22 17:58:42 EDT
Should be fixed in the bash currently in rawhide.
Comment 2 Bill Nottingham 2000-08-22 17:58:54 EDT
*** Bug 16757 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.