CD burning for dummies
Charlie Gibbs
I've tried looking at the CD-Writing-HOWTO and it's pretty daunting.
Plus, 2.6 doesn't seem to be ready for prime time; when I run
cdrecord -scanbus I get the following:
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
Linux sg driver version: 3.5.33
Using libscg version 'schily-0.8'.
scsibus0:
0,0,0 0) 'ATA ' 'WDC WD2000JS-00M' '02.0' Disk
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
scsibus2:
2,0,0 200) 'Generic ' ' CF' '1.6E' Removable Disk
2,1,0 201) *
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) *
The first entry is the 200GB SATA drive I use for /usr/local and /home.
I'm not sure just what's appearing under the "scsibus2" heading -
on my IDE interface is a 4GB hard drive as primary master (boot, swap,
and /), and a DVD-ROM and DVD writer as secondary master and slave.
The CD/DVD drives can be mounted and read as /dev/hdc and /dev/hdd -
in fact, by typing "mplayer dvd://1" as root I can view a DVD even
without mounting it. So I don't think there's anything wrong with
my hardware.
Is it just because I'm stubbornly insisting on trying to use a version
of Linux that doesn't have all the bugs out yet? Or are there other
problems that have yet to be resolved? For now, if I want to burn a
CD or DVD, I FTP the files over to a Windows box, where burning CDs
and DVDs is as easy as dragging and dropping files. But it seems a
shame to have that shiny new dual-layer DVD burner sitting there in
my Linux box doing nothing.
Unless I'm missing someething obvious, the state of CD burning under
Linux is about where X configuration was five years ago. And that's
too bad, because it means that I can't yet sell Linux to Windows
vict^H^H^H^Husers who want to burn CDs.
--
/~\ cgi...@kltpzyxm.invalid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
AZ Nomad
>Is there a quick and easy guide to burning CDs and DVDs under Linux?
>I've tried looking at the CD-Writing-HOWTO and it's pretty daunting.
>Plus, 2.6 doesn't seem to be ready for prime time; when I run
>cdrecord -scanbus I get the following:
If you're a dummy, then go with a gui cd burning program such as
k3b.
Rolf-Arne Schulze
> Unless I'm missing someething obvious, the state of CD burning under
> Linux is about where X configuration was five years ago. And that's
> too bad, because it means that I can't yet sell Linux to Windows
> vict^H^H^H^Husers who want to burn CDs.
I just pop an empty cd in my cd-burner and gnome asks what I want to do
with it. If I choose to make a data cd, a file manager window appears
and I drag the files I want to burn into that windows. When I have
composed the cd, I press "Write to disc".
If I have downloaded a cd image, I open my "home folder" in the file
manager (nautilus). I navigate to find the iso file, right clicks on it
and selects "write to disc".
I see where this is very hard and almost like configuring X 5 hears
ago. NOT!
If you want a more nero like approach, you can use k3b or any other cd
burning application.
--
Rolf-Arne Schulze
Min Weblog: http://rolfas.net/
S.Brown
news:2474.291T2...@kltpzyxm.invalid:
> snip
> scsibus2:
> 2,0,0 200) 'Generic ' ' CF' '1.6E' Removable
> Disk 2,1,0 201) *
> 2,2,0 202) *
> 2,3,0 203) *
> 2,4,0 204) *
> 2,5,0 205) *
> 2,6,0 206) *
> 2,7,0 207) *
So what do your boot messages say? Is that removable disk how your CD/DVD
drive(s) are id'ed? Or is it something on another interface, like usb?
> The first entry is the 200GB SATA drive I use for /usr/local and
> /home. I'm not sure just what's appearing under the "scsibus2" heading
> - on my IDE interface is a 4GB hard drive as primary master (boot,
> swap, and /), and a DVD-ROM and DVD writer as secondary master and
> slave. The CD/DVD drives can be mounted and read as /dev/hdc and
> /dev/hdd - in fact, by typing "mplayer dvd://1" as root I can view a
> DVD even without mounting it. So I don't think there's anything wrong
> with my hardware.
Oh well. I could easily _anything_ I hooked up under 2.4.x as a normal
optical drive. If this were under 2.4 I'd say you hadn't set up the ide-
scsi module to use that drive. Quick googling shows that we would
definitly need the ide-cd module...but you're using the drive(s) as ro, so
we should be good....
> Is it just because I'm stubbornly insisting on trying to use a version
> of Linux that doesn't have all the bugs out yet? Or are there other
> problems that have yet to be resolved? For now, if I want to burn a
> CD or DVD, I FTP the files over to a Windows box, where burning CDs
> and DVDs is as easy as dragging and dropping files. But it seems a
> shame to have that shiny new dual-layer DVD burner sitting there in
> my Linux box doing nothing.
>
> Unless I'm missing someething obvious, the state of CD burning under
> Linux is about where X configuration was five years ago. And that's
> too bad, because it means that I can't yet sell Linux to Windows
> vict^H^H^H^Husers who want to burn CDs.
I call bullshit. Sorry. The same quick googling that informs me that Mr.
Schilling (who as I recall isn't a x86 user unless he has one of those
newer opteron boxes from Sun) doesn't exactly like the newer, 2.6ish method
of dealing with ATAPI burners showed me the relevant module and had another
forum article that said straight out that you can use your regular device
name (say /dev/hdc for the SM on the ide channel...) instead of the older
dev=<bus>,<device>,<lun>. So all that has changed is how you refer to some
devices.
If you'd like, here is the relevant article I found
http://forums.debian.net/viewtopic.php?t=161
Only daunting thing I can see in that article is figuring what the device
name is for my burner...
As for the gui approach, use it if you have a phobia against the command
line, however cdrecord & growisofs are quite enough. I forgive Mr.
Schilling for his opinion, fill in the gaps it leaves, and go on.
--
There is nothing life threatening about man pages.
IRS forms, however, are a different story.
jakob
> The CD/DVD drives can be mounted and read as /dev/hdc and /dev/hdd -
You can actually burn using these names instead, though you'll get a
nasty warning. It's never caused me any problems:
# cdrecord dev=/dev/hdc ...
jakob
Charlie Gibbs
azn...@PmunOgeBOX.com (AZ Nomad) writes:
I figured there had to be an application out there - there is for
just about everything else. Download, build, drag & drop, burn -
works like a charm. Thanks for the pointer.
s. keeling
> Is there a quick and easy guide to burning CDs and DVDs under Linux?
> I've tried looking at the CD-Writing-HOWTO and it's pretty daunting.
> Plus, 2.6 doesn't seem to be ready for prime time; when I run
> cdrecord -scanbus I get the following:
>
> Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
> cdrecord: Warning: Running on Linux-2.6.13
This is good. 2.6.x kernels don't need the scsi module hacks. You
can burn directly to /dev/hdN
[Note, Jorg and Linux kernel developers have been engaging in somewhat
of a vendetta for some time.]
(0) infidel [root] /root_ mkisofs -o /scratch/iso/track_01.img \
-pad -allow-leading-dots -max-iso9660-filenames \
-r -relaxed-filenames /scratch/afio
(0) infidel /home/keeling_ cdrecord speed=8 dev=/dev/hdc -eject \
-tao -data /scratch/iso/track_01.img
--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://www.spots.ab.ca/~keeling Linux Counter #80292
- - Spammers! http://www.spots.ab.ca/~keeling/emails.html
http://www.ietf.org/rfc/rfc1855.txt
Charlie Gibbs
INV...@bellsouth.net (S.Brown) writes:
> If you'd like, here is the relevant article I found
> http://forums.debian.net/viewtopic.php?t=161
> Only daunting thing I can see in that article is figuring what the
> device name is for my burner...
Thanks for that reference. It clears up a lot. I think where the
"daunting" part comes in is because I've never seen a CD-burning
procedure that's anything more than selecting some files and telling
the program to burn them. I've never seen under the hood, and all
of a sudden I find myself in a world of .iso files (which I still
don't understand) and multiple steps to manually do what I've always
seen done automatically. I've been thinking in terms of just another
filesystem, but I don't think we're in Kansas anymore, Toto.
> As for the gui approach, use it if you have a phobia against the
> command line, however cdrecord & growisofs are quite enough. I
> forgive Mr. Schilling for his opinion, fill in the gaps it leaves,
> and go on.
I'm no GUI fanatic, and I _definitely_ don't have a command-line
phobia. In fact, I recently replaced QuickPAR and WinRAR on my
Windows box with par2verify/par2repair and unrar under Linux,
and I find it much easier.
As for burning CDs, a drag-and-drop interface is awfully seductive,
at least in my present state of ignorance. I _like_ to know what's
going on inside - but I found my initial probes into man pages and
Google to be rather intimidating. Which is why I'm posting here.
Once I understand the nuts and bolts, I'll probably be happily
burning CDs from a command line like the rest of you. But not yet -
it seems it'll take some study, and more time than I have available
at the moment.
In any event, thanks, everyone, for your help. If someone could
point me to a description of the basics of the CD-burning process,
what ISO files are all about, etc., that should be enough to set
me on the road to enlightenment.
Nico Kadel-Garcia
"Charlie Gibbs" <cgi...@kltpzyxm.invalid> wrote in message
news:2248.291T21...@kltpzyxm.invalid...
Much of it is in the "cdrecord" program, which is what the GUI's in Linux
actually use to burn CD's, and the "mkisofs" program, that can actually make
ISO images from bundles of files.
Remember that the various CD formats are built by committees from different
industries: they picked certain features to make things easy for their own
purposes, but people have tweaked them since to provide better handling of
long filenames, the ability to read the CD's on older operating systems,
etc. But there are still things that will never work will due to the
built-in limitations: I dare you to try to make an ISO from a Maildir
directory without bundling it up into a tarball first.
Rick Moen
> In article <rKGdndSUF4v8I5HZ...@giganews.com>, matachin-
> INV...@bellsouth.net (S.Brown) writes:
>
>> If you'd like, here is the relevant article I found
>> http://forums.debian.net/viewtopic.php?t=161
>> Only daunting thing I can see in that article is figuring what the
>> device name is for my burner...
>
> Thanks for that reference. It clears up a lot. I think where the
> "daunting" part comes in is because I've never seen a CD-burning
> procedure that's anything more than selecting some files and telling
> the program to burn them. I've never seen under the hood, and all
> of a sudden I find myself in a world of .iso files (which I still
> don't understand) and multiple steps to manually do what I've always
> seen done automatically. I've been thinking in terms of just another
> filesystem, but I don't think we're in Kansas anymore, Toto.
Unix-ey people like modular functionality, for lots of reasons. But
your answer basically is k3b -- plus awareness of the fact that ATAPI
addressing for CD/DVD-writing purposes has historically been a small
mess on Linux, made somewhat worse by cdrecord author Jorg Schilling
having a somewhat hostile attitude. (Some people like certain other X11
front-ends other than k3b, notably Nautilus and gCombust. Me, I'm a
dinosaur and prefer mkisofs/cdrecord.)
Personally, some years ago made almost all of this go away by going SCSI
with my CD burner (a lovely old Plextor). Which apparently won't be an
option with DVD burners, alas. That world's rapidly going SATA.
Here, this page is a little antique, but you might find it useful:
http://www.yolinux.com/TUTORIALS/LinuxTutorialCDBurn.html
--
Cheers,
Rick Moen Support your local medical examiner: Die strangely.
ri...@linuxmafia.com
iforone
Charlie Gibbs wrote:
> Thanks for that reference. It clears up a lot. I think where the
> "daunting" part comes in is because I've never seen a CD-burning
> procedure that's anything more than selecting some files and telling
> the program to burn them. I've never seen under the hood, and all
> of a sudden I find myself in a world of .iso files (which I still
> don't understand) and multiple steps to manually do what I've always
> seen done automatically. I've been thinking in terms of just another
> filesystem, but I don't think we're in Kansas anymore, Toto.
this is what I get after issuing cdrecord -scanbus (as SuperUser/Root
(sudo = SuperUser Do, basically), since I'm always/mostly logged on as
an unprivileged user)
~$ sudo cdrecord -scanbus
Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004
Jörg Schil
ling
NOTE: this version of cdrecord is an inofficial (modified) release of
cdrecord
and thus may have bugs that are not present in the original
version.
Please send bug reports and support requests to
<cdrt...@packages.debian.
org>.
The original author should not be bothered with problems of this
version.
cdrecord: Warning: Running on Linux-2.6.8-2-386
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or
Solaris.
cdrecord: Warning: Linux-2.6.8 introduced incompatible interface
changes.
cdrecord: Warning: SCSI transport does no longer work for suid root
programs.
cdrecord: Warning: if cdrecord fails, try to run it from a root
account.
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot
open SCSI dr
iver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
cdrecord:
cdrecord: For more information, install the cdrtools-doc
cdrecord: package and read /usr/share/doc/cdrecord/README.ATAPI.setup .
Have a look at ;
file:/usr/share/doc/cdrecord/README.ATAPI.setup
(paste that into your browser location/address bar)
as noted within that document;
~$ sudo grep hd.: /var/log/kern.log
will yield some nice info about your IDE/ATA devices
Also;
~$ dmesg | grep -i hd
and perhaps
~$ dmesg | grep -i sd
> I'm no GUI fanatic, and I _definitely_ don't have a command-line
> phobia. In fact, I recently replaced QuickPAR and WinRAR on my
> Windows box with par2verify/par2repair and unrar under Linux,
> and I find it much easier.
After burning an ISO using k3b, one id offered to Save the burn
session/settings(?) -- here's what's at the end of one of those text
files;
cdrecord comand:
-----------------------
/usr/bin/cdrecord.mmap -v gracetime=2 dev=1,0,0 speed=32 -dao
driveropts=burnfree -eject -data
it would seem; in this way, you can burn a CD/DVD using a front-end
like k3b, then take a look at the underlying cdrecord command that was
used to actually do the burn.
Charlie Gibbs
(Rick Moen) writes:
> Unix-ey people like modular functionality, for lots of reasons. But
> your answer basically is k3b -- plus awareness of the fact that ATAPI
> addressing for CD/DVD-writing purposes has historically been a small
> mess on Linux, made somewhat worse by cdrecord author Jorg Schilling
> having a somewhat hostile attitude. (Some people like certain other
> X11 front-ends other than k3b, notably Nautilus and gCombust.
k3b seems to be doing the job for me for the time being.
> Me, I'm a dinosaur and prefer mkisofs/cdrecord.)
I'm sure I'll get there eventually. But the man page for cdrecord
contains a list of command-line parameters that goes on and on,
without an indication of which ones are essential and which are
obscure. I'm sure it all makes sense once you figure it out, but
at first glance it's quite intimidating.
> Here, this page is a little antique, but you might find it useful:
> http://www.yolinux.com/TUTORIALS/LinuxTutorialCDBurn.html
Thanks for the pointer. Maybe that'll help me sort things out.
Rick Moen
>> Me, I'm a dinosaur and prefer mkisofs/cdrecord.)
>
> I'm sure I'll get there eventually. But the man page for cdrecord
> contains a list of command-line parameters that goes on and on,
> without an indication of which ones are essential and which are
> obscure. I'm sure it all makes sense once you figure it out, but at
> first glance it's quite intimidating.
Ja, I hear you. What I tend to do is figure it out once, and then put
all that junk in a shell script, so I don't have to remember...
mkisofs -o foo.iso -r -J -T -v bar/
and
cdrecord -dev=1,0.0 -v foo.iso
Also, in the case of cdrecord, you can just tuck it away in
/etc/cdrecord.conf. (And yes, that cdrecord manpage is infamously
overdetailed, but once you've sorted out just how much is irrelevant,
the above is about all you ever need -- and that's _without_
cdrecord.conf.)
How did I know to use "-dev=1,0.0"? From a handy lazy-man's delight
called "cdrecord -scanbus".
Steve Welsh
> Is there a quick and easy guide to burning CDs and DVDs under Linux?
[snip lots of stuff]
xcdroast works just fine for me - used it on three different boxes with
no problem.
It's not as intuitive as, say, Nero but once you get to the Linux way of
doing it (first select the files, then create the master ISO image, then
tell it that that is the image you want to burn) the burning process
works perfectly - well, it does for me.
That's for CDs - dunno about DVDs, but I suspect similar.
Cheers,
Steve
Charlie Gibbs
ri...@linuxmafia.com (Rick Moen) writes:
> Charlie Gibbs <cgi...@kltpzyxm.invalid> wrote:
>
>>> Me, I'm a dinosaur and prefer mkisofs/cdrecord.)
>>
>> I'm sure I'll get there eventually. But the man page for cdrecord
>> contains a list of command-line parameters that goes on and on,
>> without an indication of which ones are essential and which are
>> obscure. I'm sure it all makes sense once you figure it out, but at
>> first glance it's quite intimidating.
>
> Ja, I hear you. What I tend to do is figure it out once, and then put
> all that junk in a shell script, so I don't have to remember...
>
> mkisofs -o foo.iso -r -J -T -v bar/
>
> and
>
> cdrecord -dev=1,0.0 -v foo.iso
>
> Also, in the case of cdrecord, you can just tuck it away in
> /etc/cdrecord.conf. (And yes, that cdrecord manpage is infamously
> overdetailed, but once you've sorted out just how much is irrelevant,
> the above is about all you ever need -- and that's _without_
> cdrecord.conf.)
I figured it had to boil down to something simple like that. That'll
give me a starting point - as soon as I figure out my burner's address.
> How did I know to use "-dev=1,0.0"? From a handy lazy-man's delight
> called "cdrecord -scanbus".
Unfortunately, on my system "cdrecord -scanbus" can't find anything
except my two hard drives: the SATA one on "scsibus0" and the IDE one
on "scsibus2". The IDE drive is the primary master, the DVD-ROM is
the secondary master, and the burner is the secondary slave. Does
the -scanbus option only check two buses, or is this another 2.6
wrinkle? (cdrecord issues nasty warning messages about my 2.6.13
kernel.)
On the other hand, k3b manages to find the burner. Last time I ran
k3b, I noticed that it spat out all sorts of stuff on the xterm from
which I ran it, including what looks like appropriate mkisofs and
cdrecord commands. I'll take a closer look at them and see what
I can figure out.
Rick Moen
> Unfortunately, on my system "cdrecord -scanbus" can't find anything
> except my two hard drives: the SATA one on "scsibus0" and the IDE one
> on "scsibus2". The IDE drive is the primary master, the DVD-ROM is
> the secondary master, and the burner is the secondary slave. Does
> the -scanbus option only check two buses, or is this another 2.6
> wrinkle?
I'm guestimating that it's a 2.6 wrinkle. The -scanbus feature might
well not work with 2.6-style ATA addressing -- and you would want to use
"dev=ATA:1,0,0" syntax instead of "dev=1,0.0" syntax. More here:
http://www.troubleshooters.com/linux/coasterless.htm
Personally, when I went CDRW-burner shopping, I decided to avoid both
all such nonsense (including the pre-2.6 dance people went through with
the ide-scsi shim driver), by just sticking with SCSI. Bliss. However:
Most of my friends decided to be cheap, had configuration problems, and
burned lots of coasters because of ide-scsi bugs. I tried hard not to
laugh.
> On the other hand, k3b manages to find the burner. Last time I ran
> k3b, I noticed that it spat out all sorts of stuff on the xterm from
> which I ran it, including what looks like appropriate mkisofs and
> cdrecord commands. I'll take a closer look at them and see what
> I can figure out.
Excellent idea.
imotgm
> Unfortunately, on my system "cdrecord -scanbus" can't find anything
> except my two hard drives: the SATA one on "scsibus0" and the IDE one
> on "scsibus2".
Try "cdrecord -scanbus dev=ATA"
--
imotgm
"Lost? Lost? I've never been lost... Been a tad confused for a
month or two, but never lost."
Charlie Gibbs
imotg...@invalid-yahoo.com (imotgm) writes:
> On Mon, 13 Mar 2006 16:45:46 -0800, Charlie Gibbs wrote:
>
>> Unfortunately, on my system "cdrecord -scanbus" can't find anything
>> except my two hard drives: the SATA one on "scsibus0" and the IDE one
>> on "scsibus2".
>
> Try "cdrecord -scanbus dev=ATA"
Bingo!
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Using libscg version 'schily-0.8'.
scsibus1:
1,0,0 100) 'HL-DT-ST' 'DVD-ROM GDR8163B' '0L23' Removable CD-ROM
1,1,0 101) 'HL-DT-ST' 'DVDRAM GSA-4163B' 'A104' Removable CD-ROM
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
Now on to the next step. I had an ISO image of a DVD sitting on disk
(which I had already sent to a Windoze box and successfully burned),
so I gave it a try:
cdrecord -dev=1,1,0 -v "GAOLT DVD4.iso"
This returned the following (redirected from stderr):
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent
defaults.
cdrecord: Continuing in 5 seconds...
cdrecord: Warning: Running on Linux-2.6.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: '1,1,0'
scsibus: 1 target: 1 lun: 0
Linux sg driver version: 3.5.33
cdrecord: No such file or directory. Cannot open '/dev/sg*'. Cannot open SCSI
driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
Damn. Well, k3b seems to work with the drive's device name,
so let's give that a try:
cdrecord -dev=/dev/hdd -v "GAOLT DVD4.iso"
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent
defaults.
cdrecord: Continuing in 5 seconds...
cdrecord: Warning: Running on Linux-2.6.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: '/dev/hdd'
devname: '/dev/hdd'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
SCSI buffer size: 64512
cdrecord: Found DVD media but DVD-R/DVD-RW support code is missing.
cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-
ProDVD.
cdrecord: Free test versions and free keys for personal use are at
ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code.
cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-
ProDVD.
cdrecord: Free test versions and free keys for personal use are at
ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
cdrecord: Unspecified command not implemented for this drive.
cdrecord: Data will not fit on any disk.
cdrecord: Cannot write more than remaining DVD capacity.
Hmmm... cdrecord doesn't seem to want to write DVDs. k3b manages
to tickle it the right way, though. But meanwhile, let's try writing
a CD instead. With the help of Rick Moen's post, I got mkisofs to put
together some MPEGs into a 640-megabyte .iso file, replaced the blank
DVD+R in the burner with a blank CD-R, and re-ran cdrecord, changing
only the name of the .iso file:
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent
defaults.
cdrecord: Continuing in 5 seconds...
cdrecord: Warning: Running on Linux-2.6.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: '/dev/hdd'
devname: '/dev/hdd'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
SCSI buffer size: 64512
cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code.
cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-
ProDVD.
cdrecord: Free test versions and free keys for personal use are at
ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
cdrecord: DMA speed too slow (OK for 12x). Cannot write at speed 40x.
cdrecord: Max DMA data speed is 12.
cdrecord: Try to use 'driveropts=burnfree'.
cdrecord: fifo had 33 puts and 0 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 0%.
OK, so it seems to want "driveropts=burnfree". I added that parameter
to the command line and tried again. This time the CD burner churned
away for several minutes. I moved the resulting disc to the CD-ROM
drive and mounted it, and found copies of all the files I fed mkisofs,
plus a TRANS.TBL, which presumably does the Joliet name translations.
cmp said the files were good, mplayer played them, and even a Windoze
box thought the disc was OK.
So I'm definitely making some progress. I'm left with two questions:
1. How do I persuade cdrecord to write DVDs? k3b can do it; I just
have to figure out the proper incantation.
2. Is that TRANS.TBL file necessary? I suspect not, since this is
the first time I've seen it. k3b doesn't generate it, and neither
does the Windows CD burning software I've been using. Does this
have anything to do with that -joliet-long parameter I found in
the mkisofs man page? Or is it related to -hide-joliet-list or
-full-iso9660-filenames?
Thanks, everyone, for your help on this. I'll get it someday...
Unruh
>In article <pan.2006.03.14....@invalid-yahoo.com>,
>imotg...@invalid-yahoo.com (imotgm) writes:
>> On Mon, 13 Mar 2006 16:45:46 -0800, Charlie Gibbs wrote:
>>
>>> Unfortunately, on my system "cdrecord -scanbus" can't find anything
>>> except my two hard drives: the SATA one on "scsibus0" and the IDE one
>>> on "scsibus2".
>>
>> Try "cdrecord -scanbus dev=ATA"
>Bingo!
>Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
>Using libscg version 'schily-0.8'.
>scsibus1:
> 1,0,0 100) 'HL-DT-ST' 'DVD-ROM GDR8163B' '0L23' Removable CD-ROM
> 1,1,0 101) 'HL-DT-ST' 'DVDRAM GSA-4163B' 'A104' Removable CD-ROM
> 1,2,0 102) *
> 1,3,0 103) *
> 1,4,0 104) *
> 1,5,0 105) *
> 1,6,0 106) *
> 1,7,0 107) *
>Now on to the next step. I had an ISO image of a DVD sitting on disk
>(which I had already sent to a Windoze box and successfully burned),
>so I gave it a try:
>cdrecord -dev=1,1,0 -v "GAOLT DVD4.iso"
cdrecord -dev=ATAPI:1,1,0 -v -dao "GAOLT DVD4.iso"
(Why in the world do you make files with spaces in their names. That is a
really really terrible idea. Space is a word delimiter. TO overload it by
also making it a valid character is just begging for trouble)
No. cdrecord does not. HOwever numerous people have hacked cdrecord so it
DOES record dvds.
Use the right version of cdrecord.
>2. Is that TRANS.TBL file necessary? I suspect not, since this is
>the first time I've seen it. k3b doesn't generate it, and neither
>does the Windows CD burning software I've been using. Does this
>have anything to do with that -joliet-long parameter I found in
>the mkisofs man page? Or is it related to -hide-joliet-list or
>-full-iso9660-filenames?
Why are you worried? Yes, it is related to joliet.
Charlie Gibbs
unruh...@physics.ubc.ca (Unruh) writes:
> "Charlie Gibbs" <cgi...@kltpzyxm.invalid> writes:
>
>> cdrecord -dev=1,1,0 -v "GAOLT DVD4.iso"
>
> cdrecord -dev=ATAPI:1,1,0 -v -dao "GAOLT DVD4.iso"
Thanks, I'll try that prefix. I can see where -dao might help too.
> (Why in the world do you make files with spaces in their names.
> That is a really really terrible idea. Space is a word delimiter.
> TO overload it by also making it a valid character is just begging
> for trouble)
Agreed, but I didn't create the file; that's the way it downloaded.
And I had to leave the spaces in at least long enough for par2verify
to check it.
>> So I'm definitely making some progress. I'm left with two questions:
>>
>> 1. How do I persuade cdrecord to write DVDs? k3b can do it; I just
>> have to figure out the proper incantation.
>
> Use the right version of cdrecord.
Fair enough; I'll search for one in my copious free time.
It does seem strange, though, that I was able to burn a
DVD with k3b - which was spitting out messages indicating
that it was taking a close look at which version of cdrecord
it had to work with.
>> 2. Is that TRANS.TBL file necessary? I suspect not, since this is
>> the first time I've seen it. k3b doesn't generate it, and neither
>> does the Windows CD burning software I've been using. Does this
>> have anything to do with that -joliet-long parameter I found in
>> the mkisofs man page? Or is it related to -hide-joliet-list or
>> -full-iso9660-filenames?
>
> Why are you worried? Yes, it is related to joliet.
Again, it's a matter of curiosity. But why have extra files that
are apparently unnecessary? I suppose I'm a bit of a neatness freak
when it comes to things like these - although you'd never convince
my wife. :-)
Chris F Clark
>>> 2. Is that TRANS.TBL file necessary? I suspect not, since this is
>>> the first time I've seen it. k3b doesn't generate it, and neither
>>> does the Windows CD burning software I've been using. Does this
>>> have anything to do with that -joliet-long parameter I found in
>>> the mkisofs man page? Or is it related to -hide-joliet-list or
>>> -full-iso9660-filenames?
>>
>> Why are you worried? Yes, it is related to joliet.
>
> Again, it's a matter of curiosity. But why have extra files that
> are apparently unnecessary? I suppose I'm a bit of a neatness freak
> when it comes to things like these - although you'd never convince
> my wife. :-)
The trans.tbl file is necessary if you are moving CD's with long named
files to old systems. And, yes one of your "Joliet" switches probably
caused it to be created. It's a backward compatibility thing. If you
(and your clients) don't have trouble reading your CDs without the
file, then you don't need it. However, if you ever want to pop your
CD into a system with Windows NT or an equivalent legacy system, you
may find you need it to get the long names off the CD. If I recall
correctly, Joliet was Microsoft's translation between short and long
names, so the NT could handle long names on a CD and yet the CD's
would still be readable by DOS. In the old days, you cold get the
files off the CD without it, but names that don't fit into the "old"
rules would be mangled, because the old CD standard had DOS-like rules
for the names (i.e. if you had a file with a name that wasn't
portable, the system had to make up a short name for the file and put
in the trans.tbl file the long name and the name on the CD). You
needed it to be so, so that DOS computers could read your CD.
Hope this helps,
-Chris
*****************************************************************************
Chris Clark Internet : com...@world.std.com
Compiler Resources, Inc. Web Site : http://world.std.com/~compres
23 Bailey Rd voice : (508) 435-5016
Berlin, MA 01503 USA fax : (978) 838-0263 (24 hours)
------------------------------------------------------------------------------
Rick Moen
Charlie, congratulations on making headway.
> Hmmm... cdrecord doesn't seem to want to write DVDs. k3b manages
> to tickle it the right way, though. [...]
Hmm. Curious.
> 1. How do I persuade cdrecord to write DVDs? k3b can do it; I just
> have to figure out the proper incantation.
Indeed. There may be some scripting magic concealed in there. (I'm not
a k3b user; perhaps someone who is will chime in.)
In case it will help, I maintain a list of extended-cdrecord
implementations and other DVD-burning utilities for Linux, here:
"DVD" on http://linuxmafia.com/kb/Hardware
> 2. Is that TRANS.TBL file necessary? I suspect not, since this is
> the first time I've seen it.
My recollection is that it's a filenames hints/translations file helpful
if your filenames are longer than the standard ISO9660 specs would
ordinarily permit, or have normally-invalid characters, or things like
that. I've never found them indispensible. On the other hand, I do
include "-T" on cdrecord's command line, just on a "can't hurt" theory.
(Sorry about being a bit vague about the exact purpose those files
serve. I don't want to go spelunking through that manpage, any more
than you do.)
Charlie Gibbs
c...@shell01.TheWorld.com (Chris F Clark) writes:
> The trans.tbl file is necessary if you are moving CD's with long named
> files to old systems. And, yes one of your "Joliet" switches probably
> caused it to be created. It's a backward compatibility thing. If you
> (and your clients) don't have trouble reading your CDs without the
> file, then you don't need it. However, if you ever want to pop your
> CD into a system with Windows NT or an equivalent legacy system, you
> may find you need it to get the long names off the CD.
I figured it had to be something like that. The need for such things
must be long gone by now, at least in most places. Certainly my Win98
box doesn't seem to need it. I popped in one of the CDs I had burned
there and used ATTRIB.EXE to look at it. No file named TRANS.TBL
existed - hidden or otherwise - yet the system read the long file
names just fine. I'll try experimenting with cdrecord's parameters
a bit more.
imotgm
> In article <pan.2006.03.14....@invalid-yahoo.com>,
> imotg...@invalid-yahoo.com (imotgm) writes:
>
>> On Mon, 13 Mar 2006 16:45:46 -0800, Charlie Gibbs wrote:
>>
>>> Unfortunately, on my system "cdrecord -scanbus" can't find anything
>>> except my two hard drives: the SATA one on "scsibus0" and the IDE one
>>> on "scsibus2".
>>
>> Try "cdrecord -scanbus dev=ATA"
>
> Bingo!
>
> Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
> Using libscg version 'schily-0.8'.
> scsibus1:
> 1,0,0 100) 'HL-DT-ST' 'DVD-ROM GDR8163B' '0L23' Removable CD-ROM
> 1,1,0 101) 'HL-DT-ST' 'DVDRAM GSA-4163B' 'A104' Removable CD-ROM
> 1,2,0 102) *
> 1,3,0 103) *
> 1,4,0 104) *
> 1,5,0 105) *
> 1,6,0 106) *
> 1,7,0 107) *
>
> So I'm definitely making some progress. I'm left with two questions:
>
> 1. How do I persuade cdrecord to write DVDs? k3b can do it; I just
> have to figure out the proper incantation.
K3b uses growisofs, not cdrecord, to burn DVDs. The pattern, for my
computer, is;
/usr/bin/growisofs -Z /dev/hdb=/path/to/file.iso -use-the-force-luke=notray -use-the-force-luke=tty -speed=4 -overburn
Yes, that is all one line. My burner is /dev/hdb. You would have to change
that to whatever your burner dev is. No need for the "1,1,0" SCSI
designation, as it recognizes the /dev/hdx just fine. I would also advise
you to rename the .iso file, to replace the space in the .iso file name
with an "_", or add " marks around it. Bad business having spaces in file
names.
Charlie Gibbs
imotg...@invalid.yahoo.com (imotgm) writes:
> On Tue, 14 Mar 2006 13:30:14 -0800, Charlie Gibbs wrote:
>
> K3b uses growisofs, not cdrecord, to burn DVDs.
Aha. That explains those references to growisofs that I saw
coming out of k3b. I didn't realize that growisofs actually
burned the disk as well.
> The pattern, for my computer, is;
>
> /usr/bin/growisofs -Z /dev/hdb=/path/to/file.iso
> -use-the-force-luke=notray -use-the-force-luke=tty -speed=4 -overburn
>
> Yes, that is all one line.
You think that's long... :-) I tried capturing k3b's stderr output
to a file, and found a copy of the command it used to run growisofs.
Again, this command is all one line, although I've broken it up with
the backslash convention to make it more readable here:
k3b: ***** growisofs parameters:
k3b: /usr/bin/growisofs -Z /dev/hdd -use-the-force-luke=notray \
-use-the-force-luke=tty -speed=8 -gui -graft-points \
-volid Voyage to the Bottom of the Sea -volset \
-appid K3B THE CD KREATOR (C) 1998-2005 SEBASTIAN TRUEG AND THE K3B TEAM \
-publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 \
-sort /tmp/kde-cjg/k3b9mZFYa.tmp -rational-rock \
-hide-list /tmp/kde-cjg/k3bGCp9Pa.tmp -joliet -hide-joliet-list \
/tmp/kde-cjg/k3bAPRS4a.tmp -full-iso9660-filenames -iso-level 2 \
-path-list /tmp/kde-cjg/k3b4rr6xb.tmp
> My burner is /dev/hdb. You would have to change that to whatever
> your burner dev is. No need for the "1,1,0" SCSI designation,
> as it recognizes the /dev/hdx just fine.
Yes, k3b successfully found my burner (/dev/hdd) and stuffed its
devname into the command line above.
> I would also advise you to rename the .iso file, to replace the
> space in the .iso file name with an "_", or add " marks around it.
> Bad business having spaces in file names.
Point taken. What's really scary is that the -appid parameter above
was generated automatically by k3b.
One other bit of trivia: when k3b was finished, it issued the message
"growisofs did not exit cleanly", and indicated an error. However,
the disk was OK. Mind you, at this rate, I'll probably soon be
bypassing k3b, so the point might well be moot (except, perhaps,
to the k3b development team).
Charlie Gibbs
(Rick Moen) writes:
> Charlie Gibbs <cgi...@kltpzyxm.invalid> wrote:
>
>> Hmmm... cdrecord doesn't seem to want to write DVDs. k3b manages
>> to tickle it the right way, though. [...]
>
> Hmm. Curious.
>
>> 1. How do I persuade cdrecord to write DVDs? k3b can do it; I just
>> have to figure out the proper incantation.
>
> Indeed. There may be some scripting magic concealed in there. (I'm
> not a k3b user; perhaps someone who is will chime in.)
As someone else pointed out, k3b is using growisofs, which I didn't
realize can burn the result directly to a disc. Looks like my next
step is to study growisofs.
> In case it will help, I maintain a list of extended-cdrecord
> implementations and other DVD-burning utilities for Linux, here:
> "DVD" on http://linuxmafia.com/kb/Hardware
Thanks - I've stashed that away in the archives.
>> 2. Is that TRANS.TBL file necessary? I suspect not, since this is
>> the first time I've seen it.
>
> My recollection is that it's a filenames hints/translations file
> helpful if your filenames are longer than the standard ISO9660
> specs would ordinarily permit, or have normally-invalid characters,
> or things like that. I've never found them indispensible. On the
> other hand, I do include "-T" on cdrecord's command line, just on
> a "can't hurt" theory.
I tried running mkisofs without the -T parameter, using files whose
names exceeded 64 characters. Under Linux, the result was fine;
however, under Win98 and XP the file names were truncated to 64
characters. Adding the -joliet-long parameter to the mkisofs
command line corrected this.
> (Sorry about being a bit vague about the exact purpose those files
> serve. I don't want to go spelunking through that manpage, any more
> than you do.)
No problem. Maybe once I get this stuff all figured out I'll write
a "getting started" guide to burning CDs and DVDs under Linux. There
seems to be a need for such a document. A basic description (i.e.
the minimum command-line parameters to make it work) would get people
going with a minimum of pain, as well as serving as a starting point
into the full intricacies of the man pages.
Here are the commands that work for me so far:
mkisofs -o foo.iso -r -J -joliet-long -V <volid> -v <filespecs>
cdrecord -dev-/dev/hdd driveopts=burnfree -v -dao foo.iso
Rick Moen
> In article <cd3db$44185305$c690c3ba$34...@TSOFT.COM>, ri...@linuxmafia.com
> (Rick Moen) writes:
>> Indeed. There may be some scripting magic concealed in there. (I'm
>> not a k3b user; perhaps someone who is will chime in.)
>
> As someone else pointed out, k3b is using growisofs, which I didn't
> realize can burn the result directly to a disc. Looks like my next
> step is to study growisofs.
I was thinking to myself, at the time, that k3b might be using something
other than vanilla Schilling-produced cdrecord -- so I feel a _tiny_ bit
sheepish for not saying that. (In fact, I was thinking it would turn
out to be one of the several DVD-patched forks _of_ cdrecord.)
In any event, the "DVD" on http://linuxmafia.com/kb/Hardware
knowledgebase article I referred you do _does_ discuss all of those
programs, including growisofs / dvd+rw-tools.
> No problem. Maybe once I get this stuff all figured out I'll write
> a "getting started" guide to burning CDs and DVDs under Linux. There
> seems to be a need for such a document.
If I might make a suggestion: If you _do_ write such a thing, I can
help you get it included as a HOWTO in the Linux Documentation Project.
You'll find the existing HOWTOs here:
http://www.tldp.org/HOWTO/HOWTO-INDEX/howtos.html
Note that the existing "DVD HOWTO" and "DVD Playback HOWTO" both concern
video DVDs, not mastering and burning of DVD+R[W] / DVD-R[W] media. A
"DVD Writing HOWTO" to complement the existing "CD Writing HOWTO" would
be most useful.
All you'd have to do is write the basic text. One of the core Linux
Documentation Project volunteers (or I) will be glad to do the rest.
(And, hey, don't feel shy about this merely because you're "not an
expert". Most Linux documentation gets written just by some
Johnny-on-the-spot who decided _somebody_ needed to fill some need.
There's no reason why it should not be you.)
iforone
Rick;
I haven't visited your DVD page yet - but I will and I'm sure to
Bookmark it ;-)
Preface; (on Debian vanilla 2.6.8-2-i386 Sarge) -- though I *must* note
that when using apt-get and aptitude (and KPackage) when I first
installed Debian and was updating, upgrading, configuring - I grabbed
any and all packages pertaining/depending on "cdrecord" / "cdparanoia"
- and anything with "dvd" in it ;-) so I *may* have installed more than
the usual vanilla kernel Sarge stuff.
Besides offering just a small amount of info earlier (post #11) about
k3b's output file - and using that "command" directly;
cdrecord comand:
-----------------------
/usr/bin/cdrecord.mmap -v gracetime=2 dev=1,0,0 speed=32 -dao
driveropts=burnfree -eject -data
this continuing discussion led me to find cdrecord.mmap and also do a;
$ locate dvd
....
/usr/share/doc/dvd+rw-tools/dvd-rw.html
....
as you can see, one of the many docs that contains mucho info about
dvd+rw/-rw burning - note also these exe's listed in /usr/bin
/usr/bin/dvdbackup
/usr/bin/dvd-ram-control
/usr/bin/dvd+rw-booktype
/usr/bin/dvd+rw-format
/usr/bin/dvd+rw-mediainfo
/usr/lib/libdvdread.so.3
/usr/lib/libdvdread.so.3.0.0
Imotgm and others have offered much useful info for me to absorb as
well -- thanks to all