Lunar Linux - User contributions [en]

User:Keitekk

2012-02-23T00:24:09Z

Keitekk: Removing all content from page

Miscellaneous:32BitChroot

2012-02-23T00:19:19Z

Keitekk: /* Changelog: */

This is an Article about running a 32bit Chroot of Lunar Linux within 64bit Lunar Linux. It's getting updated sometimes and should work on different Distributions, too.

==Lunar Linux 32 Bit Chroot within native 64 Bit Environment==

===Changelog:===
* (23.02.12) Updated init script to conform with Lunar/LSB (keios)
* (20.02.12) Added 32bit-kernel configuration and prompt customization tidbits (keios)
* (22.02.11) Paths of qt4 changed, changed howto accordingly (for skype), fonts needs mkfontscale and mkfontdir (added), added section about ATI graphiccards (3d acceleration), some smaller adjustments.
* (29.10.10) Added bdftopcf to list of fonts, without that, fonts won't compile (thx to cavalier for helping to find out)
* (29.10.10) Added instructions regarding the kernel
* (29.10.10) Added new (with current applications installed) image (lunarlinuxchroot.tar.bz2)
* (29.10.10) Added some information at the Test-Stage
* (29.10.10) Added little side note about lunar optimize in chrooted-environments
* (29.10.10) Added little notice about the "unofficial image"
* (11.08.09) Added some Information (Thanks to beko)
* (10.07.09) 3D Acceleration howto was wrong, corrected thx to Raedwulf for pointing out :)
* (10.07.09) I rewrote some parts to a hopefully nicer english.

===Todo:===
* Bash Script which performs the actions below automatically

==Installation==

===Why===
Because. As Lunar Linux is 32bit or 64bit and not multilib, you have to use a chroot for 32bit. I really dislike this but nobody wanted to put time into multilib yet just because of a few guys which would like that and as every day some more apps work using 64bit, multilib will probably not be that useful at all. Anyway, for those of you who want to use 32bit apps within the 64bit environment, this little howto should help a lot.

===Requirements===
Having an image of a running system could help a lot and reduce the needed time amount. If you like you can use an Image i created originally for use as OpenSolaris Zone. You could also create your own 32bit image (just install 32bit linux using a vm or something and tar cjvf the whole system, without proc, sys, dev..). Anyway, i will explain here how to do it using my image.

== Images ==

These are '''unofficial''' images made by me (wdp).

* http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2 [current] 483M (unpacked 1,8G) - 29.10.2010
* http://www.jeanbruenn.info/downloads/osol_lunar_zone.tar.gz [outdated!] 570M

These images are quite outdated, so you're far better off making your own 32bit image. If you don't, you could have difficulties during the lunar update process below.

===Switch to root (For the Dummies)===
Of course you need to be root to run most of the following commands. If you don't know how to switch to the super user (root) in a Linux System you don't want to deal with this Howto. First learn some Basics. However. You can switch to the super user using the command:
<pre>wdp@yulivee ~ $ su -</pre>

===Setup Environment===
'''Important: The Image listed below''': The image was created to be used as solaris zone, however its quite fine for chrooted environments, too. Please notice that this image is "unofficial" so you won't get official support for it.

I installed my Chroot within /usr/local/32bit you might want to change that, just replace the "export" line to do so and don't forget to replace the path in the config files i'm later showing. The following lines will create the directory for your chroot, download my image and unpack it within that directory, copy over some files from the host to the chroot (like users, passwords, etc) and finally mount some directories from the host within the chroot (like dev, proc, sys, tmp).
<pre>export OC="/usr/local/32bit"
mkdir -p $OC
cd $OC
wget http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2
tar -xjvf lunarlinuxchroot.tar.bz2
cp /etc/hosts $OC/etc/hosts
cp /etc/nsswitch.conf $OC/etc/nsswitch.conf
cp /etc/passwd $OC/etc/passwd
cp /etc/shadow $OC/etc/shadow
cp /etc/resolv.conf $OC/etc/resolv.conf
mount -o bind /dev $OC/dev
mount -o bind /dev/pts $OC/dev/pts
mount -o bind /proc $OC/proc
mount -o bind /sys $OC/sys
mount -o bind /tmp $OC/tmp</pre>

Don't copy your current kernel stuff over to the chroot except for your .config:
<pre>
cp -rva /usr/src/linux/.config $OC/usr/src/
</pre>

=== Tests ===

To enter this chrooted environment, simply type in linux32 chroot $OC

===Test #1===
Within the chroot:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure –host=i686-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared
Thread model: posix
gcc version 4.2.4</pre>
Within the host:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: ../configure –host=x86_64-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared –disable-multilib
Thread model: posix
gcc version 4.2.4</pre>

===Test #2===
Within the chroot:
<pre>wdp@yulivee ~ $ uname -m
i686</pre>
Within the host:
<pre>wdp@yulivee ~ $ uname -m
x86_64</pre>
as you can see - the chroot picks a not-64bit-gcc and uname -m returns not 64bit within the chroot - It's working ;-)

===Setting up the shell prompt===
You might want to ensure you don't accidently mistake the chroot environment for your host or vice-versa. Even if you don't think this could ever happen to you, it almost inevitably will if you keep a lot of terminals open at the same time like me (keios).

So to change your default prompt automatically on entering the chroot, add something like this to your .bashrc:
<pre>
if [ $(uname -m) = "i686" ]; then
# insert whatever works for you between @ and :
export PS1="\u@lunar32:\W> "
else
export PS1="\u@\h:\W> "
fi
</pre>

Your default prompt might look different, in that case customize the snippet as you see fit. If you use a colored prompt, changing the color usually should be enough to remind you.

===Updating the Chroot-System===
My Image might be quite old and it's usually good to have the chroot environment as up to date as the host is. Run the following commands to get new packages/modules:
<pre>wdp@yulivee ~ $ lin moonbase; lin theedge</pre>
Now you can run "lunar" and set some settings. The most important Settings might be the Optimizations. You can either go through: Option -> Optimize Architecture or you run "lunar optimize" at the console.

Modules might need working 32bit kernel headers, so make sure your gcc versions in- and outside the chroot are the same (see Test 1 above). If you need a specific gcc version that's not in the moonbase, use the --want $VERSION option of lin. Then build the kernel - you need the exact same version as you have on your host so you won't run into any trouble when e.g. installing video drivers for 3d acceleration later on:
<pre>root@mari-chan:/$ lin -cr linux-stable</pre>
When it asks you if you want to configure the kernel, say yes. In the menuconfig, use the "Load alternative config" option to load the kernel .config file you've copied to /usr/src earlier. Just enter:
<pre>../.config</pre>

After you've done configuring your lunar installation run:
<pre>wdp@yulivee ~ $ lunar renew</pre>
to update your whole installation. Get a cup of tea or coffee, this might take a while depending on your box and resources. At this state you should have a running 32 Bit Chroot. However we will still need to enhance this a bit. You want for sure X11 within the Chroot.

'''Important Note about lunar optimize''':
If you select optimizations for your chrooted environment, never ever use "native" as cpu optimization, this will break things. Always go with something safe, like i686 for example.

==Enhancing your Chroot Installation==
===X11===
We mounted /tmp from the host to /tmp inside the chroot already. This way we can use the X11 Socket to connect applications within the chroot to our running x11-server within the host. You could also, if this isn’t possible, use TCP Connections. But they come usually with overhead and thus performance of x11 stuff will be bad. Anyway. You don’t need a whole X11-Server within the chroot, just a few x11 libs. Let’s go:
<pre>wdp@linux32 ~ $ lin -cr libX11 fixesproto libXxf86vm libXt libXmu libXi mesa-lib xclock</pre>
This will install some X11 staff and libraries which are needed. You need now to allow X11-Unix-Socket Connections. Within the Chroot Environment edit your /etc/hostname and set "linux32" or something similar, remember this hostname. On the host type in: xhost +local:linux32 (Replace linux32 with the hostname you've set) or you could use "xhost +" which is insecure. Now you can test your X11 using xclock within your Chroot:
<pre>wdp@linux32 ~ $ export DISPLAY=”:0.0″
wdp@linux32 ~ $ xclock</pre>
You see the Clock? Fine it worked :)

===3D Acceleration===

If you want to run 32 Bit Games or Emulators like wine which don't work in native 64 Bit you might want to have 3D Acceleration. The important thing about this is that you have to use exactly the same driver version within your chroot as the driver version in your host, otherwise it will simply not work. Thats why you should try to keep both installations as up to date as possible.

==== nVidia ====

It is really important that you got your kernel files and kernel header from the host, also within the chroot. you can do that by copy (cp) from the host to the chrooted environment or you simply copy over the current kernel configuration to the chroot and compile the kernel within the chroot again. (i will explain this step better when i got more time) - Keep also in mind, by default the kernel is on hold within the lunar installation. you might want to "unhold" it using lvu.

On the Host check which NVIDIA drivers you got installed and what version it is:
<pre>wdp@yulivee ~ $ lvu installed NVIDIA
NVIDIA is not installed
wdp@yulivee ~ $ lvu installed NVIDIA-beta
185.18.14
wdp@yulivee ~ $</pre>
As you can see, i have NVIDIA-beta installed on the host. Within the Chroot i check now whats the current version of NVIDIA-beta within the moonbase using:
<pre>root@yulivee /usr/src # lvu version NVIDIA-beta
185.18.14</pre>
As you can see, it's the same version, so everything is fine, issue:
<pre>lget NVIDIA-beta</pre>
and copy the .run from /var/spool/lunar to /usr/src. Make it executable using chmod a+x file.run and run it finally using ./file.run. Of course you have to replace "file" with the real filename.

It will tell you that you run an X-Server and you have to stop this one first. Thats np, close X11, chroot into your chroot on the console and install NVIDIA. Exit the Chroot, start X11 again and everything is fine and should be done. You have to try around a bit with the NVIDIA Installer.

==== ATI (r600/kms enabled) ====

.

===Home directory===
This is the easiest Task. We just need to mount the home directory with bind:
<pre>mount -o bind /home $OC/home</pre>
Within the Chroot you can “su - username” and you’re in your home directory, without any problems or any flaws.

===Init Script===
These are only examples.. you’ll probably find nicer variants. Anyway, for both scripts you will need a configfile containing at least the variable CHROOTDIR - which should point to your Chroot Directory. Example:

Config
This config will be used by the initscripts below and our “chroot-enter script”.
<pre>$ cat /etc/lunar32chroot.conf
#!/bin/bash

CHROOTDIR="/usr/local/32bit"</pre>
SysVinit:
This Init Script will mount with --bind some needed directories for the chroot and copy some files which you will most likely want to keep up to date, to have permissions and networking working correctly.
<pre>$ cat /etc/init.d/lunar32chroot

#!/bin/bash
#
# lunar32chroot Initializes the 32 Bit lunar chroot
#
# chkconfig: 2345 80 10
# description: Initializes 32 Bit chroot

CONFIGFILE="/etc/lunar32chroot.conf"

start() {

echo "Starting 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Mounting chroot directories..."
mount -o bind /dev $CHROOTDIR/dev >/dev/null &&
mount -o bind /proc $CHROOTDIR/proc >/dev/null &&
mount -o bind /sys $CHROOTDIR/sys >/dev/null &&
mount -o bind /tmp $CHROOTDIR/tmp >/dev/null &&
mount -o bind /home $CHROOTDIR/home >/dev/null &&
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional mounts //TODO: add check
[ -d /dev/pts ] && mount -o bind /dev/pts $CHROOTDIR/dev/pts >/dev/null
[ -d /dev/shm ] && mount -o bind /dev/shm $CHROOTDIR/dev/shm >/dev/null
[ -d /proc/bus/usb ] && mount -o bind /proc/bus/usb $CHROOTDIR/proc/bus/usb >/dev/null

echo -n " Copying essential files..."
cp -afr /etc/resolv.conf $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/passwd $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/shadow $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/group $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/hosts $CHROOTDIR/etc > /dev/null &&
cp -afr /etc/localtime $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/nsswitch.conf $CHROOTDIR/etc >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
}

stop() {

echo "Stopping 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Unmounting 32bit chroot directories..."
umount -fl $CHROOTDIR/home >/dev/null &&
umount -fl $CHROOTDIR/tmp >/dev/null &&
umount -fl $CHROOTDIR/sys >/dev/null &&
umount -f $CHROOTDIR/proc >/dev/null &&
umount -fl $CHROOTDIR/dev >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional unmounts //TODO: add check
[ -d $CHROOTDIR/proc/bus/usb ] && umount -fl $CHROOTDIR/proc/bus/usb >/dev/null
[ -d $CHROOTDIR/dev/shm ] && umount -fl $CHROOTDIR/dev/shm >/dev/null
[ -d $CHROOTDIR/dev/pts ] && umount -fl $CHROOTDIR/dev/pts >/dev/null

}

. /lib/lsb/init-functions

</pre>
Now run “chkconfig --add lunar32chroot” to create the essential init scripts/symlinks for the different runlevels and you’re done.

===Entering Chroot - Script===
With this Script you just need to type “lunar32″ to enter the chroot environment. Keep in mind the "linux32" command should be available on all boxes, you dont need to install additional software. However its part of "util-linux".
<pre>$ cat /usr/bin/lunar32

#!/bin/bash
# little script to reduce some things to just one command
# especially for lazy people like me.

source /etc/lunar32chroot.conf

echo "Entering chroot..."
linux32 chroot "$CHROOTDIR" /bin/bash</pre>

