On Thu, 12 Jun 2003, Jim Sibley wrote: > Dave wrote: > > >Methinks the Right Thing To Do would be to add function to "mt" to allow > it > >to reserve a drive (eg, "mt reserve /dev/st0") when a application wants > on, > >and provide a release function when you're done with it (eg "mt release > >/dev/st0"). That would be generic enough to handle most of the Intel cases > >as well, but would suit us nicely(*). > > 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.
It's not at all clear to me that the fact you have tape390 loaded means you want to lock _all_ your tape drives. What if you decide on a custom kernel with tape390 builtin? -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
