<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://www.zen-kernel.org/faq/RSS">
  <title>FAQ</title>
  <link>http://www.zen-kernel.org</link>

  <description>
    
      Frequently Asked Questions
    
  </description>

  

  
            <syn:updatePeriod>daily</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2009-10-18T01:07:24Z</syn:updateBase>
        

  <image rdf:resource="http://www.zen-kernel.org/logo.png"/>

  <items>
    <rdf:Seq>
      
        <rdf:li rdf:resource="http://www.zen-kernel.org/faq-folder/what_is_zen"/>
      
      
        <rdf:li rdf:resource="http://www.zen-kernel.org/faq-folder/what-is-included-in-the-zen-kernel"/>
      
      
        <rdf:li rdf:resource="http://www.zen-kernel.org/faq-folder/zen-zenstable_differences"/>
      
      
        <rdf:li rdf:resource="http://www.zen-kernel.org/faq-folder/i-incorporate-zen-can-i-get-a-cool-projects-button"/>
      
      
        <rdf:li rdf:resource="http://www.zen-kernel.org/faq-folder/why-should-i-use-this-kernel"/>
      
      
        <rdf:li rdf:resource="http://www.zen-kernel.org/faq-folder/help-i-get-all-these-merge-conflicts"/>
      
      
        <rdf:li rdf:resource="http://www.zen-kernel.org/faq-folder/i-found-a-bug-how-do-i-report-it"/>
      
    </rdf:Seq>
  </items>

</channel>


  <item rdf:about="http://www.zen-kernel.org/faq-folder/what_is_zen">
    <title>What is the Zen kernel?</title>
    <link>http://www.zen-kernel.org/faq-folder/what_is_zen</link>
    <description>A brief description that describes the zen kernel and its purpose.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<blockquote></blockquote>
<p>&nbsp;&nbsp;&nbsp;&nbsp; Zen is a variant of the Linux kernel that performs two major functions: (1) optimizes for desktop setups, and (2) provides a user base for project admins seeking testing for their project on various setups - these projects may or may not be seeking inclusion into the upstream Linux kernel. So, in essence, the kernel gears for desktop systems by adjusting tuning knobs and merging projects that suit this purpose in one way or another (for example, the BFS cpu scheduler is added <strong>_in addition_ </strong>to the default CFS scheduler). Additionally there are multiple things added and changed in the kernel that not everybody will benefit from (perhaps driver updates/additions and various bug fixes). The idea is to&nbsp;benefit Linux desktop end-users, kernel developers, and perhaps even more individuals.</p>
<p>&nbsp;&nbsp; &nbsp; Zen is a collaborative effort that includes a small group of developers but also a fairly large community that contributes much like the developers do.</p>
<p>&nbsp;</p>
<blockquote></blockquote>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Brandon Berhent</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2009-10-19T02:40:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://www.zen-kernel.org/faq-folder/what-is-included-in-the-zen-kernel">
    <title>What is included in the Zen kernel?</title>
    <link>http://www.zen-kernel.org/faq-folder/what-is-included-in-the-zen-kernel</link>
    <description>A brief synopsis about how to learn what is included in the Zen kernel.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p>&nbsp;&nbsp;&nbsp;&nbsp; The code that is merged into the zen kernel can vary at any given time. A few examples of projects that have been merged for multiple releases consistently are bfs/zen-sched, bfq i/o scheduler, aufs, reiser4, tuxonice, smapi, linux PHC, mactel, gc-linux, fbcondecor, cko,&nbsp; and others. It's not accurate for us to put a list of what's included on the web site as it can change slightly on a release-by-release basis.</p>
<p>&nbsp;&nbsp;&nbsp;&nbsp; If you are interested in learning about what is included in the zen kernel at any given time, please visit <a class="external-link" href="http://git.zen-kernel.org" target="_blank">gitweb</a> and read or search through the git logs. The gitweb interface&nbsp; displays all of the commits with commit messages and branches that exist in that tree. This information is displayed for the current 'master' branch of the tree and for any of the existing tags (so you can go back and check on an older release).</p>
<p>&nbsp;&nbsp;&nbsp;&nbsp; Alternatively there is an extensive documentation that also explains several projects merged into a Zen kernel, this can be found on the <a class="external-link" href="../documentation" target="_blank">Documentation</a> page.</p>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Brandon Berhent</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2009-10-19T21:30:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://www.zen-kernel.org/faq-folder/zen-zenstable_differences">
    <title>What is the difference between zen.git and zen-stable.git?</title>
    <link>http://www.zen-kernel.org/faq-folder/zen-zenstable_differences</link>
    <description>Explains the difference between the stable and unstable trees.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<div class="pageBreak">The core differences between the two trees are summed up below.</div>
