On February 11, 2002 08:05 pm, Bill Davidsen wrote:
> On Mon, 11 Feb 2002, Daniel Phillips wrote:
>
> > On February 9, 2002 07:15 pm, Bill Davidsen wrote:
> > > On Wed, 6 Feb 2002, Randy.Dunlap wrote:
> > >
> > > > I still prefer your suggestion to append it to the kernel image
> > > > as __initdata so that it's discarded from memory but can be
> > > > read with some tool(s).
> > >
> > > The problem is that it make the kernel image larger, which lives in
> > > /boot on many systems. Putting it in a module directory, even if not a
> > > module, would be a better place for creative boot methods, of which
> > > there are many.
> >
> > You don't seem to be clear on the concept of 'option'.
>
> Did I miss discussion of an option to put it somewhere other than as part
> of the kernel? Sorry, I missed that.
It's a trick question? The config option would let you specify that no
kernel config information at all would be stored with or in the kernel. No
cost, no memory footprint. And I would get to have the extra warm n fuzzy
usability I tend to go on at such lengths about. So we're both happy, right?
I'd even remain happy if the option were set *off* by default.
-- Daniel - 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 : Fri Feb 15 2002 - 21:00:44 EST