How to copy directory tree to cd rom using command line?
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.
BTW- when I tried to apt-get mkisofs I get this message:
Package mkisofs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
genisoimage is part of the wodim package. I'm running Debian.
I guess I need a basic _recent_ tutorial on how to do this. All the web pages I have read confuse me with discussion of iso files, images, DVD's, past versions of software, etc.
Last edited by keithostertag; 03-13-2013 at 02:56 PM.
Growisofs isn't exactly to be used against a CD-ROM. It might work if the CD format is not "finished" (an end marker record is written). You can't overwrite a CD that way very well.
Usually I've seen it used against an ISO file on disk (thus modifiable), but not on a CD. Once the ISO file is updated, a CD might be written (or overwritten if CD-R+).
Part of the problem with unfinished CD recordings is that some systems will claim an I/O error, and not process the CD at all. The problem with finished CDs is that they are marked complete, and can't be extended...
I didn't want to load a gui, I do this so seldom. I only had 155M of data I wanted to copy to cd. There are lots of examples to copy to DVD, but not to cdrom.
For me, who doesn't do this very often, the documentation is confusing. I looked through the man pages for burn, wodim, mkisofs, genisoimage, etc. Most of the docs discuss audio and creating iso images, and mostly in reference to DVD's. The terminology is confusing to someone who doesn't do this a lot or in depth.
Note the device numbers. They mean crazy things to a strange man but you don't have to worry about that. Let's say, for example, your cd is on 1,0,0
cdrecord dev=1,0,0 speed=4 -eject filename.iso
I always limit speed to limit errors as faster writing causes more errors. Take it from someone who has run BLER (Block Error) tests on real cds and cdrs. The eject spits it out when you're finished. If you want a dry run, there's an option for that also.
Thanks. Even though I didn't use your choice of apps, I learned something from your post :-)
Here's part of what was tripping me up. I had thought that if I created an iso or raw file out of a bunch of files in a directory, that it creates one big file (it does). And that I'd wind up with one iso file on the cdrom, not a directory tree of files where I could, say, read or copy just one of them (later from the created cdrom).
Now that I've tried it I see I was mistaken.
Here's what I did (after changing to the directory I wanted to copy):
$ genisoimage -R -o cdimage.raw ./
$ wodim -v speed=2 dev=1,0,0 cdimage.raw
It didn't actually like using dev=1,0,0 and gave a warning, but worked. I now guess I should just use 1,0 or /dev/sg1.
Finished, then mounted the cdrom, I feared I would see one big file on the cdrom- cdimage.raw. But instead I get the directory tree of files that I wanted to copy. I didn't realized it worked that way. Shazzam!
The original guy who wrote that uses Solaris and [B]hates[B] glibc. Everybody who comes along after returns to convention "This is dvdrtools, not dvdlibc." "Returned the source to standard build procedure." are typical comments in READMEs.
It references /dev/pg* and /dev/sg* but often they're not made :-/.