You are not logged in.
I got the dazuko PKGBUILD from aur and tried to compile but I got this error:
=======================
Configuration summary
=======================
module events = ON_OPEN ON_EXEC
devfs support = no
rsbac support = no
stacking support = yes
local __d_path() = no (using chroot events, see README.linux26)
module debug = no
library 1.x compatibility = yes
make -C /lib/modules/2.6.17-ARCH/build include/linux/version.h include/asm scripts
make[1]: Entering directory `/usr/src/linux-2.6.17-ARCH'
rm: cannot remove `.kernelrelease': Permission denied
make[1]: *** [.kernelrelease] Error 1
make[1]: Leaving directory `/usr/src/linux-2.6.17-ARCH'
make: *** [dummy_rule] Error 2
==> ERROR: Build Failed. Aborting...
any suggestions?
Offline
It tries to install files directly on the system. I'll check it out.
Offline
Any workaround?
Offline
The problem is that it uses the Makefile in /lib/modules/2.6.17-ARCH/build. So it tries to create files there. I don't have much experience in building the kernel or modules for it. A workaround would be to not use the makefile and to directly compile the dazuko with gcc but I don't know which gcc options to use.
Offline
I think I did the PKGBUILD some month ago. I since forgoted it because its not that usefull. It permit usage of "on access" virus scanner (clamav), but since their is no linux virus...
Yesterday I wanted to use dazuko, so I've re-checked the PKGBUILD, but I think it won't be possible to use it with Arch's kernel. dazuko depends on a function not exported to modules in 2.6 kernels. Also, it doesn't work well with SMP kernels (Arch's stock kernel is SMP, I think...)
In order to lookup full file paths (even in chroot environments), Dazuko
uses the kernel function __d_path(). Unfortunately this function is no
longer exported to kernel modules in the Linux 2.6 kernel.Dazuko has its own copy of this function but unfortunately it is only safe
for UP (uni-processor or non-SMP) kernels. This is because the real __d_path()
function uses a kernel lock, which is not available to kernel modules.If your kernel is not configured as SMP, then it is safe to use Dazuko's
copy of the __d_path() function. This is default.If your kernel is SMP then you should _not_ use Dazuko's copy of __d_path().
You can disable Dazuko's local copy of __d_path() by configuring Dazuko with:$ ./configure --disable-local-dpath
Since Dazuko requires __d_path(), your kernel will have to export it if you
disable the local copy. Some GNU/Linux distributions have a modified kernel
that does export this function. The "vanilla" Linux kernel does _not_ export
this function. You can check if your kernel exports this function with:$ grep __d_path /proc/kallsyms
The results can be interpreted as:xxxxx T __d_path <= exported
xxxxx t __d_path <= not exportedIf you are running an SMP kernel and __d_path() is not exported, then you
will have to modify your kernel source code to export the symbol and
rebuild your kernel. The modification is very simply and can be made by
using the included patch to modify the fs/dcache.c file. Here is an example:
So it would recquire a kernel rebuild to make it works...
Offline