Since most business still run Windows, you need to find people with enough skills to fix the same problems over and over. Printing, Outlook, and antivirus/antispyware are the base standards. Ask if they know what Active Directory is, and what its used for. The best question, imho, is still to ask what is the quickest way to find out which version of Windows a user is running. (winver.exe...btw). If they can answer any questions about those, that will filter out most of the riff-raff.
The big difference is that OpenBSD it uses GCC 2.9X. Linux ports usually won't work. I haven't looked at 3.7 - but this was the case in 3.6 and prior versions. Compile from source, and there are no functional differences. There are also very few "wrapper" scripts to start and stop daemons, which major linux distros have.
Once you get past that - you probably won't notice you're on a BSD box.
Knowledge in hardware is paramount. Classes in hardware should progress from electrial diagrams to logic circuits to chip assembly to assembly language to device drivers to operating sytems. By learning hardware, you learn why pointers work, how ethernet carries voltage across a wire, and why there are limits to ethernet length, and that intel really had figured out the Pentium chip as far back as the 8086.
Hardware knowledge really makes you more of a generalist in the computer industry. You can network computers, configure RAIDs and SANs, and trace cables with a tone generator.
You may not be able to write code with a hardware degree, but you know the capabilities of the hardware and why Windows95/98/ME were never really a true operating system (they were disk access systems that ran programs)
This is a common experiment in undergrad physics. It proves that light acts both as a wave and a particle. When light acts as a wave, it interferes with itself, and thus cancelling itself out. The same test can be done with a bucket of water and instead of using holes, tap the water with the ends of two sticks.
Slashdot Mirror
Since most business still run Windows, you need to find people with enough skills to fix the same problems over and over. Printing, Outlook, and antivirus/antispyware are the base standards. Ask if they know what Active Directory is, and what its used for. The best question, imho, is still to ask what is the quickest way to find out which version of Windows a user is running. (winver.exe ...btw). If they can answer any questions about those, that will filter out most of the riff-raff.
The big difference is that OpenBSD it uses GCC 2.9X. Linux ports usually won't work. I haven't looked at 3.7 - but this was the case in 3.6 and prior versions. Compile from source, and there are no functional differences. There are also very few "wrapper" scripts to start and stop daemons, which major linux distros have.
Once you get past that - you probably won't notice you're on a BSD box.
Knowledge in hardware is paramount. Classes in hardware should progress from electrial diagrams to logic circuits to chip assembly to assembly language to device drivers to operating sytems. By learning hardware, you learn why pointers work, how ethernet carries voltage across a wire, and why there are limits to ethernet length, and that intel really had figured out the Pentium chip as far back as the 8086. Hardware knowledge really makes you more of a generalist in the computer industry. You can network computers, configure RAIDs and SANs, and trace cables with a tone generator. You may not be able to write code with a hardware degree, but you know the capabilities of the hardware and why Windows95/98/ME were never really a true operating system (they were disk access systems that ran programs)
This is a common experiment in undergrad physics. It proves that light acts both as a wave and a particle. When light acts as a wave, it interferes with itself, and thus cancelling itself out. The same test can be done with a bucket of water and instead of using holes, tap the water with the ends of two sticks.
Thats up to engineers to figure out.