Hint from Beko
Beko has shown me a dirty way (as he said) of doing the same using sudo, thus you can enter the environment without beeing root:
<pre>
linux32 sudo chroot "$CHROOTDIR" /bin/bash -c "su $WHOAMI"
</pre>
Negative Sideeffects: you're landing in / at the start and sudo has to run with NOPASS. Thats why this solution is dirty and might be a security risk. However.. :-) By the way Of course you want to replace $WHOAMI with your username - or a variable containing the current username.

==Applications==
===Fonts===
For most applications you will need some X11 Fonts installed within the Chroot. Its enough if you install these:
<pre>lin -cr mkfontdir mkfontscale bdftopcf font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-75dpi font-adobe-utopia-100dpi font-adobe-utopia-type1 font-bitstream-100dpi font-bitstream-75dpi font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi</pre>
some of them might not be needed, but well doesnt hurt to install them.

===Skype===
If you want to use Skype you will have to install some more libraries and tools:
<pre>cd /var/lib/lunar/moonbase
cp -rva qt4-apps/qt4 zlocal/
cd zlocal/qt4
vim DEPENDS</pre>
Remove this line:
<pre>depends %X</pre>
Finally install needed stuff:
<pre>lin -cr dbus alsa-utils videoproto libXv scrnsaverproto libXScrnSaver qt4</pre>
It might be needed to install dbus-qt3 (not sure) if so, you have to copy the module to zlocal and edit the DEPENDS file (of qt3 and of dbus-qt3) to remove the X Dependecy.

Skype should now work. You might want to look at the "fonts" Section because skype will display broken fonts :)

==Useful Documentation:==
* http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 [English]
* http://ubuntuforums.org/showthread.php?t=24575 [English]
* http://wiki.ubuntuusers.de/32-Bit_chroot [German]
* http://www.debian-administration.org/article/Installing_apps_in_a_32-bit_chroot_in_AMD64_Debian_system [English]

Miscellaneous:32BitChroot

2012-02-23T00:17:40Z

Keitekk: /* Init Script */

This is an Article about running a 32bit Chroot of Lunar Linux within 64bit Lunar Linux. It's getting updated sometimes and should work on different Distributions, too.

==Lunar Linux 32 Bit Chroot within native 64 Bit Environment==

===Changelog:===
* (20.02.12) Added 32bit-kernel configuration and prompt customization tidbits (keios)
* (22.02.11) Paths of qt4 changed, changed howto accordingly (for skype), fonts needs mkfontscale and mkfontdir (added), added section about ATI graphiccards (3d acceleration), some smaller adjustments.
* (29.10.10) Added bdftopcf to list of fonts, without that, fonts won't compile (thx to cavalier for helping to find out)
* (29.10.10) Added instructions regarding the kernel
* (29.10.10) Added new (with current applications installed) image (lunarlinuxchroot.tar.bz2)
* (29.10.10) Added some information at the Test-Stage
* (29.10.10) Added little side note about lunar optimize in chrooted-environments
* (29.10.10) Added little notice about the "unofficial image"
* (11.08.09) Added some Information (Thanks to beko)
* (10.07.09) 3D Acceleration howto was wrong, corrected thx to Raedwulf for pointing out :)
* (10.07.09) I rewrote some parts to a hopefully nicer english.

===Todo:===
* Bash Script which performs the actions below automatically

==Installation==

===Why===
Because. As Lunar Linux is 32bit or 64bit and not multilib, you have to use a chroot for 32bit. I really dislike this but nobody wanted to put time into multilib yet just because of a few guys which would like that and as every day some more apps work using 64bit, multilib will probably not be that useful at all. Anyway, for those of you who want to use 32bit apps within the 64bit environment, this little howto should help a lot.

===Requirements===
Having an image of a running system could help a lot and reduce the needed time amount. If you like you can use an Image i created originally for use as OpenSolaris Zone. You could also create your own 32bit image (just install 32bit linux using a vm or something and tar cjvf the whole system, without proc, sys, dev..). Anyway, i will explain here how to do it using my image.

== Images ==

These are '''unofficial''' images made by me (wdp).

* http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2 [current] 483M (unpacked 1,8G) - 29.10.2010
* http://www.jeanbruenn.info/downloads/osol_lunar_zone.tar.gz [outdated!] 570M

These images are quite outdated, so you're far better off making your own 32bit image. If you don't, you could have difficulties during the lunar update process below.

===Switch to root (For the Dummies)===
Of course you need to be root to run most of the following commands. If you don't know how to switch to the super user (root) in a Linux System you don't want to deal with this Howto. First learn some Basics. However. You can switch to the super user using the command:
<pre>wdp@yulivee ~ $ su -</pre>

===Setup Environment===
'''Important: The Image listed below''': The image was created to be used as solaris zone, however its quite fine for chrooted environments, too. Please notice that this image is "unofficial" so you won't get official support for it.

I installed my Chroot within /usr/local/32bit you might want to change that, just replace the "export" line to do so and don't forget to replace the path in the config files i'm later showing. The following lines will create the directory for your chroot, download my image and unpack it within that directory, copy over some files from the host to the chroot (like users, passwords, etc) and finally mount some directories from the host within the chroot (like dev, proc, sys, tmp).
<pre>export OC="/usr/local/32bit"
mkdir -p $OC
cd $OC
wget http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2
tar -xjvf lunarlinuxchroot.tar.bz2
cp /etc/hosts $OC/etc/hosts
cp /etc/nsswitch.conf $OC/etc/nsswitch.conf
cp /etc/passwd $OC/etc/passwd
cp /etc/shadow $OC/etc/shadow
cp /etc/resolv.conf $OC/etc/resolv.conf
mount -o bind /dev $OC/dev
mount -o bind /dev/pts $OC/dev/pts
mount -o bind /proc $OC/proc
mount -o bind /sys $OC/sys
mount -o bind /tmp $OC/tmp</pre>

Don't copy your current kernel stuff over to the chroot except for your .config:
<pre>
cp -rva /usr/src/linux/.config $OC/usr/src/
</pre>

=== Tests ===

To enter this chrooted environment, simply type in linux32 chroot $OC

===Test #1===
Within the chroot:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure –host=i686-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared
Thread model: posix
gcc version 4.2.4</pre>
Within the host:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: ../configure –host=x86_64-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared –disable-multilib
Thread model: posix
gcc version 4.2.4</pre>

===Test #2===
Within the chroot:
<pre>wdp@yulivee ~ $ uname -m
i686</pre>
Within the host:
<pre>wdp@yulivee ~ $ uname -m
x86_64</pre>
as you can see - the chroot picks a not-64bit-gcc and uname -m returns not 64bit within the chroot - It's working ;-)

===Setting up the shell prompt===
You might want to ensure you don't accidently mistake the chroot environment for your host or vice-versa. Even if you don't think this could ever happen to you, it almost inevitably will if you keep a lot of terminals open at the same time like me (keios).

So to change your default prompt automatically on entering the chroot, add something like this to your .bashrc:
<pre>
if [ $(uname -m) = "i686" ]; then
# insert whatever works for you between @ and :
export PS1="\u@lunar32:\W> "
else
export PS1="\u@\h:\W> "
fi
</pre>

Your default prompt might look different, in that case customize the snippet as you see fit. If you use a colored prompt, changing the color usually should be enough to remind you.

===Updating the Chroot-System===
My Image might be quite old and it's usually good to have the chroot environment as up to date as the host is. Run the following commands to get new packages/modules:
<pre>wdp@yulivee ~ $ lin moonbase; lin theedge</pre>
Now you can run "lunar" and set some settings. The most important Settings might be the Optimizations. You can either go through: Option -> Optimize Architecture or you run "lunar optimize" at the console.

Modules might need working 32bit kernel headers, so make sure your gcc versions in- and outside the chroot are the same (see Test 1 above). If you need a specific gcc version that's not in the moonbase, use the --want $VERSION option of lin. Then build the kernel - you need the exact same version as you have on your host so you won't run into any trouble when e.g. installing video drivers for 3d acceleration later on:
<pre>root@mari-chan:/$ lin -cr linux-stable</pre>
When it asks you if you want to configure the kernel, say yes. In the menuconfig, use the "Load alternative config" option to load the kernel .config file you've copied to /usr/src earlier. Just enter:
<pre>../.config</pre>

After you've done configuring your lunar installation run:
<pre>wdp@yulivee ~ $ lunar renew</pre>
to update your whole installation. Get a cup of tea or coffee, this might take a while depending on your box and resources. At this state you should have a running 32 Bit Chroot. However we will still need to enhance this a bit. You want for sure X11 within the Chroot.

'''Important Note about lunar optimize''':
If you select optimizations for your chrooted environment, never ever use "native" as cpu optimization, this will break things. Always go with something safe, like i686 for example.

==Enhancing your Chroot Installation==
===X11===
We mounted /tmp from the host to /tmp inside the chroot already. This way we can use the X11 Socket to connect applications within the chroot to our running x11-server within the host. You could also, if this isn’t possible, use TCP Connections. But they come usually with overhead and thus performance of x11 stuff will be bad. Anyway. You don’t need a whole X11-Server within the chroot, just a few x11 libs. Let’s go:
<pre>wdp@linux32 ~ $ lin -cr libX11 fixesproto libXxf86vm libXt libXmu libXi mesa-lib xclock</pre>
This will install some X11 staff and libraries which are needed. You need now to allow X11-Unix-Socket Connections. Within the Chroot Environment edit your /etc/hostname and set "linux32" or something similar, remember this hostname. On the host type in: xhost +local:linux32 (Replace linux32 with the hostname you've set) or you could use "xhost +" which is insecure. Now you can test your X11 using xclock within your Chroot:
<pre>wdp@linux32 ~ $ export DISPLAY=”:0.0″
wdp@linux32 ~ $ xclock</pre>
You see the Clock? Fine it worked :)

===3D Acceleration===

If you want to run 32 Bit Games or Emulators like wine which don't work in native 64 Bit you might want to have 3D Acceleration. The important thing about this is that you have to use exactly the same driver version within your chroot as the driver version in your host, otherwise it will simply not work. Thats why you should try to keep both installations as up to date as possible.

==== nVidia ====

It is really important that you got your kernel files and kernel header from the host, also within the chroot. you can do that by copy (cp) from the host to the chrooted environment or you simply copy over the current kernel configuration to the chroot and compile the kernel within the chroot again. (i will explain this step better when i got more time) - Keep also in mind, by default the kernel is on hold within the lunar installation. you might want to "unhold" it using lvu.

On the Host check which NVIDIA drivers you got installed and what version it is:
<pre>wdp@yulivee ~ $ lvu installed NVIDIA
NVIDIA is not installed
wdp@yulivee ~ $ lvu installed NVIDIA-beta
185.18.14
wdp@yulivee ~ $</pre>
As you can see, i have NVIDIA-beta installed on the host. Within the Chroot i check now whats the current version of NVIDIA-beta within the moonbase using:
<pre>root@yulivee /usr/src # lvu version NVIDIA-beta
185.18.14</pre>
As you can see, it's the same version, so everything is fine, issue:
<pre>lget NVIDIA-beta</pre>
and copy the .run from /var/spool/lunar to /usr/src. Make it executable using chmod a+x file.run and run it finally using ./file.run. Of course you have to replace "file" with the real filename.

It will tell you that you run an X-Server and you have to stop this one first. Thats np, close X11, chroot into your chroot on the console and install NVIDIA. Exit the Chroot, start X11 again and everything is fine and should be done. You have to try around a bit with the NVIDIA Installer.

==== ATI (r600/kms enabled) ====

.

===Home directory===
This is the easiest Task. We just need to mount the home directory with bind:
<pre>mount -o bind /home $OC/home</pre>
Within the Chroot you can “su - username” and you’re in your home directory, without any problems or any flaws.

===Init Script===
These are only examples.. you’ll probably find nicer variants. Anyway, for both scripts you will need a configfile containing at least the variable CHROOTDIR - which should point to your Chroot Directory. Example:

Config
This config will be used by the initscripts below and our “chroot-enter script”.
<pre>$ cat /etc/lunar32chroot.conf
#!/bin/bash

CHROOTDIR="/usr/local/32bit"</pre>
SysVinit:
This Init Script will mount with --bind some needed directories for the chroot and copy some files which you will most likely want to keep up to date, to have permissions and networking working correctly.
<pre>$ cat /etc/init.d/lunar32chroot

#!/bin/bash
#
# lunar32chroot Initializes the 32 Bit lunar chroot
#
# chkconfig: 2345 80 10
# description: Initializes 32 Bit chroot

CONFIGFILE="/etc/lunar32chroot.conf"

start() {

echo "Starting 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Mounting chroot directories..."
mount -o bind /dev $CHROOTDIR/dev >/dev/null &&
mount -o bind /proc $CHROOTDIR/proc >/dev/null &&
mount -o bind /sys $CHROOTDIR/sys >/dev/null &&
mount -o bind /tmp $CHROOTDIR/tmp >/dev/null &&
mount -o bind /home $CHROOTDIR/home >/dev/null &&
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional mounts //TODO: add check
[ -d /dev/pts ] && mount -o bind /dev/pts $CHROOTDIR/dev/pts >/dev/null
[ -d /dev/shm ] && mount -o bind /dev/shm $CHROOTDIR/dev/shm >/dev/null
[ -d /proc/bus/usb ] && mount -o bind /proc/bus/usb $CHROOTDIR/proc/bus/usb >/dev/null

echo -n " Copying essential files..."
cp -afr /etc/resolv.conf $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/passwd $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/shadow $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/group $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/hosts $CHROOTDIR/etc > /dev/null &&
cp -afr /etc/localtime $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/nsswitch.conf $CHROOTDIR/etc >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
}

