linux-kernel - Re: installing only the newly (re)built modules

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] [day] [month] [year] [list]

Message-ID: <45A6104F.4090207@imap.cc>
Date:	Thu, 11 Jan 2007 11:24:15 +0100
From:	Tilman Schmidt <tilman@...p.cc>
To:	Bill Davidsen <davidsen@....com>
CC:	Linux Kernel mailing List <linux-kernel@...r.kernel.org>
Subject: Re: installing only the newly (re)built modules

Bill Davidsen schrieb:
> Alexy Khrabrov wrote:
>> The 2.6 build system compiles only those modules whose config
>> changed.  However, the install still installs all modules.
>> 
>> Is there a way to entice make modules_install to install only those
>> new modules we've actually just changed/built?
> 
> Out of curiosity, why? I've noticed this, but the copy runs so fast I 
> never really thought about it as an issue.

Not here. On the 933 MHz P3 machine I use for driver development,
"make modules_install" takes so much time that I always copy my
modules by hand instead after recompiling them.

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)