From owner-freebsd-net Mon Aug 23 11:27:18 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2A7F315784 for ; Mon, 23 Aug 1999 11:27:11 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA03583; Mon, 23 Aug 1999 11:24:27 -0700 (PDT) Date: Mon, 23 Aug 1999 11:26:06 -0700 (PDT) From: Julian Elischer To: itojun@iijlab.net Cc: freebsd-net@FreeBSD.ORG Subject: Re: differences in member name In-Reply-To: <8327.935427566@coconut.itojun.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If you can make a patch of things you'd like to see changed for compatibility, I'm sure that there would be a high probability that we would acce[t them. The names of elements (and similar things are not set in stone if there is a good reason for a change, and compatibility is a good reason.) The if_var.h question has been gone over many times and reverting it to if.h is unlikely. On Tue, 24 Aug 1999 itojun@iijlab.net wrote: > sorry I made a typo. > > itojun > > ------- Forwarded Message > > To: tech-net@netbsd.org, freebsd-net@netbsd.org > Subject: differences in member name > X-Template-Reply-To: itojun@itojun.org > X-Template-Return-Receipt-To: itojun@itojun.org > X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 > From: itojun@iijlab.net > Date: Tue, 24 Aug 1999 01:56:05 +0900 > Message-ID: <8224.935427365@coconut.itojun.org> > Sender: itojun@coconut.itojun.org > > I'm working on KAME code which shares most of sys/netinet6 code > among all *BSDs. I find it VERY irritating (and tend to introduce > bugs) to make #ifdef for some of very trivial differences among BSDs. > One of very good exapmle is if_list/if_link member in struct ifnet. > > NetBSD: if_list, net/if.h > FreeBSD: if_link, net/if_var.h (moved from net/if.h) > OpenBSD: if_list, net/if.h (since it was inherited from NetBSD) > > Could anyone tell me why the difference is introduced? > If either of them is more authentic than others, is there any > chance for synchronization? > > For if_list/if_link, changes are introduced in the following version: > NetBSD: > http://www.jp.netbsd.org/cgi-bin/cvsweb.cgi/syssrc/sys/net/if.h.diff?r1=1.16&r2=1.17 > FreeBSD: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/net/if.h.diff?r1=1.39&r2=1.40 > > My fundamental question is, why do people work on *BSDs needs to waste > their time on this kind of tiny (but very irritating) twists. > Other researchers/hackers find it troublesome. > > itojun > NOTE: BSDI4 is still using if_next (not queue.h) so I omitted it > from the above example. When BSDI4 changes it in the future, I hope > them try to use common member name. > > ------- End of Forwarded Message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message