If there were a single kernel envar pool, and if drivers were
allowed to putenv() as well as getenv(), it could be a unified way to
save configuration information across module incarnations, or even
across system reboots. This raises the usual questions about built-in
drivers being able to autoprobe and/or configure multiple devices, and
whether or not module-based drivers can do the same; the envar naming
convention is important here.
Presumably a "/proc" device could be used to handily view and
edit the kernel envars.
Craig Milo Rogers