SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
As far as I know, there is no diference between slackware x86 and x86_64.
If you use slackbuilds, there is no problem, allmost all programs can be compiled for 64 bits.
Alien bob have a tutorial to make a slackware multilib in is wiki.
I'm gonna start the install using Ponce's unofficial dvd and will report back
and will start Alien's mirror-slackware-current.sh for x86_64 on other pc....
I have used unofficial -current ISOs before and they worked okay. However, I now maintain and only use Alien Bob's -current ISOs. I like the md5 checksum feature of Eric's -current script.
Edit(added later): I also manually upgrade my boxes to -current.
If you replace Seamonkey with the 32-bit version (not the 32-bit compatibility version, the 32-bit version), and install the 32-bit or (64-bit and 32-bit compatibility) versions of ORBit2 and GConf, then you can run 32-bit Chrome.
Distribution: Slint64-14.2rc on Lenovo Thinkpad W520
As of 13.1, you machine's architecture is automatically detected by the slackbuilds. This is true for the "official" ones, i.e. those shipped with Slackware 13.1, and for those provided by slackbuilds.org as well. So there is no more need to indicate it at package building time -- provided you are not cross-compiling, of course
See below the relevant part of a "new" slackbuild:
# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) export ARCH=i486 ;;
arm*) export ARCH=arm ;;
# Unless $ARCH is already set, use uname -m for all other archs:
*) export ARCH=$( uname -m ) ;;
Last edited by Didier Spaier; 06-29-2010 at 02:17 PM.