From owner-freebsd-current Sun Nov 1 06:22:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13160 for freebsd-current-outgoing; Sun, 1 Nov 1998 06:22:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13153 for ; Sun, 1 Nov 1998 06:22:02 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id GAA18897; Sun, 1 Nov 1998 06:22:00 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: Andrzej Bialecki , current@FreeBSD.ORG Subject: Re: BootForth (was Re: New boot loader and alternate kernels) In-reply-to: Your message of "Sat, 31 Oct 1998 21:37:12 PST." <199811010537.VAA01330@dingo.cdrom.com> Date: Sun, 01 Nov 1998 06:21:59 -0800 Message-ID: <18893.909930119@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, how do I integrate it into the loader? Do we want to make it > optional? Do we want to strip the loader back to the bare essentials > and use BootFORTH for as much as possible? Is a "middle road" approach > preferred? Well, you could probably save some space by registering all your existing builtins as forth words and chucking the existing interpreter in favor of the more traditional INTERPRET word. Not sure how you'd do that initial timeout behavior thing though - probably some gross hack. :-) > Any Forth hackers want to play with something new and funky? In > particular, some ideas on "standard" system-interface words would be > handy. If you get it to the point where it's launching from the boot blocks, I'd certainly be willing to look into some of the ergnonomic and extensibility issues. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message