View previous topic :: View next topic |
Author |
Message |
kamagurka Veteran
Joined: 25 Jan 2004 Posts: 1026 Location: /germany/munich
|
Posted: Wed Sep 22, 2004 7:12 pm Post subject: cdrecord eh? |
|
|
after getting frustrated at cdrecord and bashburn a couple times, i finally emerged k3b. lo and behold, with k3b, everything works "out of the box"; but since k3b is merely a cdrecord frontend, there *must* be a way for me to do simple cd-burning tasks without the overhead of a gui. i'm running 2.6.7-gentoo-r6, and cdrecord never fails to remind me that any kernel newer than stoneage is "vewy vewy bad for buwning cds". however, if k3b can do it, so must cdrecord. now, to my questions:
1. is there a way to have k3b show me the cdrecord commands it issues, some sort of verbose mode?
2. if not, what the hell do i have to do to point cdrecord to my IDE dvd-writer and shoot a file (or several, for that matter) on the cd (or dvd, for that matter), preferrably while naming the cd; also, please without putting the files on there in any freaky filesystem or anything. _________________ If you loved me, you'd all kill yourselves today.
--Spider Jerusalem, the Word |
|
Back to top |
|
|
Rafje Tux's lil' helper
Joined: 19 May 2004 Posts: 109 Location: .be
|
Posted: Wed Sep 22, 2004 8:28 pm Post subject: |
|
|
Hmm. After the fact, K3b shows what it has done by clicking the "Show Debugging Output" button. Unfortunately, it shows what cdrecord said to K3b but not what K3b said to cdrecord.
Maybe something like this could work: you rename cdrecord to, let's say cdrecord.orig. Then you create a shell script called "cdrecord", that you put in the same directory and that has the same permissions as cdrecord.orig so that K3b finds it. That shell script does nothing else than log the arguments it was called with, and then call cdrecord.orig with those same arguments. You know, something like: Code: | cd /usr/bin
mv cdrecord cdrecord.orig
echo 'echo $* >> /tmp/cdrecord.log; cdrecord.orig $*' > cdrecord
chmod 4711 cdrecord
| and then run K3b.
Note that I haven't tried to do this, it's just off the top of my head. If K3b communicates with cdrecord only through the arguments it gives in the command-line, then an approach like this might actually work.
Have fun,
R. |
|
Back to top |
|
|
kamagurka Veteran
Joined: 25 Jan 2004 Posts: 1026 Location: /germany/munich
|
Posted: Thu Sep 23, 2004 1:09 am Post subject: |
|
|
yes, that is a very interesting approach, and i won't hesitate to use it if necessary. however, i find it hard to believe that this is the only way to find out what k3b does; that's so...microsoftian. also, can't anybody tell me an easy way to burn cds from the commandline? _________________ If you loved me, you'd all kill yourselves today.
--Spider Jerusalem, the Word |
|
Back to top |
|
|
psyqil Advocate
Joined: 26 May 2003 Posts: 2767
|
Posted: Thu Sep 23, 2004 1:21 am Post subject: |
|
|
http://mail4.hallertau.net/~andreasb/cdrmicrohowto.html
Sogar auf deutsch... Beispiel:
Code: | cdrecord dev=ATAPI:1,0,0 driveropts=burnfree speed=24 -v -eject blank=fast some.iso | google for "cdrecord howto" and you'll find answers to everything you ever wanted to know about burning and even dared to ask.. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|