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.
Most ISPs implement a transparent web-proxy/cache these days and they can sometimes deliver out of date information. The osuosl one has definitely been updated, so if it's still delivering the old one to you even after you've cleared your browser cache, then it's probably your ISPs fault. Alternatively, osuosl could be using some sort of round-robin cluster and not all nodes have been updated yet.
Check the ChangeLog.txt in a few minutes, Firefox update will be in there as well as some other niceties.
After upgrading 13.0 today, Firefox is at 3.6.2 but Mozilla Firefox 3.6 Release Notes say "Firefox 3.6.3 fixes a critical security issue ... bug 555109" so we are not in the clear yet. Bug 555109 is not visible even after logging in to Mozilla's Bugzilla so it's not possible to assess the risk or consider workarounds.
Time zone can be a factor. If Pat posts updates early morning US time then they might be too late for the daily sync and not turn up till the following day. I've never had to wait more than 1 day though.
My ISP virignmedia have their own mirror, but I've found that one highly unreliable.