this is what I remember from the time I tried to adapt this to my needs. Remembering the values would not be too much of a critical thing, if the kernel parameters would be settable from the user files. There's a place for that in ./files, but this behavior is not implemented.
----- Original Message ---- > From: Robert P. J. Day <[EMAIL PROTECTED]> > To: openwrt-devel@lists.openwrt.org > Sent: Monday, November 10, 2008 3:36:44 PM > Subject: Re: [OpenWrt-Devel] repeated kernel config questions > > Quoting Stanislav Sinyagin : > > > The makefiles override the kernel config each time you do "make menuconfig". > > It's not a bug, it's so by design :) > > really? i don't have the build structure in front of me, > but the standard kernel config recipe is that, if you have > no .config file, the build will grab the "default" (and, > hence, you might have to answer questions about "NEW" options.) > > however, as long as you have an existing .config, the build > process will use it. are you saying that any existing .config > file will *always* be ignored in favour of the default? that > would be unusual, and definitely non-standard behaviour. > > rday > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
