Bug-grub digest, Vol 1 #182 - 13 msgs

From: [at]} <bug-grub-request{> Date: Tue, 27 Feb 2001 12:03:07 -0500 · > Hello grubbers,

-- 
groetjes, carel
--__--__--
Message: 4
To: fm3{([at]})nowhere.xyCc: bug-grub{([at]})nowhere.xySubject: Re: Fw: GRUB: Hercules console and vbeset command
From: OKUJI Yoshinori <okuji{([at]})nowhere.xyDate: Tue, 27 Feb 2001 22:00:33 +0900
I'm sorry that I couldn't have enough time as soon as I got your
patch, but I finally added hercules support into the CVS
version. Because I didn't think the code should be written in
assembly, I translated it to C with inline assembly. In addition, I
separated the hercules console type from the normal console type.
Note that I haven't tested the code, because I have no hercules
terminal here. If you find any error, let me know, please.
Thanks,
Okuji
--__--__--
Message: 5
To: jgarzik{([at]})nowhere.xyCc: bug-grub{([at]})nowhere.xySubject: --disable-auto-linux-mem-opt (Was: Re: ack! grub bug...)
From: OKUJI Yoshinori <okuji{([at]})nowhere.xyDate: Wed, 28 Feb 2001 00:24:12 +0900
With the CVS version, you can now specify
`--disable-auto-linux-mem-opt' to the configure script.
Okuji
--__--__--
Message: 6
To: tlaronde{([at]})nowhere.xyCc: bug-grub{([at]})nowhere.xySubject: Re: [PATCH] Displaying boot file name after calling bootp
From: OKUJI Yoshinori <okuji{([at]})nowhere.xyDate: Wed, 28 Feb 2001 00:32:27 +0900
From: Thierry Laronde <tlaronde{([at]})nowhere.xySubject: [PATCH] Displaying boot file name after calling bootp
Date: Sat, 24 Feb 2001 22:32:24 +0100
> The information about the name of the boot file is, for me, needed,
Why?
Okuji
--__--__--
Message: 7
To: thasegawa{([at]})nowhere.xyCc: bug-grub{([at]})nowhere.xySubject: Re: [patch] grub-install for FreeBSD
From: OKUJI Yoshinori <okuji{([at]})nowhere.xyDate: Wed, 28 Feb 2001 00:34:10 +0900
From: HASEGAWA Tomoki <thasegawa{([at]})nowhere.xySubject: [patch] grub-install for FreeBSD
Date: Mon, 26 Feb 2001 20:49:53 +0900 (JST)
> I hack grub-install utility for FreeBSD(-4.2).  I test only
> installation to /dev/ad0 on my FreeBSD-4.2-STABLE machine, but even da
> or so will work.
Many thanks for your contribution! I'll apply your patch.
Okuji
--__--__--
Message: 8
From: "Gregg C Levine" <hansolofalcon{([at]})nowhere.xyTo: "Bug-Grub" <bug-grub{([at]})nowhere.xySubject: RE: [PATCH] Displaying boot file name after calling bootp
Date: Tue, 27 Feb 2001 10:40:00 -0500
Hello from Gregg C Levine normally with Jedi Knight Computers
How about why not? Play both sides of the problem. If he would want
the bootp process to display that kind of information, ask yourself
how hard it would be to code it into a program. And then try it. If it
works, and you like the way it works. Check in the patch then, and
then from that, release the version, through CVS first of course, and
then to the ftp servers.
----
Gregg C Levine mailto:hansolofalcon{([at]})nowhere.xy"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps
one of the most powerful of all of the Jedi Knights))
(This company dedicates this E-Mail to Master Yoda
(Perhaps the other one of the most powerful of all of the Jedi
Knights))
And the favorite line by Anonymous "May the Force be with you."
> -----Original Message-----
> From: bug-grub-admin{([at]})nowhere.xy> [mailto:bug-grub-admin{([at]})nowhere.xy> OKUJI Yoshinori
> Sent: Tuesday, February 27, 2001 10:32 AM
> To: tlaronde{([at]})nowhere.xy> Cc: bug-grub{([at]})nowhere.xy> Subject: Re: [PATCH] Displaying boot file name after calling bootp
>
>
> From: Thierry Laronde <tlaronde{([at]})nowhere.xy> Subject: [PATCH] Displaying boot file name after calling bootp
> Date: Sat, 24 Feb 2001 22:32:24 +0100
>
> > The information about the name of the boot file is, for
> me, needed,
>
> Why?
>
> Okuji
>
> _______________________________________________
> Bug-grub mailing list
> Bug-grub{([at]})nowhere.xy> http://mail.gnu.org/mailman/listinfo/bug-grub
--__--__--
Message: 9
To: kaz-hori{([at]})nowhere.xyCc: bug-grub{([at]})nowhere.xySubject: Re: Patch for EtherExpressPro100
From: OKUJI Yoshinori <okuji{([at]})nowhere.xyDate: Wed, 28 Feb 2001 00:40:41 +0900
From: HORIKAWA Kazunori <kaz-hori{([at]})nowhere.xySubject: Patch for EtherExpressPro100
Date: Tue, 27 Feb 2001 00:58:59 +0900
> Reading EEPROM failed in new EtherExpressPro100 card.
> This patch fixes it.
Thanks for your contribution. But, since the device drivers are derived
from Etherboot, I don't want to modify the code directly, if
possible. So, could you contact Etherboot developers, so Etherboot
works with your card? Once Etherboot is fixed, we can port the code to
GRUB in a normal way.
Regards,
Okuji
--__--__--
Message: 10
To: thierry{([at]})nowhere.xyCc: bug-grub{([at]})nowhere.xySubject: Re: [PATCH] default_entry and fallback
From: OKUJI Yoshinori <okuji{([at]})nowhere.xyDate: Wed, 28 Feb 2001 00:41:35 +0900
From: Thierry Laronde <thierry{([at]})nowhere.xySubject: [PATCH] default_entry and fallback
Date: Mon, 26 Feb 2001 17:33:07 +0100
> By default, if the default is wrong, it is reset to 0. Some users were a bit
> puzzled about that, expecting the default to be set to fallback.
That's a good idea. Thanks.
Okuji
--__--__--
Message: 11
Date: Tue, 27 Feb 2001 16:59:30 +0100
From: Thierry Laronde <thierry{([at]})nowhere.xyTo: OKUJI Yoshinori <okuji{([at]})nowhere.xyCc: bug-grub{([at]})nowhere.xySubject: Re: [PATCH] default_entry and fallback
On Wed, Feb 28, 2001 at 12:41:35AM +0900, OKUJI Yoshinori wrote:
> From: Thierry Laronde <thierry{([at]})nowhere.xy> Subject: [PATCH] default_entry and fallback
> Date: Mon, 26 Feb 2001 17:33:07 +0100
> 
> > By default, if the default is wrong, it is reset to 0. Some users were a bit
> > puzzled about that, expecting the default to be set to fallback.
> 
> That's a good idea. Thanks.
Can you add (suggested by Nicolas Boos <nicolas.boos{([at]})nowhere.xyChangeLog please ? I have forgotten to tell who has reported the problem.
Thanks.
-- 
Thierry LARONDE, Centre de Ressources Informatiques, Archamps - France
http://www.cri74.org
PingOO, serveur de com sur distribution GNU/Linux: http://www.pingoo.org
--__--__--
Message: 12
Date: Wed, 28 Feb 2001 01:11:08 +0900
From: HORIKAWA Kazunori <kaz-hori{([at]})nowhere.xyTo: OKUJI Yoshinori <okuji{([at]})nowhere.xyCc: bug-grub{([at]})nowhere.xySubject: Re: Patch for EtherExpressPro100
> Thanks for your contribution. But, since the device drivers are derived
> from Etherboot, I don't want to modify the code directly, if
> possible. So, could you contact Etherboot developers, so Etherboot
> works with your card? Once Etherboot is fixed, we can port the code to
> GRUB in a normal way.
I checked ehterboot.
Current version of etherboot has already fixed it.
So, patch is not needed.
Thanks.
--__--__--
Message: 13
Date: Tue, 27 Feb 2001 17:22:06 +0100
From: Thierry Laronde <thierry{([at]})nowhere.xyTo: GRUB mailing list <bug-grub{([at]})nowhere.xySubject: [netboot] A multiboot compliant GRUB ?
Hello,
With the GRUB we have a very powerful tool. For example, as everybody might
know, you can compile GRUB with the support of all PCI NIC cards, and you
will be able to boot via the network any unknown machine with a supported
PCI NIC card.
I'd liked to call GRUB, via the network, to propose a menu, but, at the
moment, this is not possible since there is only nbi or pxe GRUB.
To add support for nbi or pxe is something I can think about... But what
about taking GRUB as the examplary kernel for the multiboot specification ?
Then GRUB could be loaded via GRUB (on a floppy or on a disk), since GRUB
can load multiboot compliant kernels ?
Just an idea ;)
-- 
Thierry LARONDE, Centre de Ressources Informatiques, Archamps - France
http://www.cri74.org
PingOO, serveur de com sur distribution GNU/Linux: http://www.pingoo.org
--__--__--
_______________________________________________
Bug-grub mailing list
Bug-grub{([at]})nowhere.xyhttp://mail.gnu.org/mailman/listinfo/bug-grub
End of Bug-grub Digest