Lunar Linux - User contributions [en]

Lunar Linux:FAQ

2008-07-25T21:27:53Z

Moe: /* What is that in the Lunar-Linux logo? */

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]].

==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) or Fastest (Note that fastest doesn't work on all systems, i.e. k6).
* '''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.

Lunar Linux:FAQ

2008-07-25T21:09:17Z

Moe: /* What is that in the Lunar-Linux logo? */ Add designer information

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]].

==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) or Fastest (Note that fastest doesn't work on all systems, i.e. k6).
* '''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 [mailto:mschin@gmx.de Michael Schindler] in 2003 and appeared as the official logo of the Lunar Linux project in 2004.

Install fglrx

2008-06-06T21:25:47Z

Moe: First version of the HOWTO. Enjoy!

=Installing the ATI binary driver=
==What is this document about?==
This HOWTO covers the steps needed in order to install the ATI binary driver, also known as ''"fglrx"'', on your system. It also gives a couple of hints as how to configure your system the right way to use it afterwards.

==Which architectures are supported?==

Currently, the ''fglrx'' module is tested on x86 and x86_64-based architectures.

==Prerequisites==
===Kernel configuration===
In order to install the driver successfully you need to make sure the following kernel options are enabled within your kernel configuration:

* CONFIG_PCI_LEGACY
* CONFIG_MTRR
* CONFIG_MODVERSIONS

Then make sure the following options are '''NOT''' selected:

* PREEMPT_RCU
* CONFIG_DRM

Your kernel '''must not''' be compiled with DRM support. A DRM (direct rendering manager) kernel module is going to be compiled during the install phase.

===Module configuration===
First of all, please make sure that the module "xorg-server" has been compiled with GLX support. You can check by either taking a look at the install log (lvu install xorg-server) whether or not it installed "libglx.so" or by relining the ''xorg-server'' module:

$ lin -cr xorg-server

and say 'n' (default answer) to "Do you intent to use the NVIDIA binary driver?".

Secondly, install the module ''mesa-glu''. Its going to provide vital system headers for applications that are relying on OpenGL acceleration.

==Installation==

Now go ahead and install the ''fglrx'' module by issueing:

$ lin -cr fglrx

One the installation is finished you're good to go.

==Configuring XOrg==

In order to make use of the newly installed driver you will have to change your XOrg configuration. You can either do it manually by adding a "Device" section mentioning the fglrx driver or you use "aticonfig" which is provided by the fglrx module:

$ aticonfig --initial

Its going to do its best to autodetect most of your hardware and configure your ''xorg.conf'' (located in ''/usr/X11/xorg.conf'') accordingly. It might not work very well for multihead or other different and/or strange setup. You might want to consider a manual setup in these cases. For more information about ''aticonfig'' either run ''aticonfig --help'' or take a look at the installed documentation in ''/usr/share/doc/ati''.

==Troubleshooting==

=== Everything is painfully slow!===
XOrg 7.2+ enabled an extension called "Compositing" by default which is useful for drawing windows rendered through OpenGL on the desktop. Modules like the window manager ''compiz'' are relying on it. Unfortunately, the ''fglrx'' module (to date) does not support AIGLX, the backend used to draw those windows, very well. Thus its recommended to disable the composite extension. You can do so by adding the following lines to your ''xorg.conf''

Section "Extensions"
Option "Composite" "false"
EndSection

===It does not compile/work/I found a bug!===
Please consult with our [http://bugs.lunar-linux.org bugtracker] and file a bugreport or ask on the [http://foo-projects.org/mailman/listinfo/lunar mailinglist ] (registration required) for help. You may also [mailto:moe@lunar-linux.org drop me a mail directly] if you want to.

Created by [[User:Moe|Moe]] 21:25, 6 June 2008 (UTC)

Howto Articles

2008-06-06T20:51:37Z

Moe: Add fglrx

Here you will find several HOWTOs concerning specific software of hardware parts. If you think, you have anything useful to contribute then please go ahead and add whatever you deem necessary.

=Installation HOWTOs=
===[[Installation:No_CD|Installation without a CD]]===
* '''No CD handy''' to install Lunar Linux? Don't despair! We've got it all covered. Read on!

===[[Installation:No_network|Installation without a network connection]]===
* This HOWTO covers how to '''install Lunar Linux without a decent network connection''' available. Its tricky .. yet, possible.

===[[Installation:Software_Raid|Install Lunar Linux on a software RAID]]===
* You want to install Lunar Linux directly on a software RAID created at install time? Go ahead and read the instructions.

=Module HOWTOs=
===[[Install_XOrg7|XOrg 7 Installation guide]]===
* This guide covers all the quirks you will have to go through when '''upgrading from XOrg 6.x to XOrg 7.x'''. Also worth reading when you're '''installing XOrg7 on a new installation'''.
===[[Install_fglrx|Installing the ATI binary driver]]===
* This guide covers everything you need to know in order to install the ATI "fglrx" binary driver.

=Software HOWTOs=
===[[Using_AIGLX_-_Installing_Beryl|AIGLX Guide]]===
* How do you '''enable AIGLX XOrg acceleration''' inside XOrg7? This HOWTO shows the path. It also covers the installation of [http://www.beryl-project.org/ Beryl], a window manager that makes use of the AIGLX support.

=Hardware HOWTOs=
===[[Miscellaneous:USB camera howto|USB Camera HOWTO]]===
* This HOWTO explains how to connect and '''make use of your USB powered digital camera'''.

=Other HOWTOs=
===[[Installation:The_kernel_commandline_/dev_params_mini-HowTo|Bootloader options for handling /dev devices]]===
* This article explains how you can '''manipulate the way Lunar Linux handles devices''' at boot time using your favorite bootloader.

Using AIGLX - Installing Beryl

2007-02-18T20:37:37Z

Moe:

As of XOrg 7.2 (added to moonbase on the 15th of February 2007) AIGLX has become a permanent part of the xorg-server module. All you need to do is to update your XOrg7 installation. AIGLX is going to get installed automatically.

=Configuration=

You will have to run a hardware-accelerated XOrg server in order to utilize the full powers of AIGLX. The following xorg.conf sniplet shows exactly what needs to be done:

<code>
Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "true" #--optional--
Option "DAMAGE" "true" #--optional--
EndSection

Section "ServerLayout"
Option "AIGLX" "true"
[...]
EndSection
</code>

After that AIGLX should be enabled and ready to go. Check your XOrg logfiles to see whether thats actually the case.

==NVIDIA and AMD==

If you're using either of the binary drivers provided by NVIDIA or ATI/AMD you will have to follow a different path.

===NVIDIA===

NVIDIA provides its own infrastructure for AIGLX called 'NV-GLX' Either you use the excellent nvidia-xconfig utility to enable the required configuration patters or you edit your xorg.conf accordingly:

<code>

Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "true" #--optional--
Option "DAMAGE" "true" #--optional--
EndSection

Section "Screen"
...
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
EndSection

Section "Device"
Driver "nvidia"
Option "RenderAccel" "true"
Option "AddARGBGLXVisuals" "true"
Option "AllowGLXWithComposite" "true"
...
EndSection

</code>

===ATI/AMD (fglrx)===

FIXME

=Trying out AIGLX=

If you want to take advantage of all the new effects AIGLX is helping to induce you might want to give the following applications a try:

==Beryl==

Beryl is a window manager framework that is able to make use of OpenGL acceleration AIGLX provides for the XComposite and XDamage extensions. For more information about Beryl and its parts (and the project itself) [http://www.beryl-project.org/ visit their homepage].

The following modules are available and should all be installed if you want to achieve a satisfying experience:

{|
| * beryl-core
| Beryl core package
|-
| * beryl-plugins
| Plugins package for beryl
|-
| * beryl-dbus
| Dbus plugin for beryl
|-
| * beryl-settings
| Settings manager for beryl
|-
| * beryl-manager
| Manager package for beryl
|-
| * emerald
| Window decorator for beryl
|-
| * emerald-themes
| Themes for emerald
|}

All of those modules require XOrg7 and subversion to be installed on your computer (which is not going to be installed automagically). Xinerama and TwinView are both supported by Beryl.

Using AIGLX - Installing Beryl

2007-02-18T20:36:53Z

Moe:

XOrg 7.2 (added to moonbase on the 15th of February 2007) AIGLX has become a permanent part of the xorg-server module. All you need to do is to update your XOrg7 installation. AIGLX is going to get installed automatically.

=Configuration=

You will have to run a hardware-accelerated XOrg server in order to utilize the full powers of AIGLX. The following xorg.conf sniplet shows exactly what needs to be done:

<code>
Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "true" #--optional--
Option "DAMAGE" "true" #--optional--
EndSection

Section "ServerLayout"
Option "AIGLX" "true"
[...]
EndSection
</code>

After that AIGLX should be enabled and ready to go. Check your XOrg logfiles to see whether thats actually the case.

==NVIDIA and AMD==

If you're using either of the binary drivers provided by NVIDIA or ATI/AMD you will have to follow a different path.

===NVIDIA===

NVIDIA provides its own infrastructure for AIGLX called 'NV-GLX' Either you use the excellent nvidia-xconfig utility to enable the required configuration patters or you edit your xorg.conf accordingly:

<code>

Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "true" #--optional--
Option "DAMAGE" "true" #--optional--
EndSection

Section "Screen"
...
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
EndSection

Section "Device"
Driver "nvidia"
Option "RenderAccel" "true"
Option "AddARGBGLXVisuals" "true"
Option "AllowGLXWithComposite" "true"
...
EndSection

</code>

===ATI/AMD (fglrx)===

FIXME

=Trying out AIGLX=

If you want to take advantage of all the new effects AIGLX is helping to induce you might want to give the following applications a try:

==Beryl==

Beryl is a window manager framework that is able to make use of OpenGL acceleration AIGLX provides for the XComposite and XDamage extensions. For more information about Beryl and its parts (and the project itself) [http://www.beryl-project.org/ visit their homepage].

The following modules are available and should all be installed if you want to achieve a satisfying experience:

{|
| * beryl-core
| Beryl core package
|-
| * beryl-plugins
| Plugins package for beryl
|-
| * beryl-dbus
| Dbus plugin for beryl
|-
| * beryl-settings
| Settings manager for beryl
|-
| * beryl-manager
| Manager package for beryl
|-
| * emerald
| Window decorator for beryl
|-
| * emerald-themes
| Themes for emerald
|}

All of those modules require XOrg7 and subversion to be installed on your computer (which is not going to be installed automagically). Xinerama and TwinView are both supported by Beryl.

Howto Articles

2007-02-18T19:44:34Z

Moe: /* AIGLX Guide */

Here you will find several HOWTOs concerning specific software of hardware parts. If you think, you have anything useful to contribute then please go ahead and add whatever you deem necessary.

=Installation HOWTOs=
===[[Installation:No_CD|Installation without a CD]]===
* '''No CD handy''' to install Lunar Linux? Don't despair! We've got it all covered. Read on!

===[[Installation:No_network|Installation without a network connection]]===
* This HOWTO covers how to '''install Lunar Linux without a decent network connection''' available. Its tricky .. yet, possible.

===[[Installation:Software_Raid|Install Lunar Linux on a software RAID]]===
* You want to install Lunar Linux directly on a software RAID created at install time? Go ahead and read the instructions.

=Module HOWTOs=
===[[Install_XOrg7|XOrg 7 Installation guide]]===
* This guide covers all the quirks you will have to go through when '''upgrading from XOrg 6.x to XOrg 7.x'''. Also worth reading when you're '''installing XOrg7 on a new installation'''.

=Software HOWTOs=
===[[Using_AIGLX_-_Installing_Beryl|AIGLX Guide]]===
* How do you '''enable AIGLX XOrg acceleration''' inside XOrg7? This HOWTO shows the path. It also covers the installation of [http://www.beryl-project.org/ Beryl], a window manager that makes use of the AIGLX support.

=Hardware HOWTOs=
===[[Miscellaneous:USB camera howto|USB Camera HOWTO]]===
* This HOWTO explains how to connect and '''make use of your USB powered digital camera'''.

=Other HOWTOs=
===[[Installation:The_kernel_commandline_/dev_params_mini-HowTo|Bootloader options for handling /dev devices]]===
* This article explains how you can '''manipulate the way Lunar Linux handles devices''' at boot time using your favorite bootloader.

Howto Articles

2007-02-18T19:44:14Z

Moe: /* AIGLX Guide */

Here you will find several HOWTOs concerning specific software of hardware parts. If you think, you have anything useful to contribute then please go ahead and add whatever you deem necessary.

=Installation HOWTOs=
===[[Installation:No_CD|Installation without a CD]]===
* '''No CD handy''' to install Lunar Linux? Don't despair! We've got it all covered. Read on!

===[[Installation:No_network|Installation without a network connection]]===
* This HOWTO covers how to '''install Lunar Linux without a decent network connection''' available. Its tricky .. yet, possible.

===[[Installation:Software_Raid|Install Lunar Linux on a software RAID]]===
* You want to install Lunar Linux directly on a software RAID created at install time? Go ahead and read the instructions.

=Module HOWTOs=
===[[Install_XOrg7|XOrg 7 Installation guide]]===
* This guide covers all the quirks you will have to go through when '''upgrading from XOrg 6.x to XOrg 7.x'''. Also worth reading when you're '''installing XOrg7 on a new installation'''.

=Software HOWTOs=
===[[Using_AIGLX_-_Installing_Beryl|AIGLX Guide]]===
* How do you '''enable AIGLX XOrg acceleration''' inside XOrg7? This HOWTO shows the path. It also covers the installation of [
http://www.beryl-project.org/ Beryl], a window manager that makes use of the AIGLX support.

=Hardware HOWTOs=
===[[Miscellaneous:USB camera howto|USB Camera HOWTO]]===
* This HOWTO explains how to connect and '''make use of your USB powered digital camera'''.

=Other HOWTOs=
===[[Installation:The_kernel_commandline_/dev_params_mini-HowTo|Bootloader options for handling /dev devices]]===
* This article explains how you can '''manipulate the way Lunar Linux handles devices''' at boot time using your favorite bootloader.

Using AIGLX - Installing Beryl

2007-02-18T19:40:47Z

Moe:

Using AIGLX - Installing Beryl

2007-02-18T19:38:43Z

Moe: Adding the AIGLX guide over here again. Also includes Beryl setup.

As of XOrg 7.2 (added to moonbase on the 15th of February 2007) AIGLX has become a permanent part of the xorg-server module. All you need to do is to update your XOrg7 installation. AIGLX is going to get installed automatically.

==Configuration==

You will have to run a hardware-accelerated XOrg server in order to utilize the full powers of AIGLX. The following xorg.conf sniplet shows exactly what needs to be done:

<code>
Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "true" #--optional--
Option "DAMAGE" "true" #--optional--
EndSection

Section "ServerLayout"
Option "AIGLX" "true"
[...]
EndSection
</code>

After that AIGLX should be enabled and ready to go. Check your XOrg logfiles to see whether thats actually the case.

===NVIDIA and AMD===

If you're using either of the binary drivers provided by NVIDIA or ATI/AMD you will have to follow a different path.

====NVIDIA====

NVIDIA provides its own infrastructure for AIGLX called 'NV-GLX' Either you use the excellent nvidia-xconfig utility to enable the required configuration patters or you edit your xorg.conf accordingly:

<code>

Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "true" #--optional--
Option "DAMAGE" "true" #--optional--
EndSection

Section "Screen"
...
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
EndSection

Section "Device"
Driver "nvidia"
Option "RenderAccel" "true"
Option "AddARGBGLXVisuals" "true"
Option "AllowGLXWithComposite" "true"
...
EndSection

</code>

====ATI/AMD (fglrx)====

FIXME

==Trying out AIGLX==

If you want to take advantage of all the new effects AIGLX is helping to induce you might want to give the following applications a try:

===Beryl===

Beryl is a window manager framework that is able to make use of OpenGL acceleration AIGLX provides for the XComposite and XDamage extensions. For more information about Beryl and its parts (and the project itself) [http://www.beryl-project.org/ visit their homepage].

The following modules are available and should all be installed if you want to achieve a satisfying experience:

{|
| * beryl-core
| Beryl core package
|-
| * beryl-plugins
| Plugins package for beryl
|-
| * beryl-dbus
| Dbus plugin for beryl
|-
| * beryl-settings
| Settings manager for beryl
|-
| * beryl-manager
| Manager package for beryl
|-
| * emerald
| Window decorator for beryl
|-
| * emerald-themes
| Themes for emerald
|}

All of those modules require XOrg7 and subversion to be installed on your computer (which is not going to be installed automagically). Xinerama and TwinView are both supported by Beryl.

Install XOrg7

2007-02-18T19:04:18Z

Moe: Add XOrg 7.2. XGL is no longer required.

=The path to XOrg7=

==Upgrading from XOrg 6.x==

Currently, the XOrg7 module needs you to do a few things manually if you upgrade from an earlier XOrg 6.x installation. You have to adhere to the following steps. If you do not listen to our advice then you're on your own.

*Remove the old XOrg (XOrg 6.x conflicts with XOrg 7.x)
: <code>lrm XOrg</code>
:: This action will most likely cause some font related modules to recompile, this is to be expected.

*Backup the old /etc/X11 (with your old xorg.conf)
: <code>mv /etc/X11 /etc/X11.old</code>

*Remove the old XOrg installation remains
: <code>rm -fr /usr/X11R6</code>

*Remove some old symlinks if they still exist
**<code>rm /usr/X11</code>
**<code>rm /usr/include/X11</code>
**<code>rm /usr/lib/X11</code>
**<code>rm /usr/include/GL</code>

*Clear out the %X alias which might be set to 'XOrg':
**<code>lunar unset LUNAR_ALIAS_X</code>
::Note: The next application that depends on X is going to ask you which alias you would like to match to %X. Choose XOrg7 here or you will have to reset the alias again!

*Make sure XOrg is never installed again:
**<code>lunar exile XOrg</code>
**<code>lunar fixdepends </code>
If you do not do this it could be resurrected by modules that were installed with XOrg...

==Installing XOrg 7.x ==

* History:
** XOrg 7.2: Added 20070215
** XOrg 7.1: Added 20061017

XOrg 7.2 was added to moonbase as of 15/02/2007. It has it's own section in /var/lib/lunar/moonbase/xorg7

You may use the 'XOrg7' module to install XOrg 7.2:<br /><br />
<code>lin XOrg7</code>

XOrg-7.2 includes full support for the AIGLX extension (which means accelerated X output for the XDamage and XComposite extensions). You don't need XGL anymore.

==Installation notes==

XOrg7 is installing to /usr by default and ''NOT'' to /usr/X11R7 or any other prefix inside /usr. The [http://www.pathname.com/fhs Filesystem Hierarchy Standard] does not allow that. All major linux distributions are following the FHS and have adjusted their builds accordingly:

*[http://lists.debian.org/debian-devel-announce/2006/04/msg00010.html Debian]
*[http://wiki.archlinux.org/index.php/Xorg7 Arch Linux]
*[http://gentoo-wiki.com/HOWTO_Modular_Xorg Gentoo]

You may however set an arbitary prefix for XOrg incase you do not want it to install to /usr. You may do so by running the following command:<br /><br />
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code><br><br />
The most commonly used prefix would be /usr/X11R7, however, some other prefix inside /opt is entirely possible.

The XOrg7 profile is going to create some symlinks on your system:<br /><br />
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default<br /></code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code><br /><br />
The X11R6 symlink is there for compatibility reasons. Many of the older and even some of the newer packages inside the moonbase have a hardcoded path pointing to /usr/X11R6 inside their source trees. Keeping the symlink prevents them from breaking apart.

==Missing modules from the XOrg 7.x modular tree==

Despite our best efforts to give you the whole XOrg 7.x modular tree as modules to install there are still many of them left untouched either because they are not important to run a full featured X environment or nobody had the time to add them yet. As always contribution are welcome and appreciated:

*x11-apps
**appres - list X application resource database
**lbxproxy - Low BandWidth X proxy
**mkcfm - create summaries of CID font metric files
**oclock - round X clock
**proxymngr - proxy manager service
**scripts - run X command on another system via rsh
**sessreg - Register X sessions in system utmp/utmpx databases
**showfont - show information about X font from font server
**twm - simple window manager
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xdbedizzy - DBE sample
**xditview - display ditroff output
**xdm - list X application resource database
**xf86dga - known unto god
**xfd - display all the characters in an X font
**xfindproxy - locate proxy services
**xfontsel - point and click selection of X11 font names
**xfsinfo - X font server information utility
**xfwp - X Firewall Proxy
**xgc - X graphics demo
**xload - system load average display for X
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**xmag - magnify parts of the screen
**xphelloworld - Xprint sample applications
**xprehashprinterlist - Rehash list of Xprint printers
**xrx - "Broadway"
**xsetmode - set the mode for an X Input device
**xsetpointer - set an X Input device as the main pointer
**xsm - X Session Manager
**xstdcmap - X standard colormap utility
**xtrap - an extension to X that facilitates user emulation
**xvidtune - video mode tuner for Xorg
*x11-data ==> COMPLETE
*x11-doc
**xorg-docs
**xorg-sgml-doctools
*x11-driver
**xf86-video-sunbw2
**xf86-video-suncg3
**xf86-video-suncg6
**xf86-video-suncg14
**xf86-video-sunffb
**xf86-video-sunleo
**xf86-video-suntcx
**xf86-video-tdfx
**xf86-video-tga
**xf86-video-trident (added by Auke - 20061103)
**xf86-video-tseng
*x11-extras ==> COMPLETE
*x11-font ==> COMPLETE
*x11-lib
**libAppleWM - platform specific libraries: [MacOS]
**libWindowsWM - platform specific libraries: [Win32]
*x11-proto
**windowswmproto - platform specific protocol headers [Win32]
*x11-util
**lndir
*xserver ==> COMPLETE

Install XOrg7

2007-02-11T18:12:02Z

Moe: Adding a note about resetting aliases

=The path to XOrg7=

==Upgrading from XOrg 6.x==

Currently, the XOrg7 module needs you to do a few things manually if you upgrade from an earlier XOrg 6.x installation. You have to adhere to the following steps. If you do not listen to our advice then you're on your own.

*Remove the old XOrg (XOrg 6.x conflicts with XOrg 7.x)
: <code>lrm XOrg</code>
:: This action will most likely cause some font related modules to recompile, this is to be expected.

*Backup the old /etc/X11 (with your old xorg.conf)
: <code>mv /etc/X11 /etc/X11.old</code>

*Remove the old XOrg installation remains
: <code>rm -fr /usr/X11R6</code>

*Remove some old symlinks if they still exist
**<code>rm /usr/X11</code>
**<code>rm /usr/include/X11</code>
**<code>rm /usr/lib/X11</code>
**<code>rm /usr/include/GL</code>

*Clear out the %X alias which might be set to 'XOrg':
**<code>lunar unset LUNAR_ALIAS_X</code>
::Note: The next application that depends on X is going to ask you which alias you would like to match to %X. Choose XOrg7 here or you will have to reset the alias again!

*Make sure XOrg is never installed again:
**<code>lunar exile XOrg</code>
**<code>lunar fixdepends </code>
If you do not do this it could be resurrected by modules that were installed with XOrg...

==Installing XOrg 7.x ==

===Installing xorg-7.1===

XOrg 7.1 was added to moonbase as of 17/10/2006. It has it's own section in /var/lib/lunar/moonbase/xorg7

You may now use the 'XOrg7' module to install XOrg 7.1:<br /><br />
<code>lin XOrg7</code>

XOrg-7.1 is needed if you want to mess with Xgl.

==Installation notes==

XOrg7 is installing to /usr by default and ''NOT'' to /usr/X11R7 or any other prefix inside /usr. The [http://www.pathname.com/fhs Filesystem Hierarchy Standard] does not allow that. All major linux distributions are following the FHS and have adjusted their builds accordingly:

*[http://lists.debian.org/debian-devel-announce/2006/04/msg00010.html Debian]
*[http://wiki.archlinux.org/index.php/Xorg7 Arch Linux]
*[http://gentoo-wiki.com/HOWTO_Modular_Xorg Gentoo]

You may however set an arbitary prefix for XOrg incase you do not want it to install to /usr. You may do so by running the following command:<br /><br />
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code><br><br />
The most commonly used prefix would be /usr/X11R7, however, some other prefix inside /opt is entirely possible.

The XOrg7 profile is going to create some symlinks on your system:<br /><br />
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default<br /></code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code><br /><br />
The X11R6 symlink is there for compatibility reasons. Many of the older and even some of the newer packages inside the moonbase have a hardcoded path pointing to /usr/X11R6 inside their source trees. Keeping the symlink prevents them from breaking apart.

==Missing modules from the XOrg 7.x modular tree==

Despite our best efforts to give you the whole XOrg 7.x modular tree as modules to install there are still many of them left untouched either because they are not important to run a full featured X environment or nobody had the time to add them yet. As always contribution are welcome and appreciated:

*x11-apps
**appres - list X application resource database
**lbxproxy - Low BandWidth X proxy
**mkcfm - create summaries of CID font metric files
**oclock - round X clock
**proxymngr - proxy manager service
**scripts - run X command on another system via rsh
**sessreg - Register X sessions in system utmp/utmpx databases
**showfont - show information about X font from font server
**twm - simple window manager
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xdbedizzy - DBE sample
**xditview - display ditroff output
**xdm - list X application resource database
**xf86dga - known unto god
**xfd - display all the characters in an X font
**xfindproxy - locate proxy services
**xfontsel - point and click selection of X11 font names
**xfsinfo - X font server information utility
**xfwp - X Firewall Proxy
**xgc - X graphics demo
**xload - system load average display for X
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**xmag - magnify parts of the screen
**xphelloworld - Xprint sample applications
**xprehashprinterlist - Rehash list of Xprint printers
**xrx - "Broadway"
**xsetmode - set the mode for an X Input device
**xsetpointer - set an X Input device as the main pointer
**xsm - X Session Manager
**xstdcmap - X standard colormap utility
**xtrap - an extension to X that facilitates user emulation
**xvidtune - video mode tuner for Xorg
*x11-data ==> COMPLETE
*x11-doc
**xorg-docs
**xorg-sgml-doctools
*x11-driver
**xf86-video-sunbw2
**xf86-video-suncg3
**xf86-video-suncg6
**xf86-video-suncg14
**xf86-video-sunffb
**xf86-video-sunleo
**xf86-video-suntcx
**xf86-video-tdfx
**xf86-video-tga
**xf86-video-trident (added by Auke - 20061103)
**xf86-video-tseng
*x11-extras ==> COMPLETE
*x11-font ==> COMPLETE
*x11-lib
**libAppleWM - platform specific libraries: [MacOS]
**libWindowsWM - platform specific libraries: [Win32]
*x11-proto
**windowswmproto - platform specific protocol headers [Win32]
*x11-util
**lndir
*xserver ==> COMPLETE

Howto Articles

2007-02-11T18:06:26Z

Moe: Redesigning HOWTO page

Here you will find several HOWTOs concerning specific software of hardware parts. If you think, you have anything useful to contribute then please go ahead and add whatever you deem necessary.

=Installation HOWTOs=
===[[Installation:No_CD|Installation without a CD]]===
* '''No CD handy''' to install Lunar Linux? Don't despair! We've got it all covered. Read on!

===[[Installation:No_network|Installation without a network connection]]===
* This HOWTO covers how to '''install Lunar Linux without a decent network connection''' available. Its tricky .. yet, possible.

===[[Installation:Software_Raid|Install Lunar Linux on a software RAID]]===
* You want to install Lunar Linux directly on a software RAID created at install time? Go ahead and read the instructions.

=Module HOWTOs=
===[[Install_XOrg7|XOrg 7 Installation guide]]===
* This guide covers all the quirks you will have to go through when '''upgrading from XOrg 6.x to XOrg 7.x'''. Also worth reading when you're '''installing XOrg7 on a new installation'''.

=Software HOWTOs=
===[[Install_XGL|XGL Guide]]===
* How do you '''enable XGL XOrg acceleration''' inside XOrg7? Well, read on .. this article covers the whole story.

=Hardware HOWTOs=
===[[Miscellaneous:USB camera howto|USB Camera HOWTO]]===
* This HOWTO explains how to connect and '''make use of your USB powered digital camera'''.

=Other HOWTOs=
===[[Installation:The_kernel_commandline_/dev_params_mini-HowTo|Bootloader options for handling /dev devices]]===
* This article explains how you can '''manipulate the way Lunar Linux handles devices''' at boot time using your favorite bootloader.

Template:Main Page:Misc

2007-02-11T18:06:13Z

Moe:

<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]]
* [[Install_XOrg7|XOrg7 Installation guide]]
* '''''[[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>

Module Guidelines

2006-08-27T14:59:27Z

Moe: /* CONFLICTS */ Forgot the star

__TOC__

== Generic ==

* Never use tabs. '''Use spaces''' instead.
* Use '''72 columns''' (or was it 79?) maximum width whenever possible (but always in [[DETAILS]]!).
* '''Respect the MAINTAINER''' value. Don't bump maintained modules unless you got the permission from the maintainer.

== DETAILS ==

* Use '''sha1:''' instead of ''md5:'' for SOURCE_VFY values.
* Don't insert your eMail address into the MAINTAINER field unless you are a Lunar developer.
* Prefer '''tar.bz2''' over '''tar.gz''' tarballs (as it saves space/traffic) and prefer '''tar.gz''' over '''zip''' (or '''rar''') packages.

== DEPENDS ==

* If dependency ''B'' implies dependency ''A'', only add '''depends B''' (or '''optional_depends B ...''', depending on the dependency type).

== CONFLICTS ==

* Remember to add a CONFLICTS to both modules that conflict with each other.

== CONFIGURE ==

== PRE_BUILD ==

== BUILD ==

* Don't install files after calling '''devoke_installwatch'''.

== POST_BUILD ==

* Don't install any files into the system.

== POST_INSTALL ==

* Don't install any files into the system.

== PRE_REMOVE ==

== POST_REMOVE ==

Module Guidelines

2006-08-27T14:58:32Z

Moe: /* CONFLICTS */ Both modules must have a CONFLICTS file

__TOC__

== Generic ==

* Never use tabs. '''Use spaces''' instead.
* Use '''72 columns''' (or was it 79?) maximum width whenever possible (but always in [[DETAILS]]!).
* '''Respect the MAINTAINER''' value. Don't bump maintained modules unless you got the permission from the maintainer.

== DETAILS ==

* Use '''sha1:''' instead of ''md5:'' for SOURCE_VFY values.
* Don't insert your eMail address into the MAINTAINER field unless you are a Lunar developer.
* Prefer '''tar.bz2''' over '''tar.gz''' tarballs (as it saves space/traffic) and prefer '''tar.gz''' over '''zip''' (or '''rar''') packages.

== DEPENDS ==

* If dependency ''B'' implies dependency ''A'', only add '''depends B''' (or '''optional_depends B ...''', depending on the dependency type).

== CONFLICTS ==

Remember to add a CONFLICTS to both modules that conflict with each other.

== CONFIGURE ==

== PRE_BUILD ==

== BUILD ==

* Don't install files after calling '''devoke_installwatch'''.

== POST_BUILD ==

* Don't install any files into the system.

== POST_INSTALL ==

* Don't install any files into the system.

== PRE_REMOVE ==

== POST_REMOVE ==

Install XOrg7

2006-08-25T11:51:00Z

Moe: NVIDIA now supports XOrg 7.1

=The path to XOrg7=

==Upgrading from XOrg 6.x==

Currently, the XOrg7 module needs you to do a few things manually if you upgrade from an earlier XOrg 6.x installation. You have to adhere to the following steps. If you do not listen to our advice then you're on your own.

*Remove the old XOrg
: <code>lrm XOrg</code>
Note: XOrg conflicts with XOrg7. Thus it would've been removed anyway. But we need to do more ...

*Backup the old /etc/X11 (with your old xorg.conf)
: <code>mv /etc/X11 /etc/X11.old</code>

*Remove the old XOrg installation remains
: <code>rm -fr /usr/X11R6</code>

*Remove some old symlinks
**<code>rm /usr/X11</code>
**<code>rm /usr/include/X11</code>
**<code>rm /usr/lib/X11</code>
**<code>rm /usr/include/GL</code>

==Installing XOrg 7.x ==
===Installing xorg-7.0===
As of 2006-06-19 XOrg7 was added to zbeta of moonbase... This means you can just lin XOrg7 to install xorg-7.0

===Installing xorg-7.1===

If you want to install xorg-7.1 you will need the fetch some modules from the development tree of moonbase:<br />
Fetch the [http://merlin.ugent.be/lunar/xorg7.1.tar.gz XOrg 7.1 tarball] from http://merlin.ugent.be/lunar/ for a snapshot of the experimental moonbase branch and copy the extracted files to your $MOONBASE/zlocal. The tarballs are updated at least once a day .. so you get all the latest changes.

Now you're all set for XOrg 7.1. You may now use the 'XOrg7' module to install XOrg 7.1:<br /><br />
<code>lin XOrg7</code>

XOrg-7.1 is needed if you want to mess with Xgl.

==Installation notes==

XOrg7 is installing to /usr by default and ''NOT'' to /usr/X11R7 or any other prefix inside /usr. The [http://www.pathname.com/fhs Filesystem Hierarchy Standard] does not allow that. All major linux distributions are following the FHS and have adjusted their builds accordingly:

*[http://lists.debian.org/debian-devel-announce/2006/04/msg00010.html Debian]
*[http://wiki.archlinux.org/index.php/Xorg7 Arch Linux]
*[http://gentoo-wiki.com/HOWTO_Modular_Xorg Gentoo]

You may however set an arbitary prefix for XOrg incase you do not want it to install to /usr. You may do so by running the following command:<br /><br />
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code><br><br />
The most commonly used prefix would be /usr/X11R7, however, some other prefix inside /opt is entirely possible.

The XOrg7 profile is going to create some symlinks on your system:<br /><br />
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default<br /></code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code><br /><br />
The X11R6 symlink is there for compatibility reasons. Many of the older and even some of the newer packages inside the moonbase have a hardcoded path pointing to /usr/X11R6 inside their source trees. Keeping the symlink prevents them from breaking apart.

==Missing modules from the XOrg 7.x modular tree==

Despite our best efforts to give you the whole XOrg 7.x modular tree as modules to install there are still many of them left untouched either because they are not important to run a full featured X environment or nobody had the time to add them yet. As always contribution are welcome and appreciated:

*x11-apps
**appres - list X application resource database
**lbxproxy - Low BandWidth X proxy
**luit - Convert terminal i/o from legacy encodings to UTF-8
**mkcfm - create summaries of CID font metric files
**oclock - round X clock
**proxymngr - proxy manager service
**scripts - run X command on another system via rsh
**sessreg - Register X sessions in system utmp/utmpx databases
**showfont - show information about X font from font server
**twm - simple window manager
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xdbedizzy - DBE sample
**xditview - display ditroff output
**xdm - list X application resource database
**xf86dga - known unto god
**xfd - display all the characters in an X font
**xfindproxy - locate proxy services
**xfontsel - point and click selection of X11 font names
**xfsinfo - X font server information utility
**xfwp - X Firewall Proxy
**xgc - X graphics demo
**xload - system load average display for X
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**xmag - magnify parts of the screen
**xphelloworld - Xprint sample applications
**xprehashprinterlist - Rehash list of Xprint printers
**xrx - "Broadway"
**xsetmode - set the mode for an X Input device
**xsetpointer - set an X Input device as the main pointer
**xsm - X Session Manager
**xstdcmap - X standard colormap utility
**xvidtune - video mode tuner for Xorg
*x11-data ==> COMPLETE
*x11-doc
**xorg-docs
**xorg-sgml-doctools
*x11-driver
**xf86-video-sunbw2
**xf86-video-suncg3
**xf86-video-suncg6
**xf86-video-suncg14
**xf86-video-sunffb
**xf86-video-sunleo
**xf86-video-suntcx
**xf86-video-tdfx
**xf86-video-tga
**xf86-video-trident
**xf86-video-tseng
*x11-extras ==> COMPLETE
*x11-font
**font-cronyx-cyrillic
**font-daewoo-misc
**font-dec-misc
**font-ibm-type1
**font-isas-misc
**font-jis-misc
**font-micro-misc
**font-misc-cyrillic
**font-misc-ethiopic
**font-misc-meltho
**font-mutt-misc
**font-schumacher-misc
**font-screen-cyrillic
**font-winitzki-cyrillic
*x11-lib
**libAppleWM - platform specific libraries: [MacOS]
**libWindowsWM - platform specific libraries: [Win32]
*x11-proto
**windowswmproto - platform specific protocol headers [Win32]
*x11-util
**lndir
*xserver ==> COMPLETE

Install XOrg7

2006-06-06T10:09:14Z

Moe: /* Annoyances */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

Currently, the XOrg7 module needs you to do a few things manually if you upgrade from an earlier XOrg 6.x installation. You have to adhere to the following steps. If you do not listen to our advice then you're on your own.

*Remove the old XOrg
: <code>lrm XOrg</code>
Note: XOrg conflicts with XOrg7. Thus it would've been removed anyway. But we need to do more ...

*Backup the old /etc/X11 (with your old xorg.conf)
: <code>mv /etc/X11 /etc/X11.old</code>

*Remove the old XOrg installation remains
: <code>rm -fr /usr/X11R6</code>

*Remove some old symlinks
**<code>rm /usr/X11</code>
**<code>rm /usr/include/X11</code>
**<code>rm /usr/lib/X11</code>
**<code>rm /usr/include/GL</code>

==Installing XOrg 7.x ==
First of all you need to add the 'XOrg7' module to the alias file so that it gets picked up by the lunar package management:<br />
Edit /var/lib/lunar/moonbase/aliases and add XOrg7 to the alias line that starts with %X. Put it right at the end.

Then you need to fetch the new XOrg 7.x modules:<br />
Fetch the [http://merlin.ugent.be/lunar/xorg7.0.tar.gz XOrg 7.0 tarball] or the [http://merlin.ugent.be/lunar/xorg7.1.tar.gz XOrg 7.1 tarball] from http://merlin.ugent.be/lunar/ and copy the extracted files to your $MOONBASE/zlocal. The tarballs are updated at least once a day .. so you get all the latest changes.

Now you're all set for XOrg 7.x. You may now use the 'XOrg7' module to install XOrg 7.x:<br /><br />
<code>lin XOrg7</code>

==Installation notes==

XOrg7 is installing to /usr by default and ''NOT'' to /usr/X11R7 or any other prefix inside /usr. The [http://www.pathname.com/fhs Filesystem Hierarchy Standard] does not allow that. All major linux distributions are following the FHS and have adjusted their builds accordingly:

*[http://lists.debian.org/debian-devel-announce/2006/04/msg00010.html Debian]
*[http://wiki.archlinux.org/index.php/Xorg7 Arch Linux]
*[http://gentoo-wiki.com/HOWTO_Modular_Xorg Gentoo]

You may however set an arbitary prefix for XOrg incase you do not want it to install to /usr. You may do so by running the following command:<br /><br />
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code><br><br />
The most commonly used prefix would be /usr/X11R7, however, some other prefix inside /opt is entirely possible.

The XOrg7 profile is going to create some symlinks on your system:<br /><br />
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default<br /></code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code><br /><br />
The X11R6 symlink is there for compatibility reasons. Many of the older and even some of the newer packages inside the moonbase have a hardcoded path pointing to /usr/X11R6 inside their source trees. Keeping the symlink prevents them from breaking apart.

==Annoyances==
The latest NVIDIA driver doesn't support the current [http://lists.freedesktop.org/archives/xorg/2006-May/015396.html ABI changes] in X11R7.1. This means you will be lacking text in some programs. Gtk+-2 programs do not show this problem (though firefox does). Solution? Some have suggested that turning off the XRendeR acceleration should work (so add: Option "RenderAccel" "false"). If that doesn't work you will have to use the opensource driver (xf86-video-nv). You may also want to read up on the issue [http://www.nvnews.net/vbulletin/showthread.php?t=70570 here] [http://www.nvnews.net/vbulletin/showthread.php?t=70476 and here].

==Missing modules from the XOrg 7.x modular tree==

Despite our best efforts to give you the whole XOrg 7.x modular tree as modules to install there are still many of them left untouched either because they are not important to run a full featured X environment or nobody had the time to add them yet. As always contribution are welcome and appreciated:

*x11-apps
**appres - list X application resource database
**lbxproxy - Low BandWidth X proxy
**luit - Convert terminal i/o from legacy encodings to UTF-8
**mkcfm - create summaries of CID font metric files
**oclock - round X clock
**proxymngr - proxy manager service
**scripts - run X command on another system via rsh
**sessreg - Register X sessions in system utmp/utmpx databases
**showfont - show information about X font from font server
**twm - simple window manager
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xdbedizzy - DBE sample
**xditview - display ditroff output
**xdm - list X application resource database
**xf86dga - known unto god
**xfd - display all the characters in an X font
**xfindproxy - locate proxy services
**xfontsel - point and click selection of X11 font names
**xfsinfo - X font server information utility
**xfwp - X Firewall Proxy
**xgc - X graphics demo
**xkbprint - print an XKB keyboard description
**xkill - kill a client by its X resource
**xload - system load average display for X
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**xmag - magnify parts of the screen
**xphelloworld - Xprint sample applications
**xprehashprinterlist - Rehash list of Xprint printers
**xrx - "Broadway"
**xsetmode - set the mode for an X Input device
**xsetpointer - set an X Input device as the main pointer
**xsm - X Session Manager
**xstdcmap - X standard colormap utility
**xvidtune - video mode tuner for Xorg
*x11-data
COMPLETE
*x11-doc
**xorg-docs
**xorg-sgml-doctools
*x11-driver
**xf86-video-sunbw2
**xf86-video-suncg3
**xf86-video-suncg6
**xf86-video-suncg14
**xf86-video-sunffb
**xf86-video-sunleo
**xf86-video-suntcx
**xf86-video-tdfx
**xf86-video-tga
**xf86-video-trident
**xf86-video-tseng
*x11-extras
COMPLETE
*x11-font
**font-cronyx-cyrillic
**font-daewoo-misc
**font-dec-misc
**font-ibm-type1
**font-isas-misc
**font-jis-misc
**font-micro-misc
**font-misc-cyrillic
**font-misc-ethiopic
**font-misc-meltho
**font-mutt-misc
**font-schumacher-misc
**font-screen-cyrillic
**font-winitzki-cyrillic
*x11-lib
**libAppleWM - platform specific libraries: [MacOS]
**libWindowsWM - platform specific libraries: [Win32]
*x11-proto
**windowswmproto - platform specific protocol headers [Win32]
*x11-util
**lndir
*xserver
COMPLETE

Install XOrg7

2006-06-06T10:05:55Z

Moe: Adjusted installing paragraph

=The path to XOrg7=

==Upgrading from XOrg 6.x==

Currently, the XOrg7 module needs you to do a few things manually if you upgrade from an earlier XOrg 6.x installation. You have to adhere to the following steps. If you do not listen to our advice then you're on your own.

*Remove the old XOrg
: <code>lrm XOrg</code>
Note: XOrg conflicts with XOrg7. Thus it would've been removed anyway. But we need to do more ...

*Backup the old /etc/X11 (with your old xorg.conf)
: <code>mv /etc/X11 /etc/X11.old</code>

*Remove the old XOrg installation remains
: <code>rm -fr /usr/X11R6</code>

*Remove some old symlinks
**<code>rm /usr/X11</code>
**<code>rm /usr/include/X11</code>
**<code>rm /usr/lib/X11</code>
**<code>rm /usr/include/GL</code>

==Installing XOrg 7.x ==
First of all you need to add the 'XOrg7' module to the alias file so that it gets picked up by the lunar package management:<br />
Edit /var/lib/lunar/moonbase/aliases and add XOrg7 to the alias line that starts with %X. Put it right at the end.

Then you need to fetch the new XOrg 7.x modules:<br />
Fetch the [http://merlin.ugent.be/lunar/xorg7.0.tar.gz XOrg 7.0 tarball] or the [http://merlin.ugent.be/lunar/xorg7.1.tar.gz XOrg 7.1 tarball] from http://merlin.ugent.be/lunar/ and copy the extracted files to your $MOONBASE/zlocal. The tarballs are updated at least once a day .. so you get all the latest changes.

Now you're all set for XOrg 7.x. You may now use the 'XOrg7' module to install XOrg 7.x:<br /><br />
<code>lin XOrg7</code>

==Installation notes==

XOrg7 is installing to /usr by default and ''NOT'' to /usr/X11R7 or any other prefix inside /usr. The [http://www.pathname.com/fhs Filesystem Hierarchy Standard] does not allow that. All major linux distributions are following the FHS and have adjusted their builds accordingly:

*[http://lists.debian.org/debian-devel-announce/2006/04/msg00010.html Debian]
*[http://wiki.archlinux.org/index.php/Xorg7 Arch Linux]
*[http://gentoo-wiki.com/HOWTO_Modular_Xorg Gentoo]

You may however set an arbitary prefix for XOrg incase you do not want it to install to /usr. You may do so by running the following command:<br /><br />
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code><br><br />
The most commonly used prefix would be /usr/X11R7, however, some other prefix inside /opt is entirely possible.

The XOrg7 profile is going to create some symlinks on your system:<br /><br />
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default<br /></code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code><br /><br />
The X11R6 symlink is there for compatibility reasons. Many of the older and even some of the newer packages inside the moonbase have a hardcoded path pointing to /usr/X11R6 inside their source trees. Keeping the symlink prevents them from breaking apart.

==Annoyances==
The latest NVIDIA driver doesn't support the current [http://lists.freedesktop.org/archives/xorg/2006-May/015396.html ABI changes] in X11R7.1. This means you will be lacking text in some programs. Gtk+-2 programs do not show this problem (though firefox does). Solution? Some have suggested that turning of the XRendeR acceleration should work (so add: Option "RenderAccel" "false"). If that doesn't work i guess you'll have to use the opensource driver (xf86-video-nv) [http://www.nvnews.net/vbulletin/showthread.php?t=70570 threads] [http://www.nvnews.net/vbulletin/showthread.php?t=70476 on nvidia forum].

==Missing modules from the XOrg 7.x modular tree==

Despite our best efforts to give you the whole XOrg 7.x modular tree as modules to install there are still many of them left untouched either because they are not important to run a full featured X environment or nobody had the time to add them yet. As always contribution are welcome and appreciated:

*x11-apps
**appres - list X application resource database
**lbxproxy - Low BandWidth X proxy
**luit - Convert terminal i/o from legacy encodings to UTF-8
**mkcfm - create summaries of CID font metric files
**oclock - round X clock
**proxymngr - proxy manager service
**scripts - run X command on another system via rsh
**sessreg - Register X sessions in system utmp/utmpx databases
**showfont - show information about X font from font server
**twm - simple window manager
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xdbedizzy - DBE sample
**xditview - display ditroff output
**xdm - list X application resource database
**xf86dga - known unto god
**xfd - display all the characters in an X font
**xfindproxy - locate proxy services
**xfontsel - point and click selection of X11 font names
**xfsinfo - X font server information utility
**xfwp - X Firewall Proxy
**xgc - X graphics demo
**xkbprint - print an XKB keyboard description
**xkill - kill a client by its X resource
**xload - system load average display for X
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**xmag - magnify parts of the screen
**xphelloworld - Xprint sample applications
**xprehashprinterlist - Rehash list of Xprint printers
**xrx - "Broadway"
**xsetmode - set the mode for an X Input device
**xsetpointer - set an X Input device as the main pointer
**xsm - X Session Manager
**xstdcmap - X standard colormap utility
**xvidtune - video mode tuner for Xorg
*x11-data
COMPLETE
*x11-doc
**xorg-docs
**xorg-sgml-doctools
*x11-driver
**xf86-video-sunbw2
**xf86-video-suncg3
**xf86-video-suncg6
**xf86-video-suncg14
**xf86-video-sunffb
**xf86-video-sunleo
**xf86-video-suntcx
**xf86-video-tdfx
**xf86-video-tga
**xf86-video-trident
**xf86-video-tseng
*x11-extras
COMPLETE
*x11-font
**font-cronyx-cyrillic
**font-daewoo-misc
**font-dec-misc
**font-ibm-type1
**font-isas-misc
**font-jis-misc
**font-micro-misc
**font-misc-cyrillic
**font-misc-ethiopic
**font-misc-meltho
**font-mutt-misc
**font-schumacher-misc
**font-screen-cyrillic
**font-winitzki-cyrillic
*x11-lib
**libAppleWM - platform specific libraries: [MacOS]
**libWindowsWM - platform specific libraries: [Win32]
*x11-proto
**windowswmproto - platform specific protocol headers [Win32]
*x11-util
**lndir
*xserver
COMPLETE

Install XOrg7

2006-05-29T21:50:02Z

Moe: hmhm .. some typo fixes

Install XOrg7

2006-05-23T18:08:09Z

Moe: Adjusted some details

User Reports:Moe

2006-05-07T19:12:46Z

Moe:

__TOC__

Okay, lets start with my system's specs:

* AMD 64bit CPU 3200+ (clocked at 2 Ghz); Venice Core; 128kb L1 cache
* [http://www.asrock.com/product/939Dual-SATA2.htm| ASRock 939Dual-SATA2 Motherboard]; ULi 1695 Chipset; Onboard sound/ethernet; USB 2.0
* Hitachi Deskstar 7K250 160GB SATA/300
* 512 MB DDR-400 PC3200 CL3 RAM
: '''''Updated:''' Upgraded to 2x1024 MB DDR-400 PC3200 CL3 RAM''
* Geforce 3 TI
: '''''Updated:''' Upgraded to XFX PCIe Geforce 7600GT Extreme Edition''
* LG DVD-RAM GSA-4163B
* Samsung BF930 19" TFT monitor
* Zoltrix Nightingale soundcard

==Goals==

First and foremost: I wanted a PC for playing Enemy Territory at the highest possible resolution. Given the above specs .. I sort of exceeded that goal a bit .. Secondly, I was fed up with my laptop's resolution. Hearing others bragging about their huge screens made me wheep now and then. And last but not least, I wanted this new PC to become as quiet as possible meaning '''QUIET'''.

==First steps==

I ordered almost all the parts at [http://www.cyberport.de Cyberport] a pretty reliable German online store for all the technical goodies you need these days. For the Geforce 3 TI, that one I bought through [http://www.ebay.de eBay] for 10 Euros. Also, I got the RAM at a cheap local store. Granted, they are just some no-name chinese bars but I have a three year warranty and the store is just about around the corner. For the quietness, after all one major goal, I also got my hands on a [http://www.zalman.co.kr/usa/product/view.asp?idx=149&code=013 Zalman VF-700Cu] for the Geforce, an Arctic Cooling Silencer 64 Ultra TC for the CPU and a [http://www.be-quiet.de/ be quiet!] Blackline 420W power supply.

==Harddrive and DVD drive==

Now, you might say: Hey, a harddrive's plug'n'play .. and I say: Hell no. While I plugged in the drive correctly (using the SATAII certified onboard port) the harddrive would show up as SATAII capable device in the BIOS but not under Linux. It was just running at half-speed (1.5Gbps). Of course, 1.5Gbps is more than enough .. but then I could've bought a regular SATA device. I wanted the full speed. So I [http://marc.theaimsgroup.com/?l=linux-ide&m=114696943812450&w=2 wrote to the linux-ide mailinglist] to find out wether it was a) the driver b) the board or c) just me. It turned out to be d) .. the harddrive itself.<br /><br />
Apparently, Hitachi forces each drive to run at a mere 1.5Gbps as otherwise the drive could malfunction of loose data if it was run at 3.0Gbps without the right controller present. Now, I think thats actually a pretty good default setting as most of today's computer users don't really know how to handle such stuff. And after all Hitachi even provides an excellent utility for their Deskstar line of harddrive .. and even boot CD images! I was taken by surprise and in an instant. Nice going Hitachi. Now the harddrive sports at 3.0Gbps (often called SATA-II/SATA2) and I even managed to enable other convenient features like accoustic- and power management. The drive has become noticably quieter.<br /><br />
The LG actually was plug'n'play. As it is a regular IDE/ATAPI device and I didn't have any jumpers around I just hung it on the primary IDE controller and booted up. No damage here. The drive was recognized correctly running in UDMA-2 mode under linux. Everything seemed alright. Until I tried to burn a CD recently.<br /><br />
The burning process started to become sluggish and slow and so I figured that there had to be something wrong with the IDE driver or the DMA settings. And indeed, the drive's DMA capabilities weren't enabled. Trying to enable them failed. So I sat stuck for about 20 minutes googling for an answer until I found out that my chipset (M5229) was supported by the kernel IDE driver labeled 'uli_15x3'. Just, there is absolutely no pointers to that. Neither does the version number of the driver correspond with my chipset's identification nor does the help text for that particular driver state that it supports the M5229. Someone's oughta fix that. After having the right driver compiled into the kernel it was no further doings needed to get a fully DMA accelerated DVD drive .. and therefore burn CDs at notable speeds without errors.

'''To be continued'''

User Reports:Moe

2006-05-07T19:06:04Z

Moe:

__TOC__

Okay, lets start with my system's specs:

* AMD 64bit CPU 3200+ (clocked at 2 Ghz); Venice Core; 128kb L1 cache
* [http://www.asrock.com/product/939Dual-SATA2.htm| ASRock 939Dual-SATA2 Motherboard]; ULi 1695 Chipset; Onboard sound/ethernet; USB 2.0
* Hitachi Deskstar 7K250 160GB SATA/300
* 512 MB DDR-400 PC3200 CL3 RAM
: '''''Updated:''' Upgraded to 2x1024 MB DDR-400 PC3200 CL3 RAM''
* Geforce 3 TI
: '''''Updated:''' Upgraded to XFX PCIe Geforce 7600GT Extreme Edition''
* LG DVD-RAM GSA-4163B
* Samsung BF930 19" TFT monitor
* Zoltrix Nightingale soundcard

==Goals==

First and foremost: I wanted a PC for playing Enemy Territory at the highest possible resolution. Given the above specs .. I sort of exceeded this goal a little .. Secondly, I was fed up with my laptop's resolution. Hearing others bragging about their huge screens made me wheep now and then. And last but not least, I wanted this new PC to become as quiet as possible meaning '''QUIET'''.

==First steps==

I ordered almost all the parts at [http://www.cyberport.de Cyberport] a pretty reliable German online store for all the technical goodies you need these days. For the Geforce 3 TI, that one I bought through [http://www.ebay.de eBay] for 10 Euros. Also, I got the RAM at a cheap local store. Granted, they are just some no-name chinese bars but I have a three year warranty and the store is just about around the corner. For the quietness, after all one major goal, I also got my hands on a [http://www.zalman.co.kr/usa/product/view.asp?idx=149&code=013 Zalman VF-700Cu] for the Geforce, an Arctic Cooling Silencer 64 Ultra TC for the CPU and a [http://www.be-quiet.de/ be quiet!] Blackline 420W power supply.

==Harddrive and DVD drive==

Now, you might say: Hey, a harddrive's plug'n'play .. and I say: Hell no. While I plugged in the drive correctly (using the SATAII certified onboard port) the harddrive would show up as SATAII capable device in the BIOS but not under Linux. It was just running at half-speed (1.5Gbps). Of course, 1.5Gbps is more than enough .. but then I could've bought a regular SATA device. I wanted the full speed. So I [http://marc.theaimsgroup.com/?l=linux-ide&m=114696943812450&w=2 wrote to the linux-ide mailinglist] to find out wether it was a) the driver b) the board or c) just me. It turned out to be d) .. the harddrive itself.<br /><br />
Apparently, Hitachi forces each drive to run at a mere 1.5Gbps as otherwise the drive could malfunction of loose data if it was run at 3.0Gbps without the right controller present. Now, I think thats actually a pretty good default setting as most of today's computer users don't really know how to handle such stuff. And after all Hitachi even provides an excellent utility for their Deskstar line of harddrive .. and even boot CD images! I was taken by surprise and in an instant. Nice going Hitachi. Now the harddrive sports at 3.0Gbps (often called SATA-II/SATA2) and I even managed to enable other convenient features like accoustic- and power management. The drive has become noticably quieter.<br /><br />
The LG actually was plug'n'play. As it is a regular IDE/ATAPI device and I didn't have any jumpers around I just hung it on the primary IDE controller and booted up. No damage here. The drive was recognized correctly running in UDMA-2 mode under linux. Everything seemed alright. Until I tried to burn a CD recently.<br /><br />
The burning process started to become sluggish and slow and so I figured that there had to be something wrong with the IDE driver or the DMA settings. And indeed, the drive's DMA capabilities weren't enabled. Trying to enable them failed. So I sat stuck for about 20 minutes googling for an answer until I found out that my chipset (M5229) was supported by the kernel IDE driver labeled 'uli_15x3'. Just, there is absolutely no pointers to that. Neither does the version number of the driver correspond with my chipset's identification nor does the help text for that particular driver state that it supports the M5229. Someone's oughta fix that. After having the right driver compiled into the kernel it was no further doings needed to get a fully DMA accelerated DVD drive .. and therefore burn CDs at notable speeds without errors.

'''To be continued'''

User Reports:Moe

2006-05-07T15:41:17Z

Moe: Add hitachi to summary; Article about Hitachi and LG

__TOC__

Okay, lets start with my system's specs:

* AMD 64bit CPU 3200+ (clocked at 2 Ghz); Venice Core; 128kb L1 cache
* [http://www.asrock.com/product/939Dual-SATA2.htm| ASRock 939Dual-SATA2 Motherboard]; ULi 1695 Chipset; Onboard sound/ethernet; USB 2.0
* 512 MB DDR-400 PC3200 CL3 RAM
* Hitachi Deskstar 7K250 160GB SATA/300
: '''''Updated:''' Upgraded to 2x1024 MB DDR-400 PC3200 CL3 RAM''
* Geforce 3 TI
: '''''Updated:''' Upgraded to XFX PCIe Geforce 7600GT Extreme Edition''
* LG DVD-RAM GSA-4163B
* Samsung BF930 19" TFT monitor
* Zoltrix Nightingale soundcard

==Goals==

First and foremost: I wanted a PC for playing Enemy Territory at the highest possible resolution. Given the above specs .. I sort of exceeded this goal a little .. Secondly, I was fed up with my laptop's resolution. Hearing others bragging about their huge screens made me wheep now and then. And last but not least, I wanted this new PC to become as quiet as possible meaning '''QUIET'''.

==First steps==

I ordered almost all the parts at [http://www.cyberport.de Cyberport] a pretty reliable German online store for all the technical goodies you need these days. For the Geforce 3 TI, that one I bought through [http://www.ebay.de eBay] for 10 Euros. Also, I got the RAM at a cheap local store. Granted, they are just some no-name chinese bars but I have a three year warranty and the store is just about around the corner. For the quietness, after all one major goal, I also got my hands on a [http://www.zalman.co.kr/usa/product/view.asp?idx=149&code=013 Zalman VF-700Cu] for the Geforce, an Arctic Cooling Silencer 64 Ultra TC for the CPU and a [http://www.be-quiet.de/ be quiet!] Blackline 420W power supply.

==Harddrive and DVD drive==

Now, you might say: Hey, a harddrive's plug'n'play .. and I say: Hell no. While I plugged in the drive correctly (using the SATAII certified onboard port) the harddrive would show up as SATAII capable device in the BIOS but not under Linux. It was just running at half-speed (1.5Gbps). Of course, 1.5Gbps is more than enough .. but then I could've bought a regular SATA device. I wanted the full speed. So I [http://marc.theaimsgroup.com/?l=linux-ide&m=114696943812450&w=2 wrote to the linux-ide mailinglist] to find out wether it was a) the driver b) the board or c) just me. It turned out to be d) .. the harddrive itself.<br /><br />
Apparently, Hitachi forces each drive to run at a mere 1.5Gbps as otherwise the drive could malfunction of loose data if it was run at 3.0Gbps without the right controller present. Now, I think thats actually a pretty good default setting as most of today's computer users don't really know how to handle such stuff. And after all Hitachi even provides an excellent utility for their Deskstar line of harddrive .. and even boot CD images! I was taken by surprise and in an instant. Nice going Hitachi. Now the harddrive sports at 3.0Gbps (often called SATA-II/SATA2) and I even managed to enable other convenient features like accoustic- and power management. The drive has become noticably quieter.<br /><br />
The LG actually was plug'n'play. As it is a regular IDE/ATAPI device and I didn't have any jumpers around I just hung it on the primary IDE controller and booted up. No damage here. The drive was recognized correctly running in UDMA-2 mode under linux. Everything seemed alright. Until I tried to burn a CD recently.<br /><br />
The burning process started to become sluggish and slow and so I figured that there had to be something wrong with the IDE driver or the DMA settings. And indeed, the drive's DMA capabilities weren't enabled. Trying to enable them failed. So I sat stuck for about 20 minutes googling for an answer until I found out that my chipset (M5229) was supported by the kernel IDE driver labeled 'uli_15x3'. Just, there is absolutely no pointers to that. Neither does the version number of the driver correspond with my chipset's identification nor does the help text for that particular driver state that it supports the M5229. Someone's oughta fix that. After having the right driver compiled into the kernel it was no further doings needed to get a fully DMA accelerated DVD drive .. and therefore burn CDs at notable speeds without errors.

'''To be continued'''

User Reports:Moe

2006-04-30T12:41:53Z

Moe: Add the first two paragraphs

User Reports

2006-04-30T10:21:09Z

Moe:

This site holds reports of users about their success (or failure) regarding Lunar Linux or parts of it. We encourage every user to write down their system's specs and how they got Lunar Linux to work on their machines. It should be regarded as a helpful pool of information for everyone.

__TOC__

===Engelsman===

''Created on the 3rd of September 2005 by [[User:Engelsman|Engelsmann]]''

I started using Unix V7 on a PDP-11/70 back in 1983, even modifying some existing kernel drivers for the [http://en.wikipedia.org/wiki/Cambridge_Ring Cambridge Ring] local area network. After that I dabbled in system administration of various Sun and Apollo systems until 1991, and HP boxes up until 2000, but my main task has always been application software development, nothing on the hardware or kernel side. Since 2000 we've had dedicated system administrators at work. We had switched from NCD X-terminals over to Linux desktops (first RedHat, but then Lunar) and I realized that what little I knew had become well out of date. I installed RedHat on an old 90MHz PC at home more than five years ago, but without a LAN or modem connection it was too difficult to keep up to date, I lost interest, and that died. Since then I've had an itch to develop a spiffy [http://www.fltk.org FLTK] user interace for some old command line tools using Cygwin/Mingw on a WinXP laptop (with modem) but the machine is (a) painfully slow, and (b) painfully Windows. The time had come to get some new hardware, install an operating system that doesn't thwart you at every turn, and set up a programming environment of my own choice.<br /><br />
[[User Talk:Engelsman|Read on]] to find out more ...

===Moe===

''Created on the 30th of April 2006 by [mailto:moe@lunar-linux.org moe@lunar-linux.org]''

In April 2006 I bought a new computer and of course I ment to throw Lunar on it. I hadn't done a complete new installation since a couple of years (I think the last time Lunar has been at version 1.3.something). I bought an AMD 3200+ processor along with 512GB RAM, got a Geforce 3 Ti from eBay and a ASRock mainboard featuring a ULi 1695 939-socket based chipset.<br /><br />
[[User Reports:Moe|Read on]] to find out more ...

User Reports

2006-04-30T10:13:09Z

Moe:

Template:Main Page:Misc

2006-04-30T09:58:23Z

Moe: Be more consistent

<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-30T09:57:25Z

Moe: Take out the 2.6.x Howto -> obsolete; Add User reports section

<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>

Module Basics

2006-03-28T09:29:13Z

Moe: 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

Template:Main Page:Languages

2005-12-13T23:14:05Z

Moe: Reverted edit of 202.58.85.2, changed back to last version by Moe

<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#Request|Request a Language]]
</div>

Template:Main Page:Languages

2005-12-02T09:13:37Z

Moe: Remove ads here (disgusting!)

Lunar Linux

2005-02-01T22:41:48Z

Moe: /* 3rd Party Websites */

<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
==[[Lunar Linux/Docs|Documentation]]==
===General===
* [[Lunar Linux/Frequently Asked Questions|Frequently Asked Questions]]
===Installation===
* Placeholder
===Modules===
* Placeholder
===Other===
* [irc://irc.freenode.net/lunar #lunar] on [http://freenode.net/ Freenode.net]
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
==[[Lunar Linux/Misc|Other Information]]==
===Howto Articles===
* Placeholder
===Reviews===
* [http://www.bluefish.se/aquarium/lunar.html Review of Lunar Linux]<br />
• A review of Lunar Linux by Göran Krampe at [http://www.bluefish.se/index.html bluefish.se]

===3rd Party Websites===
* [http://lunar-linux.interhact.net/ Lunar Linux Non-Free Modules]<br />
• Non-Free Modules repository website run by a Lunar developer
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">

==[[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]] architecture, but support for [[wikipedia:Sparc|Sparc]] and [[wikipedia:IA-64|IA-64]] is being worked on.

Other source based Linux distributions include [[wikipedia:Gentoo Linux|Gentoo Linux]], [[wikipedia:Linux From Scratch|Linux From Scratch]] and [[wikipedia:Onebase Linux|Onebase Linux]]. <br>
Lunar Linux itself [[wikipedia:Fork (software)|forked]] from [[wikipedia:Sorcerer GNU/Linux|Sorcerer GNU/Linux]].
</td>
</tr></table>

Lunar Linux

2005-02-01T22:41:12Z

Moe: /* Reviews */

<table style="width: 100%; background: transparent; border-spacing: 4px;"><tr>
<td style="width: 50%; padding: 3px; background: #eef; border: 1px solid #00f; vertical-align: top;">
==[[Lunar Linux/Docs|Documentation]]==
===General===
* [[Lunar Linux/Frequently Asked Questions|Frequently Asked Questions]]
===Installation===
* Placeholder
===Modules===
* Placeholder
===Other===
* [irc://irc.freenode.net/lunar #lunar] on [http://freenode.net/ Freenode.net]
</td>
<td style="width: 50%; padding: 3px; background: #efe; border: 1px solid #080; vertical-align: top;">
==[[Lunar Linux/Misc|Other Information]]==
===Howto Articles===
* Placeholder
===Reviews===
* [http://www.bluefish.se/aquarium/lunar.html Review of Lunar Linux]<br />
• A review of Lunar Linux by Göran Krampe at [http://www.bluefish.se/index.html bluefish.se]

===3rd Party Websites===
* [http://lunar-linux.interhact.net/ Lunar Linux Non-Free Modules] • Non-Free Modules repository website run by a Lunar developer
</td>
</tr><tr>
<td colspan="2" style="padding: 3px; background: #fee; border: 1px solid #f00; vertical-align: top;">
==[[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]] architecture, but support for [[wikipedia:Sparc|Sparc]] and [[wikipedia:IA-64|IA-64]] is being worked on.

Other source based Linux distributions include [[wikipedia:Gentoo Linux|Gentoo Linux]], [[wikipedia:Linux From Scratch|Linux From Scratch]] and [[wikipedia:Onebase Linux|Onebase Linux]]. <br>
Lunar Linux itself [[wikipedia:Fork (software)|forked]] from [[wikipedia:Sorcerer GNU/Linux|Sorcerer GNU/Linux]].
</td>
</tr></table>

Lunar Linux

2005-01-30T12:19:20Z

Moe:

==Welcome to the Lunar Linux wiki==
{| border="0" width="70%"
|The [http://lunar-linux.org Lunar Linux] [http://wiki.lunar-linux.org wiki] is ment to be a way for users to contribute their knowledge <u>about</u> and experience <u>with</u> [http://lunar-linux.org Lunar Linux].
|}

Lunar Linux

2005-01-29T22:57:55Z

Moe:

Lunar Linux

2005-01-29T22:57:41Z

Moe:

Lunar Linux

2005-01-29T22:56:29Z

Moe:

==Welcome to the Lunar Linux wiki==
{| border="0" width="70%"
|The [http://lunar-linux.org Lunar Linux] [http://wiki.lunar-linux.org wiki] is ment to be a way for users to contribute their knowledge about and experience with [http://lunar-linux.org Lunar Linux].
|}
===Go Docs!===
[[Lunar Linux:Documentation|Lunar Linux Documentations]]

Lunar Linux

2005-01-29T20:54:56Z

Moe:

==Welcome to the Lunar Linux wiki==
{| border="0" width="70%"
|The [http://lunar-linux.org Lunar Linux] [http://wiki.lunar-linux.org wiki] is ment to be a way for users to contribute their knowledge about and report about their experience with [http://lunar-linux.org Lunar Linux].
|}
===Go Docs!===
[[Lunar Linux:Documentation|Lunar Linux Documentations]]

Lunar Linux

2005-01-29T20:53:39Z

Moe:

==Welcome to the Lunar Linux wiki==
{| border="0" width="70%"
|The [http://lunar-linux.org Lunar Linux] [http://wiki.lunar-linux.org wiki] is ment to be a way for users to contribute their knowledge about and report about their experience with [http://lunar-linux.org Lunar Linux]
|}
===Go Docs!===
[[Lunar Linux:Documentation|Lunar Linux Documentations]]

Lunar Linux

2005-01-29T20:31:58Z

Moe:

Still a placeholder .. just trying something.
==Go Docs!==
[[Lunar Linux:Documentation|Lunar Linux Documentations]]