From owner-freebsd-current Mon Oct 6 14:42:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA01534 for current-outgoing; Mon, 6 Oct 1997 14:42:22 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA01529 for ; Mon, 6 Oct 1997 14:42:16 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA06609; Mon, 6 Oct 1997 21:10:19 +0100 From: Luigi Rizzo Message-Id: <199710062010.VAA06609@labinfo.iet.unipi.it> Subject: Re: how to detect different kernel code (select or poll) To: tlambert@primenet.com (Terry Lambert) Date: Mon, 6 Oct 1997 21:10:18 +0100 (MET) Cc: gurney_j@resnet.uoregon.edu, tlambert@primenet.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199710062031.NAA24338@usr04.primenet.com> from "Terry Lambert" at Oct 6, 97 08:31:24 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > integrated at some point. Really, I don't see why the 2.2 code could > not go into the 2.2 tree right now. for this particular piece, because we are in code freeze. But in many other cases, it might just be because this "2.2 code" is an optional replacement for some piece of the system (e.g. a new scheduler, or a different TCP/IP implementation...) > My other point was that, whatever you do, you will have to rip out > later if you intend to integrate the code into FreeBSD: it makes no yes but at that point this will not be a problem. Cheers Luigi