But the init logic (line 365+) below implies that a more appropriate message was intended, but went arwy:Searching for Puppy files in computer disk drives...
/bin/sh: can't access tty; job control turned off
Code: Select all
if [ "$PUPSFS" = "" ];then
echo -en "\\033[1;31m" >/dev/console #31=red
echo -n "pup_${PUPPYVERSION}.sfs not found. Dropping out to initial-ramdisk console..."
/bin/echo -e "\\033[0;39m" >/dev/console
exec /bin/sh >/dev/console 2>&1
else
appears in the bootinit.log file. Furthermore, the "exec /bin/sh" line appears to be generating the "/bin/sh:..." error message, instead of restoring a color (I assume).pup_300.sfs not found. Dropping out to initial-ramdisk console...#
Correcting that logic to display the "not found" line would save people much frustration when they cannot get Puppy to boot (probably due to a typo in a menu.lst file).
Richard