Hi, I'm thinking to try the latest beta, but have no test machine, would following script work on the new beta, see attachment? Or is it too many bugs on the latest beta to have this on a "live" server?

 

//Peter

script.zip

If you're not developing for it, don't try it unless you have a test machine.

Hi, I'm thinking to try the latest beta, but have no test machine, would following script work on the new beta, see attachment? Or is it too many bugs on the latest beta to have this on a "live" server?

 

//Peter

It depends on your tolerance for change, and and tolerance for bugs in the user-interface.  The beta-2 is far better than beta-1, but there's still at least one issue in setting up share permissions on the flash drive.

 

Since the ownership/permissions on the files and directories must be set with a one-time utility on 5.0 after you upgrade, it will be one of the items you'll need to un-do if you attempt to revert to a 4.5.X version of unRAID.  This is not a big problem, bit you must keep it in mind since you might find that the permissions would prevent you from opening the files on 4.5.X until returned to their older values.

 

Other than that, there is nothing in those three scripts that will be incompatible with the newer version of unRAID.

I don't know if any of us trying it have added a new drive, or dealt with the re-construction of a failed thrive through the new interface... You might need to deal with that issue if you are planning to add a new drive in the near future or have a disk fail.  Again, it is not that it does not work, but that it is not well tested under the new interface by many other users.

 

Joe L.

The ownership/permission changes are backward compatible with 4.5.6.  If you run 'NewPermissions' on 5.0 & later revert to 4.5.6, everything will still work, but if you subsequently create new files under 4.5.6, you will have to run 'NewPermissions' again when you upgrade to 5.0 again.  Make sense?

The ownership/permission changes are backward compatible with 4.5.6.  If you run 'NewPermissions' on 5.0 & later revert to 4.5.6, everything will still work, but if you subsequently create new files under 4.5.6, you will have to run 'NewPermissions' again when you upgrade to 5.0 again.  Make sense?

tom,

 

What about file/directories copied using "rsync --daemon" invoked on the new server when on the 5.X series.  (copying from the older server running 4.5.6)?

The ownership/permission changes are backward compatible with 4.5.6.  If you run 'NewPermissions' on 5.0 & later revert to 4.5.6, everything will still work, but if you subsequently create new files under 4.5.6, you will have to run 'NewPermissions' again when you upgrade to 5.0 again.  Make sense?

 

Hi, Thanks ,will see if I test the new beta, perhaps I wait to newer build