[talk] FreeBSD question: uname info versus svn commit versus __FreeBSD_version define

[James E Keenan]

On 09/08/2016 03:09 PM, Steven Kreuzer wrote:
> Hi James-
>
>> On Sep 8, 2016, at 2:56 PM, James E Keenan <jkeen at verizon.net> wrote:
>>
>> I am trying to determine whether a particular snapshot of FreeBSD contains code which was committed for the purpose of fixing a bug which I helped to report.
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211743#c10 states:
>>
>> #####
>> Based on __FreeBSD_version define the fix is in:
>> 1200004 and up
>> 1100502 >= version < 1200000
>> 1003507 >= version < 1100000
>> #####
>>
>> I have installed a Virtual Box holding a FreeBSD whose 'uname -a' information is as follows:
>>
>> #####
>> FreeBSD  12.0-CURRENT FreeBSD 12.0-CURRENT #0 r305028: Mon Aug 29 22:45:29 UTC 2016 root at releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>> #####
>>
>> How can I determine whether that version of FreeBSD is recent enough to have included the code correction?
>
> This info is exposed via sysctl
>
> $ sysctl -n kern.osreldate
> 1200005

Thanks, Steven, that worked for me and enabled me to move forward.

>
> Also, you can look at Chapter 16 in the porter's handbook that documents each value of __FreeBSD_versions going back to 2.0-RELEASE
>
> https://www.freebsd.org/doc/en/books/porters-handbook/versions.html <https://www.freebsd.org/doc/en/books/porters-handbook/versions.html>
>

AAMOF, the very last release listed there, 1200004, was for the bug I 
helped to report.

I have one more, different question related to this VM installation, but 
I have written it up at: 
http://stackoverflow.com/questions/39402547/freebsd-dhclient-setting-not-retained-upon-reboot, 
should anyone want to take a crack at it.

Thank you very much.
Jim Keenan