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.
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.
This is just an observation by me, but it seems with the coming of Slack13 that there are more Slack users. It seems like there are more people running current too.
I think there's usually a surge in forum activity once we get to the 'Release Candidate' stage. The fact that Slack 13 introduces a 64bit option is probably generating a little more interest than normal this time, and the same is probably true of KDE4.
When it's close to an release then i find it normal to run current (if it's not an production box) to be able to test it for the last bugs that makes slackware as stable as it is. Thats my
Yep, me too. I run current alongside stable for a few weeks at the end of the release cycle. As soon as current becomes 13.0 I will edit fstab to direct to my /home directory to 13.0 and edit menu.lst to make 13.0 my default, and move my testing .kde to my new active /home. Which means I will be running 13.0 stable about 5 minutes after I notice it has been released, no having to wait on a massive download and install, because that has already been done, and configured to my taste.
Just loaded Slackware64 -current and setting up to suit my needs. Ran for a while in VM but now a real thing. She's smooth as silk.
I'm still customizing my FF but that can wait. I'm not too sure as to what add-ons that I'll really need.
Most activity with Slackware does occur around rc#. Some new users will continue while others will jump ship when they stumble. Then they just blame the Distribution. Most distro-bunnies don't stay long.
I just built a server out with Slack 12.2 a couple weeks ago BEFORE I started seeing the buzz that 13 is on the horizon. Now, I am going to replace that newly built server with a Dell PowerEdge 64-bit Intel chip. I CAN'T WAIT to get the 64-bit version of Slack!
I am checking this forum more times per day than I do any other site. Just waiting and hoping for the release...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
