Bug 1030691

Summary: Permissions at root "/ of root filesystem 755 vs 555
Product: [Fedora] Fedora Reporter: Doug Mitchell <redhat>
Component: initscriptsAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, dshea, g.kaviyarasu, johannbg, jonathan, jsynacek, lnykryn, msekleta, ovasik, plautrba, systemd-maint, vanmeeuwen+fedora, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:55:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Doug Mitchell 2013-11-14 23:23:56 UTC
Description of problem:
On a new install of Fedora 20 Beta, there is a mismatch between the actual permissions and those in the filesystem package

Version-Release number of selected component (if applicable):
filesystem-3.2-19.fc20.i686

How reproducible:
Perform clean (non-upgrade) install of Fedora 20

# stat /
  File: ‘/’
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: fd00h/64768d    Inode: 2           Links: 18
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)

# rpm -qf / 
filesystem-3.2-19.fc20.i686

# rpm -qlvf /
dr-xr-xr-x    2 root    root                        0 Aug  7 02:10 /

Comment 1 Doug Mitchell 2013-11-14 23:49:25 UTC
*** Bug 1030692 has been marked as a duplicate of this bug. ***

Comment 2 Ondrej Vasik 2013-11-15 09:57:18 UTC
Filesystem owns root filesystem dir as  %dir %attr(555,root,root) / in file section. Based on the dependency resolving, it should be one of the first packages on the system. If your system has the root filesystem dir created with / , it is probably somehow mishandled during the system installation - I assume this might be caused by some installer things. Reassigning to anaconda - I can't fix anything here from filesystem package perspective.

Comment 3 David Shea 2013-11-15 19:20:25 UTC
Anaconda leaves the permissions the way that filesystem set them. You can see this by booting a freshly-installed system with systemd.unit=emergency.target: / has mode 0555. Booting into the rescue, multi-user or graphical targets will change the mode on / to 0755.

Comment 4 Jan Synacek 2014-10-07 09:24:56 UTC
This is technically a duplicate of bug 1149419, but I'll leave it open, because it's another product version.

Comment 5 Fedora End Of Life 2015-05-29 09:46:02 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-06-29 12:55:38 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.