- RUNNING 32 BIT ON 64 BIT LINUX FOR FREE
- RUNNING 32 BIT ON 64 BIT LINUX INSTALL
- RUNNING 32 BIT ON 64 BIT LINUX FULL
- RUNNING 32 BIT ON 64 BIT LINUX SOFTWARE
It uses the above “ convertpkg-compat32” script to grab every package that is on this internal list, and convert these into '-compat32' packages. This script contains an internal list of what I consider the essential subset of 32bit Slackware packages. These are the three useful scripts which the package installs: Please read the detailed ' README' file in the /usr/doc/compat32-tools-*/ directory, it will help you on your way. This “ compat32-tools” package needs some explanation.
RUNNING 32 BIT ON 64 BIT LINUX INSTALL
Their purpose is to let you extract the content from any 32bit Slackware package and use that to create a new package which you can safely install on your 64bit Slackware. Instead, I wrote a few scripts (parts of the script code were written by Fred Emmott of Slamd64 fame) and wrapped these into a “ compat32-tools” package.
RUNNING 32 BIT ON 64 BIT LINUX FOR FREE
After all, you have probably bought the Slackware 14.2 DVD so you already possess both 64bit and 32bit versions of Slackware… or else the 32bit Slackware tree is available for free download of course I decided that it would be a waste of download bandwidth if I created 32bit compatibility versions of Slackware packages myself. Hence the name “32bit compatibility package”. What you need, is a 32bit package that does not conflict with whatever is already present in 64bit Slackware. It will seriously mess up your system if that happens.Ī little bit of extra care is required so that unnecessary/unwanted files are stripped from the 32bit packages before you install them. REPOPLUS=( slackpkgplus multilib restricted alienbob ktown )Īnd furthermore, if the 32bit package contains binaries (something like /usr/bin/foo), they will overwrite their 64bit counterparts when you install the 32bit package on top. PKGS_PRIORITY=( multilib restricted alienbob ktown ) The choice of the word “multilib” is arbitrary, it could just as well have been “compat32”, as long as you use it consistently.Ĭontents of an example file “/etc/slackpkg/nf” would be as follows: SLACKPKGPLUS=on The keyword “multilib” which defines the name for the repository must be the same keyword used in the “slackpkg” commands above. The PKGS_PRIORITY ensures that multilib packages of gcc and glibc have precedence over the Slackware originals.
This is how a typical configuration would look like - for a computer running Slackware-current and using Alien BOB's KDE testing repository. In a section further down, I will explain how you can take a 32-bit Slackware package (say, the “mesa” package) and re-package its content into a “mesa-compat32” package that you can install straight away on Slackware64.
RUNNING 32 BIT ON 64 BIT LINUX FULL
This was one of the reasons for not adding full multilib to Slackware64 - we create the right preconditions but require the user to act if she needs multilib. You simply take them from the 32-bit Slackware package tree! This means, that you do not have to compile 32-bit packages from scratch in order to add multilib capability to the 64bit system. Slackware on the other hand, is a distribution that consists of a 32bit and 64bit release, both of which are being developed in parallel. These forks added the 32bit compatibility layer by recompiling a lot of their packages as 32bit binaries. When Slackware64 was released, it had an advantage over the 64bit “forks” that existed out there.
RUNNING 32 BIT ON 64 BIT LINUX SOFTWARE
Then, system libraries are taken from 32bit Slackware and installed in the 64bit Slackware system alongside their 64bit versions which completes the process of creating a 32bit compatibility software layer.
0 kommentar(er)
