Lunar Linux - User contributions [en]

Template:Main Page:About

2012-02-29T21:29:52Z

Striker: Updated to match other main page templates

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:About|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux:About|'''About Lunar Linux''']]</h2>

'''Lunar Linux''' is a [[wikipedia:source code|source]] based [[wikipedia:Linux distribution|Linux distribution]]. It is built entirely by [[wikipedia:compiler|compiling]] [[wikipedia:source code|source code]], using custom [[wikipedia:Optimization (computer_science)|optimizations]].

It installs a complete [[wikipedia:Bootstrap#Computing|bootstrap]] development system first. After telling the Lunar package manager which software will be required, it builds the entire system by downloading current source code and locally compiling an optimized system tailored toward the users specific needs.
This should result in a lean and optimized [[wikipedia:operating system|operating system]]. On the downside, compiling a whole distribution from scratch may be time-consuming and complicate the task of keeping the packages up to date.

Currently, Lunar only supports the [[wikipedia:X86|x86]] and [[wikipedia:X86-64|x86-64]] architectures.

Lunar Linux is licensed under the GPLv2.

'''2011-03-25''': Despite appearances, Lunar Linux is still very much alive. The official 1.6.5 ISO was released on 2010-08-22, and work on a beta release of the next ISO is currently in progress. The Forums and Wiki are inactive because they were locked after prolonged spam-bot vandalism. If you require help, simply go to the #lunar irc channel and ask!

<div style="text-align: right; font-variant: small-caps; padding-right: 15px;">
[[Lunar Linux:About|More Information]]
</div>

MediaWiki:Sidebar

2012-02-29T21:18:46Z

Striker: Move wiki nav to top

Template:Main Page:Documentation

2012-02-29T21:09:13Z

Striker: Installation links

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Documentation|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux/Documentation|Documentation]]</h2>

<h4>General</h4>
* [[Lunar Linux:FAQ|Frequently Asked Questions]]

<h4>Installation</h4>
* [[Lunar Linux:Installation|Installation (latest)]]
* [[Lunar Linux:Installation/1.5.0|Installation-1.5.0 (old)]]
* [[Lunar Linux:DesktopEnvironments|Desktop Environments, etc]]

<h4>Moonbase</h4>
* [[Moonbase|The Lunar Moonbase]]
* [[Module Basics|A basic module outline]]
* [[Module Writing|Writing Lunar-Linux Modules]]
* [[Module Functions|Module Function List]]
* [[Module Submission|Submitting modules]]