stop() {

echo "Stopping 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Unmounting 32bit chroot directories..."
umount -fl $CHROOTDIR/home >/dev/null &&
umount -fl $CHROOTDIR/tmp >/dev/null &&
umount -fl $CHROOTDIR/sys >/dev/null &&
umount -f $CHROOTDIR/proc >/dev/null &&
umount -fl $CHROOTDIR/dev >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional unmounts //TODO: add check
[ -d $CHROOTDIR/proc/bus/usb ] && umount -fl $CHROOTDIR/proc/bus/usb >/dev/null
[ -d $CHROOTDIR/dev/shm ] && umount -fl $CHROOTDIR/dev/shm >/dev/null
[ -d $CHROOTDIR/dev/pts ] && umount -fl $CHROOTDIR/dev/pts >/dev/null

}

. /lib/lsb/init-functions

</pre>
Now run “chkconfig --add lunar32chroot” to create the essential init scripts/symlinks for the different runlevels and you’re done.

===Entering Chroot - Script===
With this Script you just need to type “lunar32″ to enter the chroot environment. Keep in mind the "linux32" command should be available on all boxes, you dont need to install additional software. However its part of "util-linux".
<pre>$ cat /usr/bin/lunar32

#!/bin/bash
# little script to reduce some things to just one command
# especially for lazy people like me.

source /etc/lunar32chroot.conf

echo "Entering chroot..."
linux32 chroot "$CHROOTDIR" /bin/bash</pre>

Hint from Beko
Beko has shown me a dirty way (as he said) of doing the same using sudo, thus you can enter the environment without beeing root:
<pre>
linux32 sudo chroot "$CHROOTDIR" /bin/bash -c "su $WHOAMI"
</pre>
Negative Sideeffects: you're landing in / at the start and sudo has to run with NOPASS. Thats why this solution is dirty and might be a security risk. However.. :-) By the way Of course you want to replace $WHOAMI with your username - or a variable containing the current username.

==Applications==
===Fonts===
For most applications you will need some X11 Fonts installed within the Chroot. Its enough if you install these:
<pre>lin -cr mkfontdir mkfontscale bdftopcf font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-75dpi font-adobe-utopia-100dpi font-adobe-utopia-type1 font-bitstream-100dpi font-bitstream-75dpi font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi</pre>
some of them might not be needed, but well doesnt hurt to install them.

===Skype===
If you want to use Skype you will have to install some more libraries and tools:
<pre>cd /var/lib/lunar/moonbase
cp -rva qt4-apps/qt4 zlocal/
cd zlocal/qt4
vim DEPENDS</pre>
Remove this line:
<pre>depends %X</pre>
Finally install needed stuff:
<pre>lin -cr dbus alsa-utils videoproto libXv scrnsaverproto libXScrnSaver qt4</pre>
It might be needed to install dbus-qt3 (not sure) if so, you have to copy the module to zlocal and edit the DEPENDS file (of qt3 and of dbus-qt3) to remove the X Dependecy.

Skype should now work. You might want to look at the "fonts" Section because skype will display broken fonts :)

==Useful Documentation:==
* http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 [English]
* http://ubuntuforums.org/showthread.php?t=24575 [English]
* http://wiki.ubuntuusers.de/32-Bit_chroot [German]
* http://www.debian-administration.org/article/Installing_apps_in_a_32-bit_chroot_in_AMD64_Debian_system [English]

Miscellaneous:32BitChroot

2012-02-23T00:15:52Z

Keitekk: /* Init Script */

This is an Article about running a 32bit Chroot of Lunar Linux within 64bit Lunar Linux. It's getting updated sometimes and should work on different Distributions, too.

==Lunar Linux 32 Bit Chroot within native 64 Bit Environment==

===Changelog:===
* (20.02.12) Added 32bit-kernel configuration and prompt customization tidbits (keios)
* (22.02.11) Paths of qt4 changed, changed howto accordingly (for skype), fonts needs mkfontscale and mkfontdir (added), added section about ATI graphiccards (3d acceleration), some smaller adjustments.
* (29.10.10) Added bdftopcf to list of fonts, without that, fonts won't compile (thx to cavalier for helping to find out)
* (29.10.10) Added instructions regarding the kernel
* (29.10.10) Added new (with current applications installed) image (lunarlinuxchroot.tar.bz2)
* (29.10.10) Added some information at the Test-Stage
* (29.10.10) Added little side note about lunar optimize in chrooted-environments
* (29.10.10) Added little notice about the "unofficial image"
* (11.08.09) Added some Information (Thanks to beko)
* (10.07.09) 3D Acceleration howto was wrong, corrected thx to Raedwulf for pointing out :)
* (10.07.09) I rewrote some parts to a hopefully nicer english.

===Todo:===
* Bash Script which performs the actions below automatically

==Installation==

===Why===
Because. As Lunar Linux is 32bit or 64bit and not multilib, you have to use a chroot for 32bit. I really dislike this but nobody wanted to put time into multilib yet just because of a few guys which would like that and as every day some more apps work using 64bit, multilib will probably not be that useful at all. Anyway, for those of you who want to use 32bit apps within the 64bit environment, this little howto should help a lot.

===Requirements===
Having an image of a running system could help a lot and reduce the needed time amount. If you like you can use an Image i created originally for use as OpenSolaris Zone. You could also create your own 32bit image (just install 32bit linux using a vm or something and tar cjvf the whole system, without proc, sys, dev..). Anyway, i will explain here how to do it using my image.

== Images ==

These are '''unofficial''' images made by me (wdp).

* http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2 [current] 483M (unpacked 1,8G) - 29.10.2010
* http://www.jeanbruenn.info/downloads/osol_lunar_zone.tar.gz [outdated!] 570M

These images are quite outdated, so you're far better off making your own 32bit image. If you don't, you could have difficulties during the lunar update process below.

===Switch to root (For the Dummies)===
Of course you need to be root to run most of the following commands. If you don't know how to switch to the super user (root) in a Linux System you don't want to deal with this Howto. First learn some Basics. However. You can switch to the super user using the command:
<pre>wdp@yulivee ~ $ su -</pre>

===Setup Environment===
'''Important: The Image listed below''': The image was created to be used as solaris zone, however its quite fine for chrooted environments, too. Please notice that this image is "unofficial" so you won't get official support for it.

I installed my Chroot within /usr/local/32bit you might want to change that, just replace the "export" line to do so and don't forget to replace the path in the config files i'm later showing. The following lines will create the directory for your chroot, download my image and unpack it within that directory, copy over some files from the host to the chroot (like users, passwords, etc) and finally mount some directories from the host within the chroot (like dev, proc, sys, tmp).
<pre>export OC="/usr/local/32bit"
mkdir -p $OC
cd $OC
wget http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2
tar -xjvf lunarlinuxchroot.tar.bz2
cp /etc/hosts $OC/etc/hosts
cp /etc/nsswitch.conf $OC/etc/nsswitch.conf
cp /etc/passwd $OC/etc/passwd
cp /etc/shadow $OC/etc/shadow
cp /etc/resolv.conf $OC/etc/resolv.conf
mount -o bind /dev $OC/dev
mount -o bind /dev/pts $OC/dev/pts
mount -o bind /proc $OC/proc
mount -o bind /sys $OC/sys
mount -o bind /tmp $OC/tmp</pre>

Don't copy your current kernel stuff over to the chroot except for your .config:
<pre>
cp -rva /usr/src/linux/.config $OC/usr/src/
</pre>

=== Tests ===

To enter this chrooted environment, simply type in linux32 chroot $OC

===Test #1===
Within the chroot:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure –host=i686-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared
Thread model: posix
gcc version 4.2.4</pre>
Within the host:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: ../configure –host=x86_64-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared –disable-multilib
Thread model: posix
gcc version 4.2.4</pre>

===Test #2===
Within the chroot:
<pre>wdp@yulivee ~ $ uname -m
i686</pre>
Within the host:
<pre>wdp@yulivee ~ $ uname -m
x86_64</pre>
as you can see - the chroot picks a not-64bit-gcc and uname -m returns not 64bit within the chroot - It's working ;-)

===Setting up the shell prompt===
You might want to ensure you don't accidently mistake the chroot environment for your host or vice-versa. Even if you don't think this could ever happen to you, it almost inevitably will if you keep a lot of terminals open at the same time like me (keios).

So to change your default prompt automatically on entering the chroot, add something like this to your .bashrc:
<pre>
if [ $(uname -m) = "i686" ]; then
# insert whatever works for you between @ and :
export PS1="\u@lunar32:\W> "
else
export PS1="\u@\h:\W> "
fi
</pre>

Your default prompt might look different, in that case customize the snippet as you see fit. If you use a colored prompt, changing the color usually should be enough to remind you.

===Updating the Chroot-System===
My Image might be quite old and it's usually good to have the chroot environment as up to date as the host is. Run the following commands to get new packages/modules:
<pre>wdp@yulivee ~ $ lin moonbase; lin theedge</pre>
Now you can run "lunar" and set some settings. The most important Settings might be the Optimizations. You can either go through: Option -> Optimize Architecture or you run "lunar optimize" at the console.

Modules might need working 32bit kernel headers, so make sure your gcc versions in- and outside the chroot are the same (see Test 1 above). If you need a specific gcc version that's not in the moonbase, use the --want $VERSION option of lin. Then build the kernel - you need the exact same version as you have on your host so you won't run into any trouble when e.g. installing video drivers for 3d acceleration later on:
<pre>root@mari-chan:/$ lin -cr linux-stable</pre>
When it asks you if you want to configure the kernel, say yes. In the menuconfig, use the "Load alternative config" option to load the kernel .config file you've copied to /usr/src earlier. Just enter:
<pre>../.config</pre>

After you've done configuring your lunar installation run:
<pre>wdp@yulivee ~ $ lunar renew</pre>
to update your whole installation. Get a cup of tea or coffee, this might take a while depending on your box and resources. At this state you should have a running 32 Bit Chroot. However we will still need to enhance this a bit. You want for sure X11 within the Chroot.

'''Important Note about lunar optimize''':
If you select optimizations for your chrooted environment, never ever use "native" as cpu optimization, this will break things. Always go with something safe, like i686 for example.

==Enhancing your Chroot Installation==
===X11===
We mounted /tmp from the host to /tmp inside the chroot already. This way we can use the X11 Socket to connect applications within the chroot to our running x11-server within the host. You could also, if this isn’t possible, use TCP Connections. But they come usually with overhead and thus performance of x11 stuff will be bad. Anyway. You don’t need a whole X11-Server within the chroot, just a few x11 libs. Let’s go:
<pre>wdp@linux32 ~ $ lin -cr libX11 fixesproto libXxf86vm libXt libXmu libXi mesa-lib xclock</pre>
This will install some X11 staff and libraries which are needed. You need now to allow X11-Unix-Socket Connections. Within the Chroot Environment edit your /etc/hostname and set "linux32" or something similar, remember this hostname. On the host type in: xhost +local:linux32 (Replace linux32 with the hostname you've set) or you could use "xhost +" which is insecure. Now you can test your X11 using xclock within your Chroot:
<pre>wdp@linux32 ~ $ export DISPLAY=”:0.0″
wdp@linux32 ~ $ xclock</pre>
You see the Clock? Fine it worked :)

===3D Acceleration===

If you want to run 32 Bit Games or Emulators like wine which don't work in native 64 Bit you might want to have 3D Acceleration. The important thing about this is that you have to use exactly the same driver version within your chroot as the driver version in your host, otherwise it will simply not work. Thats why you should try to keep both installations as up to date as possible.

==== nVidia ====

It is really important that you got your kernel files and kernel header from the host, also within the chroot. you can do that by copy (cp) from the host to the chrooted environment or you simply copy over the current kernel configuration to the chroot and compile the kernel within the chroot again. (i will explain this step better when i got more time) - Keep also in mind, by default the kernel is on hold within the lunar installation. you might want to "unhold" it using lvu.

On the Host check which NVIDIA drivers you got installed and what version it is:
<pre>wdp@yulivee ~ $ lvu installed NVIDIA
NVIDIA is not installed
wdp@yulivee ~ $ lvu installed NVIDIA-beta
185.18.14
wdp@yulivee ~ $</pre>
As you can see, i have NVIDIA-beta installed on the host. Within the Chroot i check now whats the current version of NVIDIA-beta within the moonbase using:
<pre>root@yulivee /usr/src # lvu version NVIDIA-beta
185.18.14</pre>
As you can see, it's the same version, so everything is fine, issue:
<pre>lget NVIDIA-beta</pre>
and copy the .run from /var/spool/lunar to /usr/src. Make it executable using chmod a+x file.run and run it finally using ./file.run. Of course you have to replace "file" with the real filename.

It will tell you that you run an X-Server and you have to stop this one first. Thats np, close X11, chroot into your chroot on the console and install NVIDIA. Exit the Chroot, start X11 again and everything is fine and should be done. You have to try around a bit with the NVIDIA Installer.

==== ATI (r600/kms enabled) ====

.

===Home directory===
This is the easiest Task. We just need to mount the home directory with bind:
<pre>mount -o bind /home $OC/home</pre>
Within the Chroot you can “su - username” and you’re in your home directory, without any problems or any flaws.

===Init Script===
These are only examples.. you’ll probably find nicer variants. Anyway, for both scripts you will need a configfile containing at least the variable CHROOTDIR - which should point to your Chroot Directory. Example:

Config
This config will be used by the initscripts below and our “chroot-enter script”.
<pre>$ cat /etc/lunar32chroot.conf
#!/bin/bash

CHROOTDIR="/usr/local/32bit"</pre>
SysVinit:
This Init Script will mount with --bind some needed directories for the chroot and copy some files which you will most likely want to keep up to date, to have permissions and networking working correctly.
<pre>$ cat /etc/init.d/lunar32chroot

#!/bin/bash
#
# lunar32chroot Initializes the 32 Bit lunar chroot
#
# chkconfig: 2345 80 10
# description: Initializes 32 Bit chroot

