From owner-freebsd-current Thu May 2 10:16:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA10984 for current-outgoing; Thu, 2 May 1996 10:16:56 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA10975 for ; Thu, 2 May 1996 10:16:53 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uF1zZ-0003wBC; Thu, 2 May 96 10:16 PDT Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.7.5/8.6.12) with SMTP id RAA00273; Thu, 2 May 1996 17:16:28 GMT X-Authentication-Warning: critter.tfs.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Christoph P. Kukulies" cc: freebsd-current@freefall.FreeBSD.org Subject: Re: LINUX COMPAT_LINUX In-reply-to: Your message of "Thu, 02 May 1996 17:22:27 +0200." <199605021522.RAA14992@gilberto.physik.rwth-aachen.de> Date: Thu, 02 May 1996 17:16:24 +0000 Message-ID: <271.831057384@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I saw Poul-Henning talking about COMPAT_LINUX and such > but didn't pay attention. Maybe I should have :-) :-) > What was that LINUX option initially good for? Obviously it is > disturbing now. I'ts renamed to COMPAT_LINUX, which I'm told is also bad, but at least it doesn't break the compile of the kernel. It may change name again if COMPAT_LINUX is too bad for compatibility... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.