[opensuse-kernel] reintroduce .configs in kernel-source.rpm?
Hi, in the past, the kernel-source package used to install the config files for it's architecture to /usr/src/linux-obj/$arch/$flavor/.config Now kernel-source is noarch and the the files below /usr/src/linux-obj/ are packaged in kernel-$flavor-devel. This works fine for KMPs, but it's unintuitive for people who install the kernel-source package and want to manually recompile their kernel - they have to install an additional -devel package for just the single .config file. Therefore I was thinking about adding the .config files to kernel-source, e.g. /usr/src/linux/config/$arch/$flavor like the config/ subdir in git (and hope that there won't appear a 'config' directory in the upstream kernel). Or maybe place the configs next to the upstream defconfigs: /usr/src/linux/arch/$arch/configs/suse_$flavor_defconfig Then it would be possible to say make O=... suse_$flavor_defconfig (it would not be that easy actually, because x86 and x86_64 share the same directory). What do you think? Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wed, Jan 20, 2010 at 03:33:21PM +0100, Michal Marek wrote:
Hi,
in the past, the kernel-source package used to install the config files for it's architecture to /usr/src/linux-obj/$arch/$flavor/.config Now kernel-source is noarch and the the files below /usr/src/linux-obj/ are packaged in kernel-$flavor-devel. This works fine for KMPs, but it's unintuitive for people who install the kernel-source package and want to manually recompile their kernel - they have to install an additional -devel package for just the single .config file. Therefore I was thinking about adding the .config files to kernel-source, e.g.
/usr/src/linux/config/$arch/$flavor
like the config/ subdir in git (and hope that there won't appear a 'config' directory in the upstream kernel). Or maybe place the configs next to the upstream defconfigs:
/usr/src/linux/arch/$arch/configs/suse_$flavor_defconfig
Then it would be possible to say make O=... suse_$flavor_defconfig (it would not be that easy actually, because x86 and x86_64 share the same directory).
What do you think?
What's wrong with the config in /proc/config.gz that is on all systems? That doesn't require a new package to be installed :) thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 20.1.2010 15:47, Greg KH wrote:
On Wed, Jan 20, 2010 at 03:33:21PM +0100, Michal Marek wrote:
Hi,
in the past, the kernel-source package used to install the config files for it's architecture to /usr/src/linux-obj/$arch/$flavor/.config Now kernel-source is noarch and the the files below /usr/src/linux-obj/ are packaged in kernel-$flavor-devel. This works fine for KMPs, but it's unintuitive for people who install the kernel-source package and want to manually recompile their kernel - they have to install an additional -devel package for just the single .config file. Therefore I was thinking about adding the .config files to kernel-source, e.g.
/usr/src/linux/config/$arch/$flavor
like the config/ subdir in git (and hope that there won't appear a 'config' directory in the upstream kernel). Or maybe place the configs next to the upstream defconfigs:
/usr/src/linux/arch/$arch/configs/suse_$flavor_defconfig
Then it would be possible to say make O=... suse_$flavor_defconfig (it would not be that easy actually, because x86 and x86_64 share the same directory).
What do you think?
What's wrong with the config in /proc/config.gz that is on all systems? That doesn't require a new package to be installed :)
That limits you to the kernel version and flavor you are running :). Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wed, Jan 20, 2010 at 03:48:25PM +0100, Michal Marek wrote:
On 20.1.2010 15:47, Greg KH wrote:
On Wed, Jan 20, 2010 at 03:33:21PM +0100, Michal Marek wrote:
Hi,
in the past, the kernel-source package used to install the config files for it's architecture to /usr/src/linux-obj/$arch/$flavor/.config Now kernel-source is noarch and the the files below /usr/src/linux-obj/ are packaged in kernel-$flavor-devel. This works fine for KMPs, but it's unintuitive for people who install the kernel-source package and want to manually recompile their kernel - they have to install an additional -devel package for just the single .config file. Therefore I was thinking about adding the .config files to kernel-source, e.g.
/usr/src/linux/config/$arch/$flavor
like the config/ subdir in git (and hope that there won't appear a 'config' directory in the upstream kernel). Or maybe place the configs next to the upstream defconfigs:
/usr/src/linux/arch/$arch/configs/suse_$flavor_defconfig
Then it would be possible to say make O=... suse_$flavor_defconfig (it would not be that easy actually, because x86 and x86_64 share the same directory).
What do you think?
What's wrong with the config in /proc/config.gz that is on all systems? That doesn't require a new package to be installed :)
That limits you to the kernel version and flavor you are running :).
Which is what I thought you said the user probably wants to do :) Anyway, I have no objection to add the config to the kernel-source package, as long as we document it. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/20/2010 09:55 AM, Greg KH wrote:
On Wed, Jan 20, 2010 at 03:48:25PM +0100, Michal Marek wrote:
On 20.1.2010 15:47, Greg KH wrote:
On Wed, Jan 20, 2010 at 03:33:21PM +0100, Michal Marek wrote:
Hi,
in the past, the kernel-source package used to install the config files for it's architecture to /usr/src/linux-obj/$arch/$flavor/.config Now kernel-source is noarch and the the files below /usr/src/linux-obj/ are packaged in kernel-$flavor-devel. This works fine for KMPs, but it's unintuitive for people who install the kernel-source package and want to manually recompile their kernel - they have to install an additional -devel package for just the single .config file. Therefore I was thinking about adding the .config files to kernel-source, e.g.
/usr/src/linux/config/$arch/$flavor
like the config/ subdir in git (and hope that there won't appear a 'config' directory in the upstream kernel). Or maybe place the configs next to the upstream defconfigs:
/usr/src/linux/arch/$arch/configs/suse_$flavor_defconfig
Then it would be possible to say make O=... suse_$flavor_defconfig (it would not be that easy actually, because x86 and x86_64 share the same directory).
What do you think?
What's wrong with the config in /proc/config.gz that is on all systems? That doesn't require a new package to be installed :)
That limits you to the kernel version and flavor you are running :).
Which is what I thought you said the user probably wants to do :)
Anyway, I have no objection to add the config to the kernel-source package, as long as we document it.
I'm good with it too. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAktXHI4ACgkQLPWxlyuTD7J6/QCggGGzVAkGTHDqVxClT9RUY1lr sIQAnR6fYUq+yt2nP9ObBl6uBlnMVREy =AGcl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wednesday 2010-01-20 15:48, Michal Marek wrote:
in the past, the kernel-source package used to install the config files for it's architecture to /usr/src/linux-obj/$arch/$flavor/.config[...]
What's wrong with the config in /proc/config.gz that is on all systems? That doesn't require a new package to be installed :)
That limits you to the kernel version and flavor you are running :).
I concur with Greg. Look at /boot/config-* -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wed, 20 Jan 2010, 15:47:01 +0100, Greg KH wrote:
On Wed, Jan 20, 2010 at 03:33:21PM +0100, Michal Marek wrote:
Hi,
in the past, the kernel-source package used to install the config files for it's architecture to /usr/src/linux-obj/$arch/$flavor/.config Now kernel-source is noarch and the the files below /usr/src/linux-obj/ are packaged in kernel-$flavor-devel. This works fine for KMPs, but it's unintuitive for people who install the kernel-source package and want to manually recompile their kernel - they have to install an additional -devel package for just the single .config file. Therefore I was thinking about adding the .config files to kernel-source, e.g.
/usr/src/linux/config/$arch/$flavor
like the config/ subdir in git (and hope that there won't appear a 'config' directory in the upstream kernel). Or maybe place the configs next to the upstream defconfigs:
/usr/src/linux/arch/$arch/configs/suse_$flavor_defconfig
Then it would be possible to say make O=... suse_$flavor_defconfig (it would not be that easy actually, because x86 and x86_64 share the same directory).
What do you think?
What's wrong with the config in /proc/config.gz that is on all systems? That doesn't require a new package to be installed :)
AFAIK, /proc/config.gz needs the kernel _running_ whose configuration your then may tamper with, so it's not actually of any use, if you want to play with other kernels. Another reason is, that /proc/config.gz (or it's equivalent from /boot/config-2.6.nn-x.y-flavor) doesn't provide any other "flavors". So FWIW, I like the idea of having the configs kept in kernel-source under /src/src/linux/config or any other name.
thanks,
greg k-h
Just my 2 ¢ ;-) Cheers. l8er manfred -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (5)
-
Greg KH -
Jan Engelhardt -
Jeff Mahoney -
Manfred Hollstein -
Michal Marek