Every been typing along somewhere and have your cursor jump across the page because your thumb hit the touchpad on your laptop accidentally?
Well, on some of those high priced commercial operating systems like Windows or MacOS there might actually be a setting or a keyboard shortcut that disables your touchpad. Us Slackware users are made of stronger stuff than most. We don’t want no silly buttons and keyboard shortcuts. We want scripts and command line stuff, right? We like to do things down at the nitty-gritty level of computing.
So, with that in mind, if you’re running Slackware/KDE, you can make yourself a nice little script that will disable your laptop’s touchpad and you’ll never have to cuss again when that cursor goes zooming across the screen while you’re typing that flaming post on USENET to that know-it-all Ubuntu dev.
Here’s what you do…
First check to see if you have a /home/<username>/.kde/env directory. If you don’t, create it:
you@your_system ~:$ cd .kde
you@your_system ~:$ mkdir env
You can also do this graphically, if you prefer, but we know you hardcore Slackers don’t do things graphically now, do you? ;)
Anyway, once you’ve determined that you have the directory or have created one, you can now create the simple little script to place in there that will KILL that annoying touchpad.
Using vi, vim, or whatever editor you like, create this small file:
Save the file as “myenv.sh” in your /home/username/.kde/env directory. Make sure it is executable:
you@your_system ~:$ chmod 755 myenv.sh
Log out of your current KDE session and log back in. The touchpad from HELL is now as dead as weird uncle Bob’s hairpiece. WOO-HOO!
For those of you who occasionally use your laptop sans an external mouse, you can always revive the touchpad by changing the permissions on the myenv.sh file or just renaming it to myenv.inop. Since “inop” is an extension that the operating system does not recognize, it just ignores it. I’ve used “inop” to kill executables since way back in my Windoze daze. It works fine.
Anywho, I hope this little trick will make your Slackware/KDE computering that much more enjoyable. Oh, and I cannot take credit for this at all. A member of the kde.org forums called google01103 posted this tip in a thread over there about disabling that pesky touchpad. Credit where credit is due. That’s my motto.
Image credits: toilet laptop user – source/ownership unknown = If you own this image, please contact me regarding permissions/copyrights. ~Eric
Slackware 14.1 released…
Yes, it is that time again! After well over a year of planning,
development, and testing, the Slackware Linux Project is proud to
announce the latest stable release of the longest running distribution
of the Linux operating system, Slackware version 14.1!
We are sure you’ll enjoy the many improvements. We’ve done our best to bring the latest technology to Slackware while still maintaining the stability and security that you have come to expect. Slackware is well known for its simplicity and the fact that we try to bring software to you in the condition that the authors intended.
Slackware 14.1 brings many updates and enhancements, among which you’ll find two of the most advanced desktop environments available today: Xfce 4.10.1, a fast and lightweight but visually appealing and easy to use desktop environment, and KDE 4.10.5, a recent stable release of the 4.10.x series of the award-winning KDE desktop environment. These desktops utilize udev, udisks, and udisks2, and many of the specifications from freedesktop.org which allow the system administrator to grant use of various hardware devices according to users’ group membership so that they will be able to use items such as USB flash sticks, USB cameras that appear like USB storage, portable hard drives, CD and DVD media, MP3 players, and more, all without requiring sudo, the mount or umount command. Just plug and play. Slackware’s desktop should be suitable for any level of Linux experience.
Slackware uses the 3.10.17 kernel bringing you advanced performance features such as journaling filesystems, SCSI and ATA RAID volume support, SATA support, Software RAID, LVM (the Logical Volume Manager), and encrypted filesystems. Kernel support for X DRI (the Direct Rendering Interface) brings high-speed hardware accelerated 3D graphics to Linux.
There are two kinds of kernels in Slackware. First there are the huge kernels, which contain support for just about every driver in the Linux kernel. These are primarily intended to be used for installation, but there’s no real reason that you couldn’t continue to run them after you have installed. The other type of kernel is the generic kernel, in which nearly every driver is built as a module. To use a generic kernel you’ll need to build an initrd to load your filesystem module and possibly your drive controller or other drivers needed at boot time, configure LILO to load the initrd at boot, and reinstall LILO. See the docs in /boot after installing for more information. Slackware’s Linux kernels come in both SMP and non-SMP types now. The SMP kernel supports multiple processors, multi-core CPUs, HyperThreading, and about every other optimization available. In our own testing this kernel has proven to be fast, stable, and reliable. We recommend using the SMP kernel even on single processor machines if it will run on them. Note that on x86_64 (64-bit), all the kernels are SMP capable.
Here are some of the advanced features of Slackware 14.1:
- Runs the 3.10.17 version of the Linux kernel from ftp.kernel.org.
The 3.10.x series is well-tested, offers good performance, and will be
getting long term support from kernel.org. For people interested in
running the previous long term support kernel series, we’ve provided
sample configuration files for Linux 3.4.66 under the /testing directory.
And, to make it easier for people who want to compile the latest Linux
kernel, we’ve also put configuration files for Linux 3.12 in /testing.
- System binaries are linked with the GNU C Library, version 2.17.
This version of glibc also has excellent compatibility with
- X11 based on the X.Org Foundation’s modular X Window System.
This is X11R7.7, a new release, with many improvements in terms of
performance and hardware support.
- Installs gcc-4.8.2 as the default C, C++, Objective-C,
Fortran-77/95/2003/2008, and Ada 95/2005/2012 compiler.
- Also includes LLVM and Clang, an alternate compiler for C, C++,
Objective-C and Objective-C++.
- The x86_64 version of Slackware 14.1 supports installation and booting
on machines using UEFI firmware.
- Support for NetworkManager for simple configuration of wired and
wireless network connections, including mobile broadband, IPv6, VPN,
and more. Roam seamlessly between known networks, and quickly set
up new connections. We’ve retained full support for the traditional
Slackware networking scripts and for the wicd network manager,
offering choice and flexibility to all levels of users.
- Support for fully encrypted network connections with OpenSSL,
OpenSSH, OpenVPN, and GnuPG.
- Apache (httpd) 2.4.6 web server with Dynamic Shared Object
support, SSL, and PHP 5.4.20.
- USB, IEEE 1394 (FireWire), and ACPI support, as well as legacy PCMCIA
and Cardbus support. This makes Slackware a great operating system
for your laptop.
- The udev dynamic device management system for Linux 3.x.
This locates and configures most hardware automatically as it
is added (or removed) from the system, loading kernel modules
as needed. It works along with the kernel’s devtmpfs filesystem
to create access nodes in the /dev directory.
- New development tools, including Perl 5.18.1, Python 2.7.5,
Ruby 1.9.3-p448, Subversion 1.7.13, git-1.8.4, mercurial-2.7.2,
graphical tools like Qt designer and KDevelop, and much more.
- Updated versions of the Slackware package management tools make it
easy to add, remove, upgrade, and make your own Slackware packages.
Package tracking makes it easy to upgrade from Slackware 14.0 to
Slackware 14.1 (see UPGRADE.TXT and CHANGES_AND_HINTS.TXT).
The slackpkg tool can also help update from an older version of
Slackware to a newer one, and keep your Slackware system up to date.
In addition, the slacktrack utility will help you build and maintain
your own packages.
- Web browsers galore! Includes KDE’s Konqueror 4.10.5, SeaMonkey 2.21
(this is the replacement for the Mozilla Suite), Mozilla Firefox ESR 24.1,
as well as the Thunderbird 24.1 email and news client with advanced
junk mail filtering. A script is also available in /extra to repackage
Google Chrome as a native Slackware package.
- The KDE Software Compilation 4.10.5, a complete desktop environment.
This includes the Calligra productivity suite (previously known as
KOffice), networking tools, GUI development with KDevelop, multimedia
tools (including the Amarok music player and K3B disc burning software),
the Konqueror web browser and file manager, dozens of games and utilities,
international language support, and more.
- A collection of GTK+ based applications including pidgin-2.10.7,
gimp-2.8.6 (with many improvements including a single window mode),
gkrellm-2.3.5, xchat-2.8.8, xsane-0.998, and pan-0.139.
- A repository of extra software packages compiled and ready to run
in the /extra directory.
- Many more improved and upgraded packages than we can list here. For
a complete list of core packages in Slackware 14.1, see this file:
Downloading Slackware 14.1:
The full version of Slackware Linux 14.1 is available for download from the central Slackware FTP site hosted by our friends at osuosl.org:
If the sites are busy, see the list of official mirror sites here:
We will be setting up BitTorrent downloads for the official ISO images. Stay tuned to http://slackware.com for the latest updates.
Instructions for burning the Slackware tree onto install discs may be found in the isolinux directory.
Purchasing Slackware on CD-ROM or DVD:
Or, please consider purchasing the Slackware Linux 14.1 six CD-ROM set or deluxe dual-sided DVD release directly from Slackware Linux, and you’ll be helping to support the continued development of Slackware Linux!
The DVD release has the 32-bit x86 Slackware 14.1 release on one side, and the 64-bit x86_64 Slackware 14.1 release on the other. Both sides are bootable for easy installation, and includes everything from both releases of Slackware 14.1, including the complete source code trees.
The 6 CD-ROM release of Slackware 14.1 is the 32-bit x86 edition. It includes a bootable first CD-ROM for easy installation. The 6 CD-ROMs are labeled for easy reference.
The Slackware 14.1 x86 6 CD-ROM set is $49.95 plus shipping, or choose the Slackware 14.1 x86/x86_64 dual-sided DVD (also $49.95 plus shipping).
Slackware Linux is also available by subscription. When we release a new version of Slackware (which is normally once or twice a year) we ship it to you and bill your credit card for a reduced subscription price ($32.99 for the CD-ROM set, or $39.95 for the DVD) plus shipping.
For shipping options, see the Slackware store website. Before ordering express shipping, you may wish to check that we have the product in stock. We make releases to the net at the same time as disc production begins, so there is a lag between the online release and the shipping of media. But, even if you download now you can still buy the official media later. You’ll feel good, be helping the project, and have a great decorative item perfect for any computer room shelf.
You can order online at the Slackware Linux store:
Other Slackware items like t-shirts, caps, pins, and stickers can also be found here. These will help you find and identify yourself to your fellow Slackware users.
Order inquiries (including questions about becoming a Slackware reseller) may be directed to this address: firstname.lastname@example.org
Have fun! :^) I hope you find Slackware to be useful, and thanks
very much for your support of this project over the years.
Patrick J. Volkerding <email@example.com>
Visit us on the web at: http://slackware.com
Thanks to Pat V., the Slackware Linux team, and everyone who has contributed to and supported Slackware throughout the years!
Don’t forget to share your knowledge and gain some knowledge at the Slackware Documentation Project.
Sources: quoted announcement from the Slackware release Announcement.
Yes, actually. There are ways to harden your ssh implementations that aren’t that difficult.
An example of a simple way to increase your security when using ssh is to utilize the public/private key security rather than using your remote system’s user passwords to access the device. By using RSA key pairs, you can initialize your remote connection without ever having to expose your remote login’s password to the transfer at all.
I recently reinstalled my Slackware on my main machine (It’s a long story for another time, maybe). One of the things I needed to do was to reestablish my ssh connections between the machines on my local network. I settled in this evening to do just that. I ended up having some laughable issues while attempting to get all my machines talking again. We won’t go there, though.
In the process of troubleshooting my issues with ssh, I ran across Noryungi‘s excellent how-to at the Slackware Documentation Project. This place is really shaping up, no thanks to me. I haven’t been too active there because of my other pursuits lately. However, the dedicated folks who contribute there on a regular basis are kicking ass!
Anyway, using this tutorial, I easily set all three of my machines to use RSA public/private key exchange to initiate my ssh connections. I don’t have to sling my user’s passwords around the Ether anymore. Now anyone sniffing packets will only see the public RSA key bouncing around.
Ain’t technology wonderful? :)
Well, back to studying tomorrow. My Cisco ICND2/CCNA examination is rapidly approaching. Gotta’ go study up on those pesky routing protocols before bedtime.
A recent posting at Jeremy’s LinuxQuestions.org really lit a fire under some hardcore Slackware users.
There is so much Slackware information spread out over the Net in the form of private blogs, forums, websites, etc. All that wonderful information is so spread out, though. A new initiative has been launched recently to gather all Slackware information together in one location. A wiki-based format is being used with Arch Linux’s outstanding wiki as inspiration.
Eric Hameleers (Alien Bob) and many others from LinuxQuestions.org have spearheaded this new initiative. We even seem to have the blessing of Slackware’s BDFL – Pat V. This is a community thing. All interested people are invited to come join in making this project a successful thing. The oldest living GNU/Linux distribution deserves this.
C’mon over and lend a hand. All assistance is appreciated. Community is what makes GNU/LInux and Open Source the awesome thing that it is.
Alright. Enough about that Arch Linux for a while. Let me return to my first love… Slackware, baby!
A few days ago, Pat V. announced that the Current branch of Slackware has now gone beta. Well, let me tell you how I do things. Ever since I started running Slack as my primary OS back around 10.1 or so, I always upgrade to Current from stable once it goes beta. Up until this time around, I’ve always used the standard UPGRADE.TXT method found on the servers along with an in depth perusal of the CHANGES_AND_HINTS.TXT. I guess you could say that’s the “Slacker Way” of doing it.
I have three production systems running Slackware as the main operating system; my main system, my home office laptop, and my workshop system out back. They were all running fully updated 13.37 at the time I started this project. Normally, I would have started with the system that was lowest priority and easiest to restore should I do something stupid… that would normally be the shop system. However, it was awfully hot out there this week. I decided to sit in the AC and upgrade the home office laptop first.
Backup. Backup. Backup.
I wasn’t worried about my separate /home partition, although I did back it up anyway. However, it was that all-important /etc directory that I really wanted to make sure I kept intact. I made a backup which later turned out to be usable with difficulties. I copied it as my user into a user-mounted partition. Ooops! All ownership/permissions went to hell. I had to manually edit to get them back the way they’re supposed to be. And why did I need to do this?
Well, because for the first time ever, an upgrade did not go to well for me. But hey… Current is beta after all, right? Besides, I think it was me that boogered it up by overwriting critical config files without thinking. I did not have enough coffee that day, I don’t think. Long story short, I had to reinstall 13.37 on the laptop and restore the edited /etc to get things back to normal again. Once I did that, it was time to try again.
This time, however, I was convinced by friend chrisretusn from my private board, an old Slacker from way back, that I should try his somewhat custom version of upgrading using the slackpkg package manager. Now, to be honest, I was skeptical. I’ve heard a few horror stories about attempting slackpkg upgrades in Slack. His plan looked good, though, and it had worked for him. I figured, myeh… what the hell. I can always install 13.37 again.
Here’s how I did the upgrade using Chris’ slackpkg method:
- Since I don’t use KDE on my systems (any system, ever, any time ), I needed to edit my /etc/slackpkg/blacklist to add the kde and kdei directories.
- This is easy enough to do… just open your favorite editor (vim for me) and edit the file to add:
# Blacklist KDE components
- Now that I have KDE blacklisted and don’t have to worry about getting tons of KDE stuff dumped on my system, I can now edit my /etc/slackpkg/mirrors file to change to my Current server from the 13.37 one previously used.
- Also simple to do. I just opened my editor again and commented out (added #) the old 13.37 mirror and then removed the hash (#) from my new Current mirror.
- Next, using slackpkg, I upgraded the critical packages first, then the rest:
- # slackpkg update
- # slackpkg upgrade glibc findutils pkgtools slackpkg tar xz
- # slackpkg update
- # slackpkg install-new
- determine what you want to do with your new configs (keep, overwrite, merge, etc). For me, it’s a per file decision, so I chose “p” for Prompt and pay close attention to each config using the “d” option to see the differences before making that final choice. You don’t want to bork up your configs.
- # slackpkg upgrade-all
- this took a while for me. Your mileage may vary depending on your hardware and connection speeds.
- again, I needed to consider how to handle new config files.
- Now we’re getting to the final stretch… I needed to create an initrd for my newly installed generic kernel.
- Using the README.initrd that you can always find in /boot, I did the following to create my new initrd:
- mkinitrd -c -k 3.2.23 -m ext3 -f ext3 -r /dev/sda2 (your partition will be different, possibly)
- I then ran “lilo” from the command line to update the bootloader.
- Using the README.initrd that you can always find in /boot, I did the following to create my new initrd:
- Lastly, I ran #slackpkg clean-system
- and selectively chose what detritus to remove from my system. Older Xfce4 installations, for example. Be careful to NOT remove apps you’ve manually installed via SlackBuilds and such.
Cross fingers, toes, eyes, etc.. reboot.
WOO-HOO! We have bootup, Houston!
Now, there were some bugaboos here and there. I basically followed this same procedure above and upgraded my shop system, and finally, my main system; in front of which I’m sitting right now typing this mess. All three systems had the same issues. I spent the last two or three days debugging. I think I’m stabilized for the moment. If you want to see the “blow-by-blow”, you can read this thread over at Scot’s Newsletter Forums – Bruno’s All Things Linux.
It’s been fun, lemme tell ya’!
I’m having a couple issues that are really aggravating, though. One is that Thunar (Xfce’s file manager) is displaying all my unmounted partitions and “network” in the treeview on the left pain. Here’s a screenie:
I knew this was coming because I had the same issue in Arch when they went to Xfce 4.10 a while back. It’s annoying. I resolved it in Arch by converting to a pure systemd installation and installing gvfs and python2-udiskie (for auto-mounting). Can’t do that in Slack, though, not at the moment; so my quick fix to get rid of the unmounted volumes and get auto-mounting (almost) working again was to install Xfe (X File Explorer) via SlackBuild. Here’s a look at it:
It’s not as pretty as Thunar, but it has some neat features, including 1-click mounting of removable media. Pretty cool little file manager. Of course, if all these GUI apps keep aggravating me, I’ll just go back to Midnight Commander.
It’s been a learning experience. No, I didn’t upgrade the “Slacker Way” this time, but this way seems to have worked nearly as well. Now to just sit back and read the daily change logs till the final release. Thanks to Patrick Volkerding and all the other contributors, helpers, de-buggers, etc. who make this all possible. My life would be ever so much more boring without my beloved Slackware.
Have FUN with it!
Addenda 1: By the way, about that saving permissions when copying folders/files… the proper way to do that is to use the -p or –preserve switches with cp in the command line. So, to properly copy my /etc to a backup location, I needed to do this:
# cp -rp /etc <desination directory>
It works a lot better that way. :)
Addenda 2: Spent the day today debugging system issues. All systems are working 100% as of now. Here’s an updated log of what I did –> vtel57-github document
Earlier today, I received an email from Jeremy @ LinuxQuestions.org alerting me to his recent interview of Pat V.
It is absolutely outstanding. I enjoyed it very much. You should give it a looksee…
The times have been difficult for many of us this past few years.
For Slackware, it’s been no exception. Some of you faithful Slackers may have noticed lately that the Slackware home page has been offline. I posted about this at Jeremy’s Linux Questions forums. Alien Bob (Eric Hameleers) replied stating that it was an old hardware/lack of funds issue. This is sad. :(
I am in no way associated with the Slackware Linux project other than being a loyal user of the distribution and a frequent commenter/blogger on the subject of Slackware. I want to say that up front here. That being said, I would like to ask a favor… Please, stop on by the Slackware Store and click on that Donate button (top left side of page). I just did a few minutes ago. I didn’t give much. I don’t have much to spare, but I did give something.
For many of us, Slackware has brought joy to our lives, increased our productivity, and provided us with secure and stable computing environment. It’s also taught us a helluva lot about GNU/Linux. Pat V. has never, to my knowledge, stood on his soap box and asked for money from any of us to help defray costs of maintaining Slackware. It’s about time that we showed Slackware a little love. Slackware has always been there for us; it’s our turn.
A buck, two, twenty… every little bit adds up. Buy a cool T-Shirt or the Slackware Essentials book while you’re there.
Slackware needs to be around for many, many more years. Let’s do our part to see that it is.
Addenda to follow:
I’m beginning to regret writing this article and starting that thread at LinuxQuestions.org. For crissakes, people! This wasn’t meant to set off a shit storm. Initially, I was only concerned that the Slackware website had been down for a few days. Eric Hameleers (Alien Bob) responded to my query regarding the outage with a comment that, I must admit, did get me worrying a bit. Eric has explained the situation further in the comments on this article. Please read what he had to say.
I don’t worry about Slackware going anywhere anytime soon. There are too many of us loyal to this venerable GNU/Linux distribution to let that happen, I believe. My article here was written only for the purpose of possibly assisting the Slackware Project and Patrick Volkerding in continuing to do what’s been done for 19 years… keeping us all Slacking, baby! :)
This article wasn’t meant to incite rock and bottle throwing. GNU/Linux is ALL of us. I don’t care if you run Gentoo, Debian, Mandriva, or some barely known distribution on your systems. The fact is we are ALL GNU/Linux users. We ALL are part of this vast community that pulls together in times of need and helps out one another. GNU/Linux, FOSS, OpenRespect, etc.; that is US, folks.
I see that a few folks have dropped a buck or two in the Slackware tip jar. That’s excellent. Many of us have been using Slackware for years or have benefited from something that came about because of Patrick Volkerding and the Slackware Project. I have NO REGRETS if that tip jar fills some as a result of this article. I will have many regrets should the current shit storms at LinuxQuestions.org or Distrowatch continue.
Member ruario at LinuxQuestions.org made the following comment on the thread linked above regarding the Slackware server being down:
AlienBOB has stated that he and the other contributors don’t get any money from the Slackware donations. That said, he does a great to maintaining Slackware64, offering non-official binary packages, giving advice to users, and teaching us all how to make zoervleis . So if after donating to Slackware you have a little more money burning a hole in your pocket I noticed he has a PayPal donate button on his blog. If might be that Roberto F. Batista (aka PiterPunk), Robby Workman, Stuart Winter and the rest of the contributors take donations as well but I didn’t notice any PayPal links on their respective pages. Ah well, never mind and also I’m not made of money! :P
I post this here as an addendum because I also feel strongly that the people mentioned by ruario, and many others, are very deserving of some sort of recognition and gratitude from the every day users of Slackware. I’ve used some of Robby’s and Eric’s resources on my own systems before. I’ve learned much from them and the others mentioned; and many not mentioned, like Willy Sudiarto Raharjo, for instance.
If you feel the same, open that wallet again. These people spend a lot of their personal time to benefit assist and improve Slackware and to assist you.
In light of the fact that conversations regarding this topic have, in my opinion, gone in negative and non-constructive directions at the original LinuxQuestions.org thread and elsewhere, and in light of the fact that I was aiming more for support and assistance rather than rock and bottle slinging; I have come to regret starting that thread and writing this article. It was not my intention to stir shit and create strife for Pat V., Eric Hameleers, or anyone in the Slackware community. For this, I apologize.
To those of you who did offer non-critical assistance and support, thanks. The GNU/LInux community is enriched by your participation in it.
Addendum Final, Maybe ;)
Man! What a ride! Anyway, http://www.slackware.com is BACK UP! YAY! :)
Yes, I’m still on spring hiatus, but the place was getting to look a bit run down.
Plus, I wanted to show you all how to install this cool little browser that I found called Midori. Oh, it’s nothing new. It’s been around for a while, but it’s new to me. I first found it while using Salix OS recently on one of my tester partitions. I’m also using it in Zorin OS on one of my laptops. It’s fast. It’s pretty simplistic and minimal, too.
It is a bit complicated to install on Slackware, though. However, I’m sure you can do it. It just requires using some excellent SlackBuild scripts provided by the dedicated folks at SlackBuilds.org. Unfortunately, Midori is not one of those apps that you can install with just one SlackBuild. It has some dependencies… and its dependencies have some dependencies.
That always complicates things a bit, particularly in Slackware where you have to be smart enough to resolve dependency issues on your own. There is no a gaggle of volunteer repo maintainers doing it for you. That’s alright, though. Slackers are known to be smart and tough. We can take it. Dependency H3LL don’t scare us none. ;)
Let’s get started, OK?
Fire up your current browser and navigate to SlackBuilds.org. You know the place. You’ve been there before. Once you’re there, you’re going to search and download six different SlackBuild scripts and their related source tar balls. Got that? OK.
Here they are (click for the SlackBuilds.org page for each one):
Midori is your ultimate goal. It requires webkitgtk, libunique, and vala. The others are dependencies of webkitgtk and will have to be built first and installed before you build webkitgtk.
You should be familiar with the whole SlackBuild thing by now. Just in case, though, I’ll run through one for you.
Let’s build libunique first:
1. Download the source and the SlackBuild
2. Decompress the SlackBuild (using Xarchiver or your favorite tool)
3. Move the newly untar’d directory to your favorite temporary build directory
4. Move the libunique source package to the untar’d libunique SlackBuild directory (see Fig. 1)
5. Open a terminal and make the script executable:
# chmod +x *Build
6. Execute the script:
# sh *Build
NOTE: If you’re building on a 64 bit Slackware, you should use the prefix Arch=x86_64. For example: # Arch=x86_64 sh *Build
7. Once the script completes, using Slackware’s pkgtool to install the newly created .tgz package you’ll find in your /tmp directory:
# installpkg libunique*
NOTE: You might also want to keep these packages somewhere safe in case you ever want to reinstall Midori on this system or another Slackware installation somewhere.
Now, we need to build and install the rest of the dependencies in this order: icu4c, libsoup, vala. Once you’ve built and installed these guys, you can then build and install webkitgtk. Something to keep in mind once you begin your webkitgtk build; it is NOT one of those zippity-fast builds. Even on a fast system, it may take 45 minutes to build. Just be patient. Don’t sit there waiting for the pot to boil. Go have some dinner or take a healthy walk around the neighborhood while it builds.
OK, assuming you’ve managed to build and install libunique, icu4c, libsoup, vala… and then webkitgtk, you should now be able to build and install midori. It’s a pretty fast build, less than 1/2 a minute. Install it using pkgtool, as you did with the others above. If all went well, you should have a nice working Midori browser on your system now. If you run Xfce4 like I do, it will automagically show up in the Menu –> Network sub-menu.
Here’s my Midori running with the Midori Home Page opened:
NOTE: That’s an April Fools post you’re seeing there about merging Midori with Postler. ;)
Have lots of FUN! :)
P.S. I’m going back on hiatus now. See you again soon…
SlackBuilds are custom written installation scripts used to install non-native applications into your Slackware Linux operating system.
For today’s little SlackBuild tutorial, I’m going to use a SlackBuild to install PysolFC, a collection of really cool card games and majong-type games that is maintained by my friend Matthew Fillpot. Matt is one of the lead gurus over at the Linux.com Community site. Stop on over for a visit sometime.
One of the first things I do on any of my Linux installations is to create a hidden directory called .build in my /home directory that I use primarily for manual compiling of applications, or in this case in Slackware, installation of SlackBuild scripts (see Fig 1).
Figure 1 – /home/<user>/.build
OK, let’s get started. The first thing you’ll need to do is navigate to SlackBuilds.org in your favorite browser. In the small search window in the upper right hand corner, type in the application you’re looking for. In this case, that would be PysolFC. Once the search is completed, you’ll be on the pysolfc SlackBuild page (see Fig 2).
Figure 2 – Pysolfc SlackBuild Page
Now, the next thing you’ll need to do is download the source (PySolFC-1.1.tar.bz2) and the SlackBuild (pysolfc.tar.gz) into your .build directory (or wherever you want to build your stuff). Untar the SlackBuild script from the command line using this command:
$ tar -xvf pysolfc.tar.gz
Or you can unpack it using your favorite graphical decompression app like Ark or Xarchiver… use whatever you’re comfortable with.
You’ll now have an uncompressed directory called “pysolfc”. Move the source directory (PySolFC-1.1.tar.bz2) that you downloaded previously into your newly uncompressed pysolfc directory. That’s right. Just grab and drag that source directory right on into the pysolfc directory (see Fig 3).
Figure 3 – Inside the Pysolfc Directory
OK, then… Now for some fun command line stuff. I know you love working in the command line. Don’t be afraid. Just follow my directions. Alrighty…
1. Open your terminal application (Gnome Terminal, Konsole, etc.)
2. Type the following command to make the pysolfc SlackBuild script executable:
$ chmod +x pysolfc.SlackBuild
3. As root (to install globally on your Slackware system so all users can access), type the following command:
4. If all went well, the SlackBuild script will have created a .tgz application installer in your /tmp directory. Navigate to the /tmp directory in the terminal:
# cd /tmp
5. Check to see what’s there:
6. You should see a file called pysolfc-1.1-i486-2_SBo.tgz. That’s the baby! Install it using Slackware’s native pkgtool:
# installpkg pysolfc-1.1-i486-2_SBo.tgz
Voila! That’s it, folks. Easy-peasy. You’ll find an entry for PysolFC in your menu. Click on it and waste a few hours of your life playing some of those funky solitaire card games or that majong stuff.
Have FUN with it…
Note: This article originally appeared on my Nocturnal Slacker/Lockergnome blog (now defunct).
Some of you Slackers out there who use this panel applet may have noticed that it’s no longer updating.
There’s a reason why: Xfce Bugzilla – Bug 8105.
I’d been sloughing this off for a few weeks now. Today, I decided I was going to find a way to fix the damned thing… or dump it from my panel. I had noticed last night that it was still working fine in my Arch installation. Hmm… seems that the Arch folks patched their package with a working license key and partner ID to alleviate the bug issue reported above.
The first thing you want to do is extract the /xfce4-weather-plugin-0.7.4/panel-plugin/weather.h file from the source tarball. Modify this file as per the patch linked above by exchanging the old license key/partner ID for the newer ones:
#define PARTNER_ID “1121946239″
#define LICENSE_KEY “3c4cd39ee5dec84f”
#define PARTNER_ID “1003666583″
#define LICENSE_KEY “4128909340a9b2fc”
Once that’s done, save the file and add it back to the tarball.
Now you can build and install your SlackBuild as you normally would. After which, your xfce4-weather-plugin will work again. YAY! Thanks, Robby! :)
NOTE: I found no need to modify the SlackBuild file as Robby does for his patch. It worked fine without any changes.
Enjoy your weather, wherever you may be.