LOG FOR SETUP FROM CLEAN INSTALL OF SLACKWARE-10.2
I did not install the Emacs, Tex, and 2.4.31 kernel headers packages as I don't foresee using them ATM. I did not install lilo at post install configuration and can log back into this install using the first install cd. At the boot prompt I enter [root=/dev/hda9 nointrd ro] to boot into the new install where /boot can be found on /dev/hda9.
After the post install setup routine, most everything else is going to be manual configuration. That's slackware, no wizards just you in the drivers seat, in control. The price you pay for speed, stability, and security.
I usually use [mc] for my CLI file manager and [mcedit] for my CLI editor when not in KDE.
Since I've been moving my /home/rick along with me since slack 9.0 or so I've decided to start off with a new /home rick directory. I'm sure there are some changes to configuration/running of kde and kde aps now and maybe I should just start anew instead of relying on backward compatibility and assuming everything is working fine.
CLI commands are noted between brackets, e.g. [mcedit /etc/fstab]. I won't explain usage in the text below. You can use man to find out what the command and flags do/mean, e.g [man ls].
#################################################
CONTENTS:
1. SETUP TO BOOT INTO KDE:
2. INSTALL THE 2.6.13 KERNEL
3. SETTING LILO UP TO BOOT
4. INSTALL PROPRIETORY NVIDIA DRIVER
5. CONFIGURING THE X SERVER
7. CREATE A USER AND REBOOT
8. WHERE ARE WE NOW?
9. SETTING UP HPLIP AND CUPS PRINTING
10. SETTING UP CUPS SERVER FOR LAN
11. CONFIGURING FOR DVB CARD
12. SETTING UP KAFFEINE FOR DIGITAL TV
13. INSTALLING A CUSTOM KDE SPLASH
14. EDIT /etc/fstab SO THAT USERS CAN MOUNT CD AND FLOPPY DRIVES
15. SETTING UP MONEYDANCE, A JAVA PROGRAM
16. SETTING UP KMAIL AND THE ADDRESSBOOK
17. SETTING UP POPFILE, A PYTHON BASED SPAM FILTER
18. SETTING UP DIGIKAM WITH ACCESS MY DIGITAL CAMERA VIA USB
19. EVERYTHING'S OK SO NO MORE TESTING
20. A NOTE ABOUT OPEN GL, MESA AND COMPILING/PLAYING GAMES
21. COMPILING AND INSTALLING FROZEN BUBBLE
22. COMPILING AND INSTALLING SUPERTUX
23. COMPILING AND INSTALLING TUXRACER
24. SETTING UP TO SCAN WITH XSANE AND KOOKA
25. FIXING KDE FILEPICKER ERROR IN KDE
26. PLAYING .wmv AND OTHER SUCH FILES USING WINCODECS
27. INSTALLING FLASHPLAYER PLUGIN (FIREFOX AND KONQUEROR)
28. SETTING UP ADOBE ACROBAT READER V-7.0 AND MAKING IT FIREFOX DEFAULT READER
29. INSTALLING REALPLAYER-10 AND REALPLAYER PLUGIN
30. GETTING LAZY ( a script that does some plugin installation)
31. INSTALLING lm_sensors and ksensors
#################################################
#################################################
1. SETUP TO BOOT INTO KDE:
Edit /etc/inittab and change runlevel from 3 to 4.
Next would be to comment out the GDM lines in /etc/rc.d/rc.4 but this is no longer needed since there is no Gnome in this release.
I could also just use the command [startx] and go into kde right now if I wanted but I want to instll my Nvidia driver (to use instead of Xorg's generic "nv" driver)so I will need to compile the driver which requires my kernel headers so I'll need to install the 2.6.13 kernel first.
#################################################
2. INSTALL THE 2.6.13 KERNEL
On install I installed the stock 2.4.31 bare.i kernel but I intend to run the 2.6.13 kernel from /linux-2.6.13 which is on the second install cd. There are some advantages for me with this kernel with hardware recognition and the dvb drivers for my dvb-t card are now included.
I'll leave the 2.4.31 kernel in /boot for now but get rid of the alsa driver package that goes with it with it using [removepkg alsadriver].
Next I'll mount the 2nd install cd and cd into the /linux-2.6.13 directory.
I'll use installpkg ./*.tgz to install everything.
Following the instructions in README.initrd in /mnt/cdrom/linux-2.6.13 I'll create an initrd for booting the new kernel since I'm using reiserfs.
After cd /boot I run the command [mkinitrd -c -k 2.6.13 -m reiserfs].
That'll be all except for editing /etc/lilo in order to boot the 2.6.13 kernel.
#################################################
3. SETTING LILO UP TO BOOT
I did not setup the lilo bootloader during post install configuration because I did not want to remove my existing lilo settings for my workstation (slack A) which is on /dev/hda2 through /dev/hda8. I will now have to reboot into slack A in order to edit the /etc/lilo.conf and run lilo there. I could also set lilo up in this install of slack-10.2 (slack B) but I'm just testing right now so I'll leave things as they are.
Setting up to boot slack B is a matter of editing /etc/lilo.conf and adding a stanza each for my two kernels and the running [/sbin/lilo] or just plain old [lilo] as root. Here's what my lilo.conf looks like
### start lilo.conf ###
### global settings ###
boot=/dev/hda
default=slack-2.6.11.9
prompt
nowarn
timeout=300
### this is my workststion ###
image = /boot/vmlinuz-generic-2.6.11.9
root = /dev/hda2
label = slack-2.6.11.9
# if you install a slack 2.6.x kernel you need this line
initrd = /boot/initrd.gz
vga = 791
read-only
### this is slack-10.2 with 2.4.31 kerel ###
image = /mnt/hda9/boot/vmlinuz-ide-2.4.31
root = /dev/hda9
label = test-2.4.31
# don't use the next line unless you want to access cdrom using this kernel
# and if you do you will need to set up /dev/cdrom to point tp /dev/scd0
#append = "hdc=ide-scsi"
vga = 791
read-only
### this is slack-10.2 with the 2.6.13 kernel ###
image = /mnt/hda9/boot/vmlinuz-generic-2.6.13
# if you install a slack 2.6.x kernel you need this line
initrd = /mnt/hda9/boot/initrd.gz
root = /dev/hda9
label = test-2.6.13
vga = 791
read-only
other = /dev/fd0
label=floppy
unsafe
### end of lilo.conf
If all is well I can now shutdown slack A and boot into slack B using lilo.
Note that since I still have to install my Nvidia driver which cannot be done while running an X session I will have to boot into slack B at the CLI which can be done by appending "linux single" at the lilo prompt, That is, instead of selecting test-2.6.13 and hitting "Enter", I will enter [test-2.6.13 linux single] which will boot me up into runlevel 1.
#################################################
4. INSTALL PROPRIETORY NVIDIA DRIVER
Prior to installing I had downloaded the most recent Nvidia driver, NVIDIA-Linux-x86-1.0-7676-pkg1.run. This is a script that will compile and install the Nvidia module which certainly makes a difference for me and my daughter can't run Tuxracer without it.
I will now copy this over to some place convenient, cd into that directory and make the script executable with [chmod +x NVIDIA-Linux-x86-1.0-7676-pkg1.run].
If I remember corrctly I was able to compile and install the previous version nvidia script and run it in runlevel 1 but this time around I was given a warning that I should use runlevel 3 so I will have to change runlevels with [telinit 3] before I run the script with [./NVIDIA-Linux-x86-1.0-7676-pkg1.run].
If all goes well there is one more thing I'll be doing before rebooting into an X session to see if all this works. I'll need to reconfigure my /etc/X11/xorg.conf.
#################################################
5. CONFIGURING THE X SERVER
I know that the default /etc/X11/xorg.conf file I get at installation will work with my hardware so I'll save that just in case with [cp /etc/X11/xorg.conf /etc/X11/xorg.conf-orig
Next I will run the command [xorgconfig] which will take me through a step by step CLI configuration of my xorg.conf settings. Its handy before starting to know what your monitors horizontal syvnc and vertical refresh rates are. If you don't know use safe settings until you find out.
I will be setting up (first) with the generic nvidia driver but you will have to know what kind of chip your graphics card or motherboard uses before you run this configuration script.
Once I've run the script I will make some further changes. I need to change over to load the nvidia driver I compiled/installed. Thats simply done by editing the relevenat section in the xorg.conf file
# Device configured by xorgconfig:
Section "Device"
Identifier "NVIDIA GeForce"
# I add this line
Driver "nvidia"
# The following line was generated by running xorgconfig. I'll comment it out
#Driver "nv"
#VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
I will also make some other changes that I know I'll need for running my Dvico Fusion DVB-T Plus card.
Section "Module"
Load "dbe"
Load "v4l" # My addition
Load "extmod" # My addition
Load "glx"
#Option"omit xfree86-dga" # don't initialise the DGA extension
# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
EndSection
#################################################
7. CREATE A USER AND REBOOT
OK. I'm ready to boot into an xsession but there'll be more things to do as root and I don't want to log into kde as root if I don't have to. I'll create a user "rick first using the command [adduser].
Then I'll use [shutdown -r now] to reboot the computer. The command [shutdown -h now] will shut the PC down.
#################################################
8. WHERE ARE WE NOW?
Ok now I've rebooted and logged in as rick with a KDE desktop before me. I want to work as root and continue setting things up. When I'm satisfied this will be my workstation system or at least the config files will be retained and/or copied over.
First to see how much space this install required i use the the "df" command.
sh-3.00# df -hm /dev/hda9
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/hda9 2997 680 2317 23% /
sh-3.00# df -hm /dev/hda10
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/hda10 3993 1739 2255 44% /usr
This shows that the complete install was roughly 2,419 Mb and this leaves me plenty of room to build on When I change over to workstation mode I'll have a seperate partition for /home and /usr/local but for now this is it.
I'll be either building new slackpacks are seeing if ones that were created in slack-10.1 will work. All installed slackpacks will be put in /usr/local/src which is where I store things like that. I only keep kernel related stuff in /usr/src
#################################################
9. SETTING UP HPLIP AND CUPS PRINTING
I have an HP 930C Deskjet and HP PSC-2355 printer/copier/scanner and if I set up HP's new Printing/Scanning application named HPLIP I will be able to print, scan and interface with digital camera cards through an all in on interface that also includes calibration, head cleaning and other functionalities. Real neat!and it was made to work with CUPS. I'll use the PSC also for colour printing and use the 930C for BW jobs since the cost per BW page is cheaper in the long run.
Hplip includes the hpijs package (hp printer drivers) and hpoj for hp scanners. Hpijs was just installed and I'll now remove it with [removepkd hpijs]
I will now install hplip and the all its dependencies that are not already aboard.
sh-3.00# installpkg hplip-0.9.4-i486-1kjz.tgz
sh-3.00# installpkg net-snmp-5.2.1-i486-1gsp.tgz
sh-3.00# installpkg PyQt-3.14-i486-1asz.tgz
sh-3.00# installpkg sip-4.2-i486-1asz.tgz
This hplip package was made specifically for a slack install and there will now be an hplip rc file named /etc/rc.d/rc.hplip. This file has to be run before rc.cups so I have to add the following to rc.M and it has to precede the call that starts CUPS.
# Start hplip. This has to run before CUPS starts.
if [ -x /etc/rc.d/rc.hplip ]; then
/etc/rc.d/rc.hplip restart
fi
If I had installed hplip from my own package or source there would not have been an /etc/rc.d/rc.hplip created nd I would have had to [ln -s /usr/share/hplip/hplip.sh /etc/rc.d/rc.hplip] in order for it all to work.
Hplip will only recognise printers that are installed on CUPS after hplip has been installed and is running in the background so now is the time to stop CUPS with [/etc/rc.d/rc.cups stop] then start hplip with [/etc/rc.d/rc.hplip start].
If hplip starts successfully, open a browser and go to http://localhost:631 and install your printer(s).
Everything worked out fine for me. When I run /usr/share/hplip/toolbox, I get the HP DEvice Manager and I have access to both printers and all their functions including scanning on the psc-2355 using sane and xsane.
For info and troubleshooting go to http://hpinkjet.sourceforge.net/hplip_readme.html
#################################################
10. SETTING UP CUPS SERVER FOR LAN
Now that hplip and CUPS are working I have to remember that Leila uses my box as her printserver so I have to copy over my known good /etc/cups/cupsd.conf but first I'll save the original with [cp /etc/cups/cupsd.conf /etc/cups/cupsd.conf-orig] and then copy in the one that I'm now using which I'll past in below just in case....
######################################################
# /etc/cups/cupsd.conf
# edited by Rick Miles 2/11/03
# This cupsd.conf works. In most cases I have deleted
# explanations and redundant commented parameters.
# They are either not used or the CUPS default is
# being used. Hence no need to uncommenet or edit.
# Note there is only one client on the net, e.i.
# 192.168.1.3
#####################################################
########
# Server Identity
########
ServerName 192.168.1.2
ServerAdmin root@192.168.1.2
########
# Server Options
########
LogLevel debug
########
# Fax Support
########
########
# Encryption Support
########
########
# Filter Options
########
########
# Network Options
########
Port 631
########
# Browsing Options
########
Browsing On
BrowseProtocols cups
BrowseAddress 192.168.1.255
BrowseShortNames Yes
########
# Security Options
########
AuthType: None
Order Deny,Allow
Deny From All
Allow From 127.0.0.1
Allow From 192.168.1.3
Allow From 192.168.1.2
#
#
#
#
#
#
# I'll put this in to see if stops client error messages
AuthClass System
AuthType Basic
Allow from 127.0.0.1
Allow from 192.168.1.3
#
#
#
#
AuthType Basic
AuthClass System
## Restrict access to local domain
Order Deny,Allow
Deny From All
Allow From 127.0.0.1
Allow From 192.168.1.2
Allow From 192.168.1.3
#Encryption Required
# End of cupsd.conf
#################################################
11. CONFIGURING FOR DVB CARD
I've run lspci and lsmod as root to check and see that my dvb card is recognised and that the correct modules hae been loaded. Everything looks OK but I need to make some changes in /etc/udev if I want the correct devices set up in /dev/dvb/adaptor0. I don't understand all of the whys about what I'm going to do but it is necessary and it worked in my current workstation. Udev is fairly new and maybe it will get simpler with time.
This script has to be copied into /etc/udev/scripts:
#!/bin/sh
/bin/echo $1 | /bin/sed -e 's,dvb\([0-9]\)\.\([^0-9]*\)\([0-9]\),dvb/adapter\1/\2\3,'
#end of script
Previously I would also have to add this to /etc/udev/rules.d/udev.rules:
# dvb devices
KERNEL="dvb*", PROGRAM="/etc/udev/scripts/dvb.sh %k", NAME="%c"
but when I take a look I find that in slack-10.2 this line is already in udev.rules:
# dvb devices
KERNEL="dvb*", PROGRAM="/etc/udev/scripts/dvb.sh %k", NAME="%c", GROUP="video", MODE="0660"
This seems to be doing the same thing plus setting some permissions.
In slack-10.1 /etc/udev there was a subdirectory /etc/udev/permissions.d which is not here in 10.2 so I'm thinking that there has been some changes since when I had to add
# DVB devices
dvb/*:$root:video:0660
dvb:$root:video:0660
dvb/adapter*:$root:video:0660
to /etc/udev/permissions.d/udev.permissions and I think I'll leave everything as it is now with the exception of copying in the missing dvb.sh and I'll see if I get the correct devices created at the next boot.
On reboot I now have a /dev/dvb/adapter0. There are four devices in adapter0 which is what I should have and the permissions are as per the dvb line in udev rules:
rick@rick:~$ ls -l /dev/dvb/adapter0/
total 0
crw-rw---- 1 root video 212, 4 2005-09-17 20:33 demux0
crw-rw---- 1 root video 212, 5 2005-09-17 20:33 dvr0
crw-rw---- 1 root video 212, 3 2005-09-17 20:33 frontend0
crw-rw---- 1 root video 212, 7 2005-09-17 20:33 net0
so its quite clear that I'll have to make rick a member of the group video if I'm going to access my dvb related devices. I'll be lazy and do it in kuser but since I need to make the chnges as root I'll do the following:
[Alt F2] will open up a little window in KDE which will allow me to type in the command [[kdesu kuser]. After I hit Enter I will be prompted for the root password and after entering that kuser will open up allowing me to make changes as root.
The alternative to this would be to change the permissions do everyone can access the devices by chnaginging the settings in /etc/udev/rules.d as follows:
# dvb devices
KERNEL="dvb*", PROGRAM="/etc/udev/scripts/dvb.sh %k", NAME="%c", GROUP="video", MODE="0666"
where MODE has been changed from 066 to 666.
#################################################
12. SETTING UP KAFFEINE FOR DIGITAL TV
Now that I know everything is in order for accessing/using my dvb card I'll setup Kaffeine for viewing digital TV programs. Kaffeine is also a good dvd viewer and has plugins for viwing other video type files as well.
The most recent is kaffeine-0.7.1 and I'll download the source and compile with ./configure, make and checkinstall which will create a slackpack. In slack-10.1 I could not get checkinstall to work right even though I followed Pat's instructions but checkinstall works fine this time around.
Kaffeine will also require libdvdcss for encrypted dvds, and win32codecs in
#################################################
13. INSTALLING A CUSTOM KDE SPLASH
I have a real neat custom splash by AYO73 that I want to use. I've downloaded it from his website. It is several different graphics files which together comprise a splash for when a user logs into KDE. The are of one of AYO73's Miss Pingus and I have to first creat a subdirectory /opt/kde/share/apps/ksplash/Themes/Miss_Pingus.
This alone won't work without also having a file named "Theme.rc". The splash files didn't come with one so I just took one out of one of the stock KDE Splashes and modified it to suit.
#
# Miss_Pingus Theme
#
[KSplash Theme: Miss_Pingus]
Name = Miss Pingus KDE Splash theme
Description = Load Miss_Pingus KDE Splash theme
Version = 1.0
#Author = AYO73
#Homepage =
# Theme behaviour settings.
Engine = Default
# Should icons blink ala KDE, or not?
Icons Flashing = true
Now the theme will show up in Control Center and can be set as the default
#################################################
14. EDIT /etc/fstab SO THAT USERS CAN MOUNT CD AND FLOPPY DRIVES
Slack installs these drives so that only root can mount these devices. This is set in /etc/fstab where the relevant lines read:
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
This means that root being the owner can mount them but nobody else.
This can be fixed by changing these lines to:
/dev/cdrom /mnt/cdrom auto noauto,users 0 0
/dev/fd0 /mnt/floppy auto noauto,users 0 0
There is more than one way to do this though and my cdrom line above was not good enough for Crossover Office it seems. When Croosover was installed it could not work with my line for /mnt/cdrom and wanted to change it to this:
/dev/cdrom /mnt/cdrom auto user,unhide,noauto,users,ro 0 0
#################################################
15. SETTING UP MONEYDANCE, A JAVA PROGRAM
Moneydance is a personal finance manager written in Java. As such it needs the Java Runtime Library which comes in /extra on the 3rd disk. Since I didn't download the 3rd cd ISO yet and I want to conserve bandwidth, I'll install from my slack-10.1 3rd cd /extra directory. 10.2 shipped with jdk-1.5.0_01 and 10.2 ships with jdk-1.5.0_04 so there really isn't that much difference.
Moneydance is a self contained application which I have installed in one directory /usr/local/moneydance. Since I've been using Moneydance for a year and have allowed automatic updates of the program and installed some extensions I'll just copy the entire moneydance directory over into the /usr/local on my new 10-2 install.
I notice that I had somewhere along the line I must have installed jre-1.3.0 in my Moneydance directory. This is a bit of a waste of space as I now have just installed jdk-1.5.0_01 from /extra in /usr/lib.
Moneydance will be looking for a /moneydance/jre/bin so I'll create a symlink with [ln -s /usr/lib/jdk1.5.0_01 /usr/local/jre]. Now I can open Moneydance with the comman [/usr/local/moneydance/moneydance] and I'll create an icon on my desktop to do the job for me.
#################################################
16. SETTING UP KMAIL AND THE ADDRESSBOOK
This is not to difficult, First I'll copy over my /home/rick/Mail directory then I will need to copy over .kde/share/apps/kmail and .kde/share/config/kmail/rc and in both cases I will have to overwrite the existing files which are empty anyway since I haven't run kmail yet in this new install.
I will also have to copy over the addressbook (database) directory which is ~/.kde/share/apps/kabc. It is not necessary to copy over ~/.kde/share/config/kaddressbookrc unless there are custom configurations or some special setup you want to carry over.
#################################################
17. SETTING UP POPFILE, A PYTHON BASED SPAM FILTER
I can't run kmail until I set popfile up since kmail gets it's emails via Popfile which uses a Baysean filter. I've been running Popfile for a couple years, am quite pleased with it, and don't want to use my database full of "good" and "bad" words plus oher things so I'll copy over the entire directory.
Popfile, being a Python application is pretty much like Moneydance in that it is self contained. I keep it as /home/user/popfile. It has to be running to download emails so I have made up a script called "popstart" which I symlink in ./kde/Autostart so that it starts popfile whenever I log into kde. Here's the script:
#!/bin/bash
##################################################
# popstart 15/01/03 rickfrm
# This is a script used to start the popfile server as a
# normal user. I keep it in ~/popfile and put a symlink to
# it in ~/.kde/Autostart with the command:
# "ln -s ~/popfile/popstart ~/.kde/Autostart/popstart"
# you will have to give it a permission set appropriate for
# your user in your distro.
##################################################
cd /home/rick/popfile
perl ./popfile.pl >> /dev/null 2>&1 &
# End of script
#################################################
18. SETTING UP DIGIKAM WITH ACCESS MY DIGITAL CAMERA VIA USB
Actually I don't need to access my camera via digikam because I can just pop my card into my hp-psc-2355 and either print direct or upload one or all pictures to my hard drive. However Leila will need to use a usb connection to access the camera and she likes digikam so I'll set it up on my box and sort it all out in preparation for doing it on her PC.
First I will need to download digikam and everything else required off www.linuxpackages.net. I'll put them all in their own directory, /usr/local/src/digikam, which is how I usually store things like this. Here's the complete list of packages:
root@rick:/usr/local/src/digikam# ls
digikam-0.8.0_beta1-i486-1mht.tgz
digikamimageplugins-0.8.0_beta1-i486-1mht.tgz
gphoto2-2.1.6-i486-1mht.tgz
imlib2-1.2.1-i486-1arf.tgz
libgphoto2-2.1.6-i486-1mht.tgz
libkexif-0.2.1-i486-1mht.tgz
libkipi-0.1.1-i486-1mht.tgz
sqlite3-3.2.5-i486-1mht.tgz
I can install them all with [installpkg ./*tgz]
Digikam will install with a menu item in KDE's "Graphics" sub-menue and everything seems to be OK including my Canon Powershot A400 being recognised. However, I will not be able to access the camera with a usb cable until I set up hotplug and I create a group named "camera" and make whomever will be accessing the camera members.
The easiest thing to do is to follow the instructions on http://gphoto.sourceforge.net/doc/manual/permissions-usb.html which will explain how to set up hotplug to to recognise my camera. I couldn't quickly locate the usbcam script for my camera (as mentioned on the manual page) without digging, so I ssh'd into Leila's PC and copied her's over to my box. Here's what it looks like:
#!/bin/bash
# $Id: usbcam.group,v 1.3 2003/09/16 16:42:44 hun Exp $
#
# /etc/hotplug/usb/usbcam
#
# Sets up newly plugged in USB camera so that only members of the
# group
GROUP=camera
# can access it from user space. (Replace camera with the name of the
# group you want to have access to the cameras.)
#
# Note that for this script to work, you'll need all of the following:
# a) a line in the file /etc/hotplug/usermap that corresponds to the
# camera you are using. You can get the correct lines for all cameras
# supported by libgphoto2 by running "print-usb-usermap".
# b) a group "camera" where all users allowed access to the
# camera are listed
# c) a Linux kernel supporting hotplug and usbdevfs
# d) the hotplug package (http://linux-hotplug.sourceforge.net/)
#
# In the usermap file, the first field "usb module" should be named
# "usbcam" like this script.
#
if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
chmod o-rwx "${DEVICE}"
chgrp "${GROUP}" "${DEVICE}"
chmod g+rw "${DEVICE}"
fi
###################################################################################
###################################################################################
19. EVERYTHING'S OK SO NO MORE TESTING
I've played around enough and am satisfied that all is in good order. I'll stick with the 2.6.13 kernel and move on to putting together my workstation system which since I'm planning on switching around hardrives will mean partitioning and a new install after backing up everything I want to save. Next I'll start downloading and/or building packages since I think it will be time to dump some of the older slackpacks for things such as Leila's games.
I won't repeat anything I've discussed in sections 1 through 18 things might change slightly this time around but not enough to rewrite anything.
I'll need to have checkinstall on board from disk 3 /extra since I'll be making slackpacks the easy way.
#################################################
20. A NOTE ABOUT OPEN GL, MESA AND COMPILING/PLAYING GAMES
Some of the programs I want to install (most notably games) will have special graphics requirements to compile and play. To quote from the Supertux INSTALL file:
"Mesa should be installed in order to compile, but it is painly
slow when running, so we advise you to install your videocard
drivers (of course, it has to be an accelerated videocard).
For linux, nvidia vendor is the only one that makes decent drivers.
But the ATI drivers should run with the same performance, since
it only uses accelerated 2d, not 3d."
I'm not going to get into a long explanation. I have installed my Nvidia drivers so I'm OK with just about any graphics requirement but you will have to be sure you are.
#################################################
21. COMPILING AND INSTALLING FROZEN BUBBLE
I will first have to check and seee what Frozen Bubble needs to run. From the Frozen Bubble site I get a list:
Perl
SDL
SDL_image
SDL_mixer
SDL-perl (2.x not compatable, need to use version 1.19.2)
Perl and SDL are stock on slack 10.2 but I'll have to download everything else and the easiest thing to do is follow the links provided on the Frozen Bubble site. But first I'll check and see if any of the required packages have been put up for download at linuxpackages.net.
I'll say this one here and not again. If you are compiling your own stuff its best to first read the READMR and INSTALL files when you open up the tarball. For example the INSTALL for Frozen Bubble includes the following excerpt:
"If you compile by hand, double-check you first compile SDL, then SDL_image
and SDL_mixer, then SDL perl, otherwise you might get the error that
NewFont.al is not found."
It also indicates that the compile procedure does not include using ./configure.
As it turns out SDL_mixer has been put up as a slackpack so I'll only need to compile SDL_images and perl-SDL. I use the commands [./configure && make && checkinstall] and everything compiles and installs without a problem. I'll now install SDL_image from the slackpack I downloaded and I'm ready to compile Frozen Bubble.
I ran the command make andt Frozen Bubble compiled without a failure so I created and installed a slackpack using checkinstall. While running checkinstall I was presented with the following message:
Some of the files created by the installation are inside the build
directory: /home/rick/src/frozen-bubble-1.0.0
You probably don't want them to be included in the package,
especially if they are inside your home directory.
Do you want me to list them? [n]: y
Should I exclude them from the package? (Saying yes is a good idea) [y]
As you can see I excluded the files from the package and one of these files was the required it seems because when I ran frozen-bubble I had an error and it wouldn't start up.
rick@rick:~$ frozen-bubble
Can't locate fb_c_stuff.pm in @INC (@INC contains: /usr/lib/perl5/5.8.7/i486-linux /usr/lib/perl5/5.8.7 /usr/lib/perl5/site_perl/5.8.7/i486-linux /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl .) at /usr/lib/perl5/site_perl/5.8.7/i486-linux/fb_stuff.pm line 27.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.7/i486-linux/fb_stuff.pm line 27.
Compilation failed in require at /usr/local/bin/frozen-bubble line 59.
BEGIN failed--compilation aborted at /usr/local/bin/frozen-bubble line 59.
I recompiled Frozen Bubble after unpacking the tarball again and this time when I ran checkinstall I did not exclude the files in question.
Frozen-bubble is now working. Just in case you are wondering where they came from, frozen-bubble will create several hidden files in a users root directory which begin with ".fb".
#################################################
22. COMPILING AND INSTALLING SUPERTUX
Actually there was nothing unusual here. No additional dependencies above those for Frozen Bubble. Compiled and installed without a problem.
#################################################
23. COMPILING AND INSTALLING TUXRACER
I will first have to install smpeg. I will also need an additional package, tuxracer-data. Make sure version numbers match, e.g. tuxracer-0.61, tuxracer-data-0.61.
My first try at compiling with make exits with an error to do with not finding something to do with tcl.
A google search eventually leads me to the LFS site which is probably the best place to find compiling solutions because the whole LFS distro is compiled one package at a time.
To quote from http://www.linuxfromscratch.org/hints/downloads/files/PREVIOUS_FORMAT/tuxracer.txt
Unpack both archives tuxracer and tuxracer_data and run this:
cd tuxracer-0.61 &&
./configure &&
make && make install &&
cd .. &&
mv tuxracer-data-0.61 /usr/local/share/tuxracer
If this fails with "Can't find Tcl", and it probably will.
Run
ln -s /usr/lib/libtcl.8.4.so /usr/lib/libtcl.so && ldconfig
Then rerun the above.
After you first run the games as any user, you will have to edit
the ~/.tuxracer/options file and edit your prefernces, like bumping up
the resolutions etc. There are hundreds of options. Have fun.
Happy racing penguins, enjoy.
PS for outright speed, run tuxracer with.....
xinit /usr/local/bin/tuxracer
No WM no DE no messing around, just tux. :)
(works with UT and quake too)
For support or complaints, email, lfshints@cmm.uklinux.net
Cya.
Note that this will not give you a true tuxracer slackpack because if it was packaged properly the tuxracer-data files would be included in the slackpack and not have to be installed seperately/manually.
checking for tcl8.3 library... no
checking for tcl83 library... no
checking for tcl8.2 library... no
checking for tcl82 library... no
checking for tcl8.0 library... no
checking for tcl80 library... no
checking for tcl library... yes
checking for tcl.h... yes
checking for sdl-config... /usr/bin/sdl-config
checking for SDL - version >= 1.0.1... yes
checking for SDL_JoystickOpen... yes
checking for Mix_OpenAudio in -lSDL_mixer... yes
checking for GL library... yes
checking for glXGetProcAddressARB... yes
checking for GLU library... yes
checking for GL/gl.h... yes
checking for GL/glx.h... yes
checking whether glx.h defines glXGetProcAddressARB... yes
checking for GL/glext.h... yes
checking whether glext.h is recent enough... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
creating src/Makefile
creating config.h
root@rick:/home/rick/src/sandbox/tuxracer-0.61# whereis tcl8.3
tcl8: /usr/lib/tcl8.4
root@rick:/home/rick/src/sandbox/tuxracer-0.61# ln -s /usr/lib/tcl8.4 /usr/lib/tcl8.3
root@rick:/home/rick/src/sandbox/tuxracer-0.61#
# Change to script by RM beginning line 2798
if test "x$with_tcl_lib_name" = "x" ; then
#TCL_LIB_NAME="tcl8.3"
TCL_LIB_NAME="tcl8.4"
else
TCL_LIB_NAME="$with_tcl_lib_name"
fi
OK I seem to have lost the plot here and there are some errors when I run make indicating that I would need to spend more time than I would like on compiling this so I'll see if the Tuxracer-0.61 slaclpack I've been using will work.
It does so I'll leave this alone for now and install the slackpack I've been using since 10.0. It will work and there is not a more recent version.
#################################################
24. SETTING UP TO SCAN WITH XSANE AND KOOKA
I'll first have to see if my scanner is can be found with the command [sane-find-scanner] which will print out some messages but eventually results in the following line:
found USB scanner (vendor=0x03f0 [HP], product=0x4911 [PSC 2350 series]) at libusb:002:004
While I can scan with HPLIP via the toolbox, I can not use XSane or Kooka because the scanner is still not recognised by these programs. I'd like to make the scanner available on other networked boxes so I'll have to get this problem sorted out.
When hplip was setup a file /etc/sane.d/dll.conf.hplip was created. This sets up the correct backend for hplip (but not for any other application) by declaring the backend for hplip to be hpaio in a single line.
The file /etc/sane.d/dll.conf lists backends for a range of scanners and at the end has an option for using hpoj
# HP OfficeJet backend homepage: http://hpoj.sf.net/
# Uncomment the following line if hpoj is installed:
#hpoj
Since hplip is installed and it provides its own backend hpaio (not hpoj) I will have to make an the following entry in dll.conf
hpaio
Anywhere would do but I'll enter it under the #hpoj line.
#################################################
25. FIXING KDE FILEPICKER ERROR IN KDE
After installing OpenOffice I get an error message when trying to open documents that tells me "The Program Openoffice (kdefilepicker) crash and send signal 11"
This is discussed here:http://bugs.kde.org/show_bug.cgi?id=100849
and it can be fixed by adding The following to ~/.kde/share/config/kdeglobals
[Development]
AutoCheckAccelerators=false
#################################################
26. PLAYING .wmv AND OTHER SUCH FILES USING WINCODECS
I receive emails from old freinds in the US who send .wmv clips and other such MS oriented files. Kaffeine and Noatun can't play them and Kaffeine gives me an error message saying that wmvdmod.dll cannot be found. This is a windows codec and it can be found in wincodec which is available from the mplayer.hu site. It seems to be down right now but I can get a slackpack already made up called MPlayer_codecs-20050412-i686-2jto.tgz from linuxpackages.net.
This will install by default into a directory /usr/lib/codecs but I need to have it in a directory named /usr/lib/win32. This can be fixed with the following command as root:
ln -s /usr/lib/codecs/ /usr/lib/win32
#################################################
27. INSTALLING FLASHPLAYER PLUGIN (FIREFOX AND KONQUEROR)
This was not difficult. Downloadthe generic linux tarball from Macromedia site. The current version is: install_flash_player_7_linux.tar.gz.
Untar with [tar -xvzf install_flash_player_7_linux.tar.gz]
cd into the newly created install_flash_player_7_linux. directory and run the flashplayer-installer script. If you run it as root you will install the plugins globally. The script will ask you where to install the plugins files. Put them in /usr/lib/firefox.
You can install the flashplayer plugin in konqueror now by Going to Settings > Configure Konqueror > Plugins (pull down on left side)
Once you have Plugins open put /usr/lib/firefox in the list of scan folders and hit the Scan for New Plugins button
#################################################
28. SETTING UP ADOBE ACROBAT READER V-7.0 AND MAKING IT FIREFOX DEFAULT READER
The newest version of Acrobat Reader for linux (acroread) is really worth using albeit there is supposed to be spyware functionality onboard so that it would be possible for pdf publishers to gather information on readers. I don't know much about this other than it is possible to dissable this functionality which is java based. You can find out more about this on google but for now...
Download the new Acrobate Reader, untar the package and install with the enclosed installation script. It will be installed in /usr/local unless you say otherwise when prompted.
cd to /usr/local/Adobe/Acrobat7.0/Browser and run the install_browser_plugin script.
After runner the install_browser_plugin script I set the browser to work offline and set the path to a directory where I knew I had some .pdf's saved so I could check and see if firefox would automatically open acroread. It din't but I was prompted to tell firefox what to do and I told it to use acroread in the future. It works everytime now without prompting.
There seemed to be a problem with /usr/local/Adobe/Acrobat7.0/Reader/intellinux/plug_ins/PPKLite.api not working. I can't remember what the exact error message was and if I clicked OK acroread would open the file and work just fine anyway. If I make PPKLite.api not executable the error message stops and acroread still runs OK.
In order to run with PPKLite.api OpenLDAP must be installed.
There is a discussion on the javabased "spyware at http://lwn.net/Articles/129729/ along with a couple suggestions on how to dissable it. The simplest one (which I used) being nominating a bogus proxy which means that acroread never gets onto the net either by direct access pr by proxy. You can change these settings via Edit > Prefwerences > Proxy Settings.
################################################
29. INSTALLING REALPLAYER-10 AND REALPLAYER PLUGIN
Download the rpm and convert rpm to tgz with rpm2tgz. Then extract resulting package to a temporary place. it will extract to a directory /usr/local/RealPlayer. I will copy the entire RealPlayer directory to /opt whish is where I keep programs like this. Then I wlll link the RealPlayer executable to /usr/bin
ln -s /opt/RealPlayer/realplay /usr/bin/realplay /usr/lib/firefox/plugins
I can now access RealPLayer with the command realplay from konsole with the command realplay and also use that command in a desktop link with the realplay.png icon from /opt/RealPlayer/share.
To take advantage of the realplayer plugin do the following:
ln -s /opt/RealPlayer/mozilla/nphelix.so /usr/lib/firefox/plugins
ln -s /opt/RealPlayer/mozilla/nphelix.xpt /usr/lib/firefox/components
If you want these plugins recognised by konqueror be sure that /usr/lib/firefox/plugins is listed as a scan folder in konqueror > settings > configure konqueror > plugins and then scan for plugins.
################################################
30. GETTING LAZY ( a script that does some plugin installation)
This script does some of the above work for me:
#/bin/bash
# lazy.sh by rickfrm 200603013
# This script is a list of commands that will make links and
# put plugins where they belong. It will link execuatable in /usr/bin,
# it links plugins in /usr/liib/firefox, and it assumes that the things
# needed are already there. If you use konqueror you will need to add
# firefox plugins to konqueror fron Settings>Configure Konqueror>Plugins.
# Run this script as root
# Realplayer-10 is already installed in /opt
ln -s /opt/RealPlayer/realplay /usr/bin/realplay
ln -s /opt/RealPlayer/mozilla/nphelix.so /usr/lib/firefox/plugins/nphelix.so
ln -s /opt/RealPlayer/mozilla/nphelix.xpt /usr/lib/firefox/components/nphelix.xpt
# Adobe Acrobat-7.0 (acroread) is installed in /opt/Adobe/Acrobat7.0
# Something will still have to be done with /opt/Adobe/Acrobat7.0/Reader/intellinux/plug_ins/PPKlite.api
# In order to run with PPKLite.api OpenLDAP must be installed. Or else delete/move it.
ln -s /opt/Adobe/Acrobat7.0/bin/acroread /usr/bin/acroread
ln -s /opt/Adobe/Acrobat7.0/Browser/intellinux/nppdf.so /usr/lib/firefox/plugins/nppdf.so
# Flashplayer is installed with its own script flashplayer-installer and is not
# handled in this script
# Install wincodecs MPlayer_codecs-20050412-i686-2jto.tgz (or some other) from linuxpackages.net.
# then make them available.
ln -s /usr/lib/codecs/ /usr/lib/win32
################################################
31. INSTALLING lm_sensors and ksensors
lm_sensors will give you info like cpu temperature, fan speeds, etc. and ksensors is a KDE ap for display in gui. ksensors can be put in the panel as an applet.
I used sensors version 2.9.2 with libsensors version 2.9.2. After installing I ran /usr/sbin/sensors-detect and followed the prompts. Towards the end I was given a list modules to load based on what sensors-detect found. I put them into the folling script and installed in /etc/rc.d
#!/bin/bash
# /etc/rc.d/rc.lm_sensors
#in 2.6.X kernerls the following line should not be required
#/sbin/modprobe i2c-proc
/sbin/modprobe it87
/sbin/modprobe eeprom
/sbin/modprobe i2c-isa
/sbin/modprobe i2c-viapro
/usr/bin/sensors -s
# End of script
This script then needs to be called at boot either from /etc/rc.d/rc.local, or /etc/rc.d/rc.modules, or /etc/rc.d/rc.M. rc.local is for scripts that one might want to run a boot which are not run from somewhere else, rc.modules is for loading modules that are not loaded from some where/thing else, and rc.M is used to call the scripts in /etc/rc.d that load servers, daemons and such.
I'll add the following lines to /etc/rc.d/rc.M as the next to last stanza just before the stanza that call rc.local.
# Load modules for lm_sensors:
if [ -x /etc/rc.d/rc.lm_sensors ]; then
/etc/rc.d/rc.lm_sensors
fi
################################################