[SOLVED] Burning an image.iso

adenial · 09-26-2010, 07:14 AM

Hi,
I want to burn an iso image.
I have downloaded debian-506-i386-CD-1.iso file and is kept on my Desktop.
I bought a new cd and want to write this file on it.
How should I proceed?

fuubar2003 · 09-26-2010, 07:39 AM

I use 'cdrecord' via cmdline.....http://sharkysoft.com/tutorials/linuxtips/cdcommands/

onebuck · 09-26-2010, 07:41 AM

Hi,

Welcome to LQ!

You should verify the downloaded image! The 'md5sum' or 'hash' is very important to learn to use and too regularly get in the habit of utilizing it. You can get a sum checker for M$ if need be; 'md5sum.exe'.

For GNU/Linux the 'man md5sum' will get you all the information to perform the check. You can get the 'man command from the 'cli' at anytime.

If you downloaded the CD/DVD iso then be sure to check the md5sum for the original ISO. From the cli;

Code:

 ~#cd /downloadisolocation      #cdromiso.iso cdromiso.md5 
 
 ~#md5sum -c cdromiso.md5       #substitute the correct name to check

If the iso md5 is ok then you should try 'CdromMd5sumsAfterBurning''.

This way you will know if the burn was OK!

This will check the download ISO with the known md5sum that you also get with the ISO. You should do the check for any download that you might perform, even a LiveCD. Plus burn the image. Sometimes you may need to lower the burn rate to get a valid burn.

As for a burn application, you haven't specified the OS you wish to use. For a GNU/Linux DE or Desktop you could use 'K3b'. For M$ system then 'Imgburn' is a free application that could be used.

The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

crahuldba@gmail.com · 09-26-2010, 08:22 AM

Hello adenial
If you are using rpm based linux system than you can download RPM for nero and install it in your system
you can download rpm for nero from following link
http://www.nero.com/enu/downloads-linux4-trial.php
and after that install it
rpm -ivh yourfilename.rpm
and after than you can easily burn your cd or dva.
Have a good day.

colucix · 09-26-2010, 09:25 AM

If you're using the GNOME Desktop, you can simply insert a blank CD-ROM in your CD writer, right click on the ISO image and select Write to disc. Then adjust the speed (keep it lower to reduce the chance of errors) and wait for the burning to complete. A previous check for md5sum or sha1sum as suggested by onebuck is a good habit to prevent wastes of CD-ROMs.

Tux Rules · 09-26-2010, 09:43 AM

Brasero for Gnome or other desktops/window managers or k3b for KDE.Or if you have enough space on your HDD you can just mount the iso to behave as a regular cd-rom without writing it to a CD or DVD, if you didn't knew that by now.

blu · 09-26-2010, 12:00 PM

I suggest to use Brasero, is very simple to use it for all ISO images!
Bye!
I am sorry but I don't write well english languages.

frankbell · 09-26-2010, 10:07 PM

The important thing, whatever burner you are using, is to find the menu item for "burn disk from image." If you just copy the image to a CD, all you will have is CD with filename.iso on it.

In KDE, from the menu bar, it's Tools-->Burn disk from image, not File-->New Project.

In Brasero, it's Project-->New Project-->Burn Image.

After burning the CD, mount it and take a look at it. If it contains one file named filename.iso, you need to look around some more.

This is from the "been there done that" department.

MTK358 · 09-27-2010, 07:19 AM

I also suggest Brasero, it's very clean and simple to use.

djsmiley2k · 09-27-2010, 07:21 AM

I like xfburn, as I use xfce4

Very simple gui, with a "burn iso" button.

GrapefruiTgirl · 09-27-2010, 07:23 AM

I prefer the command line, and would do something like this:

Code:

(root)# cdrecord dev=/dev/hdd speed=4 padsize=63s -pad -dao -v -eject /absolute/path/to/debian-506-i386-CD-1.iso

Replace /dev/hdd with your own burning drive.

onebuck · 09-27-2010, 08:24 AM

Hi,

I agree with 'GrapefruiTgirl' about the 'cli' for a guaranteed burn. Most users will work from a DE or Desktop so the suggested apps will work when used properly.

MTK358 · 09-27-2010, 08:37 AM

The problem is that many users might not know the device name of their CD burner.

