Bug 435750

Summary: [PATCH] fix booty default file params on ia64 elilo
Product: [Fedora] Fedora Reporter: Doug Chapman <dchapman>
Component: bootyAssignee: Peter Jones <pjones>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 9CC: dcantrell, katzj
Target Milestone: ---   
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-27 16:08:49 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:
Bug Depends On:    
Bug Blocks: 163350    
Attachments:
Description Flags
set default params to 755 for elilo on ia64. none

Description Doug Chapman 2008-03-03 17:59:26 UTC 
Description of problem:
The fat filesystem does not have the concept of an execute bit nor
user/group/other in file params.  Recently a kernel change was made to enforce
this.  This causes chmod to fail on fat filesystems with any perm other than 755
or 555.

This caused booty to fail when it tried to do a chmod 600 on elilo.conf and
hence caused anaconda to crash.  This patch sets the params to a valid 755 on
ia64 installs.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Doug Chapman 2008-03-03 17:59:26 UTC 
Created attachment 296647 [details]
set default params to 755 for elilo on ia64.
Comment 2 Jeremy Katz 2008-03-03 19:01:05 UTC 
Does elilo not support passwords?
Comment 3 Doug Chapman 2008-03-03 19:38:19 UTC 
(In reply to comment #2)
> Does elilo not support passwords?

No elilo does not have password support.
Comment 4 Doug Chapman 2008-03-03 19:56:37 UTC 
Also, if elilo did support passwords we still would not be able to make it
non-readable since it is on a vfat filesystem.  Since fat doesn't have the
concept of a read bit it is always readable.  In the past doing a chmod to make
it non-readable appeared to work however once the system rebooted or the inode
was just read in again the file would revert back to the 0755 permissions.
Comment 5 Jeremy Katz 2008-03-04 03:22:04 UTC 
Fixed in git
Comment 6 Bug Zapper 2008-05-14 05:44:55 UTC 
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping