Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Mar 2010 09:07:09 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        ed@80386.nl
Cc:        unixmania@gmail.com, svn-src-head@FreeBSD.ORG, svn-src-all@FreeBSD.ORG, src-committers@FreeBSD.ORG, nwhitehorn@FreeBSD.ORG
Subject:   Re: svn commit: r205014 - in head: . sys/amd64/amd64 sys/amd64/conf sys/amd64/include sys/amd64/linux32 sys/compat/freebsd32 sys/compat/ia32 sys/conf sys/fs/procfs sys/ia64/conf sys/ia64/ia64 sys/ia64/...
Message-ID:  <20100313.090709.407454645627448944.imp@bsdimp.com>
In-Reply-To: <20100313090844.GV8200@hoeg.nl>
References:  <201003111449.o2BEn6QY069179@svn.freebsd.org> <e71790db1003120436u34370f40x64a72da41893a39a@mail.gmail.com> <20100313090844.GV8200@hoeg.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20100313090844.GV8200@hoeg.nl>
            Ed Schouten <ed@80386.nl> writes:
: * Carlos A. M. dos Santos <unixmania@gmail.com> wrote:
: > COMPAT_FREEBSD32 is an unfortunate choice. It can be easily
: > interpreted as "compatible with FreeBSD 3.2".
: 
: That's no problem, since COMPAT_FREEBSD%d was already a misnomer. It
: would have been a lot better if it were replaced by a numerical
: definition:
: 
: options	COMPAT_FREEBSD_MAJOR=7

that sounds like a good idea.  But it isn't as simple as changing all
the COMPAT_FREEBSDX in the .c code.  There's also hooks in the syscall
glue generation that would be affected.

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100313.090709.407454645627448944.imp>