K3b -> Cddb Doesn’t Work… Cdfs?

Home » CentOS » K3b -> Cddb Doesn’t Work… Cdfs?
CentOS 7 Comments

Like I said, I don’t use k3b and friends. But from what I remember of it from a while back, it was configured to explicitly call (e.g.)
/usr/bin/cdrecord, so it wasn’t linked to cdrtools libraries directly. If that is the case now, then you could configure k3b to use your version of cdrecord instead, without needing to recompile (because in theory the GUI should not depend on cdrtools libs).

It’s worth investigating. If k3b does indeed compile against cdrtools libraries then you may be out of luck.


7 thoughts on - K3b -> Cddb Doesn’t Work… Cdfs?

  • Keith Keller wrote:

    Writing optical media is a task that needs special privileges. Calling e.g. cdrecord as a separate program gives prilviege separation and prevents you from being forced to do a security audit on higly complex GUI.

    The main problem wth k3b is that it does not support feature enhancements implemented during the past 10 years.

    It is e.g. a pitty that there is no support for the libfind based features in mkisofs. It would be a real challenge for a GUI writer to implement GUI support for something like find(1). So this is even expected to give fun to the author!


  • there are no ‘files’ on a Audio CD. you can mount an iso 9660 (or UDF
    etc) file system, but those don’t exist on an Audio CD.

  • I gave a couple reasons previously in this thread… too involved to repeat. There must be a lot of other reasons if so many people have spent time developing cdfs for so long a time.

  • actually, video DVD’s use UDF, and store the video streams in UDF named files. now, most commercial video DVDs are copy protected, so you can’t actually READ those files unless you play the CSS dance with the drive.