> Basically anything that you would want a computer to do. Some people will be okay playing uncompressed WAV and Sun AU files cat'ed to the audio device. Other

> Basically anything that you would want a computer to do. Some people will be okay playing uncompressed WAV and Sun AU files cat'ed to the audio device. Other people are going to want to play other audio formats. This kind of reasoning is a bit reductionist. Sure, as long as my computer has a compiler and basic interfaces, I can "do anything that you would want a computer to do", given <x> amount of work on my part to re-implement the functionality I want. Unless I want to write my own MP3 decoder, though, I'll need to install 3rd party software from ports. > Before that computer starts interacting with other computers over the network however, I generally have to ask it to. That's GOOD. Right, it is -- but most linux distributions also don't start a lot of network services. Linux has had a few more TCP/IP stack vulnerabilities than OpenBSD, but not many. And of course (mostly) Linux distros uses OpenBSD's SSH package. Your empty Linux install and empty OpenBSD install will, from the network, appear mostly identical. And the bug in Firefox that pops a shell on your system likely won't be either Linux or OpenBSD's fault, but Firefox's.