Lunar Linux - User contributions [en]

User talk:Pacmanlives

2010-08-22T20:09:01Z

Pacmanlives: /* WIKI Edits: */

== TODO LIST: ==

Things to add/ change on the website.

Meet the dev's: Pic, Where they are from what they do for the project , hobbies , how long they have been using linux/with the project.

Add some new current screenshots. Current ones are old and outdated need to show that we are still relevant.

News section to the website like major package updates kde/gnome/xfce, ect. wordpress or something like that to make changes easier

http://www.lunar-linux.org/index.php/en/information.html fix.

<s> Modules are showing twice. Found the code here “<li class="item74"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>

<li class="item84"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>”
</s>

Upgrade to some of the code so that way when you hover over the link it shows the sub menu.

== WIKI Edits: ==

How to's to get kde4, gnome, xfce, etc. installed. Add guides for stuff like Multimedia, Cool apps that you uses everyday.

<s> http://wiki.lunar-linux.org/index.php/Install_XOrg7

Remove the Xorg 6 section as it is old.

Add driver how to install Nvidia/Ati drivers. linked? </s>

http://wiki.lunar-linux.org/index.php/Install_fglrx ATI install still current?

<s> http://wiki.lunar-linux.org/index.php/Lunar_Linux

Remove 3rd party link , as it is dead. Dont think this is current in the about section "Currently, Lunar only supports the x86 and x86-64 architectures, but support for Sparc, PPC, and Alpha is being worked on."</s> Completed by engelsman

Add info to tools suchs as http://wiki.lunar-linux.org/index.php/Tools:lunar man page/ screen shots of what lunar looks like. http://wiki.lunar-linux.org/index.php/Tools:lvu is a good example of what we need to do for all the tools.

http://wiki.lunar-linux.org/index.php/Lunar_Linux:Installation

NEEDS TO BE UPDATED!

Tools:lvu.1.manpage

2010-08-22T17:03:24Z

Pacmanlives:

=== Disclaimer: ===

This page may not be in synchronization with the man pages available on a Lunar-Linux system.

The initial version was a cut'n'paste from the man command, which produces weird wiki formatting.

----

LVU(1) LUNAR LVU(1)

NAME
lvu - query/view lunar package management information

SYNOPSIS
lvu alien|leafs|orphans|pam

lvu cd|what|where|website|sources|urls|maintainer|version <module>

lvu compile|compiler|links|install|sum|md5sum <module>

lvu export|import [snapshot]

lvu moonbase|html|updatelog|activity

lvu search "phrase"

lvu service port|acronym

lvu newer|older <yyyymmdd>

lvu from <path/file>

lvu installed [module]

lvu conflicts

lvu held|exiled|expired

lvu section [section]

lvu voyeur [delay or module]

lvu depends <module>

lvu tree <module>
lvu stree <module>

lvu eert <module>

lvu size [module]

lvu new|submit|edit|unedit [module]

lvu $MODULE_SCRIPT <module>

COPYRIGHT
lvu(1) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by
previous authors 2001-2002 lvu(1) also contains material which is Copyright
(C) Lunar-Linux team.

DESCRIPTION
lvu is part of the lunar source-based package management suite. It is a gen-
eral purpose command-line tool for displaying package logs, version informa-
tion, checking for installed packages, checksums, message digests, main-
tainer information, package URL information, displaying new packages,
untracked files, sections, searching for files that are installed, finding
when modules were created and packages in the software catalogue. It can
even take and retrieve snapshots of currently installed packages for easy
duplication.

OPTIONS
alien - find and display all files which are not currently tracked by the lunar package management system

leafs - displays installed modules that have no explicit dependencies on them

orphans - displays installed modules that are missing required dependencies

pam - display modules installed that are pam aware

cd <module> - changes current directory to the given module and execs a new shell

what <module> - view the long package description

where <module> - display the section a module belongs to

website <module> - display the URL for the specified module

sources <module> - list all source files contained in a module

urls <module> - list all URLs for a module

maintainer <module> - display the email address of the person currently responsible for maintaining a specified module

version <module> - display version of module in moonbase

compile <module> - show the compiler output generated when the module was built

compiler <module> - display the version of compiler used for creating the ELF files in modules

links <module> - display the modules that this module's ELF binary files actually links to

install <module> - used to determine what files were installed by a module and where those files are located

conflicts - display modules with conflicting files

held - display held modules

exiled - display exiled modules

expired - display a list of modules which will be updated by a `lunar renew`

sum <module> - print CRC checksums for modules(s). If no module is given it defaults to all.

md5sum <module> - print module MD5 message digests (fingerprints). If no module is given it default to all

export - take a snapshot of all modules and configuration currently installed

import snapshot - restore the snapshot from a previous lvu export command (see the export option)

moonbase - prints the entire moonbase

html - prints the entire moonbase in a nice html format

updatelog - view summary log of previous lunar update

activity - view the main lunar activity log

search "phrase" - Searches modules long descriptions for phrase

service port|acronym - displays modules that provide the given service port|acronym

newer date - print packages that are newer than a specified date. the date must be specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

older date - print packages that are older than a specified date. the date must be specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

from <path/><file> - find out what module has <path>/file installed

installed <module> view all installed packages and corresponding version numbers or check to see whether a particular package is installed
and if it is installed display its version number

section <module> - view a list of all sections in the software catalogue or display a list of packages from a specific section

size <module> - display the size of a given module or all your installed modules in KB

voyeur <module> - start looking at what lin is compiling at the moment and outputs it. A module can be optionally specified.

depends <module> - displays the modules that explicitly or recursively depend on this module.

tree <module> - displays a tree of the module's dependencies.

stree <module> - displays a shorter form of the tree of the module's dependencies.

eert <module> - displays a tree of the module's reverse dependencies.

new <module> - Attempt to create a module DETAILS file from scratch using cut-n-paste data from the user. Very dirty method to get a module started by just
having 4 pieces of information handy: download url, descriptions and name

edit <module> - Copy an existing module to zlocal so it can be edited. Turn on ZLOCAL_OVERRIDES to make sure your edited module gets used instead of the
default module.

unedit <module> - Discards your 'edit'ed zlocal module. Works the same as removing it.

submit <module> - Submit a module to the lunar module submission list/mail alias. Please only submit tested changes.

$MODULE_SCRIPT <module> - replace $MODULE_SCRIPT with any of the following DETAILS | CONFIGURE | CONFLICTS | PRE_BUILD | BUILD | POST_BUILD |
POST_INSTALL | POST_REMOVE to show module scripts for the module

AUTHOR
Original version written by Brian Peterson

Modified by Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Edited and new functions added by Chuck Mead 05/21/2002

Updated again by Terry Chan 08/08/2003

Updated by Stefan Wold 06/07/2009

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
lunar(8), lin(8), lrm(8), lget(8), moonbase(5)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux June 2009 LVU(1)

Tools:lvu.1.manpage

2010-08-22T16:54:34Z

Pacmanlives:

=== Disclaimer: ===

This page may not be in synchronization with the man pages available on a Lunar-Linux system.

The initial version was a cut'n'paste from the man command, which produces weird wiki formatting.

----

LVU(1) LUNAR LVU(1)

NAME
lvu - query/view lunar package management information

SYNOPSIS
lvu alien|leafs|orphans|pam

lvu cd|what|where|website|sources|urls|maintainer|version <module>

lvu compile|compiler|links|install|sum|md5sum <module>

lvu export|import [snapshot]

lvu moonbase|html|updatelog|activity

lvu search "phrase"

lvu service port|acronym

lvu newer|older <yyyymmdd>

lvu from <path/file>

lvu installed [module]

lvu conflicts

lvu held|exiled|expired

lvu section [section]

lvu voyeur [delay or module]

lvu depends <module>

lvu tree <module>
lvu stree <module>

lvu eert <module>

lvu size [module]

lvu new|submit|edit|unedit [module]

lvu $MODULE_SCRIPT <module>

COPYRIGHT
lvu(1) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by
previous authors 2001-2002 lvu(1) also contains material which is Copyright
(C) Lunar-Linux team.

DESCRIPTION
lvu is part of the lunar source-based package management suite. It is a gen-
eral purpose command-line tool for displaying package logs, version informa-
tion, checking for installed packages, checksums, message digests, main-
tainer information, package URL information, displaying new packages,
untracked files, sections, searching for files that are installed, finding
when modules were created and packages in the software catalogue. It can
even take and retrieve snapshots of currently installed packages for easy
duplication.

OPTIONS
alien - find and display all files which are not currently tracked by the lunar package management system

leafs - displays installed modules that have no explicit dependencies on them

orphans - displays installed modules that are missing required dependencies

pam - display modules installed that are pam aware

cd <module> - changes current directory to the given module and execs a new shell

what <module> - view the long package description

where <module> - display the section a module belongs to

website <module> - display the URL for the specified module

sources <module> - list all source files contained in a module

