Anyone else having a repository problem for current?
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.
FWIW, when slack13/64 was still in -current stage (before it was ever released stable) I was using Oregon State rsync mirror, with Robby's rsync-mirror script. Upon seeing the "Warning" message from their rsync server (mentioned at the post linked above) I emailed the OSUOSL lab and inquired about it, and about whether or not I, as an end user, should not be using their rsync service for personal updates. I got a reply a day or two later, telling me that it was perfectly OK for me to be doing what I was doing.
NOTE/DISCLAIMER: I too always respect such wishes of mirrors -- their bandwidth is graciously donated to them in some cases, and to us in all cases, so it may be best to err on the cautious side in this case. Since I believe I no longer have a copy of that email from them, I cannot prove that they said it was OK, so again, err on the cautious side.
I may have posted that email on LQ here somewhere, because that issue arose before, which *might* have been why I emailed them in the first place. Also, I took it to mean specifically the rsync service, as opposed to both rsync and other methods, but that may be a wrong interpretation. If you do come across it, please provide us the location.
Maybe I should email them again..
Anyhow, back on track: "-current repos", on any particular mirror, might be in a semi-available state at any given time, due to the mirror itself being updated at the very moment YOU are trying to download from it.
I dunno if this has ever happened to me, but so far so good as I am using OSUOSL's ftp server to upgrade to current as we speak. It's in the /xap/ folder right now.
Thank you very much for this post! I became concerned that I was perhaps doing something illegal by rsynching my -current images with OSUOSL. I am very thankful that they are willing to host our distro.