I posted that if anyone wants to work on a fork then they need to do it somewhere else and I even defined fork to be clear on the meaning of the word. Obviously, you have a problem comprehending what you read.
Right.
I made a ton of compelling arguments why technically, support wise, reliability / integrity wise (metadata from file all the way up to the block device level, dual / triple parity), functionality wise, investment wise and even financially in a business case for you and everyone else a few posts back.
Are you actually going to refute any of those, contribute to the conversation or just stick to person attacks and defying the multiple warnings from the Mods?
Here is yet another reason why people might want to use an "unRAID fork"...
Over the next couple of years we are all going to be converting TBs of Media files from x.264 to x.265 and free up 40% (or more) of space those files use today and still retain the same audio / video quality.
I'm going to go out on a strong limb and guess that many users would like to take advantage of this and not have to invest money into into expanding / adding / increasing the hard drives they have.
In the "unRAID fork", you wouldn't have to pray / hope / wait that someone writes a plugin for a webGUI that does not exist and may or may not work. In the "unRAID fork", you could install it TODAY / NOW... ONCE (Hell I when even write a step by step guide with screenshots) and use a GUI from the "unRAID fork" on your Windows / Mac machine to queue up your entire library and start the process in the background / walk away while everything is done on the "unRAID fork" Server utilizing the horsepower (64 Bit, all the memory, CPUs, etc.) it has.
Since you probably have no idea technically how to do this and I know damn well you will not write a plugin for a GUI that unRAID can't install.... Are going to wait / hope / pray that someone post instructions how to install the required software in Slackware so you can do it command line? Do this over the network where the conversion takes place on your laptop?
Current development of unRaid OS will continue:
- webGui improvements
- implementation of features long on the todo list such as alerts, btrfs cache pool, plugin manager, etc. etc.
Next, using components from 64-bit unRaid OS, for example, emhttp, as a starting point, there will be
a "fork" project with these goals:
- let key unRaid components work smoothly in other distros (eg, emhttp)
- creation of a rpm (or other package type) of these key components
unRaid-fork will permit you to install onto say CentOS or ubuntu, etc. Someone could also generate,
for example, a CentOS-unRaid install disk.
Several concepts change with the unRaid-fork:
- you have a system disk to manage (actually you are just managing the base distro as intended)
- some things might no longer be directly controlled by emhttp, for example, the networking protocols,
in particular Active Directory and AFP.
- the idea is that emhttp becomes in some ways like mdadm in that it lets you configure assigned storage
devices and manage unRaid-style shares.
- there will probably be several more conceptual changes
It could very well end up this version of unRaid becomes entirely open source, but this is not
the decision at present.
You have been attacking me non-stop for days and you are not the one who is privy to conversations that Tom and I are having and where I am assisting. You are making of fool of yourself at this point so please stop or go NAS Distro hopping until you find one that wants to remain stuck in 2005.
Either that or you need to do a much better job or getting users in your camp and start a email campaign to Tom on how detrimental it is to have an OPTIONALLY and completely SEPARATE unRAID version that you can choose to install or not. Otherwise, you soon are going to be a very unhappy customer.
Let's leave telling them to go elsewhere up to Tom. We've made him aware of this.
Your point is duly noted. Please stop.
Tom, Mods, me and others have connected the dots for you... Do we need to color it in for you too?
No comments:
Post a Comment