Date: Wed, 21 Feb 2001 19:12:37 +0700 From: Eugene Grosbein <eugen@www.svzserv.kemerovo.su> To: Luigi Rizzo <rizzo@aciri.org> Cc: freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD 0.5 Message-ID: <20010221191237.B26140@svzserv.kemerovo.su> In-Reply-To: <200102210727.f1L7R8D73854@iguana.aciri.org>; from rizzo@aciri.org on Tue, Feb 20, 2001 at 11:27:08PM -0800 References: <20010221140316.A26140@svzserv.kemerovo.su> <200102210727.f1L7R8D73854@iguana.aciri.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 20, 2001 at 11:27:08PM -0800, Luigi Rizzo wrote: > I believe the above method is more convenient than the old one (as > it supports network-loading of the kernel) and it saves some space > because each file on the floppy consumes a minimum of 512 bytes, > whereas the corresponding version in MFS can be smaller as the > padding compresses quite well. Yes, but my goal is to make floppy that is very configurable at run time and capable of saving configuration changes. For example, I tried to build pico kernel with several drivers for ISA etherenet cards and use /boot/kernel.conf for tuning (enable/disable etc). I see that 'update' script will take care of it. So I made /usr/src/release/picobsd/MY/floppy.tree/boot/kernel.conf, but it does not go into image. Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010221191237.B26140>