[jfoutz]

> It is easier to copy a solution to a linux problem from stack overflow than to read the FreeBSD handbook, understand the problem and fix it.

I'm (a little) ashamed to admit tech support via trolling. Linux sucks because you can't even [whatever].

It is nice to get a quick response of "it's just [whatever], noob".

Although, that was a last resort. I've met a couple of people that reread man pages every year, i've never quite picked up that practice. Once you get the hang of parsing the super terse examples, man is pretty great.

[jlg23]

> It is nice to get a quick response

Indeed, it is. But one won't learn anything of value. One just learns the solution to a very specific problem. If one chooses to learn the basics, more often than not one will decide that it is quicker to dive into the problem and fix it than to "troll" tech support.

[CJefferson]

Often finding an answer gives me useful knowledge I can then use in other circumstances, but I can't possibly know every corner of my OS.

Recently I found my only machine running FreeBSD (as a testing machine) was kernel crashing occasionally. On a whim I googled '<machine name> kernel crash', and found a page which discussed an extra linux boot-time flag I had to add, to disable some feature of the graphics card. I couldn't figure out how to do the same thing on FreeBSD, so just switched to Debian, and added the magic option. No more crashes. Now the machine runs a FreeBSD VM on top of linux.

[jfoutz]

Well, this specific case is trolling zealots, not tech support.

I mostly agree with you, but there are some unique facts that, back in the day, you just sort of had to know. something like

    echo 1 > /proc/sys/net/ipv4/ip_forward

You know exactly what you need to do, but haven't memorized the name of the bit to twiddle to get the behavior you want. Now there are, of course, tools to configure these sorts of things. More importantly, google and stackoverflow help immensely with this kind of thing.