From owner-freebsd-hackers  Tue Mar 21 22:56:59 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 189C837C086
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 21 Mar 2000 22:56:57 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA20067;
	Tue, 21 Mar 2000 22:57:15 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Nick Sayer <nsayer@sftw.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: md_image compression? 
In-reply-to: Your message of "Tue, 21 Mar 2000 21:55:39 PST."
             <200003220555.VAA56886@yoda.sftw.com> 
Date: Tue, 21 Mar 2000 22:57:15 -0800
Message-ID: <20064.953708235@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I'm sort of thinking in my head about adding the ability for the
> md driver to handle gziped images. md's drvinit() looks like

And you can't load the kernel and the gzipped images from the boot
loader, letting the boot loader decompress the stuff and just using
the existing MD_ROOT option hook to load it?

- Jordan


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