The Configuration script: /etc/compat32pkg/compat32pkg.conf

This script contains the following variables that users could overwrite when needed.

$ compat32pkg --clear-cache slackware-32

$ compat32pkg --clear-cache compat-32

PKGS_PRECEDENCE_ORDER=( 
			"slackware/a/aaa_elflibs" \
			"patches/packages/.*" \
			"slackware/.*" \
			"extra/.*"  \
			"testing/.*" \
			"pasture/.*"  \
			)

TRUSTED_EXTERNS_CMD=( "installpkg" "upgradepkg" "c32pkg-notify-send" )

TRUSTED_EXTERNS_CMD=( "installpkg" "upgradepkg" "c32pkg-notify-send" "FOO" )

The file of mirrors: /etc/compat32pkg/mirrors

This file is required but its usage is optional and always implicit. It contains the list of mirrors and their aliases. It consists in a set of entries that rely on the syntax below:

mirror-entry ::= <key> = <mirror-addr>
key           ::= string
mirror-addr  ::= <local-directory>url>

For example, if you look at the content of this file, you will see something like that:

DVD               = /mnt/DVD
WorldWide-13.0    = ftp://mirrors.kernel.org/slackware/slackware-13.0
WorldWide-13.1    = ftp://mirrors.kernel.org/slackware/slackware-13.1
WorldWide-current = ftp://mirrors.kernel.org/slackware/slackware-current

Germany-13.0    = ftp://ftp.gwdg.de/pub/linux/slackware/slackware-13.0
Germany-13.1    = ftp://ftp.gwdg.de/pub/linux/slackware/slackware-13.1
Germany-current = ftp://ftp.gwdg.de/pub/linux/slackware/slackware-current

• The entry with the key DVD refer to the local directory in which dvd are mounted by users.
• The entries with the keys WorldWide-13.0, WorldWide-13.1 and WorldWide-current respectively refer to the Slackware mirrors of versions 13.0, 13.1 and current. The same apply to the entries with keys Germany-13.0, Germany-13.1 and Germany-current, but those key refers to servers in another country.

Each of the mirrors from this file can be defined as the default mirror for compat32pkg or explicitly passed to compat32pkg using their aliases introduced by an "at symbol" :

1. To defines the mirror bound to the key Germany-13.1 as the default mirror, the variable DEFAULT_MIRROR of configuration script /etc/compat32pkg/compat32pkg.conf should be declared as below:

   DEFAULT_MIRROR=@Germany-13.1

2. To select the mirror bound to the key WorldWide-13.1 using the command line, simply pass this key, introduced by an "at symbol", as argument to the parameter --mirror :

   $ compat32pkg --mirror @WorldWide-13.1  ...

The blacklist file : /etc/compat32pkg/blacklist

This file is required. It contains the patterns (one per line) which identify permanently excluded packages from conversion, installation, updating, and removal. Each pattern can be the basename of a package (ex: mozilla-firefox), the baseref of a package (ex: slackware/xap/mozilla-firefox), or a regular expression (ex: mozilla-.*,pasture/.*).

This file has to be used for permanent exclusion of packages only. To exclude a package, or a set of package, punctually, during execution of compat32pkg only, the optional parameter --exclude should be used instead of this file.

The configuration file for the "layer-32" : /etc/compat32pkg/multilib-32bit-packages.lst

This file contains the list of packages (ie their basename) which provide the 32-bit part of the multilib (aka "layer-32") for Slackware-64.

• This file must start with a line formatted as below :

  $ #!version=M.m.YYMMDD

  M.m.YYMMDD must be the version number of the file, where, "M" is the major revision number, "m" the minor revision number, and, "YYMMDD" the date of the revision.

  This information is used by the configuration update mechanism, ie, when compat32pkg is executed in mode --layer-32-config.

• The packages which provide the 32-bit part of the multilib must be given using their basenames only, and there must be one basename per line only.

  As this configuration file must be usable on all slackware-64 versions, it must contain references of all packages for all versions of the multilib. Therefore, this implies that a reference to a package could only be removed when the package is not any more used by all version of the multilib.

• Each line, whose the first non-whitespace character is a "#", is treated as a comment, and ignored.

