Greetings,
I'm currently packaging mkelfImage for Debian and Ubuntu, due to a number of recent LTSP products based upon LinuxBIOS not being able to boot with ELF images produced using etherboot.org's old mkelf-linux tool. There is interest on the Ubuntu side to eventually migrate to this tool for LTSP, provided that it can be verified to generate ELF images that also work for booting Etherboot/Netboot devices based on commercial BIOS.
In the process of packaging mkelfImage, a number of issues related to the upstream tarball came up, which prompted me to contact the people mentioned in AUTHORS, to no avail. No response. The main issues are a non-pristine upstream 2.7 tarball and a rather convoluted autotools implementation that makes it very difficult to cleanly build this software in a repeatable way.
Thus, in the interest of furthering LinuxBIOS adoption, I am wondering if anyone would be interested in picking up upstream's aging 2.7 tarball, cleaning up its Makefile and bringing it up to current GNU recommended practices, adding missing author credits in each source file's headers, etc. possibly even adding support for amd64 - in essence, to become the new upstream?
Once we have a new, properly documented pristine upstream 2.8 tarball with a clean autotools implementation that meets Debian's standards, inclusion into Debian and Ubuntu can proceed.
Best Regards,
On Sun, Jul 29, 2007 at 12:56:41AM +0300, Martin-Éric Racine wrote:
images that also work for booting Etherboot/Netboot devices based on commercial BIOS.
This should just be a quick test - but IIRC Etherboot can boot mkelfImage output just fine.
In the process of packaging mkelfImage, a number of issues related to the upstream tarball came up, which prompted me to contact the people mentioned in AUTHORS
I think Eric Biederman is the person to talk to.
The main issues are a non-pristine upstream 2.7 tarball and a rather convoluted autotools implementation that makes it very difficult to cleanly build this software in a repeatable way.
Ok. Dunno. I just ./configure && make && make install (or actually the equivalent in my Gentoo ebuild) and it's very repeatable for me.
I am wondering .. to become the new upstream?
Could you do it?
//Peter
On 29/07/07 05:20 +0200, Peter Stuge wrote:
On Sun, Jul 29, 2007 at 12:56:41AM +0300, Martin-Éric Racine wrote:
images that also work for booting Etherboot/Netboot devices based on commercial BIOS.
This should just be a quick test - but IIRC Etherboot can boot mkelfImage output just fine.
In the process of packaging mkelfImage, a number of issues related to the upstream tarball came up, which prompted me to contact the people mentioned in AUTHORS
I think Eric Biederman is the person to talk to.
The main issues are a non-pristine upstream 2.7 tarball and a rather convoluted autotools implementation that makes it very difficult to cleanly build this software in a repeatable way.
Ok. Dunno. I just ./configure && make && make install (or actually the equivalent in my Gentoo ebuild) and it's very repeatable for me.
I am wondering .. to become the new upstream?
Could you do it?
This tool is useful enough to us that we should probably ask Eric if we can bring it over to the lb.o SVN and keep it on life support for a while.
Jordan
On Mon, Jul 30, 2007 at 08:46:36AM -0600, Jordan Crouse wrote:
On 29/07/07 05:20 +0200, Peter Stuge wrote:
I am wondering .. to become the new upstream?
Could you do it?
This tool is useful enough to us that we should probably ask Eric if we can bring it over to the lb.o SVN and keep it on life support for a while.
Sure - just another subdir in utils.
Eric?
//Peter
-
Jordan Crouse -
Martin-Éric Racine -
Peter Stuge