<br><br><div class="gmail_quote">On Wed, Dec 12, 2012 at 5:28 PM, supratim chakraborty <span dir="ltr"><<a href="mailto:sup270792@gmail.com" target="_blank">sup270792@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font face="trebuchet ms,sans-serif">I searched on the internet for an apt answer but i couldn't find one so i thought this could be a newbie-friendly place to shoot the doubt <br><br>I have developed an interest in OS development (kernel) and have successfully built/compiled/configured the kernel source but i would like to know as to how do OS developers test their code ,as in- it could be really painful to make some changes to the code and then again recompile the entire kernel , make a new image and then boot from that <br>
<br>in essence it would require - 1. Making changes 2. Compiling 3. Reflashing the kernel 4. Rebooting the machine (physical or virtual as the case may be)<br clear="all"></font><div><span><br>So I am pretty sure that this is not the way the work's done , so can i have the needed enlightenment as to how do OS developers go about making hacks /changes to the code and then testing the new build </span></div>
<div><span><br></span></div><div><span>Regards<span class="HOEnZb"><font color="#888888"><br>Supratim Chakraborty<br>
<a href="http://about.me/borax12" target="_blank">about.me/borax12</a></font></span></span></div><br>
<br></blockquote><div>Linux Test suite is one place to test your Linux: <br></div><div><a href="http://ltp.sourceforge.net/">http://ltp.sourceforge.net/</a><br><br>more from slashdot<br><a href="http://linux.slashdot.org/story/05/06/05/1426206/linux-kernel-gets-fully-automated-test">http://linux.slashdot.org/story/05/06/05/1426206/linux-kernel-gets-fully-automated-test</a><br>
<br>kernel autotest<br><a href="http://autotest.github.com/">http://autotest.github.com/</a><br><br><br>besides people make changes in one or two parts of kernel subsystem at a time and/or parts totally related and test it out in accordance to that subsystem.<br>
<br>you can also use UML for testing. It is pretty good way to quickly get idea of basic functionality. For networkign you can use wireshark and all<br><br>and what this guy has replied.<br><a href="http://stackoverflow.com/questions/3177338/how-is-linux-kernel-tested">http://stackoverflow.com/questions/3177338/how-is-linux-kernel-tested</a><br>
<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Thank you <br>Warm Regards<br>Anuz<br><br>