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]
Date:	Wed, 31 Aug 2011 16:49:13 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Francis Moreau <francis.moro@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: make silentoldconfig question

On 23.8.2011 10:47, Francis Moreau wrote:
> Hello,
> 
> I'm a bit confused about silentoldconfig target since it doesn't
> really makes any differences with oldconfig.

silentoldconfig is a historical misnomer, nowadays oldconfig is silent
as well. The purpose of silentoldconfig is to generate include/config/*
and include/generated/autoconf.h files before build starts, oldconfig is
the user interface.

> The only difference I found is this one: if I add a new valid symbol
> at the end of my .config (therefore the position of the symbol is
> incorrect) then olconfig will recreate the .config and thus print its
> annoying message "# config written ..." to stdin whereas
> silentoldconfig won't print anything not because it's silent but
> beacuse the .config is not recreated so the symbol is still badly
> located at the end of the file.

Yes, silentoldconfig does not touch .config if no symbol changed. The
user interfaces always save the .config file.

Michal

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