> >> In the meantime, I've assigned copyright of my work (excluding the
> >> AES and RIPEMD implementations) to the FSF. The documents are
> >> probably already waiting in my mailbox at home. I'll get the
> >> signing done once I'm back home at the end of this month.
> > I assume that I shall need
> > I was about the review Simon's patch. What is the best way to
> > proceed. More than one person works on this and I am confused about
> > how to deal with this. Would it help if Simons work got in first,
> > or didn't you continue with this, but did you just pick pieces of
> > code from him
> > What's missing to get my code into GRUB2 mainline?
> I think you'll have to assign copyright to the FSF.
What part of it?
I learned that Michael Gorven already replaced the problematic parts
(RIPEMD and AES) with versions from libgcrypt. The rest of the code is
all GPL3. Is it about the extra
Hi,
is it true that GRUB2 multiboot, while supporting ELF64 images, does
not switch to long mode on its own, before booting the kernel image?
Thanks,
Simon
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Hi,
I built a Multiboot2 compliant kernel, but GRUB2 (current CVS) crashes
when loading (not booting) it (i.e. as soon as I execute the multiboot
command on it). I assert this is a bug in GRUB2, as it should print out
an error message if there's something wrong with my image.
I traced the bug bac
Hi,
is my patch for strong crypto support going to make it into GRUB2
mainline?
Thanks,
Simon
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
ub2-orig/crypto/rmd160.c
> > 1970-01-01 01:00:00.0 +0100 +++
> > grub2/crypto/rmd160.c 2007-09-02 00:52:57.0 +0200 @@
> > -0,0 +1,430 @@ +/*
> > + * 2007-09-01: Modified for GNU GRUB by Simon Peter
> > <[EMAIL PROTECTED]>.
> > + */
> &
> > and correcting the two header file dependencies (not
> > the binaries depend on the headers, but one of the source files,
> > respectively).
> This doesn't sound right. Since the source files (grub-setup.c,
> grub-probe.c) are not dynamicaly generated, make doesn't need a rule
> to "build" the
Hi!
> > Making this work properly might be a bit trickier. I myself don't
> > understand it (plus, I'm ruby illiterate), so I'm afraid I can't be
> > of help on this.
> Thank you for your response. As I said, it's pretty much a band-aid
> response. I'll take deeper look at the build process.
I
