On Thu, 2005-10-20 at 16:10 -0400, Luben Tuikov wrote: > You see? You don't need IOCTLs, yet you can be fully compliant > to the spec so that already existing user space management programs > can transition with minimal change to their code (over to the front > end: sg/whatever). this is EXACTLY my point. A proper API would NOT need the userland apps to change if the underlying mechanism changes. Or in other words: today it may be SG, tomorrow BSG or SysFS, and when we open 2.7 the mechanism may be WokkieWokkie. The implementation of the interface library may need to change for this, but the management app should not. There is a parallel in the glibc/posix/sus world: With the 2.6 kernel there is a new syscall mechanism (sysenter) on x86 kernels available. NONE of the applications needed changing, fopen() remained fopen(), not just as API but also as ABI. All that needed some adjustments were glibc internals. - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
