freebsd stable - Jun 2020 - LUA ERROR: memory allocation error: block too big

I do not want to be demoralizing, nor to hurt anyone. I am also thankfull
to all developers.

But the argumenentation used here does not convince and makes me
think about the future of FreeBSD.

OK, for putting LUA was invested many many hours, the FORTH was
done in 5 minutes and ist worst quality.

But the booting and installation problems, that I had to solve in
a tricky way and with additional hardware, began with the LUA loader,
and are solved putting an old loader, as somenone in this thread noted.

And how many users did need lua there (and everywhere, also in the
soup)?

The last beat would be to remove the forth loader from the distribution,
then a solution of the problems will become much more difficult.

Rodrigo


On Wed, 3 Jun 2020, Kyle Evans wrote:

[...]
> As an aside, I'd appreciate it if other folks in this thread could
> simply stop dumping all over the many many many hours of work that
> were put into getting lua into shape to replace the high-quality forth
> that was already in place. The reality is that lua won a popularity
> contest long ago [outside of a FreeBSD context][ and lowers the barrier
> to being able to hack on our loader menus, which should be viewed as a
> great thing. These comments were highly demoralizing, and I almost
didn't
> bother dropping into this thread because of them.
>
> Believe it or not, issues with underlying media can cause problems
> with 4thloader as well.
>
> Thanks,
>
> Kyle Evans
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
>

On Thu, Jun 4, 2020 at 5:53 AM Roderick <hruodr at gmail.com>
wrote:
> [...]
>
> OK, for putting LUA was invested many many hours, the FORTH was
> done in 5 minutes and ist worst quality.
>
I'd easily debate this latter bit- the Forth is certainly higher quality.
> But the booting and installation problems, that I had to solve in
> a tricky way and with additional hardware, began with the LUA loader,
> and are solved putting an old loader, as somenone in this thread noted.
>
Can you share a pointer to the problems you had?

It would be highly unusual for swapping out the interpreter to cause
problems of this nature. With the way loader is architected, most
low-level details don't change with different interpreters, and it's
incredibly likely you are looking at a problem that was caused
way-independently of swapping out the interpreter. Plenty of things
broke between FreeBSD 10/11 and 12 in loader-world as our loader
universe got thoroughly rototilled and improved -- many of these
things cannot be attributed to lua, but perhaps are because of the
coincidental timing.

Thanks,

Kyle Evans