From owner-freebsd-current Thu Apr 16 23:33:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09651 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:33:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09640 for ; Fri, 17 Apr 1998 06:33:40 GMT (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA03123; Fri, 17 Apr 1998 08:33:35 +0200 (MEST) (envelope-from sos) Message-Id: <199804170633.IAA03123@sos.freebsd.dk> Subject: Re: Networking strategy for -current In-Reply-To: <353699BD.ABD322C@whistle.com> from Julian Elischer at "Apr 16, 98 04:52:29 pm" To: julian@whistle.com (Julian Elischer) Date: Fri, 17 Apr 1998 08:33:34 +0200 (MEST) Cc: current@FreeBSD.ORG, kjc@csl.sony.co.jp From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Julian Elischer who wrote: > One of the things that has been apparent is that FreeBSD is being > used more and more as a firewall and router for people with > special networking requirements. The networking code however > is getting old, and needs work in various places. many people are > also using it for experimentation. Julian, to put it very simple, you need to get DEVFS and possibly softupdates finished before you get to commit any new halfbaked solutions to -current. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message