Well, it's like this..... nothing in this life is had for free. You generally pay to gain knowledge and experience. Whether that "payment" is in points, dollars, time, or blood, you have to pay for it somehow. Nobody seems to be interesting in spending any of those things, or anything else. They want it to "just work". There are OSes that "just work" MacOSX is constantly claiming to "just work". And you want to know a secret? OSX was going to get ZFS a few years ago. They decided to yank it out though(even after publicly announcing it) and allegedly it was because they determined they could never simplify ZFS down enough to make it work for everyone. There was too many requirements, too much knowledge that would be required, and they expected too many complaints. Since OSX is all about stuff 'just working' that didn't fit their mantra, so they yanked it.
FreeNAS is also quite powerful with what it chooses to do. And just like when you invent some new dangerous weapon that could be used against another country(for example, nuclear weapons) a certain amount of responsibility is expected. If that responsibility is unacceptably high, then feel free to not accept that responsibility. My mom, who is no IT person by any stretch of the imagination, could never ever get FreeNAS to work. It doesn't matter how much documentation you provide. I know *plenty* of IT people that don't fare much better than my mom, yet they are employed. Many people I've seen in the forums over my 2+ years here I've had to shake my head and wonder how they ever got the idea they should work in IT because they shouldn't.
The fact that you work in IT is no promise that if you can't get it that its not your fault. It's proof that you've likely been generally successful at solving problems in IT relative to other people. To my mom, if you know how to change the font in Microsoft Word you are "an IT guy". But we all know that because you can change the font in Word does NOT make you "an IT guy".
FreeNAS may be more than you are ready to take on. There's no shame in admitting defeat. But, it is pretty shameful to assume that a project must have poorly written documentation and help is expected if *you* can't figure it out. It makes you look like an idiot because you aren't even willing to admit the fault may be your own.
As for the ticket, I do have to say "lol". Not because of the subject matter but because you can create a wiki account and add it yourself in less time than it took to write that ticket. It is open source documentation so that others that find info that is important can add it(pending approval from an editor of course).
FreeNAS is also quite powerful with what it chooses to do. And just like when you invent some new dangerous weapon that could be used against another country(for example, nuclear weapons) a certain amount of responsibility is expected. If that responsibility is unacceptably high, then feel free to not accept that responsibility. My mom, who is no IT person by any stretch of the imagination, could never ever get FreeNAS to work. It doesn't matter how much documentation you provide. I know *plenty* of IT people that don't fare much better than my mom, yet they are employed. Many people I've seen in the forums over my 2+ years here I've had to shake my head and wonder how they ever got the idea they should work in IT because they shouldn't.
The fact that you work in IT is no promise that if you can't get it that its not your fault. It's proof that you've likely been generally successful at solving problems in IT relative to other people. To my mom, if you know how to change the font in Microsoft Word you are "an IT guy". But we all know that because you can change the font in Word does NOT make you "an IT guy".
FreeNAS may be more than you are ready to take on. There's no shame in admitting defeat. But, it is pretty shameful to assume that a project must have poorly written documentation and help is expected if *you* can't figure it out. It makes you look like an idiot because you aren't even willing to admit the fault may be your own.
As for the ticket, I do have to say "lol". Not because of the subject matter but because you can create a wiki account and add it yourself in less time than it took to write that ticket. It is open source documentation so that others that find info that is important can add it(pending approval from an editor of course).
