[BusyBox 0000594]: /etc/rc.d/rc.sysinit can't work

bugs at busybox.net bugs at busybox.net
Thu Dec 15 05:36:42 UTC 2005


The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=594 
====================================================================== 
Reported By:                robin
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   594
Category:                   Other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             12-10-2005 09:38 PST
Last Modified:              12-14-2005 21:36 PST
====================================================================== 
Summary:                    /etc/rc.d/rc.sysinit can't work
Description: 
execv function can't execute /etc/rc.d/rc.sysinit shell script when system
boot
platform x86 & mips
OS:Linux 2.6.8 or  2.6.11
====================================================================== 

---------------------------------------------------------------------- 
 robin - 12-13-05 01:08  
---------------------------------------------------------------------- 
Execv function invoke '/etc/rc.d/rc.sysinit'.Error Message is
'/etc/rc.d/rc.sysinit: Exec format error'.
At the same time execv function invoke '/bin/ap',it was runing fine.
The 'ap' function is call shell script '/etc/rc.d/rc.sysinit'. 

---------------------------------------------------------------------- 
 landley - 12-14-05 21:36  
---------------------------------------------------------------------- 
This works for other people, so it's 99% likely that your environment is
screwed up somehow.  But you didn't give us anything to go on.  Where is
the script you're trying to run?  Does the shell it point to exist, and
can that shell load its shared libraries?  Did you edit the sucker on
windows and accidentally stick an ascii 13 at the end of the line so it's
trying to run "/bin/sh\r" instead of "/bin/sh"?

How do we reproduce the failure you're seeing? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-10-05 09:39  robin          New Issue                                    
12-10-05 09:39  robin          Status                   new => assigned     
12-10-05 09:39  robin          Assigned To               => BusyBox         
12-10-05 09:57  robin          Issue Monitored: robin                       
12-13-05 01:08  robin          Note Added: 0000759                          
12-14-05 21:36  landley        Status                   assigned => closed  
12-14-05 21:36  landley        Note Added: 0000779                          
======================================================================




More information about the busybox-cvs mailing list