From owner-freebsd-hackers Mon Jan 26 17:08:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05770 for hackers-outgoing; Mon, 26 Jan 1998 17:08:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05737 for ; Mon, 26 Jan 1998 17:08:47 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id LAA00745; Tue, 27 Jan 1998 11:17:03 +1030 (CST) Message-Id: <199801270047.LAA00745@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Luigi Rizzo cc: hackers@FreeBSD.ORG Subject: Re: compressed bootloader ? In-reply-to: Your message of "Mon, 26 Jan 1998 21:50:14 BST." <199801262050.VAA00805@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jan 1998 11:17:03 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > image. Thinking about the size problem of the secondary boot loader > (7KB or so). gzipping the boot loader brings the size down from 7120 to > 4496, so I believe that even adding some 5-700 bytes for the > uncompression code would give us some additional space (assuming there > is any use for it). Any taker ? If you have a compact self-extractor for boot images, go for it. Put it in boot1 and have it extract boot2, if that's at all possible. -- \\ 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. \\