From owner-freebsd-hackers Mon Jan 18 18:36:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26165 for freebsd-hackers-outgoing; Mon, 18 Jan 1999 18:36:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles139.castles.com [208.214.165.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26157 for ; Mon, 18 Jan 1999 18:36:27 -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 SAA00675; Mon, 18 Jan 1999 18:33:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901190233.SAA00675@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: hackers@FreeBSD.ORG Subject: Re: Anyone know how to put a gzip'd kernel on the floppy? In-reply-to: Your message of "Mon, 18 Jan 1999 17:34:46 PST." <199901190134.RAA84965@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 18:33:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I can get the new multi-stage ELF loader thingy working with uncompressed > kernels, but I can't get it to work with gzip'd kernels. I've tried > stripping the symbols prior to gzip'ing ... no luck, the loader doesn't > recognize the gzip'd kernel. > > Has anyone figured out how to do this? I need to fit a workstation > kernel ( i.e. that is inclusive of sound drivers) onto a floppy and > not having much luck. It would fit fine if I could compress it. Take an ELF kernel. Gzip it, so you have 'kernel.gz'. Put it on your boot media. If you need to explicitly reference it, use eg. 'load kernel' (the .gz extension is searched automatically). -- \\ 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-hackers" in the body of the message