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 last used Slack at 3.2, so I *used* to have some idea as to how to do things.
I'm tired of Red Hat for one overriding reason- the RPM-based deal is both great and awful.
It's great for speed and ease of use. But it isn't working for me as I have a machine up long-term.
In a real system, you need to apply security patches. You might need an app that isn't built into RPM. In short, you need to be able to use the old "compile in situ" and "make install" methods. As I have found, you rapidly have your package management system (whatever that may be) with no knowledge of the actual installed system.
If pkgtool could solve this, I'd gladly use Slack again.
What would be really cool? If you could analyse what "make install" was doing, and build a Slack "package" from that, then use that "package" to do the install. You could install whatever, right from source, and always have the package management system in sync with the live system.
How can I dig deeper into pkgtool operation? I'm happy to look at docs.