For example GrapefruiTgirl's CD burner is /dev/hdd according to her post, while mine, for example, is /dev/sr0.

onebuck · 09-27-2010, 08:57 AM

Hi,

Quote:

Originally Posted by MTK358

The problem is that many users might not know the device name of their CD burner.

For example GrapefruiTgirl's CD burner is /dev/hdd according to her post, while mine, for example, is /dev/sr0.

That's why most users don't understand their systems. They are not at the system level with using a GUI, thus unaware of the details. You have a valid point in showing the difference. Why not show them from the 'cli' :

Code:

~# ls -al /dev/dvd  
lrwxrwxrwx 1 root root 3 2010-09-25 07:46 /dev/dvd -> sr0
OR
~# ls -al /dev/cdrom
lrwxrwxrwx 1 root root 3 2010-09-25 07:46 /dev/cdrom -> sr0
OR
~# ls -al /dev/sr0
brw-rw---- 1 root cdrom 11, 0 2010-09-25 07:46 /dev/sr0
AND
~# dmesg |grep -i sr0
sr0: scsi3-mmc drive: 62x/62x writer cd/rw xa/form2 cdda tray
sr 4:0:0:0: Attached scsi CD-ROM sr0

GrapefruiTgirl · 09-27-2010, 09:17 AM

That's true, good point - though even if using a GUI tool, somehow the user must select the burning device.

Perhaps the choice will be obvious on machines where there's only one such device, if the GUI tool allows you to select from a list of devices (a one item list!), but what about when there are 2 or 3 optical drives? Once again the user has to know which is which (which I guess is still better; having a list of 3 options is better than having absolutely no clue).

Seems to me though, and memory can be wrong too, but seems that last time I tried to use some burning GUI app, I had to still select what device I wanted to target, but from a long and confusing list of /dev nodes, so that wasn't much less difficult either.

What to do then, when you want to know which of your drives are which, even if for not burning something, but just to know?
For intending to use `cdrecord`, we can use it again:

Code:

sasha@reactor: cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 2.01.01a78 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2010 J�g Schilling
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
scsibus0:
        0,0,0     0) 'PIONEER ' 'DVD-RW  DVR-212D' '1.24' Removable CD-ROM
        0,1,0     1) *
        0,2,0     2) *
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *
scsibus1001:
        1001,0,0 100100) 'SAMSUNG ' 'CD-R/RW SW-408B ' 'BS02' Removable CD-ROM
        1001,1,0 100101) *
        1001,2,0 100102) *
        1001,3,0 100103) *
        1001,4,0 100104) *
        1001,5,0 100105) *
        1001,6,0 100106) *
        1001,7,0 100107) *
sasha@reactor:

The above works well, assuming one knows that they need to replace the /dev/hdd from my example in post #11, with a 0,0,0 or 1001,0,0 to indicate the correct device. In fact, `cdrecord` gives a warning when you use the /dev/hdd method, claiming it isn't supported - so they expect you to use the format produced by `cdrecord -scanbus` anyhow.

To make sure you have chosen the correct drive, you could eject them (you have to anyway, to put a blank disc in :-)

Code:

root@reactor: cdrecord dev=0,0,0 -eject
root@reactor: cdrecord dev=1001,0,0 -eject

And presto, your drive should eject (and you see a bunch of stuff you can ignore, on your terminal window).

How I initially figured out that my (at the time) optical drives were /dev/hdc and /dev/hdd I cannot remember. I might have used `lshw` or a similar thing.. One of mine show up using `lsscsi`:

Code:

root@reactor: lsscsi
[0:0:0:0]    cd/dvd  PIONEER  DVD-RW  DVR-212D 1.24  /dev/sr0 
[4:0:0:0]    disk    Generic  USB SD Reader    1.00  /dev/card-reader-SD
[4:0:0:1]    disk    Generic  USB CF Reader    1.01  /dev/card-reader-CF
[4:0:0:2]    disk    Generic  USB SM Reader    1.02  /dev/card-reader-SM
[4:0:0:3]    disk    Generic  USB MS Reader    1.03  /dev/card-reader-MS
root@reactor:

But the other one's /dev/hdc and I can't think of a command that would show me (just) optical drives of that type, without a lot of clutter...