Re: RFC: /proc/module namespace
david parsons (o.r.c@p.e.l.l.p.o.r.t.l.a.n.d.o.r.u.s)
2 Sep 1999 10:10:48 -0700
In article <linux.kernel.37CE1204.D41D0511@pobox.com>,
Jeff Garzik <jgarzik@pobox.com> wrote:
>Fuzzy Fox wrote:
>>
>> 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?
>
>No change in behavior at all. A module can be compiled into the kernel.
I don't think that's the problem.
The problem is putting /proc information into /proc/modules; unless
the driver ALWAYS puts information there, it means that applications
that use /proc have to root around in multiple places to get that
information out.
____
david parsons \bi/ That way lies madness.
\/
-
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/