Bug 70293 - RFE: use "initscripts -qc "fsck -T -a /" when checking root filesystem
Summary: RFE: use "initscripts -qc "fsck -T -a /" when checking root filesystem
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: initscripts
Version: limbo
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-31 14:56 UTC by petrosyan
Modified: 2014-03-17 02:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-07-31 14:58:27 UTC
Embargoed:


Attachments (Terms of Use)

Description petrosyan 2002-07-31 14:56:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724

Description of problem:
lines 236-238 of /etc/rc.d/rc.sysinit from initscripts-6.88-1 of Limbo2
contain the following lines:
        STRING=$"Checking root filesystem"
	echo $STRING
	initlog -c "fsck -T -a $fsckoptions /"
I would suggest modifying the last line to:
	initlog -qc "fsck -T -a $fsckoptions /"


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


here is the explanation of the "-q" option for initlog:
       -q     Do not print the program's output, unless it exits
              with a non-zero exit code.

Additional info:

So if there are any problems with the root partition the user is gonna see
exactly the same behavior as before.
When there are no errors on the root partition the user is gonna see:

Checking root filesystem                    [   OK   ]

this is how the output looks like now:

Checking root filesystem
fsck: /: clean, 93849/1089152 files, 442599/2175382 blocks  [   OK   ]

I thinks the first looks much better

Comment 1 petrosyan 2002-07-31 14:58:22 UTC
one more thing,

the log files in both cases will look identical

so this is just a cosmetic enhancement


Comment 2 Bill Nottingham 2002-08-14 01:54:20 UTC
I'm fairly sure this will break in-progress reporting of the progress bar for
actual checks.


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