Hello,
I'd like to test grub2 through netboot (I previously succesfully use
old grub with etherboot or pxe interfaces). I've downloaded latest
grub2 Debian source package (version 1.94+20060926-1) and compiled it,
and look for information on the wiki, but without success now.
In the wi
Quoting Marco Gerards <[EMAIL PROTECTED]>:
Hi,
a few remarks:
[...]
>
> Menu entries
>
>
> Menu entries are added with `menuentry' (or its alias `@'). It's
> important to notice this is not a command. Because it's part of the
> scripting syntax, it can have unique feat
As usuall I had to reinstill Windows. Now I cannot get to Kubuntu. I can use
a start disck to gae to the install section and open a terminal. The last
time this happened I could go to a terminal in kubuntu and get to grub. I do
not remember how I proceeded from there. Please help/
Thanks Dick Barm
Thanks for sending this out Vincent!
I had an opportunity to test it. It works well enough to mount a
filesystem, but unfortunately beyond that it was rather flaky:
grub> ls -l (disk,3)/boot
DIR symtypes-2.6.16.21-0.8-ppc64.gz/
DIR vmlinux-2.6.16.21-0.8-ppc6
On Sun, 8 Oct 2006, Marco Gerards wrote:
It seems to stop at 256 characters counting the input length
That's weird. Could you please have a look at loader/i386/pc/linux.c
to see if it gets the entire line or just a part. Perhaps this
limitation is in the protocol used to pass the command li
On Tue, 10 Oct 2006, Jeff Chua wrote:
Here's with ChangeLog included.
On Sun, 8 Oct 2006, Marco Gerards wrote:
It seems to stop at 256 characters counting the input length
That's weird. Could you please have a look at loader/i386/pc/linux.c
to see if it gets the entire line or just a pa
On Tue, 2006-10-10 at 09:03 +0800, Jeff Chua wrote:
>
> +#include
I don't think this is a good idea because it requires we build on a
Linux host.
-Hollis
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-deve
On Mon, 9 Oct 2006, Hollis Blanchard wrote:
+#include
I don't think this is a good idea because it requires we build on a
Linux host.
Shall I use '#ifdef __linux__' to include only on linux, and
'#define COMMAND_LINE_SIZE 255' for non-linux system?
Sorry, I only thought of using grub2 on
On Tue, 2006-10-10 at 11:08 +0800, Jeff Chua wrote:
> On Mon, 9 Oct 2006, Hollis Blanchard wrote:
>
> >> +#include
> >
> > I don't think this is a good idea because it requires we build on a
> > Linux host.
>
> Shall I use '#ifdef __linux__' to include only on linux, and
> '#define COMMAND_LINE
On Mon, 9 Oct 2006, Hollis Blanchard wrote:
Shall I use '#ifdef __linux__' to include only on linux, and
'#define COMMAND_LINE_SIZE 255' for non-linux system?
5B> Well, does this number change often? If not, let's just copy it.
If so, then we're screwed anyways because asm/param.h would o
Hollis Blanchard <[EMAIL PROTECTED]> writes:
> On Tue, 2006-10-10 at 11:08 +0800, Jeff Chua wrote:
>> On Mon, 9 Oct 2006, Hollis Blanchard wrote:
>>
>> >> +#include
>> >
>> > I don't think this is a good idea because it requires we build on a
>> > Linux host.
>>
>> Shall I use '#ifdef __linux__
Jeff Chua <[EMAIL PROTECTED]> writes:
> On Mon, 9 Oct 2006, Hollis Blanchard wrote:
>
>>> Shall I use '#ifdef __linux__' to include only on linux, and
>>> '#define COMMAND_LINE_SIZE 255' for non-linux system?
>>
> 5B> Well, does this number change often? If not, let's just copy it.
>>
>> If so, t
12 matches
Mail list logo