It really is as simple as: cdrecord -v dev=/dev/sr0 pathtoyourisoimage.iso -v is for verbose, I prefer it but if you don't you won't see as much output like below (I like to know the details and exactly what's happening) dev=/dev/sr0 specifies the device name of your burner (they say not to use it and to specify some weird annoying device string but using the raw /dev has always worked for me and is how it should have been implemented from the start IMHO)........

My Samsung drive failed on me, at first I thought it was the enclosure but a direct SATA connection causes the same problems for discs that are inserted. It will work fine for a few minutes but then starts spewing the errors below. I've never been a fan of Korean made optical drives and have always had trouble with them. The problem is that I don't believe NEC and Lite-ON make drives anymore, and I considered them the leaders. Apr 7 11:58:48 bo........

CDR Manufacturers - Why is so much media bad?I have searched for good media and tried many kinds for years. I guess I'll try to summarize my findings and conclusions. Dye is irrelevant, dye of any color can be good or bad, it more likely depends on the manufacturer. Speaking of manufacturers, the name at the top of the disc means nothing. For example, Memorex along with any other 'brand' is actually always made by another manufaturer including CMC Mag........

This will give you the basic info needed to browse and connect to Samba shares from the command line. From the GUI of Gnome or KDE etc, it is pretty standard and straight forward. However, I've found very little guides on how to do it from the command line and if you're like me, a nerd who prefers command line for its simplicity and for remote use, this is the way to go. First get a list of all the Samba/SMB shares on the target. smbclient -L hostname........