Red Hat Bugzilla – Bug 441750
ia64 selinux: Properly install files and symlinks
Last modified: 2012-10-16 04:21:03 EDT
Description of problem:
On ia64 systems the bootloader of choice is EFI. EFI
requires a VFAT partition where kernel images, etc., are placed.
The current install command, "make install" executes /sbin/installkernel in
order to correctly place the bootimage, etc., in the INSTALL_PATH directory
(/sbin/installkernel is part of the mkinitrd package).
Currently, on ia64, the INSTALL_PATH directory is /boot. This is incorrect,
and should be /boot/efi/efi/_vendor_specific_/ . For example, in the case
of RedHat INSTALL_PATH should be /boot/efi/efi/redhat/.
The patch below modifies the /sbin/installkernel script so that
a) Creates LINK_PATH which indicates which directory the soft links should
be created in. By default this is set to /boot, which is where the links
are currently being created.
b) Correctly creates the links in $LINK_PATH and not in $INSTALL_PATH, and
c) Creates the $KERNEL_NAME soft link once.
Verified on ia64 and x86_64.
I hope that we can get a mini-review and resolve any issues here so that I can
push this upstream.
Version-Release number of selected component (if applicable): Pretty much every
Steps to Reproduce:
1. execute make install in the kernel sources
vmlinuz, System.map are placed in /boot.
Expected results: vmlinuz, System.map should be in /boot/efi/efi/redhat
Need to add /boot/efi/efi/redhat/System*.map as a system_u:object_r:system_map_t:s0
Fixed in selinux-policy-2.4.6-133.fc9.noarch
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.