From owner-freebsd-hackers Thu Mar 1 6:47:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (adam042-060.resnet.wisc.edu [146.151.42.60]) by hub.freebsd.org (Postfix) with ESMTP id AB31537B719 for ; Thu, 1 Mar 2001 06:47:47 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 3547 invoked by uid 1000); 1 Mar 2001 14:47:46 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Mar 2001 14:47:46 -0000 Date: Thu, 1 Mar 2001 08:47:46 -0600 (CST) From: Mike Silbersack To: Robert Watson Cc: Ken Bolingbroke , , Subject: Re: FreeBSD on S/390? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Mar 2001, Robert Watson wrote: > Part of the "real answer" is probably that IBM or a large consumer of > S/390 machines has to shepherd the whole process to make it happen, and > that probably involves a moderate amount of money, and moderate levels of > frustration. If you can provide access to the first and survive the > second, then you can certainly make this a reality. If not, well, it > would be nice to see it happen but the task is to identify someone who can > provide these. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services If memory serves me right, the way Linux S/390 support came about was that a team of S/390 enthusiasts start working on an S/390 port. After a year or so, they were almost done. At this point an internal IBM team submitted a set of patches that they had been working on, supplanting the efforts of the enthusiast team. Hence, perhaps the best approach is just to do a really good job of making it look like a FreeBSD S/390 port is being done. If this is successfully pulled off, IBM will actually end up doing the real work. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message