That's the advantage of an appliance like FreeNAS. There is a CLI, but it's essentially a menu based interface to get the base system up and running. From that point, everything is configured via the web interface.
All hail the Great Capacitor Brand Finder
In my opinion, offline servers are the best. Think of the security risk if you connect a server to the internet with FreeNas or the like. And then later when your version gets old and no longer works online, you have to worry about the new version having compatibility with your dated hardware.
I'd say build your server with whatever hardware parts that suit your needs (from any hardware generation), then use your OS of choice, and keep the server hidden away and offline. I'm the kind of person who, when upon finding the ideal technology, I keep it around forever and collect spares of the exact parts that I would need to replace. I don't see myself forgetting XP anytime soon.. 😀
Dedicated Windows 95 Aficionado for good reasons:
http://toastytech.com/evil/setup.html
No reason you can't run FreeNAS in an isolated network.
All hail the Great Capacitor Brand Finder
wrote:In my opinion, offline servers are the best. Think of the security risk if you connect a server to the internet with FreeNas or the like. And then later when your version gets old and no longer works online, you have to worry about the new version having compatibility with your dated hardware.
I'd say build your server with whatever hardware parts that suit your needs (from any hardware generation), then use your OS of choice, and keep the server hidden away and offline. I'm the kind of person who, when upon finding the ideal technology, I keep it around forever and collect spares of the exact parts that I would need to replace. I don't see myself forgetting XP anytime soon.. 😀
FreeBSD, and by extension anything based on it, has very good legacy hardware support (as long as you have no exotic hardware, that is), better than Linux, and unlike Linux they are not likely to scrap it. See the FAQ and hardware compatibility lists (here's the one for FreeBSD 11.0R, the latest version of FreeBSD). It's not Windows.
And if you want security above everything else, use OpenBSD. Which also has good legacy hardware support.
wrote:FreeBSD, and by extension anything based on it, has very good legacy hardware support (as long as you have no exotic hardware, that is), better than Linux, and unlike Linux they are not likely to scrap it. See the FAQ and hardware compatibility lists (here's the one for FreeBSD 11.0R, the latest version of FreeBSD). It's not Windows.
And if you want security above everything else, use OpenBSD. Which also has good legacy hardware support.
Agreed, and Linux has better legacy support than Windows (modern releases). That puts FreeBSD at the top of the heap.
All hail the Great Capacitor Brand Finder
wrote:Renaming a few long named files can't be too bad after all.
I found it highly annoying though. At least if it's the same long file name problems as your long file name problems, I sometimes run into this when copying over entire directories and then getting dozens of "too long file name"-errors and have to check every single file to make sure renaming it doesn't break anything.
wrote:In my opinion, offline servers are the best. Think of the security risk if you connect a server to the internet with FreeNas or the like. And then later when your version gets old and no longer works online, you have to worry about the new version having compatibility with your dated hardware.
I'd say build your server with whatever hardware parts that suit your needs (from any hardware generation), then use your OS of choice, and keep the server hidden away and offline. I'm the kind of person who, when upon finding the ideal technology, I keep it around forever and collect spares of the exact parts that I would need to replace. I don't see myself forgetting XP anytime soon.. 😀
I have the same opinion about it, preferring offline servers not attached to the internet at any time.
