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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160406200532.GA12430@kroah.com>
Date:	Wed, 6 Apr 2016 13:05:32 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"Artem S. Tashkinov" <t.artem@...os.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: The most insane proposal in regard to the Linux kernel
 development

On Sat, Apr 02, 2016 at 05:43:47PM +0500, Artem S. Tashkinov wrote:
> One very big justification of this proposal is that core Linux development
> (I'm talking about various subsystems like mm/ ipc/ and interfaces under
> block/ fs/ security/ sound/ etc. ) has slowed down significantly over the
> past years so radical changes which warrant new kernel API/ABI are less
> likely to be introduced.

That's not true at all, the change is constant, and increasing, just
look at the tree for proof of that.

> Please, share your opinion.

Please read Documentation/stable_api_nonsense.txt for my opinion, and
that of the current developers.

If you don't agree with this, that's fine, you are welcome to fork the
kernel at any specific point and keep that api stable, just like many
companies do and make money from it (SuSE, Red Hat, etc.)

best of luck with your kernel project,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