From owner-freebsd-ports Thu Nov 14 20:59:23 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA13014 for ports-outgoing; Thu, 14 Nov 1996 20:59:23 -0800 (PST) Received: from ingenieria ([168.176.15.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA12955 for ; Thu, 14 Nov 1996 20:59:11 -0800 (PST) Received: from unalmodem.usc.unal.edu.co by ingenieria (SMI-8.6/SMI-SVR4) id XAA12281; Thu, 14 Nov 1996 23:59:14 +0600 Message-ID: <328C1D5A.5A94@ingenieria.ingsala.unal.edu.co> Date: Thu, 14 Nov 1996 23:35:54 -0800 From: "Pedro Giffuni S." Reply-To: pgiffuni@fps.biblos.unal.edu.co Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 3.0 (Win16; I) MIME-Version: 1.0 To: ports@freebsd.org Subject: Re: [comp.os.linux.announce] .... Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bakul Shah wrote: > > > What would make sense (from a software developer's point of view) is > for key FreeBSD developers to work with key LINUX developers and > come up with a common interface (beyond POSIX). [Add to taste > statements like `Free OS people can only help themselves and their > users by uniting. The enemy is not another free OS but M$. ....'] > I donīt think LINUX guys will help, they already have much work defining their own standards :(, in fact many commercial providers dislike LINUX because of their multiple distributions. POSIX is an important first step because it applies to commercial and non-commercial UNIX. A good strategy would be a "certification seal" under FreeBSD (fight using MS weapons ?): if the app runs under fbsdīs Linux emulation it will probably run under any Linux, besides most users will want to know which apps will run under FreeBSD before buying them. Pedro.