From owner-freebsd-current Mon Oct 6 22:59:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA29166 for current-outgoing; Mon, 6 Oct 1997 22:59:42 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA29159 for ; Mon, 6 Oct 1997 22:59:40 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id WAA00280; Mon, 6 Oct 1997 22:59:07 -0700 (PDT) Message-Id: <199710070559.WAA00280@rah.star-gate.com> To: Terry Lambert cc: gurney_j@resnet.uoregon.edu, luigi@labinfo.iet.unipi.it, freebsd-current@FreeBSD.ORG Subject: Re: how to detect different kernel code (select or poll) In-reply-to: Your message of "Mon, 06 Oct 1997 20:31:43 -0000." <199710062031.NAA24338@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Oct 1997 22:59:07 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I think that our current problem is that the poll code is not in 2.2 and whoever checked in the code should have at least thought of the incompatibility issues . One option is not to support 2.2 which the poll check in so far seems to imply at least with respect to drivers. The incompatibility inherent with the poll check in was deliberate to force the drivers to migrate to the new interface. A related issue is : what is the cut off point for backwards compatibility? Amancio