Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Aug 2006 12:25:34 +0200
From:      Alexander Leidinger <Alexander@Leidinger.net>
To:        Peter Jeremy <peterjeremy@optushome.com.au>
Cc:        current@freebsd.org
Subject:   Re: HEADS-UP: starting to commit linuxolator (SoC 2006) changes...
Message-ID:  <20060817122534.e57aqlbrwwogg8ko@netchild.homeip.net>
In-Reply-To: <20060817080533.GA845@turion.vk2pj.dyndns.org>
References:  <44E1BD03.2030402@FreeBSD.org> <20060815144625.362bf376@Magellan.Leidinger.net> <44E1C3E4.7080508@FreeBSD.org> <20060815153451.604d16f1@Magellan.Leidinger.net> <44E1E85D.5070805@FreeBSD.org> <20060815180713.6a4ee2e6@Magellan.Leidinger.net> <20060815212143.G45647@fledge.watson.org> <20060816002328.365a14cd@Magellan.Leidinger.net> <20060816090653.GA820@turion.vk2pj.dyndns.org> <20060816132539.owwerbnw0okwc8wo@netchild.homeip.net> <20060817080533.GA845@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Peter Jeremy <peterjeremy@optushome.com.au> (from Thu, 17 Aug =20
2006 18:05:33 +1000):

> On Wed, 2006-Aug-16 13:25:39 +0200, Alexander Leidinger wrote:
>> Quoting Peter Jeremy <peterjeremy@optushome.com.au> (from Wed, 16 Aug
>> 2006 19:06:53 +1000):
>>
>>> On Wed, 2006-Aug-16 00:23:28 +0200, Alexander Leidinger wrote:
>>>> For the curious ones: the code is "activated" by changing osrelease,
> ...
>> It's mentioned in /usr/ports/UPDATING (as in: make sure you don't
>> change the default osrelease).
>
> I found it by grepping for osrelease.  The comment is buried in
> the FC4 update and not immediately obvious.  I was thinking of
> it being documented in (eg) linux(4).

Yes, it is mentioned for those which did change it back in the days =20
where it didn't changed anything in glibc and updated to fc4. lang/icc =20
was a bit picky about the compat.linux.* sysctls a little bit longer.

Anyone with enough mdoc-fu listening for the linux(4) change?

>> The intend is to change the default value to 2.6.x when the code is
>> stable enough.
>
> What is the plan for the 2.4.x code?  Will it be maintained (in which
> case, this should be documented), left to rot or explicitly deleted?

The 2.6 code is an extension to the 2.4 code. The 2.6 one is needed =20
for newer FC releases. So the current sysctl stuff is just a disabling =20
of some code in some syscalls. The goal is get stable 2.6 extensions =20
and to forget about the 2.4 downgrade (removing the part which =20
disables some stuff currently, the rest is needed).

So no need to document the effects of some specific values for =20
osrelease, it's enough to say that only the default is supported, a =20
non default value may cause unwanted behavior and bugreports should be =20
submitted with default values.

Bye,
Alexander.

--=20
If you pick up a starving dog and make him prosperous, he will not
bite you; that is the principal difference between a dog and a man.
=09=09-- Mark Twain

http://www.Leidinger.net    Alexander @ Leidinger.net: PGP ID =3D B0063FE7
http://www.FreeBSD.org       netchild @ FreeBSD.org  : PGP ID =3D 72077137




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