Arjan van de Ven wrote:
>>>What he is saying is that you can't do that, generically. Some options are
>>>available at runtime through /proc, but most are not. You need to check what
>>>happend back at compile time.
>>>
>>Right, there is a religious issue here: some core kernel hackers believe
>>that it is wrong to encode kernel configuration in the kernel, and that
>>is why it's not available. Technically it is not difficult, nor is it
>>difficult to make it memory-efficient.
>>
>
> It's silly to put it permanently in unswappable memory; putting it in
> /lib/modules/`uname -r/
> somewhere does make tons of sense instead.
That is not guaranteed to be correct though. Why not allow the
builder of the kernel to choose an option to keep it in the
kernel unswappable memory, or to place it in the lib/modules
directory? That should allow the builder to choose tho option that
is best for them, with no adverse impacts on those who choose
a different option...
-- Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com> President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Feb 07 2002 - 21:00:36 EST