That's why the smart money is based on node-based storage: Multiple boxes that are interchangeable. It's a shameless product plug, but I work for Isilon Systems, and our solution is that the whole system is considered replaceable: We don't sell a configuration that doesn't allow you to yank an entire box transparently. A drive failure is rebuilt and ready for swapping as soon as it comes up: Most of our admins don't know about disk failures until their data is already reprotected.

Granted, our smallest config is 9TB; We're somewhat overkill for a home user. But if you need a company-wide NAS...

Commodity hardware, standard networking (Gig and 10Gig Ethernet frontend, Infiniband backend), and a very smart filesystem (Capable of protecting from up to 4 simultaneous whole-node failures) == a killer combination; It takes some seriously bad luck for data-loss to become a problem.

Fixed that for you :)

In addition to the issues artemis67 pointed out above, the GPL requires that you redistribute not only binaries, but the source to build those binaries.

Generally, that should be obvious based on what it's returning; If it's returning a copy, it should return a static User object, if it's returning a the original it will be a pointer to it. That's also what the documentation is for, in the event that it is returning a reference to a copy it needs to make clear that it's the caller's job to destroy the object. In Java, you refer to that as an "implementation detail"; In C++, you generally realize that /you are the implementer/ and need to pay attention to details.

Those that operate above the normal legal standards also need to be held to a higher moral standard: Being a military serviceman is not something to take lightly. I don't agree with all the policies (Seriously, no porn? Yeah, right, get right on that), but the reduced freedom of speech, the need to verify potential associates, etc, are part of the tradeoffs that come with the position.

Thank you, though, for making them.

Yes, mapping a windows network share would indeed cause autorun.inf to be read.

Isn't everyone?