Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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've been archiving data from our database server by creating an iso, and then using cdrecord-prodvd to burn a dvd-r of the image.
the problem is after running cdrecord-prodvd, the system time is about 7 - 15 minutes slow. the actual time loss appears to be related to how big the dvd is. burning 2 gig will slow the clock about 7 minutes, but burning a full 4.4 gig will slow the clock aboiut 15...
has anybody heard of this before? any ideas on how to stop this from happening?
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
that device should exist whether or not the real-time clock module is running. running lsmod will show the inserted modules.
if you check your /lib/modules/<kernel-version> for a rtc.o and it exists, then you'll know it's not built into the kernel.