[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Sheflug] re:k3b woes

To: sheflug <shef-lug [at] xxxxxxxxxxxxxxxxxxx>
Subject: [Sheflug] re:k3b woes
From: Paul Sims <paul_sims [at] xxxxxxxxxxxx>
Date: 08 Jun 2003 15:59:20 +0100
Delivered-to: shef-lug [at] list.sheflug.org.uk
List-help: <mailto:shef-lug-request [at] list.sheflug.org.uk?subject=help>
List-id: Sheflug <shef-lug.list.sheflug.org.uk>
List-post: <mailto:shef-lug [at] list.sheflug.org.uk>
List-subscribe: <http://community.uklinux.net/mailman/listinfo/shef-lug>,<mailto:shef-lug-request [at] list.sheflug.org.uk?subject=subscribe>
List-unsubscribe: <http://community.uklinux.net/mailman/listinfo/shef-lug>,<mailto:shef-lug-request [at] list.sheflug.org.uk?subject=unsubscribe>
Organization:
Reply-to: shef-lug [at] xxxxxxxxxxxxxxxxxxx
Sender: shef-lug-admin [at] xxxxxxxxxxxxxxxxxxx

Bad form I know, but to answer my own query from earlier, after
compiling & installing cdrdao & running from it's installation dir I
managed to do a direct cd to cd copy fine - this didn't work with k3b
however. I realised that the command-line invocation explicitly states
which drivers are used for which drive so I got the idea k3b was being a
bit sloppy about passing this info to cdrdao. 

In /usr/local/cdrdao/drivers I simply modified the file to add in the
name of my dvd as extracted by cdrdao and bingo! k3b now works quite
happily.

Hope this is of use to anyone else having similar problems.
-- 
Paul Sims <paul_sims [at] ntlworld.com>

___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.

Prev by Date: [Sheflug] k3b woes
Next by Date: [Sheflug] Apache SuExec help
Previous by thread: [Sheflug] k3b woes
Next by thread: [Sheflug] Apache SuExec help
Index(es):
- Date
- Thread