Re: kern.version and uname -v

I personally feel that building releases reproducibly is quite important. How can we trust the current 14.0-RELEASE images? Would be nice to be able to build them locally and know they are the same. What do we need to do to make sure that 14.1-RELEASE is built reproducibly? Thanks! PS: It look

Re: kern.version and uname -v

On Mon, Jan 8, 2024 at 7:17 PM Eugene Grosbein wrote: > 09.01.2024 4:16, Warner Losh wrote: > > > On Mon, Jan 8, 2024 at 1:58 PM Eugene Grosbein > wrote: > > For ages, "uname -v" output (sligtly polished sysctl kern.version) > had the following format: > > $ un

Re: kern.version and uname -v

09.01.2024 4:16, Warner Losh wrote: > On Mon, Jan 8, 2024 at 1:58 PM Eugene Grosbein > wrote: > For ages, "uname -v" output (sligtly polished sysctl kern.version) had > the following format: > $ uname -v > FreeBSD 13.2-STABLE 36a037f15 KERNELIDENT > > This

Re: kern.version and uname -v

Hi, > On 8 Jan 2024, at 22:16, Warner Losh wrote: > > This is the old, non-reproducible format. We've had both formats for several > major releases, and this format, with various tweaks as we went from CVS -> > svn -> git. > > Maybe the problem here is that in the run up to 14.0 we didn't tur

Re: kern.version and uname -v

On Mon, Jan 8, 2024 at 1:58 PM Eugene Grosbein wrote: > Hi! > > For ages, "uname -v" output (sligtly polished sysctl kern.version) had the > following format: > $ uname -v > FreeBSD 13.2-STABLE 36a037f15 KERNELIDENT > This is the reproducible format: only include data that is identical from buil

kern.version and uname -v

Hi! For ages, "uname -v" output (sligtly polished sysctl kern.version) had the following format: $ uname -v FreeBSD 13.2-STABLE 36a037f15 KERNELIDENT Where KERNELIDENT is GENERIC for x86 distribution media. But now: # uname -v FreeBSD 14.0-RELEASE #0 releng/14.0-n265380-f9716eee8ab4: Fri Nov 1