Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 got the new .10.03 source and did what I was told to do like a good little boy in the readme and install file but it still opens up .09.xx if I go to the actual location and open up the .desktop file.
(I'm still new to linux so if what I said was all wrong then please enlighten me, it's hard to get to grips with program installation without a \Program Files\ directory... heck, I made one and have been untarring there ever since)
How do I even get to that setup dealy for a previous or new (preferable) install.
Aside from all that the link you posted doen't even solve my problem, but hey, gotta compile a kernel sometime and 2.6.0 is out so I gotta get back to compiling modules.
correct me if im wrong but if you use kernel 2.6 you need not make any alterations regarding ide-scsi.
I say this because ive installed k3b for DVD writing and now ive installed all dependencies it asked for its seems to run fine. I have read that patches are needed and that I may need to edit some conf files etc but so far ive not needed.
Im running RedHat 9 with a sony DRU500A DVD-/+RW and a Pioneer DVD-RW,...so far so good
First, as you've mentioned, you must enable SCSI emulation in the kernel. I was unaware that the procedure for this might be different in the 2.6 kernel, as I am still running 2.4. Basically, you are looking for the only option that has "SCSI" and "emulation" in the same sentence. Enabling SCSI emulation won't significantly increase kernal size, slow things down, mess with other features, blah blah blah... so there's really no good resaon not to do it (if you have an IDE cd burner).
Recent versions of cdrecord, the program used by k3b, cdbakeoven, xcdroast, and other popular GUIs for cd burning, support IDE without SCSI emulation. But a lot of the cutting-edge alpha-beta versions of cdrecord do not, so it's still worth it to compile SCSI emulation into the kernel. Also, cdrdao will only work on SCSI devices, so you will have some difficulty burning with Disc-at-Once mode if you don't use SCSI emulation.
That said, here's how to enable scsi emulation:
1. Compile it into the kernel.
2. Edit /etc/lilo.conf to include the following line anywhere you like:
append = "hdc=ide-scsi"
Where hdc is the IDE cd burner. You can add as many IDE cd burners as you like on this line; just seperate them with spaces. Eg:
append = "hdc=ide-scsi hdd=ide-scsi"
3. Run /sbin/lilo
4. Reboot the machine
5. Verify that your cd burner is in /dev. It may be /dev/sg0, or it may be located somewhere in /dev/scsi/.
6. Make sure your cd-burning software is configured to use the scsi emulated device (i.e. /dev/sg0) and NOT use the raw IDE device (i.e. /dev/cdrom0).
k3b and cdbakeoven have some trouble dealing with SCSI emulated devices. If things aren't working out, use xcdroast instead.
Thanks for the advice, John.
On my machine, k3b and cdbakeoven perform some complex ritual of looking into /dev/sg, making lots of simlinks, and modifying fstab - after which they still don't recognize my CD burner as a valid SCSI device. Xcdroast just works. And since Xcdroast still has more burn related features than k3b and cdbakeoven, I haven't had the patience to manually configure either of the latter.
But regardless of what burning software you use, John is right: it is important to make sure that software looks at the SCSI device and not the IDE device, otherwise strange errors may happen!