urls <module> - list all URLs for a module

maintainer <module> - display the email address of the person currently responsible for maintaining a specified module

version <module> - display version of module in moonbase

compile <module> - show the compiler output generated when the module was built

compiler <module> - display the version of compiler used for creating the ELF files in modules

links <module> - display the modules that this module's ELF binary files actually links to

install <module> - used to determine what files were installed by a module and where those files are located

conflicts - display modules with conflicting files

held - display held modules

exiled - display exiled modules

expired - display a list of modules which will be updated by a `lunar renew`

sum <module> - print CRC checksums for modules(s). If no module is given it defaults to all.

md5sum <module> - print module MD5 message digests (fingerprints). If no module is given it default to all

export - take a snapshot of all modules and configuration currently installed

import snapshot - restore the snapshot from a previous lvu export command (see the export option)

moonbase - prints the entire moonbase

html - prints the entire moonbase in a nice html format

updatelog - view summary log of previous lunar update

activity - view the main lunar activity log

search "phrase" - Searches modules long descriptions for phrase

service port|acronym - displays modules that provide the given service port|acronym

newer date - print packages that are newer than a specified date. the date must be
specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

older date - print packages that are older than a specified date. the date must be
specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

from <path/><file> - find out what module has <path>/file installed

installed <module> view all installed packages and corresponding version numbers or
check to see whether a particular package is installed and if it is
installed display its version number

section <module> - view a list of all sections in the software catalogue or display a list of packages from a specific section

size <module> - display the size of a given module or all your installed modules in KB

voyeur <module> - start looking at what lin is compiling at the moment and outputs it. A module can be optionally specified.

depends <module> - displays the modules that explicitly or recursively depend on this module.

tree <module> - displays a tree of the module's dependencies.

stree <module> - displays a shorter form of the tree of the module's dependencies.

eert <module> - displays a tree of the module's reverse dependencies.

new <module> - Attempt to create a module DETAILS file from scratch using cut-n-paste data from the user. Very dirty method to get a module started by just having 4 pieces of information handy: download url, descriptions and name

edit <module> - Copy an existing module to zlocal so it can be edited. Turn on ZLOCAL_OVERRIDES to make sure your edited module gets used instead of the default module.

unedit <module> - Discards your 'edit'ed zlocal module. Works the same as removing it.

submit <module> - Submit a module to the lunar module submission list/mail alias. Please only submit tested changes.

$MODULE_SCRIPT <module> - replace $MODULE_SCRIPT with any of the following DETAILS | CONFIGURE | CONFLICTS | PRE_BUILD | BUILD | POST_BUILD | POST_INSTALL | POST_REMOVE to show module scripts for the module

AUTHOR
Original version written by Brian Peterson

Modified by Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Edited and new functions added by Chuck Mead 05/21/2002

Updated again by Terry Chan 08/08/2003

Updated by Stefan Wold 06/07/2009

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
lunar(8), lin(8), lrm(8), lget(8), moonbase(5)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux June 2009 LVU(1)

Tools:lin.8.manpage

2010-08-22T16:40:53Z

Pacmanlives:

=== Disclaimer: ===

This page may not be in synchronization with the man pages available on a Lunar-Linux system.

The initial version was a cut'n'paste from the man command, which produces weird wiki formatting.

----

LIN(8) LUNAR LIN(8)

NAME: lin - Lunar install software modules

SYNOPSIS
lin [options] [package1[/version]] ... [package2[/version]] ...

COPYRIGHT
lin(8) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by
previous authors 2001-2002

EXAMPLE
To install emacs type:

lin emacs

DESCRIPTION
lin is part of the Lunar source-code package management suite. It is a com-
mand-line tool for automatically retrieving, unpacking, compiling,
installing, and tracking software installations.

OPTIONS
-c, --compile Compiles module even if there is a compile cache in /var/cache/lunar.

-d, --debug Enables debug messages, very useful when emailing a bug report.

--deps Configures the modules and determines their dependencies, but they
are not compiled or installed.

-f, --from directory Specify an alternate directory to search for source code tarballs. An
alternative to /var/spool/lunar.

-h, --help Outputs short help.

-p, --prob Only lin if the module was not previously installed.

-r, --reconfigure Select new configuration and dependencies for modules.

--opts (configure flags) Add arbitrary options to the configure stage of the module. The
options are saved for future upgrades but will be erased by using
"-r".

-R, --resurrect Reinstalls a module which has been removed but still has the compiled
version available.

-w, --want (version number) Try to install a different version than the current one in moonbase.
Integrity checking is turned off. Success not guaranteed.

-s, --silent Decreases the level of message output.

-v, --verbose Increases the level of message output.

FILES
All files can be edited by hand, but its easier to edit them with lunar.

/etc/lunar/config Configuration options.

/etc/lunar/mirrors Mirror information.

