Ede, Isac, and all - thank you
The world is complicated and fortunately we have differing vision on the
same thing :-)
Robo
--
-
E=mc2
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/li
On Wed, Feb 24, 2010 at 12:57 AM, Swapnil Pimpale
wrote:
> Hi all,
>
> I am a final year engineering student and I am doing my project in
> GRUB-1.97~beta4 and Linux Kernel 2.6.24.7.
>
> I am working on Intel Core 2 Duo architecture. I want to boot a
> separate kernel on the second core.
> As o
Hi all,
I am a final year engineering student and I am doing my project in
GRUB-1.97~beta4 and Linux Kernel 2.6.24.7.
I am working on Intel Core 2 Duo architecture. I want to boot a
separate kernel on the second core.
As of now, I have brought up the halted AP from the GRUB by sending
IPIs in
.
gcc -Ikern/generic -I/build/grub2-1.98~20100223/kern/generic -nostdinc -isystem
/usr/lib/gcc/x86_64-linux-gnu/4.3.2/include
-I/build/grub2-1.98~20100223/include -I. -I./include -Wall -W -Os
-DGRUB_MACHINE_IEEE1275=1 -Wall -W -Wshadow -Wpointer-arith
-Wmissing-prototypes-W
Hi,
On Feb/23/2010, edgar.sol...@web.de wrote:
> He never stated why he wanted it exactly. Maybe he just want's not to
> confuse an everyday user.
or just for fun :-)
--
Carles Pina i Estany
http://pinux.info
___
Grub-devel mailing list
Gr
On 22.02.2010 20:45, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
Robo L wrote:
Hi all
Thanks for reply.
Colins:
It is a possible, I must check it. I tell You soon.
Richard,
I see, that I must stop it. Licence is Licence, but for my experience
I check it what is a solution.
You do not have to
What is this all about?
There are two topics here.
A) How can he remove the message?
B) Is removing it a violation of the license?
Answer to the first question A is already given.
Answer to B is short, but plain simple.
GPL gives everybody the right to modify the software as he/she wants to.
On
Seth Goldberg wrote:
> Hi,
>
> Are these no-prototype warnings normal/expected?
>
GRUB team doesn't manage files under lib/libgcrypt(-grub), they are
imported unmodified from libgcrypt. If you want them fixed, feel free to
contact libgcrypt team and the change will propagate on next resync
>
> gcc
