Why I used cdrecord from the CLI and no GUI
Back when I was still amongst the uninformed masses and still using wimpdoze it took nearly all of my processor and RAM to burn a cd. Now, running X but not using a GUI for cdrecord I use about 0.3% of my cpu and a total of 2.2% of my RAM! Is wimpdoze a resource hog or WHAT?
Learning to use the CLI to record discs is not that hard. There are all sorts of tutorials but one of my favorites is here
They give plenty of examples too. Also check out Dave Bechtels page of tips page.
He has listed some good examples for burning cd's and copying floppies.
Remember: you can always use the -dummy option w/ cdrecord and not burn any coasters. Don't forget to look at cdrdao, cdda2wav, readcd, and mkisofs.
In case you weren't aware, these programs I have just listed are what GUI's like Xcdroast and K3b use to burn a disc it's just that with a GUI you get a nice pretty screen to look at. Keep this is mind: in the time it takes you to configure one of these you could have already burned your disc from the CLI. ;)