My pogo corrupts the root file system within a number of days of being up, requiring a manual fsck in another computer before it stands a chance of booting to the point I can login remotely. I'm curious as to what you're doing to avoid this. Do you just reboot your pogo every few days and it isn't a problem? Perhaps I'm purchasing the wrong brand of USB keys? Thus far I've had the problem on AData, Kingston, and Transcend flash drives.
My solution, though not pretty (or automatic) is to remount root ro, and only mount it rw when installing packages or editing files. This allows me to run my pogo for much longer periods of time without rebooting, which I like to do
tmpfs 62M 92K 62M 1% /tmp
tmpfs 62M 48K 62M 1% /var/run
tmpfs 62M 4.5M 57M 8% /var/lib
tmpfs 62M 35M 28M 56% /var/log
tmpfs 62M 64K 62M 1% /var/spool
tmpfs 62M 3.4M 59M 6% /var/cache
I read the arch linux bug about read-only root, but putting "ro" in /etc/fstab for / does nothing for me, root is still rw when the pogo boots. My hack is to rename the above folders and mount them as tmpfs, so that any writes to them are done in memory and not to the USB key. This is incredibly hacked, and requires manual intervention after each reboot. /etc/fstab isn't doing the trick for creating these before daemons start.
Any suggestions? I'd really like a viable read-only root option so my plug doesn't require babysitting.