| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTimTm40Sp5-kMaL4d1oXf3CzytZsBCus3DN0jwD-@mail.gmail.com> Date: Sat, 26 Feb 2011 23:47:55 +0100 From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com> To: Arnaud Lacombe <lacombar@...il.com> Cc: Sam Ravnborg <sam@...nborg.org>, Jeff Mahoney <jeffm@...e.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Roman Zippel <zippel@...ux-m68k.org>, linux-kbuild@...r.kernel.org Subject: Re: [PATCH] Add ``cloneconfig'' target Hi, On Sat, Feb 26, 2011 at 8:47 PM, Arnaud Lacombe <lacombar@...il.com> wrote: > Hi, > > On Fri, Feb 25, 2011 at 1:07 AM, Sam Ravnborg <sam@...nborg.org> wrote: >> We already have something remotely similar in kconfig. >> We use the following list: >> config DEFCONFIG_LIST >> string >> depends on !UML >> option defconfig_list >> default "/lib/modules/$UNAME_RELEASE/.config" >> default "/etc/kernel-config" >> default "/boot/config-$UNAME_RELEASE" >> default "$ARCH_DEFCONFIG" >> default "arch/$ARCH/defconfig" >> > I may argue that anything within the Linux tree which point > _by_default_ to something outside the tree itself is broken. Say I try > to build a Linux kernel on a system with has its own non-kconfig > `/etc/kernel-config', I guess this would make the configuration fail. It is true that it may be annoying/unexpected, but the most common use case is to build the kernel in the same machine which will run it. In addition, it does not make the configuration fail, you just get the machine's configuration. If you typed "menuconfig" instead of "oldconfig" it means that you didn't have any configuration at all in the first place, so if you are building a kernel for some other machine you will have to configure through all the options manually anyway. > >> It would be better to teach kconfig to read /proc/config.gz >> and then add it to the list above. >> > Why ? Thing should be kept simple. kconfig's job is not to know about > the trillion file format which exist in the world, even more if the > implementation is made by building a command[0], executing it in a > separate process and reading the output. This is the shell's job. What > may be useful in the contrary would be to eventually teach kconfig to > read from <stdin>. /proc/config.gz is provided by the kernel and its format is defined by kconfig itself which is, as well, part of the kernel (it is not one random format from a pool of a trillion), so it will be nice if kconfig learns how to read its own configuration from there. kconfig only knows about config files (one format). The fact that it's gzipped its irrelevant, any reasonable machine capable of building the kernel has gzip installed. > > - Arnaud > > [0]: which is built depending on an extension, which is even more awful ... > >> This list is used if you just type "make enuconfig" without >> any configuration. >> >> Sam >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in >> the body of a message to majordomo@...r.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists