lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Sun, 5 Nov 2006 23:21:28 +0000
From:	Joachim Wagner <>
Subject: PROBLEM: make install doesn't create target directory (2.6.19-rc4)

Hi there,

make install of kernel 2.6.19-rc4 doesn't create a sometimes necessary 
directory in /lib/modules/. I attach my command history (ls and many "less 
readme" removed) and the grep^C .config file for reproduceability. However, 
even with these, I cannot reproduce the error on a different system, see 

Hope this makes any sense and is useful for the final release,

Error message:
[root@...alhost linux-2.6.19-rc4]# make install
sh /extra/build/src/linux-2.6.19-rc4/arch/i386/boot/ 2.6.19-rc4test 
arch/i386/boot/bzImage "/boot"
WARNING: Couldn't open directory /lib/modules/2.6.19-rc4test: No such file or 
FATAL: Could not open /lib/modules/2.6.19-rc4test/modules.dep.temp for 
writing: No such file or directory
No modules available for kernel "2.6.19-rc4test".
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2

After manually creating the target directory, make install runs normally, and, 
after make modules_install, the kernel works fine for me. (Actually solving a 
problem of 2.6.18-1.2200.fc5 with do_IRQ stack overflows. Very happy about 

Pentium 4 2.66GHz, Fedora Core 5, kernel 2.6.18-1.2200.fc5, gcc 4.1.1, GNU 
Make 3.80, everything run as root.

Unable to reproduce the error on a Pentium 4 2.40GHz, SuSE 10.0, kernel 
2.6.13-15.11-default, gcc 4.0.2, GNU Make 3.80 (zcat 
~/Documents/config_c_only.txt.gz >.config, make menuconfig, then just exit). 

Proposed solution:
Adding an mkdir -p ("no error if existing, make parent directories as needed") 
shouldn't harm the normal case and fix this problem in the rare case.

Download attachment "config_c_only.txt.gz" of type "application/x-gzip" (7726 bytes)

View attachment "history.txt" of type "text/plain" (553 bytes)

Powered by blists - more mailing lists