I think I’m going to upgrade from Slackware 10.0 to Slackware 10.1. Yay SlackWare! (I have since migrated to Slackware 10.2, see 2005-10-15 Software.)
I installed *ctorrent* from linuxpackages.net (for Slack 10.0) and started downloading the torrents for the two installation disks. I’m not sure I need the other two discs. They contain sources (not needed) and *extra and pasture – whatever that is. A quick check shows that extra contains k3b – and I remember downloading that one from linuxpackages.net, too. And it has aspell wordlists. Cool. The pasture README.TXT file says:*
/pasture: These are things that have been retired ("put out to /pasture" :)
from Slackware, but might still be useful to some people.
I waited for a while, but then I thought that I’d be installing the packages manually anyway (following the upgrade instructions). And so I aborted all that torrent crud and settled for wget from a local mirror:
wget -nH --cut-dirs=2 ftp://mirror.switch.ch/mirror/slackware/slackware-10.1/slackware/*
Argh. That skipped directories!
wget -c -r -nH --cut-dirs=2 ftp://mirror.switch.ch/mirror/slackware/slackware-10.1/slackware/*
Grrrr. I forgot to set cut-dirs=4. Oh well. That’s what I get for cut-n-pasting command lines from the history. 😄 Will move those up later.
Well, and here’s for k3b:
wget -c -r -nH --cut-dirs=4 ftp://mirror.switch.ch/mirror/slackware/slackware-10.1/extra/k3b/*
Even though I’m interested, I’m going to skip all of the other packages in *extra such as brltty, emacspeak, j2sdk, parted, etc. I just have to remember where to get them. 😄*
wget -c -r -nH --cut-dirs=4 ftp://mirror.switch.ch/mirror/slackware/slackware-10.1/extra/bash-completion/* wget -c -r -nH --cut-dirs=4 ftp://mirror.switch.ch/mirror/slackware/slackware-10.1/extra/aspell-word-lists/*-de-* wget -c -r -nH --cut-dirs=4 ftp://mirror.switch.ch/mirror/slackware/slackware-10.1/extra/bittorrent/
(Not sure about the last one, after all I just got ctorrent – and I never used it once...)
wget -nH --cut-dirs=2 ftp://mirror.switch.ch/mirror/slackware/slackware-10.1/slackware/*
Argh. That skipped directories!
I was unable to connect. Argh!
Later...
Hah! I seem to be back online!
My madwifi driver was no longer installed after switching from Linux Kernel 2.4.26 to 2.4.29. Makes sense, I guess. So here goes, in case I forget:
After installing a new kernel, go to the madwifi source dir and rebuild it.
cd /mnt/src/madwifi make && make install
This will install some modules in _lib_modules/2.4.29/net. Load the module:
modprobe ath_pci
Check for the new device:
iwconfig
Verify that ath0 is available.
Make sure _etc_rc.d/rc.local is executable and runs the following commands:
ifconfig ath0 up dhcpcd -t 10 ath0
Later...
Hah! I seem to be back online!
My madwifi driver was no longer installed after switching from Linux Kernel 2.4.26 to 2.4.29. Makes sense, I guess. So here goes, in case I forget:
After installing a new kernel, go to the madwifi source dir and rebuild it.
cd /mnt/src/madwifi make && make install
This will install some modules in _lib_modules/2.4.29/net. Load the module:
modprobe ath_pci
Check for the new device:
iwconfig
Verify that ath0 is available.
Make sure _etc_rc.d/rc.local is executable and runs the following commands:
ifconfig ath0 up dhcpcd -t 10 ath0
Where did anti-aliasing go? Or did I just switch fonts? Where did the Verdana default font for everything go? I will have to investigate. Firefox looks crappy without anti-aliasing. Konsole too. I think this is definitely an anti-aliasing problem.
The solution was too simple to believe: In the KDE config menu → Appearance & Themes → Fonts, click on “use anti-aliasing for fonts”. I don’t remember ever touching that checkbox. Maybe that means the default changed with the new KDE version?
Emacs is also complaining: “Font `lucidasanstypewriter-14’ is not defined”. Eek! 🤓
Investigating the files in _usr_X11/lib/X11/fonts/75dpi: lucidasanstypewriter-14 is an alias for -b&h-lucidatypewriter-medium-r-normal-sans-14-140-75-75-m-90-iso8859-1 according to fonts.alias, but fonts.dir only defines
Now that I tried that longer lucidatypewriter-medium-r-normal-sans-14 font, however, I find that it doesn’t look good at all. Did I really use this!? Right now, 10x20 looks much better. 10x20 is an alias for misc-fixed-medium-r-normal-20-200-75-75-c-100-iso8859-1.
Anyway, here’s the test to see whether you are affected:
alex@confusibombus:*$ **grep lucidasanstypewriter-14 _usr_X11/lib/X11/fonts/75dpi/fonts.alias** lucidasanstypewriter-14 -b&h-lucidatypewriter-medium-r-normal-sans-14-140-75-75-m-90-iso8859-1 alex@confusibombus:*$ **grep lucidatypewriter-medium-r-normal-sans-14** _usr_X11/lib/X11/fonts/75dpi/fonts.dir lutRS14.pcf.gz -b&h-lucidatypewriter-medium-r-normal-sans-14-140-75-75-m-90-iso10646-1 alex@confusibombus:~$ **xterm -fn lucidasanstypewriter-14** xterm: unable to open font “lucidasanstypewriter-14”, trying “fixed”....
I just found the following in _var_log/Xorg.0.log:
(WW) Open APM failed (/dev/apm_bios) (No such device)
Maybe I need to create it?
I also noticed that once again, *halt* doesn’t halt the system. And I remembered that I had to use the bareacpi. kernel.
wget -c -r -nH --cut-dirs=4 ftp://mirror.switch.ch/mirror/slackware/slackware-10.1/kernels/bareacpi.i mv bareacpi.i/* /boot
Edit _etc_lilo.conf and use bzImage as the kernel image. I like to use mcedit _etc_lilo.conf. This is what it looks like:
image = /boot/bzImage root = /dev/hdb2 label = Linux read-only
Be sure to run lilo again:
lilo
I ignore this: “Warning: The boot sector and map file are on different disks.”
I also discovered that it is possible to support the Slackware Project by “buying” a donation. I “bought” a $20 donation. 😄
#Software