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.
Just wanted to say thanks for the write up. I've used your work several times as a reference with setting up my slack system. After looking at manual iptables configuration vs. rc.firewall I just had to say thank you. Iptables IS something I actually want to take the time to understand, but at this moment I don't have those hours to dedicate. rc.firewall has me at "superstealth" according to Gibson research, while keeping all my lan services in tact in about 10 minutes from download to tested.
Thanks. It's nice to have all this slack-noob reference in a single place.
A remarkably useful thread Josh. Thanks very much
One question about the firewall stuff. You say this:
The installation GUI was very simple. It asked a few questions, and if you are like me and not hosting any servers on your Slackware machine, be sure to select the 'stand-alone' or 'single machine' setup. That setup rejects any incoming traffic to your machine, which should be ideal for day to day computing.
To me a stand-alone is exactly that, it is never intended to connect to the internet for security reasons, but you clearly are connecting to the internet, so why did you choose this option?
Once again, this is one of the most useful threads I've seen, it's helped me a lot
"KDE started up and I was greeted with some Akondai error messages and KDE Migrator errors." This was caused because your Akondai was using MySQL which won't allow root login. So, as long as you are using root login, you will met the error.
Sum it up, please ignore the error when you login root GUI.
A good, easy to understand jumping point for my first .conkyrc, truth is all I needed to do was tailor it for my machine and now I have all of the important info I need right on my desktop, many thanks!
Also, thanks for the info hughszg,
This was caused because your Akondai was using MySQL which won't allow root login. So, as long as you are using root login, you will met the error.
It always bothered me that I didn't know the reason for those errors, knowledge is power.