<strong><br />Zen-Stable.git<br /></strong>
<ul><li>Only made on top of stable kernel releases: No -rc kernels (2.6.X.Y)</li><li>Does not pull in bleeding edge git repositories scheduled for future merge windows (no drm-next, sound-2.6.git, wireless-testing, or any other "testing" tree)</li><li>Does not merge code "just to see if it works"</li><li>Only has stable + stable zen tags (no -rc tags)<br /></li></ul>
<strong>Zen.git<br /></strong>
<ul><li>Pulls in latest linux-2.6.git: -rc/git kernels (2.6.X-rcY)</li><li>Will pull in git repositories before linus (drm-next, sound-2.6.git, wireless-testing)</li><li>New projects that we want to test to see if they actually work and provide a benefit are merged into Zen.git, possibly seeing zen-stable.git after considered working and beneficial.</li><li>Only has unstable + unstable zen tags (only -rc tags)<br /></li></ul>
<div class="pageBreak"><strong>YOU DO NOT NEED TO CLONE BOTH zen-stable.git AND zen.git if you want to use both trees at any time! Read "<a class="external-link" href="../tutorials/switching-between-zen-stable-and-zen.git" target="_blank">How to switch between zen-stable and zen on the same tree</a>"<br />This provides all the tags in the same tree (not just -rc or stable tags), and getting both masters in the same tree.<br /></strong><br />With all this being said, it's clearly as the name implies. Zen-stable.git is more stable while Zen.git is not as stable and uses more experimental code. This does not mean there is no benefit to Zen.git! Typically as a -rc release gets into higher numbers it has become more stable. Code is updated and added for a reason, very frequently there is something in the new/experimental code that users benefit from.</div>
<div class="pageBreak">&nbsp;</div>
<div class="pageBreak">Running a stable kernel has benefits as well, there is a significantly less chance that there will be problems with it which should be a priority of most users. (Typically unstable code is a bad thing).</div>
<div class="pageBreak">&nbsp;</div>
<div class="pageBreak">Zen.git fosters Zen-stable.git when the -rc is dropped and the actual kernel is released. (Since very little changes zen-stable can use all the branches that were used in zen.git, with the exception of any git trees)</div>
<div class="pageBreak">&nbsp;</div>
<div class="pageBreak">Both trees exist for a reason, use either one or both as you wish to. (maybe if you have a problem with a stable kernel you can see if it's fixed on the newer kernel)</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Brandon Berhent</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2009-10-20T21:45:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://www.zen-kernel.org/faq-folder/i-incorporate-zen-can-i-get-a-cool-projects-button">
    <title>I incorporate Zen, can I get a "cool projects" button?</title>
    <link>http://www.zen-kernel.org/faq-folder/i-incorporate-zen-can-i-get-a-cool-projects-button</link>
    <description>How to get a button+link on the zen kernel web page for your project.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p>There are several projects that incorporate zen in some way. Some examples include as their primari kernel, such as Yoper or Archlive (Chinese/English), Others offer it as an option such as&nbsp; gentoo or sourcemage, and there are even projects that produce pre-built distribution packages, such as liquorix (testing/sid deb builds).</p>
<p>If you are including the Zen kernel in your project in anyway (such as one mentioned above) shoot an email (preferably to cheater-conrad) , talk to us on IRC, or shoot an email to the ML.</p>
<p>You can make your own button (png format) or give us your logo and we could make it and put it up ourselves.</p>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Brandon Berhent</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2009-10-30T19:25:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://www.zen-kernel.org/faq-folder/why-should-i-use-this-kernel">
    <title>Why should I use this kernel?</title>
    <link>http://www.zen-kernel.org/faq-folder/why-should-i-use-this-kernel</link>
    <description></description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p>Here's my answer to this question:</p>
<p>Read through the documentation and any other information throughout the web site (particularly the documentation page and gitweb) - if you can't find any reason to use it then don't use it. I can't say you should use it - do the research and decide for yourself.</p>
<p>I don't earn a commission by getting people to use it so I won't sell it to you.</p>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Brandon Berhent</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2009-11-19T21:35:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://www.zen-kernel.org/faq-folder/help-i-get-all-these-merge-conflicts">
    <title>Help! I get all these merge conflicts!</title>
    <link>http://www.zen-kernel.org/faq-folder/help-i-get-all-these-merge-conflicts</link>
    <description>How to fix the tree after a rebase.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<div class="pageBreak">After a kernel rebase you will experience a merge conflict. This is because the old master has been deleted/moved in favor of a re-done master that has a base off of a newer kernel version. On zen-stable, this will happen on major bumps - for example, 2.6.31-&gt;2.6.32, you can still use the 2.6.31 version on the master-2.6.31 branch, but the newest version is always kept on the master branch.</div>
<div class="pageBreak">&nbsp;</div>
<div class="pageBreak">They may *<strong>look</strong>* frightening, but they are no big deal and they are a simple fix.</div>
<div class="pageBreak">Here's an example of a merge conflict:</div>
<div class="pageBreak"><span class="Apple-style-span">
<pre>host@host # <span class="Apple-style-span">git pull&nbsp;
Auto-merged .gitignore&nbsp;
Auto-merged MAINTAINERS&nbsp;
Auto-merged Makefile&nbsp;
CONFLICT (content):&nbsp;<strong>Merge</strong>&nbsp;conflict in Makefile&nbsp;
Removed arch/mips/lasat/sysctl.h&nbsp;
Auto-merged drivers/ata/libata-scsi.c&nbsp;
Auto-merged drivers/char/Kconfig&nbsp;
Auto-merged drivers/char/drm/ati_pcigart.c&nbsp;
Auto-merged drivers/char/drm/drm.h&nbsp;
Auto-merged drivers/char/drm/drm_drv.c&nbsp;
CONFLICT (content):&nbsp;<strong>Merge</strong>&nbsp;conflict in drivers/char/drm/drm_drv.c&nbsp;
...&nbsp;
Automatic&nbsp;<strong>merge</strong>&nbsp;failed; fix&nbsp;<strong>conflicts</strong>&nbsp;and then commit the result.</span></pre>
</span></div>
<div class="pageBreak">The typical way to fix it can be summarized in one line, although you should really learn what each of the git commands does.</div>
<div class="pageBreak">
<pre>host@host # git add .; git reset --hard; git branch -M master master-old; git checkout -b master origin/master; git branch -D master-old</pre>
</div>
<div class="pageBreak">Now all the conflicts should be resolved and you are on the fresh master</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Brandon Berhent</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2009-12-05T06:41:26Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://www.zen-kernel.org/faq-folder/i-found-a-bug-how-do-i-report-it">
    <title>I found a bug, how do i report it?</title>
    <link>http://www.zen-kernel.org/faq-folder/i-found-a-bug-how-do-i-report-it</link>
    <description>Information on reporting bugs including what to do and what not to do.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p>Bugs are bound to happen every now and again (especially when using the unstable tree) - we want you to report them so we can get them fixed!</p>
<div class="pageBreak">Bugs can fall into any number of categories - there are a couple of ways you can report them.<br /><strong>Good ways to report a bug:<br /></strong>
<ul><li>Use the <a class="external-link" href="../issues" target="_blank">issue tracker</a> <br /></li><li>Use the <strong>mailing list</strong>, subscribe/archive information is located on the <a class="external-link" href="../community" target="_blank">community page</a>. (especially report upstream bugs - such as ones found in tuxonice,
reiser4, aufs, etc.) - partially because developers of these projects
maybe subscribed.</li><li>Report it on <a class="external-link" href="https://www.mibbit.com/chat/?url=irc%3A%2F%2Firc.rizon.net%2F%23zen-sources" target="_blank">IRC</a> (acceptable for minor bugs, such as typos, simple compile errors, etc)</li></ul>
<strong>Bad ways and bad things to do when reporting a bug:<br /></strong>
<ul><li>Sending an email (If you don't use the mailing list or bug tracker - which both send us email notifications)</li><li>Reporting the problem with Zen somewhere other than us, examples: Reporting a Zen problem to another project such as Gentoo, reporting a kernel problem with Zen to an upstream kernel developer (Unless you are absolutely SURE it is an upstream problem, if you report it to us first we can possibly fix it ourselves and submit the fix upstream - or direct you where to report it)</li><li>Posting a bug without a trace or information, EX: "Zen doesn't compile" instead of "soandso.c doesn't compile in version 2.6.x-zeny, below is an attached .config and the exact error as i saw it"</li><li>Yelling about it, EX: Say that you were having a problem with drm in 2.6.31 (not zen, just 2.6.31) - and we directed you to upstream to report the problem and you respond "F@*&amp; YOU, You SUCK, FIX IT" (this has actually happened - an upstream bug that someone expected us to report/fix - when none of us were affected by it) <br /></li></ul>
</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Brandon Berhent</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2009-10-30T19:44:47Z</dc:date>
    <dc:type>Page</dc:type>
  </item>





</rdf:RDF>

