<?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; General</title>
	<atom:link href="https://lunar-linux.org/category/general/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>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>Lunar-Linux Last.FM Group</title>
		<link>https://lunar-linux.org/2006/03/12/lunar-linux-lastfm-group/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=lunar-linux-lastfm-group</link>
		<comments>https://lunar-linux.org/2006/03/12/lunar-linux-lastfm-group/#comments</comments>
		<pubDate>Sun, 12 Mar 2006 20:35:30 +0000</pubDate>
		<dc:creator><![CDATA[v3rt1g0]]></dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.blogs.lunar-linux.org/2006/03/12/lunar-linux-lastfm-group/</guid>
		<description><![CDATA[<p>Lunar-Linux now has a Last.FM group. If you are a user of Last.FM and wish to join our group, please do so!</p> <p>Group Weblink: <a href="http://www.last.fm/group/Lunar-Linux">http://www.last.fm/group/Lunar-Linux</a></p> <p></p> <p>If you don&#8217;t know what Last.FM is here is a little description from the Last.FM website:</p> <p>Last.fm is the flagship product from the team that designed the Audioscrobbler [...]]]></description>
				<content:encoded><![CDATA[<p>Lunar-Linux now has a Last.FM group.  If you are a user of Last.FM and wish to join our group, please do so!</p>
<p>Group Weblink: <a href="http://www.last.fm/group/Lunar-Linux">http://www.last.fm/group/Lunar-Linux</a></p>
<p><span id="more-30"></span></p>
<p>If you don&#8217;t know what Last.FM is here is a little description from the Last.FM website:</p>
<p>Last.fm is the flagship product from the team that designed the Audioscrobbler system, a music engine based on a massive collection of Music Profiles. Each music profile belongs to one person, and describes their taste in music. Last.fm uses these music profiles to make personalized recommendations, match you up with people who like similar music, and generate custom radio stations for each person.</p>
]]></content:encoded>
			<wfw:commentRss>https://lunar-linux.org/2006/03/12/lunar-linux-lastfm-group/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
