From: Dave H. <dhy...@gm...> - 2006-09-20 20:13:29
|
Hi, > I have a prototype of eink and can tell you why this happens. > Your prototypes have a little, but important bug. > > Your images are delivered with enabled logging. Having logging enabled isn't enough to cause the problem. Normally the log files goto /var/log. So the real question is where is /var/log mapped to? On a default gumstix build if you do "ls -l /var" you'll see something like the following: # ls -l /var drwxr-xr-x 2 root root 0 Aug 9 2006 lib lrwxrwxrwx 1 root root 4 Aug 9 2006 lock -> /tmp lrwxrwxrwx 1 root root 4 Aug 9 2006 log -> /tmp lrwxrwxrwx 1 root root 4 Aug 9 2006 pcmcia -> /tmp lrwxrwxrwx 1 root root 4 Aug 9 2006 run -> /tmp lrwxrwxrwx 1 root root 4 Aug 9 2006 spool -> /tmp lrwxrwxrwx 1 root root 4 Aug 9 2006 tmp -> /tmp drwxr-xr-x 3 root root 0 Feb 28 2006 www which means that anything being written into /var/log will goto /tmp which according to the output from "mount": # mount /dev/root on / type jffs2 (rw) proc on /proc type proc (rw) /sys on /sys type sysfs (rw) udev on /dev type ramfs (rw) devpts on /dev/pts type devpts (rw) /dev/mmcblk0p1 on /mnt/mmc type vfat (rw,sync,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1) tmpfs on /tmp type tmpfs (rw) /tmp is in fact a tmpfs, which means it comes from RAM, and not the JFFS2 filesystem. Of course, if tmp isn't mounted, or /var/log isn't symlinked to it, then the above wouldn't hold. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |