I second the notion that numeric volume labels are in widespread use.
Maybe those barcode manufacturers gave special discounts to people who
ordered ranges without alphabetic characters in them. :-)

My suggested kludge actually would be the opposite of what others have
suggested; namely, I would assume first that user input actually is a
literal label and consider it as a potential MediaId only if no match is
found.

Further, although you can't do much for existing installations, we could
reduce ambiguity by starting with MediaId 1000000 (rather than 1) -- so
that valid MediaIds cannot be encoded in a six-character ANSI label.
That's not a total cure, I've not seen longer labels in our
environments.

Actually, suitably desperate individuals probably could perform some SQL
magic on their database now to renumber MediaIds to a less dangerous
range, and avoid the risk of bacula doing something you did not intend.
That's still no fix for mangling your input and refusing to do what you
really wanted. ;-)

Cheers,

Scott Bailey
scott.bailey AT eds DOT com


------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users