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: <20120623025520.GB18260@kroah.com>
Date:	Fri, 22 Jun 2012 19:55:20 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Chris Jones <chrisjones@...n.net.au>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Custom kernel version numbers

On Sat, Jun 23, 2012 at 08:25:30AM +1000, Chris Jones wrote:
> Is there a general rule against giving a version number to a custom
> kernel if credit is given to the base kernel version?

You have the code, you can number it however you want.

But, if you want others to have some clue as to what kernel you are
running for whatever reason (support, community help with problems,
etc.) I would recommend using the kernel.org release numbers and adding
onto that like all of the major Linux distros do already.

What were you thinking of numbering your kernel?

greg k-h
--
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