As this file describes the 32-bit part of the multilib, it could seem natural to pass it as argument to compat32pkg to manage this layer. However, this usage is discouraged, and user should use the keyword layer-32 instead, as, this one is more explicit and, furthermore, offers a better management of the 32-bit part of the multilib, mostly when checking for updates, or, when upgrading this layer :

$ compat32pkg --mirror @WorldWide-13.0 --install layer-32
$ compat32pkg --mirror @WorldWide-13.1 --list-updates layer-32
$ compat32pkg --remove all --exclude layer-32
						

The directory of triggers : /etc/compat32pkg/triggers.d

This directory is required and is dedicated to the triggers.

See point The triggers for detailed informations about this feature.

The logfile : /var/log/compat32pkg.log

This file is used by compat32pkg to log all of its activity. As this file could take more disk space over time, it has to be reset from time to time by executing :

$ compat32pkg --reset-log

Creates the trigger named NAME to execute the task TASK following the event EVENT.

NAME is the name of the trigger to create, and by extension, the basename of the file that describes this trigger.

EVENT can be one of the supported events.

STATUS_FIELD   ::= STATUS=<enabled>|<disabled>
EVENT_FIELD    ::= EVENT=<C32PKG_EVENT>
TASK_FIELD     ::= TASK=<message>|<warning>|<exec:CMD>
TASKARG_FIELDS ::= TASK_ARG[i]=text

mesa-installed-warn.trigger

Warns user he should reinstall any proprietary driver (like nvidia, ati) when the package mesa-compat32 has been installed.

By default, this trigger is enabled. It can be disabled using compat32pkg as below :

$ compat32pkg --trigger disable list:mesa-installed-warn

When this trigger is enabled and the package mesa is one of the packages targeted by compat32pkg --install ..., the user will be warned as below :

mesa-updated-warn.trigger

Warns user he should reinstall any proprietary driver (like nvidia, ati) when the package mesa-compat32 has been updated.

By default, this trigger is enabled. It can be disabled using compat32pkg as below :

$ compat32pkg --trigger disable list:mesa-updated-warn

When this trigger is enabled and the package mesa is one of the packages targeted by compat32pkg --upgrade ..., the user will be warned as below :

layer32-cfg-update-found-notify.trigger

Notifies user, using a tooltip, when there's an available update for the descriptor of the layer-32.

By default, this trigger is disabled. It can be enabled using compat32pkg as below:

$ compat32pkg --trigger enable list:layer32-cfg-update-found-notify

When this trigger is enabled, this is a good idea to create a cron job to be notified on available update for the descriptor of layer-32. This cron job could be as below :

0 */2 * * mon compat32pkg --layer-32-config check-update &>/dev/null

As needed, the notification can be sent to another screen using the variable DISPLAY as in example below :

0 */2 * * mon DISPLAY=:1 compat32pkg --layer-32-config check-update &>/dev/null

When this trigger is enabled, and there's an update for the descriptor of the layer-32 when executing compat32pkg --layer-32-config check-update, the user will be notified through a tooltip as below :

layer32-installed-notify.trigger

Notifies user, using a tooltip, following the installation of the layer-32.

By default, this trigger is disabled. It can be enabled using compat32pkg as below:

$ compat32pkg --trigger enable list:layer32-installed-notify

When this trigger is enabled, and the layer-32 is installed (ie compat32pkg --install layer-32), the user will be notified through a tooltip as below :

layer32-removed-notify.trigger

Notifies user, using a tooltip, when the layer-32 has been removed.

By default, this trigger is disabled. It can be enabled using compat32pkg as below:

$ compat32pkg --trigger enable list:layer32-removed-notify

When this trigger is enabled, and the layer-32 is removed (ie compat32pkg --remove layer-32), the user will be notified through a tooltip as below :

layer32-update-found-notify.trigger

Notifies user, using a tooltip, when there are available updates for the layer-32.

By default, this trigger is disabled. It can be enabled using compat32pkg as below:

$ compat32pkg --trigger enable list:layer32-update-found-notify

When this trigger is enabled, this is a good idea to create a cron job to be notified on available updates for the layer-32. This cron job could be as below :

0 */2 * * mon,wed,fri compat32pkg --check-updates layer-32 &>/dev/null

As needed, the notification can be sent to another screen using the variable DISPLAY as in example below :

