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.
Did Xine play all media types, then stop with some? Can you be more detailed? How did you install Xine, was it from Dropline, a .tgz, or a source package? What do you mean by your modem cannot be opened?
Originally posted by h1tman im not sure why im running into all these problems all of a sudden. how do i logs for why my modem isnt workin anymore?
i will post more info later, what i really wanted to know is this normal or something
h1tman: you can check your log files in /var/log. Just use the handy less and tail commands to view them. You can also get information about the kernel messages generated at boot time, by typing dmesg at the command line. For more information try man dmesg.
As far as getting your modem working again, check the logs then try hitting the forum with the details, perhaps it's not as bad as it seems.