module which ?

[Gintautas G. <gi...@ki...>]

Hi,

just a couple of comments from developer folks who use modules over
here:

- it is nice that modules obscure PATH, but it is not nice that
  modules obscure binary names that they give access to. Suppose
  a fascist administrator removes /usr/sbin from default PATH,
  how do i know which module gives me access to "fuser" if there
  is no "obvious" module such as "admin" (or make a more complicated
  example of your own). In other words, there's a need for
  "module which <binary name>" that spits out a corresponding
                               module name, or
                <module name>  that spits out a list of binaries/aliases
                               that module gives access to/defines.

- alternatively, there might be "module load ALL" (quite a nice stress
  test for a shell ;-), and afterwards one could unload/switch
  unnecessary modules. It should be able to detect dependencies
  between modules (could be nice for consistency tests).

What do you think ?

Regards,
Gintas