Date: Tue, 20 Jun 1995 07:39:07 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: rpt@miles.sso.loral.com (Richard Toren) Cc: hackers@freebsd.org Subject: Re: bringing up freebsd 2.0.5 Message-ID: <199506200539.HAA14510@uriah.heep.sax.de> In-Reply-To: <Pine.SUN.3.91.950619213712.8533A-100000@miles> from "Richard Toren" at Jun 19, 95 09:39:36 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Richard Toren wrote: > [2.0R binaries working under 2.0.5R] > 3? Will programs that look into the kernel (xcpustate, xmeter, lsof, Those are usually the only programs potentially affected. You can never know which internal kernel structure might change between releases, hence no forecast for 2.1R. :-) (Though, given the current policy of only selected bug fixes being accepted for 2.1, it's unlikely that 2.0.5 and 2.1 will differ.) The (known) offenders between 2.0 and 2.0.5 are all routing binaries. True userland programs will always continue to run; the worst they need is another set of shared libraries (the compatXXX distributions). And, of course (alwost no longer worth to mention), confi(8) is heavily dependend on the kernel tree. It's usually changed about 5 times or more between major releases, so you have to make sure that you're config'ing your kernel with the right config binary. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506200539.HAA14510>