unRAID Server Release 5.0 i386 Available


limetech

Recommended Posts

  • Replies 345
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

I noticed a little typo in the release notes:

If you are currently running unRAID Server OS release 5.0-rc16a:

----------------------------------------------------------------

- Copy over 'bzimage' and 'bzroot' from the release zip file to your Flash and then reboot your server.

 

I assume from Tom's original post it should be rc16c.

 

To paraphrase some of the Apollo 11 moon landing chatter....

......you got a bunch of guys about to turn blue here. We're breathing again. Thanks a lot!

 

That's one small step.........  ;D

Right, sorry a typo.  Fixed in the first post of the thread, but will show up like this in the download.  Will fix for inevitable 5.0.1  :P

Link to comment

Download

 

The "new" (not really new) webGui still has some rough cosmetic edges and so I'm taking the advice of several people and releasing 5.0 'stable' with the "stock" webGui that's been in the 5.0-beta/rc series all along.  There is an upgrade utility on the Utils menu that will download the latest webGui development located on github.  As of time of this post, I have not yet done a new 'push' - that will come after this 5.0 release is available since some features depend on minor changes to the base unRAID OS code.

 

Thanks Tom for all your hard work !! I have been waiting patiently for this release.

Link to comment

Do I need to do anything about the new webgui before I install 5.0 final? Or is it safe to keep it?

 

Running 16c atm.

Nothing special.  Give it a whirl, it's easy to remove, just delete:

plugins/webGui-latest.plg

plugins/webGui-latest.txz

and reboot the server, and back to stock webGui.

 

What's out there now on github is not the latest 'push', that will come very soon.

Link to comment

Tom, why do we see no emotion from you in this announcement? Do you not see this as a big milestone? You just pumped out the announcement like another RC release. Are you happy? How do you feel now that 5 is at stable/final status? Is there anything you would like to say to us?

 

More specifically and getting back to this release, is there a reason it still has changes between the last RC and this, yet has become the new 5 final/stable? Is that not a bit risky?

Link to comment

unRAID Server Version 5.0 Change Log

====================================

 

Changes from 5.0-rc16b to 5.0 'stable'

--------------------------------------

- emhttp: return correct MIME type for javascript (application/javascript)

- emhttp: get rid of "Welcome" page, make "Main" the default start page

- emhttp: added Release Notes page under Utils/Upgrade menu

- emhttp: added Upgrade webGui page under Utils/Upgrade menu

- mover: include rsync 'O' option in order to prevent directory modification time update

- shfs: fix bug where latest directory mtime not being returned

- slack: remove /var/log tmpfs entry in /etc/fstab since this is done in rc.S

 

Changes from 5.0-rc16b to 5.0-16c

---------------------------------

- shfs: correct share free space calculation again

- slack: update to fuse-2.9.3 to fix "transport endpoint not connected" issue

- slack: increase some system limits as follows:

  ulimit -n 40960

  ulimit -c unlimited

  ulimit -l unlimited

  ulimit -s unlimited

 

Is the above bold bits right? We went from B to C to B to stable? Or is that a typo?

Link to comment

think i found a bug.

I followed the upgrade instruction for 5.0rc16..  copy over bzimage / bzroot. rebooted.. in the ui, (http://tower/Utils/ReleaseNotes) the release notes are for 5.0rc11.

The release notes page just outputs the contents of the readme.txt file in the root of the flash device, so, yes, for upgrading from -rc16c you should also copy over 'readme.txt' from the zip file.

Link to comment

unRAID Server Version 5.0 Change Log

====================================

 

Changes from 5.0-rc16b to 5.0 'stable'

--------------------------------------

- emhttp: return correct MIME type for javascript (application/javascript)

- emhttp: get rid of "Welcome" page, make "Main" the default start page

- emhttp: added Release Notes page under Utils/Upgrade menu

- emhttp: added Upgrade webGui page under Utils/Upgrade menu

- mover: include rsync 'O' option in order to prevent directory modification time update

- shfs: fix bug where latest directory mtime not being returned

- slack: remove /var/log tmpfs entry in /etc/fstab since this is done in rc.S

 

Changes from 5.0-rc16b to 5.0-16c

---------------------------------

- shfs: correct share free space calculation again

- slack: update to fuse-2.9.3 to fix "transport endpoint not connected" issue

- slack: increase some system limits as follows:

  ulimit -n 40960

  ulimit -c unlimited

  ulimit -l unlimited

  ulimit -s unlimited

 

Is the above bold bits right? We went from B to C to B to stable? Or is that a typo?

Typo.

Link to comment

Tom, why do we see no emotion from you in this announcement? Do you not see this as a big milestone? You just pumped out the announcement like another RC release. Are you happy? How do you feel now that 5 is at stable/final status? Is there anything you would like to say to us?

I'm Dufnering.

 

More specifically and getting back to this release, is there a reason it still has changes between the last RC and this, yet has become the new 5 final/stable? Is that not a bit risky?

No.

Link to comment

Hooray! Will try it out in the next couple days and most likely purchase a plus license.

 

Another 4.7 user here. Looking forward to upgrading now that we've gone stable.

 

 

ROFL, its been stable for months and months and months and months and ..... funny how one little word can affect people's perceptions.

 

 

Link to comment

Hooray! Will try it out in the next couple days and most likely purchase a plus license.

 

Another 4.7 user here. Looking forward to upgrading now that we've gone stable.

 

 

ROFL, its been stable for months and months and months and months and ..... funny how one little word can affect people's perceptions.

Perception is reality!

 

For me, it is the fact that plugins will have a stable platform (in the sense that it is not changing) upon which they can be developed. It is my belief, although it may be wrong, that the moving target of the RCs where things constantly break with the latest update has really hindered progress.

 

I did successfully run the RC with no significant issues related to unRAID itself. I just wasn't willing to invest hard earned cash given the above.

 

Not trying to start anything and most definitely appreciate 5.0 final. I will leave it at this and don't feel the need to further justify why I consider final important in this case.

Link to comment

Thanks and congratulations Tom, IMO I think you made the right decision to release just what most have been waiting for all this time and that proved to be stable by all the ones testing it... you have now all the time to look at new gui improve it etc.

 

Btw, I think I did found a (returned) bug... see issues forum... maybe you should (please don't take this as criticism but as a suggestion for future...) have made one last rc, before release 5.0 final, to make absolute sure all 100%... then just rename rc to final as-is, with zero changes... but anyway it's not the end of the world and other small bugs may eventually arise and new versions should come, etc... ;)

Link to comment

Aside from having the ability for apps to use more memory is there any advantage to x64.

 

post about slackware going 64bit and why it matters: http://www.linux-mag.com/id/7502/

 

now with regards to unraid.. if your running 2gb of ram or less.. you deff wouldnt want a 64bit os (takes up more ram, run 32bit in 64bit requires some extra libs, etc).

now for the majority going forward, most people will want/have to run a 64bit os.. since 4gb+ ram is becoming common.. more people expect a device to do more than one thing (running apps?).. having the extra ram can always be helpful..  64bit for the masses is also mainstream.. so bugs/updates will prob come first for that as the userbase for the 32bit is shrinking. now there will probably be some pitfalls with switching.. legacy drivers? new bugs?

Link to comment
Guest
This topic is now closed to further replies.