Date: Thu, 15 Apr 2021 08:22:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254645] Build and publish official OCI images for FreeBSD releases Message-ID: <bug-254645-227-4y4bxCPmwb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254645-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254645 --- Comment #9 from Luca Pizzamiglio <pizzamig@freebsd.org> --- (In reply to Samuel Karp from comment #5) FreeBSD versioning follows (or at least tries to) semantic versioning at system-call level. A binary built for FreeBSD 12.1 will run on FreeBSD 12.1+, but there are no guarantees that it can work on FreeBSD 12.0 or 11.x In FreeBSD 12.2 new system calls can be added, but no breaking changes are introduced. In FreeBSD 13.0 new system calls can be added, but also potential breaking changes, like struct definitions passed in system calls and so on. However, in FreeBSD 13.0 there are compatibility layers to support FreeBSD 12.x ABI (and all the previous version of FreeBSD, you can run binaries from FreeBSD 4 on FreeBSD 13 if you want). That's why it's extremely important for a OCI image to have its FreeBSD version, to allow the runtime to chose the correct/compatible image to download/run. A FreeBSD 12.2 host won't use a FreeBSD 13.x image, but it can use a 11.4 or a 12.1 one (packages are build following a similar approach, one repo per major release). -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254645-227-4y4bxCPmwb>