CONFIGFILE="/etc/lunar32chroot.conf"

start() {

echo "Starting 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Mounting chroot directories..."
mount -o bind /dev $CHROOTDIR/dev >/dev/null &&
mount -o bind /proc $CHROOTDIR/proc >/dev/null &&
mount -o bind /sys $CHROOTDIR/sys >/dev/null &&
mount -o bind /tmp $CHROOTDIR/tmp >/dev/null &&
mount -o bind /home $CHROOTDIR/home >/dev/null &&
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional mounts //TODO: add check
[ -d /dev/pts ] && mount -o bind /dev/pts $CHROOTDIR/dev/pts >/dev/null
[ -d /dev/shm ] && mount -o bind /dev/shm $CHROOTDIR/dev/shm >/dev/null
[ -d /proc/bus/usb ] && mount -o bind /proc/bus/usb $CHROOTDIR/proc/bus/usb >/dev/null

echo -n " Copying essential files..."
cp -afr /etc/resolv.conf $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/passwd $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/shadow $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/group $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/hosts $CHROOTDIR/etc > /dev/null &&
cp -afr /etc/localtime $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/nsswitch.conf $CHROOTDIR/etc >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
}

stop() {

echo "Stopping 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Unmounting 32bit chroot directories..."
umount -fl $CHROOTDIR/home >/dev/null &&
umount -fl $CHROOTDIR/tmp >/dev/null &&
umount -fl $CHROOTDIR/sys >/dev/null &&
umount -f $CHROOTDIR/proc >/dev/null &&
umount -fl $CHROOTDIR/dev >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional unmounts //TODO: add check
[ -d $CHROOTDIR/proc/bus/usb ] && umount -fl $CHROOTDIR/proc/bus/usb >/dev/null
[ -d $CHROOTDIR/dev/shm ] && umount -fl $CHROOTDIR/dev/shm >/dev/null
[ -d $CHROOTDIR/dev/pts ] && umount -fl $CHROOTDIR/dev/pts >/dev/null

}

. /lib/lsb/init-functions

</pre>
Now run “chkconfig –add lunar32chroot” to create the essential init scripts/symlinks for the different runlevels and you’re done.

===Entering Chroot - Script===
With this Script you just need to type “lunar32″ to enter the chroot environment. Keep in mind the "linux32" command should be available on all boxes, you dont need to install additional software. However its part of "util-linux".
<pre>$ cat /usr/bin/lunar32

#!/bin/bash
# little script to reduce some things to just one command
# especially for lazy people like me.

source /etc/lunar32chroot.conf

echo "Entering chroot..."
linux32 chroot "$CHROOTDIR" /bin/bash</pre>

Hint from Beko
Beko has shown me a dirty way (as he said) of doing the same using sudo, thus you can enter the environment without beeing root:
<pre>
linux32 sudo chroot "$CHROOTDIR" /bin/bash -c "su $WHOAMI"
</pre>
Negative Sideeffects: you're landing in / at the start and sudo has to run with NOPASS. Thats why this solution is dirty and might be a security risk. However.. :-) By the way Of course you want to replace $WHOAMI with your username - or a variable containing the current username.

==Applications==
===Fonts===
For most applications you will need some X11 Fonts installed within the Chroot. Its enough if you install these:
<pre>lin -cr mkfontdir mkfontscale bdftopcf font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-75dpi font-adobe-utopia-100dpi font-adobe-utopia-type1 font-bitstream-100dpi font-bitstream-75dpi font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi</pre>
some of them might not be needed, but well doesnt hurt to install them.

===Skype===
If you want to use Skype you will have to install some more libraries and tools:
<pre>cd /var/lib/lunar/moonbase
cp -rva qt4-apps/qt4 zlocal/
cd zlocal/qt4
vim DEPENDS</pre>
Remove this line:
<pre>depends %X</pre>
Finally install needed stuff:
<pre>lin -cr dbus alsa-utils videoproto libXv scrnsaverproto libXScrnSaver qt4</pre>
It might be needed to install dbus-qt3 (not sure) if so, you have to copy the module to zlocal and edit the DEPENDS file (of qt3 and of dbus-qt3) to remove the X Dependecy.

Skype should now work. You might want to look at the "fonts" Section because skype will display broken fonts :)

==Useful Documentation:==
* http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 [English]
* http://ubuntuforums.org/showthread.php?t=24575 [English]
* http://wiki.ubuntuusers.de/32-Bit_chroot [German]
* http://www.debian-administration.org/article/Installing_apps_in_a_32-bit_chroot_in_AMD64_Debian_system [English]

Miscellaneous:32BitChroot

2012-02-23T00:14:23Z

Keitekk: /* Init Script */

This is an Article about running a 32bit Chroot of Lunar Linux within 64bit Lunar Linux. It's getting updated sometimes and should work on different Distributions, too.

==Lunar Linux 32 Bit Chroot within native 64 Bit Environment==

===Changelog:===
* (20.02.12) Added 32bit-kernel configuration and prompt customization tidbits (keios)
* (22.02.11) Paths of qt4 changed, changed howto accordingly (for skype), fonts needs mkfontscale and mkfontdir (added), added section about ATI graphiccards (3d acceleration), some smaller adjustments.
* (29.10.10) Added bdftopcf to list of fonts, without that, fonts won't compile (thx to cavalier for helping to find out)
* (29.10.10) Added instructions regarding the kernel
* (29.10.10) Added new (with current applications installed) image (lunarlinuxchroot.tar.bz2)
* (29.10.10) Added some information at the Test-Stage
* (29.10.10) Added little side note about lunar optimize in chrooted-environments
* (29.10.10) Added little notice about the "unofficial image"
* (11.08.09) Added some Information (Thanks to beko)
* (10.07.09) 3D Acceleration howto was wrong, corrected thx to Raedwulf for pointing out :)
* (10.07.09) I rewrote some parts to a hopefully nicer english.

===Todo:===
* Bash Script which performs the actions below automatically

==Installation==

===Why===
Because. As Lunar Linux is 32bit or 64bit and not multilib, you have to use a chroot for 32bit. I really dislike this but nobody wanted to put time into multilib yet just because of a few guys which would like that and as every day some more apps work using 64bit, multilib will probably not be that useful at all. Anyway, for those of you who want to use 32bit apps within the 64bit environment, this little howto should help a lot.

===Requirements===
Having an image of a running system could help a lot and reduce the needed time amount. If you like you can use an Image i created originally for use as OpenSolaris Zone. You could also create your own 32bit image (just install 32bit linux using a vm or something and tar cjvf the whole system, without proc, sys, dev..). Anyway, i will explain here how to do it using my image.

== Images ==

These are '''unofficial''' images made by me (wdp).

* http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2 [current] 483M (unpacked 1,8G) - 29.10.2010
* http://www.jeanbruenn.info/downloads/osol_lunar_zone.tar.gz [outdated!] 570M

These images are quite outdated, so you're far better off making your own 32bit image. If you don't, you could have difficulties during the lunar update process below.

===Switch to root (For the Dummies)===
Of course you need to be root to run most of the following commands. If you don't know how to switch to the super user (root) in a Linux System you don't want to deal with this Howto. First learn some Basics. However. You can switch to the super user using the command:
<pre>wdp@yulivee ~ $ su -</pre>

===Setup Environment===
'''Important: The Image listed below''': The image was created to be used as solaris zone, however its quite fine for chrooted environments, too. Please notice that this image is "unofficial" so you won't get official support for it.

I installed my Chroot within /usr/local/32bit you might want to change that, just replace the "export" line to do so and don't forget to replace the path in the config files i'm later showing. The following lines will create the directory for your chroot, download my image and unpack it within that directory, copy over some files from the host to the chroot (like users, passwords, etc) and finally mount some directories from the host within the chroot (like dev, proc, sys, tmp).
<pre>export OC="/usr/local/32bit"
mkdir -p $OC
cd $OC
wget http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2
tar -xjvf lunarlinuxchroot.tar.bz2
cp /etc/hosts $OC/etc/hosts
cp /etc/nsswitch.conf $OC/etc/nsswitch.conf
cp /etc/passwd $OC/etc/passwd
cp /etc/shadow $OC/etc/shadow
cp /etc/resolv.conf $OC/etc/resolv.conf
mount -o bind /dev $OC/dev
mount -o bind /dev/pts $OC/dev/pts
mount -o bind /proc $OC/proc
mount -o bind /sys $OC/sys
mount -o bind /tmp $OC/tmp</pre>

Don't copy your current kernel stuff over to the chroot except for your .config:
<pre>
cp -rva /usr/src/linux/.config $OC/usr/src/
</pre>

=== Tests ===

To enter this chrooted environment, simply type in linux32 chroot $OC

===Test #1===
Within the chroot:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure –host=i686-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared
Thread model: posix
gcc version 4.2.4</pre>
Within the host:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: ../configure –host=x86_64-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared –disable-multilib
Thread model: posix
gcc version 4.2.4</pre>

===Test #2===
Within the chroot:
<pre>wdp@yulivee ~ $ uname -m
i686</pre>
Within the host:
<pre>wdp@yulivee ~ $ uname -m
x86_64</pre>
as you can see - the chroot picks a not-64bit-gcc and uname -m returns not 64bit within the chroot - It's working ;-)

===Setting up the shell prompt===
You might want to ensure you don't accidently mistake the chroot environment for your host or vice-versa. Even if you don't think this could ever happen to you, it almost inevitably will if you keep a lot of terminals open at the same time like me (keios).

So to change your default prompt automatically on entering the chroot, add something like this to your .bashrc:
<pre>
if [ $(uname -m) = "i686" ]; then
# insert whatever works for you between @ and :
export PS1="\u@lunar32:\W> "
else
export PS1="\u@\h:\W> "
fi
</pre>

Your default prompt might look different, in that case customize the snippet as you see fit. If you use a colored prompt, changing the color usually should be enough to remind you.

===Updating the Chroot-System===
My Image might be quite old and it's usually good to have the chroot environment as up to date as the host is. Run the following commands to get new packages/modules:
<pre>wdp@yulivee ~ $ lin moonbase; lin theedge</pre>
Now you can run "lunar" and set some settings. The most important Settings might be the Optimizations. You can either go through: Option -> Optimize Architecture or you run "lunar optimize" at the console.

Modules might need working 32bit kernel headers, so make sure your gcc versions in- and outside the chroot are the same (see Test 1 above). If you need a specific gcc version that's not in the moonbase, use the --want $VERSION option of lin. Then build the kernel - you need the exact same version as you have on your host so you won't run into any trouble when e.g. installing video drivers for 3d acceleration later on:
<pre>root@mari-chan:/$ lin -cr linux-stable</pre>
When it asks you if you want to configure the kernel, say yes. In the menuconfig, use the "Load alternative config" option to load the kernel .config file you've copied to /usr/src earlier. Just enter:
<pre>../.config</pre>

After you've done configuring your lunar installation run:
<pre>wdp@yulivee ~ $ lunar renew</pre>
to update your whole installation. Get a cup of tea or coffee, this might take a while depending on your box and resources. At this state you should have a running 32 Bit Chroot. However we will still need to enhance this a bit. You want for sure X11 within the Chroot.

'''Important Note about lunar optimize''':
If you select optimizations for your chrooted environment, never ever use "native" as cpu optimization, this will break things. Always go with something safe, like i686 for example.

==Enhancing your Chroot Installation==
===X11===
We mounted /tmp from the host to /tmp inside the chroot already. This way we can use the X11 Socket to connect applications within the chroot to our running x11-server within the host. You could also, if this isn’t possible, use TCP Connections. But they come usually with overhead and thus performance of x11 stuff will be bad. Anyway. You don’t need a whole X11-Server within the chroot, just a few x11 libs. Let’s go:
<pre>wdp@linux32 ~ $ lin -cr libX11 fixesproto libXxf86vm libXt libXmu libXi mesa-lib xclock</pre>
This will install some X11 staff and libraries which are needed. You need now to allow X11-Unix-Socket Connections. Within the Chroot Environment edit your /etc/hostname and set "linux32" or something similar, remember this hostname. On the host type in: xhost +local:linux32 (Replace linux32 with the hostname you've set) or you could use "xhost +" which is insecure. Now you can test your X11 using xclock within your Chroot:
<pre>wdp@linux32 ~ $ export DISPLAY=”:0.0″
wdp@linux32 ~ $ xclock</pre>
You see the Clock? Fine it worked :)

===3D Acceleration===

If you want to run 32 Bit Games or Emulators like wine which don't work in native 64 Bit you might want to have 3D Acceleration. The important thing about this is that you have to use exactly the same driver version within your chroot as the driver version in your host, otherwise it will simply not work. Thats why you should try to keep both installations as up to date as possible.

==== nVidia ====

It is really important that you got your kernel files and kernel header from the host, also within the chroot. you can do that by copy (cp) from the host to the chrooted environment or you simply copy over the current kernel configuration to the chroot and compile the kernel within the chroot again. (i will explain this step better when i got more time) - Keep also in mind, by default the kernel is on hold within the lunar installation. you might want to "unhold" it using lvu.

On the Host check which NVIDIA drivers you got installed and what version it is:
<pre>wdp@yulivee ~ $ lvu installed NVIDIA
NVIDIA is not installed
wdp@yulivee ~ $ lvu installed NVIDIA-beta
185.18.14
wdp@yulivee ~ $</pre>
As you can see, i have NVIDIA-beta installed on the host. Within the Chroot i check now whats the current version of NVIDIA-beta within the moonbase using:
<pre>root@yulivee /usr/src # lvu version NVIDIA-beta
185.18.14</pre>
As you can see, it's the same version, so everything is fine, issue:
<pre>lget NVIDIA-beta</pre>
and copy the .run from /var/spool/lunar to /usr/src. Make it executable using chmod a+x file.run and run it finally using ./file.run. Of course you have to replace "file" with the real filename.

