SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello guys.
I have 3 computers at home with a very bad internet. Update the 3 computers is a torture.
I was thinking of using one of these computers to make a local repository server, so I would use little bandwidth, and it would be less torturous.
I found this link: https://mirrors.slackware.com/guidelines/
to sync a specific repository 'sync://mirrors.kernel.org/slackware/slackware64-14.2/'.
It turned out that I mirrored everything including the sources.
Am I on the right track or is there any more interesting way?
yep I've used that too, I have not used that script in a while but, you can make it do both just change the name of the file for stable or whatever just a different name, and mod it inside and you're cookin with gas. even have it make an updated ios. you're only going to need about ~5GB per OS current, stable, if I remember correctly.
then go into your mirror files and make the needed adjustments to point to where that is.
You can add an extra --exclude slackware64-14.2/source if you don't need the sources and slackbuilds, and replace the origin mirror with something closer to your location.
Here's mine. It's for current rather than 14.2, but it should just be a matter of changing all the 'current' references to '14.2' to swap it over.
I exclude kde, kdei, k (the kernel source), and any "source/" directories. I also backup old packages to $BKPDIR just in case I need to revert, though that's more likely when following current rather than a stable release.
rsync is a nuanced tool. It's worth reading the man-page and understanding it properly, otherwise you can have the occasional nasty surprise!
With this configuration my local mirror runs to 1.7G (as reported by du -sh). I periodically clear out $BKPDIR to reclaim space as it tends to grow quite quickly with current.
I would suggest the first step (if possible) to go to place with fast internet, download DVD iso of Slackware-current and create local mirror from this iso. Once you have it everyday updates wouldn't be so time consuming, except massive updates.
Maintain a local mirror to reduce bandwidth issues. For at least a decade or so I have been using my own modified version of Eric's rsync scripts.
One caveat is a local mirror has no package history. If you want to revert a package the local mirror will not contain older packatges. Been there done that. I retain copies of older packages through my backup plan.
Eric's script can be modified not to delete existing packages. Basically don't use the rsync --delete parameter.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.