From owner-freebsd-questions@FreeBSD.ORG Mon Feb 7 19:23:10 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B9C916A4CE for ; Mon, 7 Feb 2005 19:23:10 +0000 (GMT) Received: from smtp9.wanadoo.fr (smtp9.wanadoo.fr [193.252.22.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2FFC43D5A for ; Mon, 7 Feb 2005 19:23:09 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0908.wanadoo.fr (SMTP Server) with ESMTP id E03F11C00138 for ; Mon, 7 Feb 2005 20:23:08 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf0908.wanadoo.fr (SMTP Server) with ESMTP id B6F2A1C0012B for ; Mon, 7 Feb 2005 20:23:08 +0100 (CET) X-ME-UUID: 20050207192308749.B6F2A1C0012B@mwinf0908.wanadoo.fr Date: Mon, 7 Feb 2005 20:22:55 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <858264590.20050207202255@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <20050207171702.GP21722@thingy.apana.org.au> References: <200502061420.24415.krinklyfig@spymac.com> <849739867.20050207170757@wanadoo.fr> <20050207161015.GH21722@thingy.apana.org.au> <399973539.20050207171622@wanadoo.fr> <20050207163645.GK21722@thingy.apana.org.au> <351293826.20050207175318@wanadoo.fr> <20050207171702.GP21722@thingy.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: favor X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2005 19:23:10 -0000 David Gerard writes: DG> Actually, I most profitably apply it in my day job, which is administering DG> Solaris ;-) The purpose of vendors is to say to your boss that you have an DG> SLA; getting actual *support* out of anyone (with exceptions like NetApp) DG> is something best avoided IME. Sometimes you need support quickly, more quickly than you can manage on your own ... especially for mission-critical servers. That's when a complete formal support structure becomes invaluable. And that's what is missing from most open-source software, including FreeBSD. DG> Corporate arse-covering rather than actual support, but yeah. I am DG> told the horrible tale of a friend who is having to shift a pile of DG> servers from FreeBSD to Red Hat because Red Hat have SLAs and they DG> couldn't find sufficiently corporate-looking support for FreeBSD DG> that did. Exactly. You can run FreeBSD in these environments IF you have highly qualified in-house personnel to maintain it. It doesn't matter how reliable FreeBSD is, you need _someone_ who can fix it in an emergency. And if no such person is available with a phone call outside your organization, you need the expertise in-house. And if you don't have it in-house, you can't use FreeBSD. Linux is only marginally better. You need an external support organization with extremely competent technicians that has agreed to provide you with some specific level of support, such that they risk a lawsuit if they don't cough up when you call. Then you get support. DG> The trick will be to get organisations offering SLAs interested in the DG> program. Even then the fact that it's hard to undercut $0 is a powerful DG> factor in its spread. Getting those organizations interested in open source will effectively negate most of the advantages of open source. You'll be paying someone for your software again, and you'll be dependent on them again, and you'll be using their proprietary solutions ... again. DG> Realistically: a FreeBSD mailing list copyright apocalypse is not DG> likely. True. But it only takes one lawsuit to wipe out the entire project. -- Anthony