Jesse Stevens

I have a question regarding some items not starting for 1 hour after booting up. What is the reason behind this? Is it simply that they begin with cron, and it takes that time to count 1 hour out? Could we instead have a script include this initial starting on boot? Or is it something more like a way to save resources on booting up? If so, could we start in the background a secondary script that begins with a few minutes of sleep?

Is there any chance that the fork that has appeared on github that allows the latest builds of this project to run on chumby classics could be brought back into the fold? I have one running here quite well with this version (based on v34), and it appears to be pretty solid - they're such cute little things it'd be a shame to have them left behind. I keep seeing so many of them, and have recently been given even more. Jesse

Hi folks, I've been pretty impressed with this development, and have actually used the fork someone has made to make the latest versions of this still run on the Chumby Classic which I've successfully been using (it uses swap to help boost its tiny ram). I noticed that there was some discussion sometime ago about DLNA back in 2013, and at that time it wasn't possible for it to be a target (am I using the right terms here?) so that a remote device could send sound to pop out of the Chumby - with discussion...