This error message appear, when I using command mkinitrd...
I am so suprise, "/bin/true" is a module?
If you known, could you tell me?
I too got a similar error when I started to install the new 2.6.16 kernel on my PC. It said No module /bin/true for Linux 2.6.16, and reference to mkinitrd was mentioned.
If anyone has a solution for this please let me know!!
What distros were you guys using, and what arch? Off the top of my head I'd suspect a build environment problem, check that you have the latest build tools. Other then that, sounds like a funky distro thing.
I am using a intel p4 pc. 2.4 works wonderful on it. I tried to install 2.6 and was working well, before i installed modules_init_tools for the qm_functions problem. Then this problem of /bin/true stated and i am not able to install linux kernel automatically on grub.
In case you need any more information please do not hesitate to ask.
open file /sbin/mkinitrd
for n in $scsimodules; do
# for now allow scsi modules to come from anywhere. There are some
# RAID controllers with drivers in block/
#for n in $scsimodules; do
i'm now studying linux
mt too same problem
but i can solve my problem
thank you ^^
I am running Debian and it appears that /bin/true belongs to the package coreutils. I can't explain why you have that issue, but I don't know what distros you are running and I think you should first verify that /bin/true exists and is functional. Good luck!
I am having the same problem...I was upgrading a 2.4.20-8 kernel coming with the RH9 distribution to a 2.6.10 kernel...does that help???
When it says "there is no /bin/true" it should say "while executing the initrd (initial ram disk) that makes the root filesystem accessible (which of course does contain a /bin/true), someone did not make an initrd that contains /bin/true.
I don't know why all distros insist on building a generic kernel with all options selected, and then using an initrd to detect hardware necessary to mount the root filesystem. They must know that the average person wants to throw in CD's and hit enter as a skillset for IT, like in Windows. For commercial Linux, this is their value proposition. For community Linux, why do we want to scare newbies away with the initrd issue?
Since you want "executive summary" -- you cannot upgrade generic (distro kernel) with initrd without learning many things. You are upgrading because old 2.4 kernel cannot support new hardware. But an old "stable" Linux system with all modules 2-3 years old has a lot of vulnerabilities and will rot away. So it is a problem to want to solve your web server based on 3-4 year old "stable Linux distro" serving 1,000,000+ users/second by moving all the rotten old code to new faster hardware, which of course cannot use your ancient ~2.4.19 "golden" kernel, even with the latest patch.
You can solve all this problem by installing recent distro with web server. But probably some manager who knows everything tells you no, just upgrade minimum ("new hardware will solve this performance problem"). There is no answer to manager who is idiot other than he lose his job.