From owner-freebsd-current@FreeBSD.ORG Fri Aug 18 08:30:10 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A55B616A4DF for ; Fri, 18 Aug 2006 08:30:10 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF17D43D46 for ; Fri, 18 Aug 2006 08:30:09 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5DEEC.dip.t-dialin.net [84.165.222.236]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.6/8.13.6) with ESMTP id k7I8DK8j092797; Fri, 18 Aug 2006 10:13:21 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.4/8.13.3) with ESMTP id k7I8UCI7023856; Fri, 18 Aug 2006 10:30:12 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from psbru.cec.eu.int (psbru.cec.eu.int [158.169.131.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Fri, 18 Aug 2006 10:30:11 +0200 Message-ID: <20060818103011.1w8c9mn88w800kwg@netchild.homeip.net> X-Priority: 3 (Normal) Date: Fri, 18 Aug 2006 10:30:11 +0200 From: Alexander Leidinger To: Astrodog References: <20060815212143.G45647@fledge.watson.org> <20060816090653.GA820@turion.vk2pj.dyndns.org> <20060816132539.owwerbnw0okwc8wo@netchild.homeip.net> <20060817080533.GA845@turion.vk2pj.dyndns.org> <20060817122534.e57aqlbrwwogg8ko@netchild.homeip.net> <44E4454B.2080606@elischer.org> <20060817133721.h4cbucizcw8wc88k@netchild.homeip.net> <20060817140122.GA90642@stud.fit.vutbr.cz> <44E4881A.3050907@elischer.org> <20060817164352.GB96801@stud.fit.vutbr.cz> <2fd864e0608171556o6af3e1fdxa29c252f07c98444@mail.gmail.com> In-Reply-To: <2fd864e0608171556o6af3e1fdxa29c252f07c98444@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: Divacky Roman , current@freebsd.org Subject: Re: HEADS-UP: starting to commit linuxolator (SoC 2006) changes... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Aug 2006 08:30:10 -0000 Quoting Astrodog (from Thu, 17 Aug 2006 17:56:10 -0500)= : > On 8/17/06, Divacky Roman wrote: >> >> On Thu, Aug 17, 2006 at 08:15:38AM -0700, Julian Elischer wrote: >>> Divacky Roman wrote: >>> >>> >>Anyone with interest in this is free to take care of this, as long as >>> >>they coordinate with the people which work on the current >>> >>infrastructure on emulation@ regarding the userland/security stuff and >>> >>the kernel. Until someone stands up and shows results/progress, this >>> >>is scheduled to vanish in the future. >>> >> >>> >> >>> > >>> > >>> >I personally see this 3 possible ways: >>> > >>> >1) leave it as it is (ie. as what will be commited shortly), this means >>> >runtime >>> >checking for osrelease sysctl and behaving according to it >>> > >>> >2) introduce option LINUX_24 or something like that to make this a >> compile >>> >time build >>> > >>> >3) remove the 2.4 completely saying that "if you want 2.4 emulation >>> >downgrade fbsd as well". notice that this is 100% ok because linux >> itself >>> >doesnt support 2.4 emulation on 2.6 kernel. >>> > >>> > >>> >>> I think that would be a great selling point.. especially if two >>> processes could run the different releases at the same time.. >>> "even linux needs vmware to do this..". >> >> this is not hard to implement but remeber that it causes getpid() to be >> quite expensive function. and as netchild said - newer glibc doesnt work >> with >> 2.4 kernel so unless somone is willing to maintain libc for the old >> linux_base >> there wont be any use for this. > > > Would it be possible to maintain 2 sets? Basically, leave the old stuff > avalible, but require some sysctl or compile-time setting to use it... if > no one steps up to maintain it, let it rot. If someone wants to deal with > it... let 'em! Don't think about the kernel part. There are multiple ways of handling =20 it. You could even move the 2.4 code to "linux24" and brandelf only =20 some apps with "Linux24" instead of "Linux". This way you don't need =20 to check every time and you don't need to do a sysctl for the apps in =20 question. The kernel is the easy part. The hard part is the userland =20 stuff. As one of two active people which take care of the linux =20 userland infrastructure in ports I can tell you that we just have the =20 official man power to maintain one linux_base infrastructure. And this =20 doesn't take into account that old linux_base ports which still work =20 with 2.4 but will go away in the future and that the linux =20 distributors don't fix security bugs in old releases (so we have to =20 move on to newer linux binaries and remove the old ones). The =20 person(s) taking care about the linux24 stuff would have to create =20 binary packages with fixes for this himself. Bye, Alexander. --=20 A political man can have as his aim the realization of freedom, but he has no means to realize it other than through violence. =09=09-- Jean Paul Sartre http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137