From owner-freebsd-current Wed Mar 5 1:43: 1 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2B5537B405; Wed, 5 Mar 2003 01:42:58 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 395BD43FCB; Wed, 5 Mar 2003 01:42:58 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from dialup-209.245.134.12.dial1.sanjose1.level3.net ([209.245.134.12] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18qVQO-0006j4-00; Wed, 05 Mar 2003 01:42:57 -0800 Message-ID: <3E65C538.A4F7A73A@mindspring.com> Date: Wed, 05 Mar 2003 01:36:56 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Doug Barton Cc: Bob Bishop , Peter Wemm , Mike Barcroft , Tim Robbins , freebsd-net@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Removal of netns - politically correct version References: <3E6539B5.2F5D31B@mindspring.com> <4.3.2.7.2.20030305084442.037e9fa0@gid.co.uk> <3E65BB24.3E37D90D@mindspring.com> <20030305011926.T18288@znfgre.tberna.bet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4f02ef09876915196a9cad9c88b30f9922601a10902912494350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Doug Barton wrote: > On Wed, 5 Mar 2003, Terry Lambert wrote: > > The code is still useful as a simple implementation, much more > > easily understood by the student than the current TCP/IP stack, > > for certain. > > And it will still be available. It'll just be available in the Attic. The > fact that it will get more broken in the future because it's not being > maintained in the tree is not terribly significant since it's already > broken now. Why don't we let me sumbit patches, apply the things, and *then* dike the code out, if that's your reasoning? > > On the other hand, there's no compelling reason to dike it out, > > There is at least one, namely that it will make kernel code updates easier > to do, and easier to test. And here people were telling me I was wrong for cynically assuming that the reason people diked out so much code in the past year was because they wanted to perform kernel code updates, without having to maintain all the code they would be touching with those updates... > > if it can be made to work. I would argue that ISA support is > > more or less just as obsolete, as is 486 support, as is the F00F > > bug workaround, as is ... a lot of code that's still there. > > Your argument here is non sequitur because we still have large bases of > users and developers that have and use this hardware. I retired a box with > an original P90 f00f bug cpu not that long ago, for example. netns has > neither freebsd users or developers, and hasn't for years. And I have two XNS terminalservers, and there are people on this list with Apollo equipment. Your point was again? > > In any case, Peter pointed out that my patch was against -stable, > > not -current. I'm in the process of CVSup'ing new sources now, > > and will update the patch against -current, and post it, most > > likely tomorrow morning, if the CVSup doesn't complete in the next > > hour. > > I think that fixing the current brokeness is still useful, even if it gets > axed. Putting it to bed with a full tummy will make future educational > value of the code that much higher. I suggested that before. People are telling me they won't apply the patches before they murder the code. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message