Hi. I'm running the Debian/Woody package for both cdrecord and 2.4 kernel-sources, so the ioctls should be compatible (even if they're 4 years old). So far as I know, I'm not using any GUI-based volume management (I use fvwm2, not Gnome or KDE) but are there any processes or kernel modules I should check for?
It sounds like you're saying this is a kernel bug. Perhaps you would be kind enough to forward the report to the kernel package team if that's the case? As an aside, while clearly nothing should cause a kernel to crash, I would have expected a program that deals specifically with the SCSI interface, to the extent of scanning the bus, to notice that it was about to try to talk to an unlikely/impossible SCSI address and give a warning to the user: a message like 'ENOTTY: No such device' in response to 'dev=/dev/cdrom' would have been confusing, but something like "Impossible SCSI address [-2, -2, -2] - have you specified dev= properly?" would have been good. I sympathise with your frustration over Linux ioctl changes. You'd suggest that I use Windows or Solaris instead? Best wishes, Tim Baverstock. On Sunday 27 March 2005 1:14 pm, Joerg Schilling wrote: > 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 -- Most incoming HTML email is caught by my SPAM FILTER. http://www.baverstock.org.uk/tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
