From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: Cleaning up elkscmd and adding help text - Questions Date: Fri, 27 Mar 2015 22:19:12 +0000 Message-ID: <20150327221912.60093649@www.etchedpixels.co.uk> References: <551512AC.5050704@gmail.com> <551558D7.8040000@jodybruchon.com> <20150327141010.408a65ac@www.etchedpixels.co.uk> <89B9B0F1-40FF-41C5-A438-B9E32145B2D4@jodybruchon.com> <55159F4A.1000808@gmail.com> <5DA02C83-25D8-4C8B-859E-2814368CC566@jodybruchon.com> <5515A6EF.4060002@gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5515A6EF.4060002@gmail.com> Sender: linux-8086-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: MFLD Cc: ELKS On Fri, 27 Mar 2015 19:52:31 +0100 MFLD wrote: > I am not suggesting to build Linux on 8086, I do know it won't fit > (protected mode...) and this is why I came to ELKS! > > This is also why I cannot reuse coreboot for my project and I started to > write a kind of boot86 / mon86. > > I only suggested to try to build Busybox with dev86, and using the libc > from dev86 for the glue between Busybox code and ELKS. > > Was it tried before ? Busybox is in relative terms huge - even some of the busybox utilities split standalone are oversized compared with other implementations. Alan