From owner-freebsd-hackers Tue Nov 7 23:57:11 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA26406 for hackers-outgoing; Tue, 7 Nov 1995 23:57:11 -0800 Received: from werple.net.au (0@werple.mira.net.au [203.9.190.18]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA26401 for ; Tue, 7 Nov 1995 23:57:08 -0800 Received: from cimaxp1.UUCP (Ucimlogi@localhost) by werple.net.au (8.7/8.7.1) with UUCP id SAA22790 for hackers@freebsd.org; Wed, 8 Nov 1995 18:35:05 +1100 (EST) Message-Id: <199511080735.SAA22790@werple.net.au> X-Authentication-Warning: werple.net.au: Ucimlogi set sender to cimaxp1!jb using -f Received: by cimaxp1.cimlogic.com.au; (5.65/1.1.8.2/10Sep95-0953AM) id AA03128; Wed, 8 Nov 1995 18:38:37 +1100 From: John Birrell Subject: Re: ideas from netbsd To: lambert.org!terry@werple.net.au (Terry Lambert) Date: Wed, 8 Nov 1995 18:38:36 +1100 (EST) Cc: hackers@freebsd.org, jb@cimlogic.com.au In-Reply-To: <199511080537.WAA19254@phaeton.artisoft.com> from "Terry Lambert" at Nov 7, 95 10:37:58 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org Precedence: bulk > > Hardly! Building a FreeBSD thread-safe library gives you a > > thread-safe library and JAVA. Implementing NetBSD support to give you > > JAVA gives you only JAVA. I don't think it takes a rocket scientist > > to figure out that "1 + 1 = 2" and "1 + 0 = 1" > > Building a FreeBSD thread-safe library gives you a thread-safe library. Sigh.... Yes! So? > > Taking NetBSD's work after it's done gives you a thread-safe library. Where is the thread-safe NetBSD library? It's not _in_ NetBSD at the moment is it? Has there been an announcement that it will be in 1.2? In private mail the other day, CAP said he's talking to NetBSD about making their libc thread safe (like we're doing to FreeBSD's libc). > > I don't think it takes a rocket scientist to see the duplication of > effort in doing the same thing twice. ;-). So that would be 2 * 1 = 2? Just checking. 8-). Well I'm certainly no rocket scientist, but if FreeBSD gets a thread safe version of libc before NetBSD even _agrees_ to make their libc thread safe, then who's duplicating effort. If NetBSD had a thread safe libc, I wouldn't be putting my time into doing it for FreeBSD. We've got a local NetBSD thread safe libc (for i386 & Alpha), but this means we have to maintain a _lot_ of code because it isn't easy to get things into NetBSD. Please don't use the issue of threads to justify adding COMPAT_NETBSD. Apart from threads, what is it about JAVA that means that FreeBSD should have COMPAT_NETBSD? So, having said all that, and having listened to argument for the sake of argument, I can't see that FreeBSD has anything to gain by adding some sort of NetBSD compatibility. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > Now, if it were possible to build the FreeBSD libc for NetBSD, that'd save us a lot of grief. And then we'd probably find that 2 + 2 = 4, 2 * 2 = 4 _AND_ 2 ^ 2 = 4. 8-)>. -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 119 Cecil Street Ph +61 3 9690 9600 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137