It will tell you that you run an X-Server and you have to stop this one first. Thats np, close X11, chroot into your chroot on the console and install NVIDIA. Exit the Chroot, start X11 again and everything is fine and should be done. You have to try around a bit with the NVIDIA Installer.

==== ATI (r600/kms enabled) ====

.

===Home directory===
This is the easiest Task. We just need to mount the home directory with bind:
<pre>mount -o bind /home $OC/home</pre>
Within the Chroot you can “su - username” and you’re in your home directory, without any problems or any flaws.

===Init Script===
These are only examples.. you’ll probably find nicer variants. Anyway, for both scripts you will need a configfile containing at least the variable CHROOTDIR - which should point to your Chroot Directory. Example:

Config
This config will be used by the initscripts below and our “chroot-enter script”.
<pre>$ cat /etc/lunar32chroot.conf
#!/bin/bash

CHROOTDIR="/usr/local/32bit"</pre>
SysVinit:
This Init Script will mount with --bind some needed directories for the chroot and copy some files which you will most likely want to keep up to date, to have permissions and networking working correctly.
<pre>$ cat /etc/init.d/lunar32chroot

#!/bin/bash
#
# lunar32chroot Initializes the 32 Bit lunar chroot
#
# chkconfig: 2345 80 10
# description: Initializes 32 Bit chroot

CONFIGFILE="/etc/lunar32chroot.conf"

start() {

echo "Starting 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Mounting chroot directories..."
mount -o bind /dev $CHROOTDIR/dev >/dev/null &&
mount -o bind /proc $CHROOTDIR/proc >/dev/null &&
mount -o bind /sys $CHROOTDIR/sys >/dev/null &&
mount -o bind /tmp $CHROOTDIR/tmp >/dev/null &&
mount -o bind /home $CHROOTDIR/home >/dev/null &&
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional mounts //TODO: add check
[ -d /dev/pts ] && mount -o bind /dev/pts $CHROOTDIR/dev/pts >/dev/null
[ -d /dev/shm ] && mount -o bind /dev/shm $CHROOTDIR/dev/shm >/dev/null
[ -d /proc/bus/usb ] && mount -o bind /proc/bus/usb $CHROOTDIR/proc/bus/usb >/dev/null

echo -n " Copying essential files..."
cp -afr /etc/resolv.conf $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/passwd $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/shadow $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/group $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/hosts $CHROOTDIR/etc > /dev/null &&
cp -afr /etc/localtime $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/nsswitch.conf $CHROOTDIR/etc >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
}

stop() {

echo "Stopping 32bit chroot..."

echo -n " Unmounting 32bit chroot directories..."
umount -fl $CHROOTDIR/home >/dev/null &&
umount -fl $CHROOTDIR/tmp >/dev/null &&
umount -fl $CHROOTDIR/sys >/dev/null &&
umount -f $CHROOTDIR/proc >/dev/null &&
umount -fl $CHROOTDIR/dev >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional unmounts //TODO: add check
[ -d $CHROOTDIR/proc/bus/usb ] && umount -fl $CHROOTDIR/proc/bus/usb >/dev/null
[ -d $CHROOTDIR/dev/shm ] && umount -fl $CHROOTDIR/dev/shm >/dev/null
[ -d $CHROOTDIR/dev/pts ] && umount -fl $CHROOTDIR/dev/pts >/dev/null

}

. /lib/lsb/init-functions

</pre>
Now run “chkconfig –add lunar32chroot” to create the essential init scripts/symlinks for the different runlevels and you’re done.

===Entering Chroot - Script===
With this Script you just need to type “lunar32″ to enter the chroot environment. Keep in mind the "linux32" command should be available on all boxes, you dont need to install additional software. However its part of "util-linux".
<pre>$ cat /usr/bin/lunar32

#!/bin/bash
# little script to reduce some things to just one command
# especially for lazy people like me.

source /etc/lunar32chroot.conf

echo "Entering chroot..."
linux32 chroot "$CHROOTDIR" /bin/bash</pre>

Hint from Beko
Beko has shown me a dirty way (as he said) of doing the same using sudo, thus you can enter the environment without beeing root:
<pre>
linux32 sudo chroot "$CHROOTDIR" /bin/bash -c "su $WHOAMI"
</pre>
Negative Sideeffects: you're landing in / at the start and sudo has to run with NOPASS. Thats why this solution is dirty and might be a security risk. However.. :-) By the way Of course you want to replace $WHOAMI with your username - or a variable containing the current username.

==Applications==
===Fonts===
For most applications you will need some X11 Fonts installed within the Chroot. Its enough if you install these:
<pre>lin -cr mkfontdir mkfontscale bdftopcf font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-75dpi font-adobe-utopia-100dpi font-adobe-utopia-type1 font-bitstream-100dpi font-bitstream-75dpi font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi</pre>
some of them might not be needed, but well doesnt hurt to install them.

===Skype===
If you want to use Skype you will have to install some more libraries and tools:
<pre>cd /var/lib/lunar/moonbase
cp -rva qt4-apps/qt4 zlocal/
cd zlocal/qt4
vim DEPENDS</pre>
Remove this line:
<pre>depends %X</pre>
Finally install needed stuff:
<pre>lin -cr dbus alsa-utils videoproto libXv scrnsaverproto libXScrnSaver qt4</pre>
It might be needed to install dbus-qt3 (not sure) if so, you have to copy the module to zlocal and edit the DEPENDS file (of qt3 and of dbus-qt3) to remove the X Dependecy.

Skype should now work. You might want to look at the "fonts" Section because skype will display broken fonts :)

==Useful Documentation:==
* http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 [English]
* http://ubuntuforums.org/showthread.php?t=24575 [English]
* http://wiki.ubuntuusers.de/32-Bit_chroot [German]
* http://www.debian-administration.org/article/Installing_apps_in_a_32-bit_chroot_in_AMD64_Debian_system [English]

Miscellaneous:32BitChroot

2012-02-23T00:12:56Z

Keitekk: /* Init Script */

This is an Article about running a 32bit Chroot of Lunar Linux within 64bit Lunar Linux. It's getting updated sometimes and should work on different Distributions, too.

==Lunar Linux 32 Bit Chroot within native 64 Bit Environment==

===Changelog:===
* (20.02.12) Added 32bit-kernel configuration and prompt customization tidbits (keios)
* (22.02.11) Paths of qt4 changed, changed howto accordingly (for skype), fonts needs mkfontscale and mkfontdir (added), added section about ATI graphiccards (3d acceleration), some smaller adjustments.
* (29.10.10) Added bdftopcf to list of fonts, without that, fonts won't compile (thx to cavalier for helping to find out)
* (29.10.10) Added instructions regarding the kernel
* (29.10.10) Added new (with current applications installed) image (lunarlinuxchroot.tar.bz2)
* (29.10.10) Added some information at the Test-Stage
* (29.10.10) Added little side note about lunar optimize in chrooted-environments
* (29.10.10) Added little notice about the "unofficial image"
* (11.08.09) Added some Information (Thanks to beko)
* (10.07.09) 3D Acceleration howto was wrong, corrected thx to Raedwulf for pointing out :)
* (10.07.09) I rewrote some parts to a hopefully nicer english.

===Todo:===
* Bash Script which performs the actions below automatically

==Installation==

===Why===
Because. As Lunar Linux is 32bit or 64bit and not multilib, you have to use a chroot for 32bit. I really dislike this but nobody wanted to put time into multilib yet just because of a few guys which would like that and as every day some more apps work using 64bit, multilib will probably not be that useful at all. Anyway, for those of you who want to use 32bit apps within the 64bit environment, this little howto should help a lot.

===Requirements===
Having an image of a running system could help a lot and reduce the needed time amount. If you like you can use an Image i created originally for use as OpenSolaris Zone. You could also create your own 32bit image (just install 32bit linux using a vm or something and tar cjvf the whole system, without proc, sys, dev..). Anyway, i will explain here how to do it using my image.

== Images ==

These are '''unofficial''' images made by me (wdp).

* http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2 [current] 483M (unpacked 1,8G) - 29.10.2010
* http://www.jeanbruenn.info/downloads/osol_lunar_zone.tar.gz [outdated!] 570M

These images are quite outdated, so you're far better off making your own 32bit image. If you don't, you could have difficulties during the lunar update process below.

===Switch to root (For the Dummies)===
Of course you need to be root to run most of the following commands. If you don't know how to switch to the super user (root) in a Linux System you don't want to deal with this Howto. First learn some Basics. However. You can switch to the super user using the command:
<pre>wdp@yulivee ~ $ su -</pre>

===Setup Environment===
'''Important: The Image listed below''': The image was created to be used as solaris zone, however its quite fine for chrooted environments, too. Please notice that this image is "unofficial" so you won't get official support for it.

I installed my Chroot within /usr/local/32bit you might want to change that, just replace the "export" line to do so and don't forget to replace the path in the config files i'm later showing. The following lines will create the directory for your chroot, download my image and unpack it within that directory, copy over some files from the host to the chroot (like users, passwords, etc) and finally mount some directories from the host within the chroot (like dev, proc, sys, tmp).
<pre>export OC="/usr/local/32bit"
mkdir -p $OC
cd $OC
wget http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2
tar -xjvf lunarlinuxchroot.tar.bz2
cp /etc/hosts $OC/etc/hosts
cp /etc/nsswitch.conf $OC/etc/nsswitch.conf
cp /etc/passwd $OC/etc/passwd
cp /etc/shadow $OC/etc/shadow
cp /etc/resolv.conf $OC/etc/resolv.conf
mount -o bind /dev $OC/dev
mount -o bind /dev/pts $OC/dev/pts
mount -o bind /proc $OC/proc
mount -o bind /sys $OC/sys
mount -o bind /tmp $OC/tmp</pre>

Don't copy your current kernel stuff over to the chroot except for your .config:
<pre>
cp -rva /usr/src/linux/.config $OC/usr/src/
</pre>

=== Tests ===

To enter this chrooted environment, simply type in linux32 chroot $OC

===Test #1===
Within the chroot:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure –host=i686-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared
Thread model: posix
gcc version 4.2.4</pre>
Within the host:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: ../configure –host=x86_64-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared –disable-multilib
Thread model: posix
gcc version 4.2.4</pre>

===Test #2===
Within the chroot:
<pre>wdp@yulivee ~ $ uname -m
i686</pre>
Within the host:
<pre>wdp@yulivee ~ $ uname -m
x86_64</pre>
as you can see - the chroot picks a not-64bit-gcc and uname -m returns not 64bit within the chroot - It's working ;-)

===Setting up the shell prompt===
You might want to ensure you don't accidently mistake the chroot environment for your host or vice-versa. Even if you don't think this could ever happen to you, it almost inevitably will if you keep a lot of terminals open at the same time like me (keios).

So to change your default prompt automatically on entering the chroot, add something like this to your .bashrc:
<pre>
if [ $(uname -m) = "i686" ]; then
# insert whatever works for you between @ and :
export PS1="\u@lunar32:\W> "
else
export PS1="\u@\h:\W> "
fi
</pre>

Your default prompt might look different, in that case customize the snippet as you see fit. If you use a colored prompt, changing the color usually should be enough to remind you.

===Updating the Chroot-System===
My Image might be quite old and it's usually good to have the chroot environment as up to date as the host is. Run the following commands to get new packages/modules:
<pre>wdp@yulivee ~ $ lin moonbase; lin theedge</pre>
Now you can run "lunar" and set some settings. The most important Settings might be the Optimizations. You can either go through: Option -> Optimize Architecture or you run "lunar optimize" at the console.

Modules might need working 32bit kernel headers, so make sure your gcc versions in- and outside the chroot are the same (see Test 1 above). If you need a specific gcc version that's not in the moonbase, use the --want $VERSION option of lin. Then build the kernel - you need the exact same version as you have on your host so you won't run into any trouble when e.g. installing video drivers for 3d acceleration later on:
<pre>root@mari-chan:/$ lin -cr linux-stable</pre>
When it asks you if you want to configure the kernel, say yes. In the menuconfig, use the "Load alternative config" option to load the kernel .config file you've copied to /usr/src earlier. Just enter:
<pre>../.config</pre>

After you've done configuring your lunar installation run:
<pre>wdp@yulivee ~ $ lunar renew</pre>
to update your whole installation. Get a cup of tea or coffee, this might take a while depending on your box and resources. At this state you should have a running 32 Bit Chroot. However we will still need to enhance this a bit. You want for sure X11 within the Chroot.

'''Important Note about lunar optimize''':
If you select optimizations for your chrooted environment, never ever use "native" as cpu optimization, this will break things. Always go with something safe, like i686 for example.

==Enhancing your Chroot Installation==
===X11===
We mounted /tmp from the host to /tmp inside the chroot already. This way we can use the X11 Socket to connect applications within the chroot to our running x11-server within the host. You could also, if this isn’t possible, use TCP Connections. But they come usually with overhead and thus performance of x11 stuff will be bad. Anyway. You don’t need a whole X11-Server within the chroot, just a few x11 libs. Let’s go:
<pre>wdp@linux32 ~ $ lin -cr libX11 fixesproto libXxf86vm libXt libXmu libXi mesa-lib xclock</pre>
This will install some X11 staff and libraries which are needed. You need now to allow X11-Unix-Socket Connections. Within the Chroot Environment edit your /etc/hostname and set "linux32" or something similar, remember this hostname. On the host type in: xhost +local:linux32 (Replace linux32 with the hostname you've set) or you could use "xhost +" which is insecure. Now you can test your X11 using xclock within your Chroot:
<pre>wdp@linux32 ~ $ export DISPLAY=”:0.0″
wdp@linux32 ~ $ xclock</pre>
You see the Clock? Fine it worked :)

