Removal of RFC1644 support from CURRENT?
From: Andre Guibert de Bruet (andy_at_siliconlandmark.com)
Date: 11/04/04
- Previous message: Marc Ramirez: "Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state"
- Next in thread: Kris Kennaway: "Re: Removal of RFC1644 support from CURRENT?"
- Reply: Kris Kennaway: "Re: Removal of RFC1644 support from CURRENT?"
- Reply: Andre Oppermann: "Re: Removal of RFC1644 support from CURRENT?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 3 Nov 2004 22:15:04 -0500 (EST) To: current@freebsd.org
Hi,
May I ask what the rationale behind this was (Besides the fact that no
apps known to man actually use this support)?
20041102:
The size of struct tcpcb has changed again due to the removal
of RFC1644 T/TCP. You have to recompile userland programs that
read kmem for tcp sockets directly (netstat, sockstat, etc.)
Andy
| Andre Guibert de Bruet | Enterprise Software Consultant >
| Silicon Landmark, LLC. | http://siliconlandmark.com/ >
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Marc Ramirez: "Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state"
- Next in thread: Kris Kennaway: "Re: Removal of RFC1644 support from CURRENT?"
- Reply: Kris Kennaway: "Re: Removal of RFC1644 support from CURRENT?"
- Reply: Andre Oppermann: "Re: Removal of RFC1644 support from CURRENT?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|