[masraum]

Originally Posted by id10t

But I may end up teaching a "intro to how to program" and the person developing it decided to use python. Dunno why, she's a terrible programmer, but there it is...

Turns out my Linux admin students had serious issues, so instead of playing iwth programming I'm spending the weekend setting up practice drills on determining where/how/why network connectivity is failing (which they should've learned 2 years ago - this kids are about to graduate). Means I'm gonna end up with 10 or 12 virtual machines going at once. Gotta love modern stuff.

Python is big these days, so not a bad thing. In my realm, Python seems to be the flavor du jour.

THank you for teaching them network troubleshooting. I have worked with many, many "server" guys over the years that were clueless when it came to network troubleshooting. I don't expect them to be able to troubleshoot what I do, but they should be able to troubleshoot the basics. IP, subnet mask and default gateways get configured on servers and workstations. Servers and workstations have arp tables. You should know how to use them. Don't even get me started on multi-homed servers with routing tables and asymmetric routing.