From owner-freebsd-current Mon Mar 31 09:49:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA29425 for current-outgoing; Mon, 31 Mar 1997 09:49:20 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA29417 for ; Mon, 31 Mar 1997 09:49:17 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wBlCc-0006sH-00; Mon, 31 Mar 1997 10:49:06 -0700 To: Doug Rabson Subject: Re: A new Kernel Module System Cc: "Jordan K. Hubbard" , current@freebsd.org In-reply-to: Your message of "Mon, 31 Mar 1997 11:15:33 +0100." References: Date: Mon, 31 Mar 1997 10:49:05 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Doug Rabson writes: : Almost. You would load /lkm/devs/isa/foo.so. The driver object does not : need an instance number since the same driver could support many different : instances: : : isaconf -a foo0 port=320 irq=10 iomem=0xd0000 : isaconf -a foo1 port=330 irq=11 iomem=0xd8000 : isaconf -a foo2 port=340 irq=12 iomem=0xe0000 : modload /lkm/devs/isa/foo.so That would be way cool. I'd especially like to be able to do this with the GENERIC kernel. Right now there is no way to do this, short of booting -c. When you install a new kernel on a machine at a remote office and thinkn that you are set because the old kernel was generic too and do a reboot, only to find out that it really wasn't generic GENERIC.... That is I'd like to be able to boot a generic thing, and have it preserve my deltas to the "settings" of the device drivers across upgrades. It is often nice to have one GENERIC kernel that gets pushed out to n sites who's only differences are the IRQs and I/O addresses of some of the ethernet cards, etc. Warner