SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
kabamaru, thank you very much for your work on these SlackBuilds. They sure make the whole humble bundle experience more enjoyable. I wish you had the other Humble Bundles so I wouldn't have to figure out the SlackBuilds myself (I'm real lazy). I'd like to ask you why you sometimes write your SlackBuilds require the tar.gz version, sometimes the .deb and sometimes the binary installer? When the games only provide the binaries (FrozenSynapse) or the .debs (SpaceChem), it's easy to figure it out, but why did you make a SlackBuild for anomaly using the binary installer (when there was a tar.gz file) and for Edge using the tar.gz file (having a binary installer available)? This is not a criticism. Now that I know of that, I look at your page before downloading the games for the last Humble Bundle. I'd only like to know why you didn't choose a file format and used it for all the games as the default.
I always go with the tarball, when one is provided. If there isn't one I go with the installer which is something a Slacker would prefer downloading (I guess) instead of an rpm/deb because he can quickly install this even without using a slackbuild, so maybe he's already downloaded this. Sometimes they don't provide a tarball, nor a bin installer. Then I go with the deb (I just stick with a distro format). They're all 'binaries' though. Tarballs too. Only a couple of games provide their source, and it's a PITA to compile it.
You're right about Anomaly, it was an anomaly in the general rule; the tarballs gave me errors while extracting, _both_ times I downloaded them.
EDIT: it turns out utorrent on my mac didn't do a great job downloading the files. I used ktorrent on my Slackware machine and now they work (updated the slackbuild too). ktorrent for the win
I should have checked your slackbuilds before I scratched my noggin with Machinarium about missing 32 bit libs and LD_LIBRARY_PATH ! Boy, I don't know why I keep forgetting this stuff....
the flagship game for the aptly titled Humble Botanicula Bundle, Botanicula, is a game that is unplayable for most.
Botanicula runs on the Adobe Air platform, a platform that has been abandoned by Adobe on Linux and hasn’t seen a new release for some time. Adobe Air is no longer being actively packaged by distributions and is only available through Adobe as a binary blob. There is a lot of talk on the Internet about how to get Adobe Air going so that purchasers can give Botanicula a go, but is it really worth it?
The (otherwise excellent) Powerbase blogger must have misread my comment and got too excited, because he's giving me credit for your blog and SlackBuilds. I've posted comments stating that I've had nothing to do with either, of course. Let's hope he corrects himself soon.