John Lupa <john.l...@gmail.com> wrote: > probably a scripting language should be recommended to be learned > besides sh/bash? for maintenance tasks that a linux sysadmin would > have to perform. sometimes another language helps […] and having > options is awesome - python, perl, php and others...
I don't think anyone here doubts that knowing a scripting language is a good idea in the abstract. The problem, however, is that the effort needed to learn (or teach) a programming language such as Perl or Python (I hope nobody in their right mind uses PHP for sysadmin-type scripting – it's bad enough if people use it for web stuff) is a significant fraction of the effort needed to learn the rest of LPIC-1. For example, the set of classes my company teaches to cover LPIC-1 is 12 days long, while our introductory Perl or Python classes are 3 days. Following the rule of thumb that the time spent on a topic should roughly correlate with its weight in the exam, this would suggest that out of the 120 questions we're asking in the LPIC-1 exams, at least 24 or so should deal with the scripting language, which is patently unreasonable. And that is *before* we decide which one of the half-dozen popular scripting languages should actually be on the exam, where there is a guarantee that whichever language we pick will tick off those people who think that particular language is junk and we should have picked their favourite instead. Anselm Disclaimer: This is my personal opinion and not that of my employer. -- Anselm Lingnau ... Linup Front GmbH ... Linux-, Open-Source- & Netz-Schulungen anselm.ling...@linupfront.de, +49(0)6151-9067-103, Fax -299, www.linupfront.de Linup Front GmbH, Postfach 100121, 64201 Darmstadt, Germany Sitz: Weiterstadt (AG Darmstadt, HRB7705), Geschäftsführer: Oliver Michel _______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