===3D Acceleration===

If you want to run 32 Bit Games or Emulators like wine which don't work in native 64 Bit you might want to have 3D Acceleration. The important thing about this is that you have to use exactly the same driver version within your chroot as the driver version in your host, otherwise it will simply not work. Thats why you should try to keep both installations as up to date as possible.

==== nVidia ====

It is really important that you got your kernel files and kernel header from the host, also within the chroot. you can do that by copy (cp) from the host to the chrooted environment or you simply copy over the current kernel configuration to the chroot and compile the kernel within the chroot again. (i will explain this step better when i got more time) - Keep also in mind, by default the kernel is on hold within the lunar installation. you might want to "unhold" it using lvu.

On the Host check which NVIDIA drivers you got installed and what version it is:
<pre>wdp@yulivee ~ $ lvu installed NVIDIA
NVIDIA is not installed
wdp@yulivee ~ $ lvu installed NVIDIA-beta
185.18.14
wdp@yulivee ~ $</pre>
As you can see, i have NVIDIA-beta installed on the host. Within the Chroot i check now whats the current version of NVIDIA-beta within the moonbase using:
<pre>root@yulivee /usr/src # lvu version NVIDIA-beta
185.18.14</pre>
As you can see, it's the same version, so everything is fine, issue:
<pre>lget NVIDIA-beta</pre>
and copy the .run from /var/spool/lunar to /usr/src. Make it executable using chmod a+x file.run and run it finally using ./file.run. Of course you have to replace "file" with the real filename.

It will tell you that you run an X-Server and you have to stop this one first. Thats np, close X11, chroot into your chroot on the console and install NVIDIA. Exit the Chroot, start X11 again and everything is fine and should be done. You have to try around a bit with the NVIDIA Installer.

==== ATI (r600/kms enabled) ====

.

===Home directory===
This is the easiest Task. We just need to mount the home directory with bind:
<pre>mount -o bind /home $OC/home</pre>
Within the Chroot you can “su - username” and you’re in your home directory, without any problems or any flaws.

===Init Script===
These are only examples.. you’ll probably find nicer variants. Anyway, for both scripts you will need a configfile containing at least the variable CHROOTDIR - which should point to your Chroot Directory. Example:

Config
This config will be used by the initscripts below and our “chroot-enter script”.
<pre>$ cat /etc/lunar32chroot.conf
#!/bin/bash

CHROOTDIR="/usr/local/32bit"</pre>
SysVinit:
This Init Script will mount with --bind some needed directories for the chroot and copy some files which you will most likely want to keep up to date, to have permissions and networking working correctly.
<pre>$ cat /etc/init.d/lunar32chroot

#!/bin/bash
#
# lunar32chroot Initializes the 32 Bit lunar chroot
#
# chkconfig: 2345 80 10
# description: Initializes 32 Bit chroot

CONFIGFILE="/etc/lunar32chroot.conf"

start() {

echo "Starting 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Mounting chroot directories..."
mount -o bind /dev $CHROOTDIR/dev >/dev/null &&
mount -o bind /proc $CHROOTDIR/proc >/dev/null &&
mount -o bind /sys $CHROOTDIR/sys >/dev/null &&
mount -o bind /tmp $CHROOTDIR/tmp >/dev/null &&
mount -o bind /home $CHROOTDIR/home >/dev/null &&
mount -o bind /media/lain $CHROOTDIR/media/lain >/dev/null &&
mount -o bind /media/maelstrom $CHROOTDIR/media/maelstrom >/dev/null &&
mount -o bind /media/vortex $CHROOTDIR/media/vortex >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional mounts //TODO: add check
[ -d /dev/pts ] && mount -o bind /dev/pts $CHROOTDIR/dev/pts >/dev/null
[ -d /dev/shm ] && mount -o bind /dev/shm $CHROOTDIR/dev/shm >/dev/null
[ -d /proc/bus/usb ] && mount -o bind /proc/bus/usb $CHROOTDIR/proc/bus/usb >/dev/null

echo -n " Copying essential files..."
cp -afr /etc/resolv.conf $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/passwd $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/shadow $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/group $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/hosts $CHROOTDIR/etc > /dev/null &&
cp -afr /etc/localtime $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/nsswitch.conf $CHROOTDIR/etc >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
}

stop() {

echo "Stopping 32bit chroot..."

echo -n " Unmounting 32bit chroot directories..."
umount -fl $CHROOTDIR/media/vortex >/dev/null &&
umount -fl $CHROOTDIR/media/maelstrom >/dev/null &&
umount -fl $CHROOTDIR/media/lain >/dev/null &&
umount -fl $CHROOTDIR/home >/dev/null &&
umount -fl $CHROOTDIR/tmp >/dev/null &&
umount -fl $CHROOTDIR/sys >/dev/null &&
umount -f $CHROOTDIR/proc >/dev/null &&
umount -fl $CHROOTDIR/dev >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional unmounts //TODO: add check
[ -d $CHROOTDIR/proc/bus/usb ] && umount -fl $CHROOTDIR/proc/bus/usb >/dev/null
[ -d $CHROOTDIR/dev/shm ] && umount -fl $CHROOTDIR/dev/shm >/dev/null
[ -d $CHROOTDIR/dev/pts ] && umount -fl $CHROOTDIR/dev/pts >/dev/null

}

. /lib/lsb/init-functions

</pre>
Now run “chkconfig –add lunar32chroot” to create the essential init scripts/symlinks for the different runlevels and you’re done.

===Entering Chroot - Script===
With this Script you just need to type “lunar32″ to enter the chroot environment. Keep in mind the "linux32" command should be available on all boxes, you dont need to install additional software. However its part of "util-linux".
<pre>$ cat /usr/bin/lunar32

#!/bin/bash
# little script to reduce some things to just one command
# especially for lazy people like me.

source /etc/lunar32chroot.conf

echo "Entering chroot..."
linux32 chroot "$CHROOTDIR" /bin/bash</pre>

Hint from Beko
Beko has shown me a dirty way (as he said) of doing the same using sudo, thus you can enter the environment without beeing root:
<pre>
linux32 sudo chroot "$CHROOTDIR" /bin/bash -c "su $WHOAMI"
</pre>
Negative Sideeffects: you're landing in / at the start and sudo has to run with NOPASS. Thats why this solution is dirty and might be a security risk. However.. :-) By the way Of course you want to replace $WHOAMI with your username - or a variable containing the current username.

==Applications==
===Fonts===
For most applications you will need some X11 Fonts installed within the Chroot. Its enough if you install these:
<pre>lin -cr mkfontdir mkfontscale bdftopcf font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-75dpi font-adobe-utopia-100dpi font-adobe-utopia-type1 font-bitstream-100dpi font-bitstream-75dpi font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi</pre>
some of them might not be needed, but well doesnt hurt to install them.

===Skype===
If you want to use Skype you will have to install some more libraries and tools:
<pre>cd /var/lib/lunar/moonbase
cp -rva qt4-apps/qt4 zlocal/
cd zlocal/qt4
vim DEPENDS</pre>
Remove this line:
<pre>depends %X</pre>
Finally install needed stuff:
<pre>lin -cr dbus alsa-utils videoproto libXv scrnsaverproto libXScrnSaver qt4</pre>
It might be needed to install dbus-qt3 (not sure) if so, you have to copy the module to zlocal and edit the DEPENDS file (of qt3 and of dbus-qt3) to remove the X Dependecy.

Skype should now work. You might want to look at the "fonts" Section because skype will display broken fonts :)

==Useful Documentation:==
* http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 [English]
* http://ubuntuforums.org/showthread.php?t=24575 [English]
* http://wiki.ubuntuusers.de/32-Bit_chroot [German]
* http://www.debian-administration.org/article/Installing_apps_in_a_32-bit_chroot_in_AMD64_Debian_system [English]

Miscellaneous:32BitChroot

2012-02-23T00:11:00Z

Keitekk: /* Init Script */

This is an Article about running a 32bit Chroot of Lunar Linux within 64bit Lunar Linux. It's getting updated sometimes and should work on different Distributions, too.

==Lunar Linux 32 Bit Chroot within native 64 Bit Environment==

===Changelog:===
* (20.02.12) Added 32bit-kernel configuration and prompt customization tidbits (keios)
* (22.02.11) Paths of qt4 changed, changed howto accordingly (for skype), fonts needs mkfontscale and mkfontdir (added), added section about ATI graphiccards (3d acceleration), some smaller adjustments.
* (29.10.10) Added bdftopcf to list of fonts, without that, fonts won't compile (thx to cavalier for helping to find out)
* (29.10.10) Added instructions regarding the kernel
* (29.10.10) Added new (with current applications installed) image (lunarlinuxchroot.tar.bz2)
* (29.10.10) Added some information at the Test-Stage
* (29.10.10) Added little side note about lunar optimize in chrooted-environments
* (29.10.10) Added little notice about the "unofficial image"
* (11.08.09) Added some Information (Thanks to beko)
* (10.07.09) 3D Acceleration howto was wrong, corrected thx to Raedwulf for pointing out :)
* (10.07.09) I rewrote some parts to a hopefully nicer english.

===Todo:===
* Bash Script which performs the actions below automatically

==Installation==

===Why===
Because. As Lunar Linux is 32bit or 64bit and not multilib, you have to use a chroot for 32bit. I really dislike this but nobody wanted to put time into multilib yet just because of a few guys which would like that and as every day some more apps work using 64bit, multilib will probably not be that useful at all. Anyway, for those of you who want to use 32bit apps within the 64bit environment, this little howto should help a lot.

===Requirements===
Having an image of a running system could help a lot and reduce the needed time amount. If you like you can use an Image i created originally for use as OpenSolaris Zone. You could also create your own 32bit image (just install 32bit linux using a vm or something and tar cjvf the whole system, without proc, sys, dev..). Anyway, i will explain here how to do it using my image.

== Images ==

These are '''unofficial''' images made by me (wdp).

* http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2 [current] 483M (unpacked 1,8G) - 29.10.2010
* http://www.jeanbruenn.info/downloads/osol_lunar_zone.tar.gz [outdated!] 570M

These images are quite outdated, so you're far better off making your own 32bit image. If you don't, you could have difficulties during the lunar update process below.

===Switch to root (For the Dummies)===
Of course you need to be root to run most of the following commands. If you don't know how to switch to the super user (root) in a Linux System you don't want to deal with this Howto. First learn some Basics. However. You can switch to the super user using the command:
<pre>wdp@yulivee ~ $ su -</pre>

===Setup Environment===
'''Important: The Image listed below''': The image was created to be used as solaris zone, however its quite fine for chrooted environments, too. Please notice that this image is "unofficial" so you won't get official support for it.

I installed my Chroot within /usr/local/32bit you might want to change that, just replace the "export" line to do so and don't forget to replace the path in the config files i'm later showing. The following lines will create the directory for your chroot, download my image and unpack it within that directory, copy over some files from the host to the chroot (like users, passwords, etc) and finally mount some directories from the host within the chroot (like dev, proc, sys, tmp).
<pre>export OC="/usr/local/32bit"
mkdir -p $OC
cd $OC
wget http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2
tar -xjvf lunarlinuxchroot.tar.bz2
cp /etc/hosts $OC/etc/hosts
cp /etc/nsswitch.conf $OC/etc/nsswitch.conf
cp /etc/passwd $OC/etc/passwd
cp /etc/shadow $OC/etc/shadow
cp /etc/resolv.conf $OC/etc/resolv.conf
mount -o bind /dev $OC/dev
mount -o bind /dev/pts $OC/dev/pts
mount -o bind /proc $OC/proc
mount -o bind /sys $OC/sys
mount -o bind /tmp $OC/tmp</pre>

Don't copy your current kernel stuff over to the chroot except for your .config:
<pre>
cp -rva /usr/src/linux/.config $OC/usr/src/
</pre>

=== Tests ===

To enter this chrooted environment, simply type in linux32 chroot $OC

===Test #1===
Within the chroot:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure –host=i686-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared
Thread model: posix
gcc version 4.2.4</pre>
Within the host:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: ../configure –host=x86_64-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared –disable-multilib
Thread model: posix
gcc version 4.2.4</pre>

===Test #2===
Within the chroot:
<pre>wdp@yulivee ~ $ uname -m
i686</pre>
Within the host:
<pre>wdp@yulivee ~ $ uname -m
x86_64</pre>
as you can see - the chroot picks a not-64bit-gcc and uname -m returns not 64bit within the chroot - It's working ;-)

===Setting up the shell prompt===
You might want to ensure you don't accidently mistake the chroot environment for your host or vice-versa. Even if you don't think this could ever happen to you, it almost inevitably will if you keep a lot of terminals open at the same time like me (keios).

So to change your default prompt automatically on entering the chroot, add something like this to your .bashrc:
<pre>
if [ $(uname -m) = "i686" ]; then
# insert whatever works for you between @ and :
export PS1="\u@lunar32:\W> "
else
export PS1="\u@\h:\W> "
fi
</pre>

Your default prompt might look different, in that case customize the snippet as you see fit. If you use a colored prompt, changing the color usually should be enough to remind you.

===Updating the Chroot-System===
My Image might be quite old and it's usually good to have the chroot environment as up to date as the host is. Run the following commands to get new packages/modules:
<pre>wdp@yulivee ~ $ lin moonbase; lin theedge</pre>
Now you can run "lunar" and set some settings. The most important Settings might be the Optimizations. You can either go through: Option -> Optimize Architecture or you run "lunar optimize" at the console.

