On Fri, Jun 21, 2013 at 8:14 AM, Anselm Lingnau < [email protected]> wrote:
> This is because you can't very well use Linux without ls(1), but it is > perfectly possible to use Linux without virtualisation. Virtualisation is > surely a nice thing to have but let's not go overboard here. > We cover many things in LPIC-1 that are not required for many roles. It's just as well to remember that LPIC-1 is not supposed to be an exam for > system administrators. Really? There are a lot of root-only topics in there, from boot to library prefetch to a lot of other things. I thought it was junior Linux sysadmin administration, not user. A senior sysadmin would configure many backend and service items, while a junior would be involved with more operations and day-to-day. It does cover some system administration but – unlike > LPIC-2/3 – its target population is »Linux professionals« in general. > Which is > not to say that Linux professionals should not know about virtualisation, > but > at LPIC-1 level there still are bigger fish to fry. > Depends on your viewpoint. I would be in favour of a policy where whoever suggests an entirely new > topic > to be added to LPIC-1 or LPIC-2 should also come up with a well-argued > proposal of what other topic (or topics) to remove in order to make room. > This > is not as much of an issue in LPIC-3, where we can always make another exam > ;^) > I would rather Matt define this, given his experience. -- bjs P.S. I want everyone to keep one (1) thing in mind ... I _never_ argued for/against adding virtualization below LPIC-3. What I _argued_ was that if we do, then it should be libvirt/virsh. Virsh is an _ideal_ example of "operations" for junior sysadmins. I cannot think of a more ideal example and solution for LPIC-1. If you are ignorant of libvirt/virsh, please change that now. Otherwise, results will be typical as in other threads. I.e., you'll accuse me of various things (e.g., "Red Hat bias" or "purity/religious" or etc...), instead of seeing the point I'm making, and more importantly, why. It's one thing to disagree. It's another disagree in ignorance. -- Bryan J Smith - Professional, Technical Annoyance b.j.smith at ieee.org - http://www.linkedin.com/in/bjsmith
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
