How to install Slackware (plus others)
Dear New Slackware Linux Potential User:
I simply cannot imagine life in a Windows only world. Windows is fine for playing games and a basic fallback (when there is nothing else available) but Gawd forbid that we ever have to depend on it. I've meet some of the fellas that have worked on Windows and think it's the cat's meow of operating systems. These people are either mineral deficient or chemical dependent. If you could only see these folks in action. "Hey, I got an idea, let's just slap that together!?!". In any event, we all can't be geniuses, I guess! I am so thankful we have a world where if you want to put something together properly, you can. Your not limited to an sea of monkeys out to rule the place. If you like putting something together yourself and like being around people that also do, then you'll love Linux. There is something about doing it yourself that makes you feel like it's worth the effort. And the rewards are great. I hope things work out really well for you in your endeavor to install the latest Slackware distribution of Linux. I've included most of my secrets here. It should be a rewarding experience. Incidentally, I'm running a Kernel compiled for my AMD Athlon64. I "think" this means that my kernel is running in 64-bit mode while most of the support programs are still in 32 bit. This is pretty cool as it gives me the best of both worlds with no problems anywhere. Of all the Linux distributions and all the previous installations of Slackware I've had, I have to say that this installation (Slackware 12 + Dropline) is by far the best. Hope your experience is just as similar and even more rewarding. Welcome to the world where things just work better and if they don't you can soon figure it out and fix it yourself! I have to say, that over the last few years this site has been bit of an anchor and an outlet for me. I think this thread (a reflection of everything that I've learned from Linux) is my way of saying "Thanks" for being so good to me. It's nice to be able to be part of something this big (aka Linux). Who would have thought that not so many years ago when Linus set out to create an operating system as a simple school project that it would grow into this...! Everybody that wants to needs to be able to be part of Linux. Something that really only costs a little bit of your time and yet gives so much back. It's nice to be part of this do-it-yourself world as opposed to having everything handed to you on a platter, you just feel like your part of it! Part of something really great... ranks right up there with solving world hunger... not kidding! Incidentally, have you sponsored a child yet? Cause you gotta have faith! - Perry ps. Which says nothing of the fact that just by using Linux your insulated from 99.99% of all viruses written for and derived from the Windows platform! Step 1: Download Slackware 12 1. download slackware 12 iso 1 & 2 2. create cd's from iso images 3. using partition manager software create a 10 gig partition on your system. if you do can't get your hands on a gui based partition manager package, be prepared to use cfdisk. In either case you'll need at least 10 gig of space for a full install + extras! Step 2: Install Slackware 12 1. boot your system of slackware 12.0 cd #1 (at the boot prompt hit enter) 2. signon as root 3. run cfdisk to the harddisk to be installed (usually "/dev/hda1") partition you have reserved for slackware. reserve 8 gig for /, 1 gig for linux swap, 1 gig for /home. if you can do it, it's often a good idea to create an extended partition and place multiple partitions inside there, but for the everyday user, one single 8 gig partition is good! 4. run setup and go thru each item (for a Detailed Install Summary, see below) Step 3: Configure Slackware 12 (see Configuring Slackware 12 below) Step 4: Update the Kernel (See Updating the Kernel! below) Step 5: Configure Wireless Internet (optional) (See Wireless support for Slackware 12.0 below) Step 6: Install Hardware Acceleration (optional) (See Installing 3D Hardware Acceleration! below) (See Installing ATI-Driver-Installer-8.40.4 next page) Step 7: Perform a Linux Update (See Linux update with Swaret! below) Step 8: Install Dropline Gnome (See Installing Dropline Gnome! below) Step 9: Slackware 12 Security Options (See Securing Slackware 12.0 below) Step 10: Install various extras! There are remaining posts here for various options: - Spaceage Customizations - How to compile your Slackware 12 2.6.21.5 (22.x) Kernel! - How to setup CPU Frequency Scaling for Slackware 12! - How to install your very own initrd.gz! - How to get sound working on your Slackware ! - How to use Bluetooth with Slackware 12 ! - Give your Windows Partition a Lobotomy! - Add a graphical partition manager to your Slackware 12 setup! - Seems to me you need to try your luck with Samba! - How to resolve your "This Python has API version 1013" problem - O.M.G I've Lost My Scroll Bars!!!!! - "Want to play a game?" - Wargames (the movie) - Play 3D Hardware Accelerated Games in Style! - Configuring Linux Partitions Detailed Install Summary Much of what is listed below is adopted from Slackware 10 instructions, much of it remains the same, some parts are different. Feel your way thru, Slackware is very robust and inituitive (relatively speaking)! Code:
Getting Slackware |
Configuring SLackware 12
Installing Slackware is one thing, configuring it is another. This section will actually be a gentle introduction to you to the internal workings of your new Linux system. Slackware is known for it's closeness to the ideals of Linus's Linux where the latest kernel is rarely modified. Changing a kernel to fit a distribution is like changing a room to fit a picture. With Slackware your basically given a virgin operating system that needs *your* input as to how you want it to run. You will have to do this section if you want to configure things like your graphics card, mouse wheel, graphical login, etc.
Code:
In the first half of this training manual, the Slackware recruit will |
Installing 3D Hardware Acceleration!
Chances are you got a system capable of high end 3D hardware acceleration and it will look beautiful under Linux! Earlier 3D drivers were a pain, unfortunately. But if you are using mainstream hardware (ati,nvidia) your in luck! You should be able to setup without much hassle!
For ATI people! For NV people! Taking your "best guess", download the latest driver for your card and go from there! ATI people are recommended to download an extra package xf86-video-ati-6.6.3-i486-3.tgz and install: Code:
wget http://gulus.usherbrooke.ca/pub/distro/slackware/slackware-current/extra/xf86-video-ati-6.6.3/xf86-video-ati-6.6.3-i486-3.tgz Here's an example of how I did it: Code:
wget https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.39.4-x86.x86_64.run --no-check-certificate Sometimes you'll want to restart your X-server with a <Ctrl><Alt><BackSpace> and sometimes, the system will seem to freeze on the terminal screen. If this happens, don't panic! Resist the temptation to reboot/reset your computer as this plays havoc on the file system. Instead switch to a terminal window by pressing <Alt-F1> thru to <Alt-F7> until a prompt shows up allowing you to enter as root in terminal mode. Once there, enter a init 3 and then a init 4 to restart the X-server! Also Note! ATI users have a RADEON driver which works 1/2 as good as the latest hardware proprietary driver! If for whatever reason you cannot get satisfaction with the proprietary drivers, the RADEON driver that ships with Slackware should work great. Especially if screen real estate is more important to you. With the RADEON driver (you go into your /etc/X11/xorg.conf and you find where it says "radeon" and you make sure the default driver is the identifier) you should get the maximum screen resolution by default (in my case it is 1400x1050) and decent FPS albeit thru your main board processor: Code:
perry@slackware:~$ glxgears Code:
Section "Screen" |
Linux update with Swaret!
Keeping your system updated with the latest in refinements is not as critical as with Windows. Package updates do not occur that often so there is no need to worry there. However, after a fresh install there is usually a number of packages that will have to be updated. One popular method of doing that is using a product called swaret! Once again, the information is adopted from Slackware 10 instructions. But the latest swaret package is only 1.6.3, not bad considering how long it's been around!
Before you install swaret however, make sure to do they following so that you can make things easier on yourself at a later date (you'll be glad you did): Code:
mkdir /usr/local/opt/swaret Code:
swaret is SlackWARE Tool for Slackware software management. As of |
Wireless support for Slackware 12.0
First things first!
You owe it to yourself to see if the support that comes already built into Slackware 12 is ready to go. The rc.inet1 script and accompanying rc.inet1.conf file are the primary means by which you can setup wireless on your system: Code:
IFNAME[4]="wlan0" Code:
IFNAME[4]="wlan0" Code:
IFNAME[4]="wlan0" Plan B If for whatever reason that approach doesn't work for you, here's a common fallback. It's called making use of the same Windows drivers that your using when your booted in that system. For this process to work, you *must* have the .inf file for your wireless modem, typically found on your install CD (that came with the modem). If you don't have the CD you may be able to find your .inf file off the Internet. Typically the .inf file is in a subdirectory on the CD or after you decompress your downloaded setup file you should be able to find it. Either way, you need that .inf file in order for this fallback plan to work. NDISWRAPPER: Using your Wireless Windows Driver with Linux Your system *probably* comes with eth0 or regular network support (as in a wire/cable that plugs in the back of your computer). For those of us who have to rely on wireless it's not that simple. However, this method maybe about as simple as it gets at the moment! Step #1: Download/Install NDISWRAPPER 1. Download the latest version of NDISWRAPPER! 2. Untar, make, make install! (Ignore the CONFIG_4KSTACK warning) Code:
wget http://umn.dl.sourceforge.net/sourceforge/ndiswrapper/ndiswrapper-1.47.tar.gz 1. Get the CD that came with your wireless modem and look for an .inf file Code:
Sometimes there is more than one .inf, typically the longer the .inf has been around the greater the chances it'll work. However the newer the .inf file, the greater are the chances that it'll work faster or better! I'll use that driver here as an example. 2. Install your Windows driver as follows: Code:
root@slackware:/home/perry# ndiswrapper -i rt2500usb.inf 3. Now modprobe the thing Code:
root@slackware:/home/perry# modprobe ndiswrapper Here's a script to copy into your /usr/local/sbin folder, do a chmod +x on it Code:
#!/bin/sh Provided your router doesn't require encryption you should be able to connect to the Internet at this point. Also, if at any time your Internet goes down you can reset your wireless driver simply by entering a 'stop' and then another 'start'. Test this out now to see if everything is working! (You'll have to be in root to do this) Step #5: Add it to your bootup/shutdown process You should also add a reference to this script to your bootup and shutdown procedures! your /etc/rc.d/rc.local file: Code:
#!/bin/sh Code:
#!/bin/sh Encryption with rc.wlan0 You'll have to do some experimenting here as I don't have my Linksys router setup for encryption and am not going to set my Linksys router up for encryption (at the moment)! That could change, but experience comes the knowledge that if it's currently working, thats a good thing! Nonetheless to enable it with this script you simply config your wireless using the iwconfig utility. I'd advise you startup your wireless for the very first time by executing manually each of the commands in the "start" portion of rc.wlan0 and then execute one of the options for encryption using iwconfig. Once you got something working, add those commands to your rc.wlan0 script: Code:
key/enc[ryption] NOTE: Life on the cutting edge! Before you can use ndiswrapper however, you may have to upgrade your kernel before hand. If you've done the above steps and still no wireless, upgrade your kernel (as described below) and try again! Optional support Using your desktop to inform you that you have wireless is pretty grovy! I use both my Dropline Gnome desktop to inform me that my wireless and Internet are working by adding applets that it provides. Also, if your a gkrellm fan you can activate your wireless plugin as well! Take a look at my desktop! |
Updating the Kernel!
By default Slackware uses the huge kernel. For some of us, our system won't even boot with that. For me, I was able to work around this using a kernel from Slackware 10.1. If your doing a fresh install, your CD #2 should be able to boot up and give you a chance to install the generic kernel. I didn't do it that way and that's the best I can recommend at this point. In either case to those of you that are able to switch to the generic-smp kernel, before you can use wireless you have to upgrade the kernel as follows:
1. Get the latest generic smp kernels here! Code:
wget http://gulus.usherbrooke.ca/pub/distro/slackware/slackware-current/slackware/a/kernel-generic-smp-2.6.21.5_smp-i686-2.tgz Code:
installpkg kernel-generic-smp-2.6.21.5_smp-i686-2.tgz Code:
wget http://gulus.usherbrooke.ca/pub/distro/slackware/slackware-current/extra/linux-2.6.21.5-nosmp-sdk/kernel-headers-2.6.21.5-i386-2.tgz Otherwise make sure you do the following: 1. Add this entry to your lilo.conf Code:
# Linux bootable partition config begins Code:
mkinitrd -c -k 2.6.21.5-smp -m reiserfs -f reiserfs I'll give more detailed instructions on switch to the generic kernel a little bit later for those stuck on that! Update: Check out How to compile your Slackware 12 2.6.21.5 (22.x) Kernel! below |
Great thread, very informative and easy to follow. A candidate for Sticky-land.
|
Installing Dropline Gnome!
You *WANT* to install Dropline Gnome! Patrick gave up on supporting Gnome after 10.1 however, the folks at Dropline are a separate entity, they love Slackware and they have their act together. If you want a nice looking desktop with really nice eye candy and (full control over your) beautiful fonts, you'll want Dropline Gnome on your system. Slackware without Dropline is like cake without icing. Moreover the latest verion of Dropline is rebuilt explicitly for Slackware 12.0
1. Download the Dropline installer! 2. Installpkg dropline-installer-2.18-i686-3dl.tgz 3. Execute dropline-installer! Code:
mkdir /usr/local/opt/dropline-installer And then go and get yourself a coffee as it has a lot of downloading to do, but don't worry it'll automatically install so that you won't have to wait. You might also want to save the contents of /var/cache/dropline-installer for future installations! Well that's essentially it! If you have other operating systems on your pc you might have to deal with ntfs if so check out fuse and ntfs-3g. Just download and install as per directions. There are a few more refinements that I'll describe a little later for now, this is the general gist of what you have to do to get Slackware 12.0 + Dropline onto your system. Hope your learning curve is not *too* steep but rewarding. I've been using Linux since the late 90's and nothing compares to what Slackware 12 is doing for me tonight. Hope you get to have the same experience! - Perry |
Securing Slackware 12.0
The following is documentation intended for Slackware 10.0, much of it can be adopted for 12.0. Some of it, like the arno iptables cannot! Take a look at it and make use of what you want.
Code:
Where Do You Go From Here? |
Spaceage Customizations
To save a little space, most modern cpu's these days have little trouble creating images/thumbnails for you and information left in your browser can actually cause it malfunction on occasion. What I find really helps is to keep certain hidden directories on my system, temporary. That way I won't be carrying around hordes of thumbnails and browser cache info that I'll never use again! To do this, simply add this to your /etc/fstab:
Code:
none /home/perry/.thumbnails tmpfs defaults 0 0 Also, don't forget your /tmp directory. You wouldn't believe how many times having a permanent /tmp area kicking around has caused so many 'mysterious' problems threw out the system. If you have any decent memory at all (say 1 gig+) you owe it to yourself to setup /tmp as a truly temporary space that gets reset with every reboot (or in this case, remount)! Add this to your fstab (comment out the one already there with a '#'), you won't be sorry you did. Code:
none /tmp tmpfs defaults 0 0 Code:
Filesystem 1K-blocks Used Available Use% Mounted on - Perry ;) |
How to compile your Slackware 12 2.6.21.5 (22.x) Kernel!
Anybody else compiling their kernel can go check out the vanilla recipes for kernel compiles but us Slackware 12 people have certain refinements that require special attention.
Check out this super excellent description on how to compile a Slackware 12, 2.6.21.5-SMP Kernel Then come on back and tell us how you made out! - Perry ps. If you do this, make sure you check out how to do your own initrd.gz below! |
How to setup CPU Frequency Scaling for Slackware 12!
Also, in addition to the changes to the kernel that the author of that how-to guide indicates that you should do. Be sure to activate your cpu frequency scaling ability thereby allowing linux to keep your processor from burning out (and keep your system much running much quieter)! (also, be aware that you can use make gconfig instead of make menuconfig for a more graphically pleasing way to make changes to the kernel):
Code:
<*> Power Manage options (ACPI, APM) And be sure to add this line to your /etc/rc.d/rc.local to make sure your computer boots up in ondemand mode! Code:
#!/bin/sh Thanks and have a great day, - Perry ps. what a relief, all this time now seeing the CPU temperature hovering around 45-55 degrees with a red bar next to it and always operating at 2 GHz and I'm thinking "whats the sense in telling me something the I already know". Then when I tinkered with it and found out that my frequency scaling ability wasn't activated, i said, "right, time to get that kernel compiled properly..." |
How to install your very own initrd.gz!
It's going to be important that you update your initrd.gz if your going to compiling your kernel. Especially if you are building up from your 2.6.21.5-generic-smp kernel. Otherwise it's not going to know how to load the thing. Here's a build (gedit /boot/build) script that you can include in your /boot directory:
Code:
echo re-creating initrd.gz Code:
# The -p is for the few people that know you can set passwords on lilo that Code:
# Linux bootable partition config begins Code:
cd /usr/src/linux I'm out! - Perry |
Give your Windows Partition a Lobotomy!
Given that your new Slackware 12 / Dropline Gnome is now going to handle 99.99% of all your computer needs, the only thing you'll be keeping your Windows partition around for is just a convenient fallback position for certain games that just won't run correctly with Wine or Cedega!
In this case, what you want to do is install Fuse & NTFS-3G to properly access your Windows partition. Then with those packages in place, you'll make a backup of your Windows partition, perferrably when it's in it's ideal state (as in before all the viruses and spyware clouded it up). You can use the ntfsclone utility to make an image for you then redeploy it when you want to save yourself hours (if not days) reinstalling all those Windows drivers and updates! To install NTFS read/write support on Slackware: Code:
wget http://lp.slackwaresupport.com/Slackware-12.0/martijn/fuse-2.6.5-i486-2McD.tgz Code:
/dev/hda1 /mnt/win2k ntfs-3g defaults,force 1 0 To copy your Windows partition: Code:
cd /mnt/{somewhere with enough space} Code:
cd /mnt/{where you stored your ntfs.img} Create your ntfs.img file just after you get everything setup *perfectly* (or as "perfect" as it gets with Windows) and then make your image on another hard disk or partition (one with enough space to house a complete copy of your NTFS partition). After you drop the partition and then create it again (using fdisk, cfdisk or gparted), simply run the 2nd ntfsclone command. Afterwords, your Windows partition will act a little tipsy (just like coming out of a lobotomy) but after a chkdsk or two and a couple reboots be back to it's old reckless self for another dip in the mud! Divide & Conquer! As a bonus, this technique can allow you to clone multiple computers than need the same setup. If your running a games arcade or something you can setup a Linux server to lobotomize your Windows machines every morning...! Nice way to start the day... your Windows slaves start off with a lobotomy, you start off with a Java...! Isn't it nice to be able to say that Linux can install Windows better than Windows can install itself...! Have a nice day! - Perry |
How to get sound working on your Slackware !
This is like common problem with sound #1
By default, your sound capability with Slackware is muted. Too many times people freak out because they can't seem to get their sound working. As root, you might want to set this up. In a terminal window: Code:
alsamixer To save your settings as default, be sure to use alsactl store. Better done as root, but should work as a user. - Perry |
All times are GMT -5. The time now is 02:31 PM. |