From owner-freebsd-current Sat Dec 14 14:22:54 2002 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 81CC037B401; Sat, 14 Dec 2002 14:22:53 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2684643EC2; Sat, 14 Dec 2002 14:22:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id gBEMMqOM002572; Sat, 14 Dec 2002 14:22:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id gBEMMqcn002571; Sat, 14 Dec 2002 14:22:52 -0800 (PST) (envelope-from dillon) Date: Sat, 14 Dec 2002 14:22:52 -0800 (PST) From: Matthew Dillon Message-Id: <200212142222.gBEMMqcn002571@apollo.backplane.com> To: Maxime Henrion Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: ipfw userland breaks again. References: <200212142025.aa99706@salmon.maths.tcd.ie> <200212142038.gBEKcDVv029924@apollo.backplane.com> <20021214204426.GA62058@dragon.nuxi.com> <200212142209.gBEM9D8p002479@apollo.backplane.com> <20021214221252.GF27086@elvis.mu.org> 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 : :I have a patch here which makes the IPFIREWALL_DEFAULT_TO_ACCEPT tunable :at module load time using a kernel environment variable. Looks to me :that it would do what you want. : :Maxime No, this isn't what I want. I want something that can be articulated without having to reboot the whole system. The last time this happened to me, which was today, I had to reboot the system FIVE times before I got the network working again. For example, I tried rebooting into an old kernel and the fragging boot code tried to load the new kernel's ACPI module (actually it tried to load BOTH the old and new kernel's ACPI modules), and it panic'd of course. It took five attempts before I managed to get something that worked with the network up and then I had to reboot *AGAIN* to do the installworld with the new kernel. It's beginning to feel like a windows install! When you are sitting at a boot prompt and have no access to manual pages and such, and no in-boot-help that's significant enough to be worthwhile, it's no help tearing your hair out trying to remember the name of the stupid boot variable. The last thing I want is yet another undocumented or hard-to-find boot variable. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message