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.
I just got a new wireless router and now don't havr to go out on the road to get Wi-Fi anymore.
But what was an occasoinal annoyance is now becoming a real problem.
I cannot depend on wicd to maintain a connection.
It is as if wicd notices reduced web taffic (either slackpkg is installing a large package, or I've found a particularly interesting Wikipedia page) and when I (or the system) attempts to proceed again online, the connection isn't there.
Is there an easy way to insist that wicd hold a connection open until I specifically close it?
I used to have exactly the same problem. I never found a solid solution to the problem (it fixed itself after I upgraded from slackware 13.1 to 13.37), but my temp solution was to open a terminal and keep pinging google.com. That seemed to keep the connection open most of the time.
Wow, NetworkManager looks like it will do what I want, but I sure don't need all that Gnome stuff just to support the user interface. I don't have anything else that needs gnome-keyring and all its dependancies.
I'm running on an eeepc and prefer simpler, more lightweight solutions. I decided to take deeper look at wicd.
I checked out their home site on sourceforge. I went through all the docs again, checked the configs, didn't see anything out of line.
...but now, for ther first time ever, when wicd loses its connection, it immediately reconnects.
This is all I really need.
Last edited by leeeoooooo; 01-25-2012 at 03:44 PM.