From owner-freebsd-hackers Mon Dec 18 00:37:05 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA11277 for hackers-outgoing; Mon, 18 Dec 1995 00:37:05 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA10998 Mon, 18 Dec 1995 00:31:35 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (134.100.239.2) with smtp id ; Mon, 18 Dec 95 09:28 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for hackers@FreeBSD.org id ; Mon, 18 Dec 95 09:28 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA01417; Mon, 18 Dec 95 09:17:38 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9512180817.AA01417@wavehh.hanse.de> Subject: Re: FreeBSD-current-stable ??? To: Andreas@wavehh.hanse.de, Klemm@wavehh.hanse.de, Date: Mon, 18 Dec 1995 09:17:37 +0100 (MET) Cc: current@FreeBSD.org, hackers@FreeBSD.org, jkh@FreeBSD.org Reply-To: cracauer@wavehh.hanse.de X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org Precedence: bulk As I am the one who is named here, let me just clarify what my position is. I couldn't decide whether running NetBSD or FreeBSD is the better system for my work. I wrote down some of the experiences and made them available by WWW. In this document, I explained that one reason I feel more comfortable with NetBSD for now is that I can have one machine running -current for production use. Every problem I encounter can be fixed on that machine and the fix can be brought back into -current (actually, the NetBSD community is quite active in those system parts I encounter problems in and most problems are fixed before I get my diffs ready). Or in other words, NetBSD makes it easier to engage in a useful way without investing too much time, while engaging in FreeBSD would require more work (but possibly pay back more). I think the way FreeBSD organizes things by now is just right for their (your, our) needs. Having only one source tree as NetBSD does (ok, sort of) is not an option because much more modifications are done and one experimental vehicle is needed. I don't see how having a third source tree could help, since I can't imagine a mechanism to keep the "middle" one (that one that could qualify for production use) to the stability that is needed. The NetBSD way of organizing development just doesn't fit what I think FreeBSD is. The URL of the comparison is http://www.leo.org/pub/comp/os/bsd/cracauer/ The document is available in German language only. I consider the German version a "beta test", with the options of either translating it after some people looked over it or to remove it if I have to take too much heat. BTW, I'm just snarfing FreeBSD-current to get an own impression of how stable it is. I'm pretty sure, though, that it is usable, but not as usable for a production system as NetBSD-current is. Happy Hacking Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer - Fax +49 40 522 85 36 BSD User Group Hamburg, Germany - No NeXTMail anymore, please. Copyright 1995. Redistribution via Microsoft Network is prohibited