> Since its really a zSeries notion, it seems to me putting the > assign/unassign in "insmod/delmod tape390" initialization somehow would be > more appropriate. Also, the way the tapes have been implemented (by dev > node), there is no mount involved. Mounts in linux don't really mount > devices - they mount file systems.
"mt" is the generic tape manipulation utility -- no implication of mount at all. All the other generic utility tape handling function (eg fsf, rewind, etc) are in mt, so thus the suggestion for putting the function into mt. Unloading and loading the device driver to effect reservation seems broken to me (yes, it's how it's implemented right now, but it still seems wrong) as it's not that the device is appearing/disappearing (the device remains attached), but whether a system has a reservation on using the device. That's certainly not 390-specific -- I've been wanting this kind of semantics forever.
