On Thu, Jan 12, 2012 at 01:55:39AM -0800, Garrett Cooper wrote: > On Thu, Jan 12, 2012 at 2:06 AM, Luigi Rizzo <rizzo_at_iet.unipi.it> wrote: > > On Thu, Jan 12, 2012 at 10:16:53AM +0100, Gary Jennejohn wrote: > >> On Thu, 12 Jan 2012 09:11:39 +0100 > >> Luigi Rizzo <rizzo_at_iet.unipi.it> wrote: > >> > >> > usr/sbin/config assumes that the kernel config file > >> > lives in ${src_base}/sys/${arch}/conf , which means that > >> > if you need to build a custom kernel one needs RW > >> > access to that directory. > >> > > >> > Any idea on how we can enable config to work in a > >> > generic directory ? > >> > > >> > I scanned the source code usr.sbin/config and found that > >> > it uses hardwired paths -- specifically, it looks for > >> > the kernel source tree in "../.." and has multiple > >> > hardwired paths such as "../../conf/". > >> > There is also a somewhat undocumented access to a > >> > file called DEFAULTS that extends the configuration you pass. > >> > > >> > Any objections to the addition of a "-s" option to config(8) > >> > to specify the location of the source tree ? > >> > > >> > >> Seems like a good idea to me as long as the old behavior is kept. > > > > of course :) > > Why not just set KERNCONFDIR? The variable does not seem to be used by usr/sbin/config cheers luigiReceived on Thu Jan 12 2012 - 09:00:38 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:23 UTC