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 a clean re-install of Slackware 12.0 recently which went flawlessly.
Just one odd behavior noted: After burning a disc in K3b it no longer verifies. The disc pops out after recording and the verification doesn't start, nor will it start if I push the tray back in. I have to cancel it and accept the error message to get out of K3b. The disc it produces is always good though. It simply won't go through verification.
Same hardware, identical Slackware install, same K3b package (1.04) that I obtained from Slackware -current. Always verified in the past, but no longer does this.
I see this problem regularly on a server running 12.0 that I use to make backup CDs. The problem is inconsistent and I have no solution. I suspect that it is a result of an interaction between K3b and HAL. It seems as if when the CD tray is closed, sometimes HAL sees this and jumps in, so that K3b does not see the tray as having closed and so the verification fails. Other times, K3b works as expected.
I have not tried this, but it may help if the hald daemon is stopped before using K3b.
I got around the problem by selecting the option 'do not eject medium after write process' under advanced settings. Now the disc stays put after burning and continues on to verification. I googled the issue and it seems to be prevalent across all distros but I did not find any solution beyond disabling the tray eject.
What good is the md5sum of the hard drive(s) where the source files came from? I'm not talking about burning an .iso image, I'm talking about burning a data CD/DVD where you pick and choose what files and directories you want to back up.
(If everything is working properly, K3b will verify the disc by comparing each file with its source file byte for byte. It assumes that the source files aren't changed or moved in the meantime, of course.)
IsaacKuo, they're suggesting that you make an ISO out of the files as well (I think there's an option before burning), and then compare the md5sums of the CD/DVD with the ISO created. I always assumed K3b just created a temporary ISO and did the same only graphically, followed by deleting the ISO -- but you may be right in that it compares individual files (although in that case it may be more dangerous than comparing ISO images). I personally just create ISOs with K3b and then burn and verify the burn using a simple script that I created. That way I know exactly what is happening, and I can also use the scripts if I create an ISO without K3b (or if I download an ISO or something like that). But to each his/her own.
I know it doesn't create a temporary ISO because it would take several minutes at least to create a 4gig iso file (even if the files were on a local drive, which in my case they aren't). The actual behavior is that it starts spinning up the DVD burner and starts writing to it almost immediately.
Creating a temporary iso image is an interesting option, though, and one which I wish I had known about when I had the same problem.