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: <9a8748490804231543h1203ff59i466e1ea9c02af0f2@mail.gmail.com>
Date:	Thu, 24 Apr 2008 00:43:51 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"devzero@....de" <devzero@....de>
Cc:	linux-kernel@...r.kernel.org, agruen@...e.de
Subject: Re: make cloneconfig ?

On 24/04/2008, devzero@....de <devzero@....de> wrote:
> any reason why "make cloneconfig" never made it into mainline?
>
>  many people are quite used to it and every time i build vanilla kernel i step into that trap  "oh - that`s a suse`ism"
>
>  make cloneconfig exists since /proc/config.gz - but while that one went into mainline, cloneconfig never did.
>
>  anyone know the reason for that ?
>
>  i wished, distros kernels were more similar to vanilla kernels - so what about making them more similar ?
>
>

Isn't "cloneconfig" basically just "zcat /proc/config.gz > .config &&
make oldconfig" ???   If so, why do we need yet another "make
<some_target>" Makefile rule? What would actually be gained?

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
--
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