Modules might need working 32bit kernel headers, so make sure your gcc versions in- and outside the chroot are the same (see Test 1 above). If you need a specific gcc version that's not in the moonbase, use the --want $VERSION option of lin. Then build the kernel - you need the exact same version as you have on your host so you won't run into any trouble when e.g. installing video drivers for 3d acceleration later on:
<pre>root@mari-chan:/$ lin -cr linux-stable</pre>
When it asks you if you want to configure the kernel, say yes. In the menuconfig, use the "Load alternative config" option to load the kernel .config file you've copied to /usr/src earlier. Just enter:
<pre>../.config</pre>

After you've done configuring your lunar installation run:
<pre>wdp@yulivee ~ $ lunar renew</pre>
to update your whole installation. Get a cup of tea or coffee, this might take a while depending on your box and resources. At this state you should have a running 32 Bit Chroot. However we will still need to enhance this a bit. You want for sure X11 within the Chroot.

'''Important Note about lunar optimize''':
If you select optimizations for your chrooted environment, never ever use "native" as cpu optimization, this will break things. Always go with something safe, like i686 for example.

==Enhancing your Chroot Installation==
===X11===
We mounted /tmp from the host to /tmp inside the chroot already. This way we can use the X11 Socket to connect applications within the chroot to our running x11-server within the host. You could also, if this isn’t possible, use TCP Connections. But they come usually with overhead and thus performance of x11 stuff will be bad. Anyway. You don’t need a whole X11-Server within the chroot, just a few x11 libs. Let’s go:
<pre>wdp@linux32 ~ $ lin -cr libX11 fixesproto libXxf86vm libXt libXmu libXi mesa-lib xclock</pre>
This will install some X11 staff and libraries which are needed. You need now to allow X11-Unix-Socket Connections. Within the Chroot Environment edit your /etc/hostname and set "linux32" or something similar, remember this hostname. On the host type in: xhost +local:linux32 (Replace linux32 with the hostname you've set) or you could use "xhost +" which is insecure. Now you can test your X11 using xclock within your Chroot:
<pre>wdp@linux32 ~ $ export DISPLAY=”:0.0″
wdp@linux32 ~ $ xclock</pre>
You see the Clock? Fine it worked :)

===3D Acceleration===

If you want to run 32 Bit Games or Emulators like wine which don't work in native 64 Bit you might want to have 3D Acceleration. The important thing about this is that you have to use exactly the same driver version within your chroot as the driver version in your host, otherwise it will simply not work. Thats why you should try to keep both installations as up to date as possible.

==== nVidia ====

It is really important that you got your kernel files and kernel header from the host, also within the chroot. you can do that by copy (cp) from the host to the chrooted environment or you simply copy over the current kernel configuration to the chroot and compile the kernel within the chroot again. (i will explain this step better when i got more time) - Keep also in mind, by default the kernel is on hold within the lunar installation. you might want to "unhold" it using lvu.

On the Host check which NVIDIA drivers you got installed and what version it is:
<pre>wdp@yulivee ~ $ lvu installed NVIDIA
NVIDIA is not installed
wdp@yulivee ~ $ lvu installed NVIDIA-beta
185.18.14
wdp@yulivee ~ $</pre>
As you can see, i have NVIDIA-beta installed on the host. Within the Chroot i check now whats the current version of NVIDIA-beta within the moonbase using:
<pre>root@yulivee /usr/src # lvu version NVIDIA-beta
185.18.14</pre>
As you can see, it's the same version, so everything is fine, issue:
<pre>lget NVIDIA-beta</pre>
and copy the .run from /var/spool/lunar to /usr/src. Make it executable using chmod a+x file.run and run it finally using ./file.run. Of course you have to replace "file" with the real filename.

It will tell you that you run an X-Server and you have to stop this one first. Thats np, close X11, chroot into your chroot on the console and install NVIDIA. Exit the Chroot, start X11 again and everything is fine and should be done. You have to try around a bit with the NVIDIA Installer.

==== ATI (r600/kms enabled) ====

.

===Home directory===
This is the easiest Task. We just need to mount the home directory with bind:
<pre>mount -o bind /home $OC/home</pre>
Within the Chroot you can “su - username” and you’re in your home directory, without any problems or any flaws.

===Init Script===
These are only examples.. you’ll probably find nicer variants. Anyway, for both scripts you will need a configfile containing at least the variable CHROOTDIR - which should point to your Chroot Directory. Example:

Config
This config will be used by the initscripts below and our “chroot-enter script”.
<pre>$ cat /etc/lunar32chroot.conf
#!/bin/bash

CHROOTDIR="/usr/local/32bit"</pre>
SysVinit:
This Init Script will mount with --bind some needed directories for the chroot and copy some files which you will most likely want to keep up to date, to have permissions and networking working correctly.
<pre>$ cat /etc/init.d/lunar32chroot

#!/bin/bash
#
# lunar32chroot Initializes the 32 Bit lunar chroot
#
# chkconfig: 2345 80 10
# description: Initializes 32 Bit chroot

CONFIGFILE="/etc/lunar32chroot.conf"

start() {

echo "Starting 32bit chroot..."

if [ -e "$CONFIGFILE" ]; then
source /etc/lunar32chroot.conf
else
# we need a config...
echo "No config file found!"
echo -e $RESULT_FAIL
exit 0
fi

echo -n " Mounting chroot directories..."
mount -o bind /dev $CHROOTDIR/dev >/dev/null &&
mount -o bind /proc $CHROOTDIR/proc >/dev/null &&
mount -o bind /sys $CHROOTDIR/sys >/dev/null &&
mount -o bind /tmp $CHROOTDIR/tmp >/dev/null &&
mount -o bind /home $CHROOTDIR/home >/dev/null &&
mount -o bind /media/lain $CHROOTDIR/media/lain >/dev/null &&
mount -o bind /media/maelstrom $CHROOTDIR/media/maelstrom >/dev/null &&
mount -o bind /media/vortex $CHROOTDIR/media/vortex >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional mounts //TODO: add check
$SHELL -c "[ -d /dev/pts ] && mount -o bind /dev/pts $CHROOTDIR/dev/pts >/dev/null" &&
$SHELL -c "[ -d /dev/shm ] && mount -o bind /dev/shm $CHROOTDIR/dev/shm >/dev/null" &&
$SHELL -c "[ -d /proc/bus/usb ] && mount -o bind /proc/bus/usb $CHROOTDIR/proc/bus/usb >/dev/null"

echo -n " Copying essential files..."
cp -afr /etc/resolv.conf $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/passwd $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/shadow $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/group $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/hosts $CHROOTDIR/etc > /dev/null &&
cp -afr /etc/localtime $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/nsswitch.conf $CHROOTDIR/etc >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
}

stop() {

echo "Stopping 32bit chroot..."

echo -n " Unmounting 32bit chroot directories..."
umount -fl $CHROOTDIR/media/vortex >/dev/null &&
umount -fl $CHROOTDIR/media/maelstrom >/dev/null &&
umount -fl $CHROOTDIR/media/lain >/dev/null &&
umount -fl $CHROOTDIR/home >/dev/null &&
umount -fl $CHROOTDIR/tmp >/dev/null &&
umount -fl $CHROOTDIR/sys >/dev/null &&
umount -f $CHROOTDIR/proc >/dev/null &&
umount -fl $CHROOTDIR/dev >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
# optional unmounts //TODO: add check
$SHELL -c "[ -d $CHROOTDIR/proc/bus/usb ] && umount -fl $CHROOTDIR/proc/bus/usb >/dev/null" &&
$SHELL -c "[ -d $CHROOTDIR/dev/shm ] && umount -fl $CHROOTDIR/dev/shm >/dev/null" &&
$SHELL -c "[ -d $CHROOTDIR/dev/pts ] && umount -fl $CHROOTDIR/dev/pts >/dev/null"

}

. /lib/lsb/init-functions

</pre>
Now run “chkconfig –add lunar32chroot” to create the essential init scripts/symlinks for the different runlevels and you’re done.

===Entering Chroot - Script===
With this Script you just need to type “lunar32″ to enter the chroot environment. Keep in mind the "linux32" command should be available on all boxes, you dont need to install additional software. However its part of "util-linux".
<pre>$ cat /usr/bin/lunar32

#!/bin/bash
# little script to reduce some things to just one command
# especially for lazy people like me.

source /etc/lunar32chroot.conf

echo "Entering chroot..."
linux32 chroot "$CHROOTDIR" /bin/bash</pre>

Hint from Beko
Beko has shown me a dirty way (as he said) of doing the same using sudo, thus you can enter the environment without beeing root:
<pre>
linux32 sudo chroot "$CHROOTDIR" /bin/bash -c "su $WHOAMI"
</pre>
Negative Sideeffects: you're landing in / at the start and sudo has to run with NOPASS. Thats why this solution is dirty and might be a security risk. However.. :-) By the way Of course you want to replace $WHOAMI with your username - or a variable containing the current username.

==Applications==
===Fonts===
For most applications you will need some X11 Fonts installed within the Chroot. Its enough if you install these:
<pre>lin -cr mkfontdir mkfontscale bdftopcf font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-75dpi font-adobe-utopia-100dpi font-adobe-utopia-type1 font-bitstream-100dpi font-bitstream-75dpi font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi</pre>
some of them might not be needed, but well doesnt hurt to install them.

===Skype===
If you want to use Skype you will have to install some more libraries and tools:
<pre>cd /var/lib/lunar/moonbase
cp -rva qt4-apps/qt4 zlocal/
cd zlocal/qt4
vim DEPENDS</pre>
Remove this line:
<pre>depends %X</pre>
Finally install needed stuff:
<pre>lin -cr dbus alsa-utils videoproto libXv scrnsaverproto libXScrnSaver qt4</pre>
It might be needed to install dbus-qt3 (not sure) if so, you have to copy the module to zlocal and edit the DEPENDS file (of qt3 and of dbus-qt3) to remove the X Dependecy.

Skype should now work. You might want to look at the "fonts" Section because skype will display broken fonts :)

==Useful Documentation:==
* http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 [English]
* http://ubuntuforums.org/showthread.php?t=24575 [English]
* http://wiki.ubuntuusers.de/32-Bit_chroot [German]
* http://www.debian-administration.org/article/Installing_apps_in_a_32-bit_chroot_in_AMD64_Debian_system [English]

Miscellaneous:32BitChroot

2012-02-22T22:16:14Z

Keitekk: /* Init Script */

This is an Article about running a 32bit Chroot of Lunar Linux within 64bit Lunar Linux. It's getting updated sometimes and should work on different Distributions, too.

==Lunar Linux 32 Bit Chroot within native 64 Bit Environment==

===Changelog:===
* (20.02.12) Added 32bit-kernel configuration and prompt customization tidbits (keios)
* (22.02.11) Paths of qt4 changed, changed howto accordingly (for skype), fonts needs mkfontscale and mkfontdir (added), added section about ATI graphiccards (3d acceleration), some smaller adjustments.
* (29.10.10) Added bdftopcf to list of fonts, without that, fonts won't compile (thx to cavalier for helping to find out)
* (29.10.10) Added instructions regarding the kernel
* (29.10.10) Added new (with current applications installed) image (lunarlinuxchroot.tar.bz2)
* (29.10.10) Added some information at the Test-Stage
* (29.10.10) Added little side note about lunar optimize in chrooted-environments
* (29.10.10) Added little notice about the "unofficial image"
* (11.08.09) Added some Information (Thanks to beko)
* (10.07.09) 3D Acceleration howto was wrong, corrected thx to Raedwulf for pointing out :)
* (10.07.09) I rewrote some parts to a hopefully nicer english.

===Todo:===
* Bash Script which performs the actions below automatically

==Installation==

===Why===
Because. As Lunar Linux is 32bit or 64bit and not multilib, you have to use a chroot for 32bit. I really dislike this but nobody wanted to put time into multilib yet just because of a few guys which would like that and as every day some more apps work using 64bit, multilib will probably not be that useful at all. Anyway, for those of you who want to use 32bit apps within the 64bit environment, this little howto should help a lot.

===Requirements===
Having an image of a running system could help a lot and reduce the needed time amount. If you like you can use an Image i created originally for use as OpenSolaris Zone. You could also create your own 32bit image (just install 32bit linux using a vm or something and tar cjvf the whole system, without proc, sys, dev..). Anyway, i will explain here how to do it using my image.

== Images ==

These are '''unofficial''' images made by me (wdp).

* http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2 [current] 483M (unpacked 1,8G) - 29.10.2010
* http://www.jeanbruenn.info/downloads/osol_lunar_zone.tar.gz [outdated!] 570M

These images are quite outdated, so you're far better off making your own 32bit image. If you don't, you could have difficulties during the lunar update process below.

===Switch to root (For the Dummies)===
Of course you need to be root to run most of the following commands. If you don't know how to switch to the super user (root) in a Linux System you don't want to deal with this Howto. First learn some Basics. However. You can switch to the super user using the command:
<pre>wdp@yulivee ~ $ su -</pre>

===Setup Environment===
'''Important: The Image listed below''': The image was created to be used as solaris zone, however its quite fine for chrooted environments, too. Please notice that this image is "unofficial" so you won't get official support for it.

I installed my Chroot within /usr/local/32bit you might want to change that, just replace the "export" line to do so and don't forget to replace the path in the config files i'm later showing. The following lines will create the directory for your chroot, download my image and unpack it within that directory, copy over some files from the host to the chroot (like users, passwords, etc) and finally mount some directories from the host within the chroot (like dev, proc, sys, tmp).
<pre>export OC="/usr/local/32bit"
mkdir -p $OC
cd $OC
wget http://www.jeanbruenn.info/downloads/lunarlinuxchroot.tar.bz2
tar -xjvf lunarlinuxchroot.tar.bz2
cp /etc/hosts $OC/etc/hosts
cp /etc/nsswitch.conf $OC/etc/nsswitch.conf
cp /etc/passwd $OC/etc/passwd
cp /etc/shadow $OC/etc/shadow
cp /etc/resolv.conf $OC/etc/resolv.conf
mount -o bind /dev $OC/dev
mount -o bind /dev/pts $OC/dev/pts
mount -o bind /proc $OC/proc
mount -o bind /sys $OC/sys
mount -o bind /tmp $OC/tmp</pre>

