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 recommend using the SlackBuild script to install this driver to a manageable directory.
There are several open source drivers that are used to drive Broadcom 802.11 chips such as b43 and ssb. They will conflict with this driver and need to be uninstalled before this driver can be installed. Any previous revisions of the wl driver also need to be removed.
The ssb driver must be removed (by hand or script) before wl is loaded. The wl driver will not function
Posted 09-07-2011 at 10:12 PM byReaperX7 Updated 09-07-2011 at 11:36 PM byReaperX7
Honestly as a Slackware user I'm very well skilled in this trait and can easily manage my own system, but what about automated package management distributions? Sure you can have a system hold your hand and walk you through in baby steps, but what about that rare case when a dependency is not resolved by the package management system because the package is obscure enough not to have a mainstream dependency file? What then? Honestly, I have ran across some of these. I've had to often do hour long...
I've been using Linux on and off for the past ten years or so and at first, even I was very intimidated by the OS. It took a lot of researching and also a lot of trial and error before I settled in on my current distribution, Slackware. I've had the opportunity and unfortunate privilege of trying out other distributions that were more or less a migraine. Red Hat, Mandrake, SuSE, Ubuntu, and a few others I've forgotten over the years.
As a user of Linux I've been ridiculed in college...