<h4>Other</h4>
* [irc://irc.freenode.net/lunar #Lunar] on [http://freenode.net/ Freenode.net]
* [http://lunar-linux.org/mailman/listinfo/lunar Lunar Mailing-List] [http://lunar-linux.org/pipermail/lunar/ (archive)]
* [http://lunar-linux.org/pipermail/lunar-bugs/ Lunar Bugs Mailing-List] [http://lunar-linux.org/mailman/listinfo/lunar-bugs (archive)]
* [http://lunar-linux.org/pipermail/lunar-commits/ Lunar Commits Mailing-List] [http://lunar-linux.org/mailman/listinfo/lunar-commits (archive)]

<div style="text-align: right; font-variant: small-caps; padding-right: 15px;">
[[Lunar Linux/Documentation|More Information]]
</div>

Lunar Linux:Installation

2012-02-29T21:08:03Z

Striker: Redirected page to Lunar Linux:Installation/1.6.5

#REDIRECT [[Lunar_Linux:Installation/1.6.5]]

Lunar Linux:Installation

2012-02-29T21:07:49Z

Striker: Redirecting to latest install doc

#REDIRECT [[Lunar_Linux:Installation-1.6.5]]

Lunar Linux:Installation-1.6.5

2012-02-29T21:07:10Z

Striker: moved Lunar Linux:Installation-1.6.5 to Lunar Linux:Installation/1.6.5: Moving installation pages to sub-page of Installation

#REDIRECT [[Lunar Linux:Installation/1.6.5]]

Lunar Linux:Installation/1.6.5

2012-02-29T21:07:10Z

Striker: moved Lunar Linux:Installation-1.6.5 to Lunar Linux:Installation/1.6.5: Moving installation pages to sub-page of Installation

__TOC__

Lunar Linux is a revolutionary Linux distribution in that it is not binary based, as are most distributions, but is instead built entirely by compiling source code, using your own custom optimizations.

Essentially, it installs a complete bootstrap development system on your machine, and then you tell the Lunar package manager what tools you want, and it builds the entire system by downloading current source code and locally compiling an optimized system tailored toward your specific needs.

The result is a leaner, meaner, refreshingly uncluttered, and strikingly faster operating system than most Linux distributions.

This installation guide is designed to get you through the installation process as painlessly as possible. It assumes that you have some experience with Linux or another Unix variant, and have a general idea of what you are doing. If you are unfamiliar with such things as partitions, or have never used Linux before, Lunar may not be the best introduction for you into the world of open source. There are always Lunar gods available on irc.freenode.net in the #lunar channel to answer any questions that this manual may not make quite clear enough.

With that said, we hope you enjoy using Lunar!

==About this installation manual==

Although this manual is not intended to be a full and complete overview of any situation you may be confronted with, given the wide diversity of hardware available these days, it is intended to be an introduction to the world of Lunar Linux. You will see examples that are not tailored towards your to-be built server or workstation, optimizations that are overly broad or too specific, and examples that don't apply to any real situations. We tried hard to give you the idea of how much power you have over how you can setup your system, but we are forgetting to tell you how to run your own server or desktop (or other system) at all. That means that the examples and steps taken most probably do not apply to your situation at all.

Do not despair: if you understand what is going on and you get the idea, the installer will allow you to do pretty much everything you want to do with your system. There are really (almost) no limits.

==Getting the ISO==

The primary site for retrieving the ISO is [http://www.lunar-linux.org/ lunar-linux.org]. There, you will find links to our US, EU, and Internet2 mirrors, as well as a Bittorrent link. As of this writing, the current version of the Lunar ISO is version 1.6.5-rc1, codename Mare Ingenii (20100709). (''Check the main site for the actual latest version!'')

Locate and retrieve the file lunar-1.6.5-rc1-i686.iso.bz2 (or lunar-1.6.5-rc1-x86_64.iso.bz2 if you have a 64-bit system). After downloading this file, you will need to unpack the ISO using bzip2. Windows users will need a program that can extract bzip2 archives, like WinZip (also capable of extracting bzip2 archives under windows are IZarc, Winrar, powerarchiver and 7-Zip). Mac should unzip the file by itself. Then all that is left to do is use your favorite program to burn the ISO to a cdrom and begin the installation. Lunar can also be installed without using a CD. If you need to do it this way, our [[FAQ]] provides simple instructions.

It should be noted that the 1.6.5 ISO and Lunar use udev for device management. The devfs system, and the "old-school" method of manually installing devices, are no longer supported.

We are assuming the you are installing Lunar as your primary OS. Make sure you have a backup of any important data that you need to retain. The Lunar Linux Project and its developers are not responsible in any way for any loss of data on your system!

==Booting the ISO==

Upon booting the ISO, the first thing you will see are options for booting the ISO kernel, or for performing RAM tests [Note: MemTest is not available on x86_64]. There is even a safe mode which will disable DMA, MTRR, RAID, LVM, USB keyboards, NTFS, HPFS, Advanced Partitions, and Firewire. Most folks, however, will be just fine pressing enter at the boot prompt and loading the default kernel.

To boot the iso with support for your usb keyboard:
''linux uhci-hcd ehci-hcd''

After loading the kernel, the first screen presents you with a few options. If there are extra modules you need to load in order continue with the install, they can be loaded here. There is also a shell option. However, if you are using this ISO for rescue purposes, you do not want to shell out here; rather continue booting and shell out in the next section. Most people will select "continue booting" here.

It should be noted that the 1.6.5 ISO tries to autodetect some hardware (mostly scsi drivers and network interfaces) during this stage. This will help you establish a network connection if you desire so during installation. For this reason the programs 'dhcpcd' and 'ftp' are already available at this stage.

==Virtual Consoles==

Once the ISO has booted into the installer, you can immediately shell out or switch to one of the other virtual consoles. These will have ready to go root shells and are available throughout the installer sequence. With these you can start rescue actions, setup networking or double check the install progress and make manual adjustments.

==Language and keyboard interface Settings==

After reading the introduction, you will be presented with options for choosing the proper font, keymap, and language for your install.
You will also need to choose an editor, as you are going to need one later on in the installation for setting up your lilo or grub configuration. The choices available are e3, [e3/emacs], joe, nano, vi, and zile. If you have never used a text editor in Linux before, nano is the best choice for you. If you skip the Native Language Support option, the system will install the default editor, nano, for you. When you have finished setting up your options, press cancel to return to the main setup menu.
Less important for most people is the ability to choose the console font, although it may help display some non-English characters. Most people will want to set the system-default language variable and editor though. All these values are unset by default, so make sure you set them now.
The keymap table allows people to use azerty and dvorak keyboards, and much more. This is especially required for non-English keyboards which provide many accented characters.
All these language and keymap settings might not apply to the lunar code itself, which (currently) does not have any international support, but most programs that run during the installer sequence, and after booting into your new system, will be affected properly.

Warning: the keymap entry appears to default to ANSI-dvorak so make sure that you really select what you want.

==Creating or editing Partitions==

The next step is to set up partitions on your hard drive. Upon selecting the "Partition Drive" option, you will be shown a list of all the discs the kernel has detected. For this guide, we will assume that you have one hard drive connected via an IDE channel, which will show up in the menu as "disc0". After selecting the disc to partition, you are given the option of using one of three partitioning programs. They are:

* cfdisk -- A menu driven partitioner, and very easy to use. If you are unfamiliar with various partitioning programs, this is the best option for you.
* fdisk -- Text based partitioner that requires a little more know-how than cfdisk. More experienced users will probably use this program. However new users should not be daunted, as it does have help offered at every step.
* parted -- Text based partitioner that is good for advanced users. Parted is excellent for resizing current partitions on your hard disk, however be forewarned that resizing partitions is an excellent way to hose your entire disc.

Note: under the <Settings> option on the main menu there is an option to configure the fstab mount style as DEV, LABEL or UUID. The first is the traditional Linux method, but can sometimes give problems if a kernel update causes the disk to be renamed. The default is UUID, which uses a unique marker on the partition to avoid this problem.

For our example, we have a 40GB IDE drive and we'll set up six partitions; /, /boot, /home, /usr, /var, and a swap partition. It's a good idea to keep certain directories, such as /var and /usr on separate partitions, as this can save you a lot of headache in the future in case your disk ever completely fails on you and you need to recover data (God forbid!). Also, when you have a separate /boot partition as we have in our example, you need to have your partitioning program mark that partition as active or bootable. In our example, if we were using fdisk, you would press "a" at the command line, and then select part1 as the active partition.

You might also want to install a /tmp partition. By default, Lunar will create a tempfs filesystem mounted on /tmp (tempfs minimizes filesystem fragmentation because it resides in volatile memory). This can be a good choice if you have a lot of memory on your machine. If memory is tight, we recommend creating a /tmp partition to minimize filesystem fragmentation.

It is important to note that you <span class="emphasis">''can not''</span> mount the directories /etc, /bin, /sbin, /dev, /lib and /proc on separate partitions. These directories need to be contained within the root ("/") directory. The installation program should block you from doing this, but it's best not to try.

Here's our partition setup:

1 /boot 100MB
2 / 4GB
3 swap 1GB
5 /usr 10GB
6 /var 10GB
7 /home 15GB

(''If you're wondering about this choice of partitions: it's really just an example. Read the [[FAQ#So_how_should_I_partition_my_disk.3F|FAQ]] on what makes sense in the real world''))

You'll notice that there is no fourth partition in our list above. In order for you to have more than four partitions on a single drive, the fourth partition is made into what is known as an extended or logical partition in which the fifth, sixth, and seventh (etc, etc) partitions reside. For our example above, if we were using fdisk, we would make the fourth partition an extended/logical partition that was 35GB, and then the fifth, sixth, and seventh partitions in our scheme resided within it. However, if we used cfdisk, we would just worry about creating six partitions, making sure that the first three are the primary type, and the last three logical.

Note that the names and mount points for these partitions will be assigned during the next step of this process, when you mount the partitions. Write down exactly what partitions you are planning to create because it can otherwise get confusing!

Lunar offers two choices when it comes to swap. You can set up a swap partition, as we have in our example, or you can set up a swapfile in the root directory. We recommend setting up a swap partition, as you will get better performance with it than with the swapfile. However, there may be a need for you to set up the swapfile instead, which can be setup and activated after you have mounted your other partitions.

==Selecting Partitions and Filesystems==

After creating your partitions, you need to select them and assign file systems. Select the menu option "Select Filesystems" and verify that you are indeed done creating partitions.

The partitions can be selected in random order with the new installer. First select the partition and then assign a filesystem and mountpoint to it. The installer will add this to the job queue and formatting and mounting takes place later so you can edit your selection. Here's a list of filesystems that are currently supported:

* ''ext4'' (Fourth Extended File System) -- Version 4 of the Extended File System, which was ... TO BE COMPLETED.
* ''ext3'' (Third Extended File System) -- Version 3 of the Extended File System, which is essentially just the journaled version of ext2. This filesystem is available with all kernels on the ISO.
* ''ext2'' (Second Extended File System) -- Version 2 of the Extended File System, which was designed for linux as a replacement for the Minix Filesystem. Ext2 is not a journaled filesystem, which means that you'll need to perform disc recovery operations after a power failure or other such system crash. This filesystem is available with all kernels on the ISO.
* ''reiserfs'' (Reiser Filesystem) -- Journaled filesystem created by Hans Reiser that is excellent for use with extremely small files. This filesystem is available with all kernels on the ISO.
* ''xfs'' -- Created by SGI for IRIX, SGI's brand of Unix, and later ported to linux under the GPL. A journaled filesystem that SGI claims is better than any other at handling extremely large files and sparse files. This filesystem is only available with the lunar or grsec patched kernels, which we will come to in a few steps.
* ''jfs'' (Journaled File System) -- Created by IBM for AIX, IBM's brand of Unix, and later ported to linux by IBM under the GPL. A journaled filesystem that is very good at handling high throughput issues. This filesystem is available with all kernels on the ISO.
* ''swap'' Swap (Virtual memory or paging filesystem) for swap partitions only!

After selecting the filesystem type you wish to use, you will be prompted through a series of steps to initialize the partition. You'll notice that the prompts are quite redundant in nature in order to be absolutely positive that you will not inadvertantly erase crucial data that you might have on a working filesystem. In addition, if you have more than four partitions, as we do in our example, you don't want to select any file systems on the fourth partition, as it is the extended partition that houses the fifth, sixth (and so on) partitions. (The installer will try to detect this and skip the extended partition from the list).

As we mentioned earlier, there is an option in the installation process to set up a swap file in the root partition instead of a swap partition as we have done in our example. The next option after selecting your filesystems is to select a swapfile if you so desire. <span class="emphasis">''If you have set up a swap partition already, as we have done, you can skip this step.''</span> Otherwise, you can set up your swap file here, and the only thing you need to tell the installer is how large you want the file to be. Running without swap completely is also possible of course.

'''Please note during this step, no modifications are made to your filesystem!'''

==Installing Lunar==

Next, we need to ''format'' your partitions, ''mount'' them in the right place, create ''swap'' and transfer the entire Lunar system to the partitions that you now have created. This happens all in one single step.

Select ''Install Lunar'', and the system will proceed to transfer all of the necessary files for you. The installer will display progress as packages are transferred to your system and you'll have some idea how long it will take. On normal machines, this should take about 5 minutes.

At the end of this step, the installer sets various system parameters like language, timezone and vital package configuration files in order for your machine.

==Setting Up Your Compiler Optimizations==

The compiler optimizations is a crucial step, since what you choose will make your system fly! However, it is important that you do not overdo it on you optimization settings, as certain selections can, in some instances, break code while compiling.

The first step is to choose your preferred compiler. There is only one version on the 1.6.5 ISO, so the only option here is GCC 4.4. However, once the main system installation is complete, it is possible to install GCC 3.x -- and even the deprecated GCC 2.x! If you don't intend to install those, you should go to the GCC_4_4 submenu now and set GCC 4.4 as the default compiler.

The GCC_4_4 menu also allows you to change other options:

* ''safe'' : allows you to turn off optimization safety, so you should leave this well alone unless you really know what you are doing. Turning this off will result in many more options appearing than are described below.
* ''bopt'' : allows you to change the base compile-time optimization. Your choice depends on what your needs are. Most folks will want to use -O2 here, as it is the wisest choice. More advanced users may want to use the -O3 option, but it's not for everyone. If you're short on disk space, you would take the -Os Small option. (As an example, we used -Os for the ISO since we were working within a confined amount of disc space.) Those of you with older or slower systems that wouldn't be able to take advantage of faster optimizations may choose a more conservative setting like -O1. For our example system, we will choose -O2.
* ''cpu'' : allows you to set your processor type. This may seem unimportant, but the GCC 4.x [and GCC 3.x] compiler has ways of optimizing code for certain processors
* ''cc_opt'' : allows you to set some limited C/C++ compiler settings. Very few people, if any, would need to turn off the -pipe option.

The unsafe optimizations are:
* ''xtra'' : CPU extensions
* ''spd'' : Specialized optimizations
* ''fpm'' : Floating point optimizations
* ''stack'' : Stack optimizations

==Adding Other Compiler Toolchain Optimizations==

'''You can safely SKIP this entire step!'''

The GNU_LD menu shows the screen for linker options, where you will find that "-s Strip" has already been checked off. Very few people will want to uncheck this option, so we will leave this screen as is.

The GNU_MAKE menu allows you to set the number of concurrent makes. As the hint mentions on the "Concurrent Makes" screen, you'll want to enter in the number of cpu's your machine has. Unless you have a machine with more than one processor, you'll want to leave this field blank.

We are now finished setting up our GCC optimizations! When you have you lunar system up and running, you can always change and tweak these GCC settings by typing "lunar" at the commandline prompt, and going to "Optimization Settings". In addition, if you aren't that familiar with what your processor is capable of using for optimizations, you can go to the shell out option on the ISO and type

cat /proc/cpuinfo

at the prompt and the system will show you all the optimizations that the processor reports it can handle.

==Configuring Your Bootloader==

=== Configuring LILO ===

If you chose to use lilo and also said yes to automatically configuring and running lilo, then most of the work is done for you. If you chose not to hand edit lilo.conf, however, be warned that the default configuration has the system set up to be password protected on boot. You can change this by selecting the option from the menu "Reconfigure LILO".

To turn off password protection, you will need to comment out (with the symbol "#") or delete two lines in your lilo.conf file. The first is "password=lunar", which is found in the top section of the file, and the other is "restricted" which is found right below the name of your kernel in the second section.

The other item of note is whether you want lilo to reside in your MBR (Master Boot Record) or on the first sector of your /boot partition. The line in your lilo.conf file to edit for this purpose is

boot=/dev/sda1

To make lilo get installed on the first sector of your /boot partition, you would leave this line as it is. If you want lilo to be written to your MBR, which is the recommended method, you would change the line to read

boot=/dev/sda

Of course, these examples are pertinent to our setup that we have been using thoughout this manual. Your actual lilo.conf file may be different.

=== Configuring GRUB ===

If you chose grub as your bootloader, you will need to set up the configuration file entirely on your own. An example would be:

default 0
timeout 30
color white/blue white/black
title linux-2.4.25
root (hd0,0)
kernel /vmlinubz-2.4.25-r5.0.0 root=/dev/sda2 devfs=nomount

As we mentioned earlier in the partitioning section, you would want to mark your /boot partition as active. With grub it is ''imperative'' that you mark your /boot partition as active, otherwise grub will not work at all when you are finished with the installation and reboot to your new system.

NOTE: The option to install grub is not available on the 1.6.5-rc1-x86_64 ISO because grub is not yet fully stable on 64-bit systems. If you really know what you are doing, the source tarball is saved to disk, so you can configure it manually once the main installation is complete.
==Installing kernels==

===Installing a precompiled kernel===

The ISO comes with a selection of precompiled kernels and modules that should work for most people. If you have problems getting your kernel to compile, install or getting the right drivers, or just want to get a quick start at lunar, we ''suggest'' that you use this option instead of compiling your own kernel. You can later of course compile as many kernels as you want, and indeed the first ''lunar update'' after the main installation might ask whether you want to update the kernel too. Why do it twice if you don't need to?

There are several kernels for you to choose from. They are:

* ''2.6.34.1'' -- Normal kernel (SMP, 4GB memory max) (RECOMMENDED).
* ''2.6.34.1-safe'' -- Very safe non-optimized minimal kernel (no ACPI, DMA, SMP, 1GB).
* ''2.6.34.1-server'' -- Server optimized (SELINUX, SMP, 64GB, no preempt).

===Building Your Customized Linux Kernel===

We have now come to the most important part of the installation; the configuration of the kernel. The kernel is the heart of Linux, and without it, nothing would work. Configuration is, actually, a rather simple process. All you need to remember is to not panic, and that lunar is going to do most of the work for you. Here are a few pointers that will make the configuration a breeze for you.

* Help is a click away! The people working on creating and maintaining the Linux kernel have help placed throughout the entire configuration process. If you're not sure what something does, just look at the help file for whatever item you're on, and it will almost certainly explain what it is and what it does. The most handy thing is that every help file will suggest whether you should really use the item or not. Many help files end with "If you're not sure, it is safe to say N here", thus letting you know that it is safe to leave that particular item out of the kernel.
* You can use the ISO kernel! The configuration used to make the kernel for the ISO is the same configuration you'll see when you start your kernel customization. If you leave the configuration the way it is, the only thing you truly have to worry about is your network and, if you want it, sound. There are also two additional default configurations available on the ISO that are available to you called "config.safe" and "config.server". We'll show you how to load these configurations in just a little bit. [TODO: check these files]
* Never build filesystems or core components as modules! Make sure that whatever filesystems you decided to use for your partitions earlier are built into the kernel, and are not separate modules. Likewise, make sure that certain crucial things like ide and scsi drivers are not modules, as this will make your machine unbootable. (This rule doesn't apply to the scsi low level drivers though; they can be modules.) Modules are kernel drivers that can be manually activated and deactivated after the system has been booted, but not during boot time. The kernel from the ISO already has all the filesystems available during the installation built into the kernel, so if you don't change anything there, you will be fine.

You will be shown two screens of information before you actually begin you kernel configuration, letting you know that you are going to need a few things built into the kernel in order to have Lunar run properly, and what options you have for boot loaders. Lunar comes with both lilo (LInux LOader) and grub (GRand Unified Bootloader).

If you don't have much experience with bootloaders, we suggest using lilo for now, as the installation program will set up the configuration file for you. If you would prefer to use grub, and we encourage folks to learn how to use it, be forewarned that the installation program does not set up any configuration at all for you.

[On the 1.6.5-rc1-x86_64 ISO] There is only one kernel available for you to choose from:

* ''linux-2.6.'' -- Latest 2.6 kernel with minor patchlevel patches (2.6.x.Y)

For our example, we are going to use linux-2.6.

Before you begin is which type of configuration method you would like to use.

* ''config'' -- The original way to configure the linux kernel. It is completely text based, and assumes you know what everything is. Unless you've been using linux since its inception, you probably don't want to use this method.
* ''menuconfig'' -- As the name implies, a menu driven version of the kernel configuration. This is the easiest, and by far the most popular way of configurating your kernel.
* ''xconfig'' -- If you have an X server running, you can use this option to configure your kernel using a nifty GUI interface. You won't be able to use this on the ISO, but once your system is up and running with X, you can use this option. If you do choose this option while installing from the ISO, the system will fall back to next available configuration method, in this case menuconfig, so there is no harm in selecting it if you do.

For our example, we are going to use menuconfig. Once Lunar is finished applying the patches for the kernel, which can take a minute or two, you'll be brought to the configuration screen for the linux kernel.

As we mentioned earlier, the configuration that was used to build the kernel for the ISO is the same configuration that you'll be presented with when you start. However, as we also mentioned earlier, there are two alternate kernel configurations available to you that you may want to use; config.safe and config.server. Both of these configurations can be found on the ISO, along with the original default config file, in /etc/lunar/local. When you are looking at the kernel menuconfig main page, scroll all the way to bottom, and you will find an option called "Load an Alternate Configuration File". Select this and then give the absolute path to the alternate configuration file, i.e. /etc/lunar/local/.config.server. As with all kernel configuration files, they are hidden files preceded with a ".", so make sure to not forget it.

Once you have completed configuring your kernel, you'll get one more prompt from the installer asking if you want to go back to the configuration in case you exited by mistake or forgot something. If everything is good to go, say no here and sit back for a few minutes while your kernel compiles.

==Setting Up Networking==

The final step is to set up networking. When you select the "Set Up Networking" option, you'll be prompted by a series of questions as to what kind of card you have (only needed if you built your networking device as a module, and not part of the kernel), if you need to set up wireless or not, and whether you'll need to use dhcp or not. You should be familiar enough with your network to set this up on your own, as the questions put to you are very straightforward.

* if you use dhcp, you don't need to set up the default gateway or DNS because dhcp will take care of them for you.
* you are using a wireless connection with wpa_supplicant, you might want to run "wpa_passphrase" to set up a simple /etc/wpa_supplicant.conf rather than try to edit the example file.

==Other settings==

The installer will prompt you now for some more settings. You should set a root password and generate ssh host keys to identify your box uniquely for later. You might also want to administrate services on the newly installed machine.

==Reboot!==

Once you have completed setting up your networking, you are finished installing Lunar Linux! Congratulations! Select the option "Done" and remove the cd from the drive when it ejects. Your Lunar system is now ready to go!

==Upgrade Moonbase==

After the initial installation and reboot, please follow the instructions given in '''man lfirsttime''' to bring your system up-to-date.

Congratulations! You now have a minimal system as a foundation on which to build.

==KNOWN PROBLEMS==

=== You need to run 'lin linux-2.6' explicitly before running 'lunar update' ===

WARNING: the pre-compiled 2.6.35.3 kernel on the ISO is now out-of-date compared to the ''linux-2.6'' module in the moonbase, but you will
need to build it explicitly using '''lin linux-2.6''' because it won't be rebuilt as part of the first '''lunar update'''. If you didn't
recompile the kernel as part of the ISO installation, or if you experience problems with ALSA or NVIDIA, you should run '''lin linux-2.6'''
to rebuild the kernel explicitly. After you have built the kernel once, '''lunar update''' should then detect and install a newer versions
of the kernel as they become available in the moonbase.

=== configure: error: C compiler cannot create executables ===

WARNING: the ISO installs gcc-4.4 on your system, but gcc-4.5 will be installed as part of the '''man lfirsttime''' and '''lunar update'''
process. You will then need to run '''lunar''', select the '''Options / Optimize Architecture''' menu and set the gcc-4.5 options. Failure
to do so may result in ''"configure: error: C compiler cannot create executables"'' messages when building modules later.

==Where to go from here==
To install a desktop environment check out this page. [[Lunar_Linux:DesktopEnvironments]]

''Have Phun!!''

[http://www.gnu.org/copyleft/ Copyleft] 2004-2010 [http://lunar-linux.org/ The Lunar Penguin Team]

Lunar Installation Manual and Harassment of Lunar Developers by Drew Swayze (drew AT lunar-linux DOT org).

Edits and Nitpicking by Suzanne Burns (sburns AT lunar-linux DOT org).

Initial update for the 1.6.5 ISO by Duncan Gibson (engelsman AT lunar-linux DOT org).

Lunar Linux:Installation/1.5.0

2012-02-29T21:06:32Z

Striker: moved Lunar Linux:Installation to Lunar Linux:Installation/1.5.0: Move old installation page

__TOC__

Lunar Linux is a revolutionary linux distribution in that it is not binary based, as are most distributions, but is instead built entirely by compiling sourcecode, using your own custom optimizations.

Essentially, it installs a complete bootstrap development system on your machine, and then you tell the Lunar package manager what tools you want, and it builds the entire system by downloading current source code and locally compiling an optimized system tailored toward your specific needs.

The result is a leaner, meaner, refreshingly uncluttered, and strikingly faster operating system than most linux distributions.

This installation guide is designed to get you through the installation process as painlessly as possible. It assumes that you have some experience with linux or another Unix variant, and have a general idea of what you are doing. If you are unfamiliar with such things as partitions, or have never used linux before, Lunar may not be the best introduction for you into the world of open source. There are always Lunar gods available on irc.freenode.net in the #lunar channel to answer any questions that this manual may not make quite clear enough.

With that said, we hope you enjoy using Lunar!

==About this installation manual==

Although this manual is not intended to be a full and complete overview of any situation you may be confronted with, given the wide diversity of hardware available these days, it is intended to be an introduction to the world of Lunar Linux. You will see examples that are not tailored towards your to-be built server or workstation, optimizations that are overly broad or too specific, and examples that don't apply to any real situations. We tried hard to give you the idea of how much power you have over how you can setup your system, but we are forgetting to tell you how to run your own server or desktop (or other system) at all. That means that the examples and steps taken most probably do not apply to your situation at all.

Do not despair: if you understand what is going on and you get the idea, the installer will allow you to do pretty much everything you want to do with your system. There are really (almost) no limits.

==Getting the ISO==

The primary site for retrieving the ISO is [http://www.lunar-linux.org/ lunar-linux.org]. There, you will find links to our US, EU, and Internet2 mirrors, as well as a Bittorrent link. As of this writing, the current version of the Lunar ISO is version 1.5.0. (''Check the main site for the actual latest version!'')

Locate and retrieve the file lunar-1.5.0-i686.iso.bz2. After downloading this file, you will need to unpack the ISO using bzip2. Windows users will need a program that can extract bzip2 archives, like WinZip (also capable of extracting bzip2 archives under windows are Winrar, powerarchiver and 7-Zip). Mac should unzip the file by itself. Then all that is left to do is use your favorite program to burn the ISO to a cdrom and begin the installation. Lunar can also be installed without using a CD. If you need to do it this way, our [[FAQ]] provides simple instructions.

It should be noted that this ISO and Lunar use devfs for device management. If you prefer the "old-school" method of manually installing devices, there is an ISO available with this option at [http://thing.fwsystems.com/build/lunar/lunar-1.3_stddev.iso.bz2 thing.fwsystems.com].

We are assuming the you are installing Lunar as your primary OS. Make sure you have a backup of any important data that you need to retain. The Lunar Linux Project and its developers are not responsible in any way for any loss of data on your system!

==Booting the ISO==
Upon booting the ISO, the first thing you will see are options for booting the ISO kernel, or for performing RAM tests. There is even a safe mode which will disable DMA, MTRR, RAID, LVM, USB keyboards, NTFS, HPFS, Advanced Partitions, and Firewire. Most folks, however, will be just fine pressing enter at the boot prompt and loading the default kernel.

To boot the iso with support for your usb keyboard:
''linux uhci-hcd ehci-hcd''

After loading the kernel, the first screen presents you with a few options. If there are extra modules you need to load in order continue with the install, they can be loaded here. There is also a shell option. However, if you are using this ISO for rescue purposes, you do not want to shell out here; rather continue booting and shell out in the next section. Most people will select "continue booting" here.

It should be noted that since 1.5.0, the iso tries to autodetect some hardware (mostly scsi drivers and network interfaces) during this stage. This will help you establish a network connection if you desire so during installation. For this reason the programs 'dhcpcd' and 'ftp' are already available at this stage.

==Virtual Consoles==
Once the ISO has booted into the installer, you can immediately shell out or switch to one of the other virtual consoles. These will have ready to go root shells and are available throughout the installer sequence. With these you can start rescue actions, setup networking or double check the install progress and make manual adjustments.

==Language and keyboard interface Settings==

After reading the introduction, you will be presented with options for choosing the proper font, keymap, and language for your install.
You will also need to choose an editor, as you are going to need one later on in the installation for setting up your lilo or grub configuration. The three choices available are vi, joe, and nano. If you have never used a text editor in linux before, nano is the best choice for you. If you skip the Native Language Support option, the system will install the default editor, nano, for you. When you have finished setting up your options, press cancel to return to the main setup menu.
Less important for most people is the ability to choose the console font, although it may help display some non-english characters. Most people will want to set the system-default language variable and editor though. All these values are unset by default, so make sure you set them now.
The keymap table allows people to use azerty and dvorak keyboards, and much more. This is especially required for non-english keyboards which provide many accented characters.
All these language and keymap settings might not apply to the lunar code itself, which (currently) does not have any international support, but most programs that run during the installer sequence, and after booting into your new system, will be affected properly.
==Creating or editing Partitions==

The next step is to set up partitions on your hard drive. Upon selecting the "Partition Drive" option, you will be shown a list of all the discs the kernel has detected. For this guide, we will assume that you have one hard drive connected via an IDE channel, which will show up in the menu as "disc0". After selecting the disc to partition, you are given the option of using one of three partitioning programs. They are:

* cfdisk -- A menu driven partitioner, and very easy to use. If you are unfamiliar with various partitioning programs, this is the best option for you.
* fdisk -- Text based partitioner that requires a little more know-how than cfdisk. More experienced users will probably use this program. However new users should not be daunted, as it does have help offered at every step.
* parted -- Text based partitioner that is good for advanced users. Parted is excellent for resizing current partitions on your hard disk, however be forewarned that resizing partitions is an excellent way to hose your entire disc.

For our example, we have a 40GB IDE drive and we'll set up six partitions; /, /boot, /home, /usr, /var, and a swap partition. It's a good idea to keep certain directories, such as /var and /usr on separate partitions, as this can save you a lot of headache in the future incase your disk ever completely fails on you and you need to recover data (god forbid!). Also, when you have a separate /boot partition as we have in our example, you need to have your partitioning program mark that partion as active or bootable. In our example, if we were using fdisk, you would press "a" at the command line, and then select part1 as the active partition.

You might also want to install a /tmp partition. By default, Lunar will create a tempfs filesystem mounted on /tmp (tempfs minimizes filesystem fragmentation because it resides in volatile memory). This can be a good choice if you have a lot of memory on your machine. If memory is tight, we recommend creating a /tmp partition to minimize filesystem fragmentation.

It is important to note that you <span class="emphasis">''can not''</span> mount the directories /etc, /bin, /sbin, /dev, /lib and /proc on separate partitions. These directories need to be contained within the root ("/") directory. The installation program should block you from doing this, but it's best not to try.

Here's our partition setup:

1 /boot 100MB
2 / 4GB
3 swap 1GB
5 /usr 10GB
6 /var 10GB
7 /home 15GB

(''If you're wondering about this choice of partitions: it's really just an example. Read the [[FAQ#So_how_should_I_partition_my_disk.3F|FAQ]] on what makes sense in the real world''))

You'll notice that there is no fourth partition in our list above. In order for you to have more than four partitions on a single drive, the fourth partition is made into what is known as an extended or logical partition in which the fifth, sixth, and seventh (etc, etc) partitions reside. For our example above, if we were using fdisk, we would make the fourth partition an extended/logical partition that was 35GB, and then the fifth, sixth, and seventh partitions in our scheme resided within it. However, if we used cfdisk, we would just worry about creating six partitions, making sure that the first three are the primary type, and the last three logical.

Note that the names and mount points for these partitions will be assigned during the next step of this process, when you mount the partitions. Write down exactly what partitions you are planning to create because it can otherwise get confusing!

Lunar offers two choices when it comes to swap. You can set up a swap partition, as we have in our example, or you can set up a swapfile in the root directory. We recommend setting up a swap partition, as you will get better performance with it than with the swapfile. However, there may be a need for you to set up the swapfile instead, which can be setup and activated after you have mounted your other partitions.

==Selecting Partitions and Filesystems==

After creating your partitions, you need to select them and assign file systems. Select the menu option "Select Filesystems" and verify that you are indeed done creating partitions.

The partitions can be selected in random order with the new installer. First select the partition and then assign a filesystem and mountpoint to it. The installer will add this to the job queue and formatting and mounting takes place later so you can edit your selection. Here's a list of filesystems that are currently supported:

* ''ext2'' (Second Extended File System) -- Version 2 of the Extended File System, which was designed for linux as a replacement for the Minix Filesystem. Ext2 is not a journaled filesystem, which means that you'll need to perform disc recovery operations after a power failure or other such system crash. This filesystem is available with all kernels on the ISO.
* ''ext3'' (Third Extended File System) -- Version 3 of the Extended File System, which is essentially just the journaled version of ext2. This filesystem is available with all kernels on the ISO.
* ''reiserfs'' (Reiser Filesystem) -- Journaled filesystem created by Hans Reiser that is excellent for use with extremely small files. This filesystem is available with all kernels on the ISO.
* ''jfs'' (Journaled File System) -- Created by IBM for AIX, IBM's brand of Unix, and later ported to linux by IBM under the GPL. A journaled filesystem that is very good at handling high throughput issues. This filesystem is available with all kernels on the ISO.
* ''xfs'' -- Created by SGI for IRIX, SGI's brand of Unix, and later ported to linux under the GPL. A journaled filesystem that SGI claims is better than any other at handling extremely large files and sparse files. This filesystem is only available with the lunar or grsec patched kernels, which we will come to in a few steps.

After selecting the filesystem type you wish to use, you will be prompted through a series of steps to initialize the partition. You'll notice that the prompts are quite redundant in nature in order to be absolutely positive that you will not inadvertantly erase crucial data that you might have on a working filesystem. In addition, if you have more than four partitions, as we do in our example, you don't want to select any file systems on the fourth partition, as it is the extended partition that houses the fifth, sixth (and so on) partitions. (The installer will try to detect this and skip the extended partition from the list).

As we mentioned earlier, there is an option in the installation process to set up a swap file in the root partition instead of a swap partition as we have done in our example. The next option after selecting your filesystems is to select a swapfile if you so desire. <span class="emphasis">''If you have set up a swap partition already, as we have done, you can skip this step.''</span> Otherwise, you can set up your swap file here, and the only thing you need to tell the installer is how large you want the file to be. Running without swap completely is also possible of course.

'''Please note during this step, no modifications are made to your filesystem!'''

==Installing Lunar==

Next, we need to ''format'' your partitions, ''mount'' them in the right place, create ''swap'' and transfer the entire Lunar system to the partitions that you now have created. This happens all in one single step.

Select ''Install Lunar'', and the system will proceed to transfer all of the neccessary files for you. The installer will display progress as packages are transferred to your system and you'll have some idea how long it will take. On normal machines, this should take about 5 minutes.

At the end of this step, the installer sets various system parameters like language, timezone and vital package configuration files in order for your machine.

==Setting Up Your GCC Architecture Optimizations==

The architecture optimizations is a crucial step, since what you choose will make your system fly! However, it is important that you do not overdo it on you optimization settings, as certain selections can, in some instances, break code while compiling.

The first step is to choose your preferred compiler. The default choice here is GCC 3.x, and is the preferred choice as GCC 2.x is no longer under development, and GCC 3.x is known to make compiled code run faster. For our example, we are going to use GCC 3.x.

Next are options for the C and C++ compiler, called -pipe, that have already been checked off. Very few people, if any, would need to turn off the -pipe option, so in our example we are going to leave them checked.

Next we have the platform selection. This question would seem to be rather silly, since our ISO only boots up on x86 systems, but we like to plan for the future. You'll want to say x86 here.

Now we move onto the Basic Optimization screen. As you can see, the options speak for themselves. Your choice depends on what your needs are. Most folks will want to use -O2 here, as it is the wisest choice. More advanced users may want to use the -O3 option, but it's not for everyone. If you're short on disk space, you would take the -Os Small option. (As an example, we used -Os for the ISO since we were working within a confined amount of disc space.) Those of you with older or slower systems that wouldn't be able to take advantage of faster optimizations may choose a more conservative setting like -O1. For our example system, we will choose -O2.

After choosing your basic optimization level, you'll need to tell the compiler what type of processor you have. This may seem unimportant, however the GCC 3.x compiler has ways of optimizing code for certain processors, even though they all may be x86 based. For example, GCC 3.x has certain optimizations it can perform on code for Pentium 4 machines, but not for Pentium 3. Our example machine is a Pentium 3, so we are going to select that.

We could also select i686, as a Pentium 3 or Pentium Pro falls within that architecture. Choosing i686 is a more conservative choice than Pentium 3, as GCC 3.x will not try certain optimizations with a more general choice like i686.

==Adding Additional GCC Optimizations==

'''You can safely SKIP this entire step!'''

Next up are some extra speed optimizations you can add in to tweak your code even futher. There are too many to go into much detail here, but suffice to say that you should choose carefully. As we mentioned in the prior section, certain optimizations will cause compilation errors or even failures. An optimization such as "-ffast-math" is very risky because it breaks certain rules to get faster code, and would only be used by the bravest of souls looking to endure lots of pain. More information about GCC 3.x optimization strings can be found on the [http://gnu.org/software/gcc/gcc.html gnu.org] website.

The same rule applies on the next screen, where you are asked about some extra features that you may want further optimized, and on the following screen asking about floating point math optimizations. Some options may not pose a problem at all, while others may break things.

Moving on to the next few screens, we have options to enable or disable C and C++ compiler warnings. Most people will want to leave these boxes unchecked as deprecation warnings can be very useful some of the time. Following that is the screen for linker options, where you will find that "-s Strip" has already been checked off. Very few people will want to uncheck this option, so we will leave this screen as is. After that, we have some addons for compiler caching and distributed compiler support. Most folks will not need either one of these.

The final few steps involve setting up the number of concurrent makes and stack parameters. As the hint mentions on the "Concurrent Makes" screen, you'll want to enter in the number of cpu's your machine has. Unless you have a machine with more than one processor, you'll want to leave this field blank. The stack parameters is also fairly straightforward. The warning on that screen says that this field is best left empty, and so that is exactly what we will do with our example.

We are now finished setting up our GCC optimizations! When you have you lunar system up and running, you can always change and tweak these GCC settings by typing "lunar" at the commandline prompt, and going to "Optimization Settings". In addition, if you aren't that familiar with what your processor is capable of using for optimizations, you can go to the shell out option on the ISO and type

cat /proc/cpuinfo

at the prompt and the system will show you all the optimizations that the processor reports it can handle.

==Configuring Your Bootloader==

=== Configuring LILO ===

If you chose to use lilo and also said yes to automatically configuring and running lilo, then most of the work is done for you. If you chose not to hand edit lilo.conf, however, be warned that the default configuration has the system set up to be password protected on boot. You can change this by selecting the option from the menu "Reconfigure LILO".

To turn off password protection, you will need to comment out (with the symbol "#") or delete two lines in your lilo.conf file. The first is "password=lunar", which is found in the top section of the file, and the other is "restricted" which is found right below the name of your kernel in the second section.

The other item of note is whether you want lilo to reside in your MBR (Master Boot Record) or on the first sector of your /boot partition. The line in your lilo.conf file to edit for this purpose is

boot=/dev/hda1

To make lilo get installed on the first sector of your /boot partition, you would leave this line as it is. If you want lilo to be written to your MBR, which is the recommended method, you would change the line to read

boot=/dev/hda

Of course, these examples are pertinent to our setup that we have been using thoughout this manual. Your actual lilo.conf file may be different.

=== Configuring GRUB ===

If you chose grub as your bootloader, you will need to set up the configuration file entirely on your own. An example would be:

default 0
timeout 30
color white/blue white/black
title linux-2.4.20
root (hd0,0)
kernel /vmlinubz-2.4.25-r5.0.0 root=/dev/hda2 devfs=nomount

As we mentioned earlier in the partitioning section, you would want to mark your /boot partition as active. With grub it is ''imperative'' that you mark your /boot partition as active, otherwise grub will not work at all when you are finished with the installation and reboot to your new system.

==Installing kernels==

===Installing a precompiled kernel===

The ISO's come with a variation of precompiled kernels and modules that should work for most people. If you have problems getting your kernel to compile, install or getting the right drivers, or just want to get a quick start at lunar, we ''suggest'' that you use this option instead of compiling your own kernel. You can later of course compile as many kernels as you want.

===Building Your Customized Linux Kernel===

We have now come to the most important part of the installation; the configuration of the kernel. The kernel is the heart of linux, and without it, nothing would work. Configuration is, actually, a rather simple process. All you need to remember is to not panic, and that lunar is going to do most of the work for you. Here are a few pointers that will make the configuration a breeze for you.

* Help is a click away! The people working on creating and maintaining the linux kernel have help placed throughout the entire configuration process. If you're not sure what something does, just look at the help file for whatever item you're on, and it will almost certainly explain what it is and what it does. The most handy thing is that every help file will suggest whether you should really use the item or not. Many help files end with "If you're not sure, it is safe to say N here", thus letting you know that it is safe to leave that particular item out of the kernel.
* You can use the ISO kernel! The configuration used to make the kernel for the ISO is the same configuration you'll see when you start your kernel customization. If you leave the configuration the way it is, the only thing you truly have to worry about is your network and, if you want it, sound. There are also two additional default configurations available on the ISO that are available to you called "config.safe" and "config.server". We'll show you how to load these configurations in just a little bit.
* Never build filesystems or core components as modules! Make sure that whatever filesystems you decided to use for your partitions earlier are built into the kernel, and are not separate modules. Likewise, make sure that certain crucial things like ide and scsi drivers are not modules, as this will make your machine unbootable. (This rule doesn't apply to the scsi low level drivers though; they can be modules.) Modules are kernel drivers that can be manually activated and deactivated after the system has been booted, but not during boot time. The kernel from the ISO already has all the filesystems available during the installation built into the kernel, so if you don't change anything there, you will be fine.

You will be shown two screens of information before you actually begin you kernel configuration, letting you know that you are going to need a few things built into the kernel in order to have Lunar run properly, and what options you have for boot loaders. Lunar comes with both lilo (LInux LOader) and grub (GRand Unified Bootloader).

If you don't have much experience with bootloaders, we suggest using lilo for now, as the installation program will set up the configuration file for you. If you would prefer to use grub, and we encourage folks to learn how to use it, be forewarned that the installation program does not set up any configuration at all for you.

There are serveral kernels for you to choose from. They are:

* ''linux-2.4'' -- The default kernel for Lunar which is the Linus tree with some handy patches for the xfs filesystem, firewire, ext3, and several other fixes.
* ''linux-2.4-agr'' -- The aggressive patch includes everything from the standard patchset as well as the low latency, pre-emptive, and gcc 3.x architecture type patches.
* ''linux-2.4-grsec'' -- This is almost the same as linux, but with grsecurity, cpu frequency scaling, gcc 3.x architecture types, and crypto support.
* ''linux-2.4-stable'' -- This is the Linus tree with only critical patches for certain drivers that were created after the 2.4.20 kernel was released.
* ''linux-2.4-vanilla'' -- A completely unpatched kernel tree.
* ''linux-2.4-om'' -- A kernel specifically meant for clustering use.

For our example, we are going to use linux-2.4-agr.

Before you begin is which type of configuration method you would like to use.

* ''config'' -- The original way to configure the linux kernel. It is completely text based, and assumes you know what everything is. Unless you've been using linux since its inception, you probably don't want to use this method.
* ''menuconfig'' -- As the name implies, a menu driven version of the kernel configuration. This is the easiest, and by far the most popular way of configurating your kernel.
* ''xconfig'' -- If you have an X server running, you can use this option to configure your kernel using a nifty GUI interface. You won't be able to use this on the ISO, but once your system is up and running with X, you can use this option. If you do choose this option while installing from the ISO, the system will fall back to next available configuration method, in this case menuconfig, so there is no harm in selecting it if you do.

For our example, we are going to use menuconfig. Once Lunar is finished applying the patches for the kernel, which can take a minute or two, you'll be brought to the configuration screen for the linux kernel.

As we mentioned earlier, the configuration that was used to build the kernel for the ISO is the same configuration that you'll be presented with when you start. However, as we also mentioned earlier, there are two alternate kernel configurations available to you that you may want to use; config.safe and config.server. Both of these configurations can be found on the ISO, along with the original default config file, in /etc/lunar/local. When you are looking at the kernel menuconfig main page, scroll all the way to bottom, and you will find an option called "Load an Alternate Configuration File". Select this and then give the absolute path to the alternate configuration file, i.e. /etc/lunar/local/.config.server. As with all kernel configuration files, they are hidden files preceeded with a ".", so make sure to not forget it.

Once you have completed configuring your kernel, you'll get one more prompt from the installer asking if you want to go back to the configuration in case you exited by mistake or forgot something. If everything is good to go, say no here and sit back for a few minutes while your kernel compiles.

==Setting Up Networking==

The final step is to set up networking. When you select the "Set Up Networking" option, you'll be prompted by a series of questions as to what kind of card you have (only needed if you built your networking device as a module, and not part of the kernel), if you need to set up wireless or not, and whether you'll need to use dhcp or not. You should be familiar enough with your network to set this up on your own, as the questions put to you are very straightforward.
coa

==Other settings==

The installer will prompt you now for some more settings. You should set a root password and generate ssh host keys to identify your box uniquely for later. You might also want to administrate services on the newly installed machine.

==Reboot!==

Once you have completed setting up your networking, you are finished installing Lunar Linux! Congratulations! Select the option "Done" and remove the cd from the drive when it ejects. Your Lunar system is now ready to go!

==Upgrade Moonbase==
Following the initial installation and reboot, there are some key things that still need to be updated.

If you have installed from the 1.6.4-alpha or 1.6.4-beta ISO series from September-October 2008, all you should need to do now is follow the instructions given in '''man lfirsttime''' to bring your system up-to-date.

If you have installed from the out-of-date 1.6.2-beta1 ISO from July 2007, it is imperative that you follow the additional instructions given in the [http://www.lunar-linux.org/index.php/en/news-sections/68-general/58-lunar-linux-iso-install-guide.html 1.6.2-beta1 ISO Installation Guide] otherwise you are very likely to break your system before you even get started.

''However, you are strongly advised to install from the most recent ISO to avoid problems!''

''Have Phun!!''

[http://www.gnu.org/copyleft/ Copyleft] 2004 [http://lunar-linux.org/ The Lunar Penguin Team]

Lunar Installation Manual and Harassment of Lunar Developers by Drew Swayze (drew AT lunar-linux DOT org).

Edits and Nitpicking by Suzanne Burns (sburns AT lunar-linux DOT org).

Lunar Linux:Latest

2012-02-29T21:03:14Z

Striker: Redirect so we can have permanent links to latest installation doc

#REDIRECT [[Lunar_Linux:Installation-1.6.5]]

Lunar Linux:FAQ

2012-02-27T16:26:46Z

Striker: Moving Installation section to top where it should technically be.

These are the '''F'''requently '''A'''sked '''Q'''uestions for Lunar Linux. You have a question about Lunar? You might get your answer below.<br /><br />

__TOC__

==General==

===What is Lunar Linux?===
What exactly is Lunar Linux?

'''Answer:'''
* Please read [[Lunar Linux:About|About Lunar Linux]].

===Can I run Lunar Linux in 64-bit mode?===
Can I run Lunar Linux on my new 64-bit system?

'''Answer:'''

Yes you can. You can run Lunar Linux in '''either''' 64-bit '''or''' 32-bit mode, but there is no multi-lib mode. Be aware that some applications are still only available for 32-bit mode!

===Where can I find how to ...?===
Where can I find how to customize the kernel under Lunar Linux? Or the desktop...

'''Answer:'''

The Lunar Wiki only offers details specific to Lunar Linux. Many other resources already exist for general Linux problem solving. For example, information on how to customize the Linux kernel can be found at:
* http://kernelnewbies.org/
* http://en.wikipedia.org/wiki/Linux_kernel_mailing_list

==Lunar-Linux Installation==

===My usb keyboard is not recognized===
At the boot prompt type ''linux uhci-hcd ehci-hcd'' to make sure those modules are loaded during startup. Those will then enable your usb keyboard.

===So how should I partition my disk?===
I'm setting up lunar from scratch, but how should I partition my disk for a server or desktop system?

'''Answer:'''

Server systems have very different demands than desktops. It's all about flexibility. First desktops:

''desktops'' commonly have one hard disk. You don't want to reformat or repartition often, so you just want to be done with it at once. The easiest is just to setup 2 (two) partitions: one root filesystem big enough for all lunar software, and the rest for <code>/home</code>. Typically, lunar occupies between 4 and 12 gb based on how many applications you install. If you clean up often you can manage with 8gb, but you should keep some extra space. I certainly advise to use a swapfile instead of a swap partition: you can always later delete the swap, or move the swapfile to another disk or partition. A swap partition is harder to relocate.

''Servers'' have different needs. First of all <code>/home</code> doesn't need to be that large, but you will want to setup space for logfiles that cannot cause problems if they grow too fast. Putting <code>/var/tmp</code> and <code>/var/log</code> on separate partitions is quite normal. <code>/tmp</code> can be abused similarly, and is mostly run in [[tmpfs]] to avoid cluttering and give fast access times. Then <code>/usr</code> will be separate and the usual separate <code>rootfs</code>. As you can see this list is already getting quite big! Most users will actually want to make the <code>rootfs</code> quite small (as small as 200mb sometimes!) and thus <code>/home</code> also needs to be on a separate partition.

===Kernel features, built-in or module?===
When I compile a kernel, should I compile drivers that I need in the kernel image or as module?

'''Answer:'''

There are many schools of thought on kernel compiling. One is to build everything into the main kernel without modules. The other one takes building modules to the extreme. Here is a suggestion, if it's not needed to boot it's a module. Thus usb, input, sound, mice ACPI, network, and also cdrom, floppy, and all the non boot file systems, all get built as modules. This reduces the size of the main kernel so it can be put on a floppy. Another thing to consider is that not everything works perfectly, and some features can cause your kernel to misbehave, so if some feature is built-in, the bad behavior is practically inevitible. Instead, with a module you can choose not to load it and thus be left with a working system.

Please note that some people need to make some features built into their kernel and vice versa, do whatever works best for you.

===QEMU and Lunar ISO testing===
How do I use qemu to try out lunar ISO's?

'''Answer:'''

Just a quick note on how to use qemu for testing a Lunar Linux installation. See <code>/var/lib/lunar/moonbase/devel/qemu/DETAILS</code> for a description of qemu. Think of it as a low-cost (''read: free'') version of a virtual machine, that has quite a few useful features and is under active development.

A very simple way to just test a Lunar ISO for booting purposes is:

qemu -cdrom lunar-1.5.0-i686.iso -boot d

If you want to test a full install, then create a 512 megabyte sparse root_fs image with this <code>dd</code> command:

dd if=/dev/zero of=hda.img bs=$((1024 * 1024)) count=0 seek=512

Now invoke qemu:

qemu -cdrom lunar-1.5.0-i686.iso -boot d -hda hda.img

You can then proceed to test your Lunar install. Refer the qemu homepage for further tips and tricks. qemu can also be quite easily used to test if your brand new kernel is bootable or not, which is quite neat.

Note that you should say yes to using SDL as an optional_depends. The gui version of qemu is ''very'' nice in its own little X11 window.

==Optimizations==

===How do I set optimizations?===
How do I set these optimizations for my machine?

'''Answer:'''

Run <code>lunar optimize</code>. You'll be taken through an interactive menu that explains all the options. Remember to optimize safely.

===What are safe optimizations?===
What are the recomended safe optimizations for [[Lunar Linux]]?

'''Answer:'''

The default sure fire optimizations that are recommended are:

* '''C'''
** <code>-pipe</code>
* '''C++'''
** <code>-pipe</code>
* '''CPU Architecture'''
** You should pick the correct architecture for your own system (defaults to x86 for most people).
* '''Basic Optimzations'''
** Faster (-O2, the default).
* '''CPU'''
** This, of course, should be set to your own cpu, or the cpu of the machine you plan to run this install on. If you want to be able to run this install on many machines, you should be safe with I686.
* '''Speed Optimizations'''
** If you want to be 100% sure that there won't be optimization problems you shouldn't select any of these.
* '''Extra features'''
** It is not recommended to use any of these optimizations, even for modules known to be able to handle them, since they cause many apps to break.
* '''Floating Point Math'''
** None. If your architecture is x86 and you don't own a 386SX and 486SX, it's safe to select x387.
* '''Linker Options'''
** Strip.
* '''Addon Program Support'''
** CCache. Make sure to install it first.

These settings should work for almost everyone, and there is a lot room for pushing these optimizations more, at the risk of problems with some applications. Read <code>info gcc</code> and make sure you understand a given optimization ''before'' you enable it.

===What optimizations may cause problems?===
What optimizations are known to cause problems in some setups?

'''Answer:'''

Some optimizations that are known to cause problems on x86 with many applications, and even a entire system:

* <code>-funroll-loops</code>
* <code>-fstrict-aliasing</code>
* <code>-ffast-math</code>
* <code>-ffloat-store</code>

These are sorted from the least unstable to most unstable. Read <code>info gcc</code> and make sure you understand a given optimization ''before'' you enable it.

===What optimizations can give some speed without issues?===
What optimizations can I use to gain some speed but without major risks?

'''Answer:'''

Start with the basic optimizations in [[Lunar Linux:FAQ#What_are_safe_optimizations.3F|FAQ #2.2]] and change the Basic Optimizations to Faster or Fastest if you know that gcc will generate correct code for that cpu. -O2 obviously takes more compile time than -O1, and -O3 takes the most time to compile. Then select the cpu you will run it on. Some of the speed optimizations that should be decent and shouldn't cause too many problems, if any, are: -fomit-frame-pointer. A safe bet for floating point math on a x86 would be x387, if you know your cpu has a floating point unit. Check <code>cat /proc/cpuinfo</code> to see if your cpu supports SSE or SSE2. If your cpu does have sse or sse2 then you can also add that to the math optimizations.

Your results may vary. Read <code>info gcc</code> and make sure you understand a given optimization ''before'' you enable it.

===What optimizations should I avoid?===
What optimizations should I stay away from?

'''Answer:'''

All the ones listed in the [[Lunar Linux:FAQ#What_optimizations_may_cause_problems.3F|FAQ #2.3]] plus:
* <code>-fprofile-arcs</code>
* <code>-fbranching-probabilities</code>

Please read <code>info gcc</code> and make sure you understand a given optimization ''before'' you enable it. The Lunar developers will not respond to bug reports of broken compiles by users with risky optimizations.

==Installing modules==

===Can I compile several modules at once?===
Is it possible to install multiple modules at the same time without breaking things?

'''Answer:'''

Yes, Lunar even promotes it. However doing so will cause installs compile slower of course. Lunar will not install core system modules like gcc and glibc while something else is installing and will wait until the rest is finished. Also, you cannot install applications while those major modules are installing, they will wait their turn until it's safe and continue to install them automatically.

===error : download failed - broken URL===
I tried to install a module, but the download failed due to a broken URL. What do I do now?

'''Answer:'''

There are three possible reasons why the download failed:
# You are trying to download from one of a set of mirror sites, and the mirror you are using is either busy or incomplete.
#* Run "lunar" as root, select Options / Software Mirrors, and change the mirror to something closer to you.
#* Note: there seems to be a consistent problem with the SFORGE mirror: http://osdn.dl.sourceforge.net
# You are trying to download from a particular site, but the location of the file has changed [or the site is temporarily off-line].
#* Browse the module's website (see "lvu website") [or search the web for the tarball],
#* Download it manually, copy it to /var/spool/lunar, and try to run "lin" again,
#* Run "lvu edit" to create a [[zlocal]] copy, and edit that copy with the new location [or secondary URL]
# You are trying to download a version that has been removed because a newer version exists.
#* Browse the module's website to discover the new version number,
#* Run "lvu edit" to create a [[zlocal]] copy, and edit that copy with the new location, version number, sha1sum, etc.
#* Note: you could first try to run "lin -w newVersion" and hope that it builds without problems.
If you do create your own [[zlocal]] copy, please consider submitting it using "lvu submit". (See [[Module Submission]])

===error : C compiler cannot create executables===
What does this error mean and how can I fix it?
* <code>C compiler cannot create executables</code>

'''Answer:'''

Read the next topic - this is basically the same problem: There are kernel headers missing that are vital to compilation. You will have to restore them. Below is explained how to do that.

===configure: error: C preprocessor "/lib/cpp" fails sanity check===
What does this error mean and how can I fix it?
* <code>configure: error: C preprocessor "/lib/cpp" fails sanity check</code>

'''Answer:'''

This is an include file problem. Sometimes ''/usr/include/gnu/stubs.h'' is missing, this can be found in the glibc source tarball. Most of the time the following applies:

Your kernel headers are missing from <code>/usr/include</code>. This means the C PreProcessor cannot verify that it has the proper cached copies of those vital header files. You need to install the proper ones manually. Here's how:

lin kernel-headers-2.4

This might work for you! (Use the 2.6 version if needed of course)

Otherwise:

mkdir -p /usr/include/{linux,asm}

to create the two target dirs, if needed. Then execute:

cp -av /usr/src/linux/include/linux /usr/include/
cp -av /usr/src/linux/include/asm/* /usr/include/asm/

to copy the files manually. Be warned that the second command has to be done this way since <code>/usr/src/linux/include/asm</code> is a softlink to your arch asm header files, asm points to asm-i386, on x86 machines. So if, on the other hand, you had copied

cp -av /usr/src/linux/include/asm /usr/include/

you would then get a softlink to nowhere under <code>/usr/include/</code>.

Last, you can always try to unpack the kernel tarball you have into <code>/usr/src/linux</code> and manaully link or copy the headers over yourself.

===Can I add more window managers to gdm?===
How do I add other window managers to the sessions list on gdm?

'''Answer:'''

Copy the desktop startup files to <code>/etc/X11/dm/Sessions/</code>. That works with gdm. For kdm you will have to copy them to <code>$KDE_PREFIX/share/apps/kdm/sessions</code>.

===How do I get Flash to work in Mozilla or Firefox?===
How do I get Flash to work in Mozilla or Firefox?

'''Answer:'''

If you are using Mozilla or Firefox, then you can simply do a <code>lin flash-plugin</code> and that will download and install the Macromedia Flash plugin that works with a gtk+ based mozilla through the old abi wrappers.

The flash plugin does ''not'' work with Galeon. The Galeon developers have declined to provide the "old" abi wrappers needed for the plugin to work.

===How do I install Java?===
How do I get Java for my Lunar box?

'''Answer:'''

You will have to download the Java source code from Sun yourself and you have to "click" to agree on their license. You have to compile it yourself too. We don't have a Sun Java module as we currently have no way to automate the "click" to agree to the Sun Java license. See this URL for some handy info:

http://www.linuxfromscratch.org/~tushar/hints/javafromscratch.txt

There is a j2sdk module in moonbase which is the Blackdown port of Sun's Java Virtual Machine.

==Removing modules==

===How do I remove a module?===
How do I remove a module?

'''Answer:'''

If you have just installed a module for the first time using ''lin'' then it is usually safe to remove it using ''lrm''.

However, if you have built or rebuilt other modules that depend on it, you will need to be careful. Use ''lvu eert'' to identify these modules, and then remove them too, or rebuild them using ''lin -rc'' to change the optional dependency. You should run ''lunar nofix'' to make sure that some hidden dependency has not been affected.

You can also use ''lrm -p'' to purge all modules that depend on it, but this is not recommended in general because it is easy to break your system.

===How do I safely remove an optional module?===
How do I safely remove an optional module, especially one that is now deprecated or obsolete but lots of other modules use it?

'''Answer:'''

There are three ways, ranging from 'time-consuming but safe' to 'possibly quick but dangerous'.

1. You can use the ''lvu eert'' approach described above.

2a. You can use ''lsh'' to access the the lunar internal functions to find the other modules that have a known dependency on theModule and rebuild them. If you ''lrm theModule'' first, the rebuilds and ''lunar fix'' can not silently reuse the module again.

for i in `lsh list_installed_depending theModule` ; do lin -cr "$i" ; done
lunar fixdepends
lunar fix

2b. If you want to rebuild the modules in dependency order, you will need to do a bit more work.

MODULES=""
for i in `lsh list_installed_depending theModule`
do
VAR=$(echo "$MODULES" | grep "$i")
if [ -z "$VAR" ]
then
MODULES="$MODULES $i"
fi
done
lin -cr "$MODULES"
lunar fixdepends
lunar fix

3. Run ''lrm theModule''. Use ''lunar nofix'' to identify problems. Run ''lin -cr'' for each problem. Rinse and repeat.

==Lunar core tools==

===How can I recompile my module with new options?===
How do I force lunar to recompile my modules with different options?

'''Answer:'''

Try:

lin -r ''MODULE''

The -r switch will allow you to select new configuration and dependencies for modules.

===How can I make modules recompile instead of resurrecting?===
How do I tell lunar to recompile my application instead of resurrecting it?

'''Answer:'''

Try doing:

lin -c ''MODULE''

The -c option means tells <code>lin</code> to compile this module even if there is an install cache copy available in <code>/var/cache/lunar</code>.

===How can I tell lunar that module X no longer depends on module Y?===
Module X no longer depends on module Y, but lunar insists on reinstalling module Y too. How can I get tell lunar to remove that dependency?

'''Answer:'''

Lunar adds a module's dependencies to a cache when you install it. You can't remove a dependency automatically, but you can rebuild the dependency cache to reflect the current dependencies of the modules that are now installed.

lsh create_module_index
lsh create_depends_cache
lunar fixdepends

Note: Dependencies of modules in [[zlocal]] are ignored. If module X in the main moonbase depends on module Y then the dependency cache will still contain that dependency.

===My moonbase is gone and I can't install anything.===
How do I fix problems with my moonbase when it's missing or damaged?

'''Answer:'''

Simple solution to this is just running:

lin moonbase

This will download the latest moonbase from the internet, and restore it to working order.

===What is a module?===
What is a [[module]] and what does it do??

'''Answer:'''

A [[module]] is a set of files that tell the core tools the following:

* What name, version, and other properties a package has
* Where to download all needed source files
* What other modules are required, or conflict with this one
* How to unpack the source files, how to patch
* How to configure the code
* How to compile
* How to install everything
* What else to do with it

The [[module]] is coded in a set of files in a directory structure, and scripted in bash.

===What is the Moonbase?===
What is that thing you call [[Moonbase]]?

'''Answer:'''

The [[Moonbase]] is a database with [[modules]]. In this database there are description of packages that tell the core tools where to download, how to compile, and how install a [[module]]. You can consider this the lunar equivalent of portage, grimoire, ports, etc.

===What is theedge?===
What is theedge?

'''Answer:'''

[[theedge]] is the same as lunar, and also known as the core code. Theedge is just another version of lunar. These two pieces of code install your packages, but they do not contain package descriptions. Those are defined in moonbase.

[[Theedge]] is a development version of [[lunar]]. Often there are much more features in theedge, and bugs are fixed quicker as well. However, if you do not like all this tweaking on your system, we advice you to use the stable lunar core tools instead on your system.

You can install [[theedge]] by issuing:

lin theedge

Theedge is automatically updated if you do a <code>lunar renew</code> or <code>lunar update</code>.

==Other==

===How do I unpack an .RPM file in lunar?===
How do I install RPM files in lunar? Is that possible?

'''Answer:'''

The easiest way to unpack a rpm file is to use the module called <code>rpmunpack</code>. Simply run <code>rpmupack ''XYZ''.rpm</code> for your RPM. This will create a cpio file (''XYZ.cpio.gz'' and ''XYZ.cpio.bz2'' are not uncommon). Once you perform any additional uncompression with <code>gunzip</code> or <code>bunzip2</code>, you can then extract it using <code>cpio -i -d < XYZ.cpio</code> -- After all that you should be all done. If you are trying to rpmunpack a source RPM (i.e. .src.rpm) file then ''XYZ.cpio'' may further contain a tar.bz2 or tar.gz source tarball.

In the zbeta section of moonbase, there is an '''''unsupported''''' module called <code>rpm</code> for those of you that are really desperate.

You might want to do <code>man cpio</code>, to check out additional cpio parameters that may interest you, such as the -L switch.

===What is that in the Lunar-Linux logo?===
What is that logo of yours? It looks like a <nowiki>[cat|ferret|dog|owl|insert nutty animal here]</nowiki>!

'''Answer:'''

The logo is a [[wikipedia:Southern Rockhopper Penguin|Rockhopper Penguin]]. It's a kind of nasty penguin, the one that crowd up in thousands to take over the continent. They have a few long feathers sticking out at their "ears" sideway, just like some owl species do.

You can check out [http://images.google.com/images?q=Rockhopper+Penguin Google Images] for lots of Rockhopper Penguin pictures!

The current logo has been designed by Michael Schindler in 2003 and appeared as the official logo of the Lunar Linux project in 2004.

MediaWiki:Sidebar

2012-02-27T16:22:26Z

Striker:

MediaWiki:Sidebar

2012-02-27T16:21:52Z

Striker:

MediaWiki:Sidebar

2012-02-27T16:19:40Z

Striker:

MediaWiki:Sidebar

2012-02-27T16:17:00Z

Striker:

MediaWiki:Common.js

2012-02-26T20:43:05Z

Striker: Adding analytics

/* Any JavaScript here will be loaded for all users on every page load. */

var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-2510780-4']);
_gaq.push(['_trackPageview']);

(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();

MediaWiki:Sidebar

2012-02-26T20:34:22Z

Striker: Some tweaks

Template:Main Page:Languages

2011-02-02T00:35:11Z

Striker: Adding Русский (Russian)

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Languages|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux/Wiki Languages|Wiki Languages]]</h2>

<div style="text-align: center; padding-top: 0.1em; padding-right: 15px;">
'''English''' • [[Lunar Linux/Wiki Languages/Español (Spanish)|Español (Spanish)]] • [[Lunar Linux/Wiki Languages/Français (French)|Français (French)]] • [[Lunar Linux/Wiki Languages/Deutsch (German)|Deutsch (German)]] • [[Lunar Linux/Wiki Languages/Русский (Russian)|Русский (Russian)]] • [[Lunar Linux/Wiki Languages#Request|Request a Language]]
</div>

Lunar Linux:FAQ

2010-09-06T23:45:53Z

Striker: /* What are safe optimizations? */ -O3 is not safe.

These are the '''F'''requently '''A'''sked '''Q'''uestions for Lunar Linux. You have a question about Lunar? You might get your answer below.<br /><br />

__TOC__

==General==

===What is Lunar Linux?===
What exactly is Lunar Linux?

'''Answer:'''
* Please read [[Lunar Linux:About|About Lunar Linux]].

===Can I run Lunar Linux in 64-bit mode?===
Can I run Lunar Linux on my new 64-bit system?

'''Answer:'''

Yes you can. You can run Lunar Linux in '''either''' 64-bit '''or''' 32-bit mode, but there is no multi-lib mode. Be aware that some applications are still only available for 32-bit mode!

===Where can I find how to ...?===
Where can I find how to customize the kernel under Lunar Linux? Or the desktop...

'''Answer:'''

The Lunar Wiki only offers details specific to Lunar Linux. Many other resources already exist for general Linux problem solving. For example, information on how to customize the Linux kernel can be found at:
* http://kernelnewbies.org/
* http://en.wikipedia.org/wiki/Linux_kernel_mailing_list

==Optimizations==

===How do I set optimizations?===
How do I set these optimizations for my machine?

'''Answer:'''

Run <code>lunar optimize</code>. You'll be taken through an interactive menu that explains all the options. Remember to optimize safely.

===What are safe optimizations?===
What are the recomended safe optimizations for [[Lunar Linux]]?

'''Answer:'''

The default sure fire optimizations that are recommended are:

* '''C'''
** <code>-pipe</code>
* '''C++'''
** <code>-pipe</code>
* '''CPU Architecture'''
** You should pick the correct architecture for your own system (defaults to x86 for most people).
* '''Basic Optimzations'''
** Faster (-O2, the default).
* '''CPU'''
** This, of course, should be set to your own cpu, or the cpu of the machine you plan to run this install on. If you want to be able to run this install on many machines, you should be safe with I686.
* '''Speed Optimizations'''
** If you want to be 100% sure that there won't be optimization problems you shouldn't select any of these.
* '''Extra features'''
** It is not recommended to use any of these optimizations, even for modules known to be able to handle them, since they cause many apps to break.
* '''Floating Point Math'''
** None. If your architecture is x86 and you don't own a 386SX and 486SX, it's safe to select x387.
* '''Linker Options'''
** Strip.
* '''Addon Program Support'''
** CCache. Make sure to install it first.

These settings should work for almost everyone, and there is a lot room for pushing these optimizations more, at the risk of problems with some applications. Read <code>info gcc</code> and make sure you understand a given optimization ''before'' you enable it.

===What optimizations may cause problems?===
What optimizations are known to cause problems in some setups?

'''Answer:'''

Some optimizations that are known to cause problems on x86 with many applications, and even a entire system:

* <code>-funroll-loops</code>
* <code>-fstrict-aliasing</code>
* <code>-ffast-math</code>
* <code>-ffloat-store</code>

These are sorted from the least unstable to most unstable. Read <code>info gcc</code> and make sure you understand a given optimization ''before'' you enable it.

===What optimizations can give some speed without issues?===
What optimizations can I use to gain some speed but without major risks?

'''Answer:'''

Start with the basic optimizations in [[Lunar Linux:FAQ#What_are_safe_optimizations.3F|FAQ #2.2]] and change the Basic Optimizations to Faster or Fastest if you know that gcc will generate correct code for that cpu. -O2 obviously takes more compile time than -O1, and -O3 takes the most time to compile. Then select the cpu you will run it on. Some of the speed optimizations that should be decent and shouldn't cause too many problems, if any, are: -fomit-frame-pointer. A safe bet for floating point math on a x86 would be x387, if you know your cpu has a floating point unit. Check <code>cat /proc/cpuinfo</code> to see if your cpu supports SSE or SSE2. If your cpu does have sse or sse2 then you can also add that to the math optimizations.

Your results may vary. Read <code>info gcc</code> and make sure you understand a given optimization ''before'' you enable it.

===What optimizations should I avoid?===
What optimizations should I stay away from?

'''Answer:'''

All the ones listed in the [[Lunar Linux:FAQ#What_optimizations_may_cause_problems.3F|FAQ #2.3]] plus:
* <code>-fprofile-arcs</code>
* <code>-fbranching-probabilities</code>

Please read <code>info gcc</code> and make sure you understand a given optimization ''before'' you enable it. The Lunar developers will not respond to bug reports of broken compiles by users with risky optimizations.

==Installing modules==

===Can I compile several modules at once?===
Is it possible to install multiple modules at the same time without breaking things?

'''Answer:'''

Yes, Lunar even promotes it. However doing so will cause installs compile slower of course. Lunar will not install core system modules like gcc and glibc while something else is installing and will wait until the rest is finished. Also, you cannot install applications while those major modules are installing, they will wait their turn until it's safe and continue to install them automatically.

===error : C compiler cannot create executables===
What does this error mean and how can I fix it?
* <code>C compiler cannot create executables</code>

'''Answer:'''

Read the next topic - this is basically the same problem: There are kernel headers missing that are vital to compilation. You will have to restore them. Below is explained how to do that.

===configure: error: C preprocessor "/lib/cpp" fails sanity check===
What does this error mean and how can I fix it?
* <code>configure: error: C preprocessor "/lib/cpp" fails sanity check</code>

'''Answer:'''

This is an include file problem. Sometimes ''/usr/include/gnu/stubs.h'' is missing, this can be found in the glibc source tarball. Most of the time the following applies:

Your kernel headers are missing from <code>/usr/include</code>. This means the C PreProcessor cannot verify that it has the proper cached copies of those vital header files. You need to install the proper ones manually. Here's how:

lin kernel-headers-2.4

This might work for you! (Use the 2.6 version if needed of course)

Otherwise:

mkdir -p /usr/include/{linux,asm}

to create the two target dirs, if needed. Then execute:

cp -av /usr/src/linux/include/linux /usr/include/
cp -av /usr/src/linux/include/asm/* /usr/include/asm/

to copy the files manually. Be warned that the second command has to be done this way since <code>/usr/src/linux/include/asm</code> is a softlink to your arch asm header files, asm points to asm-i386, on x86 machines. So if, on the other hand, you had copied

cp -av /usr/src/linux/include/asm /usr/include/

you would then get a softlink to nowhere under <code>/usr/include/</code>.

Last, you can always try to unpack the kernel tarball you have into <code>/usr/src/linux</code> and manaully link or copy the headers over yourself.

===Can I add more window managers to gdm?===
How do I add other window managers to the sessions list on gdm?

'''Answer:'''

Copy the desktop startup files to <code>/etc/X11/dm/Sessions/</code>. That works with gdm. For kdm you will have to copy them to <code>$KDE_PREFIX/share/apps/kdm/sessions</code>.

===How do I get Flash to work in Mozilla or Firefox?===
How do I get Flash to work in Mozilla or Firefox?

'''Answer:'''

If you are using Mozilla or Firefox, then you can simply do a <code>lin flash-plugin</code> and that will download and install the Macromedia Flash plugin that works with a gtk+ based mozilla through the old abi wrappers.

The flash plugin does ''not'' work with Galeon. The Galeon developers have declined to provide the "old" abi wrappers needed for the plugin to work.

===How do I install Java?===
How do I get Java for my Lunar box?

'''Answer:'''

You will have to download the Java source code from Sun yourself and you have to "click" to agree on their license. You have to compile it yourself too. We don't have a Sun Java module as we currently have no way to automate the "click" to agree to the Sun Java license. See this URL for some handy info:

http://www.linuxfromscratch.org/~tushar/hints/javafromscratch.txt

There is a j2sdk module in moonbase which is the Blackdown port of Sun's Java Virtual Machine.

==Lunar core tools==

===How can I recompile my module with new options?===
How do I force lunar to recompile my modules with different options?

'''Answer:'''

Try:

lin -r ''MODULE''

The -r switch will allow you to select new configuration and dependencies for modules.

===How can I make modules recompile instead of resurrecting?===
How do I tell lunar to recompile my application instead of resurrecting it?

'''Answer:'''

Try doing:

lin -c ''MODULE''

The -c option means tells <code>lin</code> to compile this module even if there is an install cache copy available in <code>/var/cache/lunar</code>.

===How can I tell lunar that module X no longer depends on module Y?===
Module X no longer depends on module Y, but lunar insists on reinstalling module Y too. How can I get tell lunar to remove that dependency?

'''Answer:'''

Lunar adds a module's dependencies to a cache when you install it. You can't remove a dependency automatically, but you can rebuild the dependency cache to reflect the current dependencies of the modules that are now installed.

lsh create_module_index
lsh create_depends_cache
lunar fixdepends

Note: Dependencies of modules in [[zlocal]] are ignored. If module X in the main moonbase depends on module Y then the dependency cache will still contain that dependency.

===My moonbase is gone and I can't install anything.===
How do I fix problems with my moonbase when it's missing or damaged?

'''Answer:'''

Simple solution to this is just running:

lin moonbase

This will download the latest moonbase from the internet, and restore it to working order.

===What is a module?===
What is a [[module]] and what does it do??

'''Answer:'''

A [[module]] is a set of files that tell the core tools the following:

* What name, version, and other properties a package has
* Where to download all needed source files
* What other modules are required, or conflict with this one
* How to unpack the source files, how to patch
* How to configure the code
* How to compile
* How to install everything
* What else to do with it

The [[module]] is coded in a set of files in a directory structure, and scripted in bash.

===What is the Moonbase?===
What is that thing you call [[Moonbase]]?

'''Answer:'''

The [[Moonbase]] is a database with [[modules]]. In this database there are description of packages that tell the core tools where to download, how to compile, and how install a [[module]]. You can consider this the lunar equivalent of portage, grimoire, ports, etc.

===What is theedge?===
What is theedge?

'''Answer:'''

[[theedge]] is the same as lunar, and also known as the core code. Theedge is just another version of lunar. These two pieces of code install your packages, but they do not contain package descriptions. Those are defined in moonbase.

[[Theedge]] is a development version of [[lunar]]. Often there are much more features in theedge, and bugs are fixed quicker as well. However, if you do not like all this tweaking on your system, we advice you to use the stable lunar core tools instead on your system.

You can install [[theedge]] by issuing:

lin theedge

Theedge is automatically updated if you do a <code>lunar renew</code> or <code>lunar update</code>.

==Lunar-Linux Installation==

===My usb keyboard is not recognized===
At the boot prompt type ''linux uhci-hcd ehci-hcd'' to make sure those modules are loaded during startup. Those will then enable your usb keyboard.

===So how should I partition my disk?===
I'm setting up lunar from scratch, but how should I partition my disk for a server or desktop system?

'''Answer:'''

Server systems have very different demands than desktops. It's all about flexibility. First desktops:

''desktops'' commonly have one hard disk. You don't want to reformat or repartition often, so you just want to be done with it at once. The easiest is just to setup 2 (two) partitions: one root filesystem big enough for all lunar software, and the rest for <code>/home</code>. Typically, lunar occupies between 4 and 12 gb based on how many applications you install. If you clean up often you can manage with 8gb, but you should keep some extra space. I certainly advise to use a swapfile instead of a swap partition: you can always later delete the swap, or move the swapfile to another disk or partition. A swap partition is harder to relocate.

''Servers'' have different needs. First of all <code>/home</code> doesn't need to be that large, but you will want to setup space for logfiles that cannot cause problems if they grow too fast. Putting <code>/var/tmp</code> and <code>/var/log</code> on separate partitions is quite normal. <code>/tmp</code> can be abused similarly, and is mostly run in [[tmpfs]] to avoid cluttering and give fast access times. Then <code>/usr</code> will be separate and the usual separate <code>rootfs</code>. As you can see this list is already getting quite big! Most users will actually want to make the <code>rootfs</code> quite small (as small as 200mb sometimes!) and thus <code>/home</code> also needs to be on a separate partition.

===Kernel features, built-in or module?===
When I compile a kernel, should I compile drivers that I need in the kernel image or as module?

'''Answer:'''

There are many schools of thought on kernel compiling. One is to build everything into the main kernel without modules. The other one takes building modules to the extreme. Here is a suggestion, if it's not needed to boot it's a module. Thus usb, input, sound, mice ACPI, network, and also cdrom, floppy, and all the non boot file systems, all get built as modules. This reduces the size of the main kernel so it can be put on a floppy. Another thing to consider is that not everything works perfectly, and some features can cause your kernel to misbehave, so if some feature is built-in, the bad behavior is practically inevitible. Instead, with a module you can choose not to load it and thus be left with a working system.

Please note that some people need to make some features built into their kernel and vice versa, do whatever works best for you.

===QEMU and Lunar ISO testing===
How do I use qemu to try out lunar ISO's?

'''Answer:'''

Just a quick note on how to use qemu for testing a Lunar Linux installation. See <code>/var/lib/lunar/moonbase/devel/qemu/DETAILS</code> for a description of qemu. Think of it as a low-cost (''read: free'') version of a virtual machine, that has quite a few useful features and is under active development.

A very simple way to just test a Lunar ISO for booting purposes is:

qemu -cdrom lunar-1.5.0-i686.iso -boot d

If you want to test a full install, then create a 512 megabyte sparse root_fs image with this <code>dd</code> command:

dd if=/dev/zero of=hda.img bs=$((1024 * 1024)) count=0 seek=512

Now invoke qemu:

qemu -cdrom lunar-1.5.0-i686.iso -boot d -hda hda.img

You can then proceed to test your Lunar install. Refer the qemu homepage for further tips and tricks. qemu can also be quite easily used to test if your brand new kernel is bootable or not, which is quite neat.

Note that you should say yes to using SDL as an optional_depends. The gui version of qemu is ''very'' nice in its own little X11 window.

==Other==

===How do I unpack an .RPM file in lunar?===
How do I install RPM files in lunar? Is that possible?

'''Answer:'''

The easiest way to unpack a rpm file is to use the module called <code>rpmunpack</code>. Simply run <code>rpmupack ''XYZ''.rpm</code> for your RPM. This will create a cpio file (''XYZ.cpio.gz'' and ''XYZ.cpio.bz2'' are not uncommon). Once you perform any additional uncompression with <code>gunzip</code> or <code>bunzip2</code>, you can then extract it using <code>cpio -i -d < XYZ.cpio</code> -- After all that you should be all done. If you are trying to rpmunpack a source RPM (i.e. .src.rpm) file then ''XYZ.cpio'' may further contain a tar.bz2 or tar.gz source tarball.

In the zbeta section of moonbase, there is an '''''unsupported''''' module called <code>rpm</code> for those of you that are really desperate.

You might want to do <code>man cpio</code>, to check out additional cpio parameters that may interest you, such as the -L switch.

===What is that in the Lunar-Linux logo?===
What is that logo of yours? It looks like a <nowiki>[cat|ferret|dog|owl|insert nutty animal here]</nowiki>!

'''Answer:'''

The logo is a [[wikipedia:Southern Rockhopper Penguin|Rockhopper Penguin]]. It's a kind of nasty penguin, the one that crowd up in thousands to take over the continent. They have a few long feathers sticking out at their "ears" sideway, just like some owl species do.

You can check out [http://images.google.com/images?q=Rockhopper+Penguin Google Images] for lots of Rockhopper Penguin pictures!

The current logo has been designed by Michael Schindler in 2003 and appeared as the official logo of the Lunar Linux project in 2004.

Template:Main Page:About

2008-08-25T22:01:12Z

Striker: Was way out of date...

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:About|}}
</div>

==[[Lunar Linux:About|'''About Lunar Linux''']]==
'''Lunar Linux''' is a [[wikipedia:source code|source]] based [[wikipedia:Linux distribution|Linux distribution]]. It is built entirely by [[wikipedia:compiler|compiling]] [[wikipedia:source code|source code]], using custom [[wikipedia:Optimization (computer_science)|optimizations]].

It installs a complete [[wikipedia:Bootstrap#Computing|bootstrap]] development system first. After telling the Lunar package manager which software will be required, it builds the entire system by downloading current source code and locally compiling an optimized system tailored toward the users specific needs.
This should result in a lean and optimized [[wikipedia:operating system|operating system]]. On the downside, compiling a whole distribution from scratch may be time-consuming and complicate the task of keeping the packages up to date.

Currently, Lunar only supports the [[wikipedia:X86|x86]] and [[wikipedia:X86-64|x86-64]] architectures, but support for [[wikipedia:SPARC|Sparc]], [[wikipedia:PowerPC|PPC]], and [[wikipedia:DEC_Alpha|Alpha]] is being worked on.

Lunar Linux is licensed under the GPLv2.

<div style="text-align: right; font-variant: small-caps; padding-right: 15px;">
[[Lunar Linux:About|More Information]]
</div>

Lunar Linux:Installation/1.5.0

2008-08-01T18:04:12Z

Striker: Rolling back. German information goes in the german version of the wiki page.

__TOC__

Lunar Linux is a revolutionary linux distribution in that it is not binary based, as are most distributions, but is instead built entirely by compiling sourcecode, using your own custom optimizations.

Essentially, it installs a complete bootstrap development system on your machine, and then you tell the Lunar package manager what tools you want, and it builds the entire system by downloading current source code and locally compiling an optimized system tailored toward your specific needs.

The result is a leaner, meaner, refreshingly uncluttered, and strikingly faster operating system than most linux distributions.

This installation guide is designed to get you through the installation process as painlessly as possible. It assumes that you have some experience with linux or another Unix variant, and have a general idea of what you are doing. If you are unfamiliar with such things as partitions, or have never used linux before, Lunar may not be the best introduction for you into the world of open source. There are always Lunar gods available on irc.freenode.net in the #lunar channel to answer any questions that this manual may not make quite clear enough.

With that said, we hope you enjoy using Lunar!

==About this installation manual==

Unfortunately, this manual is very incomplete and inspecific. You will see examples that are not tailored towards your to-be built server or workstation, optimizations that are overly broad or too specific, and examples that don't apply to any real situations. We tried hard to give you the idea of how much power you have over how you can setup your system, but we are forgetting to tell you how to run your own server or desktop (or other system) at all. That means that the examples and steps taken most probably do not apply to your situation at all.

Do not dispair: if you understand what is going on and you get the idea, the installer will allow you to do pretty much everything you want to do with your system. There are really (almost) no limits.

==Getting the ISO==

The primary site for retrieving the ISO is [http://www.lunar-linux.org/ lunar-linux.org]. There, you will find links to our US, EU, and Internet2 mirrors, as well as a Bittorrent link. As of this writing, the current version of the Lunar ISO is version 1.5.0. (''Check the main site for the actual latest version!'')

Locate and retrieve the file lunar-1.5.0-i686.iso.bz2. After downloading this file, you will need to unpack the ISO using bzip2. Windows users will need a program that can extract bzip2 archives, like WinZip (also capable of extracting bzip2 archives under windows are Winrar, powerarchiver and 7-Zip). Mac should unzip the file by itself. Then all that is left to do is use your favorite program to burn the ISO to a cdrom and begin the installation. Lunar can also be installed without using a CD. If you need to do it this way, our [[FAQ]] provides simple instructions.

It should be noted that this ISO and Lunar use devfs for device management. If you prefer the "old-school" method of manually installing devices, there is an ISO available with this option at [http://thing.fwsystems.com/build/lunar/lunar-1.3_stddev.iso.bz2 thing.fwsystems.com].

We are assuming the you are installing Lunar as your primary OS. Make sure you have a backup of any important data that you need to retain. The Lunar Linux Project and its developers are not responsible in any way for any loss of data on your system!

==Booting the ISO==
Upon booting the ISO, the first thing you will see are options for booting the ISO kernel, or for performing RAM tests. There is even a safe mode which will disable DMA, MTRR, RAID, LVM, USB keyboards, NTFS, HPFS, Advanced Partitions, and Firewire. Most folks, however, will be just fine pressing enter at the boot prompt and loading the default kernel.

To boot the iso with support for your usb keyboard:
''linux uhci-hcd ehci-hcd''

After loading the kernel, the first screen presents you with a few options. If there are extra modules you need to load in order continue with the install, they can be loaded here. There is also a shell option. However, if you are using this ISO for rescue purposes, you do not want to shell out here; rather continue booting and shell out in the next section. Most people will select "continue booting" here.

It should be noted that since 1.5.0, the iso tries to autodetect some hardware (mostly scsi drivers and network interfaces) during this stage. This will help you establish a network connection if you desire so during installation. For this reason the prorams 'dhcpcd' and 'ftp' are already available at this stage.

==Virtual Consoles==
Once the ISO has booted into the installer, you can immediately shell out or switch to one of the other virtual consoles. These will have ready to go root shells and are available throughout the installer sequence. With these you can start rescue actions, setup networking or double check the install progress and make manual adjustments.

==Language and keyboard interface Settings==

After reading the introduction, you will be presented with options for choosing the proper font, keymap, and language for your install.
You will also need to choose an editor, as you are going to need one later on in the installation for setting up your lilo or grub configuration. The three choices available are vi, joe, and nano. If you have never used a text editor in linux before, nano is the best choice for you. If you skip the Native Language Support option, the system will install the default editor, nano, for you. When you have finished setting up your options, press cancel to return to the main setup menu.
Less important for most people is the ability to choose the console font, although it may help display some non-english characters. Most people will want to set the system-default language variable and editor though. All these values are unset by default, so make sure you set them now.
The keymap table allows people to use azerty and dvorak keyboards, and much more. This is especially required for non-english keyboards which provide many accented characters.
All these language and keymap settings might not apply to the lunar code itself, which (currently) does not have any international support, but most programs that run during the installer sequence, and after booting into your new system, will be affected properly.
==Creating or editing Partitions==

The next step is to set up partitions on your hard drive. Upon selecting the "Partition Drive" option, you will be shown a list of all the discs the kernel has detected. For this guide, we will assume that you have one hard drive connected via an IDE channel, which will show up in the menu as "disc0". After selecting the disc to partition, you are given the option of using one of three partitioning programs. They are:

* cfdisk -- A menu driven partitioner, and very easy to use. If you are unfamiliar with various partitioning programs, this is the best option for you.
* fdisk -- Text based partitioner that requires a little more know-how than cfdisk. More experienced users will probably use this program. However new users should not be daunted, as it does have help offered at every step.
* parted -- Text based partitioner that is good for advanced users. Parted is excellent for resizing current partitions on your hard disk, however be forewarned that resizing partitions is an excellent way to hose your entire disc.

For our example, we have a 40GB IDE drive and we'll set up six partitions; /, /boot, /home, /usr, /var, and a swap partition. It's a good idea to keep certain directories, such as /var and /usr on separate partitions, as this can save you a lot of headache in the future incase your disk ever completely fails on you and you need to recover data (god forbid!). Also, when you have a separate /boot partition as we have in our example, you need to have your partitioning program mark that partion as active or bootable. In our example, if we were using fdisk, you would press "a" at the command line, and then select part1 as the active partition.

You might also want to install a /tmp partition. By default, Lunar will create a tempfs filesystem mounted on /tmp (tempfs minimizes filesystem fragmentation because it resides in volatile memory). This can be a good choice if you have a lot of memory on your machine. If memory is tight, we recommend creating a /tmp partition to minimize filesystem fragmentation.

It is important to note that you <span class="emphasis">''can not''</span> mount the directories /etc, /bin, /sbin, /dev, /lib and /proc on separate partitions. These directories need to be contained within the root ("/") directory. The installation program should block you from doing this, but it's best not to try.

Here's our partition setup:

1 /boot 100MB
2 / 4GB
3 swap 1GB
5 /usr 10GB
6 /var 10GB
7 /home 15GB

(''If you're wondering about this choice of partitions: it's really just an example. Read the [[FAQ#So_how_should_I_partition_my_disk.3F|FAQ]] on what makes sense in the real world''))

You'll notice that there is no fourth partition in our list above. In order for you to have more than four partitions on a single drive, the fourth partition is made into what is known as an extended or logical partition in which the fifth, sixth, and seventh (etc, etc) partitions reside. For our example above, if we were using fdisk, we would make the fourth partition an extended/logical partition that was 35GB, and then the fifth, sixth, and seventh partitions in our scheme resided within it. However, if we used cfdisk, we would just worry about creating six partitions, making sure that the first three are the primary type, and the last three logical.

Note that the names and mount points for these partitions will be assigned during the next step of this process, when you mount the partitions. Write down exactly what partitions you are planning to create because it can otherwise get confusing!

Lunar offers two choices when it comes to swap. You can set up a swap partition, as we have in our example, or you can set up a swapfile in the root directory. We recommend setting up a swap partition, as you will get better performance with it than with the swapfile. However, there may be a need for you to set up the swapfile instead, which can be setup and activated after you have mounted your other partitions.

==Selecting Partitions and Filesystems==

After creating your partitions, you need to select them and assign file systems. Select the menu option "Select Filesystems" and verify that you are indeed done creating partitions.

The partitions can be selected in random order with the new installer. First select the partition and then assign a filesystem and mountpoint to it. The installer will add this to the job queue and formatting and mounting takes place later so you can edit your selection. Here's a list of filesystems that are currently supported:

* ''ext2'' (Second Extended File System) -- Version 2 of the Extended File System, which was designed for linux as a replacement for the Minix Filesystem. Ext2 is not a journaled filesystem, which means that you'll need to perform disc recovery operations after a power failure or other such system crash. This filesystem is available with all kernels on the ISO.
* ''ext3'' (Third Extended File System) -- Version 3 of the Extended File System, which is essentially just the journaled version of ext2. This filesystem is available with all kernels on the ISO.
* ''reiserfs'' (Reiser Filesystem) -- Journaled filesystem created by Hans Reiser that is excellent for use with extremely small files. This filesystem is available with all kernels on the ISO.
* ''jfs'' (Journaled File System) -- Created by IBM for AIX, IBM's brand of Unix, and later ported to linux by IBM under the GPL. A journaled filesystem that is very good at handling high throughput issues. This filesystem is available with all kernels on the ISO.
* ''xfs'' -- Created by SGI for IRIX, SGI's brand of Unix, and later ported to linux under the GPL. A journaled filesystem that SGI claims is better than any other at handling extremely large files and sparse files. This filesystem is only available with the lunar or grsec patched kernels, which we will come to in a few steps.

After selecting the filesystem type you wish to use, you will be prompted through a series of steps to initialize the partition. You'll notice that the prompts are quite redundant in nature in order to be absolutely positive that you will not inadvertantly erase crucial data that you might have on a working filesystem. In addition, if you have more than four partitions, as we do in our example, you don't want to select any file systems on the fourth partition, as it is the extended partition that houses the fifth, sixth (and so on) partitions. (The installer will try to detect this and skip the extended partition from the list).

As we mentioned earlier, there is an option in the installation process to set up a swap file in the root partition instead of a swap partition as we have done in our example. The next option after selecting your filesystems is to select a swapfile if you so desire. <span class="emphasis">''If you have set up a swap partition already, as we have done, you can skip this step.''</span> Otherwise, you can set up your swap file here, and the only thing you need to tell the installer is how large you want the file to be. Running without swap completely is also possible of course.

'''Please note during this step, no modifications are made to your filesystem!'''

==Installing Lunar==

Next, we need to ''format'' your partitions, ''mount'' them in the right place, create ''swap'' and transfer the entire Lunar system to the partitions that you now have created. This happens all in one single step.

Select ''Install Lunar'', and the system will proceed to transfer all of the neccessary files for you. The installer will display progress as packages are transferred to your system and you'll have some idea how long it will take. On normal machines, this should take about 5 minutes.

At the end of this step, the installer sets various system parameters like language, timezone and vital package configuration files in order for your machine.

==Setting Up Your GCC Architecture Optimizations==

The architecture optimizations is a crucial step, since what you choose will make your system fly! However, it is important that you do not overdo it on you optimization settings, as certain selections can, in some instances, break code while compiling.

The first step is to choose your preferred compiler. The default choice here is GCC 3.x, and is the preferred choice as GCC 2.x is no longer under development, and GCC 3.x is known to make compiled code run faster. For our example, we are going to use GCC 3.x.

Next are options for the C and C++ compiler, called -pipe, that have already been checked off. Very few people, if any, would need to turn off the -pipe option, so in our example we are going to leave them checked.

Next we have the platform selection. This question would seem to be rather silly, since our ISO only boots up on x86 systems, but we like to plan for the future. You'll want to say x86 here.

Now we move onto the Basic Optimization screen. As you can see, the options speak for themselves. Your choice depends on what your needs are. Most folks will want to use -O2 here, as it is the wisest choice. More advanced users may want to use the -O3 option, but it's not for everyone. If you're short on disk space, you would take the -Os Small option. (As an example, we used -Os for the ISO since we were working within a confined amount of disc space.) Those of you with older or slower systems that wouldn't be able to take advantage of faster optimizations may choose a more conservative setting like -O1. For our example system, we will choose -O2.

After choosing your basic optimization level, you'll need to tell the compiler what type of processor you have. This may seem unimportant, however the GCC 3.x compiler has ways of optimizing code for certain processors, even though they all may be x86 based. For example, GCC 3.x has certain optimizations it can perform on code for Pentium 4 machines, but not for Pentium 3. Our example machine is a Pentium 3, so we are going to select that.

We could also select i686, as a Pentium 3 or Pentium Pro falls within that architecture. Choosing i686 is a more conservative choice than Pentium 3, as GCC 3.x will not try certain optimizations with a more general choice like i686.

==Adding Additional GCC Optimizations==

'''You can safely SKIP this entire step!'''

Next up are some extra speed optimizations you can add in to tweak your code even futher. There are too many to go into much detail here, but suffice to say that you should choose carefully. As we mentioned in the prior section, certain optimizations will cause compilation errors or even failures. An optimization such as "-ffast-math" is very risky because it breaks certain rules to get faster code, and would only be used by the bravest of souls looking to endure lots of pain. More information about GCC 3.x optimization strings can be found on the [http://gnu.org/software/gcc/gcc.html gnu.org] website.

The same rule applies on the next screen, where you are asked about some extra features that you may want further optimized, and on the following screen asking about floating point math optimizations. Some options may not pose a problem at all, while others may break things.

Moving on to the next few screens, we have options to enable or disable C and C++ compiler warnings. Most people will want to leave these boxes unchecked as deprecation warnings can be very useful some of the time. Following that is the screen for linker options, where you will find that "-s Strip" has already been checked off. Very few people will want to uncheck this option, so we will leave this screen as is. After that, we have some addons for compiler caching and distributed compiler support. Most folks will not need either one of these.

The final few steps involve setting up the number of concurrent makes and stack parameters. As the hint mentions on the "Concurrent Makes" screen, you'll want to enter in the number of cpu's your machine has. Unless you have a machine with more than one processor, you'll want to leave this field blank. The stack parameters is also fairly straightforward. The warning on that screen says that this field is best left empty, and so that is exactly what we will do with our example.

We are now finished setting up our GCC optimizations! When you have you lunar system up and running, you can always change and tweak these GCC settings by typing "lunar" at the commandline prompt, and going to "Optimization Settings". In addition, if you aren't that familiar with what your processor is capable of using for optimizations, you can go to the shell out option on the ISO and type

cat /proc/cpuinfo

at the prompt and the system will show you all the optimizations that the processor reports it can handle.

==Configuring Your Bootloader==

=== Configuring LILO ===

If you chose to use lilo and also said yes to automatically configuring and running lilo, then most of the work is done for you. If you chose not to hand edit lilo.conf, however, be warned that the default configuration has the system set up to be password protected on boot. You can change this by selecting the option from the menu "Reconfigure LILO".

To turn off password protection, you will need to comment out (with the symbol "#") or delete two lines in your lilo.conf file. The first is "password=lunar", which is found in the top section of the file, and the other is "restricted" which is found right below the name of your kernel in the second section.

The other item of note is whether you want lilo to reside in your MBR (Master Boot Record) or on the first sector of your /boot partition. The line in your lilo.conf file to edit for this purpose is

boot=/dev/hda1

To make lilo get installed on the first sector of your /boot partition, you would leave this line as it is. If you want lilo to be written to your MBR, which is the recommended method, you would change the line to read

boot=/dev/hda

Of course, these examples are pertinent to our setup that we have been using thoughout this manual. Your actual lilo.conf file may be different.

=== Configuring GRUB ===

If you chose grub as your bootloader, you will need to set up the configuration file entirely on your own. An example would be:

default 0
timeout 30
color white/blue white/black
title linux-2.4.20
root (hd0,0)
kernel /vmlinubz-2.4.25-r5.0.0 root=/dev/hda2 devfs=nomount

As we mentioned earlier in the partitioning section, you would want to mark your /boot partition as active. With grub it is ''imperative'' that you mark your /boot partition as active, otherwise grub will not work at all when you are finished with the installation and reboot to your new system.

==Installing kernels==

===Installing a precompiled kernel===

The ISO's come with a variation of precompiled kernels and modules that should work for most people. If you have problems getting your kernel to compile, install or getting the right drivers, or just want to get a quick start at lunar, we ''suggest'' that you use this option instead of compiling your own kernel. You can later of course compile as many kernels as you want.

===Building Your Customized Linux Kernel===

We have now come to the most important part of the installation; the configuration of the kernel. The kernel is the heart of linux, and without it, nothing would work. Configuration is, actually, a rather simple process. All you need to remember is to not panic, and that lunar is going to do most of the work for you. Here are a few pointers that will make the configuration a breeze for you.

* Help is a click away! The people working on creating and maintaining the linux kernel have help placed throughout the entire configuration process. If you're not sure what something does, just look at the help file for whatever item you're on, and it will almost certainly explain what it is and what it does. The most handy thing is that every help file will suggest whether you should really use the item or not. Many help files end with "If you're not sure, it is safe to say N here", thus letting you know that it is safe to leave that particular item out of the kernel.
* You can use the ISO kernel! The configuration used to make the kernel for the ISO is the same configuration you'll see when you start your kernel customization. If you leave the configuration the way it is, the only thing you truly have to worry about is your network and, if you want it, sound. There are also two additional default configurations available on the ISO that are available to you called "config.safe" and "config.server". We'll show you how to load these configurations in just a little bit.
* Never build filesystems or core components as modules! Make sure that whatever filesystems you decided to use for your partitions earlier are built into the kernel, and are not separate modules. Likewise, make sure that certain crucial things like ide and scsi drivers are not modules, as this will make your machine unbootable. (This rule doesn't apply to the scsi low level drivers though; they can be modules.) Modules are kernel drivers that can be manually activated and deactivated after the system has been booted, but not during boot time. The kernel from the ISO already has all the filesystems available during the installation built into the kernel, so if you don't change anything there, you will be fine.

You will be shown two screens of information before you actually begin you kernel configuration, letting you know that you are going to need a few things built into the kernel in order to have Lunar run properly, and what options you have for boot loaders. Lunar comes with both lilo (LInux LOader) and grub (GRand Unified Bootloader).

If you don't have much experience with bootloaders, we suggest using lilo for now, as the installation program will set up the configuration file for you. If you would prefer to use grub, and we encourage folks to learn how to use it, be forewarned that the installation program does not set up any configuration at all for you.

There are serveral kernels for you to choose from. They are:

* ''linux-2.4'' -- The default kernel for Lunar which is the Linus tree with some handy patches for the xfs filesystem, firewire, ext3, and several other fixes.
* ''linux-2.4-agr'' -- The aggressive patch includes everything from the standard patchset as well as the low latency, pre-emptive, and gcc 3.x architecture type patches.
* ''linux-2.4-grsec'' -- This is almost the same as linux, but with grsecurity, cpu frequency scaling, gcc 3.x architecture types, and crypto support.
* ''linux-2.4-stable'' -- This is the Linus tree with only critical patches for certain drivers that were created after the 2.4.20 kernel was released.
* ''linux-2.4-vanilla'' -- A completely unpatched kernel tree.
* ''linux-2.4-om'' -- A kernel specifically meant for clustering use.

For our example, we are going to use linux-2.4-agr.

Before you begin is which type of configuration method you would like to use.

* ''config'' -- The original way to configure the linux kernel. It is completely text based, and assumes you know what everything is. Unless you've been using linux since its inception, you probably don't want to use this method.
* ''menuconfig'' -- As the name implies, a menu driven version of the kernel configuration. This is the easiest, and by far the most popular way of configurating your kernel.
* ''xconfig'' -- If you have an X server running, you can use this option to configure your kernel using a nifty GUI interface. You won't be able to use this on the ISO, but once your system is up and running with X, you can use this option. If you do choose this option while installing from the ISO, the system will fall back to next available configuration method, in this case menuconfig, so there is no harm in selecting it if you do.

For our example, we are going to use menuconfig. Once Lunar is finished applying the patches for the kernel, which can take a minute or two, you'll be brought to the configuration screen for the linux kernel.

As we mentioned earlier, the configuration that was used to build the kernel for the ISO is the same configuration that you'll be presented with when you start. However, as we also mentioned earlier, there are two alternate kernel configurations available to you that you may want to use; config.safe and config.server. Both of there configurations can be found on the ISO, along with the original default config file, in /etc/lunar/local. When you are looking at the kernel menuconfig main page, scroll all the way to bottom, and you will find an option called "Load an Alternate Configuration File". Select this and then give the absolute path to the alternate configuration file, i.e. /etc/lunar/local/.config.server. As with all kernel configuration files, they are hidden files preceeded with a ".", so make sure to not forget it.

Once you have completed configuring your kernel, you'll get one more prompt from the installer asking if you want to go back to the configuration in case you exited by mistake or forgot something. If everything is good to go, say no here and sit back for a few minutes while your kernel compiles.

==Setting Up Networking==

The final step is to set up networking. When you select the "Set Up Networking" option, you'll be prompted by a series of questions as to what kind of card you have (only needed if you built your networking device as a module, and not part of the kernel), if you need to set up wireless or not, and whether you'll need to use dhcp or not. You should be familiar enough with your network to set this up on your own, as the questions put to you are very straightforward.

==Other settings==

The installer will prompt you now for some more settings. You should set a root password and generate ssh host keys to identify your box uniquely for later. You might also want to administrate services on the newly installed machine.

==Reboot!==

Once you have completed setting up your networking, you are finished installing Lunar Linux! Congratulations! Select the option "Done" and remove the cd from the drive when it ejects. Your Lunar system is now ready to go!

''Have Phun!!''

[http://www.gnu.org/copyleft/ Copyleft] 2004 [http://lunar-linux.org/ The Lunar Penguin Team]

Lunar Installation Manual and Harassment of Lunar Developers by Drew Swayze (drew AT lunar-linux DOT org).

Edits and Nitpicking by Suzanne Burns (sburns AT lunar-linux DOT org).

Lunar Linux

2008-07-19T18:45:13Z

Striker: I don't know.

__NOTOC__
__NOEDITSECTION__

<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td colspan="2" style="padding: 3px; background: #ffe; border: 1px solid #ff0; vertical-align: top;">
{{Main Page:Languages}}
</td>
</tr><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
{{Main Page:Documentation}}
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
{{Main Page:Misc}}
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">
{{Main Page:About}}
</td>
</tr></table>

Lunar Linux/Wiki Languages/Deutsch (German)

2008-03-22T22:02:16Z

Striker: __NOTOC__

__NOTOC__
__NOEDITSECTION__
<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td colspan="2" style="padding: 3px; background: #ffe; border: 1px solid #ff0; vertical-align: top;">
{{Main Page:Languages de}}
</td>
</tr><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
{{Main Page:Documentation de}}
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
{{Main Page:Misc de}}
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">
{{Main Page:About de}}
</td>
</tr></table>

Lunar Linux/Wiki Languages/Français (French)

2008-03-22T22:02:00Z

Striker: __NOTOC__

__NOTOC__
__NOEDITSECTION__
<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td colspan="2" style="padding: 3px; background: #ffe; border: 1px solid #ff0; vertical-align: top;">
{{Main Page:Languages_fr}}
</td>
</tr><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
{{Main Page:Documentation_fr}}
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
{{Main Page:Misc_fr}}
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">
{{Main Page:About_fr}}
</td>
</tr></table>

Lunar Linux/Wiki Languages/Español (Spanish)

2008-03-22T22:01:50Z

Striker: __NOTOC__

__NOTOC__
__NOEDITSECTION__
<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td colspan="2" style="padding: 3px; background: #ffe; border: 1px solid #ff0; vertical-align: top;">
{{Main Page:Languages_es}}
</td>
</tr><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
{{Main Page:Documentation_es}}
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
{{Main Page:Misc_es}}
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">
{{Main Page:About_es}}
</td>
</tr></table>

Lunar Linux

2008-03-22T22:01:30Z

Striker: __NOTOC__

__NOTOC__
__NOEDITSECTION__
<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td colspan="2" style="padding: 3px; background: #ffe; border: 1px solid #ff0; vertical-align: top;">
{{Main Page:Languages}}
</td>
</tr><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
{{Main Page:Documentation}}
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
{{Main Page:Misc}}
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">
{{Main Page:About}}
</td>
</tr></table>

Template:Main Page:Languages fr

2008-03-22T18:00:17Z

Striker: Touchup to remove excess whitespace

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Languages_fr|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux/Wiki Languages|Langues du Wiki]]</h2>

<div style="text-align: center; padding-top: 0.1em; padding-right: 15px;">
[[Lunar Linux |English]] • '''Français (French)''' • [[Lunar Linux/Wiki Languages/Deutsch (German)|Deutsch (German)]] • [[Lunar Linux/Wiki Languages#Request|Ajouter une Langue]]<br>
<small>([[Lunar Linux/Wiki Contribue_FR|Contribuer]] • [[Lunar Linux/Wiki Syntaxe_FR|Syntaxe du WIKI]])</small>
</div>

Template:Main Page:Languages

2008-03-22T17:50:58Z

Striker: Adding Español (Spanish)

Español (Spanish)

2008-03-22T17:49:03Z

Striker: Español (Spanish) moved to Lunar Linux/Wiki Languages/Español (Spanish)

#REDIRECT [[Lunar Linux/Wiki Languages/Español (Spanish)]]

User talk:217.28.206.143

2008-03-07T07:04:03Z

Striker: Nothing

User:217.28.206.143

2008-03-07T07:03:27Z

Striker: Nothing.

Module Writing

2007-07-17T04:55:47Z

Striker: /* Before you start */ All modules are accepted now, as long as LICENSE= is set correctly.

__TOC__

Writing lunar [[modules]] can be extremely complex or very simple, and is analogous to performing the steps needed to install a [[package]] manually. However, there are so many variables you need to think of when writing modules, that it's hard to get them all right if you're new at writing modules.

==Before you start==
Take some time to think about ''why'' you want to make a new module. Also, there might be things to consider that would prevent you from writing a module at all. Here's some quick guidelines...

* Check if the package is already in the Lunar [[moonbase]]. Nothing is worse then doing the same work twice.
* Check the dependencies required for the module, and see if those also meet these requirements. Sometimes a module might take so much time to write that it's not worth it.
* Check if you're not better off installing it manually or using a binary. Plenty of packages are so easy to install into your home directory and even though a module would be nice, it's often just easier to install it manually.

==Starting the module==

Find a good spot in [[moonbase]]. You should always work in the [[zlocal]] section. Your system [[moonbase]] is located in "/var/lib/lunar/moonbase".

cd /var/lib/lunar/moonbase/zlocal
mkdir mymodule
cd mymodule

Every module is defined as the group of files and directories including a [[DETAILS]] file in a directory. So we need a [[DETAILS]] file:

MODULE=mymodule
VERSION=1.0
SOURCE=$MODULE-$VERSION.tar.bz2
SOURCE_URL=http://my.site.org/files/
SOURCE_VFY=sha1:e96df66f703c5ab1a295e216b5035ee14d6202b2
WEB_SITE=http://my.site.org/
ENTERED=20050808
UPDATED=20050808
SHORT="Makes module writing easy"

cat<<EOF
MyModule is a simple tool to explain module writing in
detail. It doesn't actually exist but is used as an example
for educational purposes.
EOF

This is a basic [[DETAILS]] file with all required components. As you can see it's just plain shell code.

''All lunar module files are bash code. This means that you should pay special attention to shell meta characters and proper syntax''

This [[DETAILS]] file already can be all you need for writing a module, depending on the way "mymodule" needs to be compiled.

== Module Format ==

See [[Module Basics]] and [[Module Guidelines]] for detailled information about available module scripts and module examples.

User:Engelsman

2007-06-14T03:01:19Z

Striker:

How did I come to be a Lunar Linux User? Easy. I shared an office with [[User:Sofar|Sofar]] for 18 months and was exposed to his enthusiasm for Lunar Linux.

Plus the fact that I've reached the age where playing squash four times a week wreaks havoc with the knees, so I decided to install Lunar at home and work on some programming projects instead.

And the nickname? That's easy as well. To paraphrase Sting, I'm an Englishman living in the Netherlands.

User:Engelsman

2007-06-10T23:05:23Z

Striker: Reverted edit of DsqGn1, changed back to last version by Engelsman

Package Management

2007-06-10T23:03:34Z

Striker: Reverted edit of EahG1s, changed back to last version by Sofar

===Package Management===

[[Package Management]] is the general name used to describe the art of installing, removing and updating software packages. Often this is the key component of the [[wikipedia:operating system|Operating System]].

[[Lunar Linux]]'s packagement system is unique in the way that all the applications are compiled directly from source-code.

Both the [[lunar]] and [[theedge]] package provide this feature for [[Lunar Linux]]. These two are mutually exclusive and contain the same tools. [[Lunar]] is the ''stable'' version and [[theedge]] the ''development'' branch.

Other Package Management systems known are [[wikipedia:rpm|RPM]], [[wikipedia:portage|portage]].

Lunar Linux/Wiki Languages/Deutsch (German)

2006-09-06T21:48:17Z

Striker: the actual front page :)

__NOEDITSECTION__
<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td colspan="2" style="padding: 3px; background: #ffe; border: 1px solid #ff0; vertical-align: top;">
{{Main Page:Languages de}}
</td>
</tr><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
{{Main Page:Documentation de}}
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
{{Main Page:Misc de}}
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">
{{Main Page:About de}}
</td>
</tr></table>

Template:Main Page:Misc de

2006-09-06T21:47:31Z

Striker: seeing if this is working correctly...it should i guess...

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main Page:Misc de|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux:DE_Misc|Andere Informationen]]</h2>

<h4>Howto Artikel</h4>
* [[Installation:Ohne CD|Ohne CD installieren]]
* [[Installation:Ohne Netzwerk|Ohne Netzwerk/Internet installieren]]
* [[Installation:Kernelbefehlszeilendevminihowto|Das Kernelbefehlszeilen /dev Mini-HowTo]]
* [[Installation:DE_SoftwareRaid|Installation auf einem Software RAID]]
* [[Miscellaneous:DE_USB kamera howto|USB Kamera HowTo]]
* '''''[[Howto Artikel|mehr...]]'''''

<h4>Reviews</h4>
* [http://goran.krampe.se/articles/lunar.html Review von Lunar Linux] • von Göran Krampe
* [http://distrocenter.linux.com/distrocenter/05/07/25/1319212.shtml?tid=127 Lunar Linux Review] • von Preston St Pierre on [http://linux.com/ Linux.com]

<h4>Fakten über Lunar</h4>
* [[Nutzer Berichte|Nutzer Berichte]] über Ihren Erfolg mit Lunar
* [[Wie Lange|Wie lange dauert es]] um etwas in Lunar zu installieren?

<h4>Andere Internetseiten</h4>
* [http://lunar-linux.interhact.net/ Lunar Linux Non-Free Module]

<div style="text-align: right; font-variant: small-caps; padding-right: 15px;">
[[Lunar Linux:DE_Misc|Weitere Informationen]]
</div>

Template:Main Page:Languages

2006-09-06T20:59:16Z

Striker: alphabetize

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Languages|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux/Wiki Languages|Wiki Languages]]</h2>

<div style="text-align: center; padding-top: 0.1em; padding-right: 15px;">
'''English''' • [[Lunar Linux/Wiki Languages/Français (French)|Français (French)]] • [[Lunar Linux/Wiki Languages/Deutsch (German)|Deutsch (German)]] • [[Lunar Linux/Wiki Languages#Request|Request a Language]]
</div>

Template:Main Page:Languages fr

2006-09-06T20:58:27Z

Striker: /* Langues du WIKI: */ swing and miss the preview button!

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Languages_fr|}}
</div>

==Le WIKI:==
*[[Lunar Linux/Wiki Contribue_FR|Contribuer]]
*[[Lunar Linux/Wiki Syntaxe_FR|Syntaxe du WIKI]]

==Langues du WIKI:==

<div style="text-align: center; padding-top: 0.1em; padding-right: 15px;">
[[Lunar Linux |English]] • '''Français (French)''' • [[Lunar Linux/Wiki Languages/Deutsch (German)|Deutsch (German)]] • [[Lunar Linux/Wiki Languages#Request|Ajouter une Langue]]
</div>

Template:Main Page:Languages fr

2006-09-06T20:57:49Z

Striker: adding link for german translation

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Languages_fr|}}
</div>

==Le WIKI:==
*[[Lunar Linux/Wiki Contribue_FR|Contribuer]]
*[[Lunar Linux/Wiki Syntaxe_FR|Syntaxe du WIKI]]

==Langues du WIKI:==

<div style="text-align: center; padding-top: 0.1em; padding-right: 15px;">
[[Lunar Linux |English]] • '''Français (French)''' • [[Lunar Linux/Wiki Languages#Request|Ajouter une Langue]] • [[Lunar Linux/Wiki Languages/Deutsch (German)|Deutsch (German)]]
</div>

Template:Main Page:Languages

2006-09-06T20:53:41Z

Striker: adding link for german translation

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Languages|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux/Wiki Languages|Wiki Languages]]</h2>

<div style="text-align: center; padding-top: 0.1em; padding-right: 15px;">
[[Lunar Linux/Wiki Languages/Deutsch (German)|Deutsch (German)]] • '''English''' • [[Lunar Linux/Wiki Languages/Français (French)|Français (French)]] • [[Lunar Linux/Wiki Languages#Request|Request a Language]]
</div>

Installation:Kernel 2.6. HowTo

2006-07-26T17:09:52Z

Striker: This article is now deprecated.

=Deprecated notice=
Since the officialy release of Lunar 1.6.0, this article has now become deprecated, however it may still prove useful for those still running 2.4 systems that may wish to upgrade without a complete reinstall. YMMV - [[User:Striker|Striker]] 17:09, 26 Jul 2006 (UTC)

=What's this 2.6 kernel hoo-hah about anyway?=

The Linux kernel version 2.6 is the current stable Linux kernel. Although Lunar Linux is a bleeding edge distribution, we do not think that a jump to a full 2.6 install is a good idea for production servers yet. A desktop can run comfortably on 2.6, but if you are a newbie, we strongly recommmend you starting off with 2.4. If you still think about going ahead, having a bootable fall back 2.4 kernel is useful, specially when you configure a 2.6 kernel for the first time.

Having said that, and keeping it in mind, we will describe how to install a 2.6 kernel, using our lunar kernel module called linux-2.6 (that only holds stable kernel.org releases). Although we are going to use linux-2.6 here, this howto can be applied for any other of our linux-2.6 set (currently linux-2.6-ck, linux-2.6-grsec, linux-2.6-inotify, linux-2.6-mm and linux-2.6-prepatch).

=Who wrote all this fine software?=

The main 2.5 and the later 2.6 trees have been maintained by Linus Torvalds. This responsability is now in hands of Andrew Morton, who for testing purposes keeps his own set of patches against the 2.6 tree. The patches' names are suffixed with -mm. A Lunar module with the mm patch is available, though not recommended for first 2.6 installs. If you have a problem with the current served kernel in linux-2.6, linux-2.6-mm maybe a temporary solution. Once tested, the features that are doing fine in mm patches are merged into the main 2.6 tree, so if linux-2.6-mm works now, it is very likely linux-2.6 will as well very soon.

=Why would I want to switch away from my 2.4 kernel?=

The first time I tried a (then) 2.5 kernel, I did so because of curiosity. I wanted to feel directly how this new thing ran. I've hardly ever stopped using it since then. If you have an X server running on your 2.6 kernel, the first thing that you'll notice is your mouse speed skyrocket. The responsiveness of the X apps has taken a huge step forward. This is only one of the many new features you will find in the 2.6 series.

Apparently, there has been a focus on server side, though the average user should be pleased, as exampled above with X. PDA and embedded linux users should be happy, too.

From server side, the leap from the 2.4 to the 2.6 kernel is more than a simple version change:
* 64 bit support.
* NUMA ( Non-Uniform Memory Access ): For clusters with a high amount of nodes, memory sharing is vital. NUMA adresses this problem.
* The addressing space for unique users is no more 16 bit but 32 bit. so the user support has grown to 4 billion from 65,000.
* Higher limits: PIDs (process IDs) have grown from 32,000 to 1 billion, RAM's max is now 64 GB instead of 4 GB, and filesystem's top is set at 16 Terabytes, instead of 4.

Desktop/laptop have had their share of new features as well:
* ALSA (Advanced Linux Sound Architecture) has been merged in the kernel tree and it has better joystick support.
* Broader wireless and native Bluetooth support.
* Software suspend-to-disk and speed scaling for laptops.

Embedded systems have also been taken care of:
* uCLinux support.
* Support for more types of MMU-less processors, like PDAs, for example.
* Embedded Profile support.

At least the first 2 (servers and desktops/laptops) will benefit from some other upgrades:
* New scheduler: optimization of system resources, no matter if you have 1 CPU or you have many.
* Better I/O scheduler, faster read/writes.

Those most probably are not all, but I suppose you can get a slight idea on how things have changed. Remember that 2.6 kernel is fairly young.

=Where would I want to install it?=

Starting from the features listed above, the 2.6 kernel would be suited from any machine like a big cluster, SMP machine, down to a desktop or something as small as a handheld. But I have my own case to show you that 2.6 kernels work. I have 2 desktops and a server, all 3 with 2.6 kernels and fully 2.6 installs, and I must say I have no complaint. Don't think I'm alone here, since I have friends that I have helped install 2.6 kernels (no big deal, as you will see), or they have done so by themselves on their desktops, laptops or servers. They didn't worry about if their hardware was the oldest or brand new, they jumped anyway. The news I have is that they are quite happy. Sum up Lunar users and fellow Lunar devs, and I know a good lot running 2.6 kernels. And you are hopefully next :)

=Okay. I'm convinced. How do I install this thing?=

Before you do anything else, I'd recommend you take your time to do the switch, because changing from a 2.4 tree to a 2.6 tree kernel is not so simple as compiling a 2.6 kernel with your 2.4 .config. Please don't rush!

==Installing the Kernel==

The first stage of a jump to a 2.6 kernel install would be to install the latest available in moonbase; the second stage would be setting all your Lunar install to be 2.6 based, recompiling each Lunar module against 2.6 headers, but you need not worry about that, if you don't want to -it is not necessary, though it will be explained. By the way, you can still run a 2.6 kernel in a 2.4 header environment, if you just want to give it a small test.

To install the last 2.6 kernel from moonbase all you have to do is to install the linux-2.6 Lunar module. You will start the compile from a default .config the kernel tarball brings, since the difference between 2.6's config and 2.4's is too big to import your current 2.4 kernel configuration -in some cases it has even been problematic. I again here strongly recommend walking through the whole kernel's configuration. This is important because the configuration's hierarchy tree has changed a lot: things have been moved, others taken out, and new features have been fitted in (that you might want to know).

Now let's get to the nitty gritty of it, and do the install itself. As root:

root@myshinybox ~ # lin linux-2.6

will fetch the sources and prepare the build. As a dependency, the module-init-tools Lunar module will be installed, because it is needed for kernel module management (as the modutils Lunar module is needed for 2.4 kernels).

Now you will be asked a few questions, first of all about your bootloader:

linux-2.6: Configure this kernel to load from grub? [n]

If you answer 'y', an entry will be added to grub's menu.lst file, and you will be prompted with another question after:

linux-2.6: Configure grub? [n]

If you say no, grub will be handled automagically. If you say yes, you will have to configure grub yourself after the kernel build. If, on the other hand, you said no to the "Configure this kernel to load from grub" question, you should see, analogously to grub:

linux-2.6: Configure this kernel to load from lilo? [n]

Answer yes ('y'), if you wish to use lilo as your prime bootloader.

If you answered yes to the lilo question, you should be prompted just like grub:

linux-2.6: Configure lilo? [n]

Once again, if you say 'y' (yes) you will have to hand configure lilo.conf after the kernel build has finished. If you said no, lin will take care for you. For now, a safe answer is say no to bootloader configuration, so Lunar takes care of your grub or lilo.

Next step to cope with is what interface we are going to use to configure the kernel:

linux-2.6: Do you prefer xconfig over menuconfig? [n]

If you want to use xconfig, answer 'y'. If you prefer any other answer 'n'. If you answer 'n', you will have one more question on this topic:

linux-2.6: Do you prefer menuconfig over config? [y]

Unless you really know what you are doing, say 'y' to use a ncurses interface (make menuconfig) and not use a questionaire method (make config). Any other answer than 'y' will lead you to make config.

Finally, you will see one last question:

linux-2.6: Configure linux kernel? [n]

As it is your first encounter with linux-2.6, please answer 'y', so you walk the whole kernel config (remember, it is important to walk to whole lot!).

Now that questions have been dealt with, the source will be downloaded. Once the download finished, the source has been unpacked, and the build began, your interface of choice to the kernel's configuration will be shown. Choose what you need for your box.

After kernel configuration, you will be prompted one more time:

Repeat config? [n]

If you think you missed something and you want to go back to kernel configuration, you are still in time; yet, if you are happy already, just say 'n', and watch your kernel build. You will prompted with this question every time you finish your config method.

When the kernel has succesfully built, two things may happen, depending on what you answered previously: if you have answered yes to configure your bootloader, you will see your bootloader's config file opened in an editor for you. A new kernel entry, for your new kernel will be there, so you can do some tweaking if you like. If you decided to let lin take care (answered 'n' to configure your bootloader), this will be done without your interaction.

Yay, done with the kernel! ;)

==udev and sysfs==

udev is a new feature in 2.6. It brings dynamic userspace dev nodes, the equivalent in userspace of what devfs did in kernel for 2.4. Udev is based on another new feature: sysfs. Sysfs is a virtual filesystem, that lists system information in a hierarchical way (like a boosted proc, so you can get the idea). Both udev and sysfs, unlike other features in 2.6 that have been backported, are not seen in 2.4 kernels.

There is no fixed reason why you should install udev, though it will simplify a lot your work, so we do recommend doing so. A good reason is that if you are used to using dynamic dev nodes, sooner or later devfs will be deprecated (it is already marked as such in the kernel) and will be droped out. Another solution is having a static /dev with permanent nodes, that you can hand create each time you need a new node, or create the whole lot of device nodes using the makedev Lunar module.

udev uses hotplug to create the nodes under /dev, so it is completely independant from the running kernel. It uses namedev to set device naming policies, and libsysfs to query sysfs.

To install udev, as root:

root@myshinybox ~ # lin udev

will install udev, and sysfsutils and hotplug as dependencies. One thing you have to know about udev is that its use excludes the use of devfs. You can still have devfs support as a module but you must not enable "automatically mount devfs at boot" (see the kernel's Filesystems section, subsection pseudo filesystems). Furthermore, the kernel has to be hotplug aware, so this option should be included when compiling a kernel for udev (see General Setup -> Support for hot-pluggable devices).

Yay, done with udev!

IMPORTANT NOTE: At this point, whatever you choose as your /dev, please really read [[Installation:The_kernel_commandline_/dev_params_mini-HowTo|The kernel commandline /dev params mini-HowTo]]

==Rebuilding software against 2.6 headers==

The possible second stage of a 2.6 migration would be rebuilding our software against 2.6 headers.

Before explaining how to accomplish the 2.6 header based Lunar box, I will make one last warning: The Lunar Linux team does not officially support 2.6 installs. This is very important, because we currently do not do 2.6 specific fixes, if these collide with 2.4 only Lunar module setups (there are exceptions). If you come around any problem, please report it, as it will be taken in consideration, that is for sure. Example of this willingness to help is this howto.

The process of switching is quite simple, really. There is a Lunar module that serves a series of sanitized kernel headers, kernel-headers-2.6, but everytime glibc is recompiled it creates a tarball from the headers under /usr/src/linux. So if the last kernel you installed was linux-2.6, you'll have a 2.6 headers tarball created from it and installed, if you recompiled glibc after installing your kernel. This is not true if you installed kernel-headers-2.6's Lunar module; glibc would still create the headers, but not install them. This is an exception to the Lunar's 2.6 non-support module scheme.

For the sake of standarization, we recommend the install of kernel-headers-2.6. Bug tracking for you and for us will be simplified if we use the same set of headers. If each of us have our own headers with different versions, it would be harder to know if it is an app problem or a header problem. So, if you decide to take this step, and move to a fully 2.6 environment, please install kernel-headers-2.6. We all move forward together.

Taking for granted you do want to install kernel-headers-2.6, as root type:

root@myshinybox ~ # lin kernel-headers-2.6

Second step here is to rebuild your software against your new headers. This should be done in a certain order. As a base 2.6 install, from which later rebuild the rest of your apps, you should lin:
* kernel-headers-2.6
* gcc
* glibc
* installwatch
* binutils
* coreutils
* bzip2
* gzip
* tar
* diffutils
* findutils
* make
* grep
* gawk
* sed
* gettext
* ncurses
* patch
* texinfo
* bash
* util-linux
* perl

Having done this, you will have a good base towards having a fully 2.6 install. From now on, you can rebuild in whatever order you want the rest of your installed Lunar modules so they as well are 2.6 based.

Yay, done with headers!

=Credits=

"Linux 2.6.0: What's New" from osdl.org

Special thanks to : Aaron Watry, Alex Hunsaker, and Auke Kok

Original article text by Jaime Buffery (nestu AT lunar-linux DOT org)

Old docbook conversion and other nifty tweaks by Drew Swayze (drew AT lunar-linux DOT org)

Copyleft 2004-2005 The Lunar-Linux Team

Howto Articles

2006-07-26T17:06:33Z

Striker: Okay, how about being a little less retarded

==Additional howto articles==
* [[Install_XOrg7]] • XOrg 7 Installation guide
* [[Install_XGL]] • XGL Guide

Template:Main Page:Misc

2006-05-24T14:49:41Z

Striker: /*more...*/

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Misc|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux:Misc|Other Information]]</h2>

<h4>Howto Articles</h4>
* [[Installation:No CD|No CD installation]]
* [[Installation:No network|No network installation]]
* [[Installation:The_kernel_commandline_/dev_params_mini-HowTo|The kernel commandline /dev params mini-HowTo]]
* [[Installation:Software Raid|Installation on software RAID]]
* [[Miscellaneous:USB camera howto|USB camera howto]]
* '''''[[Howto Articles|more...]]'''''

<h4>Reviews</h4>
* [http://goran.krampe.se/articles/lunar.html Review of Lunar Linux] • by Göran Krampe
* [http://distrocenter.linux.com/distrocenter/05/07/25/1319212.shtml?tid=127 Lunar Linux Review] • by Preston St Pierre on [http://linux.com/ Linux.com]

<h4>Facts about Lunar</h4>
* [[User Reports|User reports]] about their success with Lunar Linux
* [[how_long|How long does it take]] to install something on lunar?

<h4>3rd Party Websites</h4>
* [http://lunar-linux.interhact.net/ Lunar Linux Non-Free Modules]

<div style="text-align: right; font-variant: small-caps; padding-right: 15px;">
[[Lunar Linux:Misc|More Information]]
</div>

Template:Main Page:Misc

2006-04-26T18:41:55Z

Striker: fix link to review

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Misc|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux:Misc|Other Information]]</h2>

<h4>[[Howto Articles]]</h4>
* [[Installation:No CD|No CD installation]]
* [[Installation:No network|No network installation]]
* [[Installation:Kernel_2.6._HowTo|Installing a 2.6 kernel]]
* [[Installation:The_kernel_commandline_/dev_params_mini-HowTo|The kernel commandline /dev params mini-HowTo]]
* [[Installation:Software Raid|Installation on software RAID]]
* [[Miscellaneous:USB camera howto|USB camera howto]]
* [[Howto Articles|more...]]

<h4>Reviews</h4>
* [http://goran.krampe.se/articles/lunar.html Review of Lunar Linux] • by Göran Krampe
* [http://distrocenter.linux.com/distrocenter/05/07/25/1319212.shtml?tid=127 Lunar Linux Review] • by Preston St Pierre on [http://linux.com/ Linux.com]

<h4>Fun Facts about Lunar</h4>
* [[how_long|How long does it take]] to install something on lunar?

<h4>3rd Party Websites</h4>
* [http://lunar-linux.interhact.net/ Lunar Linux Non-Free Modules]

<div style="text-align: right; font-variant: small-caps; padding-right: 15px;">
[[Lunar Linux:Misc|More Information]]
</div>

Help:Editing

2006-03-27T14:05:51Z

Striker: Reverted edit of 67.171.243.40, changed back to last version by V3rt1g0

==General==
To edit a page, click on the "'''Edit this page'''" (or just "'''edit'''") link at one of its edges. This will bring you to a page with a text box containing the ''[[wikitext]]'': the editable source code from which the server produces the webpage.

After adding to or changing the wikitext it is useful to press "Show preview", which produces the corresponding webpage in your browser but does not make it publicly available yet (not until you press "Save"). Errors in formatting, links, tables, etc., are often much easier to discover from the rendered page than from the raw wikitext.

If you are not satisfied you can make more changes and preview the page as many times as necessary. Then write a short [[Help:Edit summary|edit summary]] in the small text field below the edit-box and when finished press "Save". Depending on your system, pressing the "Enter" key while the edit box is not active (i.e., there is no typing cursor in it) may have the same effect as pressing "Save".

You may find it more convenient to copy and paste the text first into your favorite [[en:text editor|text editor]], edit and spell check it there, and then paste it back into your [[en:web browser|web browser]] to preview. This way, you can also keep a local backup copy of the pages you have edited. It also allows you to make changes offline, but before you submit your changes, ''please make sure nobody else has edited the page'' since you saved your local copy (by checking the [[Help:page history|page history]]), otherwise you may accidently revert someone else's edits. If someone ''has'' edited it since you copied the page, you'll have to merge their edits into your new version (you can find their specific edits by using the "[[Help:diff|diff]]" feature of the page history). These issues are handled automatically by the Mediawiki software if you edit the page in your web browser.

== Minor edits ==
When editing a page, a logged-in user has the option of flagging the edit as a "minor edit". This feature is important, because users can choose to ''hide'' minor edits in their view of the Recent Changes page, to keep the volume of edits down to a manageable level.

When to use this is somewhat a matter of personal preference. The rule of thumb is that an edit of a page that consists of spelling corrections, formatting, and minor rearranging of text should be flagged as a "minor edit". A major edit is basically something that makes the entry worth revisiting for somebody who wants to watch the article rather closely. So any "real" change, even if it is a single word, should be flagged as a "major edit".

The reason for not allowing a user who is not logged in to mark an edit as minor is that vandalism could then be marked as a minor edit, in which case it would stay unnoticed longer. This limitation is another reason to log in.

Credits: text taken from WikiMedia's [http://meta.wikimedia.org/wiki/Help:Editing help page]. Visit there for even more editing help.

Module Basics

2006-03-17T14:26:08Z

Striker: Reverted edit of Venusparkle85, changed back to last version by Sofar

__TOC__

In ''lunar'' parlance, software packages are called [[modules]]. The collection of all modules is the [[moonbase]], which is simply a directory (usually <code>/var/lib/lunar/moonbase</code>) containing ''sections'' (i.e. directories) which in turn contain the [[module]] directories.

A module is simply a directory containing the scripts necessary to build a software package, and optionally configuration files which may be needed in <code>/etc</code>. Some modules require only a [[DETAILS]] file, however this is only the case for a few of the modules in the entire moonbase. In each case, after [[DETAILS]], [[DEPENDS]], and [[CONFIGURE]], where a module can use lunar's default internal function(s), there is no need for a module-specific script.

* [[DETAILS]] sets version, source URL(s) and other critical data
* [[CONFLICTS]] specifies modules which must (will) be removed by module
* [[CONFIGURE]] interactive script where build options can be set
* [[DEPENDS]] specifies required and optional packages
* [[PRE_REMOVE]] used by [[lrm]]; actions which must preceed removal
* [[PRE_BUILD]] most often used for patching, unpacking addional source tarballs
* [[BUILD]] runs necessary variations on: configure; make; make install
* [[POST_BUILD]] install configuration scripts and data.
* [[POST_INSTALL]] messages, notes more cleanups, configuration fixes
* [[POST_REMOVE]] used by [[lrm]]; actions which must follow removal

== Package Build and Install Scripts ==

The following scripts are used by [[lin]] or indirectly by [[lunar]] when building modules.

=== The DETAILS script ===

Every module is required to have at least a [[DETAILS]] file. A minimal [[DETAILS]] may appear as follows: (<code>/var/lib/lunar/moonbase/editors/emacs/DETAILS</code>)

MODULE=emacs
VERSION=21.3
SOURCE=$MODULE-$VERSION.tar.gz
SOURCE_DIRECTORY=$BUILD_DIRECTORY/$MODULE-$VERSION
SOURCE_URL=$GNU_URL/$MODULE/$SOURCE
SOURCE_URL=<nowiki>ftp://ftp.gnu.org/pub/gnu/$MODULE/$SOURCE</nowiki>
SOURCE_VFY=md5:a0bab457cbf5b4f8eb99d1d0a3ada420
WEB_SITE=<nowiki>http://www.gnu.org/software/emacs</nowiki>
ENTERED=20010922
UPDATED=20020529
SHORT="Emacs is the extensible, self-documenting real-time display editor."
cat << EOF
Emacs is the extensible, customizable, self-documenting real-time
display editor.
EOF

With comments, default values:

MODULE=emacs # Module name, yes it's redundant
VERSION=21.3 # Version, changes *often*
SOURCE=$MODULE-$VERSION.tar.gz # Source filename
SOURCE_DIRECTORY=$BUILD_DIRECTORY/$MODULE-$VERSION # Where source unpacks
# ($BUILD_DIRECTORY=/usr/src)
SOURCE_URL[0]=$GNU_URL/$MODULE/$SOURCE # Download URL
SOURCE_URL[1]=<nowiki>ftp://ftp.gnu.org/pub/gnu/$MODULE/$SOURCE</nowiki> # Alternate URL(s)
SOURCE_VFY=md5:a0bab457cbf5b4f8eb99d1d0a3ada420 # Sets md5 hash or pgp/gpg sig url
WEB_SITE=<nowiki>http://www.gnu.org/software/emacs</nowiki> # where to learn more
ENTERED=20010922 # First appearance in moonbase
UPDATED=20020529 # Date of latest change.
# Force update by setting this

# The remaining lines are used for input to the 'lvu what' command
# and are best copied from the source-maintainer's own description.

SHORT="Emacs is the extensible, self-documenting real-time display editor."
cat << EOF
Emacs is the extensible, customizable, self-documenting real-time
display editor.
EOF

=== The DEPENDS script ===

The [[DEPENDS]] script is essential to configuration management, and is the key to the overall operation of lunar. Dependencies should be exactly specified, preferably not assuming the presence of any other modules, while knowing the sub-dependencies of the modules which are added and not adding those explictly where not needed.

'''Warning''' - Getting this right is difficult. Because the state of installed packages may vary widely, it's important to have a good understanding of what might be or not be installed on a target system.

'''Note''' - By convention Lunar does not include the X Window System, xfree86 or XOrg, in any dependency. There are two reasons for this choice. First we expect that users must understand that to use a graphical application locally, the X Window System must be installed. Second, due to the sligtly unusual definition of client and server used by X11, it is often in fact possible to build graphical applications and tools for remote display, without the server components locally installed. At some future date we may elect to provide a client-only installation of xfree86.

[[DEPENDS]] may include both required and optional dependencies. The '''depends()''' function statement simply determines one required package. The optional_depends function is a little more complex. It consists of the required package, necessary --options to give to <code>./configure</code> for yes and no respectively, and an explanatory comment telling the user the purpose of the option being presented. A typical [[DEPENDS]] file might appear as follows: (<code>/var/lib/lunar/moonbase/devel/subversion/DEPENDS</code>)

depends zlib &&
depends openssl &&
optional_depends "db4" "--with-berkeley-db" "" "for creating local repositories"
# ^ ^ ^ ^
# | | | |
# optional package if "Y" if "N" explanatory comment
# { ./configure strings }

'''Aliases'''

Aliases are a mean to select a generic module. When you need a functionnality that can be provided by two or more softwares, you can select one of them to provide a correct dependency.

Example /var/lib/lunar/moonbase/aliases:
<code>
%APACHE:apache apache2 apache-mod_ssl
%FAM:fam gamin
%GECKO_RENDERER: firefox thunderbird mozilla
%GHOSTSCRIPT:espgs ghostscript
%MTA:postfix exim sendmail esmtp
%SLANG:slang slang2
%X:XOrg XOrg-test xfree86 xfree86-beta
%XMLRENDERER: libxml2 expat
%XSCREENSAVER:xscreensaver xscreensaver-gtk1 xscreensaver-kde
</code>

For example you can choose %X instead of XOrg in a module that would depends on any X server:
<code>
depends %X
</code>

=== The CONFLICTS script ===

This script is simply used to specify modules which will be removed when a given module is installed. An example would be: (<code>/var/lib/lunar/moonbase/editors/elvis/CONFLICTS</code>)

conflicts vim

=== The CONFIGURE script ===

The [[CONFIGURE]] script is used to collect interactive input from the user on optional parameters for the software build. use the '''query''' function and provide a default answer to each question. The results of the answers are then used to store configuration variables needed in configuration state files. An a simple example might be: (<code>/var/lib/lunar/moonbase/crypto/gnupg/CONFIGURE</code>)

if ! grep -q CONFIGURED $MODULE_CONFIG ; then
if query "Enable experimental external HKP keyserver interface? " n ; then
OPTS="$OPTS --enable-external-hkp"
fi
echo 'CONFIGURED="y"' >> $MODULE_CONFIG
fi

Another way is using '''mquery''' like the lilo module does:

mquery RUN_LILO "Run LILO automatically upon LILO upgrades?" y

=== The PRE_BUILD script ===

[[PRE_BUILD]] is used where special processing is needed before undertaking the actual build steps. Typical requirements include unpacking multiple sources, creating necessary system or source-tree direcotries and applying source patches. And example would be: (<code>/var/lib/lunar/moonbase/doc-tools/html2db/PRE_BUILD</code>)

mk_source_dir $SOURCE_DIRECTORY &&
unpack $SOURCE &&
cd $MODULE
unpack $SOURCE2
cd tidy
patch_it $SOURCE_CACHE/$SOURCE3 0
cd /usr/src/$MODULE

=== The BUILD script ===

[[BUILD]] is used where the '''default_build()''' function does not work for a given software package. For reference the commands run by default are:

Function '''default_build()''' calls '''default_config''' which executes:

./configure --build=$BUILD \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--infodir=/usr/share/info \
--mandir=/usr/share/man \
$OPTS

Next, '''default_build()''' calls '''default_make''' which executes:

make &&
prepare_install &&
make install

Where this build configuration does not work, the [[BUILD]] script is used to provide the needed steps. About 75% of modules need a [[BUILD]] script. Two examples include: (<code>/var/lib/lunar/moonbase/archive/gzip/BUILD</code>)

(
./configure --build=$BUILD \
--prefix=/usr \
--bindir=/bin \
--infodir=/usr/share/info \
--mandir=/usr/share/man &&
make &&
prepare_install &&
make bindir=/bin install
) > $C_FIFO 2>&1

and: (<code>/var/lib/lunar/moonbase/editors/ex/BUILD</code>)

(
cd $SOURCE_DIRECTORY &&
sedit 's/usr.local/usr/' Makefile &&
sedit 's/= man/= share\/man/' Makefile &&
sedit 's/ucb/bin/' Makefile &&
sedit 's/= termlib/= ncurses/' Makefile &&
make &&
prepare_install &&
make install
) > $C_FIFO 2>&1

The first example is a build which needs non-standard 'configure' and 'make install' commands. The second is a build which does not use gnu auto-tools' 'configure' script.

'''Note''' - [[BUILD]] scripts must execute inside a (), called a subshell invocation, construct and output is always directed to a named pipe (aka FIFO). Therefor all [[BUILD]] files take the follwing form:

(
# commands are put here
) > $C_FIFO 2>&1 # $C_FIFO holds the name of a fifo in /tmp used for 'voyeur'

=== The POST_BUILD script ===

[[POST_BUILD]] runs in place of the '''default_post_build''' routine which is used to install minor documentation and transfer/enable initialization scripts and similar system data, mostly into <code>/etc</code>.

[[POST_BUILD]] script usage is '''deprecated'''. You should install your config files in [[BUILD]] (remember not to overwrite previous config files!) or install defaults from [[POST_INSTALL]] (again, do not overwrite present files!). The ability to use a [[POST_BUILD]] script is purely for certain internal functions.

=== The POST_INSTALL script ===

[[POST_INSTALL]] has no equivalent functions, and is run to handle post-installation work in a general manner. An example is: (<code>/var/lib/lunar/moonbase/compilers/gcc/POST_INSTALL</code>)

cd /usr/lib/gcc-lib/$BUILD/$VERSION &&
ln -sf /usr/bin/cpp cpp &&
cd /lib/ &&
ln -sf /usr/bin/cpp cpp &&
if [ ! -e /usr/bin/cc ] ; then
ln -s gcc /usr/bin/cc
fi

== Package Removal Scripts ==

Module removal is handled by [[lrm]]. Because installation is monitored and backup tarballs are created using installwatch, most of package removal is handled automatically using the logs created by installwatch. However we provide for additional actions to be taken through the [[PRE_REMOVE]] and [[POST_REMOVE]] scripts.

=== The PRE_REMOVE script ===

[[PRE_REMOVE]] is needed to execute any tasks needed prior to the main task of removing all files installed by the module. An example would be: (<code>/var/lib/lunar/moonbase/mail/docbook-3.1/PRE_REMOVE</code>)

CENTRALIZED=/etc/sgml/catalog
DOCBOOK_INSTALL_DIR=/usr/share/sgml/docbook/$VERSION
install-catalog -r $CENTRALIZED $DOCBOOK_INSTALL_DIR/catalog

=== The POST_REMOVE Script ===

[[POST_REMOVE]] may be used to remove data not tracked by installwatch and to correctly adjust remaining configuration files and data. Examples would include: (<code>/var/lib/lunar/moonbase/devel/binutils/POST_REMOVE</code>)

install-info --delete as --info-dir /usr/info
install-info --delete bfd --info-dir /usr/info
install-info --delete binutils --info-dir /usr/info
install-info --delete configure --info-dir /usr/info
install-info --delete gasp --info-dir /usr/info
install-info --delete gprof --info-dir /usr/info
install-info --delete ld --info-dir /usr/info

or: (<code>/var/lib/lunar/moonbase/compilers/php/POST_REMOVE</code>)

if module_installed apache; then
cp /etc/httpd/httpd.conf /tmp/httpd.conf
grep -v "LoadModule php4_module" /tmp/httpd.conf |
grep -v "AddModule mod_php4.c" > /etc/httpd/httpd.conf
rm -f /tmp/httpd.conf
elif module_installed apache_mod_ssl; then
cp /etc/httpsd/httpd.conf /tmp/httpd.conf
grep -v "LoadModule php4_module" /tmp/httpd.conf |
grep -v "AddModule mod_php4.c" > /etc/httpsd/httpd.conf
rm -f /tmp/httpd.conf
fi

Moonbase

2006-01-08T01:07:50Z

Striker: Reverted edit of 222.124.225.236, changed back to last version by Sofar

==Moonbase==

__TOC__

===What is moonbase?===
The moonbase is the complete collection of all the software packages ([[module]]s) that [[Lunar Linux]] offers its users. It is organized in a hierarchical structure of directories and files; usually found on the user's system at <code>/var/lib/lunar/moonbase</code>. Generically speaking, the moonbase is just a directory with stuff (sub-directories and files) inside it.

===Sections===
The moonbase's first level of structure/organization is a [[section]]. A section is a name that serves to classify and organize a group of [[module]]s into logical partitions. Each [[section]] is simply a sub-directory that resides right below the root of the [[moonbase]] or inside another section. Sections can also be nested in other sections.

===Modules===
[[Modules]] sit in a [[section]] directory. A module consists of a directory with specific files and other directories, that are not sections. These sub-directories represent a single module that "belongs" to that section of the moonbase. A module, to be a bit simplistic, is a set of "instructions" to perform a task; Namely, instructions to compile and then install what was compiled onto the user's file-system. So if we had a [[module]] named FooGame that was located in the "games" section of the [[moonbase]], we would find a directory called FooGame at <code>/var/lib/lunar/moonbase/games/FooGame</code>.

To summarize, installable software packages are called modules. The collection of all of the modules is called the moonbase, which is simply a directory containing logical sections (sub-directories) which, in turn, contain the modules directories.

[[Moonbase]]
\--[[section]]
|--[[section]]
| \--[[module]]
| \-- files
\--[[module]]
\-- files

Lunar Linux

2005-11-11T21:34:11Z

Striker: Comment notice...

__NOEDITSECTION__
<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td colspan="2" style="padding: 3px; background: #ffe; border: 1px solid #ff0; vertical-align: top;">
{{Main Page:Languages}}
</td>
</tr><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
{{Main Page:Documentation}}
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
{{Main Page:Misc}}
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">
{{Main Page:About}}
</td>
</tr></table>

Template:Main Page:Misc

2005-11-03T19:57:27Z

Striker: add howto page

<div style="float: right; padding-top: 0.1em; padding-right: 15px;">
{{ed|Main_Page:Misc|}}
</div>

<h2 style="font-variant: small-caps;">[[Lunar Linux:Misc|Other Information]]</h2>

<h4>[[Howto Articles]]</h4>
* [[Installation:No CD|No CD Installation]]
* [[Installation:Kernel_2.6._HowTo|Install a 2.6 kernel]]
* [[Installation:The_kernel_commandline_/dev_params_mini-HowTo|The kernel commandline /dev params mini-HowTo]]
* [[Installation:Software Raid|Installation on software RAID]]
* [[Miscellaneous:USB camera howto|USB camera howto]]
* [[Howto Articles|more...]]

<h4>Reviews</h4>
* [http://www.bluefish.se/aquarium/lunar.html Review of Lunar Linux] • by Göran Krampe [http://www.bluefish.se/index.html bluefish.se]
* [http://distrocenter.linux.com/distrocenter/05/07/25/1319212.shtml?tid=127 Lunar Linux Review] • by Preston St Pierre on [http://linux.com/ Linux.com]

<h4>Fun Facts about Lunar</h4>
* [[how_long|How long does it take]] to install something on lunar?

<h4>3rd Party Websites</h4>
* [http://lunar-linux.interhact.net/ Lunar Linux Non-Free Modules]

<div style="text-align: right; font-variant: small-caps; padding-right: 15px;">
[[Lunar Linux:Misc|More Information]]
</div>

Miscellaneous:USB camera howto

2005-11-01T16:35:09Z

Striker: stub...

{{Template:Howto-stub}}

== Get pictures from your camera with gphoto2 ==

===Installing gphoto2===

# lin -cr gphoto2

This will install the required libgphoto2 which in turn will demand installing libusb and libexif... i said yes to both.

"libusb" "For usb camera support" say "yes"
"libexif" "For EXIF tag support" say "yes"

Now run the next command as a normal user
$ gphoto2 --list-files
This should result in a complete mess of error messages with the main conclusion :
gphoto2-port(0): Could not release interface 0 (Operation not permitted).
If we would like to, we could get the pictures of our camera with the root account but as this is not very convenient we'll setup some permissions for our camera so a normal user can access the camera.

===Setting up permissions to access your camera as a normal user===

I only tested this with udev and hotplug, so that's kernel 2.6.x. follow this [[Installation:Kernel 2.6. HowTo|guide]] and choose to install udev.

In /etc/fstab add this line:

usbfs /proc/bus/usb usbfs defaults 0 0

Add a new group "usb" and make sure that the user (*username*) that has to access the camera is part of that group.

# groupadd -g 31 usb

# usermod -g usb *username*

Just write the output of /usr/lib/libgphoto2/print-usb-usermap to the /etc/hotplug/usb/usbcam.usermap file:

# /usr/lib/libgphoto2/print-usb-usermap > /etc/hotplug/usb/usbcam.usermap

Copy /usr/share/doc/gphoto2/linux-hotplug/usbcam.user to /etc/hotplug/usb/usbcam

# cp /usr/share/doc/gphoto2/linux-hotplug/usbcam.user /etc/hotplug/usb/usbcam

edit /etc/hotplug/usb/usbcam and change the line :
user=ROOT
to
user=*username*

*note : If you have multiple users that have to be able to access the camera copy the file usbcam.group and add all your users in that group.

# chmod +x /etc/hotplug/usb/usbcam

Plug in the camera and switch it on. The kernel will now notice that your camera has been connected and will find no kernel driver for the device, next it will ask hotplug to do something about the new device file.
Hotplug will then look into /etc/hotplug/usb/*.usermap and find that the usbcam script is to be called for the newly attached device. Thus /etc/hotplug/usb/usbcam is executed, and will set the device permissions correctly. Your /var/log/messages syslog file will contain some messages to that effect.
You will probably want to check whether the respective device file has its permissions set up correctly. Have a look at /proc/bus/usb with ls -lR /proc/bus/usb. There should be at least one device file (named something like 015) with the permissions set according to your wishes.

===Downloading the pictures of the camera===
Just as a normal user in your home directory, perform following commands:

$ gphoto2 --list-ports
$ gphoto2 --auto-detect
$ gphoto2 --summary
$ gphoto2 --list-files
$ gphoto2 --get-all-files

Now you shouldn't see any of the errors anymore and the pictures should be downloaded to your home-directory or to wherever you want them to be downloaded
A little variation of this command can make change the filename to the date that it has been pulled of the camera. Make sure the directory 'MyPictures' exists already.
$ gphoto2 --get-all-files --filename ~/MyPictures/'%y-%M-%d-%n'.jpg

===Links===
[http://www.gphoto.org/doc/manual/ link Gphoto homepage]

Template:Howto-stub

2005-11-01T16:34:19Z

Striker: howto stub, borrowed from [http://www.wikipedia.org/ wikipedia]

<div class="boilerplate metadata" id="stub"><table cellpadding="0" cellspacing="0" style="background-color: transparent;"><tr><td></td><td>'' This howto article is a [[Lunar Linux:Perfect stub article|stub]]. You can [[Lunar Linux:Find or fix a stub|help]] us by [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} expanding it]''.</td></tr></table></div>[[Category:Howto stubs]]