Salut,
ce n'est pas vraiment un problème que je rencontre, mais c'est plutôt que je ne sais pas comment faire, le READMElinux26, ils disent de tapper la commande :
./configure
bien sur je sui en root et dans le bon dossier, la réponse est :
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-1.2868.fc6/source... yes
kernel build source in /lib/modules/2.6.18-1.2868.fc6/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
donc là si j'ai tout compris, tout est ok, apres je ne comprend pas trop le readme, je me permet de poster la partie concernant Linux :
==============================
README for Linux 2.6 kernels
==============================
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 exported
If 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:
$ patch /lib/modules/`uname -r`/build/fs/dcache.c patch_dpath.diff
The location of your Linux kernel source code may be different.
Once you have patched the fs/dcache.c file, you can rebuild and install your
kernel and kernel modules.
If your GNU/Linux distribution doesn't export the __d_path() function, you
may want to write them email suggesting that this function be exported in
the next release.
Note: As a workaround, Dazuko now offers the configuration option
--disable-chroot-support. This will disable Dazuko from trying to
resolve chroot'd filenames, thus making Dazuko safe for SMP kernels
that do not export __d_path(). However, if this option is used,
registered applications will only be able to work with chroot'd
filenames if they resolve the filenames from within userland. If
the application you plan to use with Dazuko requires handling
chroot'd filenames (and you have an SMP kernel that cannot export
__d_path()), then you should contact the application developer to
make sure it supports this option.
(bon en fait j'ai mis l'intégralité du readme 😉)
quand je tappe :
grep __d_path /proc/kallsyms
je n'ai aucune réponse particulière, le terminale me remet
utilisateur@nom-de-la-machine
et je peut tapper de nouvelles commandes, mais je ne sais pas quoi tapper.
J'ai essayer (en suivant la logique du readme) la commande suivante :
patch /usr/src/kernels/2.6.18-1.2868.fc6-i686/`uname -r`/build/fs/dcache.c patch_dpath.diff
mais la reponse est :
patch: **** Can't find file /usr/src/kernels/2.6.18-1.2868.fc6-i686/2.6.18-1.2868.fc6/build/fs/dcache.c : No such file or directory
et là je dois avouer que je ne comprend pas du tout (déjà que j'ai pas compris ce que j'ai fais précédement... sauf le ./configure)
Voila, j'espère avoir été clair dans mes explications (ce qui n'est pas toujours évident), et merci de m'aider.
@ + et Bonne année!
Bryan