0 */2 * * mon,wed,fri DISPLAY=:1 compat32pkg --check-updates layer-32 &>/dev/null

In the examples below, it's assumed that a default mirror has been defined into the configuration's script (i.e: /etc/compat32pkg/compat32pkg.conf).

When this trigger is enabled, and there's updates for the layer-32 (ie compat32pkg --check-updates layer-32), the user will be notified through a tooltip as below :

layer32-updated-notify.trigger

Notifies user, using a tooltip, when available updates for the layer-32 have been installed.

By default, this trigger is disabled. It can be enabled using compat32pkg as below:

$ compat32pkg --trigger enable list:layer32-updated-notify

When this trigger is enabled, and the layer-32 is updated (ie compat32pkg --upgrade layer-32), the user will be notified through a tooltip as below :

mesa-installed-notify.trigger

Notifies user, using a tooltip, he should reinstall any proprietary driver (like nvidia, ati) when the package mesa-compat32 has been installed.

By default, this trigger is disabled. It can be enabled using compat32pkg as below:

$ compat32pkg --trigger enable list:mesa-installed-notify

When this trigger is enabled and the package mesa is one of the packages targeted by compat32pkg --install ..., the user will be warned as below :

mesa-updated-notify.trigger

Notifies user, using a tooltip, he should reinstall any proprietary driver (like nvidia, ati) when the package mesa-compat32 has been updated.

By default, this trigger is disabled. It can be enabled using compat32pkg as below:

$ compat32pkg --trigger enable list:mesa-updated-notify

When this trigger is enabled and the package mesa is one of the packages targeted by compat32pkg --upgrade ..., the user will be warned as below :

Downloading packages and converts them to format compat32

This is done by using compat32pkg in mode --convert. As this mode needs a source to get the packages to convert, a mirror should be supplied in argument of parameter --mirror unless if a default mirror is provided into the configuration's script (i.e: /etc/compat32pkg/compat32pkg.conf). It is also possible to punctually exclude packages from this process by using optional parameter --exclude :

$ compat32pkg --convert list:l/alsa-lib,xap/mozilla-firefox
$ compat32pkg --mirror @France-13.0 --convert list:"slackware/l/alsa-\(lib\|oss\),slackware/xap/mozilla-.*" --exclude list:.*thunderbird
$ compat32pkg --convert /etc/compat32pkg/multilib-32bit-packages.lst

Since compat32pkg version 1.0.101201, the argument layer-32 can be passed in argument of --convert. In this context, layer-32 provides a simple way to automate conversion of packages that provide the 32-bit part of the multilib' :

$ compat32pkg --mirror @WorldWide-13.1 --convert layer-32

compat32pkg will store the downloaded packages and the converted packages into the directories pointed by the variables SLACK32PKG_CACHE and COMPAT32PKG_CACHE declared into the configuration's script (i.e /etc/compat32pkg/compat32pkg.conf).

In the example above, the packages to convert were identified using their baseref, which imply, unless in few exceptional cases, the selection of one package per baseref.

Now, If we use basenames instead of baserefs, the query will be less specific and more than one package would match the query. Therefore, In that case, the search engine will automatically choose the package according to the order given by the variable PGKS_PRECEDENCE_ORDER like in the example below:

As we can see above, in that case, the search engine has selected a newer version (3.6.8 vs 3.5.2) of package mozilla-firefox than in sample #1.

Obviously, the same rule as above is applied in case of mixing of basename and baseref into the query like as below :

Downloading packages, converts them to format compat32 and installs resulting packages

This works like for converting packages unlike that the parameter --install has to be used instead of --convert.

$ compat32pkg --install list:l/alsa-lib,xap/mozilla-firefox
$ compat32pkg --mirror @France-13.0 --install list:"slackware/l/alsa-\(lib\|oss\),slackware/xap/mozilla-.*" --exclude list:.*thunderbird
$ compat32pkg --install /etc/compat32pkg/multilib-32bit-packages.lst

Since compat32pkg version 1.0.101201, the argument layer-32 can be passed in argument of --install. In this context, layer-32 provides a simple way to automate install of packages that provide the 32-bit part of the multilib' :

$ compat32pkg --mirror @ WorldWide-13.1 --install layer-32

