Copying .config to /lib/modules/`uname -r`/kernel

From: Pavel Roskin
Date: Fri Oct 24 2003 - 03:27:03 EST


Hello!

Many drivers are developed outside the kernel tree. Many drivers start
their existence as separate projects. It's essential that they are tested
by the users of particular hardware, even if those users don't want to
recompile their kernels.

There should be a standard place for .config in kernel packages.
/proc/config.gz may or may not be popular with distributors. Besides, it
only gives information for the currently running kernel, but not for e.g.
newly upgraded kernel before the reboot.

Cannot we just install .config to the same directory as modules? If the
kernel doesn't support modules, then there is no point to compile any new
modules against it. But if it does, then we can be sure that the modules
correspond to that configuration file, because the modules and .config
would be installed by the same command.

That's why I prefer the "kernel" subdirectory. It's fully replaced by
"make modules_install", so that the old .config will go away for sure.

Patch against 2.6.0-test8
=====================
--- Makefile
+++ Makefile
@@ -690,6 +690,7 @@
@rm -rf $(MODLIB)/kernel
@rm -f $(MODLIB)/build
@mkdir -p $(MODLIB)/kernel
+ @cp -f .config $(MODLIB)/kernel
@ln -s $(TOPDIR) $(MODLIB)/build
$(Q)$(MAKE) -rR -f $(srctree)/scripts/Makefile.modinst

=====================

--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/