Bug 134449 - /.autofsck causes switch to vt1 without ever switching back
/.autofsck causes switch to vt1 without ever switching back
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2004-10-02 17:02 EDT by Alexandre Oliva
Modified: 2014-03-16 22:48 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-17 00:52:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexandre Oliva 2004-10-02 17:02:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)

Description of problem:
Since current rhgb displays fsck progress in the rhgb window, it is
now safe to switch back to rhgb after the prompt is answered or times
out.  Ideally, the prompt should be displayed in rhgb itself.

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

How reproducible:

Steps to Reproduce:
1.Reboot uncleanly

Actual Results:  rhgb go away for the `force file system check' prompt
and never come back

Expected Results:  rc.sysinit should switch back to vt8 before
starting the actual fsck, or not switch to vt1 if we could prompt
through rhgb

Additional info:
Comment 1 Alexandre Oliva 2004-10-02 17:04:53 EDT
DV says we probably can't feed initscripts any input, so it's tricky
to move the prompt into rhgb.  My suggestion is to intercept the
prompt, open a dialogue in rhgb, and store the result in a file in
/etc/rhgb that rc.sysinit would look for.
Comment 2 Bill Nottingham 2004-10-17 00:52:18 EDT
Fixed in 7.91-1, in that it switches back to rhgb after the fsck
finishes. More complicated fixes later. :)

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