Jump to content
  • Announcements

    • spinynorman

      Mandriva Official Documentation

      Official documentation for extant versions of Mandriva can be found at doc.mandriva.com.   Documentation for the latest release may take some time to appear there. You can install all the manuals from the main repository if you have Mandriva installed - files are prefixed mandriva-doc.
    • paul

      Forum software upgrade   10/29/17

      So you may have noticed the forum software has upgraded !!!
      A few things that have changed. We no longer have community blogs (was never really used) We no longer have a portal page.
      We can discuss this, and decide whether it is needed (It costs money) See this thread: Here
Sign in to follow this  
static

IM-11: Copying & Burning CD

Recommended Posts

Browse: [About the FAQ Forum] [Table of Contents] [FAQs] [Contribute]

 

IM-11: Copying & Burning CD's with K3b

 

This How-to covers the steps to take to setup K3b to allow you to use K3b as a user (instead of root) to copy cd's from one drive to another, and burn data or audio cd's from files on your harddrive. The emphasis is on the setup, not how to use it.

 

Prelim: Burners like to be the master device on your ide cable (flat, grey data cable) just like the harddrive you boot from. This guide assumes your harddrive is master on the primary ide (/dev/hda) and that your burner is master on the secondary ide (hdc). If you have another cdrom or dvdrom drive, it should never be on the same ide cable as the burner, thus leaving /dev/hdb (primary slave, same cable as your harddrive) for it (your reader device). Note that all drives use a little jumper to know whether they are master or slave. Also note that masters go at the end of the ide cable (furthest from the motherboard) and slaves go in the middle. If you have any questions, don't be afraid to post. If everything worked ok in wino-dows, chances are you'll be fine. Most errors when copying a cd come from the reader being on the same ide cable as the burner.

The primary master is hda & slave is hdb; the secondary master is hdc & slave is hdd.

 

Sections Overview

  • Setting up Reader Device
    • Modifying /etc/lilo.conf or /boot/grub/grub.conf
       
    • Changing /dev/cdrom symlink
       
    • Modifying /etc/fstab

    [*]Running the K3b Setup as root

1. Setting Up Reader Device

Note: You can skip to section #2 if a) you only have one drive (I assume a burner or you wouldn't be reading this) or B) you don't want to ever burn from one drive to another

 

a) Modifying /etc/lilo.conf or /boot/grub/grub.conf

The first thing we will do is edit /etc/lilo.conf (the default bootloader) or /boot/grub/grub.conf (if you specifically chose to use the grub bootloader instead of the default lilo). We do this because we wish to tell the kernel at boot time to use scsi emulation for the reader device.

Open a terminal (konsole, RXvt, eterm, xterm, etc..)

 

For lilo

$ su

Enter Password: [enter root password]



# vi /etc/lilo.conf

Under the "Append" section for booting mandrake, you should see hdc=ide-scsi. Hit 'i' to enter Insert mode and add hdb=ide-scsi so that it now looks like this:

hdc=ide-scsi hdb=ide-scsi

Now hit ESC to leave Insert mode, and type :wq to write changes & quit. Send your changes to the boot record by typing "lilo". Reboot by typing "reboot"

 

For Grub

$ su

Enter Password: [enter root password]



# vi /boot/grub/grub.conf

On the "kernel" line for booting mandrake, you should see hdc=ide-scsi. Hit 'i' to enter Insert mode and add hdb=ide-scsi so that it now looks like this:

kernel (hd0,1)/boot/vmlinuz hdc=ide-scsi hdb=ide=scsi other_stuff_untouched_by_your_meddling

Now hit ESC to leave Insert mode, and type :wq to write changes & quit. Reboot by typing "reboot"

 

Everybody

When mandrake boots back up, a wizard should detect that an ide drive has been removed and a new scsi drive has been installed. If you like wizards doing it all for you, accept all the guff it gives ya and log back in - skip to section #2. If you'd prefer to do it by hand to know your system better (and it's two short steps anyway), cancel the wizard changes and read parts b and c. I recommend doing by hand because if something fails to work you can post exactly what you changed and we can easilier help you - not that easilier is a word, but you get the picture.

 

B) Changing the /dev/cdrom symlink

Chances are you have a soft link /dev/cdrom pointing to /dev/ide/host0/bus0/target0/lun0/cd (where your reader was). We'll need to change that because as far as linux is concerned, your reader is now aboard the scsi train, not ide. Do as many "ls" and "ls -la" commands as it takes to find what we're looking for on your machine.

$ su

Enter Password: [enter root password]



# cd /dev

# ls -la cd* 

[analyse the ls output to see where your cdrom and cdrom2 links are pointing. cdrom2 should be the flashing, broken one. We want to fix the broken one]

# rm cdrom

# ln -s /dev/scsi/host0/bus0/target0/lun0/cd ./cdrom

[if you watch dvd's, or would like to eventually with your dvd drive, there's one more - check to see if you have a dvd link already]

# ls -la dvd

# rm dvd (if it's there)

# ln -s /dev/scsi/host0/bus0/target0/lun0/cd ./dvd

 

Fhew! That was easy... as long as you were careful to find the right stuff.

Now anything that was looking for /dev/cdrom still sees the same drive. One more step before we reboot:

 

c) Modifying /etc/fstab

/etc/fstab is the "filesystem table" of where your kernel should mount which filesystems. It typically wants to mount /dev/cdrom to /mnt/cdrom, /dev/cdrom2 to /mnt/cdrom2, and so on.

$ su

Enter Password: [enter root password]



# vi /etc/fstab

 

It should look something like this:

/dev/hda2 / reiserfs noatime,notail 1 1

/dev/hda3 swap swap defaults 0 0

none /dev/pts devpts mode=0620 0 0

none /mnt/cdrom supermount dev=/dev/hdb,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

none /mnt/cdrom2 supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0

/dev/hda1 /mnt/win_c ntfs iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hda5 /mnt/win_d vfat iocharset=iso8859-1,codepage=850,umask=0 0 0



none /proc proc defaults 0 0

We want the /mnt/cdrom line's dev=/dev/hdb to now be /dev/cdrom instead... change that as root of course, just like above (& don't forget to :wq to write changes before quitting). Then reboot by typing, yep, you guessed it, "reboot".

 

2. Running the K3b Setup as root

Once logged back in, open up your prefered terminal. We will now run the k3b setup.

$ su

Enter Password: [enter root password]



# k3b

The setup window should pop up. You can "Next" your way through it, but remember to set the proper max write speed for your burner to get the quickest burn. Be sure you add you user to the list of users who are allowed to use k3b. Allow k3b to edit your fstab so that it can add these two lines:

/dev/scsi/host0/bus0/target0/lun0/cd   /mnt/cdrom/   auto   ro,noauto,user,exec   0 0 

/dev/scsi/host0/bus0/target1/lun0/cd   /mnt/cdrom2/  auto   ro,noauto,user,exec   0 0

Exit k3b when it opens up after the setup dialog (because you're still root and you won't be running it as such). Now open it again as your user, and in the menu at the top there is a k3b - Configuration (as opposed to Setup). Quick scan through that to set your options/preferences for your user and you're done!

Edited by Ixthusdan

Share this post


Link to post
Share on other sites
Sign in to follow this  

×