[mk01]

@dharmabm

you would be surprised how often we answer question
- why i'm not allowed to write to my shared usb hdd ?

and answer is "there is a button in xbian-config XBMC"

(this just reminded me that I wanted to follow-up enable/disable checkbox in xbian-config XBMC to allow auto-resolution change on start/stop vnc-server. user's idea & most work done and result is amazing. normally RPI is too slow to manage resolution above 720x480 with xbmc and vnc. with this "feature" as soon as vnc is started, resolution is changed. on vnc stop, resolution is changed back!)

((so no restart, config.txt updates etc))

---

@dharmabm

as I see topic upgrading to RC1.

I have the feeling I didn't post this but generally I would recommend installing xbian\* updates first, then the rest (upstream) packages.
the reason for this is that on most upstream issues (problems with startup scripts / debian helper scripts / or even conflicts like lately the python2.7 stuff) there are fixes implemented in xbian-update (or relevant packages). having them deployed BEFORE the other broken packages are installed will simply provide seamless non interrupted install like the bug would not be existing.

for instance the autofs package problem. autofs package installation was starting the service at the end of dpkg install. starting the service was dependent on present "autofs4" filesystem support. but because xbian-kernel with autofs4 support wasn't yet installed, autofs installation never finished apt-get was blocked. in case kernel would be updated first (among other xbian packages) at the time of autofs post install configuration autofs4 support would be already present and "stuck" would be avoided.

so maybe it would be worth provide this info in one sentence under the "updating xbian" paragraph.