Joerg Schilling wrote:
I just checked, it's in 2.4.18, Redhat 8.0 release, so it goes back to at minimum June 2002, it would seem to be pretty stable. Where it belongs is arguable, but it hasn't moved in a very long time.Bill Davidsen <davidsen@tmr.com> wrote:It is present on a lot more machines than SCSI CD/DVD drives these days. While it's true that the user can suppress it, it's present in the major distributions, and I can't remember seeing any Linux system with /proc disabled in years.This strange and basically useless /proc/sys/dev/cdrom/info has not been a default interface.1) Things like this do not beling into /proc 2) This kind of "interface" was subject to many incompatible changes during the past years. If it stays stable for at least 2-3 years, we may talk again about a pissibility of using it...
The reality is that (a) almost no one uses SCSI optical devices, even if SCSI disk is in use, (b) there is a lot more use and support for Linux than any (or possibly all) of the legacy systems you mention as standard, and (c) the systems you like so well now support use of device names. That's the reality.Looks like you loose connectivity to reality.Come back to reallity! No optical drive will allow you to write whithout SCSI. You seem to forget, that a memory stick is SCSI, a CD/DVD writer is SCSI and many other devices are SCSI..... a properly designed OS would implementa proper integration of SCSI devices instead of breaking an existing integration.
None of that stuff is SCSI, it uses the SCSI command set, actually a subset plus some vendor extensions. And that's just the point, the physical bus part should be a tiny and selectable part of the process, not immutable. The logic to transfer a command to the hardware might go by ioctl, syscall, or actual device access, and there's no need to tie that to the library.
-- bill davidsen <davidsen@tmr.com> CTO TMR Associates, Inc Doing interesting things with small computers since 1979