McHan, William D ERDC-ITL-MS Contractor wrote: > Andrea, > > I figured out what was keeping the ramdisk from loading. The syntax for the > ramdisk size was out of place in the original syslinux.cfg file. I had to > make sure it was under the systemimager label like this:
[snip] correct! as specified in the comments: # Add the following to the append line above to increase the size of your tmpfs # filesystem. About 100MB larger than your image size should suffice. # # tmpfs_size=800M # ramdisk_size=80000 ... maybe we should replace "append" with "APPEND line" to be more explicit and prevent uncommenting the lines outside the systemimager label. > However, now when BusyBox begins, it can not find the boel_binaries.tar.gz > file. I looked in the path it calls, and the file doesn't exist (which is the > error.) Apparently I haven't run something that creates the file. What > routine or script creates those files / binaries on the SI server? boel_binaries.tar.gz is downloaded from the image server using rsync (if you didn't set any option to use another transport). You should check if your clients can communicate to your image server on port 873. See also: http://wiki.systemimager.org/index.php/Troubleshooting#BOEL_binaries_can.27t_be_loaded If you want to look at the code for details, search the get_boel_binaries() routine in /etc/init.d/function in your initrd.img. Regards, -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
