drawz

aitch nailed it, but I feel like we are reinventing the wheel here. There are countless other distros out there with a variety of different ways to manage packages, dependencies, and plugins. Several of these, such as OpenELEC, OpenWrt, Synology, etc. are very specialized and limited distros. There much be a way we can work off of what they are doing. In theory, using the official Slackware package repository and one of the compatible package managers is the way to go, BUT we are still based on Slackware 13.1, which is now 3 years old. Critical security fixes are available (incorporated in unRAID though??), but it's not exactly up to date, which may cause problems when trying to keep plugins current. Ok, maybe it's not so simple....that upgrade to Slack 14.0 Tom mentioned would help. Really, if we could get on board with unRAID running on any modern distro that stays up to date in general, it would be a lot easier to do all of this. In fact, it would also make Tom's life easier with regards to hardware support and kernel updates... In conclusion - this needs to wait for 5.1 or 5.2, as much as I want it.

HDD temps will be read from SMART data directly off the HDD, so no need for that module (at least for HDD temp).

Given the confusion over secure/private/public and the fact that it apparently varies depending on protocol, it would seem to make sense for Tom to make these distinctions more obvious in the webGUI. Just a thought...

Any tips on getting hardware sensors working with simplefeatures 1.0.11? Anyone have temperature-based fan speed control working?

You could save a fair amount on the CPU IMO - an Ivy Bridge Celeron or Pentium is around $60. At idle, which is where your CPU will spend most of it's time, it will use the same or less power compared to the low voltage Sandy Bridge you listed. Not sure if Plex can take advantage of hardware video transcoding offered on the i3 (and missing on the Pentium/Celeron?). You could save even further by going with an Atom or AMD Brazos CPU if you won't be transcoding. You really don't need that much CPU power for a NAS that's mostly serving files and downloading a few things. Don't forget to factor in an unRAID license, which you'll need for more than 3 drives.

Great idea to put it on git an let the community contribute (not that I can do so, but there are some smart cookies on this board).

Greg's post: http://www.kroah.com/log/blog/2013/08/04/longterm-kernel-3-dot-10/ and then from: http://kernelnewbies.org/LinuxChanges seems like some of the changes might be relevant for this project I posted such suggestion just last week, and people threw stones at me. Yet now they seem to be OK with fiddling with the GUI for what could be another year or so. Seriously, that's beyond me. I think most in the webgui thread now agree that Tom should wait until 5.1 to implement the new GUI.

Now that I think about it, I agree with going 5.0 final without the new GUI. You could then start the 5.1 beta/RC process with the new GUI and package manager. If these are almost ready, there's no reason we can't have a fairly quick 5.1 final release. If they take more time, then so be it. There's no reason we can't have more frequent finalized updates!

Ooooh looks really nice! Would love to see this become reality.

Had this problem on my Acer EasyStore H340 (originally a Windows Home Server box). I never could get it to shutdown and stay that way under unRAID, but WHS was fine. I tried every possible setting in the BIOS, updated the BIOS, ran headless, with and without a keyboard/mouse, with and without ethernet, and never reached a solution.

Right this will be addressed post-5.0. The plan is to integrate lighty, which won't be difficult. Work which has already been done in the webGui and which is taking place now will make for a smooth transition, but I can't delay the release for this. Great! Glad to hear this is on the roadmap. And agree 100% that this should not delay 5.0 final.

This is a very important statement and glad to hear it from you Tom. This separation will potentially allow for some creative work to be done on the GUI in plugin form. Also glad to see a simple version of simplefeatures becoming the stock GUI. That said, all the commentary about GUI speed is interesting. This new GUI shouldn't slow things down much, especially with modern browsers and modern PCs. What I do find somewhat painful is the fact that emhttp seems to be single threaded and there seem to be all kinds of things that can stall it in the background. If a responsive GUI is considered important, I think optimizing emhttp would go the furthest toward this goal.

It's not the pretty UI in and of itself that causes problems. It is the fact that SimpleFeatures was developed separately from the rest of unRAID. Now that Tom is in charge of this new UI, it should stay in sync with updates to unRAID. Perhaps more importantly, it should be "officially supported" and Tom is on the hook for compatibility/stability issues related to it. This is a good move forward.

Yay!

Running out of RAM perhaps?

geeze, ok back to my question on SMB and to confirm what the issue is... I'd like to hear from others reguarding my speeds and expectations. I do not know if I have a SMB issue. There is a dedicated thread for that topic. By contributing, you may be able to help solve the problem (if there even is one). It sounds to me like this is not a common problem and may not be one at all.

And therein lies the rub. UnRAID is a fully capable Slackware distribution, but unfortunately, Slackware doesn't have the best package management system. This makes dealing with dependencies much more challenging than a typical Debian derivative (e.g. Ubuntu).

One of the reasons I don't consider it a high priority to get Airprint running on unRAID is the availability of cheap, easy, and reliable alternatives. Arch Linux ARM running on a Pogoplug, which only costs $20, is one of those alternative solutions. A Raspberry Pi could do the same. There are write ups out there for both.

thanks overbyrn!

This is the key statement. See: http://en.wikipedia.org/wiki/AirPrint I would love to see a plugin for unRAID to enable this functionality. For me, it's not quite worth the effort to go through the manual install just for Airprint, but I wouldn't mind having it.

Here is the only thread I can find that suggests there is an SMB performance issue: http://lime-technology.com/forum/index.php?topic=28664.0 However, if you look in that thread, the latest posts indicate there probably is NOT an issue. It seems a little more research is needed, but so far Tom has not acknowledged an issue from what I can tell.

I actually don't even see this listed in the "issues list" section of the forum. Has Tom acknowledged it? What work has been done to investigate it? Does it happen to everyone? Is it select hardware? When these issues are worked on publicly, with Tom and the forum members who are effected, it seems that solutions are found much more quickly.

Warfare and redundant servers ... not exactly the same mission set. No lives are at stake with unRAID. All the more reason to accept good enough for now with plans to improve in the future. I would argue this principle is valid in many many aspects of life. The ramifications of inaction are still not the same unless there is a current bug putting us all at risk The ramifications of SMB running a little slow for a few people are pretty minimal. Sometimes you just have to accept that it will never be perfect and move on. There is always one more bug or just one more feature. Perhaps this proverb is more appropriate: Perfect is the enemy of good. http://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good

Warfare and redundant servers ... not exactly the same mission set. No lives are at stake with unRAID. All the more reason to accept good enough for now with plans to improve in the future. I would argue this principle is valid in many many aspects of life.

If the hold up is just documentation, how about launching only to forum members before making it fully public? You could also tap the forum for help with documentation. Alternatively, launch 5.0 final to Plus/Pro licensees with the caveat that there is only forum support available for now. Both of these strategies limit the number of upgrades happening at the same time, making support more manageable (especially in the absence of full documentation). This would allow plugin authors and other advance users to get on with things.