"Bummer, could not run '/etc/init.d/rcS': No such file or directory"

[Juliana Su]

Hi All,

Thanks for your quick responses. Yes, /etc/init.d/rcS does exist and it 
is executable. I even removed the original rcS and created a new 
executable one to do a simple echo and exit, like Hinko suggested, but I 
still get the "Bummer" error. At first, I had actually forgotten to set 
the execute bit on the new rcS and received a "Bummer, could not run 
'/etc/init.d/rcS': Permission denied" error. I fixed that, though, by 
doing a chmod 755 on it. By the way, I am using an older version of 
BusyBox, version 1.2.1 to be exact.


-Juliana


Hinko Kocevar wrote:

> Juliana Su wrote:
>   
>> Hi,
>>
>> Is anybody familiar with the "Bummer, could not run '/etc/init.d/rcS': 
>> No such file or directory" error message?
>>
>> Here's the last bit of my kernel boot log:
>>
>> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>> EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
>> VFS: Mounted root (ext2 filesystem).
>> Mounted devfs on /dev
>> Freeing unused kernel memory: 120k init
>> Bummer, could not run '/etc/init.d/rcS': No such file or directory
>>
>>     
>
> /etc/init.d/rcS is default sysinit script that is run once the kernel is finished booting. /etc/init.d/rcS is called from init process as a last action (see init.c).
> Error would suggest that you do not have the /etc/init.d/rcS in place.
>
> Put /etc/init.d/rcS on your FS with this content:
> #!/bin/sh
> echo Exec $0 script..
> exit $?
>
> and make it executable. Upon boot this script should be run and message printed in the console. Of course for production /etc/init.d/rcS should do a bit more work..
>
> HTH,
> Hinko
>   

Denys Vlasenko wrote:

> On Thursday 26 June 2008 12:32, Hinko Kocevar wrote:
>   
>> Juliana Su wrote:
>>     
>>> Hi,
>>>
>>> Is anybody familiar with the "Bummer, could not run '/etc/init.d/rcS': 
>>> No such file or directory" error message?
>>>       
>
> You run busybox older than 1.3.0, The message is coming from here:
>
>                 /* Now run it.  The new program will take over this PID,
>                  * so nothing further in init.c should be run. */
>                 execv(cmdpath, cmd);
>
>                 /* We're still here?  Some error happened. */
>                 message(LOG | CONSOLE, "Bummer, could not run '%s': %m", cmdpath);
>                 _exit(-1);
>         }
>
> Obviously, /etc/init.d/rcS does not exist at that moment.
> --
> vda
>   

Lombard, David N wrote:
> On Thu, Jun 26, 2008 at 06:16:30AM -0400, Juliana Su wrote:
>   
>> Hi,
>>
>> Is anybody familiar with the "Bummer, could not run '/etc/init.d/rcS': 
>> No such file or directory" error message?
>>     
>
> It's in busybox-1.01's init.c, and gone no later than 1.8.2 (I only those two and 1.10.0).
>
> The execv of that path failed. Does /etc/init.d/rcS exist? Is it executable?
>
>