Bug 83300

Summary: cp mv mkdir etc not statically linked
Product: [Retired] Red Hat Linux Reporter: bperkins
Component: fileutilsAssignee: Tim Waugh <twaugh>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-02-01 23:46:50 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 bperkins 2003-02-01 23:19:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212

Description of problem:
IMHO there really isn't any good reason not to make these statically linked. 
This shouldn't be a problem under most circumstances, but can be a real
lifesaver (it would have saved me a lot of hassel).

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


How reproducible:
Always

Steps to Reproduce:
1.cd /
2.mkdir foo
3.mv lib foo
    

Actual Results:  Simple shell uutilities such as cp rm and mv don't work,
because the kernel can't find ld (lor libc for that matter).

Expected Results:  They should work.

Additional info:

Comment 1 Tim Waugh 2003-02-01 23:46:50 UTC
For rescue situations, use the rescue CD.  There's no reason to statically link
these binaries.