ETA: It is also my understanding that LILO fundamentally does not support reading filesystems, while Canonical want to keep SquashFS, among others. Adding support for that to LILO, along with whatever other features are missing, would likely be a major undertaking
Development stopped not because LILO didn’t need any changes, but because of its limitations (source):
NOTE: I have finished development of LILO at December 2015 because of some limitations (e.g. with BTFS, GPT, RAID). If someone want to develop this nice software further, please let me know …
Also, I dunno what your position is on this, but it is amusing to see calls for Canonical to replace GPL licensed software, with something with a more lenient license (BSD-3-clause). Normally that would cause outrage around here
It’s probably easier to strip down GRUB, than it is to resurrect and add missing features to a project that has been dead for 10+ years
It’s default for Slackware so i’d hardly call it dead.
And i doubt it’s easier to strip a behemoth than it is to add features to a small code-base.
I guess they have their own fork of it?
Upstream hasn’t seen a new release, nor any commits, since 2015: https://lilo.joonet.de/
ETA: It is also my understanding that LILO fundamentally does not support reading filesystems, while Canonical want to keep SquashFS, among others. Adding support for that to LILO, along with whatever other features are missing, would likely be a major undertaking
Perhaps.
Has lilo needed any changes, though?
If it hasn’t, then no commits and no feature creep.
Development stopped not because LILO didn’t need any changes, but because of its limitations (source):
Also, I dunno what your position is on this, but it is amusing to see calls for Canonical to replace GPL licensed software, with something with a more lenient license (BSD-3-clause). Normally that would cause outrage around here
I recall something about LILO nor supporting RAID when i tried it a few years ago.
Par for the course with Canonical™, much like all the rust rewrites.