From owner-freebsd-current@FreeBSD.ORG Sun Jun 27 07:49:17 2004 Return-Path: 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 88CC716A4CE for ; Sun, 27 Jun 2004 07:49:17 +0000 (GMT) Received: from sv07e.atm-tzs.kmjeuro.com (sv07e.atm-tzs.kmjeuro.com [193.81.94.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id C630543D45 for ; Sun, 27 Jun 2004 07:49:16 +0000 (GMT) (envelope-from k.joch@ctseuro.com) Received: from [192.168.2.30] (adsl.sbg.kmjeuro.com [62.99.198.46]) (authenticated bits=0)i5R7mdC3062122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 27 Jun 2004 09:48:40 +0200 (CEST) (envelope-from k.joch@ctseuro.com) Message-ID: <40DE7BD0.8080304@ctseuro.com> Date: Sun, 27 Jun 2004 09:48:32 +0200 From: "Karl M. Joch" Organization: CTS User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <20040626231221.GA11573@dragon.nuxi.com> <3949.1088292437@critter.freebsd.dk> <20040626.181218.21873777.imp@bsdimp.com> <20040626.182023.07659343.imp@bsdimp.com> In-Reply-To: <20040626.182023.07659343.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-CTS-SV07-Mailserver-Information: please visit www.ctseuro.com for further instructions. Protected by www.ctseuro.com X-CTS-SV07-Mailserver: Found to be clean X-CTS-SV07-Mailserver-From: k.joch@ctseuro.com X-Mailman-Approved-At: Sun, 27 Jun 2004 11:44:52 +0000 Subject: Re: HEADSUP: ibcs2 and svr4 compat headed for history X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sun, 27 Jun 2004 07:49:17 -0000 I think if one would ask the stable userbase there would be lot of different answers. like for me, i tell customers they have a long live, very stable OS for their servers where updates are easy and free and they can stay always with the latest release. now i got the problem that in the first step there was mails around, that the stallion drivers are removed from the source tree. so i had to tell a lot of customers they have to trash the stallion card they buyed because it was in the hardware compatibility list. most was mad, because they have invested the hardware after changing their systems from SCO to FreeBSD (we replaced a lot of them). Now I have to tell them "Great, you trashed the cards (not alot of them have), but you have to stay at 4.x because the software (ERP/Financial/Billing) we moved from SCO to FreeBSD with IBCS Emulation doesnt work on 5.x". No, I am not able to maintain the moduls because i am not a good enough programmer. If that would be the case i would have adapted the stallion stl driver. Flame me if you like, but from a users/intergrators point of view breaking the backward compatibility that way is really worse for the public image of the OS. And the answer "you are free to stay with 4.x" is not an answer acceptable for customers. -- Best regards / Mit freundlichen Gruessen, Karl M. Joch