From owner-freebsd-current Thu Dec 31 04:47:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26653 for freebsd-current-outgoing; Thu, 31 Dec 1998 04:47:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26645 for ; Thu, 31 Dec 1998 04:47:06 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id NAA11358; Thu, 31 Dec 1998 13:52:14 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 31 Dec 1998 13:52:13 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Robert Nordier cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: <199812311212.OAA17631@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Robert Nordier wrote: > Peter Wemm wrote: > > > === INCOMPLETE DRAFT === > > > - The new bootblocks default to /boot/loader, but there are some problems > > for some people still. This needs to be fixed, and either the new > > bootblocks need fixing or the old bootblocks need a cutdown and > > modified to fire up /boot/loader by default. > > Since early November (and up to and including an issue reported on > -current yesterday), all apparent show-stopping problems with the > new bootblocks have turned out to be due to configuration and/or > pilot errors: where it has been possible to get further details. > > So if anyone still can't use the new bootblocks, there's almost > certainly some simple and painless solution which doesn't require > code fixes to sort out; and anyone who needs help is more than > welcome to contact me. Ok, here's my question: how do you replace functionality of kzip (which doesn't work for ELF kernels) without loosing 120kB of disk space for /boot/loader? In case of normal installations it doesn't matter, but in case of a floppy... Thus far I was able to use kzip with a.out kernels to save space on the floppy. Since we're going ELF with kernel, and kzip doesn't work there, I'm now forced to use gzip and /boot/loader, which takes about 100kB more than simply boot2 and kzipped (a.out) kernel. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message