Friday, February 13, 2015

More Musings on Raspbmc

This a follow up to this post.

I spent a couple of hours trying to figure out why the shared database had stopped working... The problem? My raspberry pi versions had gotten out of sync. One updated, the other didn't.

Given that Raspbmc uses it's very own idea of an update system, this isn't trivial. So, my number one tip: If you are running multiple pi's and they are using a shared database, and it's all working fine, turn off updates.

If your Raspbmc versions have gotten out of sync, you're going to need to ssh into your Raspberry Pis and run the following:

 sudo rm /scripts/upd_sys/*.sh  
 sudo wget http://svn.stmlabs.com/svn/raspbmc/release/update-system/getfile.sh -P /scripts/upd_sys  
 sudo wget http://svn.stmlabs.com/svn/raspbmc/release/update-system/cdn_env_prep.sh -P /scripts/upd_sys  
 sudo rm /scripts/upd_hist/kver  
 sudo rm /scripts/upd_hist/xbmcver  
 sudo rm /scripts/upd_hist/svcver  

After that reboot. It may be tempting to do it from ssh, but it seems better to do it from the GUI. You'll need to do this on EVERY Raspbmc Pi running Raspbmc using the same database in order to get their versions all to the current version. After that, turn off updates.

As great as Raspbmc is, it is a broken system... Their reinventing of the wheel isn't really doing anyone any favours. What would make sense is providing their own apt repository and providing a solid upgrade path from Rasbian...

No comments:

Post a Comment