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.
5 machines that is a good amount of machines. But anyways. In the default /etc/swaret.conf file it saves all of the downloads to /var/swaret. Then on one of the machines you can run samba, you run this on the machine with the most recently downloaded packages of course. Then from the client computers mount the network drive and cd to the mounted directory, and installpkg.
As far as automated, just let swaret run as a cron job with the -a switch after --upgrade; it will d/l and install all upgradeable packages automatically.
But what I believe you are asking about is something more along the lines of creating your own local repository. This is very doable, although I can't say exactly how. One machine can check and update the packages daily (sync up with mirrors) and the other machines would just need the path to that machine added to swaret.conf. I think I saw something concerning this in the faq or forum on the swaret site.
In swaret.conf on your 5 machines, you should be able to add a line (and comment out the rest) which points to the download folder on your main box. Then run swaret --update and swaret --upgrade -a - you could even set it as a cron job, if you feel adventurous.
I use NFS for syncing my packages between laptop and desktop, and have /var/cache as an export on my desktop to share to my laptop. Makes it pretty easy to do upgrades and the like, only downloading once.
I don't use swaret, though, I use slapt-get.