Don't copy your current kernel stuff over to the chroot except for your .config:
<pre>
cp -rva /usr/src/linux/.config $OC/usr/src/
</pre>

=== Tests ===

To enter this chrooted environment, simply type in linux32 chroot $OC

===Test #1===
Within the chroot:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure –host=i686-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared
Thread model: posix
gcc version 4.2.4</pre>
Within the host:
<pre>wdp@yulivee ~ $ gcc -v
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: ../configure –host=x86_64-pc-linux-gnu –enable-languages=c++,fortran –prefix=/usr –infodir=/usr/share/info –mandir=/usr/share/man –enable-__cxa_atexit –enable-threads –disable-nls –enable-target-optspace –with-gnu-ld –with-system-zlib –enable-shared –disable-multilib
Thread model: posix
gcc version 4.2.4</pre>

===Test #2===
Within the chroot:
<pre>wdp@yulivee ~ $ uname -m
i686</pre>
Within the host:
<pre>wdp@yulivee ~ $ uname -m
x86_64</pre>
as you can see - the chroot picks a not-64bit-gcc and uname -m returns not 64bit within the chroot - It's working ;-)

===Setting up the shell prompt===
You might want to ensure you don't accidently mistake the chroot environment for your host or vice-versa. Even if you don't think this could ever happen to you, it almost inevitably will if you keep a lot of terminals open at the same time like me (keios).

So to change your default prompt automatically on entering the chroot, add something like this to your .bashrc:
<pre>
if [ $(uname -m) = "i686" ]; then
# insert whatever works for you between @ and :
export PS1="\u@lunar32:\W> "
else
export PS1="\u@\h:\W> "
fi
</pre>

Your default prompt might look different, in that case customize the snippet as you see fit. If you use a colored prompt, changing the color usually should be enough to remind you.

===Updating the Chroot-System===
My Image might be quite old and it's usually good to have the chroot environment as up to date as the host is. Run the following commands to get new packages/modules:
<pre>wdp@yulivee ~ $ lin moonbase; lin theedge</pre>
Now you can run "lunar" and set some settings. The most important Settings might be the Optimizations. You can either go through: Option -> Optimize Architecture or you run "lunar optimize" at the console.

Modules might need working 32bit kernel headers, so make sure your gcc versions in- and outside the chroot are the same (see Test 1 above). If you need a specific gcc version that's not in the moonbase, use the --want $VERSION option of lin. Then build the kernel - you need the exact same version as you have on your host so you won't run into any trouble when e.g. installing video drivers for 3d acceleration later on:
<pre>root@mari-chan:/$ lin -cr linux-stable</pre>
When it asks you if you want to configure the kernel, say yes. In the menuconfig, use the "Load alternative config" option to load the kernel .config file you've copied to /usr/src earlier. Just enter:
<pre>../.config</pre>

After you've done configuring your lunar installation run:
<pre>wdp@yulivee ~ $ lunar renew</pre>
to update your whole installation. Get a cup of tea or coffee, this might take a while depending on your box and resources. At this state you should have a running 32 Bit Chroot. However we will still need to enhance this a bit. You want for sure X11 within the Chroot.

'''Important Note about lunar optimize''':
If you select optimizations for your chrooted environment, never ever use "native" as cpu optimization, this will break things. Always go with something safe, like i686 for example.

==Enhancing your Chroot Installation==
===X11===
We mounted /tmp from the host to /tmp inside the chroot already. This way we can use the X11 Socket to connect applications within the chroot to our running x11-server within the host. You could also, if this isn’t possible, use TCP Connections. But they come usually with overhead and thus performance of x11 stuff will be bad. Anyway. You don’t need a whole X11-Server within the chroot, just a few x11 libs. Let’s go:
<pre>wdp@linux32 ~ $ lin -cr libX11 fixesproto libXxf86vm libXt libXmu libXi mesa-lib xclock</pre>
This will install some X11 staff and libraries which are needed. You need now to allow X11-Unix-Socket Connections. Within the Chroot Environment edit your /etc/hostname and set "linux32" or something similar, remember this hostname. On the host type in: xhost +local:linux32 (Replace linux32 with the hostname you've set) or you could use "xhost +" which is insecure. Now you can test your X11 using xclock within your Chroot:
<pre>wdp@linux32 ~ $ export DISPLAY=”:0.0″
wdp@linux32 ~ $ xclock</pre>
You see the Clock? Fine it worked :)

===3D Acceleration===

If you want to run 32 Bit Games or Emulators like wine which don't work in native 64 Bit you might want to have 3D Acceleration. The important thing about this is that you have to use exactly the same driver version within your chroot as the driver version in your host, otherwise it will simply not work. Thats why you should try to keep both installations as up to date as possible.

==== nVidia ====

It is really important that you got your kernel files and kernel header from the host, also within the chroot. you can do that by copy (cp) from the host to the chrooted environment or you simply copy over the current kernel configuration to the chroot and compile the kernel within the chroot again. (i will explain this step better when i got more time) - Keep also in mind, by default the kernel is on hold within the lunar installation. you might want to "unhold" it using lvu.

On the Host check which NVIDIA drivers you got installed and what version it is:
<pre>wdp@yulivee ~ $ lvu installed NVIDIA
NVIDIA is not installed
wdp@yulivee ~ $ lvu installed NVIDIA-beta
185.18.14
wdp@yulivee ~ $</pre>
As you can see, i have NVIDIA-beta installed on the host. Within the Chroot i check now whats the current version of NVIDIA-beta within the moonbase using:
<pre>root@yulivee /usr/src # lvu version NVIDIA-beta
185.18.14</pre>
As you can see, it's the same version, so everything is fine, issue:
<pre>lget NVIDIA-beta</pre>
and copy the .run from /var/spool/lunar to /usr/src. Make it executable using chmod a+x file.run and run it finally using ./file.run. Of course you have to replace "file" with the real filename.

It will tell you that you run an X-Server and you have to stop this one first. Thats np, close X11, chroot into your chroot on the console and install NVIDIA. Exit the Chroot, start X11 again and everything is fine and should be done. You have to try around a bit with the NVIDIA Installer.

==== ATI (r600/kms enabled) ====

.

===Home directory===
This is the easiest Task. We just need to mount the home directory with bind:
<pre>mount -o bind /home $OC/home</pre>
Within the Chroot you can “su - username” and you’re in your home directory, without any problems or any flaws.

===Init Script===
These are only examples.. you’ll probably find nicer variants. Anyway, for both scripts you will need a configfile containing at least the variable CHROOTDIR - which should point to your Chroot Directory. Example:

Config
This config will be used by the initscripts below and our “chroot-enter script”.
<pre>$ cat /etc/lunar32chroot.conf
#!/bin/bash

# ^.^
OK="\033[00;29;1m[ \033[00;32;1mDONE\033[00;29;1m ]\033[0m"
FAIL="\033[00;29;1m[ \033[00;32;1mFAIL\033[00;29;1m ]\033[0m"

CHROOTDIR="/usr/local/32bit"</pre>
SysVinit:
This Init Script will mount with --bind some needed directories for the chroot and copy some files which you will most likely want to keep up to date, to have permissions and networking working correctly.
<pre>$ cat /etc/init.d/lunar32chroot

#!/bin/bash
#
# lunar32chroot Initializes the 32 Bit lunar chroot
#
# chkconfig: 2345 80 10
# description: Initializes 32 Bit chroot

if [ -e "/etc/lunar32chroot.conf" ]; then

source /etc/lunar32chroot.conf

else

# we need a config...
echo "No config file found"
echo -e $RESULT_FAIL
exit 0

fi

start() {

echo "Starting 32bit chroot..."

echo -n " Mounting chroot directories..."
mount -o bind /dev $CHROOTDIR/dev >/dev/null &&
if [ -d /dev/pts ]; then
mount -o bind /dev/pts $CHROOTDIR/dev/pts >/dev/null
fi &&
if [ -d /dev/shm ]; then
mount -o bind /dev/shm $CHROOTDIR/dev/shm >/dev/null
fi &&
mount -o bind /proc $CHROOTDIR/proc >/dev/null &&
if [ -d /proc/bus/usb ]; then
mount -o bind /proc/bus/usb $CHROOTDIR/proc/bus/usb >/dev/null
fi &&
mount -o bind /sys $CHROOTDIR/sys >/dev/null &&
mount -o bind /tmp $CHROOTDIR/tmp >/dev/null &&
mount -o bind /home $CHROOTDIR/home >/dev/null &&
mount -o bind /media/lain $CHROOTDIR/media/lain >/dev/null &&
mount -o bind /media/maelstrom $CHROOTDIR/media/maelstrom >/dev/null &&
mount -o bind /media/vortex $CHROOTDIR/media/vortex >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL

echo -n " Copying essential files..."
cp -afr /etc/resolv.conf $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/passwd $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/shadow $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/group $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/hosts $CHROOTDIR/etc > /dev/null &&
cp -afr /etc/localtime $CHROOTDIR/etc >/dev/null &&
cp -afr /etc/nsswitch.conf $CHROOTDIR/etc >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
}

stop() {

echo "Stopping 32bit chroot..."

echo -n " Unmounting 32bit chroot directories..."
umount -fl $CHROOTDIR/media/vortex >/dev/null &&
umount -fl $CHROOTDIR/media/maelstrom >/dev/null &&
umount -fl $CHROOTDIR/media/lain >/dev/null &&
umount -fl $CHROOTDIR/home >/dev/null &&
umount -fl $CHROOTDIR/tmp >/dev/null &&
umount -fl $CHROOTDIR/sys >/dev/null &&
if [ -d $CHROOTDIR/proc/bus/usb ]; then
umount -fl $CHROOTDIR/proc/bus/usb >/dev/null
fi &&
umount -f $CHROOTDIR/proc >/dev/null &&
if [ -d $CHROOTDIR/dev/shm ]; then
umount -fl $CHROOTDIR/dev/shm >/dev/null
fi &&
if [ -d $CHROOTDIR/dev/pts ]; then
umount -fl $CHROOTDIR/dev/pts >/dev/null
fi &&
umount -fl $CHROOTDIR/dev >/dev/null
exitcode=$?
[ ${exitcode} -eq 0 ] && echo -e $RESULT_OK
[ ${exitcode} -ne 0 ] && echo -e $RESULT_FAIL
}

. /lib/lsb/init-functions

</pre>
Now run “chkconfig –add lunar32chroot” to create the essential init scripts/symlinks for the different runlevels and you’re done.

===Entering Chroot - Script===
With this Script you just need to type “lunar32″ to enter the chroot environment. Keep in mind the "linux32" command should be available on all boxes, you dont need to install additional software. However its part of "util-linux".
<pre>$ cat /usr/bin/lunar32

#!/bin/bash
# little script to reduce some things to just one command
# especially for lazy people like me.

source /etc/lunar32chroot.conf

echo "Entering chroot..."
linux32 chroot "$CHROOTDIR" /bin/bash</pre>

Hint from Beko
Beko has shown me a dirty way (as he said) of doing the same using sudo, thus you can enter the environment without beeing root:
<pre>
linux32 sudo chroot "$CHROOTDIR" /bin/bash -c "su $WHOAMI"
</pre>
Negative Sideeffects: you're landing in / at the start and sudo has to run with NOPASS. Thats why this solution is dirty and might be a security risk. However.. :-) By the way Of course you want to replace $WHOAMI with your username - or a variable containing the current username.

==Applications==
===Fonts===
For most applications you will need some X11 Fonts installed within the Chroot. Its enough if you install these:
<pre>lin -cr mkfontdir mkfontscale bdftopcf font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-75dpi font-adobe-utopia-100dpi font-adobe-utopia-type1 font-bitstream-100dpi font-bitstream-75dpi font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi</pre>
some of them might not be needed, but well doesnt hurt to install them.

===Skype===
If you want to use Skype you will have to install some more libraries and tools:
<pre>cd /var/lib/lunar/moonbase
cp -rva qt4-apps/qt4 zlocal/
cd zlocal/qt4
vim DEPENDS</pre>
Remove this line:
<pre>depends %X</pre>
Finally install needed stuff:
<pre>lin -cr dbus alsa-utils videoproto libXv scrnsaverproto libXScrnSaver qt4</pre>
It might be needed to install dbus-qt3 (not sure) if so, you have to copy the module to zlocal and edit the DEPENDS file (of qt3 and of dbus-qt3) to remove the X Dependecy.

Skype should now work. You might want to look at the "fonts" Section because skype will display broken fonts :)

==Useful Documentation:==
* http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 [English]
* http://ubuntuforums.org/showthread.php?t=24575 [English]
* http://wiki.ubuntuusers.de/32-Bit_chroot [German]
* http://www.debian-administration.org/article/Installing_apps_in_a_32-bit_chroot_in_AMD64_Debian_system [English]

Module Basics

2007-09-03T11:12:35Z

Keitekk: /* 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, then answer "yes" would be stored in the ENABLE_FOO variable and --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

User:Keitekk

2007-09-03T11:10:24Z

Keitekk:

'''stuff test area'''
''wikis are interesting''

----

[http://www.sikkk.info weblog]

--[[User:Keitekk|_ktx]] 13:10, 3 Sep 2007 (CEST)