Date: Mon, 12 Nov 2012 09:40:19 -0800 From: Devin Teske <devin.teske@fisglobal.com> To: mike <mike@reifenberger.com> Cc: Adrian Chadd <adrian@freebsd.org>, Devin Teske <dteske@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: Working on Bootforth / ficl Message-ID: <1DE1DC5C-9D7F-4FC7-A27C-736B0B172DBF@fisglobal.com> In-Reply-To: <alpine.WNT.2.00.1211120856000.7920@ux32> References: <A0A46155-0969-459E-BCD6-4AA7B8B371BE@fisglobal.com> <alpine.WNT.2.00.1211120856000.7920@ux32>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 12, 2012, at 12:56 AM, mike wrote: > Hi, > a few years ago I made an upgrade to ficl 4.0 and some other changes whic= h brought among other things: - A somewhat simpler C-interface (IMHO) The simplified C interface would be welcome in the upcoming BE enhancements. > - Real compression for the softwoods I like the sound of that. > - A user-land ficl executable which acted exactly like the bootloader for= better > forth development >=20 Does it support "include" ? That's been one of the biggest things preventin= g me from simulating boot in userland. If it does, this would be a very gre= at addition. > A first step to get back on this topic would be to vendor import the rela= ted ficl versions (ficl33, ficl40, ficl41) and move the currently used ficl= 33 > from sys/boot/ficl to sys/contrib/ficl and separate the local modificatio= ns > from the vendor code. >=20 > Any objections in general? >=20 I've none, but you should seek opinions of others too. --=20 Devin P.S. Thank you! > What would be the preferred method? > - Vendor import of ficl33 as described in the commiters guide > - svn copy of ficl33 to sys/contrib/ficl > - svn copy of the locally modified ficl33 files or reapply the local chan= ges? >=20 > Other suggestions? >=20 > Thanks in advance! >=20 > Greetings > --- > Michael Reifenberger _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1DE1DC5C-9D7F-4FC7-A27C-736B0B172DBF>