From owner-freebsd-stable Sat Nov 3 17:48:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7C79237B406; Sat, 3 Nov 2001 17:48:55 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fA41mVh26905; Sat, 3 Nov 2001 17:48:31 -0800 (PST) (envelope-from dillon) Date: Sat, 3 Nov 2001 17:48:31 -0800 (PST) From: Matthew Dillon Message-Id: <200111040148.fA41mVh26905@apollo.backplane.com> To: "Jose M. Alcaide" Cc: "Bruce A. Mah" , Warner Losh , freebsd-stable@FreeBSD.ORG Subject: Re: /usr/src/UPDATING Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : * Bill Fenner's code to make ipfw/dummynet/bridge KLD'able : : BOTH THESE THINGS REQUIRES REBUILDING OF ipfw.ko and /sbin/ipfw : :I am not sure if that should be added to UPDATING. After all, it was not :added to -CURRENT's /usr/src/UPDATING neither ;-) : : Regards, : JMA :-- Whenever ipfw changes people who update their kernel and do not reinstall world (or at leaset the ipfw binary) often wind up with unaccessible machines when they reboot, because /etc/rc* cannot load the IPFW rule set. It's happened to me many, many times. It's extremely annoying. An UPDATING entry is the minimum that should be added. It would also be nice if the system detected out-of-date IPFW's (like maybe adding a version field to the 'rule' structure) so ipfw could request a 'safe' mode of operation or something. I don't know. But it's getting really annoying. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message