update_percent_complete 25
date >> /mnt/us/c.log
uname -a >> /mnt/us/c.log
update_percent_complete 50
bbconfig 2&>1 >> /mnt/us/c.log
ln -s /opt/amazon/screen_saver /mnt/us/screen_saver 2>&1 >> /mnt/us/c.log
date >> /mnt/us/c.log
update_progressbar 100

Result:

Thu Mar 19 22:18:33 UTC 2009
Linux kindle 2.6.22.19-lab126 #3 PREEMPT Mon Mar 2 12:26:35 PST 2009 armv6l unknown
Thu Mar 19 22:18:33 UTC 2009

The ln -s didn't work, and whats worse, failed silently. Any idea why?

--C

The ln -s didn't work, and whats worse, failed silently. Any idea why?

--C
Because the FAT filesystem doesn't support symbolic links.

Oh, DUH. Of course. Also, the source revealed that BBCONFIG isn't enabled in busybox.

I wonder what would happen if I deleted /opt/amazon/screen_saver, and replaced it with a symlink to something in /mnt/us. /opt isn't FAT right? (I should just check that when I get home).

When I say "what would happen" what I really mean is: would this approach be ignored by the amazon updates? After some investigation it seems that before an official kindle update runs it checks to see that files its about to update haven't changed. I'm betting that it doesn't check directories in the same way, though I've noticed a few odd things about busybox's tar implemementation that would make me not be surprised if a later amazon update simply put it back the way it was.

I wonder what would happen if I deleted /opt/amazon/screen_saver, and replaced it with a symlink to something in /mnt/us. /opt isn't FAT right? (I should just check that when I get home).
Yeah, this was discussed very briefly here (http://www.mobileread.com/forums/showpost.php?p=383386&postcount=109).