/etc/lunar/local/* Local settings.

/etc/lunar/local/config Various local settings and compiler optimization parameters (select
with lunar).

/etc/lunar/local/depends/* Dependency and configuration information for modules.

/var/lib/lunar/functions/*.lunar Contains functions used by lin.

ENVIRONMENT
The following settings can be altered in /etc/lunar/local/config It is easier, faster and less error prone to edit them with lunar.

GNU_URL - The GNU Mirror (default: ftp.gnu.org).

KERNEL_URL - The kernel mirror (default: ftp.kernel.org).

XFREE86_URL - The xfree86 mirror (default: ftp.xfree86.org).

GNOME_URL - The GNOME mirror (default: ftp.gnome.org).

KDE_URL - The KDE mirror (default: ftp.kde.org).

SFORGE_URL - The Sourceforge mirror. (default: none).

PATCH_URL - The default patch mirror.(default: download.lunar-linux.org/lunar/patches).

LRESORT_URL - The default lunar mirror. If all else fails go here! (default: download.lunar-linux.org/lunar/cache)

MOONBASE_URL - The lunar moonbase mirrors. (default: download.lunar-linux.org/lunar/).

color - If set to yes lin outputs nice colour. Green for messages, gray for compiling, yellow for questions, and red for errors.

PROMPT_DELAY - The delay in seconds that lin pauses when waiting for responses from
you.

MAIL_REPORTS - If set to yes, installation logs will be mailed to the admin upon a
successful compile. Compile logs will be mailed instead upon a failed
compilation.

ADMIN'S_EMAIL - The mailbox where the reports will be mailed. The admin's email
address.

PRESERVE - When set to yes, configuration files that have been edited will not
get deleted when the module is re-installed

SOUND If set to yes then sounds will be enabled if the lunar-sound module
is installed

SUSTAIN
When set to yes this disallows removing of modules that would cause
terrible malfunctions. eg glibc, gcc, bash, to name some obvious
ones.
MOONBASE_URL
The lunar moonbase mirrors. (default: down-
load.lunar-linux.org/lunar/).

color - If set to yes lin outputs nice colour. Green for messages, gray for
compiling, yellow for questions, and red for errors.

PROMPT_DELAY - The delay in seconds that lin pauses when waiting for responses from
you.

MAIL_REPORTS - If set to yes, installation logs will be mailed to the admin upon a
successful compile. Compile logs will be mailed instead upon a failed
compilation.

ADMIN'S_EMAIL - The mailbox where the reports will be mailed. The admin's email
address.

PRESERVE - When set to yes, configuration files that have been edited will not
get deleted when the module is re-installed

SOUND - If set to yes then sounds will be enabled if the lunar-sound module
is installed

SUSTAIN - When set to yes this disallows removing of modules that would cause
terrible malfunctions. eg glibc, gcc, bash, to name some obvious
ones.

VIEW_REPORTS - If set to yes then you will be prompted whether to view reports
before and after installation.

VOYEUR - If set to yes then compiler output will be displayed in real time.

REAP - Deletes files when removing.

AUTOFIX - If set to yes whenever a library is updated all packages that depend
on that library will be rebuilt. See FIND_CHECK, MD5SUM_CHECK,
LDD_CHECK, SYM_CHECK for autofix settings.

FIND_CHECK - See the -f options above for explanations of these.

ADVANCED USAGE
Using source code tarballs from an alternate location.

lin --from /root/spool/lunar emacs Unless the -from option is speci-
fied lin will always check the /var/spool/lunar directory first to
see if the package exists. If the package does not exist it downloads
the package via the Internet.

AUTHOR
Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Updated by Chuck Mead 07/17/2003

Updated by Terry Chan 08/08/2003

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
lunar(8), lrm(8), lvu(1), lget(8), moonbase(5)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LIN(8)

Tools:lunar.8.manpage

2010-08-22T15:10:03Z

Pacmanlives:

=== Disclaimer: ===

This page may not be in synchronization with the man pages available on a Lunar-Linux system.

The initial version was a cut'n'paste from the man command, which produces weird wiki formatting.

----

LUNAR(8) Lunar LUNAR(8)

NAME
lunar - menu-driven software package management utility

SYNTAX
lunar -d|--debug|-h|--help|-v|--verbose

lunar [prune|renew|update|rebuild|optimize|fix|nofix|fixdepends|
resurrect|install|remove|hold|unhold|exile|unexile]

COPYRIGHT
lunar(8) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by previous authors 2001-2002

DESCRIPTION
lunar is an easy-to-use menu-driven (dialog-based) interface to the Lunar source-based package manage-
ment system.

OPTIONS
lunar without options will start the menu-driven package management utility.

-d, --debug enables debug messages, very useful when emailing a bug report

-h, --help
outputs short help

-v, --verbose
increases the level of message output

prune - Removes all old source code and old backups. Since the number of sources on the system grows
steadily on a running system, you will need to clean some of the kept copies of sources and com-
pile caches. The source code from previous versions are kept so that the packages can be rolled
back to older versions. This does not delete sources that are up to date, but not installed.

renew - Update all packages without fetching a fresh moonbase first. Does not run prune or autofix.

update - Fetches a new moonbase, updates all packages and runs (optionally) a prune and autofix.

rebuild - automatically rebuilds all installed software packages. This option is non-interactive and does
not start up the menu-driven interface. It is suitable for use in cron jobs and is useful for
rebuilding distributed binaries from source.

optimize - jump straight into the compiler optimizations menu.

fix - Checks and fixs all modules and internal state of lunar. Four methods are available. The methods
can be toggled using lunar->Option->Integrity Checking. A fix is automatically issued afer a
lunar update.

Find Check - Discovers missing binary executables, libraries and header files.

MD5 Sum - Discovers modified executables and libraries.

Ldd Check - Discovers Broken executables and libraries.

Sym Check - Discovers mis-owned symbolic links to files.

nofix - Check but do not fix modules and internal state.

fixdepends - Check and fix the dependency database of lunar. Reconstructs the depends database without
recompiling modules. This might help if your depends database is missing or corrupted.

resurrect - Reinstalls a module which has been removed but still has the compiled version available.

install - Installs a module.

remove - Removes a module.

hold - Places a module on hold so it cannot be built/rebuilt.

unhold - Removes a module from hold status so it can be built/rebuilt.

exile -Prevents a module from being installed or resurrected. Perhaps because you've installed a cus-
tomized module.

unexile - Removes a module from exiled status.

REQUIREMENTS
lunar requires a connection to the Internet

Bash version 2 or higher

Dialog version 0.9a or higher

Linux kernel version 2.4.x or higher.

NOTES
Options on the Package Menu add or remove software packages to/from installation and removal queues.
The actual installation and/or removal of the packages will not be performed until either Foreground
Execution or Background Execution are selected from the main menu.

OPERATION
Navigating the Menus

To return to a previous menu press <Esc> or use the Cancel button

To exit the program from the main menu press <Esc> or use the Cancel button

To toggle between buttons press <Tab>

To select whichever button is highlighted press <Enter>

To select/deselect items from a checklist press <Space>

AUTHOR
Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Updated by Chuck Mead 07/17/2003

Updated by Terry Chan 08/08/2003

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
moonbase(5), lin(8), lvu(1), lget(8), lrm(8), lcrash(8)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar-Linux.org August 2003 LUNAR(8)

Lunar Linux:Installation/1.6.5

2010-08-15T15:09:04Z

Pacmanlives:

__TOC__

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

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

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

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

With that said, we hope you enjoy using Lunar!

==About this installation manual==

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

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

==Getting the ISO==

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

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

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

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

==Booting the ISO==

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

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

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

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

==Virtual Consoles==

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

==Language and keyboard interface Settings==

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

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

==Creating or editing Partitions==

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

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

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

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

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

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

Here's our partition setup:

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

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

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

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

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

==Selecting Partitions and Filesystems==

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

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

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

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

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

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

==Installing Lunar==

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

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

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

==Setting Up Your Compiler Optimizations==

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

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

The GCC_4_4 menu also allows you to change other options:

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

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

==Adding Other Compiler Toolchain Optimizations==

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

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

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

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

cat /proc/cpuinfo

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

==Configuring Your Bootloader==

=== Configuring LILO ===

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

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

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

boot=/dev/sda1

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

boot=/dev/sda

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

=== Configuring GRUB ===

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

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

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

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

===Installing a precompiled kernel===

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

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

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

===Building Your Customized Linux Kernel===

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

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

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

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

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

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

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

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

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

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

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

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

==Setting Up Networking==

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

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

==Other settings==

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

==Reboot!==

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

==Upgrade Moonbase==

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

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

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

''Have Phun!!''

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

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

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

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

Lunar Linux:Installation/1.6.5

2010-07-24T21:04:53Z

Pacmanlives: /* Getting the ISO */

__TOC__

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

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

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

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

With that said, we hope you enjoy using Lunar!

==About this installation manual==

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

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

==Getting the ISO==

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

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

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

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

==Booting the ISO==

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

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

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

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

==Virtual Consoles==

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

==Language and keyboard interface Settings==

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

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

==Creating or editing Partitions==

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

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

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

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

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

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

Here's our partition setup:

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

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

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

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

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

==Selecting Partitions and Filesystems==

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

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

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

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

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

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

==Installing Lunar==

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

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

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

==Setting Up Your Compiler Optimizations==

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

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

The GCC_4_4 menu also allows you to change other options:

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

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

==Adding Other Compiler Toolchain Optimizations==

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

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

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

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

cat /proc/cpuinfo

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

==Configuring Your Bootloader==

=== Configuring LILO ===

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

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

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

boot=/dev/sda1

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

boot=/dev/sda

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

=== Configuring GRUB ===

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

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

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

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

===Installing a precompiled kernel===

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

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

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

===Building Your Customized Linux Kernel===

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

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

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

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

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

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

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

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

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

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

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

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

==Setting Up Networking==

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

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

==Other settings==

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

==Reboot!==

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

==Upgrade Moonbase==

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

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

''Have Phun!!''

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

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

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

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

Install XOrg7

2010-05-12T21:31:49Z

Pacmanlives: /* NVIDIA Drivers */

=XOrg7=
All commands need to be run as root.
==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You no longer need to generate an xorg.config file as X will do this on its own.

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work with X 
<code>lin xf86-input-evdev </code>

== Third Party Drivers==

===NVIDIA Drivers===

When installing Nvidia drivers make sure that X is not running as the Nvidia drivers will not install properly.

You may install the Nvidia driver by using the following command. 
<code>lin NVIDIA </code>

To set up the nvidia driver all you need to do is run. 
<code> nvidia-xconfig </code>

Anytime you do a kernel update you are going to have to rebuild the Nvidia drivers kenrel modules. The next time you reboot into the new kernel you need to turn off X and any login managers that you may be using such as Slim/KDM/GDM/XDM then issue <code> lin NVIDIA </code> to rebuild this module

==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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T21:30:54Z

Pacmanlives: /* Installing XOrg 7.x */

=XOrg7=
All commands need to be run as root.
==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You no longer need to generate an xorg.config file as X will do this on its own.

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work with X 
<code>lin xf86-input-evdev </code>

== Third Party Drivers==

===NVIDIA Drivers===

When installing Nvidia drivers make sure that X is not running as the Nvidia drivers will not install properly.

You may install the Nvidia driver by using the following command. 
<code>lin NVIDIA </code>

To set up the nvidia driver all you need to do is run.
<code> nvidia-xconfig </code>

Anytime you do a kernel update you are going to have to rebuild the Nvidia drivers kenrel modules. The next time you reboot into the new kernel you need to turn off X and any login managers that you may be using such as Slim/KDM/GDM/XDM then issue <code> lin NVIDIA </code> to rebuild this module

==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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T15:29:02Z

Pacmanlives: /* XOrg7 */

=XOrg7=
All commands need to be run as root.
==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You no longer need to generate an xorg.config file as X will do this on its own.

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work with X 
<code>lin xf86-input-evdev </code>

== Third Party Drivers==

===NVIDIA Drivers===

When installing Nvidia drivers make sure that X is not running as the Nvidia drivers will not install properly.

You may install the Nvidia driver by using the following command. 
<code>lin NVIDIA </code>

To set up the nvidia driver all you need to do is run.
<code> nvidia-xconfig </code>

Anytime you do a kernel update you are going to have to rebuild the Nvidia drivers kenrel modules. The next time you reboot into the new kernel you need to turn off X and any login managers that you may be using such as Slim/KDM/GDM/XDM then issue <code> lin NVIDIA </code> to rebuild this module

==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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T15:28:08Z

Pacmanlives: /* NVIDIA Drivers */

=XOrg7=

==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You no longer need to generate an xorg.config file as X will do this on its own.

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work with X 
<code>lin xf86-input-evdev </code>

== Third Party Drivers==

===NVIDIA Drivers===

When installing Nvidia drivers make sure that X is not running as the Nvidia drivers will not install properly.

