On Sun, Mar 05, 2023 at 02:04:44PM +0100, Thorsten Leemhuis wrote:
> + * Create the build configuration for your kernel based on an existing
> +   configuration.
> +
> +   If you already prepared such a '.config' file yourself, copy it to
> +   ~/linux/ and run ``make olddefconfig``.
> +
> +   Use the same command, if your distribution or somebody else already tailored
> +   your running kernel to your or your hardware's needs: the make target
> +   'olddefconfig' will then try to use that kernel's .config as base.
> +
> +   Using this make target is fine for everybody else, too -- but you often can
> +   save a lot of time by using this command instead::
> +
> +     yes "" | make localmodconfig
> +
> +   This will try to pick your distribution's kernel as base, but then disable
> +   modules for any features apparently superfluous for your setup. This will
> +   reduce the compile time enormously, especially if you are running an
> +   universal kernel from a commodity Linux distribution.
> +
> +   There is a catch: the make target 'localmodconfig' will disable kernel
> +   features you have not directly or indirectly through some program utilized
> +   since you booted the system. You can reduce or nearly eliminate that risk by
> +   using tricks outlined in the reference section; for quick testing purposes
> +   that risk is often negligible, but it is an aspect you want to keep in mind
> +   in case your kernel behaves oddly.

If your distro config have ``CONFIG_IKCONFIG=y``, you can copy from
procfs::

    zcat /proc/config.gz > .config

If it isn't the case, you may want to enable the aforementioned config
option.

Thanks. 

-- 
An old man doll... just what I always wanted! - Clara