From owner-freebsd-questions Mon Jul 29 5:10:36 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3945137B400 for ; Mon, 29 Jul 2002 05:10:33 -0700 (PDT) Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 387F243E4A for ; Mon, 29 Jul 2002 05:10:32 -0700 (PDT) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.Physik.Uni-Mainz.DE (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by klima.physik.uni-mainz.de (8.12.5/8.12.5) with ESMTP id g6TCAUtB002136 for ; Mon, 29 Jul 2002 14:10:31 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Mon, 29 Jul 2002 14:10:30 +0200 (CEST) From: "Hartmann, O." To: freebsd-questions@freebsd.org Subject: IPF2 Code use in PICOBSD Message-ID: <20020729140806.L2126-100000@klima.physik.uni-mainz.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Sirs. We would like to test the new IPFW2 code in PICOBSD and for that there is the unaswered question od how to force the build process of PICOBSD to build the ipfw2 code. Can anyone give tips and hints? I tried at several stages with make -DIPFW2, but not knowing exactly how PICOBSD is build this seems a senseless task. Thanks in advance, O. Hartmann -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ------------------------------------------------------------------ IT-Administration des Institutes fuer Physik der Atmosphaere (IPA) ------------------------------------------------------------------ Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message