New Release - My Book Live Firmware Version 02.11.09-053 (4/23/12)

[adachim]

>I'm getting a lot of errors during install procedure.

It appears this new firmware introduced a module or two with which aptitude/apt-get can not keep dependency in check.

In my case, attempt to update php5 modules failed and created "broken" modules.

There might be a way to fix this but I am not a linux person so I eneded up running a fake upgrade to undo my doing.

[Myron]

Oh my....   Break php5 and you break CakePHP.  Break CakePHP and you break the Web/Dashboard UI. 

Break php5 and CakePHP and the support people at Western Digital will have a bit of a giggle....   Maybe....

[adachim]

Myron,  I wrote this on other thread but a highlight for me on this new firmware is that php5 does not have mysql support built-in anymore.  Mysql-server itself will still install without any error  however the default php5 install  can no longer talk to mysql.   Up until last firmware upgrade I was using apache2, php5, mysql combinatin  to set up a prototype web server on which I could run database driven cms such as wordpress, Joomra , modx and drupal.  All bets are off now.  

I know WD did not intend this device for such a usage (Speed of Web service with all those extra is not that great with this hardware, only adequte for prototype site usage I believe) 

Fortunately I have another MBL that I did not update the firmware. it will stay that way unless somebody figure out  the way to resolve this but I will not hold the breath for that.

[Myron]

I see W.D. point of view.and to be honest and fair, looking through all these threads of the tails of woe, the configuration for the MyBook Live, as you also state was designed for a specific set of purposes.

One of the main purposes is storage of files, to do this accurately and reliably..

Installing other stuff that changes the configuration of the Linux OS is just the same as playing Russian roulette.

Personally, I don't have a problem using software on the MBL that does not alter the configuration of the OS or interfere with W.D's customisations AND do not automatically start when the MBL starts,  Like on my MBL I've stopped netatalk but when it's rebooted netatalk will start because maybe netatalk is needed to be accessible during the OS's boot-up sequence.

Yes, there are a few annoyances like not being able to set permissions for the Public older.  It seems stuck in to allow everyone access.  That does not need software to correct and is safe to implement and if it causes a problem, to reverse.

For all who are interested. . . .

Edit /etc/trustees.conf, find the entry for Public and change that to:

[/dev/sda4]/shares/Public:admin:RWBEX:*:CU

Do the same change to /tmp/trustees.mod but do NOT change anything below ###DENY LIST.

Invoke the command: settrustees -f /tmp/trustees.mod

All of a sudden you find that only the user admin has access to the Public share and none of the system software within the MBL are affected!   WOOHOO!!!!

Point is, if it causes problems in the future, do the same again except change admin for a * and it's back to exactly the way W.D. set it.  100% reversible customisation.

Actually, I'm impressed by this so elegant change because even VSFTPD is denied access to the Public directory if the logged in user is not admin.

All good fun! 

[daveande]

Successfully upgraded via the dashboard.  8 minutes from start of download till completion of upgrade.  Blinking green LED then persisted for quite a while (possibly an hour).  Can anyone explain what's going on during this time?

Cheers.

[Myron]

Indexing media and transcoding stuff.

[daveande]

Thanks.

Even though the drive's content was constant, pre and post firmware update?

[Myron]

I think after a firmware update databases and stuff are re-built. An errr on the side of caution by W.D.

[daveande]

Understood.  Thanks Myron.

[Myron]

Makes sense.  Consider this . . .   Some time between firmware updates maybe the MBL has suffered an accidental or deliberate power loss while in the middle of writing something to disc?  It's an example.  Maybe something happened to only get a fraction of the stuff on the disk indexed and transcoded.

Thing is, the MBL is designed to be plugged in and left turned on so it's not like there is a computer with a 800 Watt power supply that has to be left on for several hours or days wasting power indexing and transcoding.

If Twonky is left like it is to watch in real-time then only changes are worked on.

Bit like performing an initial synchronisation of files between two hard drives.   First time it's painful because everything has to go across and that could take hours or even a few days.  After that frequent synchronisation tasks take a few minutes.  I guess it's the same if someone has a large media collection on their MBL, where the firmware upgrade resets the databases and Tronky has to trawl through everything.

It becomes an issue when nothing is indexing or rebuilsing anything but the green activity LED keeps on flashing and not stopping to then go to blue if the power saving option is disabled.