Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Mar 2010 12:19:32 -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.121932.997044077387131740.imp@bsdimp.com>
In-Reply-To: <20100313170725.GW8200@hoeg.nl>
References:  <20100313090844.GV8200@hoeg.nl> <20100313.090709.407454645627448944.imp@bsdimp.com> <20100313170725.GW8200@hoeg.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20100313170725.GW8200@hoeg.nl>
            Ed Schouten <ed@80386.nl> writes:
: * M. Warner Losh <imp@bsdimp.com> wrote:
: > 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.
: 
: Hmmm... Indeed.
: 
: I thought a bit more about this and I realized it would be better if we
: wouldn't use a FreeBSD major number for this, but the actual
: __FreeBSD_version.

Hmmm, that might be harder.  The problem is that when I want to run a
program from FreeBSD 3.0, I may need an interface that was in 3.0, but
was removed prior to 5.0 shipping.  This means the kernel needs the
COMPAT_FREEBSD4 option right now to work.  So things are kind of
confusing.

Under your plan, which __FreeBSD_version would we use here?

The COMPAT_FREEBSD_BACK_TO=3 would be the right setting here.  This
may pick up a little extra junk, but would be clear to the user what
they are configuring.

Comments?

Warner



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