From owner-freebsd-hackers Sun Jan 26 17:35:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA10163 for hackers-outgoing; Sun, 26 Jan 1997 17:35:34 -0800 (PST) Received: from llaic.univ-bpclermont.fr (llaic.univ-bpclermont.fr [192.54.142.163]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA10146 for ; Sun, 26 Jan 1997 17:35:22 -0800 (PST) Message-Id: <199701270135.RAA10146@freefall.freebsd.org> Received: by llaic.univ-bpclermont.fr (1.38.193.4/16.2) id AA28403; Mon, 27 Jan 1997 02:34:52 +0100 From: Roger Espel Llima Subject: Re: hackers-digest V3 #36 To: hackers@freefall.freebsd.org Date: Mon, 27 Jan 1997 02:34:51 +0100 (MET) In-Reply-To: <199701262133.NAA25596@freefall.freebsd.org> from "owner-hackers-digest@freefall.freebsd.org" at Jan 26, 97 01:33:06 pm X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am curious about the up and comming GNU 2.0 libc. Since the BSD's have > their own libc will you be replacing yours with the GNU one? Not that I > like GNU to much (it seams to be becomming the Microsoft of the free > software world) but it would save a lot of developement time if you > didn't have to worry about your own library. Since this the GNU libc > will be used by Linux it would be hard to go wrong. FreeBSD would be > using the same libc are it's chief competitor. FreeBSD would then only > have the userland commands to deal with, since Linux of course has GNU > maintaining those. Not only the userland commands -- what about the kernel? I don't really think FreeBSD should change to a completely different libc; the GNU libc has some very nice features (reentrancy...) but a system's libc is usually very closely tied to the kernel, so it's good that the same team (or almost...) develops both, as is the case with FreeBSD. > I hate GNU binutils. Really? GNU binutils are gcc, gas, ld and other related commands (nm, objdump...). Are you sure you don't mean GNU fileutils? (ls, cp, rm and all those). I personally like the GNU fileutils and their BSD equivalents pretty much the same. > The next question is. Is the GNU libc 2.0 being ported? I saw that > someone was doing a port for BSDI2.0, is this not the same as FreeBSD? A port for BSDi could probably be adapted very easily for FreeBSD. Even if it isn't used as the default libc, a port is always a good thing... > I am very interested the GNU libc 2.0 for its posix threads and the fact > that it is rentrant (which it has to be of course for threads). What is > the status of kernel-threads in FreeBSD? I heard that you where getting > there. Current kernels already support rfork(), which should be the basis for kernel threads just like clone() is under Linux. > Since you have linux compatibility (except for clone() right?) would it > not be possible to just use the GNU libc 2.0 the way it is? Does it ever > have to be ported? I am sure Linux will always have presidence with GNU > anyway. This of course looks really bad since eventually freebsd will > have linux's kernel calls. But think about it. It is only externel, just > as the GNU libc is externel. Is FreeBSD BSD without the BSD libc? Good > question. That just means that when Linux starts using GNU libc 2.0 (aka Linux libc 6.0), FreeBSD's linux compatibility libc will be changed to a copy of it. That isn't the one BSD commands use though, obviously. Roger -- e-mail: roger.espel.llima@ens.fr WWW page & PGP key: http://www.eleves.ens.fr:8080/home/espel/index.html