You may install the Nvidia driver by using the following command. 
<code>lin NVIDIA </code>

To set up the nvidia driver all you need to do is run.
<code> nvidia-xconfig </code>

Anytime you do a kernel update you are going to have to rebuild the Nvidia drivers kenrel modules. The next time you reboot into the new kernel you need to turn off X and any login managers that you may be using such as Slim/KDM/GDM/XDM then issue <code> lin NVIDIA </code> to rebuild this module

==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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T15:23:08Z

Pacmanlives: /* NVIDIA Drivers */

=XOrg7=

==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You no longer need to generate an xorg.config file as X will do this on its own.

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work with X 
<code>lin xf86-input-evdev </code>

== Third Party Drivers==

===NVIDIA Drivers===

When installing Nvidia drivers make sure that X is not running as the Nvidia drivers will not install properly.

You may install the Nvidia driver by using the following command. 
<code>lin NVIDIA </code>

Anytime you do a kernel update you are going to have to rebuild the Nvidia drivers kenrel modules. The next time you reboot into the new kernel you need to turn off X and any login managers that you may be using such as Slim/KDM/GDM/XDM then issue 'lin NVIDIA '

==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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T15:22:34Z

Pacmanlives: /* Installing XOrg 7.x */

=XOrg7=

==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You no longer need to generate an xorg.config file as X will do this on its own.

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work with X 
<code>lin xf86-input-evdev </code>

== Third Party Drivers==

===NVIDIA Drivers===

When installing Nvidia drivers make sure that X is not running as the Nvidia drivers will not install properly.

You may install the Nvidia driver by using the following command. 
<code>lin NVIDIA </code>

Anytime you do a kernel update you are going to have to rebuild the Nvidia drivers kenrel modules. The next time you reboot into the new kernel you need to turn off X and any login managers that you may be using such as Slim/KDM/GDM/XDM then issue 'lin NVIDIA '

==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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T15:22:05Z

Pacmanlives:

=XOrg7=

==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You no longer need to generate an xorg.config file as X will go this on its own.

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work with X 
<code>lin xf86-input-evdev </code>

== Third Party Drivers==

===NVIDIA Drivers===

When installing Nvidia drivers make sure that X is not running as the Nvidia drivers will not install properly.

You may install the Nvidia driver by using the following command. 
<code>lin NVIDIA </code>

Anytime you do a kernel update you are going to have to rebuild the Nvidia drivers kenrel modules. The next time you reboot into the new kernel you need to turn off X and any login managers that you may be using such as Slim/KDM/GDM/XDM then issue 'lin NVIDIA '

==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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T14:56:38Z

Pacmanlives: /* Installing XOrg 7.x */

=XOrg7=

==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work 
<code>lin xf86-input-evdev </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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T14:55:40Z

Pacmanlives:

=XOrg7=

==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<code>lin XOrg7</code>

You may also need to install xf86-input-evdev in order for you keyboard and mouse to work
<code>lin xf86-input-evdev </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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

2010-05-12T14:50:24Z

Pacmanlives:

=XOrg7=

==Installing XOrg 7.x ==

You may use the 'XOrg7' module to install XOrg 7.X: 
<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: 
: <code>lunar set X11R7_PREFIX=/your/prefix/here</code> 

The XOrg7 profile is going to create some symlinks on your system: 
: <code>/usr/X11 -> $MODULE_PREFIX; /usr by default </code>
: <code>/usr/X11R6 -> $MODULE_PREFIX; /usr by default</code> 
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
**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
**showfont - show information about X font from font server
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xditview - display ditroff output
**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
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**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 ==> COMPLETE
*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

User talk:Pacmanlives

2010-04-15T04:29:08Z

Pacmanlives:

== TODO LIST: ==

Things to add/ change on the website.

Meet the dev's: Pic, Where they are from what they do for the project , hobbies , how long they have been using linux/with the project.

Add some new current screenshots. Current ones are old and outdated need to show that we are still relevant.

News section to the website like major package updates kde/gnome/xfce, ect. wordpress or something like that to make changes easier

http://www.lunar-linux.org/index.php/en/information.html fix.

<s> Modules are showing twice. Found the code here “<li class="item74"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>

<li class="item84"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>”
</s>

Upgrade to some of the code so that way when you hover over the link it shows the sub menu.

== WIKI Edits: ==

How to's to get kde4, gnome, xfce, etc. installed. Add guides for stuff like Multimedia, Cool apps that you uses everyday.

http://wiki.lunar-linux.org/index.php/Install_XOrg7

Remove the Xorg 6 section as it is old.

Add driver how to install Nvidia/Ati drivers. linked?

http://wiki.lunar-linux.org/index.php/Install_fglrx ATI install still current?

<s> http://wiki.lunar-linux.org/index.php/Lunar_Linux

Remove 3rd party link , as it is dead. Dont think this is current in the about section "Currently, Lunar only supports the x86 and x86-64 architectures, but support for Sparc, PPC, and Alpha is being worked on."</s> Completed by engelsman

Add info to tools suchs as http://wiki.lunar-linux.org/index.php/Tools:lunar man page/ screen shots of what lunar looks like. http://wiki.lunar-linux.org/index.php/Tools:lvu is a good example of what we need to do for all the tools.

http://wiki.lunar-linux.org/index.php/Lunar_Linux:Installation

NEEDS TO BE UPDATED!

User talk:Pacmanlives

2010-04-15T04:27:51Z

Pacmanlives:

== TODO LIST: ==

Things to add/ change on the website.

Meet the dev's: Pic, Where they are from what they do for the project , hobbies , how long they have been using linux/with the project.

Add some new current screenshots. Current ones are old and outdated need to show that we are still relevant.

http://www.lunar-linux.org/index.php/en/information.html fix.

<s> Modules are showing twice. Found the code here “<li class="item74"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>

<li class="item84"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>”
</s>

Upgrade to some of the code so that way when you hover over the link it shows the sub menu.

== WIKI Edits: ==

How to's to get kde4, gnome, xfce, etc. installed. Add guides for stuff like Multimedia, Cool apps that you uses everyday.

http://wiki.lunar-linux.org/index.php/Install_XOrg7

Remove the Xorg 6 section as it is old.

Add driver how to install Nvidia/Ati drivers. linked?

http://wiki.lunar-linux.org/index.php/Install_fglrx ATI install still current?

<s> http://wiki.lunar-linux.org/index.php/Lunar_Linux

Remove 3rd party link , as it is dead. Dont think this is current in the about section "Currently, Lunar only supports the x86 and x86-64 architectures, but support for Sparc, PPC, and Alpha is being worked on."</s> Completed by engelsman

Add info to tools suchs as http://wiki.lunar-linux.org/index.php/Tools:lunar man page/ screen shots of what lunar looks like. http://wiki.lunar-linux.org/index.php/Tools:lvu is a good example of what we need to do for all the tools.

http://wiki.lunar-linux.org/index.php/Lunar_Linux:Installation

NEEDS TO BE UPDATED!

News section to the website like major package updates kde/gnome/xfce, ect.

User talk:Pacmanlives

2010-03-11T04:54:37Z

Pacmanlives: /* WIKI Edits: */

== TODO LIST: ==

Things to add/ change on the website.

Meet the dev's: Pic, Where they are from what they do for the project , hobbies , how long they have been using linux/with the project.

Add some new current screenshots. Current ones are old and outdated need to show that we are still relevant.

http://www.lunar-linux.org/index.php/en/information.html fix.

Modules are showing twice. Found the code here “<li class="item74"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>

<li class="item84"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>”

Upgrade to some of the code so that way when you hover over the link it shows the sub menu.

== WIKI Edits: ==

How to's to get kde4, gnome, xfce, etc. installed. Add guides for stuff like Multimedia, Cool apps that you uses everyday.

http://wiki.lunar-linux.org/index.php/Install_XOrg7

Remove the Xorg 6 section as it is old.

Add driver how to install Nvidia/Ati drivers. linked?

http://wiki.lunar-linux.org/index.php/Install_fglrx ATI install still current?

<s> http://wiki.lunar-linux.org/index.php/Lunar_Linux

Remove 3rd party link , as it is dead. Dont think this is current in the about section "Currently, Lunar only supports the x86 and x86-64 architectures, but support for Sparc, PPC, and Alpha is being worked on."</s> Completed by engelsman

Add info to tools suchs as http://wiki.lunar-linux.org/index.php/Tools:lunar man page/ screen shots of what lunar looks like. http://wiki.lunar-linux.org/index.php/Tools:lvu is a good example of what we need to do for all the tools.

http://wiki.lunar-linux.org/index.php/Lunar_Linux:Installation

NEEDS TO BE UPDATED!

MPD

2010-02-20T18:27:32Z

Pacmanlives:

