If not, I was thinking that it would be really neat if procfs provided
external entry points that would allow mod developers to add their own
variables to the procfs without recompiling. I'm thinking each module
would have access to proc_register_namespace, which would take two
arguments: a directory name and a function pointer.
The directory name would tell procfs where under /proc/other this
module is going to store its internal directory tree.
The function pointer points to a function that handles all the
interaction with the third-party files.
Example:
XYZ Linux Consultants develops a device driver module for the
BubbaChunk serial board. They want to provide accounting
stats in a /proc-like manner, but they don't want to burden
their users with a kernel patch simply to use accounting.
Instead, they have their module call
proc_register_namespace(), and provide their accounting stats
in the /proc/other/bubbachunk directory.
Comments? I didn't see anything like this in the proc source code,
but I may have missed something.
Thanks,
Jeff
-- The new Congressmen say they're going | Heavy, adj.: to turn the government around. I hope | Seduced by the chocolate side I don't get run over again. | of the force.