Bug 14116

Summary: bash messages when fsck fails and bash starts
Product: [Retired] Red Hat Linux Reporter: Matt Domsch <matt_domsch>
Component: bashAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED RAWHIDE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-07-17 14:50:01 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 Matt Domsch 2000-07-17 14:34:03 UTC
I get the following messages if fsck fails at startup, and it drops you to 
a bash shell.

bash: tput: command not found
bash: dircolors: command not found
bash: id: command not found
[: -: unary operator expected

The / partition is mounted, but /usr isn't, and these all live in /usr/bin.
Just kind of annoying, but doesn't really cause a problem.  Since these 
are all getting sourced from /etc/{profile,bashrc}, could simple logic be 
added to test for the existence of these programs before calling them?

Comment 1 Bernhard Rosenkraenzer 2000-07-17 14:50:00 UTC
Thanks, fixed in bash-2.04-8