From owner-freebsd-current  Mon Dec  7 18:52:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA26133
          for freebsd-current-outgoing; Mon, 7 Dec 1998 18:52:22 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26127
          for <current@FreeBSD.ORG>; Mon, 7 Dec 1998 18:52:18 -0800 (PST)
          (envelope-from karpen@ocean.campus.luth.se)
Received: (from karpen@localhost)
	by ocean.campus.luth.se (8.9.1/8.9.1) id DAA16612;
	Tue, 8 Dec 1998 03:48:21 +0100 (CET)
	(envelope-from karpen)
From: Mikael Karpberg <karpen@ocean.campus.luth.se>
Message-Id: <199812080248.DAA16612@ocean.campus.luth.se>
Subject: Re: New drivers and install floppy space
In-Reply-To: <199812072347.PAA00852@dingo.cdrom.com> from Mike Smith at "Dec 7, 98 03:47:57 pm"
To: mike@smith.net.au (Mike Smith)
Date: Tue, 8 Dec 1998 03:48:21 +0100 (CET)
Cc: mike@smith.net.au, tlambert@primenet.com, wpaul@skynet.ctr.columbia.edu,
        current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

According to Mike Smith:
> > > 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.

Ofcourse, it's an optimisation... So it's best to have something to
optimize first... Just thought I'd get the idea public, so it's thought
of later. :-)

  /Mikael

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message