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.
(For a moment I thought you were speaking Spanish )
No, I didn't even know it. But if I can't use k3b, I'd rather spend some time and learn how to use mkisofs and cdrecord (besides, I can't open Que's home page).
I tried k3b yesterday for the first time in Slackware 14 (new laptop; on my older one, with Slackware 13.1, it works), and it complained it could find no drives. Now that I think of it, I probably didn't add myself to the "cdrom" group, and running as root gave me some dbus error. But then I looked up on LQ/google, and I found out this thing about HAL, so I thought that was the problem and forgot about the "cdrom" group thing. So, I'll check it again as soon as I get home, and see if it was just a permission issue, and report back here.