Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
# CD burning info
Is it configured and what is the device? Command this to find out:
cdrecord -scanbus Adding an IDE CD-Writer to Linux CD Writing HOWTO Burning CDs on Linux
# Burn an ISO to disk
cdrecord -v speed=<burning speed> dev=<your device> /path/to/foo.iso
# Burn from disk to disk
cdrecord -v dev=<your device> speed=<burning speed> -isosize /dev/cdrom
# Generate an ISO from a directory.
mkisofs -Jr -o foo.iso /path/to/directory
mkisofs -vrTJUV "Label" -o foo.iso /path/to/directory
# Generate an ISO from a CD
dd if=/dev/cdrom of=foo.iso Linux MP3 CD Burning mini-HOWTO
# Convert mp3 to wav with lame
for i in *.mp3; do lame --decode $i `basename $i .mp3`.wav; done
# Burn a CD from wav files
cdrecord -v -audio -pad speed=<burning speed> dev=<your device> /path/to/*.wav
# Erase a CDRW
cdrecord -v dev=<your device> speed=<burning speed> blank=fast
And what if you want to burn multiple files from multiple directories or resourses? You'd spend half the day typing and I'd have my files dragged and dropped and burned on a CD and gone fishing by the time you got done typing all that stuff. GUI's were invented to make our lives easier.
Distribution: Gentoo, Debian, Ubuntu, Red Hat/CentOS
Originally posted by mooreted Why on earth would you want to type out all this:
well some of us actually prefer the command line, but you are right that the gui can make lives less complicated and I do use it at times. The point fancy is trying to make is that most gui apps are just a pretty picture on top of very powerful CLI tools. By getting comfortable with the real programs one can configure and command a great deal more from a tool. If you learn how to use cdrecord you will be at home on any *nix computer and you'll also learn a bit more about what makes it tick. When I am feeling lazy I use xcdroast. Although it has screwed me a few times when burning .iso's It is not supposed to be all that friendly, but I had to read a lot more docs when I used to use nero that I ever did with xcdroast. Try it - disks are cheap
copy/paste and using the up arrow (bash history) are extremely easy in Linux.
If I haven't used a command I want recently (up arrow goes through your last commnads) I have a text file with my handiest commands. I paste them into an x terminal and edit it with the exact path , etc. I want and then press enter. It usually is much faster than remembering a sequence of clicks needed to do it for me. I love ease of use and user friendliness.
Why hide the hammer so that you can't see the nail with a GUI?
Last edited by fancypiper; 08-29-2003 at 02:04 PM.
Well, I was mostly just messing with you but now I'll have to try cdrecord from the command-line so I have a legitimate bitch later. Can't really talk about what I haven't tried. But K3b is still really nice. My problem is that I'm at college 13 hours a day. School sure is messing with my Linux experience.
It seems like it would be easier to just drag and drop the files where they need to go. That's a lot of typing and not even a tenth of all the folders I have on my two drives and every folder has a bunch of subfolders. It seems like I would have to spend the day typing.
Originally posted by fancypiper Too much typing! I would alias that as "burn"
as of you mooreted, i agree that is alot of typing, but if that is a frequent command that you would issue alot, then you could just make it a script, and just run: ./scriptname
and all that will be executed...so again, you would only have to type that command once, and make it ease with a script...
Right, and for my static directories I do have a script. But you can see that the CLI also has it's limitations. There are many tools used in computing and the GUI is one of them. I believe in using all the useful tools at my disposal.
Boy, did this discussion get off the track.
Try K3b, if it's not working let us know what's wrong and we can help you fix it.