Bug 155436

Summary: mkinitrd can produce unusable images
Product: Red Hat Enterprise Linux 4 Reporter: Martin Poole <mpoole>
Component: mkinitrdAssignee: Peter Jones <pjones>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: rafiq_maniar, wwlinuxengineering
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: 2005-05-03 18:56: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 Martin Poole 2005-04-20 11:31:27 UTC
Description of problem:

mkinitrd honours umask.

If the user has set a umask in their .bashrc (or even globally) that quashes the
execute bit then the binaries copied to the image lose their execute bit and
fail to run at boot.

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


How reproducible:


Steps to Reproduce:
1. put 'umask 0111' in /root/.bashrc
2. create an initrd
3. boot it.
  
Actual results:

no modules load

Expected results:

modules should load.

Additional info:

script should probably force umask, and possibly even use -p on the copies so
the datestamps match original (allows easy matchup).

Comment 1 Peter Jones 2005-05-03 18:56:50 UTC
-HEAD now sets umask itself.