[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Dazuko-help] Install to CentOS5 issues
From: |
John Ogness |
Subject: |
Re: [Dazuko-help] Install to CentOS5 issues |
Date: |
Tue, 05 Feb 2008 19:30:26 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) |
On 2008-02-05, Dimitri Yioulos <address@hidden> wrote:
> Now, I'm trying to install dazuko-2.3.3 on a CentOS 5.1 box, which
> is using the SMP kernel, for the same reason. As a first step, I
> ran "grep __d_path /proc/kallsyms"; it returned "c0483463 T
> __d_path". According to README.linux26, that means that __d_path()
> is exported. However, when I try to run the installation, I get the
> following:
>
> address@hidden dazuko-2.3.3]# ./configure && make && make install
> checking host system type... Linux
> checking for make utility... ok (make)
> checking for C compiler... ok (cc)
> kernel source in /lib/modules/2.6.18-53.1.6.el5/source... yes
> kernel build source in /lib/modules/2.6.18-53.1.6.el5/build... yes
> acquiring Linux kernel code configuration... ok
> checking if Linux is RSBAC patched... no
> checking if devfs is enabled... no
> discovered host system... Linux (2.6.18)
> checking if security module support is enabled... yes
> verifying capabilities are not built-in... built-in :(
> error: capabilities are built-in to the kernel:
> you will need to recompile a kernel with capabilities
> as a kernel module
Dazuko uses the LSM interface for capturing file access events.
There is another module that uses this interface as well. It is called
"capability". If it is compiled statically in the kernel, then it
prevents Dazuko from loading. The configure script has detected that
this module is indeed compiled statically in your kernel.
Information about exactly this issue can be found in the FAQ:
http://www.dazuko.org/tconf.shtml#CAPABILTIES-BUILTIN
John Ogness
--
Dazuko Maintainer