From owner-freebsd-current Fri Jan 8 15:47:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13123 for freebsd-current-outgoing; Fri, 8 Jan 1999 15:47:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13113 for ; Fri, 8 Jan 1999 15:47:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00974; Fri, 8 Jan 1999 15:41:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901082341.PAA00974@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: mike@smith.net.au (Mike Smith), abial@nask.pl, jkh@zippy.cdrom.com, dillon@apollo.backplane.com, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Sat, 08 Jan 1999 23:17:44 +0200." <199901082117.XAA00229@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 15:41:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > It'd definitely be useful for the PicoBSD people, and anyone else that > > didn't need the loader's functionality. I'd also be interested in > > knowing if you have any compression/decompression tools suitable for > > use with BTX eg. to compress the application data/expand it when BTX > > relocates. > > I quite like Jordan's suggestion of kzip'ing the loader. The > compression is not especially efficient: > > -r-xr-xr-x 1 rnordier wheel 122880 Jan 3 23:55 loader > -rwxr-xr-x 1 rnordier wheel 70760 Jan 8 23:05 loader.kz > > but boot1/boot2 don't have a problem with loader.kz. It's actually not that bad; there's 12k of overhead for the kzip parts, which is why I was wondering if you had something more compact... > But maybe this isn't the compression you had in mind (I'm assuming > "when BTX relocates" refers to what the btxldr code does when > unpacking the composite /boot/loader object before invoking the > BTX kernel). Correct; it was my understanding that this process involved moving the "payload" data from the load location to the run location, and whether it might be feasible to unpack it along the way. Kzip is certainly a feasible interim solution, but it relies on the a.out tool chain which makes it a weak link. -- \\ 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