kernel.x86_64 0:2.6.22.4-65.fc7 (fails)

[Justin Conover]

On 8/29/07, Dave Jones <davej at redhat.com> wrote:
>
> On Tue, Aug 28, 2007 at 02:38:37PM -0500, Justin Conover wrote:
>
> > I am un-perplexed.... Looks like it is time for a relabel.
> >
> >
> > [root at echelon ~]# sestatus
> > SELinux status:                 enabled
> > SELinuxfs mount:                /selinux
> > Current mode:                   enforcing
> > Mode from config file:          enforcing
> > Policy version:                 21
> > Policy from config file:        targeted
> > [root at echelon ~]# setenforce 0
> > [root at echelon ~]# yum update
> > Running Transaction
> >   Installing: kernel                       #########################
> [1/3]
> >   Installing: kernel-devel                 #########################
> [2/3]
> >   Installing: kmod-nvidia                  #########################
> [3/3]
> >
> >
> > # yum remove kernel-devel-2.6.22.4-65.fc7 kernel-2.6.22.4-65.fc7
> > <BLAH>
> > Running Transaction
> >   Removing  : kmod-nvidia                  #########################
> [1/3]
> >   Removing  : kernel                       #########################
> [2/3]
> >   Removing  : kernel-devel                 #########################
> [3/3]
> >
> > Removed: kernel.x86_64 0:2.6.22.4-65.fc7 kernel-devel.x86_64 0:
> > 2.6.22.4-65.fc7
> > Dependency Removed: kmod-nvidia.x86_64 0:100.14.11-1.2.6.22.4_65.fc7
> > Complete!
> > [root at echelon ~]# sestatus
> > SELinux status:                 enabled
> > SELinuxfs mount:                /selinux
> > Current mode:                   permissive
> > Mode from config file:          enforcing
> > Policy version:                 21
> > Policy from config file:        targeted
> > [root at echelon ~]# setenforce 1
> > [root at echelon ~]# sestatus
> > SELinux status:                 enabled
> > SELinuxfs mount:                /selinux
> > Current mode:                   enforcing
> > Mode from config file:          enforcing
> > Policy version:                 21
> > Policy from config file:        targeted
> >
> > [root at echelon ~]# yum update
> > <BLAH>
> > Running Transaction Test
> > Finished Transaction Test
> > Transaction Test Succeeded
> > Running Transaction
> >   Installing: kernel                       #########################
> [1/3]
> > FATAL: Could not open '/boot/System.map-2.6.22.4-65.fc7': Permission
> denied
> >   Installing: kernel-devel                 #########################
> [2/3]
> >   Installing: kmod-nvidia                  #########################
> [3/3]
> > FATAL: Could not open '/boot/System.map-2.6.22.4-65.fc7': Permission
> denied
> >
> > Installed: kernel.x86_64 0:2.6.22.4-65.fc7 kernel-devel.x86_64 0:
> > 2.6.22.4-65.fc7 kmod-nvidia.x86_64 0:100.14.11-1.2.6.22.4_65.fc7
> > Complete!
>
> Fascinating.  I wonder what caused your /boot to become unlabelled.
> ls -Z / should show boot as ..
> drwxr-xr-x  root root system_u:object_r:boot_t         boot/
>
> can you double check that?
>
>         Dave
>
> --
> http://www.codemonkey.org.uk
>
> --
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
>

I did already run a relabel
drwxr-xr-x  root root system_u:object_r:boot_t         boot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-test-list/attachments/20070829/82c8d3ca/attachment.htm>