From owner-freebsd-bugs  Tue Apr 14 09:00:02 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA07990
          for freebsd-bugs-outgoing; Tue, 14 Apr 1998 09:00:02 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA07967;
          Tue, 14 Apr 1998 09:00:01 -0700 (PDT)
          (envelope-from gnats)
Date: Tue, 14 Apr 1998 09:00:01 -0700 (PDT)
Message-Id: <199804141600.JAA07967@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bill Fenner <fenner@parc.xerox.com>
Subject: Re: kern/6296: IP_HDRINCL sockets force header fields to be in host byte order 
Reply-To: Bill Fenner <fenner@parc.xerox.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/6296; it has been noted by GNATS.

From: Bill Fenner <fenner@parc.xerox.com>
To: tqbf@secnet.com
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/6296: IP_HDRINCL sockets force header fields to be in host byte order 
Date: Tue, 14 Apr 1998 08:50:34 PDT

 This is a backwards-compatibility issue; it has been this way since
 4.3-Reno when IP_HDRINCL was introduced (or before, if you count the
 patches that Van distributed with traceroute).  I'd be worried about
 backwards compatibility when making this change (for example, Van's
 "pathchar" utility is only available as a binary...).  It might make
 sense to rename the current IP_HDRINCL and create a new one with new
 semantics.
 
   Bill
 
 (P.S. At least it's not Solaris, where you have to know that you put
 the transport length into the transport checksum field and the kernel
 computes the transport checksum!...)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message