From owner-freebsd-hackers Thu May 14 14:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17097 for freebsd-hackers-outgoing; Thu, 14 May 1998 14:34:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17064 for ; Thu, 14 May 1998 14:34:10 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218] (may be forged)) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA10536; Thu, 14 May 1998 21:33:55 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id XAA21837; Thu, 14 May 1998 23:33:53 +0200 (MET DST) Message-ID: <19980514233348.17594@follo.net> Date: Thu, 14 May 1998 23:33:48 +0200 From: Eivind Eklund To: Marc Giannoni , freebsd-hackers@FreeBSD.ORG Cc: jhk@time.cdrom.com Subject: Re: NETCCITT and NETISO References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Marc Giannoni on Fri, Jan 21, 2000 at 05:26:24PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 05:26:24PM -0500, Marc Giannoni wrote: > Hello: > > I'm interested in 'resurrecting' the support for X.25 and ISO networking. > Is anybody else already doing this? If NOT... Nobody else is AFAIK doing it. There was some talk of resurrecting parts to make it easier to do Token Ring & better IPX support, but so far little has happened. > I've obtained sources from an old 2.1-RELEASE cdrom (likely obsolete) and > placed them in a 'stable' source tree. After some hacking about, I was able > to configure and attempt to compile a kernel with the CCITT, ISO, LLC, HDLC > options. From what I can tell, all that needs to be done > (for the thing to compile) is to sort out function prototyping and > some other delcarations. I'd suggest a different plan of attack (given that you seem to have a reasonable amount of resources available, and as a such probably isn't too squeamish abou diskspace): Download the CVS repository (or copy it off a friend) and keep it updated through CVSup. From this, check out some reasonably old version (say, at the time of RELENG_2_1_0_BP). Compile up and test this version. (Continue until you find a working version). Now, go forward in 'suitable' steps by 'cvs update -Dxxx', taking backups each time. I'd suggest going forward 6 months at a time; if the new version doesn't have working X.25, use a binary search to find the exact commit that broke X.25. From this, you can probably easier find what to fix - then fix it, and keep bringing the version forward (by cvs update) with that fix in. Repeat until you've actually reach -current with a working X.25. If you need more details on the techniques involved with CVS, feel free to ask. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message