compat32pkg will store the downloaded packages and the converted packages into the directories pointed by the variables SLACK32PKG_CACHE and COMPAT32PKG_CACHE declared into the configuration's script (i.e /etc/compat32pkg/compat32pkg.conf).

The Installation of packages resulting from conversion process is done by using the command upgradepkg and its option --install-new.

Checks available updates for a given subset of packages to format compat32

This is done by using compat32pkg in mode --check-updates. As this mode needs a source to search updates, a mirror should be supplied in argument of parameter --mirror unless a default mirror is provided into the configuration's script (i.e /etc/compat32pkg/compat32pkg.conf).

To check available updates for all installed packages, the keyword "all" has to be passed as argument of parameter --check-updates. Otherwise, the patterns which identify the installed packages to be checked must be given, as always, in a text file or in a comma separated list of pattern introduced by the keyword "list:". However, as installed compat32 packages can only be identified by their basenames, the use of baserefs is prohibited and will result in an error.

It is also possible to punctually exclude some of installed packages and some of updates by using optional parameter --exclude.

If updates were found, compat32pkg will terminate with 0 as exit code. Otherwise, it will terminate with 100 as exit code.

$ compat32pkg --check-updates list:mozilla-firefox
$ compat32pkg --mirror @France-13.0 --check-updates all --exclude list:patches/.*
$ compat32pkg --check-updates /etc/compat32pkg/multilib-32bit-packages.lst

Since compat32pkg version 1.0.101201, the argument layer-32 can be passed in argument of --check-updates. In this context, layer-32 provides a simple way to only check updates for packages that provide the 32-bit part of the multilib' :

$ compat32pkg --mirror @WorldWide-13.1 --check-updates layer-32

When the argument layer-32 is used, compat32pkg will check updates for the 32-bit part of the multilib only. In this case, the update mechanism recognizes as an update:

1. any new version of any installed package of the 32-bit part of the multilib
2. any package of the 32-bit part of the multilib which is not installed, nor blacklisted, nor excluded.

This implies that any addition (of package) into the file that describes the 32-bit part of the multilib is handled as update.

Lists available updates for a given subset of packages to format compat32

This works like for checking updates unlike that the parameter --list-updates has to be used instead of --check-updates.

$ compat32pkg --list-updates list:mozilla-firefox
$ compat32pkg --mirror @France-13.0 --list-updates all --exclude list:patches/.*
$ compat32pkg --list-updates /etc/compat32pkg/multilib-32bit-packages.lst

Since compat32pkg version 1.0.101201, the argument layer-32 can be passed in argument of --list-updates. In this context, layer-32 provides a simple way to only enumerate the updates for packages that provide the 32-bit part of the multilib' :

$ compat32pkg --mirror @WorldWide-13.1 --list-updates layer-32

When the argument layer-32 is used, compat32pkg will check updates for the 32-bit part of the multilib only. In this case, the update mechanism recognizes as an update:

1. any new version of any installed package of the 32-bit part of the multilib
2. any package of the 32-bit part of the multilib which is not installed, nor blacklisted, nor excluded.

This implies that any addition (of package) into the file that describes the 32-bit part of the multilib is handled as update.

Downloads available updates for a given subset of packages to format compat32 and convert them

This works like for checking updates unlike that the parameter --convert-updates has to be used instead of --check-updates.

$ compat32pkg --convert-updates list:mozilla-firefox
$ compat32pkg --mirror @France-13.0 --convert-updates all --exclude list:patches/.*
$ compat32pkg --convert-updates /etc/compat32pkg/multilib-32bit-packages.lst
$ compat32pkg --mirror @WorldWide-13.1 --convert-updates layer-32

compat32pkg will store the downloaded packages and the converted packages into the directories pointed by the variables SLACK32PKG_CACHE and COMPAT32PKG_CACHE declared into the configuration's script (i.e /etc/compat32pkg/compat32pkg.conf)..

The argument layer-32 is available since version 1.0.101201. In the context of --convert-updates, it provides a simple way to only convert updates for packages that provide the 32-bit part of the multilib. In this case, the update mechanism recognizes as an update:

1. any new version of any installed package of the 32-bit part of the multilib
2. any package of the 32-bit part of the multilib which is not installed, nor blacklisted, nor excluded.

