On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote: > On Wed, 19 Oct 2005 23:10:46 +0200, dick hoogendijk <[EMAIL PROTECTED]> wrote: > > >On Mon, 17 Oct 2005 15:52:00 -0400 > >Vivek Khera <[EMAIL PROTECTED]> wrote: > > > >>On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote: > > > >>> The *ONLY* question is: will I need to *recompile* all installed > >>> ports if I go from 5.4 to 6.0 release? > >> > >>No, the kernel has COMPAT_FREEBSD5 and COMPAT_FREEBSD4 by default, > >>so just keep those and your shared libs around and you're golden. > >>Of course, ports like lsof which dependon the kernel version will > >>have to be rebuilt, but that's true no matter the version change... > > > >I get contradicting advice. You tell me I'm golden 'cause of the > >compat_xx settings; others tell me it's way better to *recompile* all > >portsto get the cleanest system. > > > >Wat is the best way to get the cleanest FreeBSD-6.x system without > >installing from scratch? Recompile each port? Or use the > >COMPAT_FREEBSD5 layer? > > You are answering your own question I think. > Does the term COMPAT_FREEBSD5 sound as the 'cleanest FreeBSD-6.x'? No. You > get the cleanest system by recompiling all ports. (portupgrade -fa is your > friend here.) > > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications. If you > have them it's ok. If you recompile everything you don't need the > COMPAT_FREEBSD5 stuff. If you don't have the source of some of your > FreeBSD-5 applications you have to run with COMPAT_FREEBSD5. > And the switch to 6 is easier because your 5-applications keep running.
Yes. As long as you only use your old 5.x applications, you're fine with just the compat. The problem is when you start to link *new* 6.0 applications with *old* 5.x libraries (e.g. by installing a new port, e.g. a new X application, without rebuilding your 5.x X installation first). Thus, unless you upgrade all your 5.x ports (well, actually "many", i.e. only those that provide libraries or shared object modules, but it's easier to just do "all") you'll end up with 6.0 binaries that are linked to e.g. two versions of libc at once (the 5.x libc and the 6.0 libc), which is a recipe for disaster. Kris
pgpgvSsVLKo0G.pgp
Description: PGP signature
