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.
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;
~#cd /downloadisolocation #cdromiso.iso cdromiso.md5
~#md5sum -c cdromiso.md5 #substitute the correct name to check
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!
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.
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.
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.
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' :
~# ls -al /dev/dvd
lrwxrwxrwx 1 root root 3 2010-09-25 07:46 /dev/dvd -> sr0
~# ls -al /dev/cdrom
lrwxrwxrwx 1 root root 3 2010-09-25 07:46 /dev/cdrom -> sr0
~# ls -al /dev/sr0
brw-rw---- 1 root cdrom 11, 0 2010-09-25 07:46 /dev/sr0
~# 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
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:
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 :-)
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`:
[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
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...
Last edited by GrapefruiTgirl; 09-27-2010 at 09:18 AM.
Reason: tiny typo