/sbin/modprobe is not reinstalled in final system if you have already installed it from chapter 7.

[ken]

I had some oddities with modprobe not working in the final system, or only working sometimes - tracked that to whether /tools existed, found that modprobe was liked against tools. Also discovered that if I reinstalled after booting the final system, it didn't overwrite the old modprobe so I had to delete that.

Steps to reproduce: follow the 'boot' method, or at least build and install module-init-tools from chapter 7. In the final system, review the module programs.

Here are the results of 'ls -l' and 'ldd /sbin/*mod*' on a current multilib build, halted after installing modprobe in the final system:

-rwxr-xr-x 1 root root  153412 May 17 21:12 /sbin/depmod
-rwxr-xr-x 1 root root    8723 Jun  9 03:43 /sbin/generate-modprobe.conf
-rwxr-xr-x 1 root root   24668 May 17 21:12 /sbin/insmod
-rwxr-xr-x 1 root root 3159745 Jun  9 03:43 /sbin/insmod.static
lrwxrwxrwx 1 root root      12 Jun  9 03:43 /sbin/lsmod -> ../bin/lsmod
-rwxr-xr-x 1 root root  137646 Jun  9 03:43 /sbin/modinfo
-rwxr-xr-x 1 root root  109890 May 17 21:12 /sbin/modprobe
-rwxr-xr-x 1 root root   35474 May 17 21:12 /sbin/rmmod
/sbin/depmod:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libgcc_s.so.1 => /tools/lib64/libgcc_s.so.1 (0x0000040000038000)
        libc.so.6 => /tools/lib64/libc.so.6 (0x000004000005b000)
        /tools/lib64/ld64.so.1 (0x0000040000000000)
/sbin/generate-modprobe.conf:
        not a dynamic executable
/sbin/insmod:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libgcc_s.so.1 => /tools/lib64/libgcc_s.so.1 (0x0000040000038000)
        libc.so.6 => /tools/lib64/libc.so.6 (0x000004000005b000)
        /tools/lib64/ld64.so.1 (0x0000040000000000)
/sbin/insmod.static:
        not a dynamic executable
/sbin/lsmod:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libc.so.6 => /lib64/libc.so.6 (0x0000040000038000)
        /lib64/ld64.so.1 (0x0000040000000000)
/sbin/modinfo:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libc.so.6 => /lib64/libc.so.6 (0x0000040000038000)
        /lib64/ld64.so.1 (0x0000040000000000)
/sbin/modprobe:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libgcc_s.so.1 => /tools/lib64/libgcc_s.so.1 (0x0000040000038000)
        libc.so.6 => /tools/lib64/libc.so.6 (0x000004000005b000)
        /tools/lib64/ld64.so.1 (0x0000040000000000)
/sbin/rmmod:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libgcc_s.so.1 => /tools/lib64/libgcc_s.so.1 (0x0000040000038000)
        libc.so.6 => /tools/lib64/libc.so.6 (0x000004000005b000)
        /tools/lib64/ld64.so.1 (0x0000040000000000)

So, insmod.static, lsmod, modinfo are the correct versions but depmod, insmod, modprobe, rmmod are the temporary versions linked against /tools.

Suggested solution: rm -rf /sbin/depmod /sbin/insmod /sbin/modprobe /sbin/rmmod before running 'make install' in chapter 10.

[manuel@…]

In jhalfs we are using the next install comman when doing ICA/farce builds:

make INSTALL=install install

That was adopted also by the LFS SVN book to solve modul0e-init-tools reinstallation issues.

[ken]

Thanks, I missed that at the time it happened. Will add it to CLFS.

[ken]

Fixed, r1761.