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.
Why does slackbuilds require you to compile the packages from source code? Is there a technical or political reason why slackbuilds (or some other institution) cannot provide precompiled binary packages?
This is in response the the slackbuilds FAQ below:
Do you provide precompiled packages from your SlackBuild scripts?
No. We are not now, nor will we ever be, a source of precompiled packages.
The answer doesn't provide a reason, but appears vehemently against it?
I don't mind downloading the source and running the scripts to compile, but I would rather not if I can get away with it.
You probably already know this but binary packages have dependencies.
Depending on the system they were built on, they might have "unwanted" dependencies.
Providing scripts to do the job is failsafe, and gives absolute control to the one who is
building the package. Slackware is about control right?
Regarding some applications, there might also be licensing issues that prohibit binary distribution (eg. adobe reader) , so a build script is a workaround.
Never could understand that. This makes sense only when you build your own software - so you will be able to terminate build as soon as you see first error. If watching text in terminal is fun, consider using this: