I am sorry, but there is no relation between your problem and cdrercord.
Your problem is either caused by an ill-designed kernel (in
a decently designed kernel, all ioctl function codes are different
and for this reason, sending an ioctl to an improper device
will just cause a kernel error code of ENOTTY but no hang)
... or you found a bug in the volume management that is build into
some GUIs on Linux because the Linux kernel is missing support
for changeable volume management....
In any case: Note that you are using a 4 year old cdrecord!
If Linux was a kernel where the authors did take care about the
users and thus did care about stable interfaces this should be no problem.
Unfortunately this is not true for Linux. The Linux kernel authors
are proud of the fact that they constantly change interfaces in order
to show you that you need the sources of your applications. You need
to recompile them all every time you install a new kernel. Of course,
you need to fetch the latest source before as not all interface changes are
dealt by a recompile only.....the authors of applications are forced
tp constantly add new work arounds for the fact that Linux kernel interfaces
are not stable.
J�rg
--
EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
