Hi there, Reading the LPIC-2 V4 draft [1], I would like to ask what is the relevance of asking a candidate about how to patch the kernel, and only using the patch command.
1) The kernel can be easily configured at runtime or boot time. Over the years Linux has became more mature and it is possible easily change core components like schedulers, memory policies and HZ or multiplier parameters. The culture of pushing features to Linus' tree is a success. 2) Patching kernel source code is extremely rare and IMHO should be avoided. Distributions have made a lot of progress over the last decade regarding the stability and reliably of their kernels. Distributions already include various kernel flavors with patches applied, like real time kernels. 3) If one _REALLY_ must maintain a kernel, one must use git. IMHO it is completely insane to just apply patches to a kernel without using git. Developers and high level SysAdmins these days cherry-pick features using git. So, 201.3 should ask a candidate about basic git usage regarding kernel patching, or it must be removed, because I really don't remember having to patch any kernel for a long time and I strongly recommend to my students to not do it. Regards, Miguel [1] http://wiki.lpi.org/wiki/LPIC-2_Objectives_V4#201.3_Patching_a_kernel -- Instruct Treinamento e Desenvolvimento http://www.instruct.com.br 19 4062-9235 - 19 9602-2781 _______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