This implies that any addition (of package) into the file that describes the 32-bit part of the multilib is handled as update.

Downloads available updates for a given subset of packages to format compat32, converts them, and upgrade

This works like for converting updates unlike that the parameter --upgrade has to be used instead of --convert-updates.

$ compat32pkg --upgrade list:mozilla-firefox
$ compat32pkg --mirror @France-13.0 --upgrade all --exclude list:patches/mozilla-firefox
$ compat32pkg --upgrade /etc/compat32pkg/multilib-32bit-packages.lst
$ compat32pkg --mirror @WorldWide-13.1 --upgrade layer-32

The Installation of packages resulting from conversion process is done by using the command upgradepkg.

The argument layer-32 is available since version 1.0.101201. In the context of --upgrade, it provides a simple way to only upgrade packages that provide the 32-bit part of the multilib. In this case, the update mechanism recognizes as an update:

1. any new version of any installed package of the 32-bit part of the multilib
2. any package of the 32-bit part of the multilib which is not installed, nor blacklisted, nor excluded.

This implies that any addition (of package) into the file that describes the 32-bit part of the multilib is handled as update.

Looks for packages on a slackware-32 mirror

This is done by using compat32pkg in mode --search. As this mode needs a source to search packages, a mirror should be supplied in argument of parameter --mirror unless if a default mirror is provided into the configuration's script (i.e /etc/compat32pkg/compat32pkg.conf). It is also possible to punctually exclude packages from this process by using optional parameter --exclude :

$ compat32pkg --search list:.*
$ compat32pkg --search list:l/alsa-lib,xap/mozilla-firefox
$ compat32pkg --mirror @France-13.0 --search list:"slackware/l/alsa-\(lib\|oss\),slackware/xap/mozilla-.*" --exclude list:.*thunderbird
$ compat32pkg --search /etc/compat32pkg/multilib-32bit-packages.lst

Since compat32pkg version 1.0.101201, the argument layer-32 can be passed in argument of --search. In this context, layer-32 provides a simple way to search only the packages that provide the 32-bit part of the multilib' :

$ compat32pkg --mirror @WorldWide-13.1 --search layer-32

The column "mult." indicates if it exists other versions (ie duplicates) of the same package (ie with the same basename).

Removing of installed compat32 packages

This is done by using compat32pkg in mode --remove. To remove all installed compat32 packages, the keyword "all" has to be passed as argument of parameter --remove. Otherwise, the patterns which identify the installed packages to remove must be given, as always, in a text file or in a comma separated list of pattern introduced by the keyword "list:". It is also possible to punctually exclude packages from this process by using optional parameter --exclude.

As installed compat32 packages can only be identified by their basenames, the use of baserefs is prohibited and will result in an error.

$ compat32pkg --remove all  --exclude list:mozilla-firefox
$ compat32pkg --remove list:mozilla-firefox
$ compat32pkg --remove /etc/compat32pkg/multilib-32bit-packages.lst

Since compat32pkg version 1.0.101201, the argument layer-32 can be passed in argument of --remove. In this context, layer-32 provides a simple way to only remove packages that provide the 32-bit part of the multilib' :

$ compat32pkg --mirror @WorldWide-13.1 --remove layer-32

Checking updates, and upgrade, of the configuration file for the "layer-32"

By using compat32pkg in mode --layer-32-config, the user can check available updates, and upgrade, the configuration file for the layer-32

$ compat32pkg --layer-32-config <check-update>|<update> [ updates-site-url ] 

This mode allows users to follow evolving of the layer-32, easily, without to have to install a new version of compat32pkg, nor to have to look for changes made to the layer-32.

