From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: Future of ELKS Date: Mon, 24 May 2004 19:20:11 +0100 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1085422810.22331.7.camel@localhost.localdomain> References: <1084985870.3062.23.camel@talena.hsol.net> <40AC99A5.9030809@agora-2000.com> <1085066127.3062.35.camel@talena.hsol.net> <20040520153744.GL24490@duckman.distro.conectiva> <40ACEB23.7010101@agora-2000.com> <20040521083248.GT3344@vega.vega.lgb.hu> <008701c43f3e$0e934030$0101a8c0@vash> <20040524092902.GD30077@vega.vega.lgb.hu> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20040524092902.GD30077@vega.vega.lgb.hu> List-Id: Content-Type: text/plain; charset="utf-8" To: lgb@lgb.hu Cc: Jody , Linux-8086 On Llu, 2004-05-24 at 10:29, G=C3=A1bor L=C3=A9n=C3=A1rt wrote: > OK, my only though was that even some 8bit hw has got the power to ru= n an > ELKS-like OS. Just think on Enterprise-128, I've described above (4Mb > addressing page with "paging", though the base machine has got only > 128K RAM by default, you can expand it). Dave Braun did a Unix v7 clone (UZI) for banked Z80. As far as compilers and segmentation and the like go, the Xenix 286 people supported multisegment binaries and swapping of them on 286 systems, but not 8086. They used protected mode (obviously), segmentation and carefully arranged segment numbering so that you could deduce the next segment of a block of code or data. - To unsubscribe from this list: send the line "unsubscribe linux-8086" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html