I will say that I personally actually still prefer elilo in some respects.
Notably, grub2 tends to want to reinvent the world rather than interact
with other protocols. Adding ipxe download protocol to elilo was easy, but
I couldn't navigate grub2 to make the same changes. grub2 instead went
to make their own http stack, but ipxe still is ahead of them.
The only thing I've been tempted to add that I don't have a patch for yet
is loader side initrd concatenation.
I could imagine a *simpler* bootloader making me no longer care about elilo
for providing a simplistic netboot environment, but grub2 isn't in that
direction.
In short, I for one am grateful for elilo still being kept up all this time
and for being simple and to the point. Thanks for that.
From: jfly <fleischli-Rn4VEauK+AKRv+***@public.gmane.org>
To: elilo-discuss-5NWGOfrQmneRv+***@public.gmane.org
Date: 10/15/2013 05:28 PM
Subject: Re: [elilo-discuss] Please switch to GIT (or another DVCS) so
that it is easy to contribute to ELILO
Hi Keshav,
thanks for your note.
Post by Keshav Padram AmburayHi,
Can you guys please switch from CVS to GIT (or another DVCS) so
that it is easy for users to track development of ELILO. Currently it
is difficult to track using CVS. Thanks in advance.
GIT is great (and intended) for really large projects with 100's of
contributors. As elilo is neither of those, and that status wont change,
I dont see the benefits warrant the time and effort. There is nothing
that prevents you from pulling the source into your own local git
repository and working on it within git and sending patches for
consideration and elilo will stay on sourceforge. That being said, I
hear you, I work with git for the kernel and Ive thought about switching
this source over to git now and then. Git is superior to CVS so I'll
consider it again. you are the first to raise a complaint. no really.
Post by Keshav Padram AmburayOff-note: Is ELILO still under active development? Because there seems
to be no update after v3.16 which was released in March 2013 (8 months
ago). Even if it is no longer actively maintained, providing the
sources via GIT will allow contributors to fork the code and maintain
it in github/gitorious/bitbucket etc..
Elilo is still actively maintained solely by me but no longer in active
development. Elilo was designed in the early 2000's for EFI and Itanium,
thats why it exists. As neither of those are very relevant any more It
is legacy code at the end of its life cycle naturally. Im really not
accepting new features or new feature requests. New releases are for
major bug fixes for people that just cant live without elilo and
thats about it and I have no bugs waiting to release.
New bootloader efforts and contributions should rightfully go to Grub2.
It is in active development, has many active contributors and is
accepting new features and it supports UEFI and secure boot now and is
finally fairly well positioned to fulfill its original intention of
being the "GRand Unified Bootloader". It could be so if it supported
network booting and really if elilo didnt exist anymore Im sure that
somebody wouldve contributed the feature by now, most likely from a
cloud team.
And to you as well,
Jason