Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 155436 - mkinitrd can produce unusable images
mkinitrd can produce unusable images
Status: CLOSED RAWHIDE
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: mkinitrd (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
David Lawrence
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2005-04-20 07:31 EDT by Martin Poole
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-03 14:56:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Martin Poole 2005-04-20 07:31:27 EDT 
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 14:56:50 EDT 
-HEAD now sets umask itself.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.