Date: Mon, 11 Feb 2019 07:14:09 -0800 From: Cy Schubert <Cy.Schubert@cschubert.com> To: freebsd-current@freebsd.org Subject: Re: Lua Loader Failure to Include Message-ID: <28B40BDE-BBA1-49F0-9EB5-22859A9812B9@cschubert.com> In-Reply-To: <201902111305.x1BD5bWZ011358@slippy.cwsent.com> References: <201902111305.x1BD5bWZ011358@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On February 11, 2019 5:05:37 AM PST, Cy Schubert <Cy.Schubert@cschubert.com> wrote: >Hi, > >Under the old Forth loader the line: > > include /boot/testbed/test_sys > >would load the file and execute loader commands. > >However the the Lua loader results in the following: > >OK include /boot/testbed/amd64-current-r >no error message >OK > >Looking at the code, interp_include() expects to run actual Lua code >using luaL_dofile(). Is this an intended change? > >The loader statements the file above is intending to execute are: > >echo >echo >echo testbed/amd64-current-r (12.0-CURRENT) loader file selected >set bootdev=disk1s4a: >include /boot/testbed/current.hints >include /boot/testbed/do_load_KOMQUATS > >Let me know if I am to rewrite these loader statements into Lua or >whether the Lua loader should be taught to read loader statements >instead. Thinking about this while travelling to $JOB, it's probably best to leave it as is. I'll rewrite the includes into Lua. The benefit is greater flexibility and functionality. -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28B40BDE-BBA1-49F0-9EB5-22859A9812B9>