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.

Greetings,
For some time, I have been creating my own Slackware packages of software, some of which may be of interest to the Slackware community. I once negotiated with linuxpackages.net, a Slackware package repository website I use, about putting my Slackware packages on their website. However, they required me to put my package on a 3rd party website or put up my own website, for them to look at my packages before they would put them on their website. They didn't have a place on their website where I could just "drop them off" for them to look at. I looked into what it would require for me to set up my own website, but when I discovered how much effort it would take to create and maintain a website I would like, I back-burnered the effort and haven't followed up on it.

So here's my question: Do you have any suggestions for submitting Slackware packages for the community to download and how did you go about it?

I thank everyone who responded to my request. They were helpful.
As for Slackbuilds.org, my build scripts are much more complex and larger than the run-of-the-mill build scripts. They do a lot more error checking and respond to the standard --help and --version via getopt. They also allow a user build option for testing without being root. I discovered the hard way that building in /tmp can also be disastrous, so my build scripts use a safer /build instead. So, alas, my scripts do not meet the Slackbuilds.org requirements. So that rules out Slackbuilds as a distribution outlet. Unlike many package sites, such as LinuxPackages, my packages do include the build script.