From owner-freebsd-current@freebsd.org Fri Jul 17 14:58:50 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3F659A415F for ; Fri, 17 Jul 2015 14:58:49 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id D22691228 for ; Fri, 17 Jul 2015 14:58:49 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 9F0269122 for ; Fri, 17 Jul 2015 14:58:42 +0000 (UTC) Message-ID: <55A91837.50805@freebsd.org> Date: Fri, 17 Jul 2015 10:59:03 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Kernel Application Binary Interface (kABI) support in FreeBSD References: <55A9157A.8050208@freebsd.org> In-Reply-To: <55A9157A.8050208@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="11KVqXa0W6UftsbFro4U7NwXj4IBUnq4D" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2015 14:58:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --11KVqXa0W6UftsbFro4U7NwXj4IBUnq4D Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-07-17 10:47, Julian Elischer wrote: > On 7/17/15 9:02 PM, Venkat Duvvuru wrote: >> Hi, >> >> Is there kABI (Kabi-whitelist) equivalent feature in FreeBSD? > well, yes and no. >=20 > Firstly, FreeBSD maintains a backwards compatible kABI (with the > exception of programs that hunt around in kernel memory). > We also use symbol versioning on the libc. so depending on what you wan= t > to do. the answer may be useful to you or not. > Basically any binary should continue to run on a newer kernel, even if > the syscalls change, because we should still support the old abi. >=20 > tell us more about what you need and we can be more specific. >=20 > I have run Freebsd 1.1 binaries on a Freebsd 8 system, in fact I have > done a system build in a freebsd 1.1 chroot on an 8 system. > I haven't tried it on 9 or 10 but I'd expect it to work.. >=20 >=20 >> >> >> >> Thanks, >> >> Venkat. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" >> >> >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" I think the question related to drivers (kernel modules). In which case, they should be compatible across major versions (module from 10.0 works in 10.2, but not 9.3 or 11.0) --=20 Allan Jude --11KVqXa0W6UftsbFro4U7NwXj4IBUnq4D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJVqRg7AAoJEBmVNT4SmAt+IWUP/3d5GjGawOLFitf690jR/Ucx ooYDon1j1Tg10gt8PY7eD2KsggAkYnQH3OI97Ym7bavf8pRk0o1MVkb6pwLP1qwU AXN0wqWP0M/1W00z5JLALNfIqKM3J9mhz8FMsdobSWihXVp5E5VONLifp8g3cnT2 Je7F85nh2SNr/yokc8fgX1qOCD5bRHGpNTK7SptaXtFlYHG0738f1bPMVOsKJBjR jW3B8rvoC4DBkDJmXt+2UPTYyl5ujknsKdHXiaLDTRnGDDNlKwxBi+4hR4cZOVSx 4FfB3nqPyEiE5GDNWH6U2Qy1zExGWFh/VBBcMSLImqneRmBQSfZH0lmn1UamZvWb 7An9Q86sdcJQZmYRacME3lnVxb0y0rcbCnx3fmdqkU9wVl8COIajCFEDs7Wj3YX5 TbYq3/JTDH2oqF62nPzYDFAh1+166h34xHiKY2te8fRaVcprRcWSnBhgPBziUn8R LlI0DjYvHVG73qdNsM/JUZS5Qr/ZPOc9Le5IBPSyIbZ2PB9y6MqfavZUPPfPSx9H DLsIFUg3R75owSPvm+kllUx+alU1TyqHBoloA17AgZgPj4NRVTCpJ+b3jUZt/vkw jcwvwgaT5vwlYfCWSN23dW1BroXNL0iyREjqUCWliQHNul9+zpgDUnqWkm7NxKIk +QsTFsn9w15Z5gUS0X4e =vJLy -----END PGP SIGNATURE----- --11KVqXa0W6UftsbFro4U7NwXj4IBUnq4D--