<blockquote>''Music Player Daemon (MPD) is a flexible, powerful, server-side application for playing music. Through plugins and libraries it can play a variety of sound files while being controlled by its network protocol''</blockquote>
From [http://mpd.wikia.com/wiki/Music_Player_Daemon_Wiki MPD Homepage]:

== Installation ==
To install mpd all your have to do is run ' lin mpd 'as root.

==Configuration==
Copy the example config:' cp /usr/share/doc/mpd/doc/mpdconf.example /etc/mpd.conf '

Now edit /etc/mpd.conf with you favorite editor as root.

Now you need to build the database with the following command. ' /usr/bin/mpd --create-db '

==Service==
Now you can start the service by running this command as root ' /etc/init.d/mpd start '

As long as you edited your config file correctly you should have a working mpd!
Now you can install the client!

==Additional Help==
Additional help can be found at the [http://mpd.wikia.com/wiki/Music_Player_Daemon_Wiki MPD WIKI]

MPD

2010-02-20T18:25:32Z

Pacmanlives:

<blockquote>''Music Player Daemon (MPD) is a flexible, powerful, server-side application for playing music. Through plugins and libraries it can play a variety of sound files while being controlled by its network protocol''</blockquote>
From [http://mpd.wikia.com/wiki/Music_Player_Daemon_Wiki MPD Homepage]:

== Installation ==
To install mpd all your have to do is run ' lin mpd 'as root.

==Configuration==
Copy the example config: cp /usr/share/doc/mpd/doc/mpdconf.example /etc/mpd.conf
Now edit /etc/mpd.conf with you favorite editor as root.

Now you need to build the database with the following command. '/usr/bin/mpd --create-db '

==Service==
Now you can start the service by running this command as root ' /etc/init.d/mpd start '

As long as you edited your config file correctly you should have a working mpd!
Now you can install the client!

==Additional Help==
Additional help can be found at the [http://mpd.wikia.com/wiki/Music_Player_Daemon_Wiki MPD WIKI]

Module Writing

2010-02-20T17:20:46Z

Pacmanlives:

__TOC__

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

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

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

==Starting the module==

====Quick and Dirty Way====

The quick way to create a module is by using [[Tools:lvu|lvu]].
All you have to do is run this as root ' lvu new mymodule ' this will attempt to make a module [[DETAILS]] file from scratch using cut and paste from the user. It will create both the directory in [[zlocal]] and the [[DETAILS]] file. Now if you ' lvu cd mymodule ' you should see a [[DETAILS]] file in that directory. At this point you should verify that the [[DETAILS]] file looks like the one discribed in the the Normal Way

====Normal Way====

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

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

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

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

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

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

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

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

== Module Format ==

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

Module Writing

2010-02-20T16:58:24Z

Pacmanlives:

__TOC__

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

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

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

==Starting the module==

====Quick and Dirty Way====

The quick way to create a module is by using lvu.
All you have to do is run this as root ' lvu new mymodule ' this will attempt to make a module [[DETAILS]] file from scratch using cut and paste from the user. It will create both the directory in [[zlocal]] and the [[DETAILS]] file. Now if you ' lvu cd mymodule ' you should see a [[DETAILS]] file in that directory. At this point you should verify that the [[DETAILS]] file looks like the one discribed in the the Normal Way

====Normal Way====

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

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

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

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

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

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

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

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

== Module Format ==

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

Module Writing

2010-02-20T16:56:53Z

Pacmanlives:

__TOC__

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

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

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

==Starting the module==

====Quick and Dirty Way====

The quick way to create a module is by using lvu.
All you have to do is run this as root ' lvu new mymodule ' this will attempt to make a module [[DETAILS]]file from scratch using cut and paste from the user. It will create both the directory in [[zlocal]] and the [[DETAILS]] file. Now if you ' lvu cd mymodule ' you should see a [[DETAILS]] file in that directory. At this point you should verify that the [[DETAILS]] file looks like the one discribed in the the Normal Way

====Normal Way====

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

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

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

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

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

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

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

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

== Module Format ==

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

Module Writing

2010-02-20T04:04:53Z

Pacmanlives:

__TOC__

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

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

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

==Starting the module==

====Easy way====
The easy way to write a module is by using lvu.
All you have to do run this as root ' lvu new mymodule ' this will walk you though everything that is needed for a DETAILS file. It will create both the directory in [[zlocal]] and the [[DETAILS]] file. Now if you ' lvu cd mymodule ' you should see a DETAILS file in that directory.

====Hard Way====

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

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

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

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

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

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

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

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

== Module Format ==

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

MPD

2010-02-20T03:55:45Z

Pacmanlives:

The Howto guide to setting up MPD.

STEP 1. To install mpd all your have to do is type ' lin mpd 'as root
Then copy the example config: cp /usr/share/doc/mpd/doc/mpdconf.example /etc/mpd.conf

STEP 2. Edit the config

STEP 3. You now need to build the database with the following command. '/usr/bin/mpd --create-db '

STEP 4. Start the service:
/etc/init.d/mpd start

As long as you edited your config file correctly you should have a working mpd!
Now you can install the client!

This is a WIP

Module Writing

2010-02-20T02:27:35Z

Pacmanlives:

__TOC__

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

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

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

==Starting the module==

====Easy way====
The easy way to write a module is by using lvu.
All you have to do run this as root ' lvu new mymodule ' this will walk you though everything that is needed for a DETAILS file. It will create both the directory in [[zlocal]] and the [[DETAILS]] file. Now if you ' cd /var/lib/lunar/moonbase/zlocal/mymodule ' you should see a DETAILS file in that directory.

====Hard Way====

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

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

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

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

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

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

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

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

== Module Format ==

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

Tools:lvu.1.manpage

2010-02-19T22:27:06Z

Pacmanlives:

See this link for a less verbose version [[Tools:lvu]]

LVU(1) LUNAR LVU(1)

NAME
lvu - query/view lunar package management information

SYNOPSIS
lvu alien|leafs|orphans|pam

lvu cd|what|where|website|sources|urls|maintainer|version <module>

lvu compile|compiler|links|install|sum|md5sum <module>

lvu export|import [snapshot]

lvu moonbase|html|updatelog|activity

lvu search "phrase"

lvu service port|acronym

lvu newer|older <yyyymmdd>

lvu from <path/file>

lvu installed [module]

lvu conflicts

lvu held|exiled|expired

lvu section [section]

lvu voyeur [delay or module]

lvu depends <module>

lvu tree <module>

lvu eert <module>

lvu size [module]

lvu new|submit|edit|unedit [module]

lvu $MODULE_SCRIPT <module>

COPYRIGHT
lvu(1) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by
previous authors 2001-2002 lvu(1) also contains material which is Copyright
(C) Lunar-Linux team.

DESCRIPTION
lvu is part of the lunar source-based package management suite. It is a gen-
eral purpose command-line tool for displaying package logs, version informa-
tion, checking for installed packages, checksums, message digests, main-
tainer information, package URL information, displaying new packages,
untracked files, sections, searching for files that are installed, finding
when modules were created and packages in the software catalogue. It can
even take and retrieve snapshots of currently installed packages for easy
duplication.

OPTIONS
alien

find and display all files which are not currently tracked by the
lunar package management system

leafs

displays installed modules that have no explicit dependencies on them

orphans

displays installed modules that are missing required dependencies

pam

display modules installed that are pam aware

cd <module>

changes current directory to the given module and execs a new shell

what <module>

view the long package description

where <module>

display the section a module belongs to

website <module>

display the URL for the specified module

sources <module>

list all source files contained in a module

urls <module>

list all URLs for a module

maintainer <module>

display the email address of the person currently responsible for
maintaining a specified module

version <module>

display version of module in moonbase

compile <module>

show the compiler output generated when the module was built

compiler <module>

display the version of compiler used for creating the ELF files in
modules

links <module>

display the modules that this module's ELF binary files actually
links to

install <module>

used to determine what files were installed by a module and where
those files are located

conflicts

display modules with conflicting files

held

display held modules

exiled

display exiled modules

expired

display a list of modules which will be updated by a `lunar renew`

sum <module>

print CRC checksums for modules(s). If no module is given it defaults
to all.

md5sum <module>

print module MD5 message digests (fingerprints). If no module is
given it default to all

export

take a snapshot of all modules and configuration currently installed

import snapshot

restore the snapshot from a previous lvu export command (see the
export option)

moonbase

prints the entire moonbase

html

prints the entire moonbase in a nice html format

updatelog

view summary log of previous lunar update

activity

view the main lunar activity log

search "phrase"

Searches modules long descriptions for phrase

service port|acronym

displays modules that provide the given service port|acronym

newer date

print packages that are newer than a specified date. the date must be
specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

older date

print packages that are older than a specified date. the date must be
specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

from <path/><file>

find out what module has <path>/file installed

installed <module>

view all installed packages and corresponding version numbers or
check to see whether a particular package is installed and if it is
installed display its version number

section <module>

view a list of all sections in the software catalogue or display a
list of packages from a specific section

size <module>

display the size of a given module or all your installed modules in
KB

voyeur <module>

start looking at what lin is compiling at the moment and outputs it.
A module can be optionally specified.

depends <module>

displays the modules that explicitly or recursively depend on this
module.

tree <module>
displays a tree of the module's dependencies.

eert <module>

displays a tree of the module's reverse dependencies.

new <module>

Attempt to create a module DETAILS file from scratch using cut-n-
paste data from the user. Very dirty method to get a module started
by just having 4 pieces of information handy: download url, descrip-
tions and name

edit <module>

Copy an existing module to zlocal so it can be edited. Turn on ZLO-
CAL_OVERRIDES to make sure your edited module gets used instead of
the default module.

unedit <module>

Discards your 'edit'ed zlocal module. Works the same as removing it.

submit <module>

Submit a module to the lunar module submission list/mail alias.
Please only submit tested changes.

$MODULE_SCRIPT <module>

replace $MODULE_SCRIPT with any of the following DETAILS | CONFIGURE
| CONFLICTS | PRE_BUILD | BUILD | POST_BUILD | POST_INSTALL |
POST_REMOVE to show module scripts for the module

AUTHOR
Original version written by Brian Peterson

Modified by Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Edited and new functions added by Chuck Mead 05/21/2002

Updated again by Terry Chan 08/08/2003

Updated by Stefan Wold 06/07/2009

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
lunar(8), lin(8), lrm(8), lget(8), moonbase(5)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux June 2009 LVU(1)

Tools:lvu.1.manpage

2010-02-19T22:26:47Z

Pacmanlives:

See this link for a less verbose version Tools:lvu

LVU(1) LUNAR LVU(1)

NAME
lvu - query/view lunar package management information

SYNOPSIS
lvu alien|leafs|orphans|pam

lvu cd|what|where|website|sources|urls|maintainer|version <module>

lvu compile|compiler|links|install|sum|md5sum <module>

lvu export|import [snapshot]

lvu moonbase|html|updatelog|activity

lvu search "phrase"

lvu service port|acronym

lvu newer|older <yyyymmdd>

lvu from <path/file>

lvu installed [module]

lvu conflicts

lvu held|exiled|expired

lvu section [section]

lvu voyeur [delay or module]

lvu depends <module>

lvu tree <module>

lvu eert <module>

lvu size [module]

lvu new|submit|edit|unedit [module]

lvu $MODULE_SCRIPT <module>

COPYRIGHT
lvu(1) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by
previous authors 2001-2002 lvu(1) also contains material which is Copyright
(C) Lunar-Linux team.

DESCRIPTION
lvu is part of the lunar source-based package management suite. It is a gen-
eral purpose command-line tool for displaying package logs, version informa-
tion, checking for installed packages, checksums, message digests, main-
tainer information, package URL information, displaying new packages,
untracked files, sections, searching for files that are installed, finding
when modules were created and packages in the software catalogue. It can
even take and retrieve snapshots of currently installed packages for easy
duplication.

OPTIONS
alien

find and display all files which are not currently tracked by the
lunar package management system

leafs

displays installed modules that have no explicit dependencies on them

orphans

displays installed modules that are missing required dependencies

pam

display modules installed that are pam aware

cd <module>

changes current directory to the given module and execs a new shell

what <module>

view the long package description

where <module>

display the section a module belongs to

website <module>

display the URL for the specified module

sources <module>

list all source files contained in a module

urls <module>

list all URLs for a module

maintainer <module>

display the email address of the person currently responsible for
maintaining a specified module

version <module>

display version of module in moonbase

compile <module>

show the compiler output generated when the module was built

compiler <module>

display the version of compiler used for creating the ELF files in
modules

links <module>

display the modules that this module's ELF binary files actually
links to

install <module>

used to determine what files were installed by a module and where
those files are located

conflicts

display modules with conflicting files

held

display held modules

exiled

display exiled modules

expired

display a list of modules which will be updated by a `lunar renew`

sum <module>

print CRC checksums for modules(s). If no module is given it defaults
to all.

md5sum <module>

print module MD5 message digests (fingerprints). If no module is
given it default to all

export

take a snapshot of all modules and configuration currently installed

import snapshot

restore the snapshot from a previous lvu export command (see the
export option)

moonbase

prints the entire moonbase

html

prints the entire moonbase in a nice html format

updatelog

view summary log of previous lunar update

activity

view the main lunar activity log

search "phrase"

Searches modules long descriptions for phrase

service port|acronym

displays modules that provide the given service port|acronym

newer date

print packages that are newer than a specified date. the date must be
specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

older date

print packages that are older than a specified date. the date must be
specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

from <path/><file>

find out what module has <path>/file installed

installed <module>

view all installed packages and corresponding version numbers or
check to see whether a particular package is installed and if it is
installed display its version number

section <module>

view a list of all sections in the software catalogue or display a
list of packages from a specific section

size <module>

display the size of a given module or all your installed modules in
KB

voyeur <module>

start looking at what lin is compiling at the moment and outputs it.
A module can be optionally specified.

depends <module>

displays the modules that explicitly or recursively depend on this
module.

tree <module>
displays a tree of the module's dependencies.

eert <module>

displays a tree of the module's reverse dependencies.

new <module>

Attempt to create a module DETAILS file from scratch using cut-n-
paste data from the user. Very dirty method to get a module started
by just having 4 pieces of information handy: download url, descrip-
tions and name

edit <module>

Copy an existing module to zlocal so it can be edited. Turn on ZLO-
CAL_OVERRIDES to make sure your edited module gets used instead of
the default module.

unedit <module>

Discards your 'edit'ed zlocal module. Works the same as removing it.

submit <module>

Submit a module to the lunar module submission list/mail alias.
Please only submit tested changes.

$MODULE_SCRIPT <module>

replace $MODULE_SCRIPT with any of the following DETAILS | CONFIGURE
| CONFLICTS | PRE_BUILD | BUILD | POST_BUILD | POST_INSTALL |
POST_REMOVE to show module scripts for the module

AUTHOR
Original version written by Brian Peterson

Modified by Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Edited and new functions added by Chuck Mead 05/21/2002

Updated again by Terry Chan 08/08/2003

Updated by Stefan Wold 06/07/2009

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
lunar(8), lin(8), lrm(8), lget(8), moonbase(5)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux June 2009 LVU(1)

Tools:lin.8.manpage

2010-02-19T22:26:16Z

Pacmanlives:

See this link for a less verbose version [[Tools:lin]]

LIN(8) LUNAR LIN(8)

NAME: lin - Lunar install software modules

SYNOPSIS
lin [options] [package1[/version]] ... [package2[/version]] ...

COPYRIGHT
lin(8) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by
previous authors 2001-2002

EXAMPLE
To install emacs type:

lin emacs

DESCRIPTION
lin is part of the Lunar source-code package management suite. It is a com-
mand-line tool for automatically retrieving, unpacking, compiling,
installing, and tracking software installations.

OPTIONS
-c, --compile
Compiles module even if there is a compile cache in /var/cache/lunar.

-d, --debug
Enables debug messages, very useful when emailing a bug report.

--deps Configures the modules and determines their dependencies, but they
are not compiled or installed.

-f, --from directory
Specify an alternate directory to search for source code tarballs. An
alternative to /var/spool/lunar.

-h, --help
Outputs short help.

-p, --probe
Only lin if the module was not previously installed.

-r, --reconfigure
Select new configuration and dependencies for modules.

--opts (configure flags)
Add arbitrary options to the configure stage of the module. The
options are saved for future upgrades but will be erased by using
"-r".

-R, --resurrect
Reinstalls a module which has been removed but still has the compiled
version available.

-w, --want (version number)
Try to install a different version than the current one in moonbase.
Integrity checking is turned off. Success not guaranteed.

-s, --silent
Decreases the level of message output.

-v, --verbose
Increases the level of message output.

FILES
All files can be edited by hand, but its easier to edit them with lunar.

/etc/lunar/config

Configuration options.

/etc/lunar/mirrors

Mirror information.

/etc/lunar/local/*
Local settings.

/etc/lunar/local/config

Various local settings and compiler optimization parameters (select
with lunar).

/etc/lunar/local/depends/*

Dependency and configuration information for modules.

/var/lib/lunar/functions/*.lunar

Contains functions used by lin.

ENVIRONMENT
The following settings can be altered in /etc/lunar/local/config It is eas-
ier, faster and less error prone to edit them with lunar.

GNU_URL
The GNU Mirror (default: ftp.gnu.org).

KERNEL_URL
The kernel mirror (default: ftp.kernel.org).

XFREE86_URL
The xfree86 mirror (default: ftp.xfree86.org).

GNOME_URL
The GNOME mirror (default: ftp.gnome.org).

KDE_URL
The KDE mirror (default: ftp.kde.org).

SFORGE_URL
The Sourceforge mirror. (default: none).

PATCH_URL
The default patch mirror. (default: down-
load.lunar-linux.org/lunar/patches).

LRESORT_URL
The default lunar mirror. If all else fails go here! (default: down-
load.lunar-linux.org/lunar/cache)

MOONBASE_URL
The lunar moonbase mirrors. (default: down-
load.lunar-linux.org/lunar/).

color If set to yes lin outputs nice colour. Green for messages, gray for
compiling, yellow for questions, and red for errors.

PROMPT_DELAY
The delay in seconds that lin pauses when waiting for responses from
you.

MAIL_REPORTS
If set to yes, installation logs will be mailed to the admin upon a
successful compile. Compile logs will be mailed instead upon a failed
compilation.

ADMIN'S_EMAIL
The mailbox where the reports will be mailed. The admin's email
address.

PRESERVE
When set to yes, configuration files that have been edited will not
get deleted when the module is re-installed

SOUND If set to yes then sounds will be enabled if the lunar-sound module
is installed

SUSTAIN
When set to yes this disallows removing of modules that would cause
terrible malfunctions. eg glibc, gcc, bash, to name some obvious
ones.
MOONBASE_URL
The lunar moonbase mirrors. (default: down-
load.lunar-linux.org/lunar/).

color If set to yes lin outputs nice colour. Green for messages, gray for
compiling, yellow for questions, and red for errors.

PROMPT_DELAY
The delay in seconds that lin pauses when waiting for responses from
you.

MAIL_REPORTS
If set to yes, installation logs will be mailed to the admin upon a
successful compile. Compile logs will be mailed instead upon a failed
compilation.

ADMIN'S_EMAIL
The mailbox where the reports will be mailed. The admin's email
address.

PRESERVE
When set to yes, configuration files that have been edited will not
get deleted when the module is re-installed

SOUND If set to yes then sounds will be enabled if the lunar-sound module
is installed

SUSTAIN
When set to yes this disallows removing of modules that would cause
terrible malfunctions. eg glibc, gcc, bash, to name some obvious
ones.

VIEW_REPORTS
If set to yes then you will be prompted whether to view reports
before and after installation.

VOYEUR If set to yes then compiler output will be displayed in real time.

REAP Deletes files when removing.

AUTOFIX
If set to yes whenever a library is updated all packages that depend
on that library will be rebuilt. See FIND_CHECK, MD5SUM_CHECK,
LDD_CHECK, SYM_CHECK for autofix settings.

FIND_CHECK
See the -f options above for explanations of these.

ADVANCED USAGE
Using source code tarballs from an alternate location.

lin --from /root/spool/lunar emacs Unless the -from option is speci-
fied lin will always check the /var/spool/lunar directory first to
see if the package exists. If the package does not exist it downloads
the package via the Internet.

AUTHOR
Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Updated by Chuck Mead 07/17/2003

Updated by Terry Chan 08/08/2003

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
lunar(8), lrm(8), lvu(1), lget(8), moonbase(5)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LIN(8)

Tools:lin

2010-02-19T22:23:21Z

Pacmanlives:

====lin====

[[Tools:lin|lin]] is the lunar ''install'' tool. It handles downloading, upgrading (through [[tools:lrm|lrm]], installation and compilation of modules on your system.

To do this, lin follows several steps:

* resolve conflicts - if a package conflicts and is installed, it will prompt the user what to do (remove or keep).
* solve dependencies - if packages are missing, they are inserted into the install queue
* download - the packages are downloaded in the background while processing continues by [[tools:lget|lget]]
* configure options - the user may be prompted for additional configuration questions that affect the way a package is built
* checks - the checksums are checked if available, all sources are downloaded, etc.
* compile - the package is compiled
* upgrade - if a previous version of the package is installed, [[tools:lrm|lrm]] removes the old files in a safe way
* install - the package is physically installed to your system
* post-install actions - several things are done, such as administrativa, documentation, init.d scripts etc.

====Attentional Information For This Tool====
[[lin|lin]]

Tools:lin.8.manpage

2010-02-19T22:15:51Z

Pacmanlives: New page: LIN(8) LUNAR LIN(8) NAME: lin - Lunar install software modules SYNOPSIS lin [options] [package1[/version]] ... [pac...

LIN(8) LUNAR LIN(8)

NAME: lin - Lunar install software modules

SYNOPSIS
lin [options] [package1[/version]] ... [package2[/version]] ...

COPYRIGHT
lin(8) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by
previous authors 2001-2002

EXAMPLE
To install emacs type:

lin emacs

DESCRIPTION
lin is part of the Lunar source-code package management suite. It is a com-
mand-line tool for automatically retrieving, unpacking, compiling,
installing, and tracking software installations.

OPTIONS
-c, --compile
Compiles module even if there is a compile cache in /var/cache/lunar.

-d, --debug
Enables debug messages, very useful when emailing a bug report.

--deps Configures the modules and determines their dependencies, but they
are not compiled or installed.

-f, --from directory
Specify an alternate directory to search for source code tarballs. An
alternative to /var/spool/lunar.

-h, --help
Outputs short help.

-p, --probe
Only lin if the module was not previously installed.

-r, --reconfigure
Select new configuration and dependencies for modules.

--opts (configure flags)
Add arbitrary options to the configure stage of the module. The
options are saved for future upgrades but will be erased by using
"-r".

-R, --resurrect
Reinstalls a module which has been removed but still has the compiled
version available.

-w, --want (version number)
Try to install a different version than the current one in moonbase.
Integrity checking is turned off. Success not guaranteed.

-s, --silent
Decreases the level of message output.

-v, --verbose
Increases the level of message output.

FILES
All files can be edited by hand, but its easier to edit them with lunar.

/etc/lunar/config

Configuration options.

/etc/lunar/mirrors

Mirror information.

/etc/lunar/local/*
Local settings.

/etc/lunar/local/config

Various local settings and compiler optimization parameters (select
with lunar).

/etc/lunar/local/depends/*

Dependency and configuration information for modules.

/var/lib/lunar/functions/*.lunar

Contains functions used by lin.

ENVIRONMENT
The following settings can be altered in /etc/lunar/local/config It is eas-
ier, faster and less error prone to edit them with lunar.

GNU_URL
The GNU Mirror (default: ftp.gnu.org).

KERNEL_URL
The kernel mirror (default: ftp.kernel.org).

XFREE86_URL
The xfree86 mirror (default: ftp.xfree86.org).

GNOME_URL
The GNOME mirror (default: ftp.gnome.org).

KDE_URL
The KDE mirror (default: ftp.kde.org).

SFORGE_URL
The Sourceforge mirror. (default: none).

PATCH_URL
The default patch mirror. (default: down-
load.lunar-linux.org/lunar/patches).

LRESORT_URL
The default lunar mirror. If all else fails go here! (default: down-
load.lunar-linux.org/lunar/cache)

MOONBASE_URL
The lunar moonbase mirrors. (default: down-
load.lunar-linux.org/lunar/).

color If set to yes lin outputs nice colour. Green for messages, gray for
compiling, yellow for questions, and red for errors.

PROMPT_DELAY
The delay in seconds that lin pauses when waiting for responses from
you.

MAIL_REPORTS
If set to yes, installation logs will be mailed to the admin upon a
successful compile. Compile logs will be mailed instead upon a failed
compilation.

ADMIN'S_EMAIL
The mailbox where the reports will be mailed. The admin's email
address.

PRESERVE
When set to yes, configuration files that have been edited will not
get deleted when the module is re-installed

SOUND If set to yes then sounds will be enabled if the lunar-sound module
is installed

SUSTAIN
When set to yes this disallows removing of modules that would cause
terrible malfunctions. eg glibc, gcc, bash, to name some obvious
ones.
MOONBASE_URL
The lunar moonbase mirrors. (default: down-
load.lunar-linux.org/lunar/).

color If set to yes lin outputs nice colour. Green for messages, gray for
compiling, yellow for questions, and red for errors.

PROMPT_DELAY
The delay in seconds that lin pauses when waiting for responses from
you.

MAIL_REPORTS
If set to yes, installation logs will be mailed to the admin upon a
successful compile. Compile logs will be mailed instead upon a failed
compilation.

ADMIN'S_EMAIL
The mailbox where the reports will be mailed. The admin's email
address.

PRESERVE
When set to yes, configuration files that have been edited will not
get deleted when the module is re-installed

SOUND If set to yes then sounds will be enabled if the lunar-sound module
is installed

SUSTAIN
When set to yes this disallows removing of modules that would cause
terrible malfunctions. eg glibc, gcc, bash, to name some obvious
ones.

VIEW_REPORTS
If set to yes then you will be prompted whether to view reports
before and after installation.

VOYEUR If set to yes then compiler output will be displayed in real time.

REAP Deletes files when removing.

AUTOFIX
If set to yes whenever a library is updated all packages that depend
on that library will be rebuilt. See FIND_CHECK, MD5SUM_CHECK,
LDD_CHECK, SYM_CHECK for autofix settings.

FIND_CHECK
See the -f options above for explanations of these.

ADVANCED USAGE
Using source code tarballs from an alternate location.

lin --from /root/spool/lunar emacs Unless the -from option is speci-
fied lin will always check the /var/spool/lunar directory first to
see if the package exists. If the package does not exist it downloads
the package via the Internet.

AUTHOR
Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Updated by Chuck Mead 07/17/2003

Updated by Terry Chan 08/08/2003

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
lunar(8), lrm(8), lvu(1), lget(8), moonbase(5)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LIN(8)

Tools:lvu.1.manpage

2010-02-19T22:05:41Z

Pacmanlives: New page: LVU(1) LUNAR LVU(1) NAME lvu - query/view lunar package management information SYNOPSIS lvu alien|leafs|orph...

LVU(1) LUNAR LVU(1)

NAME
lvu - query/view lunar package management information

SYNOPSIS
lvu alien|leafs|orphans|pam

lvu cd|what|where|website|sources|urls|maintainer|version <module>

lvu compile|compiler|links|install|sum|md5sum <module>

lvu export|import [snapshot]

lvu moonbase|html|updatelog|activity

lvu search "phrase"

lvu service port|acronym

lvu newer|older <yyyymmdd>

lvu from <path/file>

lvu installed [module]

lvu conflicts

lvu held|exiled|expired

lvu section [section]

lvu voyeur [delay or module]

lvu depends <module>

lvu tree <module>

lvu eert <module>

lvu size [module]

lvu new|submit|edit|unedit [module]

lvu $MODULE_SCRIPT <module>

COPYRIGHT
lvu(1) is Copyright (C) 2002-2003 Terry Chan with portions copyrighted by
previous authors 2001-2002 lvu(1) also contains material which is Copyright
(C) Lunar-Linux team.

DESCRIPTION
lvu is part of the lunar source-based package management suite. It is a gen-
eral purpose command-line tool for displaying package logs, version informa-
tion, checking for installed packages, checksums, message digests, main-
tainer information, package URL information, displaying new packages,
untracked files, sections, searching for files that are installed, finding
when modules were created and packages in the software catalogue. It can
even take and retrieve snapshots of currently installed packages for easy
duplication.

OPTIONS
alien

find and display all files which are not currently tracked by the
lunar package management system

leafs

displays installed modules that have no explicit dependencies on them

orphans

displays installed modules that are missing required dependencies

pam

display modules installed that are pam aware

cd <module>

changes current directory to the given module and execs a new shell

what <module>

view the long package description

where <module>

display the section a module belongs to

website <module>

display the URL for the specified module

sources <module>

list all source files contained in a module

urls <module>

list all URLs for a module

maintainer <module>

display the email address of the person currently responsible for
maintaining a specified module

version <module>

display version of module in moonbase

compile <module>

show the compiler output generated when the module was built

compiler <module>

display the version of compiler used for creating the ELF files in
modules

links <module>

display the modules that this module's ELF binary files actually
links to

install <module>

used to determine what files were installed by a module and where
those files are located

conflicts

display modules with conflicting files

held

display held modules

exiled

display exiled modules

expired

display a list of modules which will be updated by a `lunar renew`

sum <module>

print CRC checksums for modules(s). If no module is given it defaults
to all.

md5sum <module>

print module MD5 message digests (fingerprints). If no module is
given it default to all

export

take a snapshot of all modules and configuration currently installed

import snapshot

restore the snapshot from a previous lvu export command (see the
export option)

moonbase

prints the entire moonbase

html

prints the entire moonbase in a nice html format

updatelog

view summary log of previous lunar update

activity

view the main lunar activity log

search "phrase"

Searches modules long descriptions for phrase

service port|acronym

displays modules that provide the given service port|acronym

newer date

print packages that are newer than a specified date. the date must be
specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

older date

print packages that are older than a specified date. the date must be
specified in the 'yyyymmdd' format, where y=year, m=month, and d=day

from <path/><file>

find out what module has <path>/file installed

installed <module>

view all installed packages and corresponding version numbers or
check to see whether a particular package is installed and if it is
installed display its version number

section <module>

view a list of all sections in the software catalogue or display a
list of packages from a specific section

size <module>

display the size of a given module or all your installed modules in
KB

voyeur <module>

start looking at what lin is compiling at the moment and outputs it.
A module can be optionally specified.

depends <module>

displays the modules that explicitly or recursively depend on this
module.

tree <module>
displays a tree of the module's dependencies.

eert <module>

displays a tree of the module's reverse dependencies.

new <module>

Attempt to create a module DETAILS file from scratch using cut-n-
paste data from the user. Very dirty method to get a module started
by just having 4 pieces of information handy: download url, descrip-
tions and name

edit <module>

Copy an existing module to zlocal so it can be edited. Turn on ZLO-
CAL_OVERRIDES to make sure your edited module gets used instead of
the default module.

unedit <module>

Discards your 'edit'ed zlocal module. Works the same as removing it.

submit <module>

Submit a module to the lunar module submission list/mail alias.
Please only submit tested changes.

$MODULE_SCRIPT <module>

replace $MODULE_SCRIPT with any of the following DETAILS | CONFIGURE
| CONFLICTS | PRE_BUILD | BUILD | POST_BUILD | POST_INSTALL |
POST_REMOVE to show module scripts for the module

AUTHOR
Original version written by Brian Peterson

Modified by Kyle Sallee

Updated Thomas Stewart 01/15/2002

Converted to Lunar by Terry Chan 03/23/2002

Edited and new functions added by Chuck Mead 05/21/2002

Updated again by Terry Chan 08/08/2003

Updated by Stefan Wold 06/07/2009

REPORTING BUGS
Report bugs to <maintainer@lunar-linux.org>

SEE ALSO
lunar(8), lin(8), lrm(8), lget(8), moonbase(5)

WARRANTY
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux June 2009 LVU(1)

User talk:Pacmanlives

2010-02-18T22:24:16Z

Pacmanlives: New page: == TODO LIST: == Things to add/ change on the website. Meet the dev's: Pic, Where they are from what they do for the project , hobbies , how long they have been using li...

== TODO LIST: ==

Things to add/ change on the website.

Meet the dev's: Pic, Where they are from what they do for the project , hobbies , how long they have been using linux/with the project.

Add some new current screenshots. Current ones are old and outdated need to show that we are still relevant.

http://www.lunar-linux.org/index.php/en/information.html fix.

Modules are showing twice. Found the code here “<li class="item74"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>

<li class="item84"><a href="http://www.lunar-linux.org/index.php/en/links/76-lunar-linux/3-moonbase.html">Modules</a></li>”

Upgrade to some of the code so that way when you hover over the link it shows the sub menu.

== WIKI Edits: ==

How to's to get kde4, gnome, xfce, etc. installed. Add guides for stuff like Multimedia, Cool apps that you uses everyday.

http://wiki.lunar-linux.org/index.php/Install_XOrg7

Remove the Xorg 6 section as it is old.

Add driver how to install Nvidia/Ati drivers. linked?

http://wiki.lunar-linux.org/index.php/Install_fglrx ATI install still current?

http://wiki.lunar-linux.org/index.php/Lunar_Linux

Remove 3rd party link , as it is dead. Dont think this is current in the about section "Currently, Lunar only supports the x86 and x86-64 architectures, but support for Sparc, PPC, and Alpha is being worked on."

Add info to tools suchs as http://wiki.lunar-linux.org/index.php/Tools:lunar man page/ screen shots of what lunar looks like. http://wiki.lunar-linux.org/index.php/Tools:lvu is a good example of what we need to do for all the tools.

http://wiki.lunar-linux.org/index.php/Lunar_Linux:Installation

NEEDS TO BE UPDATED!

MPD

2010-02-18T05:53:01Z

Pacmanlives:

The Howto guide to setting up MPD.

STEP 1. To install mpd all your have to do is type ' lin mpd 'as root
Then copy the example config: cp /usr/share/doc/mpd/doc/mpdconf.example /etc/mpd.conf

STEP 2. Edit the config

STEP 3. You now need to build the database with the following command. '/usr/bin/mpd --create-db '

STEP 4. Start the service:
/etc/init.d/mpd start

As long as you edited your config file you should have a working mpd!
Now you can install the client!

This is a WIP

Howto Articles

2010-02-18T05:45:28Z

Pacmanlives: /* Software HOWTOs */

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=
===[[Use_Developer_branches|How to use a branch from one of the module developers]]===
* This guide covers how one can checkout the branch of a developer so you can test out some stuff.
===[[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.
===[[MPD | MPD Setup Guide]]===
* How to guide to installing and setting up MPD

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

MPD

2010-02-18T05:43:00Z

Pacmanlives: New page: The Howto guide to setting up MPD.

The Howto guide to setting up MPD.