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.
Mon Jun 10 21:51:54 UTC 2013
After careful consideration and a lot of testing as the 3.9.x kernel series has progressed, we have decided to move to the latest kernel. It should be a nice improvement over 3.8.13, which as you all know has reached EOL (at kernel.org anyway... I do know about Ubuntu's git maintained version). After the last experience with upgrading 14.0 to a newer LTS kernel, I can't say that I have too much faith in the idea that LTS kernels can be upgraded without causing any regressions. If the kernel we're using in -current happens to be delared an LTS kernel, sure, that's a nice plus, but I don't think it's worth rolling all the way back to 3.4.x just to have an LTS kernel. Anyway, test it out and report any issues!
Get the packages from my 14.0 package repository while they are hot! If you are still running Slackware 13.37 you should stick with LibreOffice 3.6.6 for which I also have packages. They are also available from several mirrors. Remember, the mirror sites usually have a bigger bandwidth available than the master site! If you are a mirror administrator, and want to be added to the list, contact me.
Here is the shortlist:
Sat Jun 29 22:08:25 UTC 2013 patches/packages/mozilla-firefox-17.0.7esr-x86_64-1_slack14.0.txz: Upgraded. This release contains security fixes and improvements. For more information, see: http://www.mozilla.org/security/know...irefoxESR.html (* Security fix *) We had to switch to ESR here as well, as there's a problem running Firefox 22.0 on Slackware 14.0 under KDE (crash when oxygen-gtk2 is installed). Forcing people to uninstall oxygen-gtk2 isn't really an option for a security fix, and upgrading to the latest oxygen-gtk2 did not help. It's possible that future Firefox/Thunderbird security updates will always come from the ESR branch.
Mozilla will offer an Extended Support Release (ESR) based on an official release of Firefox for desktop for use by organizations including schools, universities, businesses and others who need extended support for mass deployments. You can read more about the plan here.
What does the Mozilla Firefox ESR life cycle look like?
Releases will be maintained for approximately one year, with point releases containing security updates coinciding with regular Firefox releases. The ESR will also have a two cycle (12 week) overlap between the time of a new release and the end-of-life of the previous release to permit testing and certification prior to deploying a new version.
Maintenance of each ESR, through point releases, is limited to high-risk/high-impact security vulnerabilities and in rare cases may also include off-schedule releases that address live security vulnerabilities. Backports of any functional enhancements and/or stability fixes are not in scope.
At the end of the support period for an ESR version:
the release will reach its end-of-life
no further updates will be offered for that version
an update to the next version will be offered through the application update service
Some Slackers believe that Mozilla ESR releases should be in patches with Mozilla FF & Thunderbird official releases in /extra for those that do not use KDE. Look here for LQ Slackers input: Firefox 17.0.7esr?
Tue Aug 6 05:23:34 UTC 2013 Looks like 3.10.x got LTS status, but more importantly fixes the power issue on resume with some Intel machines. So, we're bumping the kernel to 3.10.5, and will stick with that series for the release. A few more things to look at before calling this a beta, but it's pretty close. Enjoy!
Wed Sep 18 02:56:19 UTC 2013 Hey folks, I'm calling this a beta! Really, it's been better than beta quality for a while. There will probably still be a few more updates here and there (and certainly updates to the docs). Enjoy, and please test.
Mon Oct 14 22:09:17 UTC 2013 And with this batch of updates and fixes (clearing the rest of the important stuff from the TODO list), we have arrived at Slackware 14.1 release candidate 1! Please test and report any remaining issues. UEFI (with the exception of Secure Boot, which will have to wait until we have real hardware) should be fully implemented in the installer now, which will detect and warn about common problems, set up the EFI System Partition under /boot/efi, and install ELILO and a UEFI boot entry automatically. There's a new README_UEFI.TXT file with detailed instructions for installing 64-bit Slackware on UEFI (32-bit won't support native UEFI due to the mismatch between 64-bit UEFI firmware and a 32-bit kernel, so Legacy BIOS will be the only way to install 32-bit Slackware on UEFI). Several useful netfilter and networking utilities have been added (thanks to Robby Workman and /dev/rob0 for these). With this batch of updates, everything should be considered frozen (including the kernel) unless there's a good reason to change something. Enjoy! See you all for the release, hopefully soon. :-)