In this way, let Linux mental tenet, I will migrate all the data from the original Windows2000 server to all the services provided to the new Linux server. When I am about to throw this old windows2000 server to a dark small corner, I'm bright, and I suddenly found that there is another Sony CD burner on this broken machine. I have always had to take it to the habit of being discarded, turned into treasures, so I naturally I can't let go of this good stuff. How do I use a burner under Linux? I also searched online database, and I have not found a more effective and comprehensive textbook. Under the helplessness, only one person can be shaped. When I took the 7th cigarette, a string of Success finally appeared on the screen. I am surprised, screaming loudly, scare the old brother who is gourmet, the finger is shaking, a big fat is on the ground. This brother is heartbroken, gnow me, and swear up to the sky: I will take my head in my item in three days, I will never lose words, otherwise ... This and after, I will no longer say, enter our theme. Hardware Environment: CPU: Inter Pentium2 400 MEM: 384MB CDROM: ASUS CDR: SONY Software Environment: OS: Redhat 7.0 Kernel: 2.2.16 The most famous tool for implementing disc burning under Linux is CDRecord. In fact it is a kit, including CDREOCRD, MKISOFS, CDDA2WAV. DDA2WAV is for burning AUDIO CDs, not within the scope of this article. We focus on explaining CDRecord, Mkisofs usage to use how to configure SCSI and IDE devices. Many graphical interface CD burning software is actually called CDRecord, which we can find in www.linuxByte.NET and download them. In the Linux system, CDRecord works with the SCSI generic device. I think most of the readers are all IDE disc burners, so the key to configuring the IDE device into SCSI devices. To play IDE devices into SCSI devices, the system kernel must support Atapi-SCSI Emulation or SCSI Host Adapter Emulation. If your system kernel is not so configured now, then you need to recompile the kernel and upgrade it. Fortunately, this Linux version used in my hand has been supported by default. The first step, we should know which one of our CD-ROMs and the burner correspond to Ide, which device name is used under Linux. Because we want to let the system kernel know which devices need to simulate into SCSI devices, we have to deliver some parameters to the system kernel. The specific practices are as follows: Edit the lilo.conf file, add a line of parameters to the Linux boot module. Append = "HDB = IDE-SCSI HDD = IDE-SCSI" executes a libo command for backup operation. HDX refers to the IDE device name corresponding to the optical drive or burner in Linux. If you intend to direct disc data directly to direct burn, you need the above two fields because CDRecord requires two devices to be SCSI interfaces when reading and writing data. But if you are just through Mr. ISO intermediate file, then burn this form, just specify one of the fields. As follows: append = "HDD = IDE-SCSI"
In the second step, when the reboot system is completed, we need to do the two kernel drive modules to the IDE-SCSI to the system core and set the SCSI device name for them. SG refers to the SCSI device driver module, and IDE-SCSI refers to an IDE device to touch the SCSI device driver module. The operation is as follows: MODPROBE SG MODPROBE IDE-SCSI executes these two operations, we execute the lsmod command, query the system kernel has loaded module information, verify the results of our operation, display information as follows: Module Size Used by IDE-SCSI 7336 0 (autoclean) sg 15704 0 (unused) vfat 9404 0 (autoclean) (unused) fat 30688 0 (autoclean) [vfat] soundcore 2596 0 (autoclean) (unused) autofs 9124 1 (autoclean) lockd 31176 1 (autoclean) sunrpc 52964 1 (AutoClean) [LOCKD] 3C59X 19844 1 (AUSED) USB-UHCI 19052 0 (unused) USBCORE 42088 1 [USB-UHCI] After performing the above operation, we can check the kernel data image file, Get more detailed information, the most important thing is the ID number of the IDE simulation device corresponding to the SCSI device. Cat / proc / scsi / scsi ------------------------------------------- ------------------------ Attached Devices: Host: SCSI0 CHANNEL: 00 ID: 00 LUN: 00 VENDOR: ASUS Model: CD-S400 / A REV : 2.0S Type: CD-ROM ANSI SCSI REVISION: 00 ID: 01 LUN: 00 VENDOR: SONY MODEL: CD-RW CRX100E REV: 1.0M Type: CD-ROM ANSI SCSI REVISION: 02 Of course, Your display may vary, but the form should be the same. The system has already recognized the SCSI devices we simulated, but we still have to provide SCSI device names to map them so that the burning software can be used. When the kernel system is loaded, the / dev / sg0, / dev / sg1 is automatically established with our equipment. Now you can use the SCSI_INFO command to view the SCSI device information. SCSI_INFO / DEV / SG0 --------------------------------------------- ------------------ SCSI_ID = "0,0,0" model = "ASUS CD-S400 / A" FW_REV = "2.0s" SCSI_INFO / DEV / HDD - -------------------------------------------------- ----------- SCSI_ID = "0, 1, 0" model = "SONY CD-RW CRX100E" fw_rev = "1.0m" At this time we have applied these devices.
