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've probably installed about 20-odd slackbuilds (from slackbuild.org) on a vanilla 12.1 install and I'm not too sure about how updates are going to work yet.
If I install say slackpkg will it pull all the slackbuild packages in too and check for updates to those as well or just the ones installed by slackware. Something like digikam for instance has half a dozen dependencies listed, do I have to check all these manually for updates?
What's the best way to go about this? I wouldn't be too keen to be regularly checking tens of libraries for updates.
Regular checks is your ownly option. The http://slackbuilds.org site only has scripts, and you built all those packages yourself. Slackpkg or any other tool (except perhaps sbopkg) can not handle this.
I use a convenient shell alias to keep me informed about kernel update
alias newkernel='curl http://www.kernel.org/kdist/finger_banner'
Ok this was easy, now to make scripts that search for new version from every software site may not be an option
But not all softwares need to be updated as frequently as server softwares for example (which are mainly updated for security patches). As long as it works, for my part I don't bother with mplayer upgrade for example.
Just my opinion anyway
Hey, saw your work: http://code.google.com/p/sbopkg/, it is incredible! Congrat
Thank you and Alien bob too! Although I have my slackbuild system, I visit often Slackbuild.org to see the configure options for various packages , also if there are any tweaks with the install etc.. very great values of information! Keep up the good work
Thanks, guys, I'm glad you are finding it useful. It's under active development with lots of great patches and helpful contributions coming in from users, and a new version is released about once a month. If you encounter any problems or wish to file a bug report or feature request, please feel free to find me in IRC or, better yet, file it in the Issue tracker at the project's web site.