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.
I see a lot of people that maintain alone a repository of their slackware packages or slackbuilds. Why not centralize all of this in a single place? I did a new project on google code, this provide a way to manage the files with git and it provides a way to just "upload" things and they can be downloaded after really easily after in the "Downloads" tab.
As a bonus, it provides us a bug tracker, that can be used to track outdated packages, packaging bugs, etc...
By default, we would have 4gb of space, but like, ALL the entire slackware package set is 2gb. So it's quite enough IMO.
I would give commit access to everyone that is currently maintaining a package repository and/or anyone that seems to be a known user here, on LQ.
Please, if your interested in this project, tell me what you think.
I'd like to know too if it's not a really good idea.
yes, they only provide you with the script to build the binary packages
it has a big advantage since you can use the same script to build the binaries on every machine, customized to what you have on your system
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
I can think of one downside: I build a lot of packages from SlackBuilds.org (like 85) but I insist that add-on software be installed in the /usr/local tree (bin, etc, lib64, ...) when it's libraries or applications and in /opt if it qualifies as something similar to FreeCAD, GMT, OpenOffice.org and the like. I try to keep distribution software; i.e., what comes on the DVD, uh, pristine might be the word.
Too, I have a thing about building from source on the platform (yeah, I know it really doesn't matter, binaries work just fine, but I like to optimize for the hardware just because).
So, I'm weird -- that's what FOSS is all about, eh?