linux-kernel - Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2d1362fd-c109-1d8f-5954-3d60475ed907@gmail.com>
Date:   Tue, 7 Mar 2023 09:57:57 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Thorsten Leemhuis <linux@...mhuis.info>,
        Jonathan Corbet <corbet@....net>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        regressions@...ts.linux.dev
Subject: Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel

On 3/6/23 16:07, Thorsten Leemhuis wrote:
>> I think it depends whether someone would pick from /proc/config.gz or
>> /boot/config. My kernel configuration have CONFIG_IKCONFIG=y but I
>> often copy the config from the latter instead, since I booted with
>> arbitrary kernel version when compiling two or three versions, and I
>> want to ensure that the config used is from correct version (i.e.
>> I use /boot/config-5.15.x-string to build 5.15.x+1 kernel).
> 
> Well, I'd say for most users the file that was automatically picked up
> by olddefconfig/localmodconfig will be the right one. And for cases like
> yours there is already this in the text:
> 
> ```
> The make targets try to find the configuration for your running kernel
> automatically, but might choose poorly. A line like ‘# using defaults
> found in /boot/config-6.0.7-250.fc36.x86_64’ or ‘using config:
> ‘/boot/config-6.0.7-250.fc36.x86_64’ tells you which file they picked.
> If that is not the intended one, simply store it as ‘~/linux/.config’
> before using these make targets.
> ```
> 

Ah, I don't see that feature! Thanks anyway.

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