I myself have been on V3.04 since having a harrowing experience in upgrading to V3.04 in which it frozed after updating. It was the first time I did a 40 second reset on my device with it going into a white light mode with no SSH ability because the device was busy initiating. The device took 3 hours to initiate and at the end I was glad it was back and I’ve only rebooted the device twice for fear that the device will remained locked in a white light mode.
I know I could SSH into it in previous versions while white light because I had to with the USB attached; I had to kill off two jobs in order to fix the USB attached problem. However some “know it all” user here on the forum told me that I could not have SSHed into any of the device while white light in all versions and in fact he also informs us that all versions after was just perfectly stable and he has no problems with V4 himself and therefore nobody else should have any problems and it would be a user error.
I have checked and I’m fairly sure that in /etc/init.d/bootmisc.sh the whole routine for DELAYLOGIN did not exist before verision 3.04. I am sure that particular user will check and will prove me wrong.
Anyways, after restoring my setup, I vow that unless they fix sleep and the plethora of problems that seems to come with V4, I would not upgrade and this is looking to be more and more that I would be stuck at V3.
However there is a good possibility that I will never upgrade for the following reasons:
unable to upgrade from 3.04 to versions 5 due to needing to incrementally upgrade through all previous versions.
white lighting and lock ups
reseting all my shares and setups
I am afraid that one day the cloud.app for my iphone/ipad will be upgraded to be incompatible with my Cloud that is stuck at V3.04. When that day happens, I will be moving on to another product.
Alright, now that I had my say, I can go for breakfast