From owner-freebsd-current Mon Dec 7 15:50:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03228 for freebsd-current-outgoing; Mon, 7 Dec 1998 15:50:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp6.portal.net.au [202.12.71.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03222 for ; Mon, 7 Dec 1998 15:50:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00852; Mon, 7 Dec 1998 15:47:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812072347.PAA00852@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mikael Karpberg cc: mike@smith.net.au (Mike Smith), tlambert@primenet.com, wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Mon, 07 Dec 1998 02:52:40 +0100." <199812070152.CAA13609@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 15:47:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Mike Smith: > > > o a mechanism for dumping drivers from the kernel after > > > installation so that they need not be installed twice: > > > once to boot, once to install; this probably implies > > > driver data areas be mapped copy-on-write to maintain > > > the data image integrity to allow it to be written > > > back out > > > > This is actually fairly tough, as the entire ELF object is not loaded > > in the first place. My preference is simply to track the driver(s) > > that are loaded, and request the use re-provide the media from which > > the driver was read when it comes time to copy it. > > Wouldn't the best and easiest solution here be something like this in > the loader: save_drivers_in_ram = (total_ram_MB > 8); > And if the variable is set, you just don't load the driver, you also > store the complete file it was loaded from in a memory block which > can then just be dumped to file. If you don't have enough memory to do > that, you can ask for the disks again, instead. That sounds like a worthwhile optimisation, but since you need to support asking for the disks, it's probably better to start with that first. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message