Lunar Linux - User contributions [en]

Use Developer branches

2009-04-16T08:52:41Z

Elangelo:

Imagine you want to try out the xfce4-svn branch from developer elangelo.
You can see this branch [http://foo-projects.org/git/?p=elangelo/moonbase.git;a=shortlog;h=refs/heads/xfce4-svn here].

These would be the commands:
* clone the main repository lunar:
git clone git://lunar-linux.org/lunar/moonbase.git moonbase.git

* pull the xfce4-svn branch from elangelo and at the same time create a local xfce4-svn branch
cd moonbase.git
git pull git://lunar-linux.org/elangelo/moonbase.git xfce4-svn:xfce4-svn

* switch to the xfce4-svn branch:
git checkout xfce4-svn

* updating the xfce4-svn branch with latest master (the main repository of moonbase)
# switch back to the main repository
git checkout master
# update our master branch with the main repository
git pull git://lunar-linux.org/lunar/moonbase.git master
# switch back to our xfce4-svn branch
git checkout xfce4-svn
# merge the changes in master into out xfce4-svn branch (you can get conflicts with this)
git merge master
# install xfce4 (if you have xfce installed already you can simply lunar renew)
lin xfce4

* telling lunar to use the git repository instead of the default (/var/lib/lunar/moonbase) one:
lunar set MOONBASE /home/samuel/moonbase.git

* you're tired of xfce4-svn and want to try elangelo's xorg branch:
cd /home/samuel/moonbase.git
git checkout master
git pull git://lunar-linux.org/elangelo/moonbase.git xorg:xorg
git checkout xorg
#updating the branch with latest master of the main repository
git merge master
lunar renew

* you want to use both xfce4-svn and the xorg branch:
cd /home/samuel/moonbase.git
git checkout master
# create a new branch
git branch xfce4-svn_xorg
# switch to the new branch
git checkout xfce4-svn_xorg
# merge xorg branch changes
git merge xorg
# merge xfce4-svn branch changes
git merge xfce4-svn
# update lunar
lunar renew

* you are tired of all those branches:
git checkout master
git branch -D xfce4-svn
git branch -D xorg
git branch -D xfce4-svn_xorg

Use Developer branches

2009-04-16T08:48:19Z

Elangelo:

Imagine you want to try out the xfce4-svn branch from developer elangelo.
You can see this branch [http://foo-projects.org/git/?p=elangelo/moonbase.git;a=shortlog;h=refs/heads/xfce4-svn here].

These would be the commands:
* clone the main repository lunar:
git clone git://lunar-linux.org/lunar/moonbase.git moonbase.git

* pull the xfce4-svn branch from elangelo and at the same time create a local xfce4-svn branch
cd moonbase.git
git pull git://lunar-linux.org/elangelo/moonbase.git xfce4-svn:xfce4-svn

* switch to the xfce4-svn branch:
git checkout xfce4-svn

* updating the xfce4-svn branch with latest master (the main repository of moonbase)
git checkout master
git pull git://lunar-linux.org/lunar/moonbase.git master
git checkout xfce4-svn
git merge master
lin xfce4

* telling lunar to use the git repository instead of the default (/var/lib/lunar/moonbase) one:
lunar set MOONBASE /home/samuel/moonbase.git

* you're tired of xfce4-svn and want to try elangelo's xorg branch:
cd /home/samuel/moonbase.git
git checkout master
git pull git://lunar-linux.org/elangelo/moonbase.git xorg:xorg
git checkout xorg
git merge master
lunar renew

* you want to use both xfce4-svn and the xorg branch:
cd /home/samuel/moonbase.git
git checkout master
git branch xfce4-svn_xorg
git checkout xfce4-svn_xorg
git merge xorg
git merge xfce4-svn
lunar renew

* you are tired of all those branches:
git checkout master
git branch -D xfce4-svn
git branch -D xorg
git branch -D xfce4-svn_xorg

Use Developer branches

2009-04-16T08:47:06Z

Elangelo:

Imagine you want to try out the xfce4-svn branch from developer elangelo.
You can see this branch [http://foo-projects.org/git/?p=elangelo/moonbase.git;a=shortlog;h=refs/heads/xfce4-svn here].

These would be the commands:
* clone the main repository lunar:
git clone git://lunar-linux.org/lunar/moonbase.git moonbase.git

* pull the xfce4-svn branch from elangelo and at the same time create a local xfce4-svn branch
cd moonbase.git
git pull git://lunar-linux.org/elangelo/moonbase.git xfce4-svn:xfce4-svn

* switch to the xfce4-svn branch:
git checkout xfce4-svn

* updating the xfce4-svn branch with latest master (the main repository of moonbase)
git checkout master
git pull git://lunar-linux.org/lunar/moonbase.git master
git checkout xfce4-svn
git merge master
lin xfce4

* telling lunar to use the git repository instead of the default (/var/lib/lunar/moonbase) one:
lunar set MOONBASE /home/samuel/moonbase.git

* you're tired of xfce4-svn and want to try elangelo's xorg branch:
cd /home/samuel/moonbase.git
git checkout master
git pull git://lunar-linux.org/elangelo/moonbase.git xorg:xorg
git checkout xorg
git merge master
lunar renew

* you want to use both xfce4-svn and the xorg branch:
cd /home/samuel/moonbase.git
git checkout master
git branch xfce4-svn_xorg
git checkout xfce4-svn_xorg
git merge xorg
git merge xfce4-svn
lunar renew

* you are tired of all those branches:
git checkout master
git branch -D xfce4-svn
git branch -D xorg
git branch -D xfce4-svn_xorg

Use Developer branches

2009-04-16T08:43:31Z

Elangelo: New page: Imagine you want to try out the xfce4-svn branch from developer elangelo. You can see this branch [http://foo-projects.org/git/?p=elangelo/moonbase.git;a=shortlog;h=refs/heads/xfce4-svn he...

Installation:No CD

2008-10-22T17:07:52Z

Elangelo: /* Usb bootable lunar */

Installing Lunar-Linux without a CD drive or other removable media isn't really that hard. There are several ways of emulating a cd-rom with linux. There's some easy ways and some hard ways. I'll try to discuss all of them.

''Disclaimer: The methods below might destroy all your data and not work for you at all. Make backups! You yourself are responsible for your own data and system!''

__TOC__

==Booting the ISO from a hard disk partition==

Yes, I'm not kidding. This is by far one of the easiest methods. The idea behind this method is that you can boot the ISO from any media, all you need to do is boot from it. If that means that the ISO is somehow written on your hard disk, and you have a bootloader capable of booting boot sectors (like lilo, grub, windows all can do), then you're in business.

'''requires:'''

* Enough free disk space plus partition big enough for the iso image
* Any installed operating system and tools that allow directly to write to a partition
* A working boot loader like windows' bootloader, lilo or grub

Your best bet is to free some space at the end of your disk. Make sure this is '''larger''' than the lunar iso (somewhere around 350mb). Create a partition and ''copy'' the contents of the iso to that partition:

cat lunar-1.5.1-i686.iso > /dev/hda15

Once done, you should edit your bootloader (be it windows or grub or lilo) and make it boot the boot sector of the iso. Here's the lilo entry you would need:

other = /dev/hda15
label = lunar-1.5.1

That's it! reboot and select the iso entry, and you're ready to go! The lunar installer should start and everything should work just as good as from a CD!

==Chrooting into the ISO==

===Installing from 2.4 kernels with devfs support===

If the above method fails, you can always manually chroot into the ISO and start the installer manually too.

'''requires:'''

* A running linux installation with relatively new 2.4 kernel that has devfs support and allows chroot usage (must be root)

This method is a bit trickier since you will be repartitioning your hard disk from which you just have booted, so you should actually install a '''small''' linux installation somewhere near the end of your disk, losetup/loopmount the iso on there, and then install to partitions that are NOT active/mounted. This might even fail since the kernel doesn't like changing partitions when it's running.

So, start out by getting your 'tiny' linux running anf booting. Preferably install it at the end of your hard disk and re-partition the beginning of your hard disk already for the lunar installation. Reboot your system so the partitions are known by the kernel, and prepare to mount the ISO over loop:

losetup /dev/loop0 lunar-1.5.1-i686.iso
mount /dev/loop0 /mnt -o ro
chroot /mnt /sbin/lunar-install

that's it! The installer should run and you can perform all steps necessary for installing lunar on the remaining partitions. At the end, make sure you don't accidentally overwrite your bootstrap linux installation so you can fallback to it. Beware that you might want to add the bootstrap bootloader info too, in case you want to boot that installation if something goes wrong. Once lunar installs succesfully, you can remove this partition of course.

===Installing from 2.6 kernels with udev support===

===This is something different===
When the previous installation methods fail this is one you can ry as well:

A more up-to-date method for 2.6 kernels with udev was outlined on #lunar (for installing from Debian?):

root@rescue ~ # wget http://download.lunar-linux.org/lunar/lunar-1.6.1-i686.iso.bz2
root@rescue ~ # bunzip2 lunar-1.6.1-i686.iso.bz2
root@rescue ~ # mkdir tmp
root@rescue ~ # mount lunar-1.6.1-i686.iso -o loop -t iso9660 tmp
root@rescue ~ # cp -R tmp/* /tmp/
root@rescue ~ # cp -R tmp/.packages /tmp/
root@rescue ~ # cp -R tmp/.lunar-cd /tmp/
root@rescue ~ # cd /tmp/
root@rescue /tmp # mkdir -p proc && mount -t proc proc ./proc
root@rescue /tmp # mkdir -p dev && mount -o bind /dev ./dev
root@rescue /tmp # mkdir -p dev/pts && mount -t devpts devpts ./dev/pts
root@rescue /tmp # cd dev
root@rescue /tmp/dev # ln -sf /proc/self/fd
root@rescue /tmp/dev # ln -sf fd/0 stdin
root@rescue /tmp/dev # ln -sf fd/1 stdout
root@rescue /tmp/dev # ln -sf fd/2 stderr
root@rescue /tmp/dev # rm null
root@rescue /tmp/dev # mknod null c 1 3
root@rescue /tmp/dev # cd

root@rescue ~ # chroot /tmp /sbin/lunar-install

Version numbers obviously change over time, so please check the steps above before you begin.

===Usb bootable lunar===

root@morholt ~ # mkdosfs -F 16 /dev/sda1
mkdosfs 2.11 (12 Mar 2005)
root@morholt ~ # mkdir /mnt/stick
root@morholt ~ # mkdir /mnt/iso
root@morholt ~ # modprobe loop
root@morholt ~ # mount lunar-1.6.4-beta1-i686.iso -o loop /mnt/iso
root@morholt ~ # mount /dev/sda1 /mnt/stick
root@morholt ~ # cp -R /mnt/iso/isolinux /mnt/stick/syslinux
root@morholt ~ # rename isolinux syslinux /mnt/stick/syslinux/isolinux*
root@morholt ~ # ls /mnt/stick/syslinux/
boot.cat f2.txt f4.txt initrd memtest safe syslinux.cfg
f1.txt f3.txt generate-iso.sh linux readme syslinux.bin
root@morholt ~ # cp ~samuel/lunar-1.6.4-beta1-i686.iso /mnt/stick/
root@morholt ~ # syslinux /dev/sda1
root@morholt ~ # fdisk -l /dev/sda
Disk /dev/sda: 1027 MB, 1027603456 bytes
255 heads, 63 sectors/track, 124 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 * 1 125 1003464 b W95 FAT32
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(124, 236, 63)
# following step installs an mbr on the usbstick. Pay attention you need the stick, not the partition on the stick!
root@morholt ~ # dd if=/usr/share/syslinux/mbr.bin of=/dev/sda
# if you want you can install the module ''mbr'' to do the same for you (root@morholt ~ # install-mbr /dev/sda) NOT NEEDED IF YOU DID THE DD!!

Installation:From PXE env

2008-10-22T08:53:54Z

Elangelo:

The '''Preboot eXecution Environment''' ('''PXE''', aka Pre-Execution Environment, or 'pixie') is an environment to boot computers using a network interface card independently of available data storage devices (like hard disks) or installed operating systems.

PXE was introduced as part of the Wired for Management framework by Intel and is described in the [http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf specification (v2.1)] published by Intel and [http://www.systemsoft.com/ Systemsoft] on September 20,1999. It makes use of several network protocols like IP, UDP, DHCP and TFTP and of concepts like GUID/UUID and Universal Network Device Interface and extends the firmware of the PXE client (the computer to be bootstrapped via PXE) with a set of predefined APIs.

The term ''PXE client'' only refers to the role that the machine takes in the PXE boot process. A ''PXE client'' can be a server, desktop, laptop or any other machine that is equipped with a PXE boot code.

As a reference (for sure no advertisement) the servers you can hire @ Hetzner have a PXE environment. The sequence/installation procedure i will describe here was based on experience on one of their machines.

see http://wiki.lunar-linux.org/index.php/Installation:No_CD for an explanation on how to do this... (bottom)

Installation:No CD

2008-10-18T15:52:11Z

Elangelo: /* Usb bootable lunar */

Installation:No CD

2008-10-18T15:51:00Z

Elangelo: /* This is something different */

Installing Lunar-Linux without a CD drive or other removable media isn't really that hard. There are several ways of emulating a cd-rom with linux. There's some easy ways and some hard ways. I'll try to discuss all of them.

''Disclaimer: The methods below might destroy all your data and not work for you at all. Make backups! You yourself are responsible for your own data and system!''

__TOC__

==Booting the ISO from a hard disk partition==

Yes, I'm not kidding. This is by far one of the easiest methods. The idea behind this method is that you can boot the ISO from any media, all you need to do is boot from it. If that means that the ISO is somehow written on your hard disk, and you have a bootloader capable of booting boot sectors (like lilo, grub, windows all can do), then you're in business.

'''requires:'''

* Enough free disk space plus partition big enough for the iso image
* Any installed operating system and tools that allow directly to write to a partition
* A working boot loader like windows' bootloader, lilo or grub

Your best bet is to free some space at the end of your disk. Make sure this is '''larger''' than the lunar iso (somewhere around 350mb). Create a partition and ''copy'' the contents of the iso to that partition:

cat lunar-1.5.1-i686.iso > /dev/hda15

Once done, you should edit your bootloader (be it windows or grub or lilo) and make it boot the boot sector of the iso. Here's the lilo entry you would need:

other = /dev/hda15
label = lunar-1.5.1

That's it! reboot and select the iso entry, and you're ready to go! The lunar installer should start and everything should work just as good as from a CD!

==Chrooting into the ISO==

===Installing from 2.4 kernels with devfs support===

If the above method fails, you can always manually chroot into the ISO and start the installer manually too.

'''requires:'''

* A running linux installation with relatively new 2.4 kernel that has devfs support and allows chroot usage (must be root)

This method is a bit trickier since you will be repartitioning your hard disk from which you just have booted, so you should actually install a '''small''' linux installation somewhere near the end of your disk, losetup/loopmount the iso on there, and then install to partitions that are NOT active/mounted. This might even fail since the kernel doesn't like changing partitions when it's running.

So, start out by getting your 'tiny' linux running anf booting. Preferably install it at the end of your hard disk and re-partition the beginning of your hard disk already for the lunar installation. Reboot your system so the partitions are known by the kernel, and prepare to mount the ISO over loop:

losetup /dev/loop0 lunar-1.5.1-i686.iso
mount /dev/loop0 /mnt -o ro
chroot /mnt /sbin/lunar-install

that's it! The installer should run and you can perform all steps necessary for installing lunar on the remaining partitions. At the end, make sure you don't accidentally overwrite your bootstrap linux installation so you can fallback to it. Beware that you might want to add the bootstrap bootloader info too, in case you want to boot that installation if something goes wrong. Once lunar installs succesfully, you can remove this partition of course.

===Installing from 2.6 kernels with udev support===

===This is something different===
When the previous installation methods fail this is one you can ry as well:

A more up-to-date method for 2.6 kernels with udev was outlined on #lunar (for installing from Debian?):

root@rescue ~ # wget http://download.lunar-linux.org/lunar/lunar-1.6.1-i686.iso.bz2
root@rescue ~ # bunzip2 lunar-1.6.1-i686.iso.bz2
root@rescue ~ # mkdir tmp
root@rescue ~ # mount lunar-1.6.1-i686.iso -o loop -t iso9660 tmp
root@rescue ~ # cp -R tmp/* /tmp/
root@rescue ~ # cp -R tmp/.packages /tmp/
root@rescue ~ # cp -R tmp/.lunar-cd /tmp/
root@rescue ~ # cd /tmp/
root@rescue /tmp # mkdir -p proc && mount -t proc proc ./proc
root@rescue /tmp # mkdir -p dev && mount -o bind /dev ./dev
root@rescue /tmp # mkdir -p dev/pts && mount -t devpts devpts ./dev/pts
root@rescue /tmp # cd dev
root@rescue /tmp/dev # ln -sf /proc/self/fd
root@rescue /tmp/dev # ln -sf fd/0 stdin
root@rescue /tmp/dev # ln -sf fd/1 stdout
root@rescue /tmp/dev # ln -sf fd/2 stderr
root@rescue /tmp/dev # rm null
root@rescue /tmp/dev # mknod null c 1 3
root@rescue /tmp/dev # cd

root@rescue ~ # chroot /tmp /sbin/lunar-install

Version numbers obviously change over time, so please check the steps above before you begin.

===Usb bootable lunar===
root@morholt ~ # mkdosfs -F 16 /dev/sda1
mkdosfs 2.11 (12 Mar 2005)
root@morholt ~ # mkdir /mnt/stick
root@morholt ~ # mkdir /mnt/iso
root@morholt ~ # modprobe loop
root@morholt ~ # mount lunar-1.6.4-beta1-i686.iso -o loop /mnt/iso
root@morholt ~ # mount /dev/sda1 /mnt/stick
root@morholt ~ # cp -R /mnt/iso/isolinux /mnt/stick/syslinux
root@morholt ~ # rename isolinux syslinux /mnt/stick/syslinux/isolinux*
root@morholt ~ # ls /mnt/stick/syslinux/
boot.cat f2.txt f4.txt initrd memtest safe syslinux.cfg
f1.txt f3.txt generate-iso.sh linux readme syslinux.bin
root@morholt ~ # cp ~samuel/lunar-1.6.4-beta1-i686.iso /mnt/stick/
root@morholt ~ # syslinux /dev/sda1
root@morholt ~ # fdisk -l /dev/sda
Disk /dev/sda: 1027 MB, 1027603456 bytes
255 heads, 63 sectors/track, 124 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 * 1 125 1003464 b W95 FAT32
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(124, 236, 63)

Installation:No CD

2008-10-11T19:30:23Z

Elangelo: /* Installing from 2.6 kernels with udev support */

Installation:Software Raid

2008-01-18T14:47:14Z

Elangelo: /* BootLoader */

__TOC__

Software raid is a relatively powerful way of achieving better performance and/or reliability (redundancy). There is no automated way of setting this up in lunar yet but it's fairly easy to do manually.

==Getting started==

First setup your box with the number of hard disks you need and boot the ISO. As soon as you boot into the installer and have selected language and locale stuff, switch to vc/2 and start with the manual part of the software raid setup

==Partitioning==

The easiest way to setup partitioning if you're working with partition raid-components is to partition one disc and copy the contents to another using [[cfdisk]] and [[sfdisk]]:

cfdisk /dev/hda

Setup your partitions and make sure you have some space left over for later to resize and move stuff if needed. '''Make sure you set your partition type as linux-raid-autodetect''' (0xfd). Otherwise you won't be able to boot from the partitions.

cd /tmp
sfdisk -d /dev/hda > dump
sfdisk -i /dev/hdb < dump

This formats the second disc identically to the first one, especially usefull for RAID-1 setups

==Setting up your RAID devices==

go to /tmp and create a new raidtab file:

raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 32
device /dev/hda1
raid-disk 0
device /dev/hdb1
raid-disk 1

Now, since this is sitting on tmpfs you will lose your data if you reboot so be careful. The next step is to initiate the raid device so that it's actively mirroring them (or striping depending on your setup).

mkraid --really-force --configfile /tmp/raidtab /dev/md0

The raid driver will start syncing the discs and you can check progress with:

cat /proc/mdstat

==Formatting the filesystem==

From now on, you'll refer to your disks as /dev/md0 instead of hda1 etc. So the same goes with formatting. You can format and work with the disks even when syncing is in progress:

mkfs.ext3 /dev/md0

It might be a bit slower due to the syncing going on. I advice you to have the unit finish syncing before you reboot, if only to make sure there's no bad sectors on the units and all is OK for normal work.

==Saving your config raidtab==

You should of course save your raidtab file and most likely you will want to save it as /etc/raidtab on the raid-device itself. You'll need to mount it therefore:

mount /dev/hda1 /mnt
mkdir /mnt/etc
cp /tmp/raidtab /mnt/etc/raidtab
umount /mnt

Now you're ready to install lunar in the normal way!

==Installing on RAID==

The last step is to let the normal installer code handle the partitions. For this reason, the installer allows you to pass an arbitrary block device name as an additional hard disk partition. In the partition selection, you select 'Add...' device and enter '/dev/md0'. Make sure you don't format the partition and select the right filesystem. Alternatively, you could have skipped to formatting and let the lunar ISO installer handle it as well.

==BootLoader==

As maybe known, only lilo can directly boot from software raid but with tricks grub can read the underlaying partition on only one of the raid devices, which will obviously not work with striping raid setups. Make sure you pass the proper device names to the lilo.conf. Your mileage may vary.

Referring to the Lunar ISO 1.5.1: to have LILO boot from the software raid, all you have to do is make sure that /etc/lilo.conf has the following lines for boot and root:

boot = /dev/hda # the fysical drive to boot from
root = /dev/md2 # the raid-partition that your root-resides on

'''Note by El_Angelo''': This part is really very confusing.
Just to clarify : the iso will write a lilo.conf that is not correct.
what it will write:
boot = /dev/md0
root = /dev/md2
while it should be:
boot = /dev/hda #or sda or whatever
root = /dev/md2
or even better:
raid-extra-boot=/dev/hda,/dev/hdb
boot = /dev/md0
root = /dev/md1
The last option is actually very safe because it will write a bootloader on both MBR's of you hard drives...
(20080118: i will try to add this to the installer, so ppl no longer have to take this into account)

'''end note'''

If you have an older machine and/or a less intelligent BIOS, you might have to tell LILO where to find the boot-stuff by providing the disk's fysical details. More information on that subject can be found in [http://www.linux.com/howtos/Boot+Root+Raid+LILO-3.shtml#ss3.1 this howto].

==More information==

There are several HOWTO's about software RAID. The newest I could find is [http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Software-RAID-HOWTO.html this one], although I find [http://www.linux.com/howtos/Boot+Root+Raid+LILO.shtml#toc3 this one] more useful.

Installation:From PXE env

2008-01-18T14:24:25Z

Elangelo:

Installation:From PXE env

2008-01-18T14:23:05Z

Elangelo:

Installation:From PXE env

2008-01-18T14:17:43Z

Elangelo:

The '''Preboot eXecution Environment''' ('''PXE''', aka Pre-Execution Environment, or 'pixie') is an environment to [[booting|boot]] [[computer]]s using a [[network interface card]] independently of available [[data storage device]]s (like [[hard disk]]s) or installed [[operating system]]s.

{{for|a high-level overview of network booting|Network booting}}

PXE was introduced as part of the [[Wired for Management]] framework by [[Intel]] and is described in the [http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf specification (v2.1)] published by Intel and [http://www.systemsoft.com/ Systemsoft] on [[September 20]],[[1999]]. It makes use of several [[network protocol]]s like [[Internet Protocol|IP]], [[User Datagram Protocol|UDP]], [[Dynamic Host Configuration Protocol|DHCP]] and [[Trivial File Transfer Protocol|TFTP]] and of concepts like [[Globally Unique Identifier|GUID]]/[[Universally Unique Identifier|UUID]] and [[Universal Network Device Interface]] and extends the [[firmware]] of the PXE [[Client (Computing)|client]] (the computer to be bootstrapped via PXE) with a set of predefined [[Application Programming Interface|APIs]].

The term ''PXE client'' only refers to the role that the machine takes in the PXE boot process. A ''PXE client'' can be a server, desktop, laptop or any other machine that is equipped with a PXE boot code.

Installation:Software Raid

2008-01-18T14:13:49Z

Elangelo: /* BootLoader */

__TOC__

Software raid is a relatively powerful way of achieving better performance and/or reliability (redundancy). There is no automated way of setting this up in lunar yet but it's fairly easy to do manually.

==Getting started==

First setup your box with the number of hard disks you need and boot the ISO. As soon as you boot into the installer and have selected language and locale stuff, switch to vc/2 and start with the manual part of the software raid setup

==Partitioning==

The easiest way to setup partitioning if you're working with partition raid-components is to partition one disc and copy the contents to another using [[cfdisk]] and [[sfdisk]]:

cfdisk /dev/hda

Setup your partitions and make sure you have some space left over for later to resize and move stuff if needed. '''Make sure you set your partition type as linux-raid-autodetect''' (0xfd). Otherwise you won't be able to boot from the partitions.

cd /tmp
sfdisk -d /dev/hda > dump
sfdisk -i /dev/hdb < dump

This formats the second disc identically to the first one, especially usefull for RAID-1 setups

==Setting up your RAID devices==

go to /tmp and create a new raidtab file:

raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 32
device /dev/hda1
raid-disk 0
device /dev/hdb1
raid-disk 1

Now, since this is sitting on tmpfs you will lose your data if you reboot so be careful. The next step is to initiate the raid device so that it's actively mirroring them (or striping depending on your setup).

mkraid --really-force --configfile /tmp/raidtab /dev/md0

The raid driver will start syncing the discs and you can check progress with:

cat /proc/mdstat

==Formatting the filesystem==

From now on, you'll refer to your disks as /dev/md0 instead of hda1 etc. So the same goes with formatting. You can format and work with the disks even when syncing is in progress:

mkfs.ext3 /dev/md0

It might be a bit slower due to the syncing going on. I advice you to have the unit finish syncing before you reboot, if only to make sure there's no bad sectors on the units and all is OK for normal work.

==Saving your config raidtab==

You should of course save your raidtab file and most likely you will want to save it as /etc/raidtab on the raid-device itself. You'll need to mount it therefore:

mount /dev/hda1 /mnt
mkdir /mnt/etc
cp /tmp/raidtab /mnt/etc/raidtab
umount /mnt

Now you're ready to install lunar in the normal way!

==Installing on RAID==

The last step is to let the normal installer code handle the partitions. For this reason, the installer allows you to pass an arbitrary block device name as an additional hard disk partition. In the partition selection, you select 'Add...' device and enter '/dev/md0'. Make sure you don't format the partition and select the right filesystem. Alternatively, you could have skipped to formatting and let the lunar ISO installer handle it as well.

==BootLoader==

As maybe known, only lilo can directly boot from software raid but with tricks grub can read the underlaying partition on only one of the raid devices, which will obviously not work with striping raid setups. Make sure you pass the proper device names to the lilo.conf. Your mileage may vary.

Referring to the Lunar ISO 1.5.1: to have LILO boot from the software raid, all you have to do is make sure that /etc/lilo.conf has the following lines for boot and root:

boot = /dev/hda # the fysical drive to boot from
root = /dev/md2 # the raid-partition that your root-resides on

'''Note by El_Angelo''': This part is really very confusing.
Just to clarify : the iso will write a lilo.conf that is not correct.
what it will write:
boot = /dev/md0
root = /dev/md2
while it should be:
boot = /dev/hda #or sda or whatever
root = /dev/md2
'''end note'''

If you have an older machine and/or a less intelligent BIOS, you might have to tell LILO where to find the boot-stuff by providing the disk's fysical details. More information on that subject can be found in [http://www.linux.com/howtos/Boot+Root+Raid+LILO-3.shtml#ss3.1 this howto].

==More information==

There are several HOWTO's about software RAID. The newest I could find is [http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Software-RAID-HOWTO.html this one], although I find [http://www.linux.com/howtos/Boot+Root+Raid+LILO.shtml#toc3 this one] more useful.

Installation:Software Raid

2008-01-18T14:13:20Z

Elangelo: /* BootLoader */

__TOC__

Software raid is a relatively powerful way of achieving better performance and/or reliability (redundancy). There is no automated way of setting this up in lunar yet but it's fairly easy to do manually.

==Getting started==

First setup your box with the number of hard disks you need and boot the ISO. As soon as you boot into the installer and have selected language and locale stuff, switch to vc/2 and start with the manual part of the software raid setup

==Partitioning==

The easiest way to setup partitioning if you're working with partition raid-components is to partition one disc and copy the contents to another using [[cfdisk]] and [[sfdisk]]:

cfdisk /dev/hda

Setup your partitions and make sure you have some space left over for later to resize and move stuff if needed. '''Make sure you set your partition type as linux-raid-autodetect''' (0xfd). Otherwise you won't be able to boot from the partitions.

cd /tmp
sfdisk -d /dev/hda > dump
sfdisk -i /dev/hdb < dump

This formats the second disc identically to the first one, especially usefull for RAID-1 setups

==Setting up your RAID devices==

go to /tmp and create a new raidtab file:

raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 32
device /dev/hda1
raid-disk 0
device /dev/hdb1
raid-disk 1

Now, since this is sitting on tmpfs you will lose your data if you reboot so be careful. The next step is to initiate the raid device so that it's actively mirroring them (or striping depending on your setup).

mkraid --really-force --configfile /tmp/raidtab /dev/md0

The raid driver will start syncing the discs and you can check progress with:

cat /proc/mdstat

==Formatting the filesystem==

From now on, you'll refer to your disks as /dev/md0 instead of hda1 etc. So the same goes with formatting. You can format and work with the disks even when syncing is in progress:

mkfs.ext3 /dev/md0

It might be a bit slower due to the syncing going on. I advice you to have the unit finish syncing before you reboot, if only to make sure there's no bad sectors on the units and all is OK for normal work.

==Saving your config raidtab==

You should of course save your raidtab file and most likely you will want to save it as /etc/raidtab on the raid-device itself. You'll need to mount it therefore:

mount /dev/hda1 /mnt
mkdir /mnt/etc
cp /tmp/raidtab /mnt/etc/raidtab
umount /mnt

Now you're ready to install lunar in the normal way!

==Installing on RAID==

The last step is to let the normal installer code handle the partitions. For this reason, the installer allows you to pass an arbitrary block device name as an additional hard disk partition. In the partition selection, you select 'Add...' device and enter '/dev/md0'. Make sure you don't format the partition and select the right filesystem. Alternatively, you could have skipped to formatting and let the lunar ISO installer handle it as well.

==BootLoader==

As maybe known, only lilo can directly boot from software raid but with tricks grub can read the underlaying partition on only one of the raid devices, which will obviously not work with striping raid setups. Make sure you pass the proper device names to the lilo.conf. Your mileage may vary.

Referring to the Lunar ISO 1.5.1: to have LILO boot from the software raid, all you have to do is make sure that /etc/lilo.conf has the following lines for boot and root:

boot = /dev/hda # the fysical drive to boot from
root = /dev/md2 # the raid-partition that your root-resides on

'''Note by El_Angelo''': This part is really very confusing. Just to clarify stuff: the iso will write a lilo.conf that is not correct.
what it will write:
boot = /dev/md0
root = /dev/md2
while it should be:
boot = /dev/hda #or sda or whatever
root = /dev/md2
'''end note'''

If you have an older machine and/or a less intelligent BIOS, you might have to tell LILO where to find the boot-stuff by providing the disk's fysical details. More information on that subject can be found in [http://www.linux.com/howtos/Boot+Root+Raid+LILO-3.shtml#ss3.1 this howto].

==More information==

There are several HOWTO's about software RAID. The newest I could find is [http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Software-RAID-HOWTO.html this one], although I find [http://www.linux.com/howtos/Boot+Root+Raid+LILO.shtml#toc3 this one] more useful.

Install XOrg7

2007-12-02T11:47:59Z

Elangelo: /* Installation notes */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

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

==Installing XOrg 7.x ==

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

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

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

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

==Installation notes==

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

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

You may however set an arbitary prefix for XOrg incase you do not want it to install to /usr. You may do so by running the following command: 
: <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

2007-09-18T15:41:07Z

Elangelo: /* Missing modules from the XOrg 7.x modular tree */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

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

==Installing XOrg 7.x ==

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

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

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

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

==Installation notes==

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

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

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

The XOrg7 profile is going to create some symlinks on your system: 
: <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

Module Basics

2007-07-04T09:36:27Z

Elangelo: /* The CONFIGURE script */

__TOC__

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

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

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

== Package Build and Install Scripts ==

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

=== The DETAILS script ===

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

MODULE=emacs
VERSION=21.3
SOURCE=$MODULE-$VERSION.tar.gz
SOURCE_URL=$GNU_URL/$MODULE
SOURCE_URL=<nowiki>ftp://ftp.gnu.org/pub/gnu/$MODULE</nowiki>
SOURCE_VFY=sha1:94d7ae9cb3aef05159cfff148265fc9ce0973980
WEB_SITE=<nowiki>http://www.gnu.org/software/emacs</nowiki>
ENTERED=20010922
UPDATED=20020529
SHORT="the extensible, self-documenting real-time display editor"

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

Other SOURCE_URLS in lunar :
* $GNOME_URL : GNOME mirrors
* $GNU_URL : GNU mirrors
* $KDE_URL : KDE mirrors
* $SFORGE_URL : SourceForge mirrors
* $LRESORT_URL : lunar-linux mirrors
* $XFREE86_URL : XFree86 mirrors

Other optional fields :
* If the application does not compile on more than one thread, add: PSAFE="no" or PSAFE=no
* If the tarball is not extracting into the default $MODULE-$VERSION (e.g. emacs-21.7), add: SOURCE_DIRECTORY=$BUILD_DIRECTORY/"$MODULE"_"$VERSION"_src
* If you want your name in the module and be listed as maintainer and like to be notified when somebody modifies the module, add : MAINTAINER=youremailadress
* If you have more than one SOURCE_URL, list them as: SOURCE_URL=, SOURCE_URL[1]=, SOURCE_URL[2]=, ...
* If you have more than one SOURCE, list them as: SOURCE ,SOURCE2, SOURCE3, ... (don't forget to tell the BUILD script what to do with it...) and add a SOURCE1_URL as well...
* If you want to force lunar to use the gcc4 compiler for this module, add: LUNAR_COMPILER=GCC_4_0 or GCC_3_4 for gcc3

Update the UPDATED field only when you have added something that will change the compile behaviour, updated the version or you added configure options... don't change it just for outlining the DETAILS or BUILD or... file, so in general don't force ppl to recompile if all you did what tweaking around a bit...

sha1 checksums are preferred, md5sums can be listed as SOURCE_VFY=md5:

If you find a MAINTAINER field please respect this and notify the person listed there that you will or have updated his module.

With comments, default values:

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

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

SHORT="the extensible, self-documenting real-time display editor"

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

=== The DEPENDS script ===

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

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

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

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

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

Many old modules use '&&' in [[DEPENDS]] to be consistent with [[BUILD]] files, but the '&&' delimiter is not required and new [[DEPENDS]] files should not use it.

'''Aliases'''

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

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

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

=== The CONFLICTS script ===

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

conflicts vim

=== The CONFIGURE script ===

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

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

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

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

mquery ENABLE_FOO "Enable foo?" n "--enable-foo --enable-foo2" "--disable-foo --disable-foo2"

Where "No" would be the default answer for the user. When he chooses to enable-foo, so answer "yes", --enable-foo and --enable-foo2 will get added to the ./configure command in the BUILD script.

=== The PRE_BUILD script ===

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

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

=== The BUILD script ===

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

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

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

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

make &&
prepare_install &&
make install

If you have modules from git,svn or cvs, the ''configure'' script is missing most of the time. You can then use the ''default_cvs_build()'' function. The commands run are:

./autogen.sh --prefix=/usr

it will then call ''default_make()''

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

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

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

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

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

In the examples above, the [[BUILD]] scripts contain multiple commands separated by '&&' to ensure that execution stops as soon as any command fails. The '&&' are 'and' operations: the command after the '&&' will only be run if the one before the '&&' completed successfully. The use of '&&' is '''required''' in multi-command [[BUILD]] scripts.

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

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

=== The POST_BUILD script ===

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

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

=== The POST_INSTALL script ===

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

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

As in the [[BUILD]] scripts, the '&&' represent 'and' operations, but their use in [[POST_INSTALL]] scripts is '''preferred''' rather than '''required'''.

== Package Removal Scripts ==

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

=== The PRE_REMOVE script ===

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

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

=== The POST_REMOVE Script ===

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

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

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

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

Lunar Linux:About

2007-05-09T18:58:43Z

Elangelo:

'''What is Lunar Linux?'''

Lunar is a source based Linux distribution developed by a very talented team of programmers from all over the world, working together to extend the Linux technology into better-tailored and more optimized software for the end user.

Lunar uses and builds upon the Linux kernel, the software started by Linus Torvalds and supported by thousands of programmers worldwide, and offers a unique package management system which builds each software package, or module, from scratch for the machine in which it is being installed.

This is what sets Lunar apart. It makes customization a breeze-- you choose the compile options before a module is built, and install a lean and uncluttered system that has exactly what you need. Nothing more, or less.

Once installed, Lunar is remarkably fast, breaking new ground in flexibility and in the options it offers the individual user.

'''How have you Licensed it?'''

Lunar-Linux and all it's code are licensed under the GPLv2.

'''How does it work?'''

In a nutshell: Lunar installs a complete bootstrap development system on your machine. You then 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.

Lunar's installer is fast and provides full control over the process of installation, including a wide variety of install and rescue tools. The installer provides the user with an interface to compile a custom kernel during installation.

Installing applications is remarkably simple-- type in "lin [package name]" and the system will install the application from the moonbase, our module repository. Don't want it after all? Type "lrm [package name]" and it is gone. Lunar has a unique shell-based Application Management System which handles the dependencies when installing software. There is no "dependency hell"-- if there are other things the system needs to install a particular application, the AMS will simply find them for you.

Updating lunar is a matter of one single command, lunar update. It fetches an updated moonbase, checks if there were any updated modules and builds those. The AMS is network aware and uses the network to acquire source code. The moonbase and core tools are updated every hour at Lunar-Linux.org.
What is the advantage?

The advantage for the end user is clear: a system that is both robust and stable, and easy to install and maintain without sacrificing variety and flexibility. Lunar has built in integrity checking and a robust self-repairing capability. It also enables system users to develop their own source-packages using the toolset.

Lunar is for everyone. Though it may be difficult for the beginner to administer, it provides you with all the possible features you could want from a Linux distribution. It is incredibly accessible to anyone who has played around with a UNIX system.

All of this presents a rich potential for a user who seeks speed, strong performance, and a system that "works smart".
How can I get started?

If you'd like to start using Lunar, you can easily obtain downloads and ISO images from our web site.

You will also need to download our installation manual, which will walk you through everything you need to know about installing Lunar on your machine. As you begin to put Lunar to work, you will find additional resources in our support section, including our FAQ, our Man Pages, and the archives for the Lunar mailing list.

'''What do I get when I install the ISO?'''

The Lunar-Linux ISO installs only a basic set of packages needed to build the rest. There is no GNOME or KDE, not even XOrg on your machine after you finish installing the ISO. The only service running is secure shell (ssh), and root logins are expressly prohibited! However, once you are done installing and have compiled a kernel once to get the kernel sources in /usr/src/linux, you can just `lin XOrg7` and start installing your desktop from there!

Allthough this may sound spartan to you, there are still a ton of things you can do with a finished installation. You have links, the text-based webbrowser to surf to webpages. Irssi is installed for IRC chat. The ISO also comes preloaded with a whole bunch of networking tools and hardware utilities (lspci, dmidecode, discover) that allow you to figure out what kind of hardware your system has.

'''So what should I do now?'''

You should either go to the download section or read some more in the library. Follow the links below:

* http://lunar-linux.org/
* http://wiki.lunar-linux.org/

''Copyright 2003, Lunar-Linux.org, written by Suzanne Burns''

''history is irrelevant, only the future matters''

Module Basics

2007-02-20T10:38:25Z

Elangelo: /* The BUILD script */

__TOC__

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

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

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

== Package Build and Install Scripts ==

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

=== The DETAILS script ===

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

MODULE=emacs
VERSION=21.3
SOURCE=$MODULE-$VERSION.tar.gz
SOURCE_URL=$GNU_URL/$MODULE
SOURCE_URL=<nowiki>ftp://ftp.gnu.org/pub/gnu/$MODULE</nowiki>
SOURCE_VFY=sha1:94d7ae9cb3aef05159cfff148265fc9ce0973980
WEB_SITE=<nowiki>http://www.gnu.org/software/emacs</nowiki>
ENTERED=20010922
UPDATED=20020529
SHORT="the extensible, self-documenting real-time display editor"

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

Other SOURCE_URLS in lunar :
* $GNOME_URL : GNOME mirrors
* $GNU_URL : GNU mirrors
* $KDE_URL : KDE mirrors
* $SFORGE_URL : SourceForge mirrors
* $LRESORT_URL : lunar-linux mirrors
* $XFREE86_URL : XFree86 mirrors

Other optional fields :
* If the application does not compile on more than one thread, add: PSAFE="no" or PSAFE=no
* If the tarball is not extracting into the default $MODULE-$VERSION (e.g. emacs-21.7), add: SOURCE_DIRECTORY=$BUILD_DIRECTORY/"$MODULE"_"$VERSION"_src
* If you want your name in the module and be listed as maintainer and like to be notified when somebody modifies the module, add : MAINTAINER=youremailadress
* If you have more than one SOURCE_URL, list them as: SOURCE_URL=, SOURCE_URL[1]=, SOURCE_URL[2]=, ...
* If you have more than one SOURCE, list them as: SOURCE ,SOURCE2, SOURCE3, ... (don't forget to tell the BUILD script what to do with it...) and add a SOURCE1_URL as well...
* If you want to force lunar to use the gcc4 compiler for this module, add: LUNAR_COMPILER=GCC_4_0 or GCC_3_4 for gcc3

Update the UPDATED field only when you have added something that will change the compile behaviour, updated the version or you added configure options... don't change it just for outlining the DETAILS or BUILD or... file, so in general don't force ppl to recompile if all you did what tweaking around a bit...

sha1 checksums are preferred, md5sums can be listed as SOURCE_VFY=md5:

If you find a MAINTAINER field please respect this and notify the person listed there that you will or have updated his module.

With comments, default values:

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

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

SHORT="the extensible, self-documenting real-time display editor"

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

=== The DEPENDS script ===

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

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

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

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

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

the && is not obligatory but makes the file much more readable

'''Aliases'''

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

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

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

=== The CONFLICTS script ===

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

conflicts vim

=== The CONFIGURE script ===

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

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

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

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

=== The PRE_BUILD script ===

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

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

=== The BUILD script ===

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

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

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

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

make &&
prepare_install &&
make install

If you have modules from git,svn or cvs, the ''configure'' script is missing most of the time. You can then use the ''default_cvs_build()'' function. The commands run are:

./autogen.sh --prefix=/usr

it will then call ''default_make()''

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

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

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

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

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

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

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

=== The POST_BUILD script ===

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

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

=== The POST_INSTALL script ===

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

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

== Package Removal Scripts ==

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

=== The PRE_REMOVE script ===

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

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

=== The POST_REMOVE Script ===

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

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

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

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

Howto Articles

2007-02-18T19:07:09Z

Elangelo: /* AIGLX Guide */

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

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

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

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

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

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

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

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

Install AIGLX

2007-02-18T19:06:45Z

Elangelo: Install AIGLX moved to Using AIGLX - Installing Beryl

#REDIRECT [[Using AIGLX - Installing Beryl]]

Howto Articles

2007-02-18T18:59:40Z

Elangelo: /* XGL Guide */

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

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

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

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

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

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

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

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

Install XGL

2007-02-18T18:59:09Z

Elangelo: Install XGL moved to Install AIGLX

#REDIRECT [[Install AIGLX]]

Lunar Linux:FAQ

2007-02-15T12:08:34Z

Elangelo: /* So how should I partition my disk? */

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

__TOC__

==General==

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

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

==Optimizations==

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

'''Answer:'''

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

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

'''Answer:'''

The default sure fire optimizations that are recommended are:

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

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

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

'''Answer:'''

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

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

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

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

'''Answer:'''

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

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

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

'''Answer:'''

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

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

==Installing modules==

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

'''Answer:'''

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

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

'''Answer:'''

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

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

'''Answer:'''

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

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

lin kernel-headers-2.4

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

Otherwise:

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

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

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

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

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

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

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

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

'''Answer:'''

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

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

'''Answer:'''

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

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

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

'''Answer:'''

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

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

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

==Lunar core tools==

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

'''Answer:'''

Try:

lin -r ''MODULE''

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

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

'''Answer:'''

Try doing:

lin -c ''MODULE''

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

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

'''Answer:'''

Simple solution to this is just running:

lin moonbase

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

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

'''Answer:'''

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

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

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

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

'''Answer:'''

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

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

'''Answer:'''

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

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

You can install [[theedge]] by issuing:

lin theedge

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

==Lunar-Linux Installation==

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

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

'''Answer:'''

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

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

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

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

'''Answer:'''

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

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

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

'''Answer:'''

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

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

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

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

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

Now invoke qemu:

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

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

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

==Other==

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

'''Answer:'''

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

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

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

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

'''Answer:'''

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

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

Lunar Linux:Installation/1.5.0

2007-02-15T12:02:56Z

Elangelo: /* Booting 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 sourcecode, using your own custom optimizations.

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

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

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

With that said, we hope you enjoy using Lunar!

==About this installation manual==

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

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

==Getting the ISO==

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

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

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

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

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

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

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

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

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

==Language and keyboard interface Settings==

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

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

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

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

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

It is important to note that you ''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:

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

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

As we mentioned earlier, there is an option in the installation process to set up a swap file in the root partition instead of a swap partition as we have done in our example. The next option after selecting your filesystems is to select a swapfile if you so desire. ''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 neccessary files for you. The installer will display progress as packages are transferred to your system and you'll have some idea how long it will take. On normal machines, this should take about 5 minutes.

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

==Setting Up Your GCC Architecture Optimizations==

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

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

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

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

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

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

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

==Adding Additional GCC Optimizations==

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

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

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

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

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

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

cat /proc/cpuinfo

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

==Configuring Your Bootloader==

=== Configuring LILO ===

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

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

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

boot=/dev/hda1

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

boot=/dev/hda

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

=== Configuring GRUB ===

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

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

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

==Installing kernels==

===Installing a precompiled kernel===

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

===Building Your Customized Linux Kernel===

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

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

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

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

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

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

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

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

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

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

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

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

==Setting Up Networking==

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

==Other settings==

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

==Reboot!==

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

''Have Phun!!''

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

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

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

Install XOrg7

2006-11-07T08:54:59Z

Elangelo: /* Missing modules from the XOrg 7.x modular tree */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

The XOrg7 profile is going to create some symlinks on your system: 
: <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
**appres - list X application resource database
**lbxproxy - Low BandWidth X proxy
**luit - Convert terminal i/o from legacy encodings to UTF-8 (import in moonbase 20061107 - elangelo)
**mkcfm - create summaries of CID font metric files
**oclock - round X clock
**proxymngr - proxy manager service
**scripts - run X command on another system via rsh
**sessreg - Register X sessions in system utmp/utmpx databases
**showfont - show information about X font from font server
**twm - simple window manager
**viewres - graphical class/resource browser for Xt
**xbiff - watch mailboxes for new message delivery
**xclipboard - X clipboard manager
**xdbedizzy - DBE sample
**xditview - display ditroff output
**xdm - list X application resource database
**xf86dga - known unto god
**xfd - display all the characters in an X font
**xfindproxy - locate proxy services
**xfontsel - point and click selection of X11 font names
**xfsinfo - X font server information utility
**xfwp - X Firewall Proxy
**xgc - X graphics demo
**xload - system load average display for X
**xlogo - Draw [old] X logo
**xlsclients - list client applications running on a display
**xmag - magnify parts of the screen
**xphelloworld - Xprint sample applications
**xprehashprinterlist - Rehash list of Xprint printers
**xrx - "Broadway"
**xsetmode - set the mode for an X Input device
**xsetpointer - set an X Input device as the main pointer
**xsm - X Session Manager
**xstdcmap - X standard colormap utility
**xvidtune - video mode tuner for Xorg
*x11-data ==> COMPLETE
*x11-doc
**xorg-docs
**xorg-sgml-doctools
*x11-driver
**xf86-video-sunbw2
**xf86-video-suncg3
**xf86-video-suncg6
**xf86-video-suncg14
**xf86-video-sunffb
**xf86-video-sunleo
**xf86-video-suntcx
**xf86-video-tdfx
**xf86-video-tga
**xf86-video-trident (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

2006-11-06T15:32:07Z

Elangelo: /* Missing modules from the XOrg 7.x modular tree */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

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

Install XOrg7

2006-10-20T07:43:02Z

Elangelo: /* Upgrading from XOrg 6.x */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

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

Install XOrg7

2006-10-20T07:41:57Z

Elangelo: /* Upgrading from XOrg 6.x */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

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

Install XOrg7

2006-10-20T07:41:40Z

Elangelo: /* Upgrading from XOrg 6.x */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

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

Install XOrg7

2006-10-19T10:56:57Z

Elangelo: /* Missing modules from the XOrg 7.x modular tree */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

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

Install XOrg7

2006-10-17T09:15:16Z

Elangelo: /* Upgrading from XOrg 6.x */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

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

Install XOrg7

2006-10-17T08:58:41Z

Elangelo: /* Installing xorg-7.1 */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

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

Install XOrg7

2006-10-17T08:57:42Z

Elangelo: /* Installing xorg-7.0 */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

==Installing XOrg 7.x ==

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

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

Install XOrg7

2006-06-26T07:06:18Z

Elangelo: /* Missing modules from the XOrg 7.x modular tree */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

The XOrg7 profile is going to create some symlinks on your system: 
: <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.

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

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

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

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

Install XOrg7

2006-06-22T14:29:40Z

Elangelo: /* Missing modules from the XOrg 7.x modular tree */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

The XOrg7 profile is going to create some symlinks on your system: 
: <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.

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

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

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

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

Install XOrg7

2006-06-21T12:26:31Z

Elangelo: /* Installing xorg-7.1 */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

===Installing xorg-7.1===

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

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

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

==Installation notes==

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

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

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

The XOrg7 profile is going to create some symlinks on your system: 
: <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.

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

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

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

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

Install XOrg7

2006-06-21T12:25:40Z

Elangelo: /* Missing modules from the XOrg 7.x modular tree */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

===Installing xorg-7.1===

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

Now you're all set for XOrg 7.1. You may now use the 'XOrg7' module to install XOrg 7.1: 
<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 most commonly used prefix would be /usr/X11R7, however, some other prefix inside /opt is entirely possible.

The XOrg7 profile is going to create some symlinks on your system: 
: <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.

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

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

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

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

Install XOrg7

2006-06-21T12:24:49Z

Elangelo: /* Installing XOrg 7.x */

=The path to XOrg7=

==Upgrading from XOrg 6.x==

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

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

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

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

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

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

===Installing xorg-7.1===

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

Now you're all set for XOrg 7.1. You may now use the 'XOrg7' module to install XOrg 7.1: 
<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 most commonly used prefix would be /usr/X11R7, however, some other prefix inside /opt is entirely possible.

The XOrg7 profile is going to create some symlinks on your system: 
: <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.

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

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

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

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

Howto Articles

2006-06-07T13:46:06Z

Elangelo:

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

Howto Articles

2006-06-07T13:45:55Z

Elangelo:

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

Tools:lvu

2006-06-07T07:46:44Z

Elangelo: /* WARRANTY */

=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 held|exiled|expired 

lvu section [section] 

lvu voyeur [delay or $MODULE 

lvu depends $MODULE 

lvu tree $MODULE 

lvu eert $MODULE 

lvu size $MODULE 

lvu 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 general purpose command-line tool for displaying package logs, version information, checking for installed packages, checksums, message digests, maintainer 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=
<dt> alien</dt>
<dd>find and display all files which are not currently tracked by the lunar package management system</dd>

<dt>leafs</dt>

<dd>displays installed $MODULEs that have no explicit dependencies on them orphans or displays installed $MODULEs that are missing required dependencies</dd>

<dt>pam</dt>

<dd>display $MODULEs installed that are pam aware</dd>

<dt>cd $MODULE</dt>

<dd>changes current directory to the given $MODULE and execs a new shell</dd>

<dt>what $MODULE</dt>

<dd>view the long package description</dd>

<dt>where $MODULE</dt>

<dd>display the section a $MODULE belongs to</dd>

<dt>website $MODULE</dt>

<dd>display the URL for the specified $MODULE</dd>

<dt>sources $MODULE</dt>

<dd> list all source files contained in a $MODULE</dd>

<dt>urls $MODULE</dt>

<dd> list all URLs for a $MODULE</dd>

<dt>maintainer $MODULE</dt>

<dd>display the email address of the person currently responsible for maintaining a specified $MODULE</dd>

<dt>version $MODULE</dt>

<dd> display version of $MODULE in moonbase</dd>

<dt>compile $MODULE</dt>

<dd> show the compiler output generated when the $MODULE was built</dd>

<dt>compiler $MODULE</dt>
<dd> display the version of compiler used for creating the ELF files in $MODULEs</dd>

<dt>links $MODULE</dt>

<dd> display the $MODULEs that this $MODULE's ELF binary files actually links to</dd>

<dt>install $MODULE</dt>

<dd> used to determine what files were installed by a $MODULE and where those files are located</dd>

<dt>held</dt>

<dd> display held $MODULEs</dd>

<dt>exiled</dt>

<dd> display exiled $MODULEs</dd>

<dt>expired</dt>

<dd> display a list of $MODULEs which will be updated by a `lunar renew`</dd>

<dt>sum $MODULE</dt>

<dd> print CRC checksums for $MODULEs(s). If no $MODULE is given it defaults to all.</dd>

<dt>md5sum $MODULE</dt>

<dd> print $MODULE MD5 message digests (fingerprints). If no $MODULE is given it default to all</dd>

<dt>export</dt>

<dd> take a snapshot of all $MODULEs currently installed</dd>

<dt>import snapshot</dt>

<dd> restore the snapshot from a previous lvu export command (see the export option)</dd>

<dt>moonbase</dt>

<dd> prints the entire moonbase</dd>

<dt>html</dt>

<dd> prints the entire moonbase in a nice html format</dd>

<dt>updatelog</dt>

<dd> view summary log of previous lunar update</dd>

<dt>activity</dt>

<dd> view the main lunar activity log</dd>

<dt>search "phrase"</dt>

<dd> Searches $MODULEs long descriptions for phrase</dd>

<dt>service port|acronym</dt>

<dd> displays $MODULEs that provide the given service port|acronym</dd>

<dt>newer date</dt>

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

<dt>older date</dt>

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

<dt>from <path/>file</dt>

<dd> find out what $MODULE has $PATH/file installed</dd>

<dt>installed $MODULE</dt>

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

<dt>section $MODULE</dt>

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

<dt>size $MODULE</dt>

<dd> display the size of a given $MODULE or all your installed $MODULEs in KB</dd>

<dt>voyeur $MODULE</dt>

<dd> start looking at what lin is compiling at the moment and outputs it. A $MODULE can be optionally specified.</dd>

<dt>depends $MODULE</dt>

<dd>displays the $MODULEs that explicitly or recursively depend on this $MODULE.</dd>

<dt>tree $MODULE</dt>

<dd>displays a tree of the $MODULE's dependencies.</dd>

<dt>eert $MODULE</dt>

<dd> displays a tree of the $MODULE's reverse dependencies.</dd>

<dt>edit $MODULE</dt>

<dd> 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.</dd>

<dt>unedit $MODULE</dt>

<dd> Discards your 'edit'ed zlocal $MODULE. Works the same as removing it.</dd>

<dt>submit $MODULE</dt>

<dd> Submit a $MODULE to the lunar $MODULE submission list/mail alias. Please only submit tested changes.</dd>

<dt>$MODULE_SCRIPT $MODULE</dt>

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

=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 

=REPORTING BUGS=
Report bugs to <maintainer@lunar-linux.org> or http://bugs.lunar-linux.org/

=SEE ALSO=
lunar(8), lin(8), lrm(8), lget(8), moonbase(1)

=WARRANTY=
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LVU(1)

Tools:lvu

2006-06-07T07:46:36Z

Elangelo: /* SEE ALSO */

Tools:lvu

2006-06-07T07:46:28Z

Elangelo: /* REPORTING BUGS */

Tools:lvu

2006-06-07T07:44:55Z

Elangelo: /* COPYRIGHT */

=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 held|exiled|expired 

lvu section [section] 

lvu voyeur [delay or $MODULE 

lvu depends $MODULE 

lvu tree $MODULE 

lvu eert $MODULE 

lvu size $MODULE 

lvu 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 general purpose command-line tool for displaying package logs, version information, checking for installed packages, checksums, message digests, maintainer 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=
<dt> alien</dt>
<dd>find and display all files which are not currently tracked by the lunar package management system</dd>

<dt>leafs</dt>

<dd>displays installed $MODULEs that have no explicit dependencies on them orphans or displays installed $MODULEs that are missing required dependencies</dd>

<dt>pam</dt>

<dd>display $MODULEs installed that are pam aware</dd>

<dt>cd $MODULE</dt>

<dd>changes current directory to the given $MODULE and execs a new shell</dd>

<dt>what $MODULE</dt>

<dd>view the long package description</dd>

<dt>where $MODULE</dt>

<dd>display the section a $MODULE belongs to</dd>

<dt>website $MODULE</dt>

<dd>display the URL for the specified $MODULE</dd>

<dt>sources $MODULE</dt>

<dd> list all source files contained in a $MODULE</dd>

<dt>urls $MODULE</dt>

<dd> list all URLs for a $MODULE</dd>

<dt>maintainer $MODULE</dt>

<dd>display the email address of the person currently responsible for maintaining a specified $MODULE</dd>

<dt>version $MODULE</dt>

<dd> display version of $MODULE in moonbase</dd>

<dt>compile $MODULE</dt>

<dd> show the compiler output generated when the $MODULE was built</dd>

<dt>compiler $MODULE</dt>
<dd> display the version of compiler used for creating the ELF files in $MODULEs</dd>

<dt>links $MODULE</dt>

<dd> display the $MODULEs that this $MODULE's ELF binary files actually links to</dd>

<dt>install $MODULE</dt>

<dd> used to determine what files were installed by a $MODULE and where those files are located</dd>

<dt>held</dt>

<dd> display held $MODULEs</dd>

<dt>exiled</dt>

<dd> display exiled $MODULEs</dd>

<dt>expired</dt>

<dd> display a list of $MODULEs which will be updated by a `lunar renew`</dd>

<dt>sum $MODULE</dt>

<dd> print CRC checksums for $MODULEs(s). If no $MODULE is given it defaults to all.</dd>

<dt>md5sum $MODULE</dt>

<dd> print $MODULE MD5 message digests (fingerprints). If no $MODULE is given it default to all</dd>

<dt>export</dt>

<dd> take a snapshot of all $MODULEs currently installed</dd>

<dt>import snapshot</dt>

<dd> restore the snapshot from a previous lvu export command (see the export option)</dd>

<dt>moonbase</dt>

<dd> prints the entire moonbase</dd>

<dt>html</dt>

<dd> prints the entire moonbase in a nice html format</dd>

<dt>updatelog</dt>

<dd> view summary log of previous lunar update</dd>

<dt>activity</dt>

<dd> view the main lunar activity log</dd>

<dt>search "phrase"</dt>

<dd> Searches $MODULEs long descriptions for phrase</dd>

<dt>service port|acronym</dt>

<dd> displays $MODULEs that provide the given service port|acronym</dd>

<dt>newer date</dt>

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

<dt>older date</dt>

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

<dt>from <path/>file</dt>

<dd> find out what $MODULE has $PATH/file installed</dd>

<dt>installed $MODULE</dt>

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

<dt>section $MODULE</dt>

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

<dt>size $MODULE</dt>

<dd> display the size of a given $MODULE or all your installed $MODULEs in KB</dd>

<dt>voyeur $MODULE</dt>

<dd> start looking at what lin is compiling at the moment and outputs it. A $MODULE can be optionally specified.</dd>

<dt>depends $MODULE</dt>

<dd>displays the $MODULEs that explicitly or recursively depend on this $MODULE.</dd>

<dt>tree $MODULE</dt>

<dd>displays a tree of the $MODULE's dependencies.</dd>

<dt>eert $MODULE</dt>

<dd> displays a tree of the $MODULE's reverse dependencies.</dd>

<dt>edit $MODULE</dt>

<dd> 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.</dd>

<dt>unedit $MODULE</dt>

<dd> Discards your 'edit'ed zlocal $MODULE. Works the same as removing it.</dd>

<dt>submit $MODULE</dt>

<dd> Submit a $MODULE to the lunar $MODULE submission list/mail alias. Please only submit tested changes.</dd>

<dt>$MODULE_SCRIPT $MODULE</dt>

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

=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 

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

=SEE ALSO=
lunar(8), lin(8), lrm(8), lget(8), moonbase(1)

=WARRANTY=
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LVU(1)

Tools:lvu

2006-06-07T07:44:38Z

Elangelo: /* NAME */

=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 held|exiled|expired 

lvu section [section] 

lvu voyeur [delay or $MODULE 

lvu depends $MODULE 

lvu tree $MODULE 

lvu eert $MODULE 

lvu size $MODULE 

lvu 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 general purpose command-line tool for displaying package logs, version information, checking for installed packages, checksums, message digests, maintainer 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=
<dt> alien</dt>
<dd>find and display all files which are not currently tracked by the lunar package management system</dd>

<dt>leafs</dt>

<dd>displays installed $MODULEs that have no explicit dependencies on them orphans or displays installed $MODULEs that are missing required dependencies</dd>

<dt>pam</dt>

<dd>display $MODULEs installed that are pam aware</dd>

<dt>cd $MODULE</dt>

<dd>changes current directory to the given $MODULE and execs a new shell</dd>

<dt>what $MODULE</dt>

<dd>view the long package description</dd>

<dt>where $MODULE</dt>

<dd>display the section a $MODULE belongs to</dd>

<dt>website $MODULE</dt>

<dd>display the URL for the specified $MODULE</dd>

<dt>sources $MODULE</dt>

<dd> list all source files contained in a $MODULE</dd>

<dt>urls $MODULE</dt>

<dd> list all URLs for a $MODULE</dd>

<dt>maintainer $MODULE</dt>

<dd>display the email address of the person currently responsible for maintaining a specified $MODULE</dd>

<dt>version $MODULE</dt>

<dd> display version of $MODULE in moonbase</dd>

<dt>compile $MODULE</dt>

<dd> show the compiler output generated when the $MODULE was built</dd>

<dt>compiler $MODULE</dt>
<dd> display the version of compiler used for creating the ELF files in $MODULEs</dd>

<dt>links $MODULE</dt>

<dd> display the $MODULEs that this $MODULE's ELF binary files actually links to</dd>

<dt>install $MODULE</dt>

<dd> used to determine what files were installed by a $MODULE and where those files are located</dd>

<dt>held</dt>

<dd> display held $MODULEs</dd>

<dt>exiled</dt>

<dd> display exiled $MODULEs</dd>

<dt>expired</dt>

<dd> display a list of $MODULEs which will be updated by a `lunar renew`</dd>

<dt>sum $MODULE</dt>

<dd> print CRC checksums for $MODULEs(s). If no $MODULE is given it defaults to all.</dd>

<dt>md5sum $MODULE</dt>

<dd> print $MODULE MD5 message digests (fingerprints). If no $MODULE is given it default to all</dd>

<dt>export</dt>

<dd> take a snapshot of all $MODULEs currently installed</dd>

<dt>import snapshot</dt>

<dd> restore the snapshot from a previous lvu export command (see the export option)</dd>

<dt>moonbase</dt>

<dd> prints the entire moonbase</dd>

<dt>html</dt>

<dd> prints the entire moonbase in a nice html format</dd>

<dt>updatelog</dt>

<dd> view summary log of previous lunar update</dd>

<dt>activity</dt>

<dd> view the main lunar activity log</dd>

<dt>search "phrase"</dt>

<dd> Searches $MODULEs long descriptions for phrase</dd>

<dt>service port|acronym</dt>

<dd> displays $MODULEs that provide the given service port|acronym</dd>

<dt>newer date</dt>

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

<dt>older date</dt>

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

<dt>from <path/>file</dt>

<dd> find out what $MODULE has $PATH/file installed</dd>

<dt>installed $MODULE</dt>

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

<dt>section $MODULE</dt>

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

<dt>size $MODULE</dt>

<dd> display the size of a given $MODULE or all your installed $MODULEs in KB</dd>

<dt>voyeur $MODULE</dt>

<dd> start looking at what lin is compiling at the moment and outputs it. A $MODULE can be optionally specified.</dd>

<dt>depends $MODULE</dt>

<dd>displays the $MODULEs that explicitly or recursively depend on this $MODULE.</dd>

<dt>tree $MODULE</dt>

<dd>displays a tree of the $MODULE's dependencies.</dd>

<dt>eert $MODULE</dt>

<dd> displays a tree of the $MODULE's reverse dependencies.</dd>

<dt>edit $MODULE</dt>

<dd> 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.</dd>

<dt>unedit $MODULE</dt>

<dd> Discards your 'edit'ed zlocal $MODULE. Works the same as removing it.</dd>

<dt>submit $MODULE</dt>

<dd> Submit a $MODULE to the lunar $MODULE submission list/mail alias. Please only submit tested changes.</dd>

<dt>$MODULE_SCRIPT $MODULE</dt>

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

=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 

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

=SEE ALSO=
lunar(8), lin(8), lrm(8), lget(8), moonbase(1)

=WARRANTY=
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LVU(1)

Tools:lvu

2006-06-07T07:42:55Z

Elangelo: /* DESCRIPTION */

=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 held|exiled|expired 

lvu section [section] 

lvu voyeur [delay or $MODULE 

lvu depends $MODULE 

lvu tree $MODULE 

lvu eert $MODULE 

lvu size $MODULE 

lvu 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 general purpose command-line tool for displaying package logs, version information, checking for installed packages, checksums, message digests, maintainer 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=
<dt> alien</dt>
<dd>find and display all files which are not currently tracked by the lunar package management system</dd>

<dt>leafs</dt>

<dd>displays installed $MODULEs that have no explicit dependencies on them orphans or displays installed $MODULEs that are missing required dependencies</dd>

<dt>pam</dt>

<dd>display $MODULEs installed that are pam aware</dd>

<dt>cd $MODULE</dt>

<dd>changes current directory to the given $MODULE and execs a new shell</dd>

<dt>what $MODULE</dt>

<dd>view the long package description</dd>

<dt>where $MODULE</dt>

<dd>display the section a $MODULE belongs to</dd>

<dt>website $MODULE</dt>

<dd>display the URL for the specified $MODULE</dd>

<dt>sources $MODULE</dt>

<dd> list all source files contained in a $MODULE</dd>

<dt>urls $MODULE</dt>

<dd> list all URLs for a $MODULE</dd>

<dt>maintainer $MODULE</dt>

<dd>display the email address of the person currently responsible for maintaining a specified $MODULE</dd>

<dt>version $MODULE</dt>

<dd> display version of $MODULE in moonbase</dd>

<dt>compile $MODULE</dt>

<dd> show the compiler output generated when the $MODULE was built</dd>

<dt>compiler $MODULE</dt>
<dd> display the version of compiler used for creating the ELF files in $MODULEs</dd>

<dt>links $MODULE</dt>

<dd> display the $MODULEs that this $MODULE's ELF binary files actually links to</dd>

<dt>install $MODULE</dt>

<dd> used to determine what files were installed by a $MODULE and where those files are located</dd>

<dt>held</dt>

<dd> display held $MODULEs</dd>

<dt>exiled</dt>

<dd> display exiled $MODULEs</dd>

<dt>expired</dt>

<dd> display a list of $MODULEs which will be updated by a `lunar renew`</dd>

<dt>sum $MODULE</dt>

<dd> print CRC checksums for $MODULEs(s). If no $MODULE is given it defaults to all.</dd>

<dt>md5sum $MODULE</dt>

<dd> print $MODULE MD5 message digests (fingerprints). If no $MODULE is given it default to all</dd>

<dt>export</dt>

<dd> take a snapshot of all $MODULEs currently installed</dd>

<dt>import snapshot</dt>

<dd> restore the snapshot from a previous lvu export command (see the export option)</dd>

<dt>moonbase</dt>

<dd> prints the entire moonbase</dd>

<dt>html</dt>

<dd> prints the entire moonbase in a nice html format</dd>

<dt>updatelog</dt>

<dd> view summary log of previous lunar update</dd>

<dt>activity</dt>

<dd> view the main lunar activity log</dd>

<dt>search "phrase"</dt>

<dd> Searches $MODULEs long descriptions for phrase</dd>

<dt>service port|acronym</dt>

<dd> displays $MODULEs that provide the given service port|acronym</dd>

<dt>newer date</dt>

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

<dt>older date</dt>

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

<dt>from <path/>file</dt>

<dd> find out what $MODULE has $PATH/file installed</dd>

<dt>installed $MODULE</dt>

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

<dt>section $MODULE</dt>

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

<dt>size $MODULE</dt>

<dd> display the size of a given $MODULE or all your installed $MODULEs in KB</dd>

<dt>voyeur $MODULE</dt>

<dd> start looking at what lin is compiling at the moment and outputs it. A $MODULE can be optionally specified.</dd>

<dt>depends $MODULE</dt>

<dd>displays the $MODULEs that explicitly or recursively depend on this $MODULE.</dd>

<dt>tree $MODULE</dt>

<dd>displays a tree of the $MODULE's dependencies.</dd>

<dt>eert $MODULE</dt>

<dd> displays a tree of the $MODULE's reverse dependencies.</dd>

<dt>edit $MODULE</dt>

<dd> 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.</dd>

<dt>unedit $MODULE</dt>

<dd> Discards your 'edit'ed zlocal $MODULE. Works the same as removing it.</dd>

<dt>submit $MODULE</dt>

<dd> Submit a $MODULE to the lunar $MODULE submission list/mail alias. Please only submit tested changes.</dd>

<dt>$MODULE_SCRIPT $MODULE</dt>

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

=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 

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

=SEE ALSO=
lunar(8), lin(8), lrm(8), lget(8), moonbase(1)

=WARRANTY=
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LVU(1)

Tools:lvu

2006-06-07T07:38:48Z

Elangelo: /* OPTIONS */

=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 held|exiled|expired 

lvu section [section] 

lvu voyeur [delay or $MODULE 

lvu depends $MODULE 

lvu tree $MODULE 

lvu eert $MODULE 

lvu size $MODULE 

lvu 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
general purpose command-line tool for displaying package logs, version
information, checking for installed packages, checksums, message
digests, maintainer 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 soft-
ware catalogue. It can even take and retrieve snapshots of currently
installed packages for easy duplication.

=OPTIONS=
<dt> alien</dt>
<dd>find and display all files which are not currently tracked by the lunar package management system</dd>

<dt>leafs</dt>

<dd>displays installed $MODULEs that have no explicit dependencies on them orphans or displays installed $MODULEs that are missing required dependencies</dd>

<dt>pam</dt>

<dd>display $MODULEs installed that are pam aware</dd>

<dt>cd $MODULE</dt>

<dd>changes current directory to the given $MODULE and execs a new shell</dd>

<dt>what $MODULE</dt>

<dd>view the long package description</dd>

<dt>where $MODULE</dt>

<dd>display the section a $MODULE belongs to</dd>

<dt>website $MODULE</dt>

<dd>display the URL for the specified $MODULE</dd>

<dt>sources $MODULE</dt>

<dd> list all source files contained in a $MODULE</dd>

<dt>urls $MODULE</dt>

<dd> list all URLs for a $MODULE</dd>

<dt>maintainer $MODULE</dt>

<dd>display the email address of the person currently responsible for maintaining a specified $MODULE</dd>

<dt>version $MODULE</dt>

<dd> display version of $MODULE in moonbase</dd>

<dt>compile $MODULE</dt>

<dd> show the compiler output generated when the $MODULE was built</dd>

<dt>compiler $MODULE</dt>
<dd> display the version of compiler used for creating the ELF files in $MODULEs</dd>

<dt>links $MODULE</dt>

<dd> display the $MODULEs that this $MODULE's ELF binary files actually links to</dd>

<dt>install $MODULE</dt>

<dd> used to determine what files were installed by a $MODULE and where those files are located</dd>

<dt>held</dt>

<dd> display held $MODULEs</dd>

<dt>exiled</dt>

<dd> display exiled $MODULEs</dd>

<dt>expired</dt>

<dd> display a list of $MODULEs which will be updated by a `lunar renew`</dd>

<dt>sum $MODULE</dt>

<dd> print CRC checksums for $MODULEs(s). If no $MODULE is given it defaults to all.</dd>

<dt>md5sum $MODULE</dt>

<dd> print $MODULE MD5 message digests (fingerprints). If no $MODULE is given it default to all</dd>

<dt>export</dt>

<dd> take a snapshot of all $MODULEs currently installed</dd>

<dt>import snapshot</dt>

<dd> restore the snapshot from a previous lvu export command (see the export option)</dd>

<dt>moonbase</dt>

<dd> prints the entire moonbase</dd>

<dt>html</dt>

<dd> prints the entire moonbase in a nice html format</dd>

<dt>updatelog</dt>

<dd> view summary log of previous lunar update</dd>

<dt>activity</dt>

<dd> view the main lunar activity log</dd>

<dt>search "phrase"</dt>

<dd> Searches $MODULEs long descriptions for phrase</dd>

<dt>service port|acronym</dt>

<dd> displays $MODULEs that provide the given service port|acronym</dd>

<dt>newer date</dt>

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

<dt>older date</dt>

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

<dt>from <path/>file</dt>

<dd> find out what $MODULE has $PATH/file installed</dd>

<dt>installed $MODULE</dt>

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

<dt>section $MODULE</dt>

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

<dt>size $MODULE</dt>

<dd> display the size of a given $MODULE or all your installed $MODULEs in KB</dd>

<dt>voyeur $MODULE</dt>

<dd> start looking at what lin is compiling at the moment and outputs it. A $MODULE can be optionally specified.</dd>

<dt>depends $MODULE</dt>

<dd>displays the $MODULEs that explicitly or recursively depend on this $MODULE.</dd>

<dt>tree $MODULE</dt>

<dd>displays a tree of the $MODULE's dependencies.</dd>

<dt>eert $MODULE</dt>

<dd> displays a tree of the $MODULE's reverse dependencies.</dd>

<dt>edit $MODULE</dt>

<dd> 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.</dd>

<dt>unedit $MODULE</dt>

<dd> Discards your 'edit'ed zlocal $MODULE. Works the same as removing it.</dd>

<dt>submit $MODULE</dt>

<dd> Submit a $MODULE to the lunar $MODULE submission list/mail alias. Please only submit tested changes.</dd>

<dt>$MODULE_SCRIPT $MODULE</dt>

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

=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 

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

=SEE ALSO=
lunar(8), lin(8), lrm(8), lget(8), moonbase(1)

=WARRANTY=
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LVU(1)

Tools:lvu

2006-06-07T07:38:00Z

Elangelo: /* OPTIONS */

=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 held|exiled|expired 

lvu section [section] 

lvu voyeur [delay or $MODULE 

lvu depends $MODULE 

lvu tree $MODULE 

lvu eert $MODULE 

lvu size $MODULE 

lvu 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
general purpose command-line tool for displaying package logs, version
information, checking for installed packages, checksums, message
digests, maintainer 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 soft-
ware catalogue. It can even take and retrieve snapshots of currently
installed packages for easy duplication.

=OPTIONS=
<dt> alien</dt>
<dd>find and display all files which are not currently tracked by the lunar package management system</dd>

<dt>leafs</dt>

<dd>displays installed modules that have no explicit dependencies on them orphans or displays installed modules that are missing required dependencies</dd>

<dt>pam</dt>

<dd>display modules installed that are pam aware</dd>

<dt>cd module</dt>

<dd>changes current directory to the given module and execs a new shell</dd>

<dt>what module</dt>

<dd>view the long package description</dd>

<dt>where module</dt>

<dd>display the section a module belongs to</dd>

<dt>website module</dt>

<dd>display the URL for the specified module</dd>

<dt>sources module</dt>

<dd> list all source files contained in a module</dd>

<dt>urls module</dt>

<dd> list all URLs for a module</dd>

<dt>maintainer module</dt>

<dd>display the email address of the person currently responsible for maintaining a specified module</dd>

<dt>version module</dt>

<dd> display version of module in moonbase</dd>

<dt>compile module</dt>

<dd> show the compiler output generated when the module was built</dd>

<dt>compiler module</dt>
<dd> display the version of compiler used for creating the ELF files in modules</dd>

<dt>links module</dt>

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

<dt>install module</dt>

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

<dt>held</dt>

<dd> display held modules</dd>

<dt>exiled</dt>

<dd> display exiled modules</dd>

<dt>expired</dt>

<dd> display a list of modules which will be updated by a `lunar renew`</dd>

<dt>sum $MODULE</dt>

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

<dt>md5sum $MODULE</dt>

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

<dt>export</dt>

<dd> take a snapshot of all modules currently installed</dd>

<dt>import snapshot</dt>

<dd> restore the snapshot from a previous lvu export command (see the export option)</dd>

<dt>moonbase</dt>

<dd> prints the entire moonbase</dd>

<dt>html</dt>

<dd> prints the entire moonbase in a nice html format</dd>

<dt>updatelog</dt>

<dd> view summary log of previous lunar update</dd>

<dt>activity</dt>

<dd> view the main lunar activity log</dd>

<dt>search "phrase"</dt>

<dd> Searches modules long descriptions for phrase</dd>

<dt>service port|acronym</dt>

<dd> displays modules that provide the given service port|acronym</dd>

<dt>newer date</dt>

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

<dt>older date</dt>

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

<dt>from <path/>file</dt>

<dd> find out what module has $PATH/file installed</dd>

<dt>installed $MODULE</dt>

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

<dt>section $MODULE</dt>

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

<dt>size $MODULE</dt>

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

<dt>voyeur $MODULE</dt>

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

<dt>depends $MODULE</dt>

<dd>displays the modules that explicitly or recursively depend on this module.</dd>

<dt>tree $MODULE</dt>

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

<dt>eert $MODULE</dt>

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

<dt>edit $MODULE</dt>

<dd> 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.</dd>

<dt>unedit $MODULE</dt>

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

<dt>submit $MODULE</dt>

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

<dt>$MODULE_SCRIPT $MODULE</dt>

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

=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 

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

=SEE ALSO=
lunar(8), lin(8), lrm(8), lget(8), moonbase(1)

=WARRANTY=
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LVU(1)

Tools:lvu

2006-06-07T07:35:52Z

Elangelo: /* OPTIONS */

=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 held|exiled|expired 

lvu section [section] 

lvu voyeur [delay or $MODULE 

lvu depends $MODULE 

lvu tree $MODULE 

lvu eert $MODULE 

lvu size $MODULE 

lvu 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
general purpose command-line tool for displaying package logs, version
information, checking for installed packages, checksums, message
digests, maintainer 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 soft-
ware catalogue. It can even take and retrieve snapshots of currently
installed packages for easy duplication.

=OPTIONS=
<dt> alien</dt>
<dd>find and display all files which are not currently tracked by the lunar package management system</dd>

<dt>leafs</dt>

<dd>displays installed modules that have no explicit dependencies on them orphans or displays installed modules that are missing required dependencies</dd>

<dt>pam</dt>

<dd>display modules installed that are pam aware</dd>

<dt>cd module</dt>

<dd>changes current directory to the given module and execs a new shell</dd>

<dt>what module</dt>

<dd>view the long package description</dd>

<dt>where module</dt>

<dd>display the section a module belongs to</dd>

<dt>website module</dt>

<dd>display the URL for the specified module</dd>

<dt>sources module</dt>

<dd> list all source files contained in a module</dd>

<dt>urls module</dt>

<dd> list all URLs for a module</dd>

<dt>maintainer module</dt>

<dd>display the email address of the person currently responsible for maintaining a specified module</dd>

<dt>version module</dt>

<dd> display version of module in moonbase</dd>

<dt>compile module</dt>

<dd> show the compiler output generated when the module was built</dd>

<dt>compiler module</dt>
<dd> display the version of compiler used for creating the ELF files in modules</dd>

<dt>links module</dt>

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

<dt>install module</dt>

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

<dt>held</dt>

<dd> display held modules</dd>

<dt>exiled</dt>

<dd> display exiled modules</dd>

<dt>expired</dt>

<dd> display a list of modules which will be updated by a `lunar renew`</dd>

<dt>sum $MODULE</dt>

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

<dt>md5sum $MODULE</dt>

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

<dt>export</dt>

<dd> take a snapshot of all modules currently installed</dd>

<dt>import snapshot</dt>

<dd> restore the snapshot from a previous lvu export command (see the export option)</dd>

<dt>moonbase</dt>

<dd> prints the entire moonbase</dd>

<dt>html</dt>

<dd> prints the entire moonbase in a nice html format</dd>

<dt>updatelog</dt>

<dd> view summary log of previous lunar update</dd>

<dt>activity</dt>

<dd> view the main lunar activity log</dd>

<dt>search "phrase"</dt>

<dd> Searches modules long descriptions for phrase</dd>

<dt>service port|acronym</dt>

<dd> displays modules that provide the given service port|acronym</dd>

<dt>newer date</dt>

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

<dt>older date</dt>

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

<dt>from <path/>file</dt>

<dd> find out what module has $PATH/file installed</dd>

<dt>installed $MODULE</dt>

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

<dt>section $MODULE</dt>

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

<dt>size $MODULE</dt>

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

<dt>voyeur $MODULE</dt>

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

<dt>depends $MODULE</dt>

<dd>displays the modules that explicitly or recursively depend on this module.</dd>

<dt>tree $MODULE</dt>

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

<dt>eert $MODULE</dt>

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

<dt>edit $MODULE</dt>

<dd> 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.</dd>

<dt>unedit $MODULE</dt>

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

<dt>submit $MODULE</dt>

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

<dt>$MODULE_SCRIPT $MODULE</dt>

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

=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 

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

=SEE ALSO=
lunar(8), lin(8), lrm(8), lget(8), moonbase(1)

=WARRANTY=
This is free software with ABSOLUTELY NO WARRANTY

Lunar Linux August 2003 LVU(1)