Jeff Garzik <jgarzik@pobox.com> wrote:
>
> This new feature provides a /proc playground for modules. As it
> stands now, any random driver or module that exports something to
> /proc generally must create a file, or directory, in /proc root. Over
> time that can get messy.
Does that mean that, if a device driver is compiled as a module, its
data gets placed in /proc/module, but if it is compiled statically into
the kernel, that the information will go somewhere else?
--
fox@dallas.net (Fuzzy Fox) || "Just about every computer on the market
sometimes known as David DeSimone || today runs Unix, except the Mac (and
http://www.dallas.net/~fox/ || nobody cares about it). -- Bill Joy '85
-
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/
>
> This new feature provides a /proc playground for modules. As it
> stands now, any random driver or module that exports something to
> /proc generally must create a file, or directory, in /proc root. Over
> time that can get messy.
Does that mean that, if a device driver is compiled as a module, its
data gets placed in /proc/module, but if it is compiled statically into
the kernel, that the information will go somewhere else?
--
fox@dallas.net (Fuzzy Fox) || "Just about every computer on the market
sometimes known as David DeSimone || today runs Unix, except the Mac (and
http://www.dallas.net/~fox/ || nobody cares about it). -- Bill Joy '85
-
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/