>> Wouldn't it make more sense to just scan all subdirectories of
>> the parent rather than limiting it to those in a list?
> Possibly, but that is a significant change to modutils. At the
> moment I hesitate to do something like this, people are used to
> the current method.
What I'd like to see is a variant combining both methods, which would
result in something like the following algorithm:
1. Scan the config file for standard directories to search. For
each one found, search it for the required module, stopping
with the first one found.
2. If the required module isn't found in any of the standard
directories, scan the config file for a config statement
naming a base directory, then do a full tree search from
that directory for a matching module.
3. If the required module still hasn't been found, scan the
config file for a "last resort" directory statement, and
search in that directory for the module.
4. If the required module still hasn't been found, report an
error.
In theory, all modules would be found using step (1), so steps (2)
and (3) would only get used for modules which are not in the expected
directory for some reason. As a result, this would minimise the
overhead incurred.
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/Linux/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/