From owner-freebsd-hackers Sun Apr 13 09:01:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA11535 for hackers-outgoing; Sun, 13 Apr 1997 09:01:46 -0700 (PDT) Received: from apolo.biblos.unal.edu.co ([168.176.37.75]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA11523 for ; Sun, 13 Apr 1997 09:01:40 -0700 (PDT) Received: from unalmodem.usc.unal.edu.co (unalmodem17.usc.unal.edu.co [168.176.3.47]) by apolo.biblos.unal.edu.co (8.8.5/8.8.5) with SMTP id LAA27134; Sun, 13 Apr 1997 11:04:34 -0500 (COT) Message-ID: <335119F2.19A1@fps.biblos.unal.edu.co> Date: Sun, 13 Apr 1997 10:37:54 -0700 From: Pedro Giffuni X-Mailer: Mozilla 3.0 (Win16; I) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: jbryant@tfs.net, freebsd-hackers@freebsd.org Subject: Re: question about X.25 drivers References: <16474.860906973@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > Seriously, the biggest reason things "rot" in FreeBSD is that nobody > is actively maintaining them. If you want to take on X.25 both > now and for the forseeable future, I see no problem with resurrecting > it. > Jordan Is there a place for rotten FreeBSD thingies? Perhaps when the big changes in 3.0 are over and the interfaces documented we can resurrect many of them that don't require much maintainance (OSI, X25..and so on). Pedro.