<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Lunar Linux &#187; moe</title>
	<atom:link href="https://lunar-linux.org/author/moe/feed/" rel="self" type="application/rss+xml" />
	<link>https://lunar-linux.org</link>
	<description>It&#039;s out of this world!</description>
	<lastBuildDate>Tue, 15 Aug 2023 07:21:25 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.8.3</generator>
	<item>
		<title>Lunar Linux ISO install guide</title>
		<link>https://lunar-linux.org/2008/07/10/lunar-linux-iso-install-guide/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=lunar-linux-iso-install-guide</link>
		<comments>https://lunar-linux.org/2008/07/10/lunar-linux-iso-install-guide/#comments</comments>
		<pubDate>Thu, 10 Jul 2008 21:19:53 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[ISO]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2008/07/10/lunar-linux-iso-install-guide/</guid>
		<description><![CDATA[Note: This guide only applies to 1.6.2 or lower. <p>Since our ISO is pretty outdated right now (work has begun on a new release, yet, there is no release date in sight. Its going to be ready &#8216;when its done&#8217; &#8482;) it does require a special kind of way to install it properly. This guide [...]]]></description>
				<content:encoded><![CDATA[<h1>Note: This guide only applies to 1.6.2 or lower.</h1>
<p>Since our ISO is pretty outdated right now (work has begun on a new release, yet, there is no release date in sight. Its going to be ready &#8216;when its done&#8217; &#8482;) it does require a special kind of way to install it properly. This guide is ment to help you through the pain.</p>
<p><span id="more-33"></span><br />First and foremost, once you hit your first command prompt telling you to read &#8216;man lfirsttime&#8217; you should still go ahead and read &#8216;man lfirsttime&#8217;.</p>
<p>However, once you&#8217;re through reading &#8216;man lfirsttime&#8217; <b>DO NOT FOLLOW IT&#8217;S INSTRUCTIONS JUST YET!</b></p>
<p>The following steps are <b>REQUIRED</b> before any other to get a working system:</p>
<ol>
<li>Update your moonbase and coretools by running
<p>  <code>$ lin moonbase</code></p>
<p>     and</p>
<p>  <code>$ lin theedge</code> (or if you prefer lunar over theedge you should obviously &#8216;lin lunar&#8217;)</li>
<p></p>
<li>Now, update gcc <b>ONCE</b>.
<p> <b>DO NOT UPDATE GLIBC OR ANY OTHER MODULE RIGHT AFTER GCC!</b></p>
<p>  <code>$ lin -cr gcc</code></li>
<p></p>
<li>Reset your optimizations by running
<p>  <code>$ lunar optimize</code></p>
<p>  <b>This is the most crucial step right here</b>. Make sure GCC_4_2 (gcc 4.2.x obviously) is your default compiler by selecting &#8216;GCC_4_2 -> default&#8217; and pressing ENTER. It should tell you that from now on gcc 4.2.x is going to be used as your default compiler. Also, don&#8217;t forget to set the rest of the optimizations again. Don&#8217;t overdo it. Chose a sane amount of compiler and ld flags.</p>
<p>Without resetting your optimizations glibc is not going to compile and neither are a couple of other important modules. Basically, you are going to end up with a unusable system.</li>
<p></p>
<li>Update your kernel headers by issueing
<p>  <code>$ lin kernel-headers-2.6</code></p>
<p>  You need the newer headers installed in order for glibc to compile the right set of headers. Otherwise you&#8217;re going to get in trouble sooner or later.<br />
  <b>HINT:</b> If any of the modules you&#8217;re going to compile past this point are failing because of missing SCSI headers files such as &#8216;scsi.h&#8217; you need to recompile &#8216;kernel-headers-2.6&#8242; and &#8216;glibc&#8217; again. The modules in question should be compiling normally afterwards.</li>
<p></p>
<li>Update glibc:
<p>  <code>$ lin glibc</code></p>
<li>Now, go on with the rest of modules mentioned inside &#8216;man lfirsttime&#8217;, notably (in this precise order) gcc, bash, coreutils, tar and wget:
<p>  <code>$ lin -cr gcc bash coreutils tar wget</code></li>
<p></p>
<li>Update &#8216;lunar-init&#8217; and &#8216;udev&#8217; .. otherwise your new system is not going to boot
<p>  <code>$ lin -c lunar-init udev</code></p>
</li>
<li>Once all of the above steps are completed I strongly recommend updating your kernel before going ahead with a full scale update or renew (for a reference see &#8216;man lunar&#8217;) since your currently installed header files are from a newer kernel than the one you&#8217;re running right now. And honestly: Who doesn&#8217;t like a fresh new kernel, right?
<p> <code>$ lin linux-2.6</code></p>
<p>  Don&#8217;t forget to reboot your system to get the newer kernel running!</li>
<p>
</ol>
<p>I hope this guide is going to ease the pain of installing the outdated ISO a little bit. The whole team knows about this issue, however, time simply doesn&#8217;t allow for a full scale ISO deployment right now. Once you&#8217;re through with the general update procedure though your lunar install is going to be as good as any other.</p>
<p>If there are any further questions or comments don&#8217;t hesitate to use the comment functionality of this lovely CMS, <a href="irc://irc.freenode.org/#lunar">drop by via IRC</a> or even write an email to <a href="http://foo-projects.org/mailman/listinfo/lunar" class="broken_link" rel="nofollow">our mailinglist</a> (registration required!). If you&#8217;re desperate enough you may also <a href="mailto:moe@lunar-linux.org">drop me a mail directly</a>.</p>
<p>Cheers, Moritz</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2008/07/10/lunar-linux-iso-install-guide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mandatory server updates</title>
		<link>https://lunar-linux.org/2008/02/12/server-maint-02-12/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=server-maint-02-12</link>
		<comments>https://lunar-linux.org/2008/02/12/server-maint-02-12/#comments</comments>
		<pubDate>Tue, 12 Feb 2008 19:47:25 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[website]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2008/02/12/server-maint-02-12/</guid>
		<description><![CDATA[<p>Our main server is currently undergoing mandatory maintenance. Please be patient and bear with us until our administrative squirrels (well, just one squirrel actually) have completed their nutty works.<br /> This note is going to get updated once everything is resolved.</p> <p>Thank you.</p> <p>UPDATE: The squirrels are done and our main server is up and [...]]]></description>
				<content:encoded><![CDATA[<p>Our main server is currently undergoing mandatory maintenance. Please be patient and bear with us until our administrative squirrels (well, just one squirrel actually) have completed their nutty works.<br />
This note is going to get updated once everything is resolved.</p>
<p>Thank you.</p>
<p><b>UPDATE:</b> The squirrels are done and our main server is up and fully functional again. Thank you for bearing with us.</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2008/02/12/server-maint-02-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>glibc update</title>
		<link>https://lunar-linux.org/2007/11/18/glibc-update/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=glibc-update</link>
		<comments>https://lunar-linux.org/2007/11/18/glibc-update/#comments</comments>
		<pubDate>Sun, 18 Nov 2007 20:53:37 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[Modules]]></category>
		<category><![CDATA[glibc]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2007/11/18/glibc-update/</guid>
		<description><![CDATA[<p>Hello dear community,</p> <p>as of right now lunar is shipping the latest available glibc with its moonbase. It tooks some time, yet .. we managed to make it count. From now on, glibc comes bundled with a new language choser giving you the opportunity to chose from all currently supported languages including UTF-8 based locales [...]]]></description>
				<content:encoded><![CDATA[<p>Hello dear community,</p>
<p>as of right now lunar is shipping the latest available glibc with its moonbase. It tooks some time, yet .. we managed to make it count. From now on, glibc comes bundled with a new language choser giving you the opportunity to chose from all currently supported languages including UTF-8 based locales (which has been missing from lunar ever since).</p>
<p>Along with it we&#8217;re rolling out updates to several key core components like binutils, udev and hal .. some of them are being patched to work with the latest glibc. Others had to have the newer glibc ready in order to work correctly.</p>
<p>Also shipping is a brand-new kernel-headers-2.6 module including the latest headers from 2.6.23. It comes in both flavours, x86 and x86_64.</p>
<p>This update also marks the end of the linux-2.4 kernels in moonbase. The newer glibc does not work with the old 2.4.x based kernel series. So <b>IF YOU&#8217;RE RUNNING LINUX 2.4.X PLEASE PUT GLIBC <i>ON HOLD</i>!</b> In the end you&#8217;re not going to get around migrating to 2.6.x .. but its going to buy you some time.</p>
<p>All updates have been tested back and forth .. yet, I&#8217;m pretty sure there are bugs going to pop up here and there. Please make use of <a href="http://bugs.lunar-linux.org/view_all_bug_page.php" class="broken_link" rel="nofollow">our bugtracker</a> if you think you encoutered one.</p>
<p>All in all this has been a great team effort and I&#8217;d like to thank each and every member of our team for putting his/her spare time into it.</p>
<p>Thank you and have fun with the new glibc!</p>
<p>Cheers,</p>
<p>For the Lunar Linux Development Team, Moritz &#8216;Moe&#8217; Heiber</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2007/11/18/glibc-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Attention! Huge update</title>
		<link>https://lunar-linux.org/2007/04/05/attention-huge-update/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=attention-huge-update</link>
		<comments>https://lunar-linux.org/2007/04/05/attention-huge-update/#comments</comments>
		<pubDate>Thu, 05 Apr 2007 23:19:59 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[Announcements]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2007/04/05/attention-huge-update/</guid>
		<description><![CDATA[p#q:first-letter,p#a:first-letter { font-size: 150%; font-weight: bold; float: left; padding-right: 0.5em; } p#q { margin-top: 2em; margin-bottom: 0; } p#a { margin-top: 0; } <p>I just commited a huge update to the way Lunar Linux handles its<br /> most vital init scripts. From now on, a module named &#8216;lunar-init&#8216; is going to hold some of the [...]]]></description>
				<content:encoded><![CDATA[<style type="text/css">
p#q:first-letter,p#a:first-letter {
  font-size: 150%;
  font-weight: bold;
  float: left;
  padding-right: 0.5em;
}
p#q {
  margin-top: 2em;
  margin-bottom: 0;
}
p#a {
  margin-top: 0;
}
</style>
<p>I just commited a huge update to the way Lunar Linux handles its<br />
most vital init scripts. From now on, a module named &#8216;<tt>lunar-init</tt>&#8216; is going to hold some of the more system-bound init scripts like &#8216;<tt>mount</tt>&#8216; (which has been with e2fsprogs before) and &#8216;<tt>network</tt>&#8216; (which has been a part of net-tools). <b>This update is by no means automatic and requires your attention</b>:</p>
<p><span id="more-19"></span></p>
<ol>
<li>Run lunar update as usual. lunar-init is a dependency of<br />
lunar/theedge and thus will get installed before anything else.</li>
<p>However, it is meant to fail on the first run since the old init scripts are still installed in <tt>/etc/init.d</tt>. DO NOT PANIC. This is the intended behaviour and saves us from dozens of lines of migration code.</p>
<li>Let your update continue as planned. e2fsprogs and net-tools have<br />
both been &#8220;updated&#8221; (their UPDATED field has been set to today) in<br />
order for them to complete a compilation without installing any init<br />
scripts. This step has to be taken to asure that none of the init<br />
scripts are tracked via any other installation logs than that of<br />
&#8216;<tt>lunar-init</tt>&#8216;.</li>
<li>Check whether one of the following files is still present<br />
in <tt>/etc/init.d/</tt>:</li>
<ul>
<li><tt>hostname</tt></li>
<li><tt>network</tt></li>
<li><tt>netmount</tt></li>
<li><tt>mount</tt></li>
</ul>
<p>If that is the case (and you do not employ your own version of these scripts) remove them on your own. If you don&#8217;t remove them on your own &#8216;<tt>lunar-init</tt>&#8216; is NOT going to install or overwrite any files present and will throw an error again.</p>
<li>Reinstall &#8216;<tt>lunar-init</tt>&#8216;. It should now go smooth and without an error. If that is not the case DO NOT REBOOT your machine but report the problem to our bugtracker.</li>
<li>Check whether you now have existing copies in <tt>/etc/init.d</tt> of the files mentioned earlier.</li>
</ol>
<p>And we&#8217;re done. Congratulations! Its now safe to reboot your box (not<br />
mandatory).</p>
<h2>FAQ</h2>
<p id="q">Q Any updates on the init scripts?</p>
<p id="a">A Absolutely. The network script has been refactored to support WEP/WPA/ifplugd out of box. Now you will be able to configure your wpa_supplicant and just let it run at boottime. Combined with ifplugd it lets you run dhcp clients on requests or network connectivity. Roaming and network priorities etc .. you name it.</p>
<p>The other scripts have been tweaked to work with chkconfig.</p>
<p id="q">Q Are there any other init scripts going to be intregrated with this module?</p>
<p id="a">A Most likely.
<p id="q">Q Why go through all this trouble?</p>
<p id="a">A It makes the init scripts maintainable. Before that we always had to bump individual versions of modules that weren&#8217;t related to any of the actions these scripts invoked.</p>
<p id="q">Q No seriously, why?</p>
<p id="a">A Because sofar said so.</p>
<p>Any further questions or bugs can be directed either to this list, the IRC channel or our beloved bugtracker.</p>
<p>Enjoy!</p>
<p>Moritz Heiber for the Lunar Linux Development Team</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2007/04/05/attention-huge-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Update to coreutils</title>
		<link>https://lunar-linux.org/2006/12/17/update-to-coreutils/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=update-to-coreutils</link>
		<comments>https://lunar-linux.org/2006/12/17/update-to-coreutils/#comments</comments>
		<pubDate>Sun, 17 Dec 2006 11:28:19 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[Modules]]></category>
		<category><![CDATA[coreutils]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2006/12/17/update-to-coreutils/</guid>
		<description><![CDATA[<p>Hello community,</p> <p>to let you know: For the recent updates to &#8216;coreutils&#8217; you HAVE TO update your coretools (lunar/theedge) first in order for the update not fail because of chmod and chown being lost in the process.</p> <p>chown and chmod have recently been added to the so called &#8216;protected&#8217; list thus they are now preserved [...]]]></description>
				<content:encoded><![CDATA[<p>Hello community,</p>
<p>to let you know: For the recent updates to &#8216;coreutils&#8217; you HAVE TO update your coretools (lunar/theedge) first in order for the update not fail because of chmod and chown being lost in the process.</p>
<p>chown and chmod have recently been added to the so called &#8216;protected&#8217; list thus they are now preserved throughout upgrades and your machines should not be rendered useless incase your coreutils are being updated.</p>
<p>If that is the case please extract chown and chmod from a working cache copy (located in /var/cache/lunar/) or grab them directly from /usr/src/coreutils-$VERSION and put them into /bin. Once that is accomplished please update your coretools first and relin coreutils afterwards.</p>
<p>We are sorry for inconvenience and hope that this hasn&#8217;t caused too much agony for all of you.</p>
<p>Regards,</p>
<p>Moritz aka Moe</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2006/12/17/update-to-coreutils/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Madwifi-svn module / CVS module to be phased out</title>
		<link>https://lunar-linux.org/2006/12/14/new-madwifi-svn-module-cvs-module-to-be-phased-out/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=new-madwifi-svn-module-cvs-module-to-be-phased-out</link>
		<comments>https://lunar-linux.org/2006/12/14/new-madwifi-svn-module-cvs-module-to-be-phased-out/#comments</comments>
		<pubDate>Thu, 14 Dec 2006 22:57:08 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[Modules]]></category>
		<category><![CDATA[zbeta]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2006/12/14/new-madwifi-svn-module-cvs-module-to-be-phased-out/</guid>
		<description><![CDATA[<p>Hey everybody,</p> <p>I added a madwifi-svn module to the moonbase. It is going to replace the madwifi-cvs module in a week (means the cvs modules is going to disappear and there&#8217;s only going to be the svn module). Also, the stable version of the madwifi wireless driver has been added as well named madwifi. It [...]]]></description>
				<content:encoded><![CDATA[<p>Hey everybody,</p>
<p>I added a madwifi-svn module to the moonbase. It is going to replace the madwifi-cvs module in a week (means the cvs modules is going to disappear and there&#8217;s only going to be the svn module). Also, the stable version of the madwifi wireless driver has been added as well named madwifi. It is supposed to provide people with a stable alternative to the bleeding edge svn driver. Unfortunately, the stable driver is semi-broken with the current kernel so if you are considering an upgrade please use the svn module for the time being. Once the stable driver recieves an update we&#8217;re going to test and probably bump it so everyone can use it.</p>
<p>Everyone is strongly encouraged to update to the newer madwifi driver. It contains fixes of a whole year that the (dead) cvs version hasn&#8217;t recieved (and probably never will).</p>
<p>Enjoy!</p>
<p>Moritz aka Moe</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2006/12/14/new-madwifi-svn-module-cvs-module-to-be-phased-out/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New DRM module for XOrg 7.x</title>
		<link>https://lunar-linux.org/2006/12/01/new-drm-module-for-xorg-7x/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=new-drm-module-for-xorg-7x</link>
		<comments>https://lunar-linux.org/2006/12/01/new-drm-module-for-xorg-7x/#comments</comments>
		<pubDate>Fri, 01 Dec 2006 20:45:01 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[Modules]]></category>
		<category><![CDATA[XOrg]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2006/12/01/new-drm-module-for-xorg-7x/</guid>
		<description><![CDATA[<p>Hello community,</p> <p>I just added a new module to the moonbase called &#8216;drm-git&#8217;. It replaces the obsolete &#8216;libdrm-cvs&#8217;. Both modules have the sole purpose of providing the kernel interface modules for the direct rendering manager X uses to enable your video card&#8217;s 3D acceleration. So if you happen to have libdrm-cvs installed its going to [...]]]></description>
				<content:encoded><![CDATA[<p>Hello community,</p>
<p>I just added a new module to the moonbase called &#8216;drm-git&#8217;. It replaces the obsolete &#8216;libdrm-cvs&#8217;. Both modules have the sole purpose of providing the kernel interface modules for the direct rendering manager X uses to enable your video card&#8217;s 3D acceleration. So if you happen to have libdrm-cvs installed its going to get removed on the next run and you will have to install drm-git instead to get a fully accelerated X environment again.</p>
<p>ATTENTION: THIS DOES NOT APPLY IF YOU ARE USING THE NVIDIA OR FGLRX DRIVER! DO NOT lin mesa-lib! You don&#8217;t need it as the binary drivers you use provide the kernel modules on their own.</p>
<p>Alongside with this update comes a libdrm (regular version) update and a slight mesa-lib modification (which shouldn&#8217;t effect anyone actually). Although, if were using the mach64 or r300 driver provided by mesa-lib you will not be able to do that until the next mesa release since the drivers are temporarily disabled. I&#8217;m sorry for that inconvenience but they just do not compile.</p>
<p>Enjoy.</p>
<p>Moritz Heiber<br />
Lunar Linux Development Team</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2006/12/01/new-drm-module-for-xorg-7x/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>udev update to 101</title>
		<link>https://lunar-linux.org/2006/10/08/udev-update-to-101/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=udev-update-to-101</link>
		<comments>https://lunar-linux.org/2006/10/08/udev-update-to-101/#comments</comments>
		<pubDate>Sun, 08 Oct 2006 11:11:50 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[udev]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2006/10/08/udev-update-to-101/</guid>
		<description><![CDATA[<p>udev has been updated in moonbase yesterday. Its been tested extensively, features a new rules patchset that is ment to provide a wider range of compatibility and effectiveness considering the hotplug and coldplug stages of every Lunar installation.</p> <p>Right now we don&#8217;t expect any error to turn up but of course we are just human [...]]]></description>
				<content:encoded><![CDATA[<p>udev has been updated in moonbase yesterday. Its been tested extensively, features a new rules patchset that is ment to provide a wider range of compatibility and effectiveness considering the hotplug and coldplug stages of every Lunar installation.</p>
<p>Right now we don&#8217;t expect any error to turn up but of course we are just human like everybody else. Yet, there can be some warnings popping up at boot time considering missing groups for device nodes (Yes, udev now actually checks wether groups that it assigns devices to are present or not), especially considering the groups &#8220;uucp&#8221;, &#8220;dialout&#8221;, &#8220;usb&#8221; and &#8220;cdrw&#8221;. If you encouter any of those warnings just go ahead and create these groups. They provide a broader range of possibilities for administrators to adjust their machines access-rights.</p>
<p>Enjoy!</p>
<p>For the Lunar Linux Development Team,</p>
<p>Moritz Heiber</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2006/10/08/udev-update-to-101/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ERRATA: 1.6.0 &#8211; non-configured kernel sources</title>
		<link>https://lunar-linux.org/2006/04/20/errata-160-non-configured-kernel-sources/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=errata-160-non-configured-kernel-sources</link>
		<comments>https://lunar-linux.org/2006/04/20/errata-160-non-configured-kernel-sources/#comments</comments>
		<pubDate>Thu, 20 Apr 2006 19:37:51 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[Announcements]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2006/04/20/errata-160-non-configured-kernel-sources/</guid>
		<description><![CDATA[<p>Hi,</p> <p>The 1.6.0 ISO has a minor flaw in the installation procedure that doesn&#8217;t correctly configure the kernel sources in /usr/src/linux.</p> <p>People who wish to compile XOrg or any other module that requires kernel sources will be unable to with out doing the following:</p> <p>$ make -C /usr/src/linux prepare</p> <p>this correctly creates /usr/src/linux/include/version.h, and should [...]]]></description>
				<content:encoded><![CDATA[<p>Hi,</p>
<p>The 1.6.0 ISO has a minor flaw in the installation procedure that doesn&#8217;t correctly configure the kernel sources in /usr/src/linux.</p>
<p>People who wish to compile XOrg or any other module that requires kernel sources will be unable to with out doing the following:</p>
<p><i>$ make -C /usr/src/linux prepare</i></p>
<p>this correctly creates /usr/src/linux/include/version.h, and should fix this problem.</p>
<p>Cheers,</p>
<p>Auke</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2006/04/20/errata-160-non-configured-kernel-sources/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Changes to thunderbird and removal of linux-2.6-inotify</title>
		<link>https://lunar-linux.org/2005/09/17/changes-to-thunderbird-and-removal-of-linux-26-inotify/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=changes-to-thunderbird-and-removal-of-linux-26-inotify</link>
		<comments>https://lunar-linux.org/2005/09/17/changes-to-thunderbird-and-removal-of-linux-26-inotify/#comments</comments>
		<pubDate>Sat, 17 Sep 2005 22:03:13 +0000</pubDate>
		<dc:creator><![CDATA[moe]]></dc:creator>
				<category><![CDATA[Modules]]></category>
		<category><![CDATA[kernel]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2005/09/17/changes-to-thunderbird-and-removal-of-linux-26-inotify/</guid>
		<description><![CDATA[<p>Hello community,<br/><br/></p> <p>just to let you know, I&#8217;ve just been taking out enigmail support of the thunderbird module since it doesn&#8217;t work anymore. If you wish to use enigmail with thunderbird in the future you will have to install it manually using the packages from <a href="http://enigmail.mozdev.org/home/index.php.html" class="broken_link" rel="nofollow">http://enigmail.mozdev.org</a>.<br/><br/> We apologize for the inconvenience but [...]]]></description>
				<content:encoded><![CDATA[<p>Hello community,<br/><br/></p>
<p>just to let you know, I&#8217;ve just been taking out enigmail support of the thunderbird module since it doesn&#8217;t work anymore. If you wish to use enigmail with thunderbird in the future you will have to install it manually using the packages from <a href="http://enigmail.mozdev.org/home/index.php.html" class="broken_link" rel="nofollow">http://enigmail.mozdev.org</a>.<br/><br/> We apologize for the inconvenience but there&#8217;s hardly anything we can do about thunderbird&#8217;s messed up code <img src="https://lunar-linux.org/wp-includes/images/smilies/icon_wink.gif" alt=";-)" class="wp-smiley" /> <br/><br/></p>
<p>Also, I&#8217;m about to remove the &#8216;linux-2.6-inotify&#8217; kernel as the patches that were applied to the referred module have been merged with the main kernel tree and therefore are no longer needed.<br/><br/></p>
<p>Thank you for your ongoing support!<br/><br/></p>
<p>Cheers,</p>
<p>Moritz aka Moe on behalf of the Lunar Linux Team</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2005/09/17/changes-to-thunderbird-and-removal-of-linux-26-inotify/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