The argument updates-site-url is optional. When presents, this must be the url of the updates site that compat32pkg will use for the requested update operation, otherwise, the default one (ie http://sourceforge.net/projects/compat32pkg/files/updates-site) will be used.

In case of configuration file for the layer-32, the following files must be available on the selected updates-site, otherwise the update operation will fail :

1. The latest revision of the configuration file for the layer-32 which must be named multilib-32bit-packages.lst

2. The file containing information about the file (1), named multilib-32bit-packages.lst.infos, and, which must contain the following data:

   • The version number of the configuration file (1). This version must be given by a field named version :

     version = 1.4.110319

   • The md5sum of the configuration file (1). This value must be given by a field named md5sum :

     md5sum = 6f7d19e164201754d28a66c59913afed

   • The description of changes since the previous revision. This description must be given by using lines starting by a character ":". Example:

     :This is the description of changes since the previous revision of the file
     :that describes the layer-32.
     :  + package X was added. This does not affect the multilib for 13.0

To check available updates related to the configuration file for the layer-32, compat32pkg will have to be used like below:

$ compat32pkg --layer-32-config check-update
$ compat32pkg --layer-32-config check-update	http://my.compat32pkg.updates-site-url

When an update is available, the changes since the previous revision of the configuration files for the layer-32 is shown, as in the sample below :

To upgrade the configuration file for the layer-32 to the version available on the selected updates site, compat32pkg will have to be used like below :

$ compat32pkg --layer-32-config update
$ compat32pkg --layer-32-config update	http://my.compat32pkg.updates-site-url

When an update is available, a backup of the previous revision of the configuration file for layer-32 is automatically performed prior to the updating. This backup will be named multilib-32bit-packages.lst.bak_<date>, where <date> is the current date to format YYYYMMDD.

List the dependencies

Since revision 1.6.130502, compat32pkg includes the command --depends which lists the dependencies required by a single 32-bit binary, or by the 32-bit binaries in a directory hierarchy, or by the 32-bit binaries from an installed package.

  $ compat32pkg --depends skype

  compat32pkg ver. 1.6.130502 (stable)

  [--depends] Started on Thu 02 May 2013 04:14:27 PM CEST

  [--depends]   Inspecting 32-bit binaries from package skype-4.1.0.20-i486-1_SBo
  [--depends]     Found 1 32-bit binaries.        
  [--depends]     Found 48 dependencies (0 orphans, 0 unresolved)

  [--depends]   48 dependencies are fulfilled by these packages:

          aaa_elflibs-compat32
          alsa-lib-compat32
          bzip2-compat32
          cxxlibs-compat32
          expat-compat32
          fontconfig-compat32
          freetype-compat32
          gcc
          gcc-g++
          glib2-compat32
          glibc
          glibc-solibs
          gst-plugins-base-compat32
          gstreamer-compat32
          libICE-compat32
          libSM-compat32
          libX11-compat32
          libXScrnSaver-compat32
          libXau-compat32
          libXdmcp-compat32
          libXext-compat32
          libXrender-compat32
          libXv-compat32
          libffi-compat32
          libpng-compat32
          libxcb-compat32
          libxml2-compat32
          qt-compat32
          sqlite-compat32
          util-linux-compat32
          zlib-compat32

  [--depends] Ended on Thu 02 May 2013 04:14:31 PM CEST     					
					

Clearing the cache(s)

As said before here and here, both directories used to store downloaded packages and the converted packages have to be cleaned periodically. This could be easily automated by using compat32pkg in mode --clear-cache with one of the arguments below :

Resetting the logfile

As said here, the logfile used by compat32pkg to log its activity can be reset using the mode --reset-cache.

Using of Firefox 32-bit and Firefox 64-bit at the same time

First of all, the 32-bit version of Firefox must be installed. This is easily done by using compat32pkg like as below :

$ compat32pkg --install list:mozilla-firefox

compat32pkg ver. 0.9.101808
[--install] Started on Wed 08 Sep 2010 12:15:45 PM CEST
[--install]   Using mirror ftp://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-13.0
[--install]   Local system is Slackware/x86_64 version 13.0.0.0.0
[--install]   Mirrored system is Slackware/i486 version 13.0
[--install]   Slackware-32 packages will be stored into /var/cache/compat32pkg/slackware-32
[--install]   compat32 packages will be stored into /var/cache/compat32pkg/compat-32

[--install]   1 package(s) were found (1,020 sec.)

[--install]   Processing package mozilla-firefox version 3.6.8 build 1
[--install]     Package successfully downloaded (/var/cache/compat32pkg/slackware-32/mozilla-firefox-3.6.8-i686-1.txz)
[--install]     Package converted to format compat32 (/var/cache/compat32pkg/compat-32/mozilla-firefox-compat32-3.6.8-x86_64-1.txz)
[--install]     Package successfully installed.

[--install] Ended on Wed 08 Sep 2010 12:16:53 PM CEST

Once firefox-32 is installed you have to execute,as root, the command update-pango-querymodules, otherwise, firefox will be unusable (its output will be unreadable). Another way to achieve this is to reset the system :

$ su
Password:
$ /usr/bin/update-pango-querymodules

Now, to be able to use firefox 32-bit and 64-bit at the same time, you will need to create two different profile, one for the 32-bit version and another for the 64-bit version.

Create a profile for 64-bit firefox

Close all instance of Firefox and run it as follow :

$ /usr/bin/firefox -P

Into "Firefox - Choose User Profile", create a profile named "64bit" for example, validate and exit.

Create a profile for 32-bit firefox

Close all instance of Firefox and run it as follow :

$ /usr/bin/32/firefox -P

Into "Firefox - Choose User Profile", create a profile named "32bit" for example, validate and exit.

Once both profile created, both versions of firefox can be started using their respective profile:

$ /usr/bin/firefox -P "64bit" --no-remote &
$ /usr/bin/32/firefox -P "32bit" --no-remote &

Firefox-32 plugins

Mplayer plugins

First of all, the 32-bit version of this plugin have to be installed. This is easily done by using compat32pkg like below :

$ compat32pkg --install list:mplayerplug-in

compat32pkg ver. 0.9.101808
[--install] Started on Wed 08 Sep 2010 14:03:51 PM CEST
[--install]   Using mirror ftp://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-13.0
[--install]   Local system is Slackware/x86_64 version 13.0.0.0.0
[--install]   Mirrored system is Slackware/i486 version 13.0
[--install]   Slackware-32 packages will be stored into /var/cache/compat32pkg/slackware-32
[--install]   compat32 packages will be stored into /var/cache/compat32pkg/compat-32

[--install]   1 package(s) were found (1,094 sec.)

[--install]   Processing package mplayerplug-in version 3.55 build 1
[--install]     Package successfully downloaded (/var/cache/compat32pkg/slackware-32/mplayerplug-in-3.55-i486-1.txz)
[--install]     Package converted to format compat32 (/var/cache/compat32pkg/compat-32/mplayerplug-in-compat32-3.55-x86_64-1.txz)
[--install]     Package successfully installed.                           

[--install] Ended on Wed 08 Sep 2010 14:03:59 PM CEST

Once installed, this plugin should work flawlessly the next time firefox-32 will be started. It is possible to test it here, which should give you something like below :

Java plugin

First of all, the 32-bit version of the JRE or of the JDK has to be installed. This is easily done by using compat32pkg like below :

$ compat32pkg --install list:jre

compat32pkg ver. 0.9.101808
[--install] Started on Wed 08 Sep 2010 16:13:44 PM CEST
[--install]   Using mirror ftp://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-13.0
[--install]   Local system is Slackware/x86_64 version 13.0.0.0.0
[--install]   Mirrored system is Slackware/i486 version 13.0
[--install]   Slackware-32 packages will be stored into /var/cache/compat32pkg/slackware-32
[--install]   compat32 packages will be stored into /var/cache/compat32pkg/compat-32

[--install]   1 package(s) were found (1,059 sec.)

[--install]   Processing package jre version 6u16 build 1
[--install]     Package successfully downloaded (/var/cache/compat32pkg/slackware-32/jre-6u16-i586-1.txz)
[--install]     Package converted to format compat32 (/var/cache/compat32pkg/compat-32/jre-compat32-6u16-x86_64-1.txz)
[--install]     Package successfully installed.                

[--install] Ended on Wed 08 Sep 2010 16:16:17 PM CEST

After installation of the jre (or jdk), the plugins have to be installed manually as explained below :

• In case of firefox < 3.6

   $ ln -sfv /usr/lib/java/plugin/i386/ns7/libjavaplugin_oji.so /usr/lib/mozilla/plugins/

• In case of firefox >= 3.6

   $ ln -sfv /usr/lib/java/lib/i386/libnpjp2.so /usr/lib/mozilla/plugins/

Afterward, the java plugin should work flawlessly the next time firefox-32 will be started. It is possible to test it here which should give you something like below :