I've acutally been through this a couple of times, and I'm currently training a friend. I recommend finding something your intern knows how to do from the command line and set them to automating it. One advantage to this approach is that they already know how it should work, so they can focus on the programming aspect.

For example, have them write a log file filter. Set them to writing a script that will open a logfile, search for key data, and output that data to a separate file.

Another task would be to have them write a wrapper around ping, host, and traceroute that would crawl your network. The output might actually be useful, as you may discover some things about your network.

Another good project is a tool that uses MP3::Tag to manipulate the tags on an mp3 collection. It's a good project for learning perl modules, hashes, and pattern matching.

Finally, as to the Camel and Llama books, if your intern wants to code perl, they need the Camel book. It's a formal requirement. Period. If they're so dead broke that they can't afford usedcopies (and I remember those days), and your company refuses to pony up for a corporate copy of O'Reilly's CD bookshelf, and you can't get them to trade for it ("Mow my lawn and wash my car and I'll buy you the damn book, kid"), there's a solution. It's not pretty, and it's illegal I'm sure: Google for it.

I know this is blasophmy, but I've never found the Camel and Llama books all that helpful. I've yet to read every single page in them.

Your best chance to learn is to find an online tutorial or two. Understand how perl deals with variables (i.e. the difference between $foo @foo %foo &foo) and program control (i.e. if while for foreach sub). Also look over http://www.perldoc.com/perl5.8.4/pod/perlfunc.html to get an idea of what commands are available.

At that point try your first simple project. If you can't figure out how to do it after a few days, google for it. If that fails ask around here.