On Mon, Oct 10, 2011 at 3:14 PM, Lance Jump <[email protected]> wrote: > Yes, the symlink is there. As a test, I changed the script name in the > inittab file and and I get an error: > > VFS: Mounted root (nfs filesystem) on device 0:13. > Freeing init memory: 156K > init started: BusyBox v1.18.4 (2011-10-07 23:48:57 GMT) > can't run '/etc/rc.d/startupx': No such file or directory > > This suggests two things. First, it is finding the correct file (without > the change) since I get no error and, second, that something is properly > processing inittab. What I can't tell is whether the message is coming from > the shell processor or something else (Busybox init?).
Interesting... As a somewhat quick sanity check, if you build BusyBox 1.17.3 and apply the proper patches from that generation of the embedded book, do you get the same operation? Apply both the fixes and config patches at the beginning of the BusyBox build, section 7.4. As I have output from a successful boot with this version, that might be a good sanity check. https://gist.github.com/874183 Downloads you'll need: http://busybox.net/downloads/busybox-1.17.3.tar.bz2 http://svn.cross-lfs.org/svn/repos/patches/busybox/busybox-1.17.3-fixes-1.patch http://svn.cross-lfs.org/svn/repos/patches/busybox/busybox-1.17.3-config-1.patch If you grab a copy of the git repo for the embedded book, you can checkout commit 1b109e6eae092a7a1fe4a5580683e93507fa7e02 to get the old instructions at the last point where BusyBox was version 1